OCSB Unexpectedly Sends A Cancel Message When The Callee Party Is Busy
(Doc ID 1324634.1)
Last updated on MARCH 18, 2019
Applies to:Oracle Communications Service Broker - Version 3.1.0 and later
Information in this document applies to any platform.
In the following call flow:
1. A party calls B party, but B party is busy.
2. If B party is busy, we play an announcement for the A party. After the announcement we have to release the call with an appropriate cause code.
AS gets the 486 message (B party is busy) and the OCSB unexpectedly sends a CANCEL message.
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