org.mobicents.servlet.sip.core.DispatcherException

Cannot find the corresponding sip application session to this subsequent request BYE sip:9988002@192.168.4.160:11180;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.4.204:11180;rport=11180;branch=z9hG4bKBH36Ht963rXeB;received=192.168.4.204 Max-Forwards: 70 From: "Extension 9988001" <sip:9...@192.168.4.204>;tag=KtgZ29USetpNj To: <sip:9...@192.168.4.89>;tag=vN8t8Xm8yXg2K Call-ID: 0e0bee76-943b-1234-4ba8-000c29680286 CSeq: 91266548 BYE Contact: <sip:mod_sofia@192.168.4.204:11180> User-Agent: FreeSWITCH-mod_sofia/1.2.23~64bit Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY Supported: timer,path,replaces Reason: Q.850;cause=16;text="NORMAL_CLEARING" Content-Length: 0 with the following popped route header <sip:192.168.4.89:5060;transport=udp;as=ded31d5f-500e-4c2d-84bb-370065d85c87;appname=1180947b;proxy=true;app_id=7599adf4;lr>, it may already have been invalidated or timed out

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4

  • via Unknown by David Chi,
  • Stack trace

    • org.mobicents.servlet.sip.core.DispatcherException: Cannot find the corresponding sip application session to this subsequent request BYE sip:9988002@192.168.4.160:11180;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.4.204:11180;rport=11180;branch=z9hG4bKBH36Ht963rXeB;received=192.168.4.204 Max-Forwards: 70 From: "Extension 9988001" <sip:9...@192.168.4.204>;tag=KtgZ29USetpNj To: <sip:9...@192.168.4.89>;tag=vN8t8Xm8yXg2K Call-ID: 0e0bee76-943b-1234-4ba8-000c29680286 CSeq: 91266548 BYE Contact: <sip:mod_sofia@192.168.4.204:11180> User-Agent: FreeSWITCH-mod_sofia/1.2.23~64bit Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY Supported: timer,path,replaces Reason: Q.850;cause=16;text="NORMAL_CLEARING" Content-Length: 0 with the following popped route header <sip:192.168.4.89:5060;transport=udp;as=ded31d5f-500e-4c2d-84bb-370065d85c87;appname=1180947b;proxy=true;app_id=7599adf4;lr>, it may already have been invalidated or timed out at org.mobicents.servlet.sip.core.dispatchers.SubsequentRequestDispatcher.dispatchMessage(SubsequentRequestDispatcher.java:248) at org.mobicents.servlet.sip.core.SipApplicationDispatcherImpl.processRequest(SipApplicationDispatcherImpl.java:861) at gov.nist.javax.sip.EventScanner.deliverRequestEvent(EventScanner.java:250) at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:146) at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185) at gov.nist.javax.sip.DialogFilter.processRequest(DialogFilter.java:1324) at gov.nist.javax.sip.stack.SIPServerTransactionImpl.processRequest(SIPServerTransactionImpl.java:811) at gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:578) at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:524) at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:319) at java.lang.Thread.run(Thread.java:722)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.