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

Asterisk AMI PJSIP resource list is missing, stale or incomplete

Find the first divergence across module support, completed AMI inventory, pjsip.conf ownership, list semantics, subscription refresh, NOTIFY delivery and endpoint state.

Reviewed 2026-10-26Current branch-23-generated Asterisk PJSIPShowResourceLists and ResourceListDetail documentation, resource-list subscription and res_pjsip_pubsub configuration guidance, PJSIP troubleshooting, AMI v2, event-filtering and network-security documentation were reviewed October 26, 2026; installed Asterisk version, module availability, pjsip.conf object graph, endpoint support, active subscription state, manager permissions and filters, SIP signaling, notification size and device behavior remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, endpoint, subscription, SIP message, packet, notification or device was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one node, object and contradiction

Record node, build, process start context, module state, configuration source, resource-list name, intended event package and items, manager identity, ActionID, response, detail rows, completion event and the first contradictory timestamp.

Classify the symptom as unknown or denied action, missing completion, missing object, stale fields, wrong event package, wrong membership, existing-dialog staleness, missing NOTIFY or endpoint display failure. Do not merge these layers.

Prove module and manager support first

Confirm res_pjsip_pubsub is loaded in the exact responding process and inventory the actions available to the authenticated AMI identity. Verify write authorization for the action and read authorization plus filters for both ResourceListDetail and ResourceListDetailComplete.

Repair module or AMI visibility before interpreting an absent row. An unsupported observation surface is not evidence that the configuration object or subscription failed.

Repeat a bounded completed inventory

Use a fresh ActionID, retain the action response and every matching detail row, and wait for the matching completion event. Compare the returned object names and raw fields with the authoritative pjsip.conf resource-list sections on that node.

If completion is absent, fix the collector, connection, read class or filter. If completion is present but the object is absent or stale, resolve configuration generation, include order, reload and node-selection ownership.

Validate list semantics and size separately

Check type = resource_list, event package, each list_item, nesting, full_state, batch interval and display-name setting. For nested lists, reason from the top-most interval. Check for a same-name individual resource when the subscriber advertises eventlist.

Estimate and observe the resulting NOTIFY size rather than assuming an item-count threshold. Split overly large lists into smaller sub-lists when the documented message-size limitation is implicated.

Re-establish the subscription after a list change

Do not expect an established dialog to absorb changed membership or a resource that appeared after setup. End the authorized test subscription and establish a new one, then inspect the separate PJSIP subscription inventory and bounded SIP SUBSCRIBE and NOTIFY evidence.

A correct AMI configuration row still does not prove an active dialog, accepted NOTIFY or updated lamp. Continue through endpoint event-package support and device rendering.

Repair the first owner and verify end to end

Correct only the demonstrated owner: module loading, AMI authorization or filters, collector completion, configuration generation or reload, object semantics, list size, subscription renewal, SIP delivery or endpoint behavior. Repeat one bounded inventory and one authorized fresh subscription.

Retain the before and after object row, completion marker, new dialog evidence and endpoint result without secrets. No PBX, module, configuration, manager session, endpoint, subscription, SIP message, packet, notification or device 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-generated Asterisk PJSIPShowResourceLists and ResourceListDetail documentation, resource-list subscription and res_pjsip_pubsub configuration guidance, PJSIP troubleshooting, AMI v2, event-filtering and network-security documentation were reviewed October 26, 2026; installed Asterisk version, module availability, pjsip.conf object graph, endpoint support, active subscription state, manager permissions and filters, SIP signaling, notification size and device behavior remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, endpoint, subscription, SIP message, packet, notification or device was inspected or tested

Asterisk AMI PJSIP resource-list inventory and configuration evidence

Use PJSIPShowResourceLists as a completed configuration inventory while keeping configured list membership, active subscriptions, SIP NOTIFY delivery and endpoint display state separate.

Read guide →
Troubleshooting · Current branch-23 inbound and outbound subscription-list actions and detail events, res_pjsip and res_pjsip_pubsub configuration references, presence and resource-list guidance, PJSIP troubleshooting guidance and the AMI v2 specification were reviewed October 21, 2026. The actions are documented since Asterisk 12.0.0, while installed branch, loaded modules, manager permissions and filters, endpoint identity, subscription dialogs, persistence records, event packages, body generators, device interpretation and state sources remain deployment specific. No PBX, module, manager account, endpoint, subscription, persistence record, SUBSCRIBE, NOTIFY, packet, phone display, mailbox lamp, BLF key or live call was inspected or tested

Asterisk AMI PJSIP subscription list is missing, stale or incomplete

Trace action availability, AMI completion, subscription direction, dialog identity, state ownership and the actual NOTIFY path before changing endpoints.

Read guide →
Troubleshooting · Current Asterisk device-state, extension-hint, state-query, presence-state and res_pjsip subscription documentation plus the Asterisk 22.12.0-rc2 change record were reviewed October 8, 2026; exact commands, modules, bodies and phone behavior depend on the installed branch, dialplan and endpoint, and candidate fixes are not final-release availability

Asterisk BLF lamp is stale, unknown or not updating

Trace one monitored extension from loaded hint and device provider through the PJSIP subscription dialog, NOTIFY bodies and the phone's key mapping.

Read guide →
Troubleshooting · SIP standards and current diagnostic documentation; Asterisk examples apply to 22, FreePBX controls to the installed 17 module

BLF stays stale while the phone can still make calls

Inspect the monitored resource, subscription lifetime and delivered event state before replacing phone buttons.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated Events, Filter, WaitEvent, Login and Ping action references, matching branch-22 Events, Filter and WaitEvent references, the official AMI event-filtering guide and Manager TCP/IP API reviewed October 16, 2026; installed branch, manager user permissions, login mask, static and dynamic filters, connection type, event queue, client parser, reconnect behavior, action concurrency, downstream storage and call activity remain deployment specific; no PBX, AMI session, manager user, permission, configuration file, socket, HTTP session, event queue, channel, bridge, packet, media stream or live call was inspected or tested

Asterisk AMI events are missing, filtered, delayed or duplicated

Locate the first divergence among manager permissions, the per-session event mask, configured and dynamic filters, HTTP WaitEvent queueing, TCP reads, reconnects, parsing and downstream deduplication.

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

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →