Hi All, As the Request URI parameters are used to define a way to process the Request URI so if a sip proxy receives a request containing the request URI parameters that it don't understand then it should copy these params as it is in the Request URI while forming Request URI for the target in case of Request Forwarding. This will ensure that the proxy is not breaking any end to end functionality because it can be a case where your upstream element required those params for the Request URI processing. So it's better to be on safe side :).
Thanks and Regards, Rajat Chandna Software Engg. A R I C E N T The Presidency Tower - A 351/2, Sector-14, M.G.Road, Gurgaon -122001. Haryana (India) Ext: 5105 Mobile: 9891446659 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anuradha Gupta Sent: Thursday, August 21, 2008 12:11 PM To: Rockson Li (zhengyli); [email protected] Subject: Re: [Sip-implementors] which parameter is not allowed in Req-URI Hi There are parameters which are SIP Header specific. For example: to-param = tag-param / generic-param from-param = tag-param / generic-param info-param = ( "purpose" EQUAL ( "icon" / "info" / "card" / token ) ) / generic-param auth-param = auth-param-name EQUAL ( token / quoted-string Such parameters are not allowed in Request URI. Therefore if included in the Request URI of a message as unknown parameters then these should be ignores while the copying the Request URI of the target in case of Request Forwarding. Regards Anuradha Gupta Technical Leader A R I C E N T The Presidency Tower - A 351/2, Sector-14, M.G.Road, Gurgaon -122001. Haryana (India) Ext : 5119 Mobile : 9811814731 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rockson Li (zhengyli) Sent: Thursday, August 21, 2008 11:40 AM To: [email protected] Subject: [Sip-implementors] which parameter is not allowed in Req-URI Hi folks, RFC3261 16.6 Request Forwarding 2. Request-URI The Request-URI in the copy's start line MUST be replaced with the URI for this target. If the URI contains any parameters not allowed in a Request-URI, they MUST be removed. But I don't see which parameter(s) is/are not allowed in Req-URI, Since as per BNF below, it looks like all SIP-URI / SIPS-URI / absoluteURI is ok for Req-URI SIP-URI = "sip:" [ userinfo ] hostport uri-parameters [ headers ] uri-parameters = *( ";" uri-parameter) uri-parameter = transport-param / user-param / method-param / ttl-param / maddr-param / lr-param / other-param Request-URI = SIP-URI / SIPS-URI / absoluteURI Could anybody clarify please? Thanks -Rockson _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
