SIP IMS P-CSCF P-Asserted Identity in Responses
In releases earlier than Release S-C6.1.0, the Oracle Communications Unified Session Manager—operating as a P-CSCF—removes the P-Preferred-Identity header (if present) on receipt of a 1xx or 2xx response. It also inserts a P-Asserted-Identity header with the value received in the P-Preferred-Identity header.
Release S-C6.1.0 changes this behavior. Now the Oracle Communications Unified Session Manager:
- Caches a copy of the P-Called-Party-ID header when it receives one of the following destined for a UE prior to forwarding the request:
- An initial request for dialog
- A request for a standalone transaction
- A request for an unknown method that does not related to an existing dialog
The SIP interface receiving the request should have the SIP IMS feature enabled.
- Removes the P-Preferred-Identity header (if present) and inserts a P-Asserted-Identity header with the value saved from the P-Called-Party-ID header on receipt of a 1xx or 2xx response.