If you read further down, the reason is given. The
was received using the port and transport indicated (explicitly or by
default) in the Request-URI, the proxy MUST strip the maddr and any
non-default port or transport parameter and continue processing as if
those values had not been present in the request.
Rosenberg, et. al. Standards Track [Page 96]
RFC 3261 SIP: Session Initiation Protocol June 2002
A request may arrive with a maddr matching the proxy, but on a
port or transport different from that indicated in the URI. Such
a request needs to be forwarded to the proxy using the indicated
port and transport.
Also refer to the Section 18.1.1 Sending Requests and see how multicast is
handled.
Thanks,
Neel
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of karthik
Sent: Monday, August 28, 2006 12:49 AM
To: sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] Reg Removal of Nondefault Port and Transport by
proxy
hi all,
As per RFC 3261 it is given in section 16.4 that the Proxy has to remove
the Default port and transport in the Request URI when it gets an INVITE
with those parameters.
Kindly tell me what is the significance of removing those parameters
before forwarding it to next level?
Thanks in advance,
Geetha.
--
karthik
[EMAIL PROTECTED]
--
http://www.fastmail.fm - Same, same, but different.
_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
