If SIP transport isn't UDP, transport=tcp or tls must be presented in the contact header. Although, RFC 5630 says transport = tls deprecated, many implantations still use it. Are there some RFCs talking about what we need to do if transport type is missing and SIP transport isn't UDP?
Thanks, Jing Jiang , PhD * Embedded Software Engineer Biamp Systems * 9300 SW Gemini Drive, Beaverton, OR 97008 www.biamp.com<http://www.biamp.com/> * tel. +1.503.641.7287 * direct +1.503.718.9238 * fax +1.503.626.0281 ----------------------------------------------------------------------------------- BIAMP SYSTEMS EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ----------------------------------------------------------------------------------- _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
