Hi,
Section 14.1 of 3261 states
2. If there is an ongoing INVITE server transaction, the TU MUST
wait until the transaction reaches the confirmed or terminated
state before initiating the new INVITE.
Refer the state m/c of INVITE server transaction state m/c under 17.2.1.
It needs to wait for ACK OR Timer H to go to Confirmed or terminated
state.
Thx
Samir
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rohit
Sonalkar
Sent: Wednesday, December 22, 2004 12:02 PM
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
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
