You are referring to the dialog section of RFC. Remote URI is updated with the To Header information when the dialog is created after receiving any response with a to-tag in it ( Could be 1xx or 2xx). Now the responses are not suppose to change the To header. They are suppose to copy the to header as it is and append a To-Tag ( dialog-identifier ). So w.r.t to our discussion the initial INVITE from and to header URI information will not be changed in subsequent message on that session/call. Remote Target URI is different than Remote URI info and is updated in dialog based on received contact header info, which can be changed subsequently by any target-refresh requests like re-INVITE and I was only pointing to from/to header for subsequent messages not the contact header. But theoretically if some one is using tel URL in from and to header they will use tel URI also in the contact header and R-URI of messages associated with that session ( PRACK/BYE/CANCEL/Re-INVITEs etc ) Regards, Indresh K Singh
________________________________ From: Vikas [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 9:58 AM To: Singh, Indresh (SNL US) Cc: Vikas Gupta; [email protected] Subject: Re: [Sip-implementors] tel uri query Hi Indresh, It should be possible in any method associated with INVITE requested dialog, keeping in perspective that from and to headers can not change during the call. So PRACK/ACK/CANCEL/BYE/SUBSCRIBE/NOTIFY (in-dialog)/REFER have to have the same from/to header as initial INVITE which is allowed to have TEL URL. >>>From rfc 3261 section 12.2.1 its mentioned that To header should be filled with "remote URI" for mid dialog requests.and in its earlier section (12.1.2) it is saying that remote target uri must be set from the CONTACT header(which can never be a tel: uri for INVITE request). So shall we not make a conclusion that these mid dialog request's header field can never have a <tel:> uri in its To header. Regards, Parveen On 27/03/07, Singh, Indresh (SNL US) <[EMAIL PROTECTED]> wrote: My thoughts on this inline.Hopefully it would help a little bit. Regards, Indresh K Singh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikas Gupta Sent: Monday, March 26, 2007 8:47 AM To: [email protected]; [email protected] Subject: [Sip-implementors] tel uri query Hi, I am currently implementing the support of <tel:> URI in our existing user agent as per rfc 3966.I have some doubts regarding the same.Any inputs will be highly appreciated. 1)Is it possible to have tel: URI as request URI in methods other than INVITE and REGISTER i.e in OPTION,PRACK,ACK,CANCEL,BYE, Notify,Subscribe and REFER methods ? >> It should be possible in any method associated with INVITE requested dialog, keeping in perspective that from and to headers can not change during the call. So PRACK/ACK/CANCEL/BYE/SUBSCRIBE/NOTIFY ( in-dialog)/REFER have to have the same from/to header as initial INVITE which is allowed to have TEL URL. 2)From RFC 3396 and 3261 ,I concluded that tel: URI can be present in INVITE and REGISTER request in following headers. For INVITE tel: uri can be present in "request URI" , "From header", "TO header". >From Register tel: URI can be present in "Contact header". for privacy it can also be present in p-preferred and p-asserted header. besides this ,is it possible to have <tel:> uri in any other header(e.gRoute, record-route ,Via )? >> It should also be possible to have TEL URIs in Diversion Header. Regards, Vikas _______________________________________________ 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
