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

Asterisk PJSIP AoR or contact lookup is empty, stale or wrong

Trace the exact endpoint, AoR name, returned contact identifier, lifecycle and queried field before changing registration, qualification or dial logic.

Reviewed 2026-10-19Current Asterisk PJSIP_AOR, PJSIP_CONTACT and PJSIP_DIAL_CONTACTS function documentation plus PJSIP object-relationship and troubleshooting guidance reviewed October 13, 2026; both inspection functions are documented since Asterisk 13.2.0, while installed branch, maintenance release, loaded modules, configuration source, object names, registrations, contacts, qualification state, timing and routing remain deployment specific; no PBX, module, configuration, endpoint, AoR, contact, registration, OPTIONS exchange, packet, channel or call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze the disputed object and collection time

Record timestamp and timezone, installed Asterisk release, function name, endpoint, endpoint aors value, queried AoR name and field, returned contact list, selected contact identifier and field, expected value and the dialplan consumer. Preserve a sanitized working example when one exists.

Classify the first mismatch: function unavailable, AoR missing, contact list empty, wrong identifier selected, field empty, value stale, status or RTT misunderstood, multi-contact list truncated, or routing fails despite correct inspection.

Prove release, module and loaded object state

Both inspection functions are documented since Asterisk 13.2.0, but current online documentation does not prove the running release or loaded function modules. Confirm the installed branch and that the functions are registered, then compare the active endpoint and AoR objects with the intended configuration source.

If the AoR cannot be shown, inspect spelling, type=aor, unsupported options and whether configuration was generated and loaded. Do not diagnose registration packets for an object that never loaded.

Follow endpoint to AoR before following AoR to contact

Confirm the endpoint uses the plural aors option and that it points to the intended object. Then query that exact AoR. Similar section names do not create an association automatically, and the username presented by a device does not prove the endpoint references an identically named AoR.

A missing association produces a different failure from an associated AoR with no contacts. Keep the endpoint, association and contact inventory as three observations.

Explain an empty or changing contact list

For a static destination, verify the AoR contains a complete sip: URI. For a dynamic destination, prove the REGISTER was accepted for this AoR, the registrar module is running, max_contacts permits the binding and expiry or replacement policy did not remove it. Re-run the query after one controlled registration change.

A contact can disappear or be replaced legitimately after expiry, network change, reboot or a new registration. Compare identifiers and collection times rather than treating a remembered URI as permanent.

Resolve the exact identifier and field

Preserve every comma-separated identifier from PJSIP_AOR(...,contact) and pass one complete identifier at a time to PJSIP_CONTACT(). Do not pass the AoR name where a contact ID is required, split an identifier at its internal delimiter, or assume the first contact belongs to the device under investigation.

Compare URI, expiry, User-Agent, endpoint, Path, Via, status and RTT only when each field answers the stated question. An old User-Agent string or reachable status does not prove identity, current registration ownership or usable calling.

Correct one boundary and repeat the same route

Correct only the demonstrated owner: installed function support, loaded object, endpoint aors association, static URI, registrar state, contact capacity, expiry or replacement policy, list parsing, identifier selection or field interpretation. Repeat the same lookup and preserve the later dial-string, channel and SIP outcomes separately.

Check an unrelated AoR and an intentionally absent contact so empty remains distinguishable from wrong. Remove temporary verbose logging and protect network and device identifiers. No PBX, configuration, endpoint, AoR, contact, REGISTER, OPTIONS exchange, packet, channel or call was inspected or tested for this diagnostic.

Prove the endpoint profile before following its AoR

Use the PJSIP endpoint diagnostic when the failure begins with a missing endpoint, wrong channel owner or incorrect aors association.

Check whether the wrong AMI inventory hid the contact

The inbound-registration diagnostic distinguishes static, dynamic and all-contact list contracts.

Compare AoR lookup with endpoint object detail

