A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Registration, DNS, and routing / Locating a server with RFC 3263

Locating a server with RFC 3263

RFC 3263 turns a SIP domain into a transport, a port, and an address with NAPTR, SRV, and A or AAAA.

Learn in 5 minutes

  1. Order NAPTR, then SRV, then A or AAAA
  2. Name the SIP+D2U, SIP+D2T, and SIPS+D2T services
  3. Skip the name lookup when the Request-URI is already an IP address

Visual

SIP after the lookup · study drawing · cyphermonkeylabs.com UAProxyPeer INVITE 100 INVITE 200

SVG HTML PNG

An explicit transport or port skips the records that are no longer needed. A numeric IP skips the name.

Worked example

What happened before the INVITE The first note states the DNS result. The SIP itself contains no NAPTR records.

  1. Read the first hop note.
  2. Inspect the INVITE Request-URI.
  3. Name the record that would have supplied a port.

Fault

The peer moved in DNS. The SBC still sends to 192.0.2.40 because the dial-peer target is a literal address. Calls time out.

RFC 3263 runs on a domain. An address skips it.

Quiz

RFC 3263 specifies


SIP+D2U selects


SRV is used to learn


A Request-URI that is already an IP address


SIPS+D2T means


Responses find the previous hop by


Ecosystem

Glossary, sister systems, and the integration seam for this room.

Quality management and recording QM scores interactions. The standardized way an SBC forks a session to a recorder is SIPREC.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper