Bad MSS Disconnect ACR Flow IN Non-Compatibility Mode
Last updated on DECEMBER 20, 2017
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 (Application 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.
This issue is happening in non-compatibility mode.
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