VoIP.infoThe independent guide to business communications.
VoIP.info Reference

SIP URI structure: identity, routing and parameters

Parse sip and sips addresses without assuming they behave like ordinary telephone numbers.

Reviewed 2026-10-14SIP standards; extension support depends on both peersIntermediateDocumentation based · not lab tested

Read the address in parts

A SIP URI identifies a resource using a scheme, an optional user component, a host and optional port and parameters. In sip:alice@example.net, alice is the user and example.net identifies the domain responsible for routing. That domain does not have to be the same as the endpoint's current IP address. A numeric user component does not automatically make an address a public telephone number. Dialplan normalization, domain ownership and trunk policy determine how it is handled. A tel URI has a different syntax and may need translation before a SIP request is routed.

Scheme and transport are not synonyms

The sips scheme expresses secure routing requirements in SIP; it is not a promise that the media is end-to-end encrypted. Transport parameters, DNS selection, certificate identity and the destination's supported transports still matter. Keep signaling protection separate from SRTP media protection. URI parameters are part of the routing information. Do not discard them indiscriminately when copying a Request-URI into a test. Characters requiring escaping and user-versus-host parsing can also change the meaning of an address.

Practical troubleshooting

Compare the dialed string, the Request-URI sent to the PBX and the Request-URI sent to the provider. Record exactly where prefixes, country codes or domains change. An authentication username can differ from the user in the called URI, so substituting one for the other may create a different failure. Use examples with reserved documentation domains when sharing traces. Redact personal numbers consistently while preserving the structure and relevant parameters. For a routing problem, explain what the recipient is expected to own: a local extension, a federated domain or a carrier destination.

Map SIP URI grammar to Asterisk parser selectors

The Asterisk PJSIP_PARSE_URI guide maps display, scheme, user, password, host, port and documented URI parameters without treating a parsed value as identity or route proof.

Keep URI parameters inside the address and header parameters outside

The Asterisk From-parameter guide turns that syntax boundary into a channel-scoped read, write and packet-verification workflow.

Distinguish dialog, request and target URIs in Asterisk

The PJSIP channel-context guide keeps local and remote dialog identity, original inbound Request-URI and current send target as different objects before parsing.

Apply URI roles to SIP MESSAGE explicitly

The Asterisk MessageSend guide shows why the Request-URI chosen by the destination and the logical To and From URIs must be recorded independently.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Reference · SIP standards; extension support depends on both peers

SIP DNS discovery: NAPTR, SRV and address records

Understand service selection and failover before hard-coding a SIP server IP address.

Read guide →
Protocol reference

SIP authentication: challenges and modern digest support

Understand the difference between a normal challenge, failed credentials and an unsupported algorithm.

Read guide →
Guide · Asterisk Latest API branch 23 PJSIP_PARSE_URI, PJSIP_PARSE_URI_FROM, PJSIP_HEADER and FILTER documentation plus current Asterisk security guidance and RFC 3261 reviewed October 13, 2026; no Asterisk host, module, channel, header, variable, URI, parser result, endpoint, route, transport, DNS result, SIP message or call was inspected or tested

Asterisk PJSIP_PARSE_URI: extract SIP URI parts without inventing trust

Parse a bounded SIP URI into documented components while keeping header ownership, absent-value sentinels, authorization, DNS, transport selection and final routing independently observable.

Read guide →
Troubleshooting · Asterisk Latest API branch 23 PJSIP_PARSE_URI, PJSIP_PARSE_URI_FROM, PJSIP_HEADER and FILTER documentation plus current Asterisk security guidance and RFC 3261 reviewed October 13, 2026; no Asterisk host, module, channel, header, variable, URI, parser result, endpoint, route, transport, DNS result, SIP message or call was inspected or tested

Asterisk PJSIP_PARSE_URI returns an empty or wrong component

Trace one URI from its exact SIP header or channel variable through function availability, argument form, selector, absence sentinel and the downstream policy or routing decision.

Read guide →
Guide · Current Asterisk PJSIP_HEADER_PARAM, PJSIP_HEADER, PJSIP_PARSE_URI_FROM, CHANNEL, Dial and pre-dial-handler documentation plus RFC 3261 reviewed October 13, 2026; PJSIP_HEADER_PARAM is documented since Asterisk 18.16.0 and 20.1.0 and currently supports only the From header, while installed release, loaded module, dialplan owner, channel leg, parameter contract, endpoint policy, upstream rewriting and emitted SIP remain deployment specific; no PBX, module, endpoint, trunk, dialplan, channel, request, response, packet or call was inspected or tested

