Double ReleaseCall And SIP Race Condition On Simultaneous A/B Disconnect.
Last updated on JUNE 18, 2018
Applies to:Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and later
Information in this document applies to any platform.
On : OCCAS-SC 6.1.0 version
When attempting A has a calling 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
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