Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 2561 by [email protected]: Proxy does not support
strict routing
http://code.google.com/p/mobicents/issues/detail?id=2561
What steps will reproduce the problem?
1. Create a proxy
2. Pass an initial INVITE that has a top record-route that DOES NOT have
an ;lr parameter
3. Observe the following ACK before and after the proxy
What is the expected output? What do you see instead?
The ACK arriving at the proxy should have a top-most Route: header with
no ;lr parameter (i.e. it indicates an RFC 2543 compliant "strict routing"
proxy).
The Mobicents proxy should perform the manipulation as per RFC 3261 section
16.12.1.2 (Top of P121).
It appears that Mobicents does not do this processing.
What version of the product are you using? On what operating system?
1.6 Snapshot on CentOS 5.5 and Windows 7
Please provide any additional information below.
This is not terribly urgent, as RFC 2543 proxies are getting increasingly
rare.
The patch to issue 2439 should be retested to ensure that locally generated
BYEs are also correctly reformatted
