Diameter Control Agent (DCA) Fails to End Data Session When Released from Control Plan (Doc ID 1392504.1)

Last updated on JUNE 28, 2012

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 to 4.4.0 [Release 2.2 to 4.4]
Information in this document applies to any platform.

Symptoms

Scenario:

A user initiates a data session from handset. The Gateway GPRS Support Node (GGSN) triggers the Diameter Control Agent (DCA) with a Credit-Control-Request (CCR) that contains a Multiple-Services-Indicator Attribute-Value Pairs (AVP).

DCA then triggers a control plan which releases the call with release cause 31 because the subscriber has insufficient credit.

DCA then responds with a Credit Control Answer (CCA) that has Result-Code [2001] (success). Note that the CCA also has an Multiple Service Credit Control (MSCC) AVP, containing a (pre-configured) Rating-Group AVP of 200, but no Granted-Units AVP.

This is problematic: although the control plan releases the session, there is no indication sent back to the GGSN that the session must end.

After this has happened, the data session for the user simply continues (although he is not able to use any data, because no service units were granted).

When the user finally ends the session, this triggers the GGSN to send a Termination-Request.
DCA does not recognise this message (because internally it has ended the session already) and errors with:

ERROR: {960124} CC-Request-Type 3 received in state Idle.


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