org.mobicents.servlet.sip.core.dispatchers.DispatcherException

Unexpected >> exception while processing response : SIP/2.0 200 OK >> Call-ID: 17f8ab6df40d3244...@192.168.1.65 >> CSeq: 3 REGISTER >> From: >> <sip:+3460...@rcs.alcatel-lucent.com>;tag=41081757_85c9a2a2_48934332311391 >> To: >> <sip:+346...@rcs.alcatel-lucent.com>;tag=SD799ba99-4a78064c-1263206286238790 >> Via: SIP/2.0/UDP >> 192.168.1.65:5080;branch=z9hG4bK48934332311391_85c9a2a2_48958179429610 >> Contact: >> <sip:192.168.1.65:5080;transport=udp>;expires=0;+g.oma.sip-im;+g.3gpp.app_ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-is" >> Date: Mon, 11 Jan 2010 10:38:06 GMT >> P-Associated-URI: >> <sip:+346...@rcs.alcatel-lucent.com>,<tel:+3460000000000> >> Server: Alcatel-Lucent-HPSS/3.0.3 >> Content-Length: 0 >> >> at >> org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher$1.dispatch(ResponseDispatcher.java:314) at >> org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:55) at >> org.mobicents.servlet.sip.core.dispatchers.DispatchTask.run(DispatchTask.java:50) at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web17

  • via Google Groups by Roberto, 11 months ago
    %3A3gpp-application.ims.iari.gsma-is" > Date: Mon, 11 Jan 2010 10:38:06 GMT > P-Associated-URI: > <sip:+346...@rcs.alcatel-lucent.com>,<tel:+3460000000000> > Server: Alcatel-Lucent-HPSS/3.0.3 > Content-Length: 0 > > at
  • via Google Groups by AyhanKemal, 1 year ago
    Cannot find the corresponding sip application session to this subsequent request BYE sip:192.168.20.107:5080;transport=udp SIP/2.0 Via: SIP/2.0/UDP 192.168.20.107:5065;branch=z9hG4bK- d8754z-1c1eab5ab65b4973-1---d8754z-0718dzsd Via: SIP/2.0/UDP
  • via Google Groups by QTuan, 1 year ago
    =08849591_8a1e29b3_41891793299844 From: <sip:tran@open-ims.test>;tag=2 CSeq: 4 BYE Call-ID: 2-1...@157.159.16.91 User-Agent: Sip EXpress router(2.1.0-dev1 OpenIMSCore (i386/linux)) Reason: SIP;cause=503;text="Session Time-out on S-CSCF" Content-Length: 0 , it may already have been invalidated or timed out
  • Stack trace

    • org.mobicents.servlet.sip.core.dispatchers.DispatcherException: Unexpected >> exception while processing response : SIP/2.0 200 OK >> Call-ID: 17f8ab6df40d3244...@192.168.1.65 >> CSeq: 3 REGISTER >> From: >> <sip:+3460...@rcs.alcatel-lucent.com>;tag=41081757_85c9a2a2_48934332311391 >> To: >> <sip:+346...@rcs.alcatel-lucent.com>;tag=SD799ba99-4a78064c-1263206286238790 >> Via: SIP/2.0/UDP >> 192.168.1.65:5080;branch=z9hG4bK48934332311391_85c9a2a2_48958179429610 >> Contact: >> <sip:192.168.1.65:5080;transport=udp>;expires=0;+g.oma.sip-im;+g.3gpp.app_ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-is" >> Date: Mon, 11 Jan 2010 10:38:06 GMT >> P-Associated-URI: >> <sip:+346...@rcs.alcatel-lucent.com>,<tel:+3460000000000> >> Server: Alcatel-Lucent-HPSS/3.0.3 >> Content-Length: 0 >> >> at >> org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher$1.dispatch(ResponseDispatcher.java:314) at >> org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:55) at >> org.mobicents.servlet.sip.core.dispatchers.DispatchTask.run(DispatchTask.java:50) at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)

    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

    You’re the first here who have seen this exception.