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

Asterisk AMI PJSIP contact list is stale or a status event is missing

Trace a disputed contact state through list completion, exact identity, event authority, registration lifecycle, qualification policy and node-local timing.

Reviewed 2026-10-19Current branch-23 PJSIPShowContacts, ContactList, ContactListComplete, ContactStatus, ContactStatusDetail, PJSIPShowRegistrationInboundContactStatuses, PJSIPQualify, PJSIP_CONTACT and res_pjsip references plus PJSIP troubleshooting and AMI v2 guidance were reviewed October 19, 2026. Installed branch, loaded modules, manager permissions and filters, configuration owner, contact population, registration lifecycle, qualify exchange and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, OPTIONS exchange, packet, media stream or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one disputed observation window

Record timestamp and timezone, node and branch, manager identity, action and ActionID, immediate response, every ContactList row, ContactListComplete, exact contact ID, URI, AoR, endpoint, expiration, status, RTT and qualification policy. Preserve any ContactStatus events with their original field names.

Classify the symptom: list incomplete; contact absent; wrong static or dynamic population; stale expiration; unexpected status; missing Removed or Updated; missing reachability transition; RTT unchanged; or contact looks reachable while calls fail.

Prove list authority and terminal framing

Verify the action exists for the installed branch and the manager account can execute it and receive command-class rows. Require ContactListComplete and reconcile its count after applying documented parser rules.

Do not interpret rejected authority, filtered events, disconnect, timeout, cancellation, parser loss or querying a different node as an empty or completed list.

Resolve exact contact ownership and lifecycle

Match ObjectName byte-for-byte, then map it to its AoR and endpoint. Determine whether it is a permanent contact created from an AoR contact= URI or a dynamic contact created by REGISTER. Compare current expiration, registrar evidence and the exact PJSIP_CONTACT fields.

An absent contact may reflect failed registration, de-registration, expiry, replacement policy, reload, restart pruning, a different node or observation timing. Correct the first demonstrated divergence instead of recreating every PJSIP object.

Audit the live-event path separately from the snapshot

Confirm system-event read authority, event filters, session continuity and the observation start time. Preserve the documented ContactStatus vocabulary rather than normalizing it to the ContactList vocabulary. Check whether refresh-update events were intentionally enabled with send_contact_status_on_update_registration.

A quiet live stream proves only that this observer received no matching event during that interval. It does not reconstruct earlier transitions or establish an unchanged contact.

Run one bounded qualification experiment

Record loaded qualify_frequency, qualify_timeout, qualify_2xx_only, proxy and authentication policy. If authorized, issue PJSIPQualify for the exact endpoint with a unique ActionID, then retain the action response, subsequent events and a fresh completed contact list.

Separate DNS time, request transmission, challenge handling, response class, timeout and status update. An accepted action, old RTT, or later Reachable label alone does not prove which packet caused the change or that calls and media work.

Correct the first divergence and verify the user symptom

Correct only the proven boundary: action availability, manager authority, filter, parser, node, exact identity, configuration ownership, registration lifecycle, expiration, periodic qualification or explicit qualify handling. Repeat the same completed snapshot and observation window.

If contact state now agrees but calls still fail, continue through endpoint selection, dialplan, signaling, SDP and media. No PBX, module, manager account, session, AoR, endpoint, contact, registration, OPTIONS exchange, 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 PJSIPShowContacts, ContactList, ContactListComplete, ContactStatus, ContactStatusDetail, PJSIPShowRegistrationInboundContactStatuses, PJSIPQualify, PJSIP_CONTACT and res_pjsip references plus PJSIP troubleshooting and AMI v2 guidance were reviewed October 19, 2026. Installed branch, loaded modules, manager permissions and filters, configuration owner, contact population, registration lifecycle, qualify exchange and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, OPTIONS exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP contact lists, status events and qualification evidence

Separate completed contact snapshots, dynamic-registration detail, asynchronous state changes and requested qualification without turning any one surface into proof of a working call.

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 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 · 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 →