SIP URI
Click on the red underlined text to get to the source
... 1], the request can be sent to a
specific intermediate proxy not identified by a SIP URI, but rather,
by a hostname or numeric IP address. In that case, a temporary URI ...
... 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) [6], and thus
the only one guaranteed to be interoperable for a SIP URI. It was
also specified as the default transport in RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) ...
... 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) when no transport
was present in the SIP URI. However, another transport, such as TCP,
...
... service field. The
converse is not true, however. A client resolving a SIP URI SHOULD
retain records with "SIPS" as the protocol, if the client supports
...
... identifier "_sips" for SIPS URIs. For a
SIP URI, if the client wishes to use TLS, it also uses the service ...
...
In many cases, an element needs to construct a SIP URI for inclusion
in a Contact header in a REGISTER ...
... is truly needed, but we allow TLS to be used for requests resolved by
a SIP URI to allow security that is better than no TLS at all.
...