Oracle SCA - Running Multiple SCA Instances And Call-ID Non-uniqueness
(Doc ID 2205844.1)
Last updated on JANUARY 05, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 4.4.1 to 6.0.0 [Release 4.4 to 6.0]Information in this document applies to any platform.
Symptoms
This addresses an scenario where the customer has multiple SCA(Session Control Agent) instances, each with it's own IP address. There might be a SIP (Session Initiation Protocol) 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 Oracle Communications Network Charging and Control (OCNCC/NCC) 4.4.1 but it might affect newer versions of NCC.
Changes
No changes have been noted on the environment, product, account or hardware.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |