DiameterControlAgent (DCA) Frequently Reporting "Unknown Session-Id" Error Messages (Doc ID 1363808.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 3.2.0 and later
Information in this document applies to any platform.

Symptoms

A very high number of "Unknown session-id" error messages are reported by the Service Logic Controller's (SLC) diameterControlAgent (DCA) process, which is a gateway for a real-time Online Charging System (OCS), as defined by the RFC (Request for Comments) 4006 - Diameter Credit-Control Application (RFC 4006) standards document.

Example of DCA "Unknown session-id" error message:

Jul 19 03:12:19 slc01 diameterControlAgent: [ID 675952 user.error] diameterControlAgent(5065) ERROR: {960021} Unknown session-id. Origin-Host=ggsn01, Session-Id=ggsn01;123456789;125;64249>

The error messages are mainly being raised when the first Diameter protocol Credit-ControlRequest Update message is received by DCA (sometime after the Credit-ControlRequest Initial begins the diameter session), as shown in the sequence diagram below:

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