Oracle SCA - Running Multiple SCA Instances And Call-ID Non-uniqueness

(Doc ID 2205844.1)

Last updated on NOVEMBER 22, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.


This addresses an scenario where the customer has multiple SCA instances, each with it's own IP address. There might be a SIP softswitch that has SIP trunks set up, one for each SCA instance.

There is one issue that was identified when running more than one SCA instance: there are 2 completely different calls to SCA in B2BUA mode being made to 2 different instances of SCA. Each instance of SCA happens to have assigned the exact same SIP Call-ID value on the B-leg of the call to the two different calls. This means there are cases of Call-ID collision, which impacts the system.

This was tested and confirmed for NCC 4.4.1 but it might affect newer versions of NCC.


 No changes have been noted on the environment, product, account or hardware.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms