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

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.

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

Establish release, module and manager identity first

The current Asterisk AMI index still lists IAXpeerlist, IAXpeers, IAXregistry and IAXnetstats under chan_iax2. Record the responding node, exact Asterisk branch and maintenance release, package or build provenance, loaded module, authenticated manager identity, action permissions and local and UTC time before interpreting a response.

The label IAX in action names refers here to Asterisk's IAX2 channel driver. Action availability is not proof that a peer, registry row, active channel, route or media path exists.

Keep the two peer-list actions inside their documented contracts

The current generated pages describe both IAXpeerlist and IAXpeers as listing IAX peers, and both document an optional ActionID. They do not document row-event names, field schemas or completion events. Preserve the raw request and every received AMI frame, but do not invent Peerlist, PeerlistComplete or another closure marker by analogy with a different channel driver.

A successful response can confirm that the action was accepted; it does not establish a complete inventory. Treat differences between the two actions as version-bound implementation output unless the installed release or source provides a stronger contract.

Treat IAXregistry as registration evidence only

IAXregistry is documented as showing IAX registrations and accepts an optional ActionID. Keep configured peers, dynamic peer binding, outbound registry state, qualification, authentication, inbound matching, routing and call behavior as separate observations.

A registration row does not prove peer reachability, authorization, route selection, completed calling or two-way audio. Retain the identity, server, address, state and timestamp exactly as returned by the installed branch rather than normalizing unknown fields into a generic online status.

Bound IAXnetstats to active-channel point-in-time output

IAXnetstats is documented as showing IAX channel network statistics. Its current syntax documents no arguments: no ActionID, peer filter, channel selector or time range is declared. Do not fabricate request correlation, filters, row events, units or a completion marker.

Network statistics are a point-in-time observation for active IAX channels, not a historical quality record, capacity result, endpoint-health result, route-success result or guarantee. Preserve the raw fields and exact Asterisk release because implementation output and units may be version-sensitive.

Keep configuration, security and transport evidence separate

Bind address and port, peer type, authentication, encryption, call token policy, ACL, registration expiry, qualification and jitterbuffer settings solve different problems. Asterisk documents call token validation as protection against spoofed-source call-number exhaustion; disabling it broadly is not a peer-discovery fix.

IAX2 carries its own signaling and media protocol path. Do not transpose SIP or PJSIP endpoint, AoR and contact semantics onto these actions. An ACL pass, accepted credential, dynamic address, qualified peer, active channel and received media remain distinct.

Correlate one call and state the untested boundary

For an authorized test, align peer and registry snapshots, exact dial target, route, channel creation, IAXnetstats captured while the channel is active, packet directions, answer, decoded media and audible result on one timeline. Remove or sanitize credentials, addresses and call data before sharing evidence.

No PBX, FreePBX system, module, configuration, manager account, credential, peer, registry, channel, packet, call or audio was inspected or tested. Documentation and source review do not establish availability, compatibility, observed field meanings or laboratory validation for a deployment.

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

Hub

Asterisk

Understand the programmable PBX and follow the Asterisk 22 LTS documentation baseline.

Explore topic →
Guide · Current Asterisk interface documentation reviewed September 30, 2026; implementation must be checked against the installed branch and integration library

Asterisk AMI, ARI and AGI: choose the control boundary

Separate management events, synchronous dialplan work and application-owned call control before exposing an integration.

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 · Asterisk branch-23-generated Login, Challenge, Logoff and Events references, branch-22-generated Login reference, and official AMI syntax, v2, permission and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, listener and transport, manager.conf ownership, username, secret rotation, ACL, read and write classes, login event mask, connection lifetime, client timeout, reconnect policy and downstream operations remain deployment specific; no PBX, manager configuration, credential, ACL, socket, manager session, request, response, event, channel, packet, media stream or live call was inspected or tested

Asterisk AMI session authentication, Login, Logoff and Challenge

Keep manager identity, authentication exchange, transport protection, event mask, permissions and session lifetime as separate AMI evidence.

Read guide →
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 · Sangoma Asterisk Info documentation, the FreePBX Asterisk Info and ARI Manager release/17.0 repositories, and current Asterisk CLI documentation reviewed October 16, 2026. The Asterisk Info release branch exposed module version 17.0.2 and an ARI Manager dependency when reviewed; that repository state does not establish the versions installed or loaded on a selected PBX. The report surfaces snapshots from Asterisk, while configuration ownership, module state, report implementation, time, node, command output and service outcomes remain separate. No PBX, module, ARI or AMI session, endpoint, trunk, channel, queue, conference, voicemail box, subscription, packet, media stream or live call was inspected or tested

FreePBX Asterisk Info: read each report as a bounded runtime snapshot

Use FreePBX Asterisk Info without collapsing module availability, generated configuration, loaded Asterisk state, report rendering and call outcomes into one status label.

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 →