OCCAS-SC Continuing Dropped Calls
(Doc ID 2540820.1)
Last updated on AUGUST 24, 2020
Applies to:
Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and laterInformation in this document applies to any platform.
Symptoms
Some calls failed because the Request-URI is not changed according to the CAP Connect GenericNumber; these Invites not being correct.
OCCAS-SC is in fact changing leg states from INITIATED/IDLE to RELEASED, but instead of releasing the calls, the initial Invite is copied to the B2BUA session.
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 |