Last updated on MARCH 27, 2015
Applies to:Oracle Communications Network Charging and Control - Version: 2.4.0
Information in this document applies to any platform.
ACS prior to version 184.108.40.206 behaves the following way:
- If the CgPN did not change during internal processing i.e. the CgPN when sending the connect is the same as the CgPN received in the Initial DP,
- ACS will not set the CgPN in the connect message it sends.
In its default behavior, ACS specifically mentions in debug that it is not setting the calling party in the connect
In the log file (usually located at /IN/service_packages/ACS/tmp/slee_acs.log) if the process has debug turned on, the following can be observed :
2010/02/11 13:43:51 acsChassisTelephony.cc 6472  acsChassisSLEE Not setting calling party number in the connect
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