OCCAS-SC doesn't disable IMSSF B2B SAL CPC Header propagation
Last updated on MARCH 27, 2015
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 triggers (using a RequestReportBCSM) and sends a Connect, OCCAS-SC sends the Connect message to the network with callingPartysCategor copied from the Inital 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.
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