Brett Tate <br...@broadsoft.com> writes: > 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.
At the least, if the scheme is 'sip', the host-part is a DNS host name, and 'transport' is omitted, the transport could be either UDP or TCP. The processes in 3263 and 3261 for determining all of the possible destination address/port/protocol combinations are complicated... Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
