Live AF Sessions Found Dead After NT Service Restarted
(Doc ID 1669112.1)
Last updated on AUGUST 27, 2020
Applies to:Oracle Communications Services Gatekeeper - Version 5.1.0 to 5.1.0 [Release 5.1]
Information in this document applies to any platform.
During fail-over test, it's found that there are missing Session Termination Requests (STRs) from assured-forwarding (AF) session.
This situation was found by counting Authorization and Authentication Request (AAR)/Authorization and Authentication Answer (AAA) and STR/Session Termination Answer (STA) counts in qos.log during the period of Fail-over test.
Normally in the case of applyQosFeature with specified duration, Oracle Communications Services Gatekeeper (OCSG) will start associated timer, when the timer is expired, OCSG will send STR to PCRF and then clear up the qos session.
However, when one of the two Network Tiers (NTs) is restarted as normal operation, the alive qos session created by applyQosFeature with duration will be kept death in the database forever, the reason is that the timer is NT wide, NOT cluster wide.
If applyQosFeature with a specified duration is heavily used, so nearly half of the online qos sessions are lost with NT restart operation.
In such case, it means end user will pay a big unnecessary money or telecom operator will waste network bandwidth.
Note: To have more details on the meaning of AAR/AAA or STR/STA messages, you could check the following reference : http://tools.ietf.org/html/rfc6733
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