Double ReleaseCall And SIP Race Condition On Simultaneous A/B Disconnect.
(Doc ID 1959195.1)
Last updated on FEBRUARY 22, 2019
Applies to:
Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and laterInformation in this document applies to any platform.
Symptoms
On : OCCAS-SC 6.1.0 version
When A attempts to have a call with B, the following warnings can be seen in the log file:
Steps to reproduce:
-------------------------
The issue can be reproduced at will with the following steps:
1. A and B are in a statefull call, ApplyCharging is active for A.
2. When B disconnects, the AS releases A as well by sending an INFO message (cause=902;text=BYE).
3. If A disconnects before OCSC sends out the requested releaseCall message, OCSC will generate a second releaseCall for the same call
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |