Hi Bob,
       I think that holds true for stateless proxy. If a stateful proxy has 
forwarded final response to UAC then no need to send further responses back to 
UAC.

Thanks and Regards,
Vivek Talwar
________________________________________
From: [email protected] 
[[email protected]] On Behalf Of Bob Penfield 
[[email protected]]
Sent: Tuesday, May 10, 2011 6:14 PM
To: Iñaki Baz Castillo; Brez Borland
Cc: [email protected]
Subject: Re: [Sip-implementors] Proxy receives 200 for INVITE while in 
"completed" state

In RFC 3261, section 16.7 (Response Processing for proxies) on page 110, it 
says:

         After a final response has been sent on the server transaction,
         the following responses MUST be forwarded immediately:

         -  Any 2xx response to an INVITE request

Thus the proxy must forward the 2xx when the client transaction is in the 
"completed" state.

If the client transaction has already been deleted, then this text (on page 
107) applies:

   When a response is received by an element, it first tries to locate a
   client transaction (Section 17.1.3) matching the response.  If none
   is found, the element MUST process the response (even if it is an
   informational response) as a stateless proxy (described below).  If a
   match is found, the response is handed to the client transaction.

      Forwarding responses for which a client transaction (or more
      generally any knowledge of having sent an associated request) is
      not found improves robustness.  In particular, it ensures that
      "late" 2xx responses to INVITE requests are forwarded properly.

Therefore, the proxy always forward all 2xx responses to INVITE.

Hope that helps.

cheers,
(-:bob



-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Iñaki Baz 
Castillo
Sent: Tuesday, May 10, 2011 8:35 AM
To: Brez Borland
Cc: [email protected]
Subject: Re: [Sip-implementors] Proxy receives 200 for INVITE while in 
"completed" state

2011/5/10 Brez Borland <[email protected]>:
> Hi Inaki, I think what you are looking for is Timer D. Have a look in the
> rfc3261, the last paragraph on the page 126, and the page 127.

Hi Brez, timer D is waiting time for response retransmissions. My
question is: what happen if a response is a retransmission (according
to its Via branch parameter) but is a 200 rather than the previous
4XX?

But don't worry, I had the doubt initially due to a bad day, I'm
pretty sure that such response (even with diferent status code) must
be ignored/absorbed by the client transaction during timer D.

Thanks a lot.

--
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
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

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."

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

Reply via email to