Comments inline.
Paul
[EMAIL PROTECTED] wrote:
Hi Paul,
Hi haven't got the reply on this chain of discussion. I am little unclear about the concept here. Please follow the chain and tell me if there is anything missing in my understanding or in the spec.
Thanks, Vivek
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 23, 2004 10:42 AM To: [EMAIL PROTECTED]; [email protected] Subject: RE: [Sip-implementors] Query about INVITE transaction and UASbehaviour
Hi,
On receiving 200 OK from TU, INVITE server transaction passes it to transport layer for transmission and transition to 'Terminated' state. Client transaction also transition to 'Terminated' state on receiving this 200 ok. So there is no client server transaction on both sides. As per my understanding, Re-invite can be sent now and UAS should not wait for ACK.
I have not studied the transaction state machines in detail so I will defer to Vivek. The above certainly sounds plausible to me.
But I m not clear about the case when offer is sent in 200 ok and answer is expected in ACK. In this case UAS should not send Re-invite to change the media session because old media session is yet not confirmed.
The offer/answer protocol restrictions must be followed across reinvites. So in this case, before receiving the ACK, the UAS could not send a reinvite with a session description. However, assuming the above case is ok, then it might be ok to send a reinvite *without* a session description.
This is however probably a very risky proposition.
Paul
ACK for a 2xx response to an invite is a separate transaction.
Vivek
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rohit Sonalkar Sent: Thursday, December 23, 2004 1:32 AM To: [email protected] Subject: [Sip-implementors] Query about INVITE transaction and UAS behaviour
Hi,
If a UAS gets an INVITE and responds with 200, is it allowed for it to follow up with a reINVITE of it's own without waiting for an ACK? The RFC states that a UAC must not initiate a new INVITE transaction until the previous one has completed. Does this not apply to the UAS in this case too, i.e. should not the UAS wait for ACK from the UAC before sending a reINVITE of it's own?
Thanks.
Rohit
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Confidentiality Notice
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Confidentiality Notice
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
