OCCAS-SC doesn't disable IMSSF B2B SAL CPC Header propagation
(Doc ID 1968950.1)
Last updated on APRIL 17, 2019
Applies to:Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and later
Information in this document applies to any platform.
In CAP2 Mediation solution, when SCP arms trigger (using a RequestReportBCSM) and sends a Connect, OCCAS-SC sends the Connect message to the network with callingPartysCategor copied from the Initial Detection Point.
There can be an issue caused by the B2B propagation of SALCPC header which will cause the IMSCF to create a Connect with additional information that doesn't exist in the original Connect from SCP.
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