Enable Local Dispatch Doesn't Work
(Doc ID 2295106.1)
Last updated on AUGUST 24, 2020
Applies to:
Oracle Communications Converged Application Server - Version 7.0.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Converged Application Server (OCCAS), when 'enable local dispatch' is enabled, Invite requests fail to proxy to the next 'chained' application.
Scenario:
Invite is processed by the first application, it gets proxied, the app router sends to next app, but the next app does receive the invite.
If 'enable local dispatch' is turned off then the invite is proxied to the second and third apps. The app router chains together the various applications to support multiple call flows based upon regular expressions from the request URI and previous application router state for the call.
So with 'enable local dispatch' turned off, the invite is chained through all applications and the call works just fine. With 'enable local dispatch' turned on, the call stalls because the second production app never sees the Invite.
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 |