This whole thread sounds confusing.� At a
high level, the way it works is as follows:
- The UAS in the initial
transaction uses Record-Route headers and Contact in the Invite to set the
Route set.
- The UAC in the initial
transaction uses Record-Route headers and Contact in the 200 OK to set the
Route set.
- In subsequent requests within
the dialog, either UA uses it’s route set stored from the initial transaction
to build Route headers.� It does not rebuild the Route set from
Record-Route headers in subsequent requests, though the Contact is updated
if it changes.
- Proxies may Record-Route
subsequent requests.� This is only for robustness in the case a UA crashes
and restarts, and is willing to rebuild the session from the mid-dialog
request, in which case it uses the new Record-Routes. �If a proxy decides
not to include Record-Route in mid-dialog requests, it will not receive
future requests in this case.
John Hearty
Level3
-----Original Message-----
From: Nataraju A.B.
[mailto:[EMAIL PROTECTED]
Sent: Thursday, June
05, 2003 6:27 AM
To: Christer Holmberg (LMF);
'Natesan Kannan'; 'Annamalai Meenatchy'; [EMAIL PROTECTED]
Subject: Re: [Sip-implementors]
Record-Route and re-INVITE
Regards,
-Nataraju A.B.
May you live as long as you wish and love as long as you live.
--Robert A. Heinlein Time Enough for Love. (He may have gotten it elsewhere.)
----- Original Message
-----
Sent: Thursday, June 05, 2003
5:09 PM
Subject: RE: [Sip-implementors]
Record-Route and re-INVITE
A little strange text in
12.2, I think...
What is the use of
including a mid-session Record-Route header if you can't change the route set?
I am not saying one should be able to change the route set, but I wonder what
the Record-Route header shall be used for...
"
The Record-Route process is designed to work for any SIP
request that initiates a
dialog. INVITE is the only such
request in this specification,
but extensions to the protocol
MAY define others.
"
- Only the dialog
creating requests will insert the RR header, while other requests must not add
the RR header..
-----Original Message-----
From: Natesan Kannan [mailto:[EMAIL PROTECTED]
Sent: 5. kes�kuuta 2003 14:39
To: Christer Holmberg (LMF);
'Annamalai Meenatchy'; [EMAIL PROTECTED]
Subject: Re: [Sip-implementors]
Record-Route and re-INVITE
Further to that, the
route-set in the dialog never changes even if there is a record-route header in
the response (UAS just copies this from the request to the response) to a
mid-dialog request.
"Requests within a
dialog MAY contain Record-Route and Contact header
fields. However, these requests do not cause the dialog's
route set
to be modified, although they may modify the remote target
URI."
----- Original Message
-----
Sent: Thursday, June 05, 2003
4:58 PM
Subject: RE: [Sip-implementors]
Record-Route and re-INVITE
There has been
discussions about if it is allowed to change the route set during a session,
but in general the re-INVITE is like any other mid-session request, ie if you
have a route set you include the Route headers...
-----Original Message-----
From: Annamalai Meenatchy [mailto:[EMAIL PROTECTED]]
Sent: 5. kes�kuuta 2003 13:13
To: [EMAIL PROTECTED]
Subject: [Sip-implementors]
Record-Route and re-INVITE
When we send out re-INVITE do we need to include the Route headers
with it? Does the Record-route header in the re-INVITE change/modify the
route-set? When we respond to the re-INVITE, do we need to include the
Record-route header in the 2xx messsage?
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
|
