"When issuing an offer that modifies the session, the "o=" line of the new
SDP MUST be identical to that in the previous SDP,
except that the version in the origin field MUST increment by one from the
previous SDP. If the version in the
origin line does not increment, the SDP MUST be identical to the SDP with
that version number."
- study along with the next statement. If there is a change in the session
then the offerer increments the version # in the o line to denote the
session change. But the other fields in the o line remain the same, because
it is from the same offerer.
"The answer to an offered session description is based on the offered
session description. If the answer is
different from the offer in any way (different IP addresses, ports, etc.),
the origin line MUST be different in
the answer, since the answer is generated by a different entity. In that
case, the version number in the "o="
line of the answer is unrelated to the version number in the o line of the
offer."
- Answer is generated by a different entity, so the o line is bound to be
different.
Have a look @ draft-johnston-mmusic-offer-answer-examples for examples and
flows.
-Elias
Hughes Software Syatems
http://www.hssworld.com
Krishna Kanth T
<[EMAIL PROTECTED]
.com> To
Sent by: [EMAIL PROTECTED]
sip-implementors- cc
[EMAIL PROTECTED]
ia.edu Subject
[Sip-implementors] A doubt in
offer/answer model
03/05/04 10:46 AM
Hi all,
I have one doubt in rfc 3264. Section 8 of rfc3264 says that
"When issuing an offer that modifies the session,the "o=" line of the new
SDP MUST be identical to that in the previous SDP"
1. Is there any specific reason to enforce this condition?
2. Why isn't the same restriction enforced while giving an answer SDP.
It will be greatful if you can clarify the above doubt that is pestering me
from past few days.
Rgds
Krishna_______________________________________________
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
