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

Asterisk AMI chan_sip peer inventory and PJSIP migration evidence

Interpret legacy SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry only within the chan_sip version boundary, then map the operational question to current PJSIP objects and bounded inventories.

Reviewed 2026-10-27Asterisk 20-generated SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry action documentation, current PJSIPShowEndpoints and ListCommands contracts, chan_sip deprecation and removal records, migration guidance, AMI v2 and network-security guidance were reviewed October 27, 2026; installed Asterisk and FreePBX versions, build options, loaded modules, channel driver, manager permissions, configuration ownership, endpoint objects, registrations, contacts, authentication, transports, routing and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, endpoint, AoR, contact, registration, packet, call or audio was inspected or testedAdvancedDocumentation based · not lab tested

Establish the channel driver and release first

chan_sip was deprecated in Asterisk 17 and removed in Asterisk 21. Its AMI actions remain documented on the Asterisk 20 surface, while current Asterisk uses chan_pjsip and res_pjsip for SIP. Record the responding node, installed branch and maintenance release, build provenance, loaded modules and authenticated AMI identity before interpreting any action result.

A missing SIPpeers, SIPshowpeer, SIPpeerstatus or SIPshowregistry action on Asterisk 21 or later can be the expected result of module removal. It is not evidence that a phone, trunk or registration is absent.

Bound the legacy peer inventory without extending its contract

On a deployment that actually runs chan_sip, Action: SIPpeers accepts ActionID, emits separate Peerlist events and closes with PeerlistComplete. Publish the snapshot only after the documented completion boundary and retain the request identity, all rows, completion and timestamps.

SIPshowpeer instead takes one required Peer and returns text-format detail. SIPpeerstatus takes an optional Peer and can request one or all peer statuses. Keep these contracts separate; a peer detail response is not a completed global inventory.

Keep peer, registry and live call evidence distinct

SIPshowregistry describes the legacy chan_sip registry surface. A configured peer, a reported peer status, an outbound registration, an inbound request match, an authenticated dialog and two-way media are different observations. Preserve peer name, registration identity, remote address, timestamps and call identifiers without flattening them into one “online” state.

Text returned by a legacy action is version-bound output, not a guaranteed schema for a current collector. Retain raw AMI frames and the Asterisk release used to interpret them.

Map the question to PJSIP objects rather than renaming fields

PJSIP separates endpoint, AoR, contact, authentication, identify, transport and registration objects. PJSIPShowEndpoints raises an EndpointList event for each endpoint and ends with EndpointListComplete; it does not recreate the old chan_sip peer model.

Choose the current action for the actual question: endpoint inventory, exact endpoint detail, AoR policy, current contacts, inbound or outbound registrations, identify matching or transport configuration. Do not translate one legacy peer row into one PJSIP object by label alone.

Treat conversion as a reviewed migration, not proof

Asterisk ships sip_to_pjsip.py as a basic conversion aid and explicitly says it is not intended to cover every scenario. It can process included files when run with the right source context, but generated pjsip.conf remains a candidate configuration that needs object-by-object review.

Retain the before-image, included-file set, conversion output, warnings, effective configuration, loaded objects and rollback. PJSIP syntax is stricter, and transport, NAT, authentication, matching and registration semantics require deliberate validation.

Use least privilege and state the untested boundary

Use ListCommands with the intended manager identity to inventory only the actions available to that user; distinguish absent module registration from denied action classes. Restrict AMI source addresses and permissions and protect peer, endpoint, address and credential-bearing output.

No PBX, FreePBX system, module, configuration, manager account, credential, peer, endpoint, AoR, contact, registration, packet, call or audio was inspected or tested. Validate the migration against the installed release, generated configuration owner and an authorized acceptance plan.

Do not copy chan_sip list framing into IAX2 actions

The IAX2 AMI evidence guide notes that the current IAX peer pages do not document Peerlist or PeerlistComplete.

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

Asterisk · First-party Asterisk lifecycle, release-candidate announcement, change-log and artifact indexes were rechecked October 30, 2026. The versions table still labelled 24.x Pre-release, the project had announced 24.0.0-rc4 on October 29, and the inspected release index exposed rc1 through rc4 without establishing a final 24.0.0 release. Lifecycle labels, scheduled dates, branch documentation, candidate artifacts, downstream packages and an installed runtime remain separate evidence. No host, repository, package channel, artifact, hash, signature, source tree, dependency, build, module, configuration, process, API, endpoint, hint, parked call, packet, media stream or call was inspected or tested

Asterisk release lifecycle: status, branch docs and module availability

Read support labels and scheduled dates as separate evidence, match documentation to the running branch, and trace a feature from source and build selection to loaded capability.

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 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 →
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 →
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 20-generated SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry action documentation, current PJSIPShowEndpoints and ListCommands contracts, chan_sip deprecation and removal records, migration guidance, AMI v2 and network-security guidance were reviewed October 27, 2026; installed Asterisk and FreePBX versions, build options, loaded modules, channel driver, manager permissions, configuration ownership, endpoint objects, registrations, contacts, authentication, transports, routing and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, endpoint, AoR, contact, registration, packet, call or audio was inspected or tested

Asterisk AMI SIPpeers or SIPshowpeer is missing after an upgrade

Separate expected chan_sip removal from manager permissions, module state, collector assumptions and incomplete PJSIP migration before diagnosing a missing peer or registration.

Read guide →
Guide · Current and Asterisk 22-generated IAXpeers, IAXpeerlist, IAXregistry and IAXnetstats action documentation, IAX2 security guidance, iax.conf sample, chan_iax2 source and AMI v2 specification were reviewed October 27, 2026; installed Asterisk and FreePBX versions, downstream patches, build options, loaded chan_iax2 module, manager permissions, peer configuration, dynamic binding, outbound registration, qualification, active channels, network-stat fields and units, routing, packets and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, registry, channel, packet, call or audio was inspected or tested

Asterisk AMI IAX2 peer, registry and netstats evidence

Use IAXpeerlist, IAXpeers, IAXregistry and IAXnetstats as separate chan_iax2 observations without inventing undocumented event schemas, completion markers, filters or proof of call quality.

Read guide →
Troubleshooting · Current and Asterisk 22-generated IAXpeers, IAXpeerlist, IAXregistry and IAXnetstats action documentation, IAX2 security guidance, iax.conf sample, chan_iax2 source and AMI v2 specification were reviewed October 27, 2026; installed Asterisk and FreePBX versions, downstream patches, build options, loaded chan_iax2 module, manager permissions, peer configuration, dynamic binding, outbound registration, qualification, active channels, network-stat fields and units, routing, packets and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, registry, channel, packet, call or audio was inspected or tested

Asterisk AMI IAX2 peer, registry or netstats is missing, stale or incomplete

Separate action availability, manager permissions, undocumented list framing, peer and registry state, active-channel timing and collector assumptions before changing IAX2 configuration.

Read guide →