In Radius Update Packet The Session Time Is Not Calculating Properly (Doc ID 1113414.1)

Last updated on APRIL 23, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.1.0.1 and later   [Release: 7.3.1 and later ]
Information in this document applies to any platform.

Symptoms

The search opcode for Radius stop packet is considering the session-time and Trans_id in the packet whereas the search opcode for Radius update packet is considering only the Trans_id while searching for the event object.

For stop packet :
pvt-(ip-window)-session_time

For update packet:
pvt-(ip-window)

-- Steps To Reproduce:

1. Send the start packet lets take Nov 2 -2009 sent a packet
2. Change the pin virtual time to Nov -4 -2009
3. Use the Acct-Session-Time parameter above 86400 and send the Update packet

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