search

himalaya51 / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

CANCEL not proxied after INVITE #164

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Send an INVITE that will be proxied.
2.Send a CANCEL for that INVITE before a final response is received.

What is the expected output? What do you see instead?
I expect the CANCEL to be proxied as the INVITE was.
The CANCEL is responded to with a 200 Cancelling, but is not proxied.

What version of the product are you using? On what operating system?
I'm using sipservlets 1.7.0 on CentOS5.8

Please provide any additional information below.
I've attached a copy of the servlet I used for testing along with the SIPp 
scripts I used and a wireshark trace of the output. 
I ran the SIPp server on 127.0.0.2 and the client on 127.0.0.1 and the servlet 
was running on 172.16.0.49.

Original issue reported on code.google.com by mark.woo...@telsis.com on 19 Sep 2012 at 2:18

Attachments:

GoogleCodeExporter commented 8 years ago 
The version of mobicents I was using was 
mss-1.7.0.FINAL-apache-tomcat-7.0.26-1204061634

Original comment by mark.woo...@telsis.com on 19 Sep 2012 at 2:21

GoogleCodeExporter commented 8 years ago 
This could be related to 
http://code.google.com/p/sipservlets/issues/detail?id=33

Original comment by mark.woo...@telsis.com on 19 Sep 2012 at 2:45

GoogleCodeExporter commented 8 years ago 
There are a couple of errors in client_SimpleSipServletTest.xml. The Via lines 
in the INVITE and the CANCEL should be identical. Also there should be no 
[routes] line in the CANCEL.

With those changes sip-server.log is showing a NullPointerException being 
raised:

2012-10-09 17:21:41,534 ERROR 
[org.mobicents.servlet.sip.core.dispatchers.DispatchTask] 
(MSS-Executor-Thread-0) Unexpected exception while processing message CANCEL 
sip:333011000@127.0.0.2 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK269211_1
From: "sipp" <sip:333017890@sip.telsis.com>;tag=269211
To: "sut" <sip:333011000@127.0.0.2>
Call-ID: 1-26921@127.0.0.1
CSeq: 1 CANCEL
Max-Forwards: 70
Content-Length: 0

java.lang.NullPointerException
        at org.mobicents.servlet.sip.core.dispatchers.CancelRequestDispatcher$CancelDispatchTask.dispatch(CancelRequestDispatcher.java:220)
        at org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:61)
        at org.mobicents.servlet.sip.core.dispatchers.DispatchTask.run(DispatchTask.java:56)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)

Original comment by mark.woo...@telsis.com on 9 Oct 2012 at 4:25

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 19 Oct 2012 at 11:18

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 19 Oct 2012 at 11:18

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 5 Jul 2013 at 7:44

GoogleCodeExporter commented 8 years ago 
This issue was updated by revision ce2e261177c7 and revision d5d0c0fe6504. 
Added non regression test, couldn't reproduce the issue against latest HEAD. 
Marking as invalid

Original comment by jean.deruelle on 25 Apr 2014 at 11:05

GoogleCodeExporter commented 8 years ago

Original comment by jean.der...@telestax.com on 25 Aug 2014 at 10:53