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)

Google Groups | Roberto | 7 years ago
  1. 0

    Developing a SIP application with SEAM framework

    Google Groups | 7 years ago | Roberto
    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)
  2. 0

    B2BuaHelper: Problem while linking & unlinking sip sessions

    Google Groups | 6 years ago | AyhanKemal
    org.mobicents.servlet.sip.core.dispatchers.DispatcherException: 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 192.168.20.107:5060;branch=z9hG4bK- d8754z-1c1eab5ab65b4973-1---d8754z-0718d Via: SIP/2.0/UDP 192.168.2.48:5060;branch=z9hG4bK- d8754z-1c1eab5ab65b4973-1---d8754z-;rport=5060;received=192.168.2.48 Max-Forwards: 69 Contact: <sip:+12340...@192.168.2.48> To: "Ayhan Kemal" <sip: 01514...@192.168.2.176>;tag=61695038_b61a9482_e3b18293-86b2-4204- b9ac-1150c72689eb From: <sip:+12340...@192.168.2.48>;tag=6370131b Call-ID: 0718d2f91bd32824...@192.168.20.107 CSeq: 2 BYE User-Agent: X-Lite release 1103d stamp 53117 Reason: SIP;description="User Hung Up" Content-Length: 0 , it may already have been invalidated or timed out
  3. 0

    Mobicents Sip Servlet : session duration

    Google Groups | 6 years ago | QTuan
    org.mobicents.servlet.sip.core.dispatchers.DispatcherException: Cannot find the corresponding sip application session to this subsequent request BYE sip:157.159.16.91:5080 SIP/2.0 Via: SIP/2.0/UDP 157.159.16.91:6060;branch=z9hG4bKb11b.0f5364b6.0 To: <sip:sip-servlets- conference@157.159.16.91:4060>;tag=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
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    cannot find the application to handle this subsequent request PRACK

    Google Groups | 7 years ago | Hui WANG
    org.mobicents.servlet.sip.core.dispatchers.DispatcherException: cannot find the application to handle this subsequent request PRACK sip: 127.0.0.1:5080 SIP/2.0 From: <sip:alice@open-ims.test>;tag=1 To: <sip:sport@msm.open-ims.test>;tag=1 Via: SIP/2.0/UDP 127.0.0.1:4060;branch=z9hG4bK491b.45d95c37.0 Via: SIP/2.0/UDP 127.0.0.1:5090;rport=5090;branch=z9hG4bK-5320-1-4 Call-ID: 1-5...@127.0.0.1 CSeq: 2 PRACK Contact: <sip:alice@127.0.0.1:5090> Max-Forwards: 16 RAck: 88 1 INVITE Content-Type: application/sdp P-Asserted-Identity: <sip:alice@open-ims.test> Content-Length: 247 v=0 o=alice 3468086555 3468086555 IN IP4 127.0.0.1 s=A SIPp Stream c=IN IP4 127.0.0.1 t=0 0 m=audio 23002 RTP/AVP 0 8 14 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:14 MPA/8000 q=6.6.5.3 a=recvonly:80 q=6.6.4.1 a=maxCapacity:100
  6. 0

    Cannot find the corresponding sip session to this...

    Google Groups | 7 years ago | R.Domingo
    org.mobicents.servlet.sip.core.dispatchers.DispatcherException: Cannot find the corresponding sip session to this subsequent request ACK sip: +31666@service-test1.test.lan SIP/2.0 Via: SIP/2.0/UDP 192.168.74.121;branch=z9hG4bK657d.72324415.0 From: "sipp" <sip:perftest7@.......ipt2.test.lan:5060>;tag=7 Call-ID: 7-2...@192.168.2.51 To: "+31666" <sip: +31666@........ipt2.test.lan>;tag=11924587_eec49ee4_253705597938625 CSeq: 1 ACK Max-Forwards: 70 User-Agent: .......... (............ (i386/linux)) Content-Length: 0 , it may already have been invalidated or timed out

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. 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()
    2. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:619)
      1 frame