Moving to sip-implementors....

Hi Prashant,

You should not be using headers such as Route to decide
whether to drop or forward the ACK. In your (stateless)
proxy, three cases would arise:

- ACK is for a non-2xx that was not generated by
  your element.
- ACK is for a 2xx generated by an endpoint
- ACK is for a non-2xx generated by your element
  (Eg, for a 483)

You would only need to drop the ACK received in case 3
above. In this case, since you have generated the non-2xx,
you could generate the To tag for the response in a fashion
that allows you to recognize it in subsequent messages.
To-tag algorithm is implementation specific and can be
used for this purpose.

Subhash Nayak
Hughes Software Systems
http://www.hssworld.com






"Prashant" <[EMAIL PROTECTED]> on 10/31/2002 03:27:47 AM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:    (bcc: Subhash Ullal Nayak/HSSBLR)

Subject:  [Sipping] ACK without Route




Hi all,
 The ACK message with no Route header is generally treated as a response to
non-200 message.

  However in case, when  our proxy is routing the calls between two SIP
proxies and one of the SIP proxy does not support route header. The ACK
message  comes with no Route header and it gets drop. Our proxy is mostly
stateless.

Is there any other option than Route header to check the treatment of ACK
message i.e to proxy it or to drop it. or is it a confirmation of  200
response or a non-200 response.


thanks
Prashant


__________________________________________________________
Outgrown your current e-mail service? Get 25MB Storage, POP3 Access,
Advanced Spam protection with LYCOS MAIL PLUS.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments of core SIP






_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to