The Diameter Control Agent (DCA) Refuses Multiple Vendor-Id AVPs Nested in the Vendor-Specific-Application-Id AVP

(Doc ID 1548450.1)

Last updated on MARCH 27, 2015

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.1 to 5.0.0 [Release 4.4 to 5.0]
Oracle Solaris on SPARC (64-bit)

Symptoms

The Diameter Control Agent (DCA) from Oracle Communications Network Charging and Control (OCNCC) is rejecting incoming Credit-Control-Request (CCR) Diameter messages if the CCR contains multiple Vendor-Id (266) AVPs (Attribute-Value-Pair) when nested in a Vendor-Specific-Application-Id (260) Grouped AVP.  The 5009 (DIAMETER_AVP_OCCURS_TOO_MANY_TIMES) error code is sent back to the GGSN (Gateway GPRS Support Node).

This can be seen in a either a network trace, or by enabling DCA debug with the following line reporting the issue:

The 1* means one or more Vendor-Id values must be in the Vendor-Specific-Application-Id AVP.

Changes

New implementation of OCNCC or integration of a new GGSN to an existing OCNCC implementation.

Cause

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