SIP Cancel Not Properly Handled If There Are 2 Different Early Dialogs On UAS Side

(Doc ID 1317828.1)

Last updated on JULY 27, 2011

Applies to:

Oracle Communications Converged Application Server - Version: 4.0.0 and later   [Release: 4.0.0 and later ]
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.


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
at com.bea.wcp.sip.engine.server.TransactionManager.receiveRequest(
at com.bea.wcp.sip.engine.server.TransactionManager.receiveMessage(
at com.bea.wcp.sip.engine.server.MessageHandler$MessageQueue.processMessages(

<BEA-330608> <Socket error
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(
at java.lang.Long.parseLong(
at java.lang.Long.valueOf(
at com.bea.wcp.sip.engine.server.SipServletResponseImpl.getTargetClusterId(


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