The Session Time Was Not Calculated Properly in Radius Update Packet
(Doc ID 1113414.1)
Last updated on MARCH 19, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
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 :
For update packet:
-- 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
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