SIP-IMS Surrogate Registration Proxy Authorization Header for Non-Register Requests
The Oracle Communications Session Delivery Manager’s IMS functionality helps customers who use SIP IP PBX or SIP gateways that can only peer with carriers connected to IMS via a P-CSCF. As part of this function, the Oracle Communications Session Delivery Manager provides for generating a Proxy-Authorization or Authorization header for REGISTER requests that are challenged. This feature extends the Oracle Communications Session Delivery Manager’s capabilities by also allowing you to configure the generation of Proxy-Authorization and Authorization headers for non-REGISTER requests.
When you configured it to do so, the Oracle Communications Session Delivery Manager caches Proxy-Authorization or Authorization headers from the most recent (last-sent) messages in the following exchange: REGISTER--407 Proxy Authentication Required--REGISTER--200. Then the system uses these values in the subsequent requests. The following methods are supported:
- INVITE
- ACK
- BYE
- CANCEL
- UPDATE
- INFO
- PRACK
- OPTIONS
The Oracle Communications Session Delivery Manager updates the following parameters when it generates the header:
- nonce-count—Incremented for every new request the Oracle Communications Session Delivery Manager receives
- response—Contains the digest-request, newly generated using the cnonce, nonce, and other fields as input
In addition, the system supports the nonce text parameter in the Authentication-Info header. And for surrogate registration, it recognizes the Authentication-Info header in 200 OK responses received from the UAS and updates its cached nonce value accordingly; in this case, the system resets the nonce count to 1 for the subsequent request.