Manju is correct that transport parameter should not be present in the from and to header as per table-1 of RFC-3261.
Page 151 also suggest that Elements processing URI should ignore any disallowed components if they are present. But I am not sure if the transport parameter in the from header ( which is not allowed ) should be ignored while populating the local target uri information in dialog. Paul could you kindly comment on this ?? Regards, Indresh K Singh >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On >>Behalf Of ext Manjunath Warad >>Sent: Wednesday, August 01, 2007 1:39 AM >>To: 'Biju Kayakal'; sip-implementors@lists.cs.columbia.edu >>Subject: Re: [Sip-implementors] URI parameter in To and From headers >> >>Hi Biju, >> RFC recommends not to add transport param in From and To header. >>However, if the end-point receives transport param then that >>param should be >>ignored. >> >> However about creation of responses, if the request is dialog >>creating then >>1. From header is clone as in request, drop all the >>unnecessary info like >>transport param if any in request. >>2. To header too is clone as in request, dropping all >>unnecessary info like >>trans param and this end-point has to generate To tag. >> >>Further mid-dialog request MUST carry the same From and To >>header in reverse >>order with tags intact if generated from callee point. >> >>If the request is not dialog creating one then To tag MUST >>NOT be generated. >> >>For the information about the parameters in the URI you can >>look into Table >>1 from RFC 3261. >> >>Regards, >>Manju >> >> >>************************************************************** >>************** >>*********** >>This e-mail and attachments contain confidential information >>from HUAWEI, >>which is intended only for the person or entity whose address >>is listed >>above. Any use of the information contained herein in any way >>(including, >>but not limited to, total or partial disclosure, reproduction, or >>dissemination) by persons other than the intended recipient's) is >>prohibited. If you receive this e-mail in error, please >>notify the sender by >>phone or email immediately and delete it! >> >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On >>Behalf Of Biju >>Kayakal >>Sent: Wednesday, August 01, 2007 3:39 AM >>To: sip-implementors@lists.cs.columbia.edu >>Subject: [Sip-implementors] URI parameter in To and From headers >> >>Hi All, >> A SIP endpoint receives a request containing the >>transport param >>as URI parameter in the To header ? >>E.g. >>To: <sip:[EMAIL PROTECTED];transport=tcp> >> >>Should it copy this URI parameter in the To header when it forms the >>response ? >>Also should it also copy this URI param into the From header >>when it has to >>send subsequent requests within this dialog ? >> >>RFC 3261 stats that when forming responses, "If the To header >>field in the >>request did not contain a tag, the URI in the To header field in the >>response MUST equal the URI in the To header field" >> >>And for subsequent transactions: >>"The From URI of the request MUST be set to the local URI >>from the dialog >>state" >> >>How should the URI parameters be handled in this regard ? >> >>Any inputs would be appreciated. >> >>Thanks >>-Biju >>_______________________________________________ >>Sip-implementors mailing list >>Sip-implementors@lists.cs.columbia.edu >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> >> >>_______________________________________________ >>Sip-implementors mailing list >>Sip-implementors@lists.cs.columbia.edu >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
