Note that there are some devices increasing the version (o-line) even if the details of the session have not changed.
On Mon, Jun 14, 2010 at 12:49 PM, Iñaki Baz Castillo <[email protected]> wrote: > Thanks for the quotation. It's exactly what I needed :) > > 2010/6/14, Victor Pascual Avila <[email protected]>: >> On Mon, Jun 14, 2010 at 12:13 PM, Iñaki Baz Castillo <[email protected]> wrote: >>> Hi, after reading RFC 3311 (UPDATE method) and RFC 4028 (Session >>> Timers) it's not clear for me if I can use UPDATE requests and >>> responses with no SDP offer/answers after the dialog is established. >> >> From RFC 4028: >> >> It is RECOMMENDED that the UPDATE request not contain an >> offer [4], but a re-INVITE SHOULD contain one, even if the details of >> the session have not changed. In that case, the offer MUST indicate >> that it has not changed. In the case of SDP, this is accomplished by >> including the same value for the origin field as did previous SDP >> messages to its peer. >> -- >> Victor Pascual Ávila >> > > > -- > Iñaki Baz Castillo > <[email protected]> > -- Victor Pascual Ávila _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
