ACR Disconnect Call Flow sends only one BYE to AS
(Doc ID 1623958.1)
Last updated on AUGUST 24, 2020
Applies to:Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 to 6.1.0 [Release 6.1]
Information in this document applies to any platform.
There's an incompatibility between OCSB3 and OCCAS-SC 6.1 handling the following case:
- stateful call, ApplyCharging is used.
- in ApplyCharging, AS (Apllication Server) requests MSC to disconnect the call at the next ACR (ApplyChargingReport).
- OCSB3 sends BYE to AS on both legs, OCCAS-SC 6.1 sends only one BYE to AS.
OCCAS-SC should send 2 SIP BYE messages on both call legs.
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