2008/8/16 Bob Penfield <[EMAIL PROTECTED]>: > If any in-dialog request needs to be sent prior to receipt of the final > response, then the Remote Target (from the Contact) and Route Set (from the > Record-Route) must be set up based on the 1xx response. This is needed > especially if reliable provisional responses are being used. The PRACK needs > the remote target and route set. Some User Agents like to send DTMF in INFO > requests, and like to do it before the session is established.
Again good point. >>But is also says that UAS MUST copy RR headers into the response, and >>this only makes sense in a 200 response, so: > > See above. All User Agent implementations should include Record-Route and > Contact in 1xx response just like they would be included in a 2xx response. I > don't see any reason not to, and not including them breaks things. > > Note that the Record-Route headers and Contact header in a 2xx final response > will replace the route set and remote target of the dialog from the 1xx > response. But they usually will be the same. Understood. >> >>* Question: does 12.1.1 speak about a real "dialog" (2XX) or both a >>real dialog and an "early-dialog" (1XX)? >> > > When the term "dialog" is used without the early or confirmed qualifier, it > means either an early dialog or a confirmed dialog. 1xx (except 100) and 2xx > responses establish a "dialog". A 1xx establishes an "early dialog". A 2xx > establishes a "confirmed dialog", or turns an "early dialog" into a > "confirmed dialog" if one already exists. Ok clear now. Thanks a lot to all. -- Iñaki Baz Castillo <[EMAIL PROTECTED]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
