Hi Stephan, I agree that if the server is fully RFC 3261 compliant it has to set both port parameter and transport paramter In URI. Additionally, I think you are right such behaviour has sprung because of difference between RFCs 2543 and 3216.
In my opinion a pragmatic approach is to consider sip:[EMAIL PROTECTED]:5060 not equivalent to sip:[EMAIL PROTECTED] because it can resolve to different port as a result of SRV query; however, if the host portion is an address which is already resolved these are equivalent. The same can be said about the transport parameter. regards Rayees -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephan Steiner Sent: Friday, May 18, 2007 5:41 PM To: [email protected] Subject: Re: [Sip-implementors] Contact matching in registration Hi Rayees Couldn't the fact that many UAs still recognize the Contact stem from the fact that sip:[EMAIL PROTECTED] was considered to be equal to sip:[EMAIL PROTECTED]:5060 in RFC2543 and the difference was only introduced in RFC 3261? And there's a bit I missed in my last message: 19.1.4 also requires matching transport, ttl and user parameters and in my case the UA gave a transport parameter, but the Contact in the response did not include the transport. Shouldn't the reply contain the following Contact header for full RFC 3261 compliance: Contact: <sip:[EMAIL PROTECTED];transport=UDP>;expires=360 (I added the brackets because the transport requires a semicolon in the URI and then according to 20.10 you have to use the brackets even if no display name is present) Regards Stephan ----- Original Message ----- From: "Rayees Khan" <[EMAIL PROTECTED]> To: "Stephan Steiner" <[EMAIL PROTECTED]>; <[email protected]> Sent: Friday, May 18, 2007 6:26 PM Subject: RE: [Sip-implementors] Contact matching in registration Hi Stephan, It appears that both the messages are valid syntatically. Since absense of port in a sip-URI is assmed to mean 5060 and absence of transport parameter is assumed to be UDP, the AOR in REGISTER and 200 OK do match. In my opinion, UA should have found the matching AOR in contact header valid for 360 seconds. To be frank I have experience this matching of AOR with and with :5060 a number of times. regards Rayees _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ---------------------------------------------------------------------------------- IMPORTANT The information contained in this e-mail any attachments is intended only for the named recipient and may be privileged or confidential. If you are not the intended recipient, please notify us immediately on +44 (0)1908 425000 and do not disclose, copy, distribute or take any action based on the contents of this e-mail. You should understand and accept that, when communicating with us by e-mail, it is not a totally secure communication medium. We accept no liability for any direct, indirect or consequential loss arising from any action taken in reliance on the information contained in this e-mail and give no warranty or representation as to its accuracy or reliability. DIGITALK has the facility to monitor and read both incoming and outgoing communications by e-mail. In line with industry efforts to reduce the proliferation of Un-Solicited SPAM messages, DIGITALK uses various methods including Reverse-DNS lookups and ban-lists to prevent malicious content reaching our users. This message and any attachments has been scanned for known viruses. However, we would advise you to ensure the content is indeed virus free. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or breach of confidentiality in relation to transmissions sent by e-mail. VAT No: GB 876 3287 81. Reg No: 3080801 Place of Registration: England Registered Office Address: 2 Radian Court, Knowlhill, Milton Keynes ----------------------------------------------------------------------------------" _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
