Status: New
Owner: ----
Labels: Type-Defect Priority-Medium MSS-1.6.0.FINAL Release-Type-FINAL
Roadmap-Fix Component-Sip-Servlets
New issue 2616 by [email protected]: Proxy forwards 487 as well
as 200 to caller
http://code.google.com/p/mobicents/issues/detail?id=2616
What steps will reproduce the problem?
1. Proxy a call to two destinations
2. Answer one leg
What is the expected output? What do you see instead?
I'd expect the 200 OK to the INVITE to be forwarded, but the 487 from the
CANCELed leg to be absorbed.
Instead, both are forwarded to the caller
What version of the product are you using? On what operating system?
mss-1.6.0-SNAPSHOT-jboss-jdk6-5.1.0.GA-1106010345-LGPL on CentOS 5.6
Please provide any additional information below.
Attached is a zip with a Wireshark trace, a server.log and the application.
192.168.0.88 Is the Proxy
192.168.0.83 is a SIPp script acting as the caller
192.168.0.82 is a SIPp script acting as the answering leg
192.168.0.173 is an instance of Blink (0.2.7) running on Windows 7
Call is terminated by a timer expiring (it's what my simple test proxy was
doing anyway...)
Is this related to issue 2390? I'm sure it didn't use to happen.
I didn't spot this in initial testing as all my CANCEL scenario SIPp
scripts base the via in their 487 on the via set in the CANCEL, hence they
terminate at the proxy. Using a real client, the 487 has vias all the way
back to the caller.
Attachments:
487Issue.zip 39.0 KB
