[much better to split up the question]

>>but I receive it on UDP, should I strip it? 

I'd leave it, I don't think it matters much, you would
strip the top Route anyway (if the top route is you).

(unless you had different applications running on UDP and TCP,
 I don't think it's important)



>>What if the port is different?
it shouldn't ever be really.
But it could be an issue if you have multiple SIP entities
listening on different ports.
If it came to you on the wrong port, then it's going to break anyway
so you could respond with an error response


Regards,

Attila



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Taisto Qvist XX
Sent: 29 April 2009 14:18
To: [email protected]
Subject: [Sip-implementors] Clarifying RFC3261/3
regardingroute-preprocessing

[On request, splitting my previous question in three more emails...]

Greetings fellow SIPers!
 
I've got a few questions regarding how I should interpret a few things
in rfc3263, and related text in 3261.

===========
Question 2.
===========
Route preprocessing says, with regard to stripping the route header:
 
   If the first value in the Route header field indicates this proxy,
   the proxy MUST remove that value from the request.
 
All the other text in Ch. 16.4 regards the Request-URI and ;maddr
parameter, so my question is.....Please Define: "indicates this proxy".
 
Do we have the same rules here as when matching the request-uri and
maddr?
In other words, if I receive a request with 
 
  Route: <sip:my-ipaddr:5063;transport=TCP>
  
but I receive it on UDP, should I strip it? What if the port is
different?
I want to do the same checks as for the request-uri, checking port,
transport, etc, but the term "indicates this proxy", is a bit to vague
for my taste, so I wouldnt mind hearing your views.

I'd be very interessted, and thankful for whatever feedback you folks
can provide. 
 
Thanks in advanced
 
Regards
Taisto Qvist
IP-Solutions AB


_______________________________________________
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

Reply via email to