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

Asterisk AMI PJSIP AoR list is empty, stale or has the wrong contacts

Trace an unexpected AoR inventory through completion, exact object identity, endpoint association, generated configuration, contact ownership and lifecycle timing.

Reviewed 2026-10-19Current branch-23 PJSIPShowAors, AorList, AorListComplete, PJSIPShowEndpoint, AorDetail, PJSIP_AOR and PJSIP_CONTACT references, PJSIP object and troubleshooting 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, AoR, endpoint association, static contact, dynamic registration, contact expiry, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, REGISTER transaction, qualification exchange, channel, packet, media stream or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one disputed AoR snapshot

Record timestamp and timezone, responding node and branch, configuration owner, manager identity, action and ActionID, immediate response, every row, AorListComplete, exact AoR name, expected endpoint association, contact text, MaxContacts, replacement controls, expiration and qualification policy.

Classify the symptom: entire list empty; exact AoR absent; duplicate or unexpected AoR; wrong policy; static contact missing; dynamic contact missing or stale; endpoint association wrong; list never completes; or inventory is correct but service fails.

Prove action availability, authority and completion

Verify PJSIPShowAors exists in the authenticated manager action inventory for the installed branch. Check manager authentication, command-class authorization, event filters, session continuity and parser behavior. Require the named completion event and reconcile its ListItems with retained rows.

Do not interpret a permission failure, filtered event stream, disconnect, timeout or cancelled transaction as an empty AoR inventory.

Resolve the exact name and configuration owner

Compare the requested name byte-for-byte with the loaded AoR inventory. In generated FreePBX deployments, identify the module or database owner and prove which node loaded the generated object. A saved GUI record does not prove the queried Asterisk process accepted it.

Use the exact PJSIP_AOR field read or endpoint-associated AorDetail only after proving their scope. Preserve load or reload errors rather than directly editing generated files.

Separate static contacts from REGISTER-created contacts

A static contact= entry is configured directly. A dynamic contact is created by inbound REGISTER and is governed by AoR naming, registrar availability, max_contacts, expiration and replacement policy. The troubleshooting guide notes that a missing max_contacts prevents inbound registration.

Compare the current contact identifier with exact contact detail and registration evidence. An absent dynamic contact can reflect rejection, expiry, de-registration, replacement, node mismatch or observation timing; it is not automatically a network failure.

Reconcile count, replacement and qualification evidence

Confirm whether MaxContacts applies to the disputed contact population and whether remove_existing and remove_unavailable are intended to replace the soonest-expiring or unavailable entries. Preserve the before-and-after list around one authorized registration attempt.

Qualification settings govern OPTIONS behavior and availability marking. They do not create a registration, prove endpoint association or guarantee that INVITE, SDP and RTP will succeed.

Correct the first divergence and retest service independently

Correct only the demonstrated boundary: action availability, manager authority, parser framing, node, generated object, exact name, endpoint association, static contact, registrar module, contact limit, replacement policy, expiration, qualification or stale cache. Repeat the same completed inventory.

If the AoR and contacts now agree but calls still fail, continue through endpoint identification, authentication, dialplan, signaling, SDP and media. No PBX, module, manager account, session, AoR, endpoint, contact, registration, REGISTER transaction, qualification exchange, channel, packet, media stream or live call was inspected or tested.

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 branch-23 PJSIPShowAors, AorList, AorListComplete, PJSIPShowEndpoint, AorDetail, PJSIP_AOR and PJSIP_CONTACT references, PJSIP object and troubleshooting 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, AoR, endpoint association, static contact, dynamic registration, contact expiry, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, REGISTER transaction, qualification exchange, channel, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP AoR lists, contact policy and exact inspection

Inventory every loaded AoR without turning contact text, counts or registration policy into proof of one current binding, reachable device or working call.

Read guide →
Troubleshooting · 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 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.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

Asterisk PJSIP endpoint shows unavailable

Distinguish object loading, contact existence and qualify results before replacing a working configuration.

Read guide →
Troubleshooting · FreePBX 17 platform, version-13-scoped Sangoma extension field reference and current Asterisk PJSIP runtime documentation reviewed October 5, 2026; no PBX, endpoint or registration test

FreePBX PJSIP extension does not register

Trace one failed REGISTER through transport, authentication, endpoint loading, AoR Contact policy and FreePBX-generated runtime state.

Read guide →
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 CLI, logging, PJSIP troubleshooting and call-identifier documentation reviewed September 30, 2026; CLI commands are not shell commands; no PBX, trace, call or media tested

Asterisk CLI and PJSIP logging for one failed call

Bind one failed call to the loaded PJSIP objects, dialplan decision and short signaling trace, then prove diagnostic cleanup.

Read guide →