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

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.

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

Freeze the release, driver and failed request

Record node, exact Asterisk branch and maintenance release, package or build provenance, upgrade path, loaded SIP modules, configuration owner, AMI user, ActionID, raw request and response, and the first changed timestamp. Classify the symptom as unknown action, denied action, empty legacy list, missing peer detail, stale registry view, collector parse failure, absent PJSIP object or call behavior that differs after migration.

Do not start by recreating a legacy action name. First establish whether the upgraded release can contain chan_sip at all.

Apply the documented removal boundary

chan_sip was deprecated in Asterisk 17 and removed in 21. The legacy SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry pages are generated from Asterisk 20, not the current branch. On 21 or later, their absence is expected unless the product has made a separately documented downstream change.

On 20 or earlier, distinguish module not built, module not loaded, configuration failure and AMI authorization from a genuinely empty peer inventory. ListCommands shows what the authenticated manager user can invoke; it is not a package inventory.

Validate the old snapshot only where chan_sip exists

Where chan_sip is supported and loaded, issue SIPpeers with a unique ActionID, collect every Peerlist row and require PeerlistComplete before declaring the inventory empty or complete. Use SIPshowpeer only for one exact Peer; keep its text-format response separate from the list transaction.

If rows arrive without completion, or a collector loses framing, report an incomplete observation. Do not convert socket quiet or one missing row into proof that the peer disappeared.

Rebuild the operational question on PJSIP

Inventory current endpoints with PJSIPShowEndpoints, then inspect the specific endpoint, AoR, contacts, authentication, identify rule, transport and registration objects needed for the symptom. Preserve the completion boundary for each event list and keep endpoint configuration separate from contact reachability and registration state.

A legacy peer name may map to several PJSIP objects or to no direct equivalent. Compare intent, matching rules and relationships rather than copying a display label or a text field.

Review conversion output and effective ownership

If sip_to_pjsip.py was used, capture its source directory, included files, version, options, output and warnings. Compare the candidate output with the generated or hand-owned configuration actually loaded by Asterisk or FreePBX. The conversion helper is a starting point, not evidence that authentication, NAT, transports, inbound matching or outbound registration is correct.

Respect the configuration owner. On a GUI-managed PBX, repair the supported object model and regenerate through its normal workflow rather than editing generated files as an undocumented shortcut.

Repair the first demonstrated boundary and retest narrowly

Correct only the proved boundary: unsupported legacy integration, missing module on a supported release, AMI permissions, collector framing, configuration conversion, endpoint relationships, registration, identify matching, transport or routing. Repeat the exact inventory and detail checks on the same node and record their completion boundaries.

In an authorized maintenance window, validate registration, one inbound route, one outbound route, identity handling, answer, two-way audio and release as separate outcomes. No system, migration, endpoint, registration or call was tested for this diagnostic.

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

Read guide →
Troubleshooting · 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 feature or module is missing after a version or build change

Find the first divergence among branch documentation, source, dependencies, build selection, installed files, load policy, running module state and registered capability.

Read guide →
Troubleshooting · 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 action is missing, unknown or permission denied

Trace one unavailable AMI action through session identity, user-scoped inventory, administrator registry, release and module support, authorization, framing and target behavior.

Read guide →
Troubleshooting · 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 list has the wrong state, count or objects

Trace an unexpected endpoint row through list completion, exact object detail, configuration ownership, contacts, device-state calculation, channels and node scope.

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

VoIP troubleshooting

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

Explore topic →