Hi, The ACK of 200OK of INVITE serves multiple purpose. The primary purpose of the ACK is to confirm the reception of the final response of the offer i.e 200 OK. If the UAC did not send any offer in the initial INVITE, the 200 OK should contain the offer and ACK contains the answer of the UAC. The ACK for a 200 OK response to an INVITE request is considered as a separate transaction and it completes the three way handshake procedure to establish a SIP session.
Consider an imaginary situation where Bob and Alice has to agree on one aspect of session (like codec to be used for the session). The whole logic of 3 way handshake can be visualized in this simple example where Bob initiates a SIP session towards Alice. Bob sends 10 aspects/items which can used in initial INVITE . The UAS (Alice) sends back 200 OK specifying that it can support 5 items, but you tell me which one would you like to use for this session. Now the final decision is in hand of Bob (UAC) to accept a particular aspect/item and inform the UAS (Alice) about this. This final decision is conveyed in an ACK of the INVITE request. I hope this a very crude example (ps: this might not be the best way ) will help you understand the logic behind the need of ACK for 200 OK. For more details on ACK, refer rfc 3261. That will clear all your doubts! -sameer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, September 18, 2006 9:37 AM To: [email protected] Subject: [Sip-implementors] ACK is needed ?? Hi, What was the intention behind proposing the need for sending ACK after 200OK of INVITE under SIP. _______________________________________________ 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
