SIP PAI Not Preserved in Outgoing INVITES After SRP Interaction
(Doc ID 2237244.1)
Last updated on SEPTEMBER 12, 2018
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), a problem exists in Session Control Agent (SCA) where a Privacy Asserted Identifier (PAI) is not preserved and forwarded in outgoing INVITE Session Initiation Protocol (SIP) headers after slee_acs has interacted with a Specialized Resource Point (SRP) over Intelligent Network Application Protocol (INAP).
SCA is NCC/OC3C SIP Gateway.
This is an example of the problematic call flow:
- The Selection Dependent Routing (SD) node triggers the INVITE to the SRP (which responds with INAP messages)
- The Attempt Terminate (AT) node triggers the INVITE to the actual B-Party
In this example, Frame 18 should include the PAI from Frame 1 (as this is part of the "trusted" SIP network) but due to this issue, the PAI is not forwarded.
More information on the SIP PAI and its use can be found in RFC 3325 "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks".
Integration of NCC/OC3C into a SIP network.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document