How To Avoid SIP Calls Are Split Between Multiple Engines?
Last updated on FEBRUARY 16, 2018
Applies to:Oracle Communications Converged Application Server - Version 4.0.0 to 5.1.0 [Release 4.0.0 to 5.1]
Information in this document applies to any platform.
***Checked for relevance on 12-Mar-2013***
Given there is a OCCAS replicated domain containing 2 engines and 2 replicas and a SIP application is deployed on the engine cluster.
For the same call, the SIP transactions are split between the engines in the sense that both engines handle request for the same call id.
This makes the near-cache feature of OCCAS not being effectively used which results in lower performance.
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