My Oracle Support Banner

diameterControlAgent Crashes if GGSN Continues Sends Requests for Invalid MSCC Session (Doc ID 2082003.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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


In all versions of Oracle Communications Network Charging and Control (NCC), a problem exists in the diameterControlAgent process where it can crash (due to a Segmentation Fault (SEGV)) if a Gateway General Packet Radio Service (GPRS) Support Node (GGSN) continuously tries to request more units from a MSCC sub-service which the diameterControlAgent has already released.

The following error may be seen in the diameterControlAgent.log just before it crashes:

Oct 24 16:27:15 slc01 diameterControlAgent: [ID 675952 user.error] diameterControlAgent(24958) ERROR: {960210} TCAP_PRE_END received in state ACSent, Session-Id=UGW1UTB_gy;3654691831;210;4174, Charge key = 555


Possible integration with new GGSN or some new type of DIAMETER traffic is hitting the diameterControlAgent.


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.