OCCAS 5.x Terminates the SIP Session on Receipt of a 408 Response for an INFO Request
(Doc ID 1520961.1)
Last updated on AUGUST 11, 2020
Applies to:
Oracle Communications Converged Application Server - Version 5.0.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Communications Converged Application Server (OCCAS) 5.x terminates a SIP session on receipt of a 408 timeout response for an INFO request.
The following SIP message scenarios shows the sending of two SIP INFO requests from an application running inside OCCAS.
Application:
|----INFO------------->|
|<----503--------------|
|----INFO------------->| // WLSS 3.1 and OCCAS 5.0 and 5.1 allow this INFO to be sent.
Application:
|----INFO------------->|
|<----408--------------| // timeout
|-------X-------> | // OCCAS 5.0 and 5.1 does not allow the INFO to be sent; WLSS 3.1 does.
// OCCAS throws a java.lang.IllegalStateException: Could not create request when session is in TERMINATED state!
|----INFO------------->|
|<----503--------------|
|----INFO------------->| // WLSS 3.1 and OCCAS 5.0 and 5.1 allow this INFO to be sent.
Application:
|----INFO------------->|
|<----408--------------| // timeout
|-------X-------> | // OCCAS 5.0 and 5.1 does not allow the INFO to be sent; WLSS 3.1 does.
// OCCAS throws a java.lang.IllegalStateException: Could not create request when session is in TERMINATED state!
The second INFO is unrelated to the first INFO, however it is in the same SIP session as the first INFO.
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 |
| Cause |
| Solution |
| References |