Re: [Sip-implementors] transport=udp|tcp|tls in contact header

2016-04-27 Thread Brett Tate
> 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. A transport parameter is not required unless unable to determine it through other means such as the use of DNS NAPTR

[Sip-implementors] transport=udp|tcp|tls in contact header

2016-04-27 Thread Jing Jiang
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, J