Last updated on DECEMBER 21, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (NCC), when using Session Control Agent (SCA) as the gateway between Session Initiation Protocol (SIP) traffic on the network and Intelligent Network Application Part (INAP) to Advanced Control Services (ACS), a problem exists if the SIP INVITE contains a Privacy Asserted Identity (PAI) with a Display Name to hide the identity of the Calling Party. An example of a Privacy Header Uniform Resource Identifier (URI) with a Display Name in RFC 3325 is:
where "Cullen Jennings" is the Display Name.
When SCA receives a SIP INVITE with a PAI and a Display Name in said PAI, the Initial Detection Point (IDP) created and sent to ACS contains a blank Calling Party field.
New SIP traffic triggering SCA.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms