>>>>> Stefan Sayer <[EMAIL PROTECTED]> wrote: >> complete treatment, see >> http://www.ietf.org/internet-drafts/draft-ietf-sipping-sip-offeranswer-02.txt > where you write in 4.2.5. Subsequent Offers and Answers:
> o In the o-line, only the version number may change, and if it > changes it must increment by one from the one previously sent as > an offer or answer. If it doesn't change then the entire SDP body > must be identical to what was previously sent as an offer or > answer. This is the most often misimplemented part. It's usual to see UAs which send e.g. SDP with session ID and version both identical and showed a time from session start, either for the same SDP or changed one; or in another broken mode. In practice, one shall never rely on this (in 4.2.5) rule. -- Valentin Nechayev PortaOne Inc., Software Engineer mailto:[EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
