> 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 or SRV. Other transport values exist; the following shows what is registered with IANA. And similar to tls, some of these are not defined for inclusion within the Contact's URI. http://www.iana.org/assignments/sip-parameters/sip-parameters.xhtml#sip-tr ansport > Are there some RFCs talking about what we need to do if > transport type is missing and SIP transport isn't UDP? If it is missing, you don't know that the transport isn't UDP. It requires going through the RFC 3263 process to determine the transport (unless you have a local policy to behave differently). In addition to RFC 3263, you might find RFC 3261 sections 18 and 19.1.2 to be useful. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
