SCA Ignoring Values of inap_noa_calling_party and inap_noa_called_party Parameters From sca.config File
Last updated on JUNE 13, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (NCC), a problem exists where in the Initial Detection Point (IDP) message sent by the Session Control Agent for Session Initiation Protocol (SIP) (SCA) to slee_acs, the value of Nature of Address (NoA) is different than what is configured in the sca.config file.
There are three parameters in sca.config that can be used to set the NoA for called/calling/redirecting party.
So NoA for calling party is “4”, despite the value set in sca.config being “3”.
This problem appeared after default values of inap_noa_calling_party and inap_noa_called_party parameters from sca.config were changed.
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