[EMAIL PROTECTED] wrote:
Hi all,
I have some questions:-
1) Why as per RFC 3262, the Offer-Answer is a MUST in the Provisional
Resp+PRACK phase?
I have yet to find anyone who could explain the WHY to me. However that
is the way it is. People have asked in the past if this could be
changed. The answer is that it perhaps could be changed, but the effort
and impact of doing it would be considerable, and you would still be
stuck supporting the old cases for backward compatibility. There are
ways to adhere to the current requirement, so its hard to justify making
a change.
2) If the 3262 is only for Reliability of Provisional responses, Why should
it mandate Offer-Answer completion?
Again, I am not sure it is possible to answer why. What some people have
proposed for a rationale is that there should be at most one
offer/answer per transaction.
3) As per current recommendations (that are evolved as per discussions in
the sip groups), Why we can not send new Offer in the 200 OK to the INVITE,
after establishing the early media?
There was extensive discussion of this about a year and a half ago.
There were differences in interpretation of this, and finally it was
decided that there can be at most one offer/answer per transaction.
At this point, that is just the way it is.
4) If we can not change the media using 200 OK to INVITE, how this early
Media is useful?
You may establish early media with a 1xx to the invite, and then change
to some other media via an UPDATE sent prior to the 2xx.
5) Are we seriously missing some thing in 3262, that forced us to come up
with 3311 (UPDATE)?
Perhaps. The UPDATE permits changes in media, initiated in *either*
direction, prior to completion of the invite.
Paul
Thanks in advance,
rgds,
Prince
*********************** FSS- Confidential ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."
_______________________________________________
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
