OCCAS Response Codes When The APP Is Down
(Doc ID 2631299.1)
Last updated on JANUARY 30, 2024
Applies to:
Oracle Communications Converged Application Server - Version 5.1.0 and laterInformation in this document applies to any platform.
Goal
OCCAS receives the SIP INVITE without the APP being brought up, will it respond with 404? If yes, can we configure the SIP Response Codes to others, such as 408, 5XX ? Or that is hardcoded in OCCAS?
According to the online help, it should respond with 500:
The default behavior of the WebLogic Communications Server instance if the server cannot match an incoming SIP request to a deployed SIP Servlet, or if the matching Servlet has been invalidated or timed out.
Valid values are:
proxy: Act as a stateless proxy server.
ua: Act as a User Agent.
"proxy" is used as the default if you do not specify a value.
When acting as a User Agent (UA), WebLogic Communications Server acts in the following way in response to SIP requests:
ACK requests are discarded without notice.
CANCEL or BYE requests receive response code 481 - Transaction does not exist.
All other requests receive response code 500 - Internal server error.
When acting as a stateless proxy requests are automatically forwarded to an outbound proxy if one is configured. If no proxy is defined, WebLogic Communications Server proxies to a specified Request URI only if the Request URI does not match the IP and port number of a known local address for a SIP Servlet container, or a load balancer address configured for the server. This ensures that the request does not constantly loop to the same servers. When the Request URI matches a local container address or load balancer address, WebLogic Communications Server instead acts as a UA.
Solution
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
| Goal |
| Solution |
| References |