The AMI endpoint-state diagnostic preserves repeated associated objects and the exact completion boundary.

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

Guide · Current Asterisk PJSIP_AOR, PJSIP_CONTACT and PJSIP_DIAL_CONTACTS function documentation plus PJSIP object-relationship and troubleshooting guidance reviewed October 13, 2026; both inspection functions are documented since Asterisk 13.2.0, while installed branch, maintenance release, loaded modules, configuration source, object names, registrations, contacts, qualification state, timing and routing remain deployment specific; no PBX, module, configuration, endpoint, AoR, contact, registration, OPTIONS exchange, packet, channel or call was inspected or tested

Asterisk PJSIP AoR and contact inspection: identity, fields and runtime evidence

Read one Address of Record and its current contact objects without confusing endpoint configuration, registration, qualification or a generated dial string.

Read guide →
Guide · Current Asterisk res_pjsip, PJSIP troubleshooting, dialing and management-interface references reviewed October 6, 2026; no Asterisk host, endpoint, AoR, contact, registration, device, network path or call was inspected or tested

Asterisk PJSIP AoRs and contacts: registration, limits and dialing

Follow a PJSIP endpoint through its AoR and live contacts, then keep admission limits, reachability and first-versus-all-contact dialing as separate decisions.

Read guide →
Guide · Current Asterisk res_pjsip and AMI references plus Asterisk 22 contact-event schemas reviewed October 6, 2026; no endpoint, PBX, DNS path, proxy, OPTIONS exchange, event stream, call or media result was inspected or tested

Asterisk PJSIP contact qualification: read OPTIONS status correctly

Interpret PJSIP OPTIONS, timeouts and contact-event vocabulary without turning qualification into proof of registration, authentication or a usable call.

Read guide →
Guide · Asterisk Latest API PJSIP_DIAL_CONTACTS, Dial, PJSIP_AOR, PJSIP_CONTACT and AMI object documentation plus PJSIP configuration relationships reviewed October 12, 2026; the generated pages reported branch 23, but the installed Asterisk version, endpoint, AoRs, contacts, registration expiry, qualification, dialplan, SIP responses and call legs remain deployment-specific, and no PBX, endpoint, AoR, contact, registration, device, channel, request, response or call was inspected or tested

Asterisk PJSIP_DIAL_CONTACTS: dial every current AoR contact

Build a call-time PJSIP dial string from the intended endpoint and AoR while keeping contact inventory, qualification, outbound channels and the winning answer independently observable.

Read guide →
Diagnostic · Current Asterisk res_pjsip, ContactStatus, ContactStatusDetail, PJSIP contact-listing and troubleshooting documentation reviewed September 29, 2026; no PBX, endpoint, AoR, contact, registration, DNS result, proxy, network path, qualify transaction or call was tested

Asterisk PJSIP contact keeps switching reachable and unreachable

Correlate one contact's registration, expiration, OPTIONS response, RTT and network path before changing qualify timers or contact limits.

Read guide →
Diagnostic · Current Asterisk res_pjsip and diagnostic references plus Sangoma FreePBX extension semantics and Core GraphQL fields reviewed October 6, 2026; the Sangoma Extensions page says it was updated for FreePBX 13, so the installed FreePBX 17 interface and generated configuration remain authoritative

FreePBX PJSIP registration exceeds max contacts or replaces a device

Compare FreePBX extension intent, generated AoR policy, loaded contacts and REGISTER source changes before raising max contacts or enabling automatic replacement.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

VoIP packet-capture methodology

Select interfaces, time windows and paired capture points that distinguish network loss from missing evidence.

Read guide →
Guide · Current Asterisk logging, runtime command, logger.conf, debug-collection, call-identifier and console-verbosity documentation reviewed September 30, 2026; no process, logger, trace, storage path or call tested

Asterisk logging without permanent debug overload

Map configured destinations, console levels, call identifiers and a bounded protocol trace without leaving sensitive debug collection active.

