SIP Cancel Not Properly Handled If There Are 2 Different Early Dialogs On UAS Side
(Doc ID 1317828.1)
Last updated on MARCH 01, 2019
Applies to:
Oracle Communications Converged Application Server - Version 4.0.0 to 5.0.0 [Release 4.0.0 to 5.0]Information in this document applies to any platform.
Symptoms
OCCAS does not handle SIP CANCEL request properly if it has 2 different early dialogs on UAS side. Following error stacks are seen:
<BEA-330608> <Socket error
java.lang.NullPointerException
at com.bea.wcp.sip.engine.server.TransactionManager.receiveRequest(TransactionManager.java:854)
at com.bea.wcp.sip.engine.server.TransactionManager.receiveMessage(TransactionManager.java:801)
at com.bea.wcp.sip.engine.server.MessageHandler$MessageQueue.processMessages(MessageHandler.java:590)
......
<BEA-330608> <Socket error
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Long.parseLong(Long.java:424)
at java.lang.Long.valueOf(Long.java:491)
at com.bea.wcp.sip.engine.server.SipServletResponseImpl.getTargetClusterId(SipServletResponseImpl.java:751)
......
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 |