Asterisk PJSIP_HEADER_PARAM: From URI and header parameter boundaries

Read or set one documented From parameter on the correct PJSIP channel without confusing URI placement, header placement, caller identity, carrier policy or emitted SIP.

Read guide →
Troubleshooting · Current Asterisk PJSIP_HEADER_PARAM, PJSIP_HEADER, PJSIP_PARSE_URI_FROM, CHANNEL, Dial and pre-dial-handler documentation plus RFC 3261 reviewed October 13, 2026; PJSIP_HEADER_PARAM is documented since Asterisk 18.16.0 and 20.1.0 and currently supports only the From header, while installed release, loaded module, dialplan owner, channel leg, parameter contract, endpoint policy, upstream rewriting and emitted SIP remain deployment specific; no PBX, module, endpoint, trunk, dialplan, channel, request, response, packet or call was inspected or tested

Asterisk PJSIP From parameter is empty, misplaced or absent

Trace release support, parameter type, channel ownership, pre-dial timing, emitted From syntax and intermediary rewriting before replacing a complete SIP header.

Read guide →
Guide · Current Asterisk branch 23 CHANNEL, PJSIP_ENDPOINT, PJSIP_PARSE_URI and pre-dial-handler documentation plus RFC 3261 reviewed October 14, 2026; CHANNEL(pjsip,...) exposes signaling data for the exact current PJSIP channel, while installed release, loaded modules, caller or callee leg, dialog state, endpoint association, transport object, intermediary rewriting and packet evidence remain deployment specific; no PBX, module, configuration, endpoint, channel, dialog, URI, address, transport, packet or call was inspected or tested

Asterisk PJSIP channel signaling context: URI, tag and socket evidence

Read one PJSIP call leg without confusing its Call-ID, local and remote dialog identity, target, original inbound Request-URI, transport security, socket addresses or endpoint object.

Read guide →
Diagnostic · Current Asterisk branch 23 CHANNEL, PJSIP_ENDPOINT, PJSIP_PARSE_URI and pre-dial-handler documentation plus RFC 3261 reviewed October 14, 2026; CHANNEL(pjsip,...) exposes signaling data for the exact current PJSIP channel, while installed release, loaded modules, caller or callee leg, dialog state, endpoint association, transport object, intermediary rewriting and packet evidence remain deployment specific; no PBX, module, configuration, endpoint, channel, dialog, URI, address, transport, packet or call was inspected or tested

Asterisk PJSIP channel URI or address is empty or wrong

Prove technology, channel leg, read timing and selector meaning before treating a blank or unexpected URI, tag, Call-ID, security flag or socket address as a SIP failure.

Read guide →
Guide · Current Asterisk MessageSend, MESSAGE, MESSAGE_DATA and res_pjsip documentation plus RFC 3428 reviewed October 14, 2026; the APIs have been documented since Asterisk 10.0.0 and the endpoint message_context option since 13.5.0, but installed modules, endpoint and contact state, URI construction, authentication, peer method support, SIP transaction result, endpoint display and user receipt remain deployment specific, and no PBX, module, endpoint, AoR, contact, dialplan, header, body, request, response, packet, device, user interface or message was inspected or tested

Asterisk PJSIP MessageSend: Request-URI, headers and delivery evidence

Build one SIP MESSAGE deliberately, keep its Request-URI separate from To and From identity, and prove the protocol response without treating handler acceptance as user receipt.

Read guide →
Troubleshooting · Current Asterisk MessageSend, MESSAGE, MESSAGE_DATA and res_pjsip documentation plus RFC 3428 reviewed October 14, 2026; the APIs have been documented since Asterisk 10.0.0 and the endpoint message_context option since 13.5.0, but installed modules, endpoint and contact state, URI construction, authentication, peer method support, SIP transaction result, endpoint display and user receipt remain deployment specific, and no PBX, module, endpoint, AoR, contact, dialplan, header, body, request, response, packet, device, user interface or message was inspected or tested

Asterisk PJSIP MessageSend fails or uses the wrong URI

Trace one text message from the Asterisk message object through destination parsing, endpoint and contact selection, SIP request, response and endpoint presentation.

Read guide →