Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-2.0.0.FINAL
Roadmap-Fix
New issue 154 by [email protected]: Proxy implementation not
forwarding additional 2xx responses from downstream fork (again)
http://code.google.com/p/sipservlets/issues/detail?id=154
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
