Ivar wrote:
> Hmm, i tought i described well.
>
> But ok, request-URI it the one what "normally" proxy handles locally
> like INVITE and request-URI is in that server.
> But proxy can't process it normally, there is un expected route header
> .... .
I believe the way things are written, the proxy should do whatever
processing it thinks is appropriate based on the R-URI. If that involves
translating the R-URI and forwarding the request, the next hop will be
determined by the Route header.
(I have some problems with this - it would make way more sense to simply
forward based on the Route header if there is one, and do local
processing based on the R-URI only if there are no Route headers.)
Paul
> [EMAIL PROTECTED] wrote:
>> From: Ivar <[EMAIL PROTECTED]>
>> Sender: [EMAIL PROTECTED]
>>
>> Hi,
>>
>> This is dumb question but, if proxy has route header and request-URI is
>> the proxy local, must proxy forward request or handle it ?
>>
>> You must describe the situation more carefully. "A proxy receives a
>> request. In the request, the route header(s) are ... and the
>> request-URI is .... What should the proxy do?"
>>
>> 6. Postprocess routing information
>> 7. Determine the next-hop address, port, and transport
>>
>> By this it is like proxy needs to always use route.
>>
>> I see 2 possibilities there:
>> 1) proxy forwards to route address
>> 2) proxy removes route header and handles it
>>
>> Which one is actually better,cleaner and more rfc compilant.
>>
>> Dale
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
