Diameter Data Sessions End Abruptly After a Given Amount of Data Has Been Consumed (Doc ID 1417650.1)

Last updated on MARCH 27, 2015

Applies to:

Oracle Communications Network Charging and Control - Version: 2.2.0 to 4.2.0 - Release: 2.2 to 4.2
Information in this document applies to any platform.

Symptoms

Diameter data sessions are getting terminated on every attempt exactly when the same amount of data has been consumed by the end user.

Every time, an user is able to establish a data session, but the session is getting terminated abruptly by the Diameter Control Agent (DCA) even though he still has sufficient funds in his wallets for the data session to continue.

By activating selective call tracing on slee_acs or full debug, the following can be observed in the slee_acs log file (location of this log file depends on the implementation constraints):

2012/02/13 16:55:10 FOXActionHandler.cc 332 [5902] foxActionsAPI Message Received:
2012/02/13 16:55:10 FOXActionHandler.cc 333 [5902] foxActionsAPI Map of 4 elements:
2012/02/13 16:55:10 FOXActionHandler.cc 333 [5902] foxActionsAPI [ACTN] = 'NACK'
2012/02/13 16:55:10 FOXActionHandler.cc 333 [5902] foxActionsAPI [BODY] = Map of 2 elements:
2012/02/13 16:55:10 FOXActionHandler.cc 333 [5902] foxActionsAPI [CODE] = 'MAXL'
2012/02/13 16:55:10 FOXActionHandler.cc 333 [5902] foxActionsAPI [WHAT] = "Maximum call length of 7200.00 seconds exceeded "

Changes

While this may be a preexisting problem, changing the "Maximum Call Length (secs)" field in the "Edit Product Type" screens can be the cause of the issue.

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