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

Asterisk AMI PRI span inventory and bounded debug evidence

Use PRIShowSpans for a bounded PRI status snapshot, then govern PRI debug level and file output as separate operational changes without treating either as physical-line proof.

Reviewed 2026-10-27Current branch-23-generated Asterisk PRIShowSpans, PRIDebugSet, PRIDebugFileSet, PRIDebugFileUnset, SpanAlarm and SpanAlarmClear documentation, AMI v2, event-filtering, logging and network-security guidance were reviewed October 27, 2026; installed Asterisk, libpri and DAHDI versions, chan_dahdi availability, manager permissions, spans, debug levels, file paths, signaling, timing, framing, coding, alarms, hardware and carrier facilities remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, D channel, B channel, line, circuit, configuration, manager account, credential, event stream, debug file, signaling frame, call, packet or audio was inspected or testedAdvancedDocumentation based · not lab tested

Separate PRI, DAHDI and physical identifiers

Record the responding Asterisk node and build, loaded chan_dahdi module, libpri and DAHDI context, generated and effective configuration owner, manager identity and capture time. Keep PRI span, DAHDI span, D channel, B channel, Asterisk channel, carrier circuit and physical port as separate identifiers.

An AMI status response describes the responding Asterisk process. It does not by itself prove carrier service, cabling, framing, coding, timing, signaling exchange, call completion or audio.

Take the PRI span snapshot exactly as documented

Action: PRIShowSpans is documented since Asterisk 10.0.0 as similar to pri show spans. It accepts an ActionID and optional Span; zero or omission requests all spans, while a value narrows the request to one span.

The action page does not document generated row or completion events. Preserve the complete raw response, ActionID, connection identity and timestamps rather than inventing a list boundary or parsing undocumented prose as a stable schema.

Treat debug level as a state change

Action: PRIDebugSet, documented since 13.0.0, requires Span and Level. The documented text values are Level: off, Level: on, Level: hex and Level: intense; the page also permits a numeric value. Record the exact requested and returned values and do not normalize an unfamiliar numeric level into a named mode.

Use the least verbose mode that can answer the stated question and a defined stop time. An accepted action changes Asterisk debug state; it does not prove that a signaling frame was emitted, retained or interpreted correctly.

Control file output separately and plan teardown

Action: PRIDebugFileSet takes a File path and directs PRI debug output to that file. PRIDebugFileUnset disables file output and has no Span or Level argument. The published contracts do not say that unsetting the file also turns span debug off, so use PRIDebugSet with Level: off as a separate, explicit teardown where appropriate.

Choose an approved path, confirm ownership, free space, rotation, access, retention and deletion before enabling output. Asterisk warns that debug logging can generate large volumes quickly on production systems.

Reconcile inventory, alarms and a narrow reproduction

Capture all PRI spans first, then one specific span when narrowing a known identifier. Retain SpanAlarm and SpanAlarmClear as transition evidence and compare them with the separate DAHDI span and channel inventory, configuration and carrier ticket for the same node and observation window.

If a reproduction is authorized, mark its start and stop, expected signaling step and call identifiers. A debug file may expose called or calling numbers and protocol details; redact shared evidence without destroying the chronology needed to diagnose the boundary.

Collect with least privilege and disclose unknowns

Use a dedicated AMI identity, source restrictions, only the required action and event classes, and filters that retain the relevant alarm transitions. Protect AMI credentials, circuit identifiers and debug output in transit and at rest.

No PBX, FreePBX system, module, driver, card, gateway, span, channel, circuit, configuration, manager account, event stream, debug file, signaling frame, call, packet or audio was inspected or tested. Validate the procedure against the installed branch, authorized hardware records and carrier handoff 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-generated Asterisk DAHDIShowStatus, DAHDIShowChannels, DAHDIChannel, SpanAlarm and SpanAlarmClear documentation, channel fundamentals, AMI v2, event-filtering and network-security guidance were reviewed October 27, 2026; installed Asterisk and DAHDI versions, chan_dahdi availability, kernel drivers, spans, timing, signaling, hardware, carrier facilities, analog lines, manager permissions and filters, channel activity and alarm state remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, channel, line, carrier circuit, configuration, manager account, credential, event stream, call, packet or audio was inspected or tested

Asterisk AMI DAHDI span and channel inventory with alarm evidence

Use DAHDIShowStatus, DAHDIShowChannels and DAHDI events as separate span, channel and change observations without turning an AMI response into proof of physical-circuit health.

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 · Current Asterisk logging, runtime command, logger.conf, debug-collection, call-identifier and console-verbosity documentation reviewed September 30, 2026; no process, logger, trace, storage path or call tested

Asterisk logging without permanent debug overload

Map configured destinations, console levels, call identifiers and a bounded protocol trace without leaving sensitive debug collection active.

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 PRIShowSpans, PRIDebugSet, PRIDebugFileSet, PRIDebugFileUnset, SpanAlarm and SpanAlarmClear documentation, AMI v2, event-filtering, logging and network-security guidance were reviewed October 27, 2026; installed Asterisk, libpri and DAHDI versions, chan_dahdi availability, manager permissions, spans, debug levels, file paths, signaling, timing, framing, coding, alarms, hardware and carrier facilities remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, D channel, B channel, line, circuit, configuration, manager account, credential, event stream, debug file, signaling frame, call, packet or audio was inspected or tested

Asterisk AMI PRI span is missing, down or its debug evidence is incomplete

Find the first divergence across action support, chan_dahdi and libpri state, PRI and DAHDI inventory, alarm chronology, bounded debug output and the carrier circuit.

Read guide →