Read guide →
Guide · Current Asterisk PJSIP_ENDPOINT and CHANNEL function documentation, res_pjsip endpoint configuration reference, object-relationship guidance and PJSIP troubleshooting guidance reviewed October 13, 2026; PJSIP_ENDPOINT is documented since Asterisk 12.0.0, while installed branch, maintenance release, loaded modules, configuration backend, object names, defaults, endpoint identification, channel association, contacts, signaling and media remain deployment specific; no PBX, module, configuration, endpoint, identify object, channel, SIP exchange, packet or call was inspected or tested

Asterisk PJSIP endpoint inspection: configuration fields, channel identity and proof

Read one loaded endpoint field without confusing configuration, inbound endpoint identification, AoR location, a live channel or negotiated SIP and media state.

Read guide →
Troubleshooting · Current Asterisk PJSIP_ENDPOINT and CHANNEL function documentation, res_pjsip endpoint configuration reference, object-relationship guidance and PJSIP troubleshooting guidance reviewed October 13, 2026; PJSIP_ENDPOINT is documented since Asterisk 12.0.0, while installed branch, maintenance release, loaded modules, configuration backend, object names, defaults, endpoint identification, channel association, contacts, signaling and media remain deployment specific; no PBX, module, configuration, endpoint, identify object, channel, SIP exchange, packet or call was inspected or tested

Asterisk PJSIP endpoint lookup is empty, missing or shows the wrong field

Trace the function, exact endpoint name, loaded object, current channel association, default resolution and consuming decision before changing SIP policy.

Read guide →
Guide · Current branch-23 and branch-22 PJSIPShowRegistrationsInbound and PJSIPShowRegistrationInboundContactStatuses references, current PJSIPShowContacts, InboundRegistrationDetail and ContactStatusDetail references, PJSIP object guidance and the AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded registrar modules, manager action inventory and permissions, configuration owner, AoR and endpoint relationships, static and dynamic contacts, registration expiry, qualification policy, event framing, network path and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, static contact, dynamic registration, REGISTER transaction, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP inbound registration inventories

Choose the correct AMI inventory for configured AoRs, dynamic inbound registrations or all contacts without turning one completed list into endpoint reachability or call evidence.

Read guide →
Troubleshooting · Current branch-23 and branch-22 PJSIPShowRegistrationsInbound and PJSIPShowRegistrationInboundContactStatuses references, current PJSIPShowContacts, InboundRegistrationDetail and ContactStatusDetail references, PJSIP object guidance and the AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded registrar modules, manager action inventory and permissions, configuration owner, AoR and endpoint relationships, static and dynamic contacts, registration expiry, qualification policy, event framing, network path and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, static contact, dynamic registration, REGISTER transaction, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP inbound registration list shows static contacts or misses a phone

Trace action choice, completion framing, AoR ownership, static versus dynamic contact creation, expiry and node scope before changing registration or NAT settings.

Read guide →
Guide · Current branch-23 PJSIPShowEndpoints, PJSIPShowEndpoint, EndpointList, EndpointListComplete, EndpointDetail and EndpointDetailComplete references, PJSIP object guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, endpoint, AoR, auth, transport, identify, contact, device-state provider, active channel, registration, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, AoR, auth, transport, identify, contact, channel, registration, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP endpoint lists and object detail

Use completed endpoint-list and single-endpoint transactions without turning aggregate device state, contact text or active-channel counts into registration or call proof.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowEndpoints, PJSIPShowEndpoint, EndpointList, EndpointListComplete, EndpointDetail and EndpointDetailComplete references, PJSIP object guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, endpoint, AoR, auth, transport, identify, contact, device-state provider, active channel, registration, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, AoR, auth, transport, identify, contact, channel, registration, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP endpoint list has the wrong state, count or objects

Trace an unexpected endpoint row through list completion, exact object detail, configuration ownership, contacts, device-state calculation, channels and node scope.

Read guide →