query
Click on the red underlined text to get to the source
... amount of time in order to reduce call setup delays of subsequent
calls. The client cannot query a failed server continuously to
determine when it becomes available again, since this does not scale.
Furthermore, the availability state ...
... sip:user@example.com. The client performs a NAPTR query for that
domain, and the following NAPTR records ...
... NAPTR replacement
field to match the domain of the original query (i.e., example.com
above). However, for backwards compatibility with RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop) ...
... MUST maintain SRV records for the domain of the original query, even
if the NAPTR record is in a different domain ...
... a site certificate), the domain name in the query and the domain name
in the replacement field MUST both be valid ...
... NAPTR records are found, the client constructs SRV queries for
those transport protocols it supports, and does a query ...
... queries for
those transport protocols it supports, and does a query for each.
Queries are done using the service ...
... transport protocols it supports, and does a query for each.
Queries are done using the service identifier "_sip" for SIP ...
... URIs. A particular transport is supported if the
query is successful. The client MAY use any transport protocol it
...
... URI, the client performs an SRV query on the record returned
from the NAPTR processing of Section 4.1, if such processing was
...
... 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 are selected. Irregardless
...
... stateless proxy receives the request, it performs the appropriate
DNS queries as described above. However, the procedures of RFC 2782prop
are not guaranteed to be deterministic. This is because records that
...
... If, however, the sent-by field contained a domain name and a port
number, the server queries for A or AAAA records with that name. It
tries to send the response to each element ...
... implies that the transport protocol in the SRV query is TCP). The
resulting list is sorted as described in [2 ...
... NAPTR records contain SIPS in the services field. If such
records were present, but in later queries cease to appear, it is a
sign of a potential attack. In this case, the client ...
... clients that
perform the NAPTR queries. It is therefore possible for a proxy to
ignore SIPS entries even though they are present, resulting in
...