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

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.

Reviewed 2026-10-27Current 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 testedAdvancedDocumentation based · not lab tested

Freeze the node, release, request and first symptom

Record node, exact Asterisk branch and maintenance release, build provenance, loaded chan_iax2 module, configuration owner, AMI identity and permissions, raw request and response, local and UTC timestamps and the first failed boundary. Classify unknown or denied action, empty peer output, stale registry row, absent active-channel statistics, collector timeout or a separate call symptom.

Use a unique ActionID only for IAXpeerlist, IAXpeers and IAXregistry. The documented IAXnetstats syntax has no arguments, so adding ActionID is not a supported correlation method.

Prove action availability and authorization before peer state

Confirm the installed branch documents the action, the module is present and loaded, and the authenticated manager identity can invoke it. Compare direct raw AMI frames with collector output. Unknown action, permission denial, socket closure, parser failure and an accepted but apparently empty response have different owners.

A successful manager login or action response does not prove that the result is complete. Preserve response framing and timestamps instead of treating quiet time as an undocumented list terminator.

Compare peer actions without inventing equivalence or completion

Run IAXpeerlist and IAXpeers only where authorized, each with its own ActionID, and retain all frames. Current generated action pages do not document row-event schemas or a completion event for either action. Do not invent PeerlistComplete, count socket silence as completion or force the two outputs into one schema.

If an installed branch or implementation source defines additional output, label that evidence with the exact release. Report incomplete observation when the collector cannot prove its framing boundary.

Separate registry rows from peer, binding and route state

Use IAXregistry for its documented registration view, then check peer configuration, dynamic binding, qualification, authentication, ACL and routing independently. Confirm server identity, resolved address, observed source, expiry or refresh timing and clock alignment before calling a row stale.

Registration does not prove inbound authorization, outbound route selection, answer or two-way audio. Repair only the first demonstrated configuration, network, authentication or timing boundary.

Capture IAXnetstats only while the target channel is active

Prove the exact IAX channel exists at the capture time, then collect the raw IAXnetstats response and a packet timeline for the same call. Because the action documents no arguments, do not claim an ActionID, channel filter, peer filter or historical window. Preserve unfamiliar field names and units as version-bound unknowns until verified against the installed release.

No rows can mean no active IAX channel at that instant, an action or collector problem, or other deployment-specific behavior. Network-stat output alone does not prove capacity, completed routing, decoded media or audible quality.

Correct the first boundary and repeat one controlled workflow

Assign one owner: release or module, AMI permission, response framing, collector parser, peer configuration, registration refresh, ACL, authentication, call token policy, bind or network path, route, active-channel timing or media. Avoid blanket ACL, authentication, encryption or call token disablement.

Repeat the same peer and registry observations and one authorized call with channel, packet, answer and two-way audio evidence kept separate. No PBX, peer, registry, active channel, packet, call or audio 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 · 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 · 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 · 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 →
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 →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

VoIP packet-capture methodology

Select interfaces, time windows and paired capture points that distinguish network loss from missing evidence.

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

VoIP troubleshooting

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

Explore topic →