Radius Control Agent (RCA) Access-Accept Message Contains Event-Timestamp from the Past

(Doc ID 1357588.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 17-Mar-2013***

Symptoms

When Radius Control Agent (RCA) receives two consecutive packets on the same conversation having the same identifier field, RCA considers the second packet as a resend of the first one, and resends the same response. The correct behavior is that a packet resend is a packet that has the same source IP address, source port and identifier and which is sent within a short time frame from the previous packet (usually between 5 to 30 seconds).

Below is a diagram showing this scenario:



In the above example, the first two Access-Request messages received a correct response from the Radius Control Agent (RCA). The third Access-Request, however, was considered by RCA as a resend of the second Access-Request message and RCA responded with the same Access-Accept message, which is wrong.

Below is an extract from a snoop trace, showing more details about the parameters in each message in the above diagram:

Please note that not all fields are shown below. Only the fields relevant to this issue are shown.


1- Access-Request (id=176):

 

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