SRV
Click on the red underlined text to get to the source
... These NAPTR records provide a mapping from a domain to the SRV record
for contacting a server with the specific transport protocol in the
...
... resource record will contain an empty
regular expression and a replacement value, which is the SRV record
for that particular transport protocol. If the server supports
...
... transport protocol of the server that is supported
by the client, as well as an SRV record for the server. It will also
allow the client to discover if TLS ...
... TCP will be used, targeted to a host determined by an SRV lookup of
_sip._tcp.example.com. That lookup ...
... 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop), a domain
MUST maintain SRV records for the domain of the original query, even
...
... NAPTR record is in a different domain. As an example, even
though the SRV record for TCP is _sip._tcp.school.edu, there MUST
also be an SRV record ...
... SRV record for TCP is _sip._tcp.school.edu, there MUST
also be an SRV record at _sip._tcp.example.com.
RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) ...
...
RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) will look up the SRV records for the domain directly. If
these do not exist because the NAPTR ...
... domain name in the target in
the SRV record MUST both be valid based on the same site certificate.
...
... If no NAPTR records are found, the client constructs SRV queries for
those transport protocols ...
... most preferred record.
If no SRV records are found, the client SHOULD use TCP for a SIPS
URI ...
... 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop). Previously, if the port was
explicit, but with a value of 5060, SRV records were used. Now, A
or AAAA records will be used.
...
... transport was specified
explicitly, the client performs an SRV query for that specific
transport ...
... "_sip". If the NAPTR processing was not done because no NAPTR
records were found, but an SRV query for a supported transport
protocol was successful, those SRV records ...
... SRV query for a supported transport
protocol was successful, those SRV records are selected. Irregardless
of how the SRV records were determined, the procedures of RFC 2782prop ...
... transport
protocol was successful, those SRV records are selected. Irregardless
of how the SRV records were determined, the procedures of RFC 2782prop,
as described in the section titled "Usage rules ...
...
RFC 2782prop spells out the details of how a set of SRV records are
sorted and then tried. However, it only states that the client
...
... RECOMMENDED that domain administrators make the weights of SRV
records with equal priority different (for example, using weights of
1000 and 1001 if two servers are equivalent, rather than assigning
...
... response through a backup.
SRV provides a way to fix this. Instead of using an IP address, a
domain name ...
... provider.com
The SRV records for a particular target can be set up so that there
is a single record with a low value for the priority ...
... map an incoming SIP or SIPS URI to a set of SRV records for the
various servers that can handle the URI.
...
... 8].
Expected Output: The result of the application is an SRV record
for the server to contact.
...