Make sure you don'y just take quotes without looking
at what was written before:

   When in either the "Calling" or "Proceeding" states, reception of a
   response with status code from 300-699 MUST cause the client
   transaction to transition to "Completed".  The client transaction
   MUST pass the received response up to the TU, and the client
   transaction MUST generate an ACK request, even if the transport is
   reliable (guidelines for constructing the ACK from the response are
   given in Section 17.1.1.3) and then pass the ACK to the transport
   layer for transmission.  The ACK MUST be sent to the same address,
   port, and transport to which the original request was sent.  The
   client transaction SHOULD start timer D when it enters the
   "Completed" state, with a value of at least 32 seconds for unreliable
   transports, and a value of zero seconds for reliable transports.
   Timer D reflects the amount of time that the server transaction can
   remain in the "Completed" state when unreliable transports are used.
   This is equal to Timer H in the INVITE server transaction, whose

Rosenberg, et. al.          Standards Track                   [Page 126]


The sentence "The ACK MUST be sent to the same address, port, and
transport to
which the original request was sent" refers to 3xx-6xx responses.



For 2xx responses, the ACK can be sent directly to the Contact
(provided there is no "route set").



                     atlanta.com  . . . biloxi.com
                 .      proxy              proxy     .
               .                                       .
       Alice's  . . . . . . . . . . . . . . . . . . . .  Bob's
      softphone                                        SIP Phone
         |                |                |                |
         |    INVITE F1   |                |                |
         |--------------->|    INVITE F2   |                |
         |  100 Trying F3 |--------------->|    INVITE F4   |
         |<---------------|  100 Trying F5 |--------------->|
         |                |<-------------- | 180 Ringing F6 |
         |                | 180 Ringing F7 |<---------------|
         | 180 Ringing F8 |<---------------|     200 OK F9  |
         |<---------------|    200 OK F10  |<---------------|
         |    200 OK F11  |<---------------|                |
         |<---------------|                |                |
         |                       ACK F12                    |
         |------------------------------------------------->|
         |                   Media Session                  |
         |<================================================>|
         |                       BYE F13                    |
         |<-------------------------------------------------|
         |                     200 OK F14                   |
         |------------------------------------------------->|
         |                                                  |

         Figure 1: SIP session setup example with SIP trapezoid


Regards,

Attila
 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Vivek Gupta
Sent: 05 June 2008 11:11
To: [email protected]
Subject: [Sip-implementors] FW: Change of transport type in 2XX response



-----Original Message-----
From: Vivek Gupta
Sent: Thursday, June 05, 2008 3:32 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Sip-implementors] Change of transport type in 2XX response

Following is the text from RFC 3261 [page 126]:

The ACK MUST be sent to the same address, port, and transport to which
the original request was sent. 

-----Original Message-----
From: srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 1:57 PM
To: Vivek Gupta
Subject: RE: [Sip-implementors] Change of transport type in 2XX response

UAC has to send the ACK to contact address which it has received in 200
OK response for the Invite request.

Thanks & Regards,
Srinivas CH,
Huawei Technologis India Pvt Ltd,
7th Floor Leela Palace,
Airport Road, Bangalore-8, 
Contact: (Off) 080-41117676 ext: 7023                (Mob)
+919731316362.
 
This e-mail and attachments contain confidential information from
HUAWEI, which is intended only for the person or entity whose address is
listed above. Any use of the information contained herein in any way
(including, but not limited to, total or partial disclosure,
reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the
sender by phone or email immediately and delete it!
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Vivek Gupta
Sent: Thursday, June 05, 2008 12:29 PM
To: [email protected]
Subject: [Sip-implementors] Change of transport type in 2XX response

Hi,

 

Say, the UAS changes its contact details in the contact header of 200 OK
response to an initial INVITE. Shall UAC send out the ACK to the
original contact to which the initial INVITE was sent or to the updated
contact address?

 

With regards,

Vivek Gupta

_______________________________________________
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

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to