[Sip-implementors] PRACK and RFC Compliant to RFC 2543

2017-01-04 Thread Vimal Tewari
RFC 3262 says (in the Introduction part): PRACK is a normal SIP message, like BYE. As such, its own reliability is ensured hop-by-hop through each stateful proxy. Also like BYE, but unlike ACK, PRACK has its own response. *If this were not the case, the PRACK message could not trave

[Sip-implementors] PRACK and Proxy Servers Compliant to RFC 2543

2017-01-04 Thread Vimal Tewari
RFC 3262 says (in the Introduction part): PRACK is a normal SIP message, like BYE. As such, its own reliability is ensured hop-by-hop through each stateful proxy. Also like BYE, but unlike ACK, PRACK has its own response. *If this were not the case, the PRACK message could not trave

Re: [Sip-implementors] PRACK and Proxy Servers Compliant to RFC 2543

2017-01-04 Thread Brett Tate
Hi, RFC 3261 and RFC 3262 attempted to be backward compatible with RFC 2543 devices. This includes ACK being the only request that does not generate responses and the potential for an intermediary to return 407 (or other responses) for an unknown request. There is an open issue about if "PRACK i

Re: [Sip-implementors] SIP Domain with single part

2017-01-04 Thread Dale R. Worley
wor...@ariadne.com (Dale R. Worley) writes: > However, there has > been at least one exception: Fredrik Thulin once managed the nameserver > for .SE and added an MX record for .SE, directed to the host that > handled his e-mail. Thus, was a valid e-mail address for > him. Thinking more about th

Re: [Sip-implementors] PRACK and RFC Compliant to RFC 2543

2017-01-04 Thread Paul Kyzivat
On 1/4/17 7:42 AM, Vimal Tewari wrote: RFC 3262 says (in the Introduction part): PRACK is a normal SIP message, like BYE. As such, its own reliability is ensured hop-by-hop through each stateful proxy. Also like BYE, but unlike ACK, PRACK has its own response. *If this were not th

[Sip-implementors] SIP Request URI Domain processing without Port

2017-01-04 Thread Varadhan Work
Hello Everyone, I'm trying to figure out proper method for implementing sip-domain routing policy, while using port number different than default 5060. Suppose, SIP Domain name: *mydomain.org * SIP Port: *8060* SIP Client configured with domain name with port number *mydomai

Re: [Sip-implementors] SIP Request URI Domain processing without Port

2017-01-04 Thread Mohit Soni
Hi Vardhan, Quoting from RFC3261 section 10.3; "The registrar inspects the Request-URI to determine whether it has access to bindings for the domain identified in the Request-URI. If not, and if the server also acts as a proxy server, the server SHOULD forward the request to the addressed domain,