Hi Ivar, I would recommend referring to section-12 ( dialog ) section 13 (session ) and section 17 ( transaction ) collectively of RFC-3261 for case described below.
Yes the UAS created dialog should wait for the ACK, otherwise TU ( Transaction User ) running a 2xx timer waiting for ACK should timeout and release the call by sending a BYE or fall-back to previous successfully negotiated media ( if it was for re-INVITE-200OK ). For 2XX case please note that the transaction becomes free, so it is the TU which is running the retransmission and timeout timers. Regards, Indresh K Singh ------------------------------------------------------------- Sr. Software Engineer SIP Media Control and Signaling Nokia Siemens Networks Boca Raton, FL-33487 Ph: 561-923-5085 (o), 561-923-2048 (o) ------------------------------------------------------------- >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On Behalf >>Of ext Ivar >>Sent: Tuesday, May 15, 2007 11:02 AM >>To: [email protected] >>Subject: [Sip-implementors] ACK and UAS dialog >> >>Hi, >> >>After reading RFC 3261, i don't find place what describes following: >> >>UAC send INVITE, UAS gives 200 ok answer. >> >>Now UAC send ACK (thats nicely in rfc 13.2.2.4), where ACK is >>handled in >>UAS ? >>Does UAS created dialog must wait for ACK confirmation, if it doesn't >>get it, dialog will be terminated and BYE is sent to UAC ? >> >> >>_______________________________________________ >>Sip-implementors mailing list >>[email protected] >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
