Two Encoded Extension Types in an IDP from DCA are not both Available in ACS
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.1.0 to 4.3.0 [Release 4.1 to 4.3]
Information in this document applies to any platform.
***Checked for relevance on 25-Nov-2013***
When two encoded format DIAMETER extensions are configured to be passed in the IDP (Initial Detection Point) to slee_acs from the diameterControlAgent, only the extension encoded into the Profile Tag with the lower ID is accessible in an ACS (Advanced Control Services) Control Plan.
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