My Oracle Support Banner

DCA Never Advertises Root Diameter Session Timeout (Doc ID 3012655.1)

Last updated on APRIL 19, 2024

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 to [Release 4.3 to 15.0.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to [Release 6.0 to 15.0.0]
Information in this document applies to any platform.


On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including, Diameter Control Agent (DCA) does not advise the Diameter network how long it has to reuse a root diameter session after all the sub-sessions have been closed.

When using Diameter Multi-Services-Credit-Control (MSCC), the root level Diameter session can support between 0 to many sub-session each with their own rating session.  For an existing sub-session, if the Diameter network sends a Credit-Control-Request (CCR) Update (CCR-U) without a Request-Service-Units (RSU) Attribute Value Pair (AVP), DCA will close the sub-session, and return just a Credit-Control-Answer Update (CCA-U) with no MSCC AVP.

DCA will then keep the root level Diameter session open for up to the length defined by the tcc parameter before closing it and throwing the error:

ERROR: {960215} sessionFallback timer expired, Session-Id=<SESSION ID>.

Due to DCA not advising the diameter network how long it intended to hold the root session open for reuse, when the network does decide to reuse it, DCA will log another error and return an error to the network:

ERROR: {960204} Abort-Session failure: DIAMETER_UNABLE_TO_DELIVER. Session-Id = <SESSION ID.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.