Hi all,
Wanted a couple of clarifications regarding the handling
of the SDP origin line vis-a-vis offer/answer. Tried going
through the offer/answer and the call-flows draft, but
could not solve all of them.
1. In case the UAC sends SDP in INVITE with the session-id
in the "o=" line as (say) 2845844566, is it a MUST for
the UAS to return the same session-id in the answer?
The offer/answer-02 draft allows the UAS to have an
independant version number, but is silent about the
session-id field. Can the UAS use a different session-id
and use the same session-id henceforth? The call-flows
draft (draft-ietf-sipping-basic-call-flows-00.txt) does
seem to indicate this.
2. Same offer, but a different answer
----------------------------------
Should the 'version' field of the "o=" line in the answer
be incremented even if the offer was unchanged and the
answer is different from the original answer in
(a) only the ports?
(b) only a change in IP address?
(c) change (addition/subtraction) in accepted codecs?
3. Different offer, but same answer
--------------------------------
If the offer is different from the previous offer by
the UAC (he's trying to add some codecs, say); but the
answer that the UAS generates is the same as the previous
answer (all additions that were attempted are rejected),
then should the UAS increment its version in the o= line?
If it does, is it an error?
I feel it would be good if the offer/answer draft was
made more explicit regarding the handling of the o= line.
Thanks in advance.
Siddharth.
-----------------
Siddharth Toshniwal @ Hughes Software Systems
http://www.hssworld.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
