My Oracle Support Banner

SGSNs Aborting With CAP-U-ABORT-REASON: Invalid-reference When MAXCORRELATIONIDS is Exhausted (Doc ID 2045892.1)

Last updated on MARCH 12, 2019

Applies to:

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


Network Charging and Control (NCC) version 5.0.1 introduced the CAP version 3 GPRS Control Agent (CAP3GPRS Control Agent). The CAP3GPRS Control Agent is a SLEE application that translates between CAP3 GPRS messages and internal INAP operations.

In Product Version 5.0.2 there is an issue in CAP3GPRS Control Agent when the number of open PDP contexts exceeds MAXCORRELATIONIDS parameter: the originationReference field from any new PDP context is duplicated, causing SGSN to send CAP-U-ABORT-REASON: invalid-reference (6) back to SLC and closing the PDP Contexts.


According to CAP specification:
.."invalid-reference shall be set if the received destinationReference is unknown or for a known destination Reference the received originationReference does not match with the stored originationReference".


In cap3GprsControlAgent log files it can be seen that at one point further, the originationReference field from any new PDP context is duplicated; It is *always* 131583.

The originationReference from the CAP3GPRS should be unique per PDP context since it's based on a "SLEE correlation ID" which should be unique across the entire SLEE.







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.