search

noushadali / sipservlets

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

Proxy implementation not forwarding additional 2xx responses from downstream fork (again) #154

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Send an INVITE to a SIP servlet that is proxied.
2. At the downstream (simulated) forking proxy, return two sets of 180/200 
responses, with different tags in the To: header to indicate different forks.

What is the expected output? What do you see instead?
See: Both 180 responses are forwarded to the UAC, but only one 200 response.
Expected: In the case of a response to an INVITE, the second 2xx response 
should also be proxied.  See JSR 289 10.2.4.1, and RFC 3261 16.7 step 5.

What version of the product are you using? On what operating system?
mss-1.7.0.FINAL-apache-tomcat-7.0.26

Please provide any additional information below.
I've had this problem before, which was reported and fixed under 
http://code.google.com/p/mobicents/issues/detail?id=2390.  The fix lead to some 
CANCEL issues raised under 
http://code.google.com/p/mobicents/issues/detail?id=2616.  The fix to 2616 
looks like it broke the original issue again, but in a different way.  The 
message is getting passed up to the container correctly (mistakenly flagging it 
as a retransmission), but ResponseDispatcher is throwing it away:

2012-08-24 13:03:26,715 DEBUG 
[org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher] 
(Mobicents-SIP-Servlets-UDPMessageChannelThread-4) best final response sent 
200, response status 200 not forwarding response

Original issue reported on code.google.com by gavin.ll...@telsis.com on 24 Aug 2012 at 1:55

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago 
Did you set the SIP Stack property gov.nist.javax.sip.MAX_FORK_TIME_SECONDS to 
a value greater than 0 (10 by example) ?
If so can you provide the logs with org.mobicents category at DEBUG level 
against the latest from 
https://mobicents.ci.cloudbees.com/job/Mobicents-SipServlets-Release/lastSuccess
fulBuild/artifact/ ?

Original comment by jean.deruelle on 25 Apr 2014 at 4:38

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 04c8423e74bc.

Non regression test

(cherry picked from commit f1d5edcc45bd28f9a928d3d928ee0be9f28618b0)

Original comment by jean.der...@telestax.com on 25 Apr 2014 at 6:43

GoogleCodeExporter commented 9 years ago 
comment #5 and test was meant be for Issue 24

Original comment by jean.deruelle on 25 Apr 2014 at 6:45

GoogleCodeExporter commented 9 years ago 
Issue was moved to GitHub:

https://github.com/Mobicents/sip-servlets/issues/29

Original comment by desi.pep...@telestax.com on 18 Dec 2014 at 6:43

GoogleCodeExporter commented 9 years ago

Original comment by jean.deruelle on 18 Dec 2014 at 9:27