SBC delayed release call when small flow guard timer is configured
(Doc ID 2849802.1)
Last updated on NOVEMBER 17, 2023
Applies to:
Net-Net OS - Version S-Cz7.4.0 to S-Cz9.0.0 [Release S-Cz7.0 to S-Cz9.0]Information in this document applies to any platform.
Symptoms
Flow guard timer (initial-guard-timer and subsq-guard-timer) is configured in media-manager or realm (realm-config) for supervising RTP streams and to release SIP sessions in case that no packets are sent for the defined period of time. The default timer is 300 seconds.
For some unique application environment, the flow guard timer is set to the small value of i.e 3 seconds. It is expected that the SBC detects after this timer that no more RTP packets are received an releases the call because of "media timer expiry". However, practically, the call is not released after 3 seconds, but after 12 to 25 seconds
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |