Please note that draft-rosenberg-sip-route-construct-01 is a proposal
that is far from complete, and it proposes *changes* to existing
specifications. So it is dangerous to use it today as guidance on how to
work with the existing specifications. It may contradict behavior that
is required to work in some current environments. It, or something like
it, is likely to be enacted at some point, but its hard to predict when.
Paul
[EMAIL PROTECTED] wrote:
> If you are looking for how to use Service-Route and Record-Route in
> construction of route set, look at
> "draft-rosenberg-sip-route-construct-01.txt". Specifically section "5.3 UAC
> Behavior" in construtcing route set for mid dialog and outside dialog
> requests.
>
> -Ramakrishna
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kedar Karmarkar
> Sent: Thursday, May 04, 2006 10:53 PM
> To: rahul; Sip_Impl
> Subject: Re: [Sip-implementors] query regarding BYE request URI
>
> A related question, is there any interaction between "path" and
> "record-route"? Or is path is to be used only for initial request and
> record-route is also added by intermediate proxies?
>
> Kedar
>
>
> On 5/4/06, rahul <[EMAIL PROTECTED]> wrote:
>
>>Hi,
>>If Only Contact header is present : To release it sends a BYE request
>>with the Request-URI set to the Contact URI included in the request
>>and with no Route header set.
>>
>>If Contact and Route header is present: sends a BYE request with the
>>Request-URI set to the Contact URI and a Route header set to the list
>>in a reverse order of the Record-Route included in the request.
>>
>>Regards,
>>Ravi
>>
>>
>>Nataraju A B <[EMAIL PROTECTED]> wrote:
>>Comments inline...
>>
>>Thanks & Regards,
>>Nataraju A.B.
>>-----Original Message-----
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED] On Behalf Of sudhir
>>kumar
>>Sent: Wednesday, May 03, 2006 6:28 PM
>>To: Sip_Impl
>>Subject: [Sip-implementors] query regarding BYE request URI
>>
>>Hi All,
>>
>>If UA received INVITE request with contact and record-route header,
>>when UA want to built the BYE request.
>>
>>How BYE request-URI is built? Should I use record-route or contact
>>header to construct BYE request-URI?
>>
>>[ABN] when the UAC generates the Request for the first time, the R-URI
>>would be that of the Contact header in 200OK, then that request-URI
>>would be modified based on the Route header (which is formed out of RR
>>header) being exchanged after the INVITE transaction
>>
>>[ABN] Basic functionality is to form the R-URI from contact header and
>>then might be overwritten by diff values based on the routing
>>decisions based on ROUTE header information...
>>
>>Any response is appreciated
>>
>>Thanks in advance
>>Sudhir
>>
>>
>>
>>
>>
>>__________________________________________________________
>>Yahoo! India Answers: Share what you know. Learn something new.
>>http://in.answers.yahoo.com
>>_______________________________________________
>>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
>>
>>
>>
>>---------------------------------
>>Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
>>countries) for 2ยข/min or less.
>>_______________________________________________
>>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
>
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should
> check this email and any attachments for the presence of viruses. The company
> accepts no liability for any damage caused by any virus transmitted by this
> email.
>
> www.wipro.com
>
> _______________________________________________
> 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
