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

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.

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

Define the observation boundary first

Record the responding node, exact Asterisk build, loaded res_pjsip_pubsub module, configuration owner, manager identity and capture time. PJSIPShowResourceLists displays configured resource-list objects; it does not enumerate active subscription dialogs or prove that a phone accepted a NOTIFY.

Keep resource-list object name, list items, event package, endpoint, subscription dialog and device key or lamp as separate identifiers. Join them only where retained configuration and signaling evidence establish the relationship.

Close the AMI list with its completion marker

Send Action: PJSIPShowResourceLists with a unique ActionID, retain every matching ResourceListDetail, and wait for ResourceListDetailComplete. The action documentation says one detail event is issued for each configured resource-list object before the completion event.

A zero-row result is trustworthy only when the response and matching completion marker are present. Missing rows without completion can reflect collection timing, authorization, filters or a disconnected client rather than an empty configuration.

Interpret each configuration row narrowly

A ResourceListDetail row identifies ObjectType, ObjectName, SIP Event, FullState, comma-separated ListItem values, NotificationBatchInterval and ResourceDisplayName. Preserve the raw row and compare it with the reviewed pjsip.conf source.

These fields describe the configured object. They do not report which endpoint subscribed, whether each list item resolved, whether a dialog is active or whether a notification fit on the wire.

Understand list semantics before changing them

A resource list uses type = resource_list, an event package and one or more list_item entries. Lists can be nested. The documented policy applies the top-most list batching interval, and a name collision can resolve to the list when the subscriber advertises eventlist support.

Large full-state notifications can exceed the implementation message-size boundary, so the configuration guide recommends smaller sub-lists when necessary. Treat list structure, event package and device support as part of the contract.

Do not treat reload as a live-dialog update

The resource-list guide states that an established subscription keeps the list snapshot from setup time: later list changes and resources that appear later are not incorporated into that dialog. Terminate and re-establish the authorized subscription when validation requires the changed list.

After configuration inventory agrees, use the separate PJSIP subscription inventory and bounded SIP evidence to verify a new dialog, its event package, NOTIFY exchange and endpoint behavior.

Collect least-privilege evidence

Use a dedicated AMI identity with only the required action and event classes, source restrictions and explicit filters that allow the detail and completion events. Redact manager secrets, endpoint identities and tenant-specific object names while preserving ActionID, row count, raw field names, completion and timestamps.

No PBX, FreePBX system, module, configuration, manager account, credential, endpoint, subscription, SIP message, packet, notification or device was inspected or tested. Validate on one authorized disposable list and endpoint before operational reliance.

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 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 inventory and dialog evidence

Read inbound and outbound subscription lists as completed AMI snapshots while keeping notifier roles, subscriber roles, SIP dialogs and endpoint display separate.

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

Asterisk device state, extension hints and presence

Separate a device provider's state, a hint's aggregate extension state, a user's presence choice and the PJSIP subscription that delivers updates to a phone.

Read guide →
Reference · SIP standards; extension support depends on both peers

SIP SUBSCRIBE and NOTIFY: presence, BLF and event state

Separate event subscriptions from registration and identify stale phone indicators.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated ListCommands references plus official AMI syntax, v2 specification, manager-command, change/versioning, permission, module-loader and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, build, package and module set, manager user, read and write authorizations, session mask, action registration, request framing, parameters, target objects, response, related events and service outcome remain deployment specific; no PBX, module, package, manager user, manager session, request, response, event, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk AMI command inventory and permission evidence

Use ListCommands and the administrator CLI to distinguish the actions visible to one manager user from the actions registered by the running Asterisk instance.

Read guide →
Guide · 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 event delivery, filters and WaitEvent

Trace event delivery through manager read permissions, login and Events masks, configured and session filters, TCP or HTTP transport, WaitEvent queueing and client processing without treating silence as a failed PBX.

Read guide →
Guide · Operational guidance; Asterisk 22 / FreePBX 17 where applicable

Least privilege for PBX users and integrations

Separate the right to register, place calls, administer the PBX and read sensitive data.

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

Read guide →