> -----Original Message-----
> From: ext Vijay Kamath [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 15, 2002 10:05 AM
> To: [EMAIL PROTECTED]
> Cc: AJIT KATANKOT
> Subject: [Sip-implementors] Preconfigured route
>
>
> 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.
well, their implementation is buggy. Even in obsolete RFC2543, the proxy had to
examine the route-header.
/Hisham
> 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
>
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
