We didn't put the "lr" parameter, since the local outbound proxy did not support loose-routing. Hence, the request-uri is that of the proxy, & the topmost Route header has the remote target.
Regards... Vijay
Christer Holmberg wrote:
Hi Vijay, I think you need the "lr" parameter in your pre-defined route, don't you? How will the outbound proxy otherwise know that you are using loose routing?Regards, Christer Holmberg Ericsson Finland Vijay Kamath wrote:At SIPIT11, we found an issue when we want to configure a local outbound proxy using the procedures specified in rfc3261(sec 8.1.2). Here is a sample INVITE which we send :- INVITE sip:1.2.3.4:5060 SIP/2.0 To:ua1<sip:[EMAIL PROTECTED]:5060> From:sipit1<sip:[EMAIL PROTECTED]>;tag=52792329608rc880 Call-ID:130920245025z2qi CSeq:2 INVITE Via:SIP/2.0/UDP 65.243.118.179:5060;branch=z9hG4bK56241282309bvhjg Contact:sip:65.243.118.179 Route:ua1<sip:[EMAIL PROTECTED]:5060> We found that some implentations that didn't support loose-routing, never looked at the topmost ROUTE header for determining the target set. They just look at the request-uri which would be that of the proxy itself, since it is a strict-router. So the proxy responds with 404, as the user part was missing in the request-uri. Is this a backward compatibility problem with older proxies? Regards... Vijay ------------------------------------------------------------------------ Name: Wipro_Disclaimer.txt Wipro_Disclaimer.txt Type: Plain Text (text/plain) Encoding: 7bit
**************************Disclaimer************************************************** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ****************************************************************************************
