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

Asterisk logging without permanent debug overload

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

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

Inventory the existing logging path first

Asterisk can send log messages to files, consoles and syslog, with destinations and message types configured in logger.conf. Record the exact running version, logger show channels output, core show settings output, log directory, syslog path where used, time source, timezone, retention owner and available storage before enabling anything new.

Root-console and remote-console verbosity are independent. Seeing more text in one attached console does not prove that a file channel contains the same records. Likewise, a configured file name does not prove that the expected message levels were enabled, storage was writable or an external collector accepted them.

Select the narrowest evidence source

Begin with normal warnings, errors and focused runtime state. A failed registration may need a short SIP exchange, an unexpected route may need dialplan execution and a media symptom may need SDP plus a separately authorized packet observation. Broad debug output is not automatically more probative. State the question, affected endpoint or trunk, test time and expected result first.

Asterisk's issue-tracker guide documents a temporary logger add channel path for Asterisk 13 and later. That runtime channel lasts until restart, logger reload or log rotation. Treat those lifecycle events as part of the capture plan; do not rotate or reload midway and then mistake a missing temporary channel for an absence of events.

Preserve levels, capture one reproduction and restore them

If PJSIP protocol logging is required, preserve the current verbose and debug levels, enable the logger immediately before one authorized reproduction and turn it off immediately afterward. The pair below is intentionally not a paste-as-one script. Restore the recorded prior levels rather than assuming zero was the site's baseline. Confirm cleanup with the installed help and runtime state.

The PJSIP logger shows SIP handled by that driver. It is not a packet capture, does not show every network drop and does not establish RTP delivery or audible media. Debug, DTMF and signaling output can be voluminous and sensitive; bound the call, duration and destination before collection.

Asterisk CLI — enable and disable around one authorized reproduction
pjsip set logger on
pjsip set logger off

Correlate identifiers without merging them

Asterisk's bracketed C-XXXXXXXX call identifier is not caller ID and is not the SIP Call-ID. It can bind logs from several channels and threads, while a transfer can create a new Asterisk call identifier and independent SIP legs can use different dialog identifiers. Preserve timestamp, Asterisk call ID, channel name, unique and linked identifiers, SIP Call-ID, CSeq and dialplan context as separate fields.

Compare a known-good control from the same logging scope. No event in one file means only that the event was not observed by that configured destination at that time. The responsible level, module, process, capture point or external collector may lie elsewhere.

Rotate, retain and share deliberately

Asterisk documents sequential, rotate and timestamp log-rotation strategies and warns that production debug output can fill files quickly. Size storage and retention before collection, monitor the actual filesystem and keep log growth from exhausting space used by voicemail, recordings or the database. logger rotate rotates and reopens files; it is a state-changing operation, not a read-only inspection.

Restrict originals, hash or otherwise identify the retained artifact, and make a redacted sharing copy. Remove credentials and authorization values while preserving method, status, sequence, time and sanitized addressing. Record the recipient, approved transfer channel and deletion date. Do not paste a full trace into a public ticket.

Close the diagnostic change

Confirm the protocol logger is off, temporary channels are removed or allowed to expire under the recorded lifecycle, console levels match the before state and storage is healthy. Preserve the original evidence before repair, then repeat the same bounded reproduction and control after the change.

No Asterisk process, logger channel, file, syslog destination, storage volume, PJSIP exchange, identifier, call, packet, credential or cleanup action was inspected or tested for this guide.

Keep the queue log outside ordinary channel assumptions

Asterisk queue events have dedicated enablement, filename and file-versus-realtime controls. Use the queue-log diagnostic when the symptom is a missing queue record rather than assuming an ordinary logger channel or a broader debug level owns it.

Apply the evidence model to a FreePBX-managed logger

On FreePBX, use the Asterisk Logfile Settings guide to keep module version, GUI intent, generated include, loaded Asterisk channels, storage and operating-system rotation separate before enabling more detail.

Capture handler-stack and teardown evidence together

For teardown failures, the hangup-handler diagnostic correlates CLI stack state, AMI push/pop/run events, handler logs and the final channel hangup without treating one log line as completion.

Log the event boundary, not just a speech label

The TALK_DETECT diagnostic correlates channel identifiers, threshold values, audiohook order, media evidence and consumer timestamps.

Correlate queue priority with entry, offers and exits

The FreePBX queue-priority diagnostic uses queue-log records with channel identity and the effective QUEUE_PRIO value rather than treating answer order as sufficient evidence.

Correlate group decisions with exact channel identity

The channel-group diagnostic records unique IDs, group lists, count reads, branch decisions and teardown instead of inferring occupancy from one call log line.

Correlate fax logs with one session ID and channel

The res_fax diagnostic keeps FAXOPT results, channel identity, signaling, media and file handling together while bounding temporary debugging and redacting document content.

Correlate quality fields without flattening call legs

The RTCP diagnostic aligns channel logs, RTCP reports, packet evidence and bridge transitions while keeping sensitive media capture bounded.

Correlate a response value with the exact SIP transaction

Use the PJSIP response-header diagnostic to retain Call-ID, INVITE CSeq, callee identity, final status, header match and instance without logging the full response by default.

Log one bounded AoR and contact lookup

The AoR/contact diagnostic records object names, contact identifiers, fields and collection time without dumping credentials or the full inventory.

Log one endpoint field with channel identity

The PJSIP endpoint diagnostic records endpoint, field, channel, direction and collection time without dumping authentication or unrestricted configuration data.

Log DTMF mode, direction and duration without sensitive digits

The runtime DTMF diagnostic correlates one channel value with bounded begin/end and protocol evidence while keeping PINs out of shared logs.

Correlate REFER, ChannelTransfer and NOTIFY without flattening states

The transfer-event diagnostic preserves Call-ID, channel, bridge, event consumer and final transfer outcome as distinct records.

Correlate handler execution with the emitted From field

The From-parameter diagnostic keeps release, module, channel, placement, write timing, packet and peer response as separate evidence.

Trace NOTIFY construction, routing, response and action separately

The PJSIP NOTIFY diagnostic aligns invocation, target, emitted request and peer response without claiming the endpoint completed an action.

Correlate the AMI action with registration events and SIP

The PJSIP action diagnostic keeps manager acceptance, outbound REGISTER, registrar response, Registry event and NextReg as separate timestamps.

Correlate inherited-header operations with the exact callee

The focused diagnostic records add, update or remove timing, child-channel creation, pre-dial execution and emitted SIP without inventing a read action.

Correlate refresh method, CSeq, SDP and media state

The focused session-refresh diagnostic preserves method support, glare, final response and post-refresh RTP as separate evidence.

Log selected names without dumping every header value

The inbound-header inventory guide preserves request identifiers and the approved value while avoiding broad logging of credentials, identity and routing fields.

Log the policy decision before PJSIPHangup terminates execution

Record the matched condition, channel and selected cause before calling PJSIPHangup(), then use the SIP trace to prove the first final response. The diagnostic avoids placing secrets or full captures in long-lived logs.

Log one redacted PJSIP channel tuple

The channel signaling guide records selector, leg, timestamp and value together, then removes temporary logging rather than retaining user, URI and address data broadly.

Correlate MessageSend status with the actual SIP transaction

Use the focused diagnostic to bind the destination expansion and application status to one MESSAGE Call-ID, CSeq, final response and endpoint result.

Use LOG_GROUP as a narrow channel selector

The LOG_GROUP guide shows how early channel assignment, replacement and clearing interact with a CLI group filter without being confused with call identifiers, log levels or files.

Keep frame filters separate from logger output

The FRAME_TRACE diagnostic checks trace selection, logger level, destination and time window before an empty console is represented as a missing event.

Log lock ownership without leaking protected state

The lock diagnostic records channel IDs, normalized lock name, result and duration while redacting sensitive shared values.

Log key identity and branch without leaking values

The AstDB diagnostic retains family, key, existence result and route while redacting sensitive stored values.

Log the evaluated instant, expression and branch

The wrong-branch diagnostic records a safe channel correlation, incident epoch, zone, exact timespec, selected target and later caller treatment without leaving broad debug enabled.

Log variable ownership without logging the value

The wrong-channel diagnostic records channel identifiers, write and read priorities, prefix form and existence separately while keeping secrets and customer values out of logs.

Preserve exception origin without exposing input

The missing-handler diagnostic captures redacted exception fields at handler entry and keeps custom reasons to an allow-listed vocabulary.

Log one evaluated result and reuse it

The dialplan lookup diagnostic records one redacted result and invocation count without repeating a potentially side-effecting function.

Keep PJSIP logger and PJSIP History distinct

The PJSIP History guide compares live protocol logging with the separate in-memory history module and its explicit off and clear lifecycle.

Keep metrics and event evidence distinct

The Prometheus metrics guide treats time-series counters and gauges as monitoring signals, not replacements for timestamped logs, SIP messages or call records.

Measure database-backed dialplan delay at the right boundary

The func_odbc diagnostic separates connection attempts, negative caching, query execution and later dialplan work without exposing credentials or rows.

Correlate write execution with transaction completion

The ODBC mutation diagnostic preserves redacted statement status, affected rows, transaction ID, completion and caller outcome without logging credentials or row data.

Log one Realtime object path without exposing its secrets

The PJSIP Realtime diagnostic retains names, timestamps, error classes and cache boundaries while redacting credentials and secret-valued columns.

Correlate periodic hook runs without permanent noise

The periodic-hook diagnostic logs hook ID, owner identity and bounded invocation timing, then removes temporary verbosity.

Log one bounded wait without retaining call payloads

The silence and noise diagnostic correlates application timing, channel identity, arguments and result while minimizing sensitive media evidence.

Correlate one bounded condition wait without logging secrets

The WaitForCondition diagnostic records expression ownership, writer timing, return status and next priority while minimizing retained data.

Log the conversion boundary without exposing caller data

The WaitUntil diagnostic correlates civil-time input, explicit zone and format, epoch, channel, timestamps, immediate status and next priority.

Log one Dial invocation as a bounded event timeline

The Dial diagnostic correlates loaded arguments, channel creation, signaling, answer, bridge, hangup, status and next priority without exposing credentials.

Log one Originate as a bounded multi-stage timeline

The Originate diagnostic correlates loaded arguments, wait mode, created channel, answer, destination entry, later Dial and workflow result.

Log Bridge as two channel lifecycles

The Bridge diagnostic correlates exact target resolution, answer, entry, leave, hangup, result and media.

Log holding roles and add operations as channel lifecycles

The BridgeWait and BridgeAdd diagnostic correlates handles, roles, membership, removal and results.

Log AMI bridge requests, snapshots and events as one chronology

The wrong-membership diagnostic correlates manager, bridge and channel identities.

Log the complete AMI transfer chronology

The AMI transfer diagnostic joins action, channel, bridge, dialplan and outcome evidence.

Log attended-transfer cancellation as a chronology

The CancelAtxfer diagnostic correlates action, feature configuration, channels, bridges, callbacks and media.

Log Local optimization as an event chronology

The Local optimization diagnostic correlates action, Begin, End, bridge changes and final media.

Log AMI list boundaries and counts

The channel snapshot diagnostic records each request, row, terminal event and lifecycle change.

Log AMI mask, filter and reconnect state

The AMI event diagnostic builds a raw-to-stored event chronology.

Log the producer, schema and correlation key

The UserEvent diagnostic compares producer logs, raw AMI frames, parsing and idempotent storage.

Log remote device-state ownership and list boundaries

The AMI device-state diagnostic preserves entity ID, cache intent, action response, raw rows and completion before comparing downstream state.

Log presence ownership without oversharing messages

The AMI presence-state diagnostic retains the provider, writer, boundaries and timestamps while minimizing personal subtype and message data.

Log extension state with its context and raw status

The AMI extension-state diagnostic retains Exten, Context, Hint, numeric status, status text and completion evidence.

Log the complete dialplan mutation key

The AMI dialplan diagnostic retains ActionID, context, extension, caller-ID suffix, priority, application, data and Replace intent.

Correlate configuration write and reload separately

The AMI configuration diagnostic retains ActionID, ordered operations, reload request, module log and loaded-state evidence.

Correlate module actions with registration logs

The module capability diagnostic uses load, dependency, parser and registration evidence to find the first divergence.

Correlate AMI requests without overreading message text

The AMI missing-action diagnostic retains ActionID, response, optional Message and registration logs without treating prose as a stable error taxonomy.

Correlate manager sessions without logging credentials

The AMI login diagnostic records session identity, ActionID, response and termination while redacting secret material.

Correlate core snapshots without logging secrets

The core-query diagnostic records node, session, ActionID and raw response while keeping credentials out of logs.

Correlate queue snapshots without recording credentials

The queue-snapshot diagnostic preserves node, session, filters, ActionID and completion while redacting caller and credential data.

Log mailbox query identity without exposing message or credential data

The mailbox-query diagnostic preserves node, session, ActionID, mailbox context and raw fields while requiring redaction.

Retain list framing without publishing user data

The voicemail-user diagnostic preserves action boundaries while requiring redaction.

Retain completed ConfBridge list transactions

The ConfBridge list diagnostic preserves the response, every row, completion event, ActionID and timestamps.

Audit the complete ConfBridge control transaction

The ConfBridge control diagnostic retains operator intent, exact target, response, events and bounded before-and-after snapshots.

Retain raw ConfBridge event intervals and connection gaps

The ConfBridge event diagnostic records filters, reconnects, identities, receipt times and effective talk-detection profile.

Capture profile resolution, digit receipt and application return

The ConfBridge menu diagnostic records bounded channel evidence without enabling permanent DTMF or media debugging.

Audit the AMI recording transaction and artifact lifecycle

The AMI recording diagnostic retains request, response, events and bounded filesystem evidence while redacting credentials and audio content.

Log the parking lifecycle without collapsing outcomes

The AMI parking diagnostic correlates request, assigned slot, terminal reason, retriever and media outcome while redacting personal data.

Log queue-member scope and state dimensions separately

The AMI queue-member diagnostic preserves interface, state interface, pause, penalty, status, in-call and wrap-up evidence.

Log queue control scope and postconditions separately

The AMI queue reload or reset diagnostic preserves action, source, parser, snapshot, statistic and history evidence.

Log queue caller request and postconditions separately

The queue caller-control diagnostic retains action, snapshot, lifecycle, dialplan and historical evidence.

Trace a QueueLog request into the exact active destination

The AMI QueueLog guide distinguishes active and rotated files, alternate backends, parser checkpoints and reports.

Route security events through their dedicated dynamic level

Use the security-event logging guide to separate event generation, res_security_log, the SECURITY level, channel configuration, file custody and downstream consumers.

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 22 LTS

Asterisk dialplan: contexts, patterns and loaded-call evidence

Build a restricted Asterisk 22 call path, then prove its context, match, priorities and runtime behavior separately.

Read guide →
Guide · Current Asterisk CLI, PJSIP troubleshooting, call-identifier and console-verbosity documentation reviewed September 30, 2026; no host, CLI, module, object, channel or call tested

Asterisk CLI: inspect the running system

Establish the exact running instance, loaded modules, PJSIP object graph and live call state before using a command that changes service.

Read guide →
Guide · Current Asterisk 23 ARI logging API and REST data model plus Asterisk logging configuration, runtime-command, debug-collection and call-identifier guidance reviewed October 10, 2026; no Asterisk host, ARI identity, logger channel, logger.conf, file, filesystem, syslog target, collector, trace, credential, call or cleanup action was inspected or tested

Asterisk ARI logging channels: inventory, bounded capture and rotation

Use ARI to inventory and control one approved logging channel while keeping runtime state, logger.conf, file output, retention and evidence handling independently verifiable.

Read guide →
Troubleshooting guide · Current Asterisk 23 ARI logging API and REST data model plus Asterisk logging configuration, runtime-command, debug-collection and call-identifier guidance reviewed October 10, 2026; no Asterisk host, ARI identity, logger channel, logger.conf, file, filesystem, syslog target, collector, trace, credential, call or cleanup action was inspected or tested

Asterisk ARI log channel is missing, silent or will not rotate

Trace one logging channel through instance identity, ARI inventory, level configuration, runtime lifecycle, destination write, event generation, rotation and downstream collection.

Read guide →
Guide

Protecting PBX backups

Treat recovery files as sensitive assets containing more than route names.

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 →
Troubleshooting · Current Asterisk queue-log, logging-configuration and main-configuration documentation plus Asterisk 22 Queue, QueueLog and QUEUE_VARIABLES references and the Certified Asterisk 22.8 QueueLog AMI reference reviewed October 11, 2026; installed version, module state, effective configuration, log directory, file or realtime backend, permissions, rotation, clock, queue, call, custom event and consumer require local evidence, and no PBX, logger, queue, file, realtime backend, database, importer, report, packet, audio or live call was inspected or tested

Asterisk queue log is missing, incomplete or attributed to the wrong call

Trace one queued call from Queue entry through logger policy, file or realtime storage, event identity, rotation and downstream import before changing queue behavior.

Read guide →
Guide · FreePBX Asterisk Logfiles release/17.0 repository and security advisory, Sangoma module indexes and retention note, and current Asterisk logging documentation reviewed October 12, 2026; repository and advisory state do not prove the installed module version or patch state, the Sangoma retention note describes an older FreePBX Distro path rather than the FreePBX 17 Debian 12 baseline, and no PBX, module, file, logger channel, disk, rotation job, call or captured event was inspected or tested

FreePBX Asterisk Logfile Settings: generated channels, runtime and retention

Separate the installed Logfiles module, saved rows, generated logger configuration, loaded Asterisk channels, actual writes, rotation owner and retained evidence.

Read guide →
Guide · Asterisk hangup-handler, CHANNEL, AMI event, hangup-cause and Return documentation reviewed October 12, 2026; exact events and channel behavior remain dependent on the installed Asterisk branch, modules, dialplan, channel technology and observer permissions, and no PBX, dialplan, channel, handler stack, event, record, endpoint, call or teardown path was inspected or tested

Asterisk hangup handlers: channel stack, order and teardown evidence

Attach bounded hangup subroutines to the correct channel, preserve LIFO stack order and prove push, pop, run and final hangup separately.

Read guide →
Troubleshooting · Asterisk hangup-handler, CHANNEL, AMI event, hangup-cause and Return documentation reviewed October 12, 2026; exact events and channel behavior remain dependent on the installed Asterisk branch, modules, dialplan, channel technology and observer permissions, and no PBX, dialplan, channel, handler stack, event, record, endpoint, call or teardown path was inspected or tested

Asterisk hangup handler is missing, duplicated, out of order or slow

Trace one channel from handler push and stack order through invocation, Return, teardown timing, final cause and downstream record.

Read guide →
Guide · Asterisk 22 TALK_DETECT, DENOISE, AMI ChannelTalkingStart and ChannelTalkingStop, and ARI data-model documentation reviewed October 12, 2026; behavior remains channel-, media-, audiohook-order-, threshold-, module-, application-subscription- and branch-specific, and no PBX, module, channel, bridge, audiohook, RTP flow, AMI or ARI session, event stream, recording, endpoint or call was inspected or tested

Asterisk TALK_DETECT: channel scope, thresholds and event evidence

Attach talk detection to the intended channel, keep silence time separate from signal magnitude, order audiohooks deliberately and interpret AMI or ARI events within their documented scope.

Read guide →
Troubleshooting · Asterisk 22 TALK_DETECT, DENOISE, AMI ChannelTalkingStart and ChannelTalkingStop, and ARI data-model documentation reviewed October 12, 2026; behavior remains channel-, media-, audiohook-order-, threshold-, module-, application-subscription- and branch-specific, and no PBX, module, channel, bridge, audiohook, RTP flow, AMI or ARI session, event stream, recording, endpoint or call was inspected or tested

Asterisk TALK_DETECT events are missing, early or late

Trace one channel from detector attachment and media frames through threshold crossings, audiohook order and the selected AMI or ARI consumer before tuning.

Read guide →
Guide · Sangoma Queue Priorities overview and PBX GUI 13 user guide, FreePBX Queue Priorities release/17.0 repository metadata and Queueprio.class.php dialplan source, and current Asterisk QUEUE_PRIO and Queue application documentation reviewed October 12, 2026; the Sangoma screen guide is explicitly version 13, repository state does not prove an installed module or loaded channel state, and no PBX, module, priority object, route, queue, caller, member, channel variable, queue log, SLA result or call was inspected or tested

FreePBX Queue Priorities: caller weight, channel scope and queue order

Assign a documented queue priority to the intended caller path, preserve it across the configured destination chain and distinguish caller ordering from agent penalty, staffing, service level and answer outcome.

Read guide →
Troubleshooting · Sangoma Queue Priorities overview and PBX GUI 13 user guide, FreePBX Queue Priorities release/17.0 repository metadata and Queueprio.class.php dialplan source, and current Asterisk QUEUE_PRIO and Queue application documentation reviewed October 12, 2026; the Sangoma screen guide is explicitly version 13, repository state does not prove an installed module or loaded channel state, and no PBX, module, priority object, route, queue, caller, member, channel variable, queue log, SLA result or call was inspected or tested

FreePBX queue priority is not applied or callers answer in the wrong order

Trace one caller from its selecting route through the generated priority target, inherited QUEUE_PRIO value, queue admission, comparable waiters, member offers and queue outcome before changing weights or penalties.

Read guide →
Guide · Asterisk Latest API GROUP, GROUP_COUNT, GROUP_LIST and GROUP_MATCH_COUNT references generated from branch 23, channel architecture, variable-inheritance and Local-channel optimization documentation reviewed October 12, 2026; a group count is local channel state rather than a provider entitlement or complete call count, and no PBX, dialplan, group, channel, bridge, trunk, account, call, limit or denial was inspected or tested

Asterisk channel groups: counting concurrency without counting calls twice

Assign channels to explicit group and category names, interpret counts against the chosen call leg and lifecycle, and keep a local dialplan guard separate from trunk entitlement or platform capacity.

Read guide →
Troubleshooting · Asterisk Latest API GROUP, GROUP_COUNT, GROUP_LIST and GROUP_MATCH_COUNT references generated from branch 23, channel architecture, variable-inheritance and Local-channel optimization documentation reviewed October 12, 2026; a group count is local channel state rather than a provider entitlement or complete call count, and no PBX, dialplan, group, channel, bridge, trunk, account, call, limit or denial was inspected or tested

Asterisk channel-group count is wrong or a call limit is bypassed

Trace one admission decision through the selected channel, exact group and category, count timing, created legs, Local-channel optimization, transfer and teardown before changing a threshold.

Read guide →
Guide · Asterisk 22 FAXOPT, ReceiveFAX and SendFAX documentation plus branch 22 res_fax configuration and implementation reviewed October 13, 2026; the installed Asterisk version, res_fax module, technology resource, configuration, channel, TIFF/F file, signaling, T.38 negotiation, audio path, session result, storage and delivery remain deployment specific, and no host, module, file, channel, packet, fax session or document was inspected or tested

Asterisk res_fax: session options, mode and result evidence

Keep the generic res_fax layer, loaded technology resource, per-session FAXOPT policy, TIFF/F file, audio or T.38 mode and final transmission result independently observable.

Read guide →
Troubleshooting · Asterisk 22 FAXOPT, ReceiveFAX and SendFAX documentation plus branch 22 res_fax configuration and implementation reviewed October 13, 2026; the installed Asterisk version, res_fax module, technology resource, configuration, channel, TIFF/F file, signaling, T.38 negotiation, audio path, session result, storage and delivery remain deployment specific, and no host, module, file, channel, packet, fax session or document was inspected or tested

Asterisk ReceiveFAX or SendFAX fails or uses the wrong mode

Trace one fax from the exact channel and loaded res_fax stack through FAXOPT inputs, file access, audio or T.38 negotiation, application result and downstream artifact handling.

Read guide →
Guide · Asterisk 22 CHANNEL documentation plus current Asterisk Media Experience Score, bridge and PJSIP direct-media documentation reviewed October 13, 2026; installed version, channel driver, bridge technology, media topology, RTCP availability, endpoint reports, counters, timing, codec, network path and user experience remain deployment specific, and no PBX, channel, RTP or RTCP stream, packet capture, endpoint, network path, call or audible result was inspected or tested

Asterisk RTCP statistics: channel, direction and call-quality evidence

Read PJSIP CHANNEL(rtcp,...) values as channel-scoped RTP and RTCP observations, not an end-to-end MOS or a complete explanation of what either participant heard.

Read guide →
Troubleshooting · Asterisk 22 CHANNEL documentation plus current Asterisk Media Experience Score, bridge and PJSIP direct-media documentation reviewed October 13, 2026; installed version, channel driver, bridge technology, media topology, RTCP availability, endpoint reports, counters, timing, codec, network path and user experience remain deployment specific, and no PBX, channel, RTP or RTCP stream, packet capture, endpoint, network path, call or audible result was inspected or tested

Asterisk RTCP statistics are empty or do not match call quality

Trace the exact PJSIP channel, media stream, collection time, RTCP reporter, bridge topology and audible symptom before treating an empty or surprising value as a network verdict.

Read guide →
Guide · Current Asterisk PJSIP_RESPONSE_HEADER, PJSIP_RESPONSE_HEADERS, pre-bridge-handler and Dial documentation plus the project source implementation reviewed October 13, 2026; the functions are documented from Asterisk 16.28.0, 18.14.0 and 19.6.0, and installed branch, maintenance release, channel topology, peer response, header set, dialplan and consumer policy remain deployment specific; no PBX, module, dialplan, channel, request, response, header, endpoint, provider, bridge or call was inspected or tested

Asterisk PJSIP response headers: channel, answer and pre-bridge timing

Read named headers from the answered outbound INVITE response on the callee PJSIP channel without confusing request headers, provisional responses or caller state.

Read guide →
Troubleshooting · Current Asterisk PJSIP_RESPONSE_HEADER, PJSIP_RESPONSE_HEADERS, pre-bridge-handler and Dial documentation plus the project source implementation reviewed October 13, 2026; the functions are documented from Asterisk 16.28.0, 18.14.0 and 19.6.0, and installed branch, maintenance release, channel topology, peer response, header set, dialplan and consumer policy remain deployment specific; no PBX, module, dialplan, channel, request, response, header, endpoint, provider, bridge or call was inspected or tested

Asterisk PJSIP response header is empty or from the wrong response

Trace the exact answered outbound INVITE, PJSIP callee channel, pre-bridge handler, header match and instance before changing request headers or copying caller state.

Read guide →
Guide · Current Asterisk PJSIP_AOR, PJSIP_CONTACT and PJSIP_DIAL_CONTACTS function documentation plus PJSIP object-relationship and troubleshooting guidance reviewed October 13, 2026; both inspection functions are documented since Asterisk 13.2.0, while installed branch, maintenance release, loaded modules, configuration source, object names, registrations, contacts, qualification state, timing and routing remain deployment specific; no PBX, module, configuration, endpoint, AoR, contact, registration, OPTIONS exchange, packet, channel or call was inspected or tested

Asterisk PJSIP AoR and contact inspection: identity, fields and runtime evidence

Read one Address of Record and its current contact objects without confusing endpoint configuration, registration, qualification or a generated dial string.

Read guide →
Troubleshooting · Current Asterisk PJSIP_AOR, PJSIP_CONTACT and PJSIP_DIAL_CONTACTS function documentation plus PJSIP object-relationship and troubleshooting guidance reviewed October 13, 2026; both inspection functions are documented since Asterisk 13.2.0, while installed branch, maintenance release, loaded modules, configuration source, object names, registrations, contacts, qualification state, timing and routing remain deployment specific; no PBX, module, configuration, endpoint, AoR, contact, registration, OPTIONS exchange, packet, channel or call was inspected or tested

Asterisk PJSIP AoR or contact lookup is empty, stale or wrong

Trace the exact endpoint, AoR name, returned contact identifier, lifecycle and queried field before changing registration, qualification or dial logic.

Read guide →
Guide · Current Asterisk PJSIP_ENDPOINT and CHANNEL function documentation, res_pjsip endpoint configuration reference, object-relationship guidance and PJSIP troubleshooting guidance reviewed October 13, 2026; PJSIP_ENDPOINT is documented since Asterisk 12.0.0, while installed branch, maintenance release, loaded modules, configuration backend, object names, defaults, endpoint identification, channel association, contacts, signaling and media remain deployment specific; no PBX, module, configuration, endpoint, identify object, channel, SIP exchange, packet or call was inspected or tested

Asterisk PJSIP endpoint inspection: configuration fields, channel identity and proof

Read one loaded endpoint field without confusing configuration, inbound endpoint identification, AoR location, a live channel or negotiated SIP and media state.

Read guide →
Troubleshooting · Current Asterisk PJSIP_ENDPOINT and CHANNEL function documentation, res_pjsip endpoint configuration reference, object-relationship guidance and PJSIP troubleshooting guidance reviewed October 13, 2026; PJSIP_ENDPOINT is documented since Asterisk 12.0.0, while installed branch, maintenance release, loaded modules, configuration backend, object names, defaults, endpoint identification, channel association, contacts, signaling and media remain deployment specific; no PBX, module, configuration, endpoint, identify object, channel, SIP exchange, packet or call was inspected or tested

Asterisk PJSIP endpoint lookup is empty, missing or shows the wrong field

Trace the function, exact endpoint name, loaded object, current channel association, default resolution and consuming decision before changing SIP policy.

Read guide →
Guide · Current Asterisk PJSIP_DTMF_MODE, PJSIP_ENDPOINT, CHANNEL, Dial, res_pjsip and AMI DTMF event documentation reviewed October 13, 2026; PJSIP_DTMF_MODE is documented since Asterisk 13.18.0, 14.7.0 and 15.1.0, while installed branch, maintenance release, loaded channel driver, endpoint configuration, channel ownership, negotiated SDP, received and transmitted digits, downstream IVR behavior and media remain deployment specific; no PBX, endpoint, channel, dialplan, SIP message, RTP event, audio stream, digit or call was inspected or tested

Asterisk PJSIP_DTMF_MODE: channel override, signaling method and proof

Read or change the DTMF mode on one PJSIP call leg without confusing endpoint policy, channel ownership, advertised telephone events or a downstream IVR result.

Read guide →
Troubleshooting · Current Asterisk PJSIP_DTMF_MODE, PJSIP_ENDPOINT, CHANNEL, Dial, res_pjsip and AMI DTMF event documentation reviewed October 13, 2026; PJSIP_DTMF_MODE is documented since Asterisk 13.18.0, 14.7.0 and 15.1.0, while installed branch, maintenance release, loaded channel driver, endpoint configuration, channel ownership, negotiated SDP, received and transmitted digits, downstream IVR behavior and media remain deployment specific; no PBX, endpoint, channel, dialplan, SIP message, RTP event, audio stream, digit or call was inspected or tested

Asterisk PJSIP DTMF mode override is ignored or digits still fail

Trace function availability, channel ownership, endpoint policy, selected mode, protocol evidence, digit direction and the final consumer before changing codecs or global settings.

Read guide →
Guide · Current Asterisk PJSIP_TRANSFER_HANDLING, ARI transfer handling, ChannelTransfer data-model, res_pjsip endpoint, remote attended-transfer and CHANNEL documentation reviewed October 13, 2026; PJSIP_TRANSFER_HANDLING is documented since Asterisk 20.13.0, 21.8.0 and 22.3.0, while installed branch, maintenance release, loaded modules, endpoint allow_transfer policy, channel ownership, ARI subscription, SIP dialog correlation, application actions, peer behavior and transfer result remain deployment specific; no PBX, endpoint, channel, bridge, ARI client, event, REFER, NOTIFY, INVITE, packet or transfer was inspected or tested

Asterisk PJSIP_TRANSFER_HANDLING: core versus ARI-owned REFER transfers

Choose who owns one incoming SIP REFER without confusing endpoint permission, event delivery, application action, dialog correlation or the final transfer result.

Read guide →
Troubleshooting · Current Asterisk PJSIP_TRANSFER_HANDLING, ARI transfer handling, ChannelTransfer data-model, res_pjsip endpoint, remote attended-transfer and CHANNEL documentation reviewed October 13, 2026; PJSIP_TRANSFER_HANDLING is documented since Asterisk 20.13.0, 21.8.0 and 22.3.0, while installed branch, maintenance release, loaded modules, endpoint allow_transfer policy, channel ownership, ARI subscription, SIP dialog correlation, application actions, peer behavior and transfer result remain deployment specific; no PBX, endpoint, channel, bridge, ARI client, event, REFER, NOTIFY, INVITE, packet or transfer was inspected or tested

Asterisk PJSIP transfer event is missing or the transfer stalls

Trace release support, endpoint permission, channel timing, ARI subscription, REFER correlation, application action, NOTIFY progress and the final bridge before changing global transfer policy.

Read guide →
Guide · Current Asterisk PJSIP_HEADER_PARAM, PJSIP_HEADER, PJSIP_PARSE_URI_FROM, CHANNEL, Dial and pre-dial-handler documentation plus RFC 3261 reviewed October 13, 2026; PJSIP_HEADER_PARAM is documented since Asterisk 18.16.0 and 20.1.0 and currently supports only the From header, while installed release, loaded module, dialplan owner, channel leg, parameter contract, endpoint policy, upstream rewriting and emitted SIP remain deployment specific; no PBX, module, endpoint, trunk, dialplan, channel, request, response, packet or call was inspected or tested

Asterisk PJSIP_HEADER_PARAM: From URI and header parameter boundaries

Read or set one documented From parameter on the correct PJSIP channel without confusing URI placement, header placement, caller identity, carrier policy or emitted SIP.

Read guide →
Troubleshooting · Current Asterisk PJSIP_HEADER_PARAM, PJSIP_HEADER, PJSIP_PARSE_URI_FROM, CHANNEL, Dial and pre-dial-handler documentation plus RFC 3261 reviewed October 13, 2026; PJSIP_HEADER_PARAM is documented since Asterisk 18.16.0 and 20.1.0 and currently supports only the From header, while installed release, loaded module, dialplan owner, channel leg, parameter contract, endpoint policy, upstream rewriting and emitted SIP remain deployment specific; no PBX, module, endpoint, trunk, dialplan, channel, request, response, packet or call was inspected or tested

Asterisk PJSIP From parameter is empty, misplaced or absent

Trace release support, parameter type, channel ownership, pre-dial timing, emitted From syntax and intermediary rewriting before replacing a complete SIP header.

Read guide →
Guide · Current Asterisk branch-23 PJSIPNotify dialplan, AMI, res_pjsip_notify and res_pjsip configuration documentation, the October 9, 2024 Asterisk feature introduction, and RFC 6665 reviewed October 13, 2026; the dialplan application is documented since Asterisk 18.25.0, 20.10.0 and 21.5.0, while installed maintenance release, loaded module, endpoint and contact state, default outbound endpoint, configured notify type, vendor event contract, authorization, request routing, response and endpoint action remain deployment specific; no PBX, module, endpoint, contact, phone, URI, dialog, NOTIFY, response, packet, reboot, resync or call was inspected or tested

Asterisk PJSIP NOTIFY: endpoint, URI and in-dialog boundaries

Send one documented NOTIFY through CLI, AMI or dialplan without confusing a configured message, target selection, SIP acceptance or an endpoint action.

Read guide →
Troubleshooting · Current Asterisk branch-23 PJSIPNotify dialplan, AMI, res_pjsip_notify and res_pjsip configuration documentation, the October 9, 2024 Asterisk feature introduction, and RFC 6665 reviewed October 13, 2026; the dialplan application is documented since Asterisk 18.25.0, 20.10.0 and 21.5.0, while installed maintenance release, loaded module, endpoint and contact state, default outbound endpoint, configured notify type, vendor event contract, authorization, request routing, response and endpoint action remain deployment specific; no PBX, module, endpoint, contact, phone, URI, dialog, NOTIFY, response, packet, reboot, resync or call was inspected or tested

Asterisk PJSIP NOTIFY is not sent, is rejected or is ignored

Trace feature availability, notify content, target mode, loaded endpoint state, request routing, SIP response and endpoint action before changing a global PJSIP endpoint.

Read guide →
Guide · Current Asterisk branch-23 PJSIPRegister, PJSIPUnregister, PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, Registry and res_pjsip_outbound_registration documentation plus the outbound-registration configuration guide reviewed October 13, 2026; PJSIPUnregister is documented since Asterisk 12.0.0 and PJSIPRegister since 13.2.0, while installed release, loaded module, registration object, AMI identity and permissions, persistent configuration, timer state, network path, registrar response and service behavior remain deployment specific; no PBX, AMI session, credential, registration object, REGISTER, response, timer, provider, trunk, packet or call was inspected or tested

Asterisk PJSIPRegister and PJSIPUnregister: runtime registration control

Start or stop one loaded outbound-registration object through AMI without confusing an accepted action, unregister transaction, future retry schedule, provider binding or call readiness.

Read guide →
Troubleshooting · Current Asterisk branch-23 PJSIPRegister, PJSIPUnregister, PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, Registry and res_pjsip_outbound_registration documentation plus the outbound-registration configuration guide reviewed October 13, 2026; PJSIPUnregister is documented since Asterisk 12.0.0 and PJSIPRegister since 13.2.0, while installed release, loaded module, registration object, AMI identity and permissions, persistent configuration, timer state, network path, registrar response and service behavior remain deployment specific; no PBX, AMI session, credential, registration object, REGISTER, response, timer, provider, trunk, packet or call was inspected or tested

Asterisk PJSIPRegister or PJSIPUnregister action fails or has no effect

Trace AMI authorization, loaded object identity, action response, REGISTER exchange, Registry event, detail status and later timer before repeating a fleet-wide control.

Read guide →
Guide · Current Asterisk PJSIP_INHERITABLE_HEADER, PJSIP_HEADER, Dial and pre-dial-handler documentation reviewed October 14, 2026; the inheritable function is documented since Asterisk 20.19.0, 22.9.0 and 23.3.0, is absent from the documented Asterisk 21 function set, and exposes add, update and remove rather than a read action; installed release, loaded module, dialplan owner, channel graph, generated request, intermediary policy and peer acceptance remain deployment specific, and no PBX, module, dialplan, channel, endpoint, header, request, response, packet or call was inspected or tested

Asterisk PJSIP_INHERITABLE_HEADER: channel inheritance and outbound SIP evidence

Add one controlled SIP header on a calling channel, follow it to each outbound PJSIP child, and keep inheritance, callee-specific mutation, emitted signaling and peer acceptance separate.

Read guide →
Troubleshooting · Current Asterisk PJSIP_INHERITABLE_HEADER, PJSIP_HEADER, Dial and pre-dial-handler documentation reviewed October 14, 2026; the inheritable function is documented since Asterisk 20.19.0, 22.9.0 and 23.3.0, is absent from the documented Asterisk 21 function set, and exposes add, update and remove rather than a read action; installed release, loaded module, dialplan owner, channel graph, generated request, intermediary policy and peer acceptance remain deployment specific, and no PBX, module, dialplan, channel, endpoint, header, request, response, packet or call was inspected or tested

Asterisk inheritable PJSIP header is missing, duplicated or wrong

Trace branch support, source-channel state, callee creation, per-leg pre-dial mutation, the emitted request and intermediary handling before adding another header copy.

Read guide →
Guide · Current Asterisk PJSIP_SEND_SESSION_REFRESH, PJSIP_MEDIA_OFFER and CHANNEL documentation plus RFC 3261, RFC 3311 and RFC 3264 reviewed October 14, 2026; the write-only refresh function is documented since Asterisk 13.12.0 and 14.1.0 and can request re-INVITE or UPDATE on an established media session, but installed module state, channel ownership, peer method support, offer and answer, response handling, RTP path and audible result remain deployment specific, and no PBX, module, endpoint, channel, dialog, request, response, SDP body, RTP stream, packet or call was inspected or tested

Asterisk PJSIP_SEND_SESSION_REFRESH: re-INVITE, UPDATE and media evidence

Initiate one controlled in-dialog media refresh, distinguish re-INVITE from UPDATE, and prove the offer, answer, negotiated state and resulting RTP instead of treating a sent request as success.

Read guide →
Troubleshooting · Current Asterisk PJSIP_SEND_SESSION_REFRESH, PJSIP_MEDIA_OFFER and CHANNEL documentation plus RFC 3261, RFC 3311 and RFC 3264 reviewed October 14, 2026; the write-only refresh function is documented since Asterisk 13.12.0 and 14.1.0 and can request re-INVITE or UPDATE on an established media session, but installed module state, channel ownership, peer method support, offer and answer, response handling, RTP path and audible result remain deployment specific, and no PBX, module, endpoint, channel, dialog, request, response, SDP body, RTP stream, packet or call was inspected or tested

Asterisk PJSIP session refresh is rejected or media is lost

Trace the exact channel, method, outstanding offer, request and response SDP, negotiated formats and post-refresh RTP before retrying or changing endpoint policy.

Read guide →
Guide · Current Asterisk PJSIP_HEADERS and PJSIP_HEADER documentation, Asterisk project source and RFC 3261 reviewed October 13, 2026; PJSIP_HEADERS is documented from Asterisk 16.20.0 and 18.6.0, and installed branch, maintenance release, module, channel topology, request, header set, endpoint policy and dialplan remain deployment specific; no PBX, module, dialplan, channel, request, header, endpoint, provider, packet or call was inspected or tested

Asterisk PJSIP inbound header inventory: names, prefixes and instances

Enumerate unique header names from the current INVITE, then read the intended value and repeated instance without treating a name list as a packet capture.

Read guide →
Troubleshooting · Current Asterisk PJSIP_HEADERS and PJSIP_HEADER documentation, Asterisk project source and RFC 3261 reviewed October 13, 2026; PJSIP_HEADERS is documented from Asterisk 16.20.0 and 18.6.0, and installed branch, maintenance release, module, channel topology, request, header set, endpoint policy and dialplan remain deployment specific; no PBX, module, dialplan, channel, request, header, endpoint, provider, packet or call was inspected or tested

Asterisk PJSIP header list is empty, incomplete or misleading

Trace function availability, INVITE scope, current channel, prefix, unique-name behavior and repeated instances before changing endpoint trust or outbound headers.

Read guide →
Guide · Current Asterisk branch 23 PJSIPHangup and Hangup application documentation, hangup-cause inspection and mapping guidance, and RFC 3261 reviewed October 14, 2026; PJSIPHangup is documented since Asterisk 18.21.0, 20.6.0 and 21.1.0, accepts a numeric 400 through 699 response or supported PJSIP response name, must run on an incoming PJSIP channel before any other final response, terminates dialplan execution and maps the selected SIP response into an Asterisk or ISDN cause, while installed release, loaded channel driver, channel direction, prior provisional or final responses, transaction state, mapping, upstream rewriting and caller behavior remain deployment specific; no PBX, module, dialplan, channel, request, response, cause, packet, endpoint, trunk or call was inspected or tested

Asterisk PJSIPHangup: return one final SIP response safely

Place one explicit 4xx, 5xx or 6xx final response on the incoming PJSIP transaction before answer, then keep SIP, translated cause and caller outcome separate.

Read guide →
Diagnostic · Current Asterisk branch 23 PJSIPHangup and Hangup application documentation, hangup-cause inspection and mapping guidance, and RFC 3261 reviewed October 14, 2026; PJSIPHangup is documented since Asterisk 18.21.0, 20.6.0 and 21.1.0, accepts a numeric 400 through 699 response or supported PJSIP response name, must run on an incoming PJSIP channel before any other final response, terminates dialplan execution and maps the selected SIP response into an Asterisk or ISDN cause, while installed release, loaded channel driver, channel direction, prior provisional or final responses, transaction state, mapping, upstream rewriting and caller behavior remain deployment specific; no PBX, module, dialplan, channel, request, response, cause, packet, endpoint, trunk or call was inspected or tested

Asterisk PJSIPHangup returns the wrong response or 200 was already sent

Find the first final SIP response, prove the current channel and application availability, then correct one policy or timing owner without rewriting evidence after answer.

Read guide →
Guide · Current Asterisk branch 23 CHANNEL, PJSIP_ENDPOINT, PJSIP_PARSE_URI and pre-dial-handler documentation plus RFC 3261 reviewed October 14, 2026; CHANNEL(pjsip,...) exposes signaling data for the exact current PJSIP channel, while installed release, loaded modules, caller or callee leg, dialog state, endpoint association, transport object, intermediary rewriting and packet evidence remain deployment specific; no PBX, module, configuration, endpoint, channel, dialog, URI, address, transport, packet or call was inspected or tested

Asterisk PJSIP channel signaling context: URI, tag and socket evidence

Read one PJSIP call leg without confusing its Call-ID, local and remote dialog identity, target, original inbound Request-URI, transport security, socket addresses or endpoint object.

Read guide →
Diagnostic · Current Asterisk branch 23 CHANNEL, PJSIP_ENDPOINT, PJSIP_PARSE_URI and pre-dial-handler documentation plus RFC 3261 reviewed October 14, 2026; CHANNEL(pjsip,...) exposes signaling data for the exact current PJSIP channel, while installed release, loaded modules, caller or callee leg, dialog state, endpoint association, transport object, intermediary rewriting and packet evidence remain deployment specific; no PBX, module, configuration, endpoint, channel, dialog, URI, address, transport, packet or call was inspected or tested

Asterisk PJSIP channel URI or address is empty or wrong

Prove technology, channel leg, read timing and selector meaning before treating a blank or unexpected URI, tag, Call-ID, security flag or socket address as a SIP failure.

Read guide →
Guide · Current Asterisk MessageSend, MESSAGE, MESSAGE_DATA and res_pjsip documentation plus RFC 3428 reviewed October 14, 2026; the APIs have been documented since Asterisk 10.0.0 and the endpoint message_context option since 13.5.0, but installed modules, endpoint and contact state, URI construction, authentication, peer method support, SIP transaction result, endpoint display and user receipt remain deployment specific, and no PBX, module, endpoint, AoR, contact, dialplan, header, body, request, response, packet, device, user interface or message was inspected or tested

Asterisk PJSIP MessageSend: Request-URI, headers and delivery evidence

Build one SIP MESSAGE deliberately, keep its Request-URI separate from To and From identity, and prove the protocol response without treating handler acceptance as user receipt.

Read guide →
Troubleshooting · Current Asterisk MessageSend, MESSAGE, MESSAGE_DATA and res_pjsip documentation plus RFC 3428 reviewed October 14, 2026; the APIs have been documented since Asterisk 10.0.0 and the endpoint message_context option since 13.5.0, but installed modules, endpoint and contact state, URI construction, authentication, peer method support, SIP transaction result, endpoint display and user receipt remain deployment specific, and no PBX, module, endpoint, AoR, contact, dialplan, header, body, request, response, packet, device, user interface or message was inspected or tested

Asterisk PJSIP MessageSend fails or uses the wrong URI

Trace one text message from the Asterisk message object through destination parsing, endpoint and contact selection, SIP request, response and endpoint presentation.

Read guide →
Guide · Asterisk Latest API branch 23 and Asterisk 22 LOG_GROUP documentation plus current Asterisk logging, CLI, call-identifier and debug-collection guidance reviewed October 14, 2026; LOG_GROUP is documented since 18.21.0, 20.6.0 and 21.1.0, but installed-version availability, active logger filters, console verbosity, logger destinations, channel creation, group assignment, protocol traces and captured output remain deployment specific, and no PBX, module, console, channel, dialplan, group, filter, log file, packet or call was inspected or tested

Asterisk LOG_GROUP: channel-scoped CLI filtering without losing evidence

Assign one channel to a named log-filter group, keep filter state separate from log generation and preserve call, channel and protocol evidence outside the filtered console view.

Read guide →
Troubleshooting · Asterisk Latest API branch 23 and Asterisk 22 LOG_GROUP documentation plus current Asterisk logging, CLI, call-identifier and debug-collection guidance reviewed October 14, 2026; LOG_GROUP is documented since 18.21.0, 20.6.0 and 21.1.0, but installed-version availability, active logger filters, console verbosity, logger destinations, channel creation, group assignment, protocol traces and captured output remain deployment specific, and no PBX, module, console, channel, dialplan, group, filter, log file, packet or call was inspected or tested

Asterisk LOG_GROUP hides or exposes the wrong dialplan output

Locate the first mismatch among function availability, current-channel assignment, group replacement, active CLI filter, console verbosity, logger destinations and the actual channel leg.

Read guide →
Guide · Asterisk Latest API branch 23 FRAME_TRACE, FRAME_DROP and CHANNEL documentation plus current Asterisk logging and debug-collection guidance reviewed October 14, 2026; FRAME_TRACE is documented since Asterisk 10.0.0 and FRAME_DROP since 16.21.0 and 18.7.0, while installed-version availability, loaded functions, channel ownership, frame direction, frame type, media topology, logger state and observed output remain deployment specific; no PBX, module, dialplan, channel, frame, DTMF event, control event, media stream, log, packet or call was inspected or tested

Asterisk FRAME_TRACE and FRAME_DROP: observe frames without masking the fault

Trace internal frame classes on one channel, keep read and write directions explicit, and reserve temporary frame dropping for controlled behavior tests with a defined restoration point.

Read guide →
Troubleshooting · Asterisk Latest API branch 23 FRAME_TRACE, FRAME_DROP and CHANNEL documentation plus current Asterisk logging and debug-collection guidance reviewed October 14, 2026; FRAME_TRACE is documented since Asterisk 10.0.0 and FRAME_DROP since 16.21.0 and 18.7.0, while installed-version availability, loaded functions, channel ownership, frame direction, frame type, media topology, logger state and observed output remain deployment specific; no PBX, module, dialplan, channel, frame, DTMF event, control event, media stream, log, packet or call was inspected or tested

Asterisk frame trace shows no DTMF, voice or expected control event

Locate the first mismatch among function availability, channel leg, trace filter, RX or TX viewpoint, logger output and the external signaling or media path before dropping frames.

Read guide →
Guide · Asterisk Latest API branch 23 LOCK, TRYLOCK and UNLOCK documentation, Asterisk 22 SHARED documentation and current global-variable guidance reviewed October 14, 2026; function availability, loaded func_lock and func_global modules, exact lock names, channel ownership, protected data, wait duration, dialplan branches and external side effects remain deployment specific; no PBX, module, dialplan, channel, lock, variable, database row, file, external service or call was inspected or tested

Asterisk dialplan locks: serialize shared state without hiding call failure

Use LOCK, TRYLOCK and UNLOCK around the smallest shared-state update, preserve channel ownership and failure branches, and keep the protected operation distinct from mutex acquisition.

Read guide →
Troubleshooting · Asterisk Latest API branch 23 LOCK, TRYLOCK and UNLOCK documentation, Asterisk 22 SHARED documentation and current global-variable guidance reviewed October 14, 2026; function availability, loaded func_lock and func_global modules, exact lock names, channel ownership, protected data, wait duration, dialplan branches and external side effects remain deployment specific; no PBX, module, dialplan, channel, lock, variable, database row, file, external service or call was inspected or tested

Asterisk calls wait on a lock or shared state is wrong

Find the first mismatch among function availability, lock name, acquisition result, channel ownership, critical-section duration, shared-value read and write, release and downstream caller treatment.

Read guide →
Guide · Asterisk current internal-database overview and Latest API branch 23 DB, DB_EXISTS, DB_DELETE and DB_KEYS documentation reviewed October 14, 2026; installed version, loaded func_db module, database families, keys, values, file ownership, backup scope, concurrent writers, managed-PBX ownership and cross-node behavior remain deployment specific; no PBX, module, database file, key, value, dialplan, channel, backup, restore or call was inspected or tested

Asterisk AstDB: persistent local keys without confusing blank and absent

Use AstDB families and keys with explicit ownership, existence checks, bounded deletion and backup evidence while keeping local persistence separate from concurrency and cluster-wide state.

Read guide →
Troubleshooting · Asterisk current internal-database overview and Latest API branch 23 DB, DB_EXISTS, DB_DELETE and DB_KEYS documentation reviewed October 14, 2026; installed version, loaded func_db module, database families, keys, values, file ownership, backup scope, concurrent writers, managed-PBX ownership and cross-node behavior remain deployment specific; no PBX, module, database file, key, value, dialplan, channel, backup, restore or call was inspected or tested

Asterisk AstDB key is missing, blank, stale or unexpectedly deleted

Find the first mismatch among running version, family and key spelling, existence, value ownership, concurrent update, deletion, persistence, backup and the later dialplan branch.

Read guide →
Guide · Asterisk 22 GotoIfTime, ExecIfTime, IFTIME, TESTTIME and STRFTIME documentation plus current public Sangoma Time Conditions and Time Groups guidance and FreePBX release/17.0 Time Conditions metadata version 17.0.1.19 reviewed October 15, 2026; Sangoma interface guidance is explicitly labelled for PBX GUI version 13 and is used for object and override semantics rather than as an exact FreePBX 17 screen map; installed modules, generated dialplan, host and explicit timezones, clock state, schedule, overrides, targets and calls remain deployment specific; no PBX, module, clock, timezone, dialplan, condition, override, destination or live call was inspected or tested

Asterisk time-based dialplan routing: conditions, zones and test time

Keep the timespec, timezone, channel clock, selected primitive, jump target and final destination independently observable when routing by time.

Read guide →
Troubleshooting · Asterisk 22 GotoIfTime, ExecIfTime, IFTIME, TESTTIME and STRFTIME documentation plus current public Sangoma Time Conditions and Time Groups guidance and FreePBX release/17.0 Time Conditions metadata version 17.0.1.19 reviewed October 15, 2026; Sangoma interface guidance is explicitly labelled for PBX GUI version 13 and is used for object and override semantics rather than as an exact FreePBX 17 screen map; installed modules, generated dialplan, host and explicit timezones, clock state, schedule, overrides, targets and calls remain deployment specific; no PBX, module, clock, timezone, dialplan, condition, override, destination or live call was inspected or tested

Asterisk GotoIfTime selects the wrong branch or destination

Find the first mismatch among channel time, timespec fields, explicit timezone, executed priority, selected target, fall-through and the downstream destination.

Read guide →
Guide · Current Asterisk variable-inheritance guidance and Asterisk 22 Set, CHANNEL, MASTER_CHANNEL, LOCAL, LOCAL_PEEK, VARIABLE_EXISTS and IMPORT documentation reviewed October 15, 2026; channel creation, inheritance depth, Gosub stack frames, master-channel lifetime, cross-channel access and loaded dialplan remain deployment specific; no PBX, channel, variable, subroutine, transfer, Local-channel path or live call was inspected or tested

Asterisk channel-variable scope and inheritance

Choose channel, child-depth, Gosub-frame, master-channel or explicit cross-channel scope before using a variable to control a call.

Read guide →
Troubleshooting · Current Asterisk variable-inheritance guidance and Asterisk 22 Set, CHANNEL, MASTER_CHANNEL, LOCAL, LOCAL_PEEK, VARIABLE_EXISTS and IMPORT documentation reviewed October 15, 2026; channel creation, inheritance depth, Gosub stack frames, master-channel lifetime, cross-channel access and loaded dialplan remain deployment specific; no PBX, channel, variable, subroutine, transfer, Local-channel path or live call was inspected or tested

Asterisk variable is missing on a child or read from the wrong channel

Find the first mismatch among variable owner, prefix depth, child-creation timing, Gosub frame, master-channel lifetime and explicit cross-channel read.

Read guide →
Guide · Current Asterisk special-extension guidance and Asterisk 23 RaiseException, EXCEPTION and TryExec documentation reviewed October 15, 2026; loaded contexts, generated dialplan, application return behavior, timeout settings and call outcomes remain deployment specific; no PBX, module set, dialplan, channel, exception, timeout or live call was inspected or tested

Asterisk dialplan exceptions and application failures

Keep the e exception path, explicit RaiseException flow and application return status separate so each failure reaches the intended handler.

Read guide →
Troubleshooting · Current Asterisk special-extension guidance and Asterisk 23 RaiseException, EXCEPTION and TryExec documentation reviewed October 15, 2026; loaded contexts, generated dialplan, application return behavior, timeout settings and call outcomes remain deployment specific; no PBX, module set, dialplan, channel, exception, timeout or live call was inspected or tested

Asterisk exception handler does not run or has the wrong origin

Find the first mismatch among event class, executing context, local special extension, missing e handler, overwritten evidence and unchecked TRYSTATUS.

Read guide →
Guide · Current Asterisk 23 DIALPLAN_EXISTS, EVAL_EXTEN, EVAL_SUB and Return documentation reviewed October 15, 2026; installed branch, loaded modules, generated dialplan, dynamic inputs, target variables, subroutine effects and call outcomes remain deployment specific; no PBX, module set, dialplan, channel, lookup, subroutine, side effect or live call was inspected or tested

Asterisk dialplan lookups and evaluated subroutines

Prove an exact target, understand EVAL_EXTEN target-context evaluation and reserve EVAL_SUB for bounded routines with explicit returns and effects.

Read guide →
Troubleshooting · Current Asterisk 23 DIALPLAN_EXISTS, EVAL_EXTEN, EVAL_SUB and Return documentation reviewed October 15, 2026; installed branch, loaded modules, generated dialplan, dynamic inputs, target variables, subroutine effects and call outcomes remain deployment specific; no PBX, module set, dialplan, channel, lookup, subroutine, side effect or live call was inspected or tested

Asterisk dialplan lookup returns the wrong value or runs side effects

Find the first mismatch among function availability, exact target, target-context variables, Return value, arguments, evaluation timing and repeated effects.

Read guide →
Guide · Current Asterisk res_pjsip_history source plus official PJSIP history, troubleshooting, logging and CHANNEL documentation reviewed October 15, 2026; the history module has extended support status in current source and was introduced in Asterisk 13.8.0, while exact module availability, CLI grammar, loaded state, memory headroom, message volume, logger filters and retention policy remain installation specific; no host, module, process, memory state, endpoint, trunk, message, capture, credential, packet, dialog or live call was inspected or tested

Asterisk PJSIP History: bounded in-memory SIP evidence

Capture a short SIP interval in memory, filter it by supported fields and preserve one dialog without turning permanent tracing into a memory or privacy risk.

Read guide →
Troubleshooting · Current Asterisk res_pjsip_history source plus official PJSIP history, troubleshooting, logging and CHANNEL documentation reviewed October 15, 2026; the history module has extended support status in current source and was introduced in Asterisk 13.8.0, while exact module availability, CLI grammar, loaded state, memory headroom, message volume, logger filters and retention policy remain installation specific; no host, module, process, memory state, endpoint, trunk, message, capture, credential, packet, dialog or live call was inspected or tested

Asterisk PJSIP History is empty, incomplete or too noisy

Prove module state, capture timing, retained entries, filter grammar and call-leg identity before concluding that signaling is absent.

Read guide →
Guide · Current Asterisk 23 res_prometheus configuration, sample configuration, implementation, built-in HTTP-server guidance and official release history plus the Prometheus pull-model overview reviewed October 15, 2026; Asterisk documents res_prometheus from 17.0.0, while channel- and bridge-detail cardinality controls are version-specific and the installed branch, package, module providers, HTTP prefix, URI, authentication, network policy, scraper, label set, retention and alert rules remain deployment specific; no host, module, configuration, credential, HTTP route, scrape target, metric series, dashboard, alert, endpoint, registration, channel, bridge or live call was inspected or tested

Asterisk Prometheus metrics: module, HTTP route and cardinality boundaries

Expose a bounded, authenticated Asterisk metrics route, prove the installed metric providers and keep scrape success separate from call-service health.

Read guide →
Troubleshooting · Current Asterisk 23 res_prometheus configuration, sample configuration, implementation, built-in HTTP-server guidance and official release history plus the Prometheus pull-model overview reviewed October 15, 2026; Asterisk documents res_prometheus from 17.0.0, while channel- and bridge-detail cardinality controls are version-specific and the installed branch, package, module providers, HTTP prefix, URI, authentication, network policy, scraper, label set, retention and alert rules remain deployment specific; no host, module, configuration, credential, HTTP route, scrape target, metric series, dashboard, alert, endpoint, registration, channel, bridge or live call was inspected or tested

Asterisk Prometheus metrics are missing, stale or too large

Find the first failure among branch support, module state, HTTP path, authentication, provider families, scrape timing, labels and cardinality.

Read guide →
Guide · Current Asterisk ODBC setup guidance, upstream res_odbc and func_odbc samples, Asterisk 23 ODBC_FETCH and SQL escaping references, and security advisory AST-2022-003 reviewed October 15, 2026; installed ODBC driver, system DSN, Asterisk modules, configuration ownership, database schema, permissions, query plan, transaction policy and call-flow fallback remain deployment specific; no host, driver, DSN, module, credential, database, schema, query, row, transaction, channel or live call was inspected or tested

Asterisk func_odbc dialplan lookups: DSN, escaping, rows and latency

Design one bounded database-backed dialplan lookup without confusing a loaded connector, a successful query, a returned row and the final call-flow outcome.

Read guide →
Troubleshooting · Current Asterisk ODBC setup guidance, upstream res_odbc and func_odbc samples, Asterisk 23 ODBC_FETCH and SQL escaping references, and security advisory AST-2022-003 reviewed October 15, 2026; installed ODBC driver, system DSN, Asterisk modules, configuration ownership, database schema, permissions, query plan, transaction policy and call-flow fallback remain deployment specific; no host, driver, DSN, module, credential, database, schema, query, row, transaction, channel or live call was inspected or tested

Asterisk func_odbc returns empty, errors or delays the call

Find the first failure among module availability, connection naming, DSN and driver state, query execution, escaping, result cardinality and synchronous call-path latency.

Read guide →
Guide · Current Asterisk database-transaction guidance, latest generated ODBC transaction, commit and rollback references, upstream func_odbc and res_odbc samples, and res_odbc configuration guidance reviewed October 15, 2026; installed Asterisk branch, module packaging, driver, DSN, DBMS, schema, statements, account permissions, isolation support, transaction lifetime, concurrency, idempotency, retry policy and caller treatment remain deployment specific; no host, module, driver, DSN, credential, database, schema, statement, row, transaction, channel or live call was inspected or tested

Asterisk ODBC writes and transactions: commit, rollback and hangup safety

Design one authorized database write with a bounded func_odbc contract, named transaction, explicit completion and deterministic failure treatment.

Read guide →
Troubleshooting · Current Asterisk database-transaction guidance, latest generated ODBC transaction, commit and rollback references, upstream func_odbc and res_odbc samples, and res_odbc configuration guidance reviewed October 15, 2026; installed Asterisk branch, module packaging, driver, DSN, DBMS, schema, statements, account permissions, isolation support, transaction lifetime, concurrency, idempotency, retry policy and caller treatment remain deployment specific; no host, module, driver, DSN, credential, database, schema, statement, row, transaction, channel or live call was inspected or tested

Asterisk ODBC write commits, rolls back or duplicates data

Trace one database mutation from func_odbc input and affected rows through active transaction, commit or rollback, channel teardown and any later retry.

Read guide →
Guide · Current Asterisk Realtime architecture, PJSIP Realtime tutorial, Sorcery mapping and caching guidance, Realtime schema-management guidance, PJSIP troubleshooting guide, and upstream extconfig and sorcery samples reviewed October 15, 2026; installed Asterisk branch, packaged modules, mapping order, connector, DSN, driver, schema revision, database account, rows, cache policy, reload behavior and PJSIP runtime state remain deployment specific; no host, module, connector, credential, database, schema, row, cache, endpoint, registration, message, packet or live call was inspected or tested

Asterisk PJSIP Realtime: Sorcery mapping, schema and cache boundaries

Map one PJSIP object from Sorcery type and source order through Realtime family, connector, schema row, cache and runtime consumer.

Read guide →
Troubleshooting · Current Asterisk Realtime architecture, PJSIP Realtime tutorial, Sorcery mapping and caching guidance, Realtime schema-management guidance, PJSIP troubleshooting guide, and upstream extconfig and sorcery samples reviewed October 15, 2026; installed Asterisk branch, packaged modules, mapping order, connector, DSN, driver, schema revision, database account, rows, cache policy, reload behavior and PJSIP runtime state remain deployment specific; no host, module, connector, credential, database, schema, row, cache, endpoint, registration, message, packet or live call was inspected or tested

Asterisk PJSIP Realtime object is missing, stale or from the wrong source

Find the first divergence among Sorcery type, mapping order, Realtime family, connector, schema row, cache and PJSIP runtime view.

Read guide →
Guide · Current Asterisk branch-23-generated PERIODIC_HOOK, Playback and CHANNEL references plus branch 22 and 20 PERIODIC_HOOK references reviewed October 15, 2026; installed branch, func_periodic_hook availability, owner channel, hook ID, context, extension, whole-second interval, hook-channel dialplan, audio file, bridge and media topology, recording policy, load and teardown remain deployment specific; no host, module, dialplan, channel, hook, bridge, recording, audio stream or live call was inspected or tested

Asterisk periodic hooks: owner channel, async execution and injected audio

Attach one bounded periodic dialplan hook while keeping the owner channel, generated hook ID, asynchronous hook channel, interval, audio and teardown evidence separate.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated PERIODIC_HOOK, Playback and CHANNEL references plus branch 22 and 20 PERIODIC_HOOK references reviewed October 15, 2026; installed branch, func_periodic_hook availability, owner channel, hook ID, context, extension, whole-second interval, hook-channel dialplan, audio file, bridge and media topology, recording policy, load and teardown remain deployment specific; no host, module, dialplan, channel, hook, bridge, recording, audio stream or live call was inspected or tested

Asterisk periodic hook is missing, duplicated or heard late

Find the first divergence among module availability, hook creation, retained ID, owner channel, async hook execution, playback, media injection and teardown.

Read guide →
Guide · Current Asterisk branch-23-generated WaitForSilence, WaitForNoise and BackgroundDetect references plus branch 22 WaitForSilence and WaitForNoise references reviewed October 15, 2026; installed branch, app_waitforsilence availability, exact channel, answered state, received voice frames, DSP classification, duration, iterations, timeout, return-variable contract and final call flow remain deployment specific; no host, module, dialplan, channel, packet, media frame, detector, endpoint or live call was inspected or tested

Asterisk WaitForSilence and WaitForNoise: duration, timeout and media evidence

Wait for a bounded silence or noise interval while keeping channel ownership, received frames, duration, iterations, timeout, status and downstream call flow independently observable.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated WaitForSilence, WaitForNoise and BackgroundDetect references plus branch 22 WaitForSilence and WaitForNoise references reviewed October 15, 2026; installed branch, app_waitforsilence availability, exact channel, answered state, received voice frames, DSP classification, duration, iterations, timeout, return-variable contract and final call flow remain deployment specific; no host, module, dialplan, channel, packet, media frame, detector, endpoint or live call was inspected or tested

Asterisk silence or noise wait never finishes, times out or advances early

Find the first divergence among loaded application, channel leg, received media, duration units, iterations, timeout, status handling and downstream dialplan.

Read guide →
Guide · Current Asterisk branch-23-generated WaitForCondition, VARIABLE_EXISTS and GLOBAL_EXISTS references, branch 22 WaitForCondition reference, and current dialplan expression and conditional-application documentation reviewed October 15, 2026; installed branch, module packaging, exact dialplan, expression, channel, mutable-state owner, writer, timing, function cost and downstream call flow remain deployment specific; no host, module, dialplan, channel, variable, global, function, poll, packet or live call was inspected or tested

Asterisk WaitForCondition: deferred expressions, polling and status evidence

Wait for a mutable condition without freezing its first value, while keeping expression ownership, poll interval, timeout, status and downstream call flow independently observable.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated WaitForCondition, VARIABLE_EXISTS and GLOBAL_EXISTS references, branch 22 WaitForCondition reference, and current dialplan expression and conditional-application documentation reviewed October 15, 2026; installed branch, module packaging, exact dialplan, expression, channel, mutable-state owner, writer, timing, function cost and downstream call flow remain deployment specific; no host, module, dialplan, channel, variable, global, function, poll, packet or live call was inspected or tested

Asterisk WaitForCondition times out, fails or returns early

Find the first divergence among installed application, loaded expression, deferred evaluation, mutable-state owner, writer timing, truth rules, interval, timeout, status and next dialplan step.

Read guide →
Guide · Current Asterisk branch-23-generated WaitUntil, TIMEOUT, STRFTIME and STRPTIME references and branch 22 WaitUntil reference reviewed October 15, 2026; installed branch, module packaging, exact dialplan, channel lifetime, epoch source, civil-time input, timezone database, host clock, clock correction, scheduling, downstream action and caller treatment remain deployment specific; no host, module, dialplan, channel, epoch source, timezone database, clock, packet, scheduler or live call was inspected or tested

Asterisk WaitUntil: epoch scheduling, status and channel-lifetime evidence

Wait on an active channel until an absolute epoch while keeping civil-time conversion, status, channel lifetime, call timeout and downstream action independently observable.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated WaitUntil, TIMEOUT, STRFTIME and STRPTIME references and branch 22 WaitUntil reference reviewed October 15, 2026; installed branch, module packaging, exact dialplan, channel lifetime, epoch source, civil-time input, timezone database, host clock, clock correction, scheduling, downstream action and caller treatment remain deployment specific; no host, module, dialplan, channel, epoch source, timezone database, clock, packet, scheduler or live call was inspected or tested

Asterisk WaitUntil returns PAST, fails or fires at the wrong time

Find the first divergence among installed application, loaded epoch, civil-time conversion, timezone, host clock, channel lifetime, absolute timeout, immediate status and downstream action.

Read guide →
Guide · Current Asterisk branch-23-generated and branch 22 Dial references, pre-dial-handler guidance, hangup-cause guidance, HANGUPCAUSE_KEYS and CHANNEL references reviewed October 15, 2026; installed branch, channel driver, loaded dialplan, endpoint, contact set, signaling, causes, bridge, media and caller treatment remain deployment specific; no host, module, dialplan, channel, endpoint, trunk, packet, bridge, media stream or live call was inspected or tested

Asterisk Dial: outbound legs, status, timing and continuation evidence

Follow one Dial invocation through created channels, provisional events, answer, bridge, return status and post-call continuation without collapsing per-leg evidence into one result.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch 22 Dial references, pre-dial-handler guidance, hangup-cause guidance, HANGUPCAUSE_KEYS and CHANNEL references reviewed October 15, 2026; installed branch, channel driver, loaded dialplan, endpoint, contact set, signaling, causes, bridge, media and caller treatment remain deployment specific; no host, module, dialplan, channel, endpoint, trunk, packet, bridge, media stream or live call was inspected or tested

Asterisk Dial returns early, reports the wrong status or never answers

Find the first divergence among loaded dial string, outbound-channel creation, progress, final response, answer, bridge, application result and continuation.

Read guide →
Guide · Current Asterisk branch-23-generated and branch 22 Originate references, pre-dial-handler guidance, Dial reference, AMI Originate reference and ARI interface overview reviewed October 15, 2026; installed branch, channel driver, loaded dialplan, channel technology, destination, endpoint, signaling, application, bridge, codec negotiation and media remain deployment specific; no host, module, dialplan, channel, endpoint, packet, bridge, media stream or live call was inspected or tested

Asterisk Originate: channel creation, destination and result evidence

Use the dialplan Originate application without confusing its synchronous or asynchronous return, destination handoff and channel status with a completed two-party call.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch 22 Originate references, pre-dial-handler guidance, Dial reference, AMI Originate reference and ARI interface overview reviewed October 15, 2026; installed branch, channel driver, loaded dialplan, channel technology, destination, endpoint, signaling, application, bridge, codec negotiation and media remain deployment specific; no host, module, dialplan, channel, endpoint, packet, bridge, media stream or live call was inspected or tested

Asterisk Originate reports success but the call or second leg is missing

Find the first divergence among loaded Originate arguments, channel creation, answer, destination handoff, a later Dial attempt, bridge and final workflow result.

Read guide →
Guide · Current Asterisk branch-23-generated and branch 22 Bridge references, Bridge application overview, CHANNELS and CHANNEL function references and ARI bridge overview reviewed October 15, 2026; installed branch, channel driver, loaded dialplan, live channel names and identifiers, bridge technology, feature configuration, endpoint signaling, codec negotiation and media remain deployment specific; no host, module, dialplan, channel, bridge, packet, media stream or live call was inspected or tested

Asterisk Bridge(): join two existing channels with explicit ownership

Use the dialplan Bridge application without confusing target lookup, bridge entry, application return and media verification.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch 22 Bridge references, Bridge application overview, CHANNELS and CHANNEL function references and ARI bridge overview reviewed October 15, 2026; installed branch, channel driver, loaded dialplan, live channel names and identifiers, bridge technology, feature configuration, endpoint signaling, codec negotiation and media remain deployment specific; no host, module, dialplan, channel, bridge, packet, media stream or live call was inspected or tested

Asterisk Bridge fails, loops, cannot find the target or has no media

Find the first divergence among live-channel lookup, target lifetime, answer state, bridge entry, application result, exit and bidirectional media.

Read guide →
Guide · Current Asterisk branch-23-generated and branch 22 BridgeWait and BridgeAdd references, Bridge application overview and ARI bridge overview reviewed October 15, 2026; installed branch, loaded modules, dialplan, live channel identities, holding-bridge lifecycle, music-on-hold classes, bridge technology, endpoint signaling and media remain deployment specific; no host, module, dialplan, channel, holding bridge, bridge, packet, media stream or live call was inspected or tested

Asterisk BridgeWait and BridgeAdd: holding roles and bridge membership

Place participants and announcers in a named holding workflow, then add a channel to an existing bridge without confusing names, live bridge identity, entertainment and media.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch 22 BridgeWait and BridgeAdd references, Bridge application overview and ARI bridge overview reviewed October 15, 2026; installed branch, loaded modules, dialplan, live channel identities, holding-bridge lifecycle, music-on-hold classes, bridge technology, endpoint signaling and media remain deployment specific; no host, module, dialplan, channel, holding bridge, bridge, packet, media stream or live call was inspected or tested

Asterisk BridgeWait has wrong entertainment or BridgeAdd fails

Find the first divergence among the holding handle, role, answer state, entertainment, duration exit, live target lookup, bridge membership and media.

Read guide →
Guide · Current Asterisk branch-23-generated AMI Bridge, BridgeList, BridgeInfo, BridgeKick and bridge-event references plus branch 22 Bridge and BridgeKick references reviewed October 15, 2026; installed branch, loaded manager actions, AMI user permissions, live channel and bridge identities, event delivery, signaling, bridge technology and media remain deployment specific; no AMI session, user, permission, host, manager action, bridge, channel, packet, media stream or live call was inspected or tested

Asterisk AMI bridge control: actions, membership and event evidence

Bridge two live channels, inventory bridge identity and remove a member without confusing action acknowledgement, bridge membership, signaling and media.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated AMI Bridge, BridgeList, BridgeInfo, BridgeKick and bridge-event references plus branch 22 Bridge and BridgeKick references reviewed October 15, 2026; installed branch, loaded manager actions, AMI user permissions, live channel and bridge identities, event delivery, signaling, bridge technology and media remain deployment specific; no AMI session, user, permission, host, manager action, bridge, channel, packet, media stream or live call was inspected or tested

Asterisk AMI Bridge succeeds but membership is wrong

Find the first divergence among manager authorization, action correlation, live channel identity, bridge identity, membership events and media.

Read guide →
Guide · Current Asterisk branch-23-generated AMI Redirect, BlindTransfer, Atxfer and transfer-event references plus branch 22 action references reviewed October 16, 2026; installed branch, loaded manager actions, AMI user permissions, bridge transfer policy, live channel identity, dialplan destination, event delivery, signaling, connected-line identity and media remain deployment specific; no AMI session, user, permission, host, manager action, channel, bridge, dialplan destination, packet, media stream or live call was inspected or tested

Asterisk AMI transfer control: Redirect, BlindTransfer and Atxfer

Choose the manager action that matches the intended transfer and correlate acknowledgement, bridge events, dialplan entry, target result and media.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated AMI Redirect, BlindTransfer, Atxfer and transfer-event references plus branch 22 action references reviewed October 16, 2026; installed branch, loaded manager actions, AMI user permissions, bridge transfer policy, live channel identity, dialplan destination, event delivery, signaling, connected-line identity and media remain deployment specific; no AMI session, user, permission, host, manager action, channel, bridge, dialplan destination, packet, media stream or live call was inspected or tested

Asterisk AMI transfer succeeds but the call is wrong

Find the first divergence among manager authorization, action contract, live channel, bridge ownership, dialplan entry, target result and final media.

Read guide →
Guide · Current Asterisk branch-23-generated CancelAtxfer, Atxfer, attended-transfer event and feature-configuration references plus branch 22 action and configuration references reviewed October 16, 2026; installed branch, loaded actions, AMI permissions, effective features.conf, transfer permissions, live channel identity, bridge topology, callback behavior, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, configuration file, feature code, channel, bridge, callback, packet, media stream or live call was inspected or tested

Asterisk AMI attended-transfer cancel and recovery

Use CancelAtxfer against the active transferer, distinguish abort from complete, swap and three-way actions, and verify re-bridging or callback recovery separately.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated CancelAtxfer, Atxfer, attended-transfer event and feature-configuration references plus branch 22 action and configuration references reviewed October 16, 2026; installed branch, loaded actions, AMI permissions, effective features.conf, transfer permissions, live channel identity, bridge topology, callback behavior, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, configuration file, feature code, channel, bridge, callback, packet, media stream or live call was inspected or tested

Asterisk CancelAtxfer fails or the wrong call resumes

Find the first divergence among action availability, abort configuration, active transferer identity, transfer phase, re-bridging, callback recovery and media.

Read guide →
Guide · Current Asterisk branch-23-generated LocalOptimizeAway, LocalOptimizationBegin, LocalOptimizationEnd and LocalBridge references plus the branch 22 action, AMI v2 specification and Local-channel optimization and modifier references reviewed October 16, 2026; installed branch, loaded action and events, AMI permissions, dial string, Local modifiers, channel identities, bridge topology, variables, recording hooks, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, dialplan, Local channel, bridge, packet, media stream or live call was inspected or tested

Asterisk AMI Local-channel optimization and identity

Control when Local channel halves may leave the media path, correlate Begin and End events, and preserve identity, variables and bridge evidence across optimization.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated LocalOptimizeAway, LocalOptimizationBegin, LocalOptimizationEnd and LocalBridge references plus the branch 22 action, AMI v2 specification and Local-channel optimization and modifier references reviewed October 16, 2026; installed branch, loaded action and events, AMI permissions, dial string, Local modifiers, channel identities, bridge topology, variables, recording hooks, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, dialplan, Local channel, bridge, packet, media stream or live call was inspected or tested

Asterisk Local channel disappears or optimization fails

Find the first divergence among Local modifiers, current channel identity, bridge eligibility, manager response, correlated optimization events, final topology and media.

Read guide →
Guide · Current Asterisk branch-23-generated CoreShowChannelMap, CoreShowChannelMapComplete, CoreShowChannels, CoreShowChannel, CoreShowChannelsComplete, Status, StatusComplete, Newchannel and Rename references plus the branch 22 map action and completion event reviewed October 16, 2026; installed branch, loaded actions and events, manager permissions, session ordering, channel names, stable identifiers, bridge membership, variables, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, channel, bridge, variable, packet, media stream or live call was inspected or tested

Asterisk AMI channel snapshots and connected maps

Choose CoreShowChannels, CoreShowChannelMap or Status deliberately, preserve list boundaries, and correlate mutable channel, linked and bridge identities without treating a snapshot as a final call result.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated CoreShowChannelMap, CoreShowChannelMapComplete, CoreShowChannels, CoreShowChannel, CoreShowChannelsComplete, Status, StatusComplete, Newchannel and Rename references plus the branch 22 map action and completion event reviewed October 16, 2026; installed branch, loaded actions and events, manager permissions, session ordering, channel names, stable identifiers, bridge membership, variables, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, channel, bridge, variable, packet, media stream or live call was inspected or tested

Asterisk AMI channel snapshot is missing, stale or maps the wrong call

Find the first divergence among installed-version support, list completion, manager-session correlation, live channel name, stable identity, bridge membership, lifecycle events and downstream media.

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 →
Troubleshooting · 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 events are missing, filtered, delayed or duplicated

Locate the first divergence among manager permissions, the per-session event mask, configured and dynamic filters, HTTP WaitEvent queueing, TCP reads, reconnects, parsing and downstream deduplication.

Read guide →
Guide · Current Asterisk branch-23-generated AMI UserEvent action, UserEvent event and UserEvent dialplan-application references, matching branch-22 references, plus the official AMI event-filtering, command-syntax and Manager TCP/IP material reviewed October 16, 2026; installed branch, module, dialplan, manager permissions, session mask, filters, transport, parser, retry policy, schema and application outcome remain deployment specific; no PBX, module, dialplan, manager session, event stream, channel, bridge, endpoint, packet, media stream, business system or live call was inspected or tested

Asterisk AMI UserEvent custom telemetry

Design application-owned UserEvent names, headers and correlation keys while keeping AMI action responses, dialplan emission, event delivery and downstream outcomes independently observable.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated AMI UserEvent action, UserEvent event and UserEvent dialplan-application references, matching branch-22 references, plus the official AMI event-filtering, command-syntax and Manager TCP/IP material reviewed October 16, 2026; installed branch, module, dialplan, manager permissions, session mask, filters, transport, parser, retry policy, schema and application outcome remain deployment specific; no PBX, module, dialplan, manager session, event stream, channel, bridge, endpoint, packet, media stream, business system or live call was inspected or tested

Asterisk AMI UserEvent is missing, duplicated or misleading

Trace one application-owned event from its AMI action or dialplan producer through event naming, USER permission, masks, filters, transport, parsing, idempotent storage and the separate business outcome.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 AMI DeviceStateChange action, DeviceStateList action, DeviceStateChange event, DeviceStateListComplete event and DEVICE_STATE references, plus official device-state, hint and AMI-filtering documentation reviewed October 16, 2026; the write action requires Asterisk 24.1.0, 23.7.0, 22.13.0 or 20.23.0 or later within those branches and res_manager_devicestate; installed release, module, manager permissions, session mask, filters, provider ownership, entity identity, cache behavior, hint mapping and downstream consumer remain deployment specific; no PBX, node, module, manager session, state provider, hint, subscription, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI device-state synchronization and listing

Use the version-gated DeviceStateChange action only for remote-device synchronization, and consume DeviceStateList as a bounded snapshot without flattening provider, hint or endpoint evidence.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 AMI DeviceStateChange action, DeviceStateList action, DeviceStateChange event, DeviceStateListComplete event and DEVICE_STATE references, plus official device-state, hint and AMI-filtering documentation reviewed October 16, 2026; the write action requires Asterisk 24.1.0, 23.7.0, 22.13.0 or 20.23.0 or later within those branches and res_manager_devicestate; installed release, module, manager permissions, session mask, filters, provider ownership, entity identity, cache behavior, hint mapping and downstream consumer remain deployment specific; no PBX, node, module, manager session, state provider, hint, subscription, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI device state is missing, stale or wrong

Trace one remote state write or bounded list from installed action support through EntityID, cache choice, event delivery, provider ownership, hint aggregation and the separately observed endpoint outcome.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 AMI PresenceState, PresenceStateList, PresenceStateChange, PresenceStatus, PresenceStateListComplete and PRESENCE_STATE references, plus official presence, hint, state-query and AMI-filtering documentation reviewed October 16, 2026; installed branch, maintenance release, res_manager_presencestate and func_presencestate availability, manager permissions, session mask, filters, provider ownership, writer, hint mapping, subscriber and privacy policy remain deployment specific; no PBX, module, manager session, presence provider, dialplan, hint, subscription, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI presence-state queries, lists and hint events

Keep a single-provider PresenceState response, a completed PresenceStateList, every-provider PresenceStateChange events and hint-scoped PresenceStatus events as distinct evidence.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 AMI PresenceState, PresenceStateList, PresenceStateChange, PresenceStatus, PresenceStateListComplete and PRESENCE_STATE references, plus official presence, hint, state-query and AMI-filtering documentation reviewed October 16, 2026; installed branch, maintenance release, res_manager_presencestate and func_presencestate availability, manager permissions, session mask, filters, provider ownership, writer, hint mapping, subscriber and privacy policy remain deployment specific; no PBX, module, manager session, presence provider, dialplan, hint, subscription, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI presence state is missing, stale or wrong

Trace one named presence provider through its writer, direct query, bounded list, every-provider event, hint-scoped event and separately observed subscriber or routing outcome.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 AMI ExtensionState, ExtensionStateList, ExtensionStatus and ExtensionStateListComplete references, EXTENSION_STATE and HINT function references, plus official extension-state, device-state and AMI-filtering documentation reviewed October 16, 2026; installed branch, maintenance release, loaded dialplan, manager permissions, session mask, filters, hint context, devices, presence mapping, subscription and endpoint behavior remain deployment specific; no PBX, module, manager session, dialplan, hint, state provider, subscription, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI extension-state queries, lists and hint evidence

Keep one Exten-and-Context query, a completed extension-state list, hint aggregation, live ExtensionStatus events and subscriber outcomes as distinct evidence.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 AMI ExtensionState, ExtensionStateList, ExtensionStatus and ExtensionStateListComplete references, EXTENSION_STATE and HINT function references, plus official extension-state, device-state and AMI-filtering documentation reviewed October 16, 2026; installed branch, maintenance release, loaded dialplan, manager permissions, session mask, filters, hint context, devices, presence mapping, subscription and endpoint behavior remain deployment specific; no PBX, module, manager session, dialplan, hint, state provider, subscription, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI extension state is missing, stale or wrong

Trace one Exten-and-Context pair through the loaded hint, its device providers, direct query, bounded list, live event and separately observed subscriber or call outcome.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated DialplanExtensionAdd, DialplanExtensionRemove and ShowDialPlan action references plus official dialplan structure, reload, pattern-order, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, dialplan engine, configuration owner, include graph, reload behavior, manager privileges, channel origin, pattern match, application availability and call outcome remain deployment specific; no PBX, module, manager session, configuration file, loaded dialplan, channel, packet, media stream or live call was inspected or tested

Asterisk AMI runtime dialplan inspection and exact extension mutation

Use ShowDialPlan, DialplanExtensionAdd and DialplanExtensionRemove without confusing the loaded dialplan, its persistent source, a manager response or a completed call.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated DialplanExtensionAdd, DialplanExtensionRemove and ShowDialPlan action references plus official dialplan structure, reload, pattern-order, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, dialplan engine, configuration owner, include graph, reload behavior, manager privileges, channel origin, pattern match, application availability and call outcome remain deployment specific; no PBX, module, manager session, configuration file, loaded dialplan, channel, packet, media stream or live call was inspected or tested

Asterisk AMI dialplan extension is missing, stale or wrong

Trace one context, extension and priority from owned source through the loaded dialplan, mutation response, match selection, execution and separately observed call result.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated GetConfig, GetConfigJSON, ListCategories, CreateConfig and UpdateConfig action references plus official configuration-file, template, include, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, configuration directory, file ownership, generated-file owner, include graph, template inheritance, module parser, reload support, manager privileges and runtime outcome remain deployment specific; no PBX, module, manager session, configuration file, filesystem, reload, channel, packet, media stream or live call was inspected or tested

Asterisk AMI configuration-file inspection and controlled update

Use GetConfig, ListCategories, CreateConfig and UpdateConfig without confusing file content, inherited effective values, a write response, a reload or loaded runtime state.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated GetConfig, GetConfigJSON, ListCategories, CreateConfig and UpdateConfig action references plus official configuration-file, template, include, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, configuration directory, file ownership, generated-file owner, include graph, template inheritance, module parser, reload support, manager privileges and runtime outcome remain deployment specific; no PBX, module, manager session, configuration file, filesystem, reload, channel, packet, media stream or live call was inspected or tested

Asterisk AMI configuration update is missing, stale or wrong

Trace one intended file change across source and destination, ordered UpdateConfig operations, includes and templates, reload response, loaded module state and service outcome.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated ModuleCheck, ModuleLoad and Reload action references plus official module-loader, module-type, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, package contents, module directory, dependencies, modules.conf policy, active use counts, reload support, registered capabilities, parsed configuration, runtime objects, manager privileges and service outcome remain deployment specific; no PBX, module, package, manager session, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk AMI module checks, load, reload and refresh

Use ModuleCheck, ModuleLoad and Reload without confusing a loaded shared object with registered features, parsed configuration, durable startup policy or working calls.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated ModuleCheck, ModuleLoad and Reload action references plus official module-loader, module-type, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, package contents, module directory, dependencies, modules.conf policy, active use counts, reload support, registered capabilities, parsed configuration, runtime objects, manager privileges and service outcome remain deployment specific; no PBX, module, package, manager session, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk module is loaded but its capability is missing

Trace one missing application, function, driver, action or runtime object through package inventory, load response, registration, configuration, dependencies and behavior.

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 →
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 →
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 →
Troubleshooting · 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 login fails or the session drops

Trace one failed login or lost manager session through listener identity, protected reachability, framing, authentication fields, manager account policy and the exact termination boundary.

Read guide →
Guide · Asterisk branch-23-generated CoreStatus and CoreSettings references, branch-22-generated references for the same actions, and official AMI syntax, v2 and permission documentation reviewed October 16, 2026; installed branch and maintenance release, server identity, manager transport, account, ACL, read and write classes, action availability, returned fields, clock, restart and reload history, configured limits, runtime load, channels and downstream collector behavior remain deployment specific; no PBX, manager configuration, account, credential, socket, session, request, response, status value, setting, process, channel, packet, media stream or live call was inspected or tested

Asterisk AMI CoreStatus and CoreSettings: separate status from settings

Use the two core-query actions as correlated, node-specific evidence without turning a successful response into proof of call health, configuration ownership or capacity.

Read guide →
Troubleshooting · Asterisk branch-23-generated CoreStatus and CoreSettings references, branch-22-generated references for the same actions, and official AMI syntax, v2 and permission documentation reviewed October 16, 2026; installed branch and maintenance release, server identity, manager transport, account, ACL, read and write classes, action availability, returned fields, clock, restart and reload history, configured limits, runtime load, channels and downstream collector behavior remain deployment specific; no PBX, manager configuration, account, credential, socket, session, request, response, status value, setting, process, channel, packet, media stream or live call was inspected or tested

Asterisk AMI core status or settings is missing, stale or wrong

Trace one core query through node identity, session, framing, action visibility, response correlation, parser behavior and the independent evidence that owns the disputed value.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated QueueSummary and QueueStatus action references plus official AMI v2, permission and queue documentation reviewed October 16, 2026; installed branch and maintenance release, app_queue version, server identity, manager transport, account, ACL, read and write classes, queue and member names, dynamic membership, event schema, completion behavior, clock, configuration owner, caller state, member reachability, device state and downstream collector behavior remain deployment specific; no PBX, queue, member, caller, manager configuration, account, credential, socket, session, request, response, event series, completion marker, channel, packet, media stream or live call was inspected or tested

Asterisk AMI QueueStatus and QueueSummary snapshots

Collect queue summaries and detailed status as separate, filtered AMI transactions with explicit correlation and completion boundaries.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated QueueSummary and QueueStatus action references plus official AMI v2, permission and queue documentation reviewed October 16, 2026; installed branch and maintenance release, app_queue version, server identity, manager transport, account, ACL, read and write classes, queue and member names, dynamic membership, event schema, completion behavior, clock, configuration owner, caller state, member reachability, device state and downstream collector behavior remain deployment specific; no PBX, queue, member, caller, manager configuration, account, credential, socket, session, request, response, event series, completion marker, channel, packet, media stream or live call was inspected or tested

Asterisk AMI queue status or summary is missing, stale or incomplete

Trace one queue snapshot through target identity, filters, permissions, response correlation, completion, parser behavior and the queue evidence that owns the disputed fact.

Read guide →
Guide · Asterisk branch-22-generated MailboxCount, MailboxStatus, VoicemailBoxSummary, VoicemailRefresh, MWIGet, MWIUpdate and MailboxStateChange action references plus official VM_INFO, AMI v2 and manager-permission documentation reviewed October 17, 2026; installed branch and maintenance release, action availability, module selection, voicemail backend, mailbox and context identity, folder, external MWI ownership, manager transport, account, ACL, read and write classes, response field behavior, storage freshness, clock, configuration owner, endpoint subscription, phone indicator and downstream collector behavior remain deployment specific; no PBX, mailbox, voicemail store, IMAP account, manager configuration, account, credential, socket, session, request, response, MWI subscription, endpoint, phone, message, playback or live call was inspected or tested

Asterisk AMI MailboxCount and MailboxStatus queries

Query one voicemail mailbox with explicit identity, raw response preservation and a clear boundary between message counts, waiting state and downstream MWI behavior.

Read guide →
Troubleshooting · Asterisk branch-22-generated MailboxCount, MailboxStatus, VoicemailBoxSummary, VoicemailRefresh, MWIGet, MWIUpdate and MailboxStateChange action references plus official VM_INFO, AMI v2 and manager-permission documentation reviewed October 17, 2026; installed branch and maintenance release, action availability, module selection, voicemail backend, mailbox and context identity, folder, external MWI ownership, manager transport, account, ACL, read and write classes, response field behavior, storage freshness, clock, configuration owner, endpoint subscription, phone indicator and downstream collector behavior remain deployment specific; no PBX, mailbox, voicemail store, IMAP account, manager configuration, account, credential, socket, session, request, response, MWI subscription, endpoint, phone, message, playback or live call was inspected or tested

Asterisk AMI mailbox count or status is missing, stale or inverted

Trace one mailbox query through target identity, mailbox context, action availability, permissions, raw field semantics, voicemail-store freshness, response parsing and cache behavior.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 VoicemailUsersList and VoicemailUserStatus references, branch-22 VoicemailBoxSummary and MailboxCount references, and official AMI v2 and manager-permission documentation reviewed October 17, 2026; VoicemailUsersList is documented by app_voicemail from Asterisk 1.6 while VoicemailUserStatus is documented by app_voicemail_imap from Asterisk 16, and the generated action pages do not define a shared response schema or make either response proof of message inventory, storage freshness, playback or MWI delivery; installed branch, maintenance release, module, backend, mailbox and context identity, manager permissions, response framing, parser and cache behavior remain deployment specific; no PBX, module, mailbox, voicemail user, store, IMAP account, manager configuration, credential, session, request, response, message, MWI subscription, endpoint, phone, playback or live call was inspected or tested

Asterisk AMI VoicemailUsersList and VoicemailUserStatus evidence

Keep an app_voicemail user-list request, an IMAP-specific single-user status request, mailbox counts and downstream message evidence separate.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 VoicemailUsersList and VoicemailUserStatus references, branch-22 VoicemailBoxSummary and MailboxCount references, and official AMI v2 and manager-permission documentation reviewed October 17, 2026; VoicemailUsersList is documented by app_voicemail from Asterisk 1.6 while VoicemailUserStatus is documented by app_voicemail_imap from Asterisk 16, and the generated action pages do not define a shared response schema or make either response proof of message inventory, storage freshness, playback or MWI delivery; installed branch, maintenance release, module, backend, mailbox and context identity, manager permissions, response framing, parser and cache behavior remain deployment specific; no PBX, module, mailbox, voicemail user, store, IMAP account, manager configuration, credential, session, request, response, message, MWI subscription, endpoint, phone, playback or live call was inspected or tested

Asterisk AMI voicemail user list or status is missing, incomplete or wrong

Trace one list or status request through target identity, module ownership, permissions, raw response framing, mailbox context, parsing and cache behavior.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 ConfbridgeListRooms and ConfbridgeList action references, current list-event references, and official ConfBridge, AMI v2 and manager-permission documentation reviewed October 17, 2026; ConfbridgeListRooms reports active conferences and ConfbridgeList reports participants for one specified conference, each as a multi-event response terminated by its documented Complete event; room presence, participant rows, configured bridge, user and menu profiles, dialplan reachability, admission, media, recording and caller experience remain separate evidence boundaries; installed branch, loaded app_confbridge module, conference identifiers, manager permissions, filters, event ordering and live state remain deployment specific; no PBX, module, manager configuration, credential, session, conference, profile, menu, participant, channel, event stream, recording, packet, audio or live call was inspected or tested

Asterisk AMI ConfbridgeListRooms and ConfbridgeList snapshots

Inventory active ConfBridge rooms and the participants in one room without treating configuration, partial event rows or manager visibility as a working conference.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 ConfbridgeListRooms and ConfbridgeList action references, current list-event references, and official ConfBridge, AMI v2 and manager-permission documentation reviewed October 17, 2026; ConfbridgeListRooms reports active conferences and ConfbridgeList reports participants for one specified conference, each as a multi-event response terminated by its documented Complete event; room presence, participant rows, configured bridge, user and menu profiles, dialplan reachability, admission, media, recording and caller experience remain separate evidence boundaries; installed branch, loaded app_confbridge module, conference identifiers, manager permissions, filters, event ordering and live state remain deployment specific; no PBX, module, manager configuration, credential, session, conference, profile, menu, participant, channel, event stream, recording, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge room or participant list is missing, incomplete or stale

Trace one ConfbridgeListRooms or ConfbridgeList transaction through node, module, permission, conference identity, complete framing, filtering and live conference state.

Read guide →
Guide · Current Asterisk branch-23-generated ConfbridgeLock, ConfbridgeUnlock, ConfbridgeMute, ConfbridgeUnmute, ConfbridgeKick, ConfbridgeStartRecord and ConfbridgeStopRecord action references, branch-22 lock and recording references, current recording events, and official ConfBridge AMI, CLI and manager-command documentation reviewed October 17, 2026; an accepted manager action, room lock state, participant mute state, participant membership, recording event, generated path, durable file, captured audio and caller outcome remain separate evidence boundaries; installed branch, loaded app_confbridge module, active conference identity, channel names, manager permissions, event policy, recording directory and filesystem behavior remain deployment specific; no PBX, module, manager account, credential, session, conference, participant, channel, lock, mute, kick, recorder, file, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge moderation and recording controls

Operate ConfBridge lock, mute, kick and recording actions with exact targets, bounded authority and separate response, event, state and outcome evidence.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated ConfbridgeLock, ConfbridgeUnlock, ConfbridgeMute, ConfbridgeUnmute, ConfbridgeKick, ConfbridgeStartRecord and ConfbridgeStopRecord action references, branch-22 lock and recording references, current recording events, and official ConfBridge AMI, CLI and manager-command documentation reviewed October 17, 2026; an accepted manager action, room lock state, participant mute state, participant membership, recording event, generated path, durable file, captured audio and caller outcome remain separate evidence boundaries; installed branch, loaded app_confbridge module, active conference identity, channel names, manager permissions, event policy, recording directory and filesystem behavior remain deployment specific; no PBX, module, manager account, credential, session, conference, participant, channel, lock, mute, kick, recorder, file, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge control is accepted but state does not change

Trace one lock, mute, unmute, kick or recording request through action availability, exact target, response, event, later snapshot and downstream effect.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 ConfbridgeStart, ConfbridgeEnd, ConfbridgeJoin, ConfbridgeLeave and ConfbridgeTalking event references plus official ConfBridge configuration, AMI event and filtering documentation reviewed October 17, 2026; conference lifecycle, participant membership, talk-detection state, channel lifetime, media flow, intelligible speech, audible mixed audio and caller outcome remain separate evidence boundaries; talk_detection_events is a user-profile option that defaults to no, while documented DSP thresholds govern when enabled talking events begin and end; installed branch, loaded app_confbridge module, user profiles, manager class authorization, event filters, reconnect gaps, clocking and live state remain deployment specific; no PBX, module, manager account, credential, session, conference, profile, participant, channel, event stream, packet, audio, speech or live call was inspected or tested

Asterisk AMI ConfBridge lifecycle and talking events

Interpret ConfbridgeStart, Join, Leave, End and Talking as bounded runtime events without turning event presence or absence into media or caller-outcome proof.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 ConfbridgeStart, ConfbridgeEnd, ConfbridgeJoin, ConfbridgeLeave and ConfbridgeTalking event references plus official ConfBridge configuration, AMI event and filtering documentation reviewed October 17, 2026; conference lifecycle, participant membership, talk-detection state, channel lifetime, media flow, intelligible speech, audible mixed audio and caller outcome remain separate evidence boundaries; talk_detection_events is a user-profile option that defaults to no, while documented DSP thresholds govern when enabled talking events begin and end; installed branch, loaded app_confbridge module, user profiles, manager class authorization, event filters, reconnect gaps, clocking and live state remain deployment specific; no PBX, module, manager account, credential, session, conference, profile, participant, channel, event stream, packet, audio, speech or live call was inspected or tested

Asterisk AMI ConfBridge events are missing, out of order or show the wrong talking state

Trace one ConfBridge lifecycle or talking-event disagreement through node, module, profile, authorization, filtering, transport, identity, thresholds and snapshot evidence.

Read guide →
Guide · Current branch-23-generated and branch-22 ConfBridge application and CONFBRIDGE function references plus official ConfBridge concepts, configuration, functions, sound-prompt, res_pjsip and PJSIP_DTMF_MODE documentation reviewed October 17, 2026; static and dynamic bridge, user and menu profiles, selected DTMF transport, collected menu sequence, prompt playback, menu action, conference exit and CONFBRIDGE_RESULT remain separate evidence boundaries; installed branch, generated dialplan and configuration, loaded app_confbridge module, effective channel variables, endpoint DTMF mode, sound packages and runtime conference state remain deployment specific; no PBX, module, dialplan, generated configuration, profile, menu, prompt, sound package, endpoint, channel, DTMF frame, packet, media stream, conference or live call was inspected or tested

Asterisk ConfBridge profiles, menus and exit-result evidence

Separate bridge, user and menu selection, dynamic overrides, DTMF collection, prompt playback, menu action and CONFBRIDGE_RESULT before describing conference behavior.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 ConfBridge application and CONFBRIDGE function references plus official ConfBridge concepts, configuration, functions, sound-prompt, res_pjsip and PJSIP_DTMF_MODE documentation reviewed October 17, 2026; static and dynamic bridge, user and menu profiles, selected DTMF transport, collected menu sequence, prompt playback, menu action, conference exit and CONFBRIDGE_RESULT remain separate evidence boundaries; installed branch, generated dialplan and configuration, loaded app_confbridge module, effective channel variables, endpoint DTMF mode, sound packages and runtime conference state remain deployment specific; no PBX, module, dialplan, generated configuration, profile, menu, prompt, sound package, endpoint, channel, DTMF frame, packet, media stream, conference or live call was inspected or tested

Asterisk ConfBridge menu, prompt or exit result is wrong

Trace one ConfBridge menu or prompt symptom through profile resolution, DTMF receipt, sequence matching, authorization, prompt assets, action execution and application return.

Read guide →
Guide · Current branch-23-generated and branch-22 AMI MixMonitor, MixMonitorMute and StopMixMonitor action references, current MixMonitorStart, MixMonitorMute and MixMonitorStop event references, and current dialplan MixMonitor and StopMixMonitor references reviewed October 17, 2026; AMI request, action response, channel-bound audiohook, start or mute or stop event, filename, open file handle, durable file, decoded audio, retention and caller outcome remain separate evidence boundaries; installed branch, loaded app_mixmonitor module, manager permissions, event filters, channel lifetime, storage, legal basis and generated FreePBX dialplan remain deployment specific; no PBX, module, manager account, credential, session, channel, audiohook, event stream, file, packet, media stream, recording or live call was inspected or tested

Asterisk AMI MixMonitor controls and recording-event evidence

Separate AMI recording requests, channel-scoped audiohooks, start, mute and stop events, file-handle release, stored files, decoded audio and retention outcomes.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 AMI MixMonitor, MixMonitorMute and StopMixMonitor action references, current MixMonitorStart, MixMonitorMute and MixMonitorStop event references, and current dialplan MixMonitor and StopMixMonitor references reviewed October 17, 2026; AMI request, action response, channel-bound audiohook, start or mute or stop event, filename, open file handle, durable file, decoded audio, retention and caller outcome remain separate evidence boundaries; installed branch, loaded app_mixmonitor module, manager permissions, event filters, channel lifetime, storage, legal basis and generated FreePBX dialplan remain deployment specific; no PBX, module, manager account, credential, session, channel, audiohook, event stream, file, packet, media stream, recording or live call was inspected or tested

Asterisk AMI MixMonitor starts but the recording is missing, empty or wrong

Trace one disputed AMI recording through channel identity, action response, start and stop events, options, path, file-handle release, storage, decoding, transfer boundaries and retention.

Read guide →
Guide · Current branch-23-generated and branch-22 AMI Park, ParkedCalls and Parkinglots action references, current ParkedCall, UnParkedCall, ParkedCallGiveUp and ParkedCallTimeOut event references, branch-22 res_parking and ParkedCall application references, and the AMI v2 specification reviewed October 17, 2026; action acceptance, channel identity, parked-state event, snapshot framing, announcement, slot assignment, retrieval, media, timeout routing and caller outcome remain separate evidence boundaries; installed branch, loaded res_parking module, manager permissions, event filters, generated FreePBX configuration, parking lot, dialplan and endpoint behavior remain deployment specific; no PBX, module, config, manager account, session, parking lot, channel, bridge, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI parked-call control, snapshots and lifecycle events

Separate AMI parking requests, exact channel and lot identity, parked-call snapshots, lifecycle events, slot assignment, retrieval, timeout routing and caller outcomes.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 AMI Park, ParkedCalls and Parkinglots action references, current ParkedCall, UnParkedCall, ParkedCallGiveUp and ParkedCallTimeOut event references, branch-22 res_parking and ParkedCall application references, and the AMI v2 specification reviewed October 17, 2026; action acceptance, channel identity, parked-state event, snapshot framing, announcement, slot assignment, retrieval, media, timeout routing and caller outcome remain separate evidence boundaries; installed branch, loaded res_parking module, manager permissions, event filters, generated FreePBX configuration, parking lot, dialplan and endpoint behavior remain deployment specific; no PBX, module, config, manager account, session, parking lot, channel, bridge, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI parked call is missing, in the wrong slot, times out or retrieves incorrectly

Trace one disputed parked call through exact channel identity, action response, list framing, lot and space assignment, lifecycle reason, retrieval selection, timeout routing and media outcome.

Read guide →
Guide · Current branch-23-generated and branch-22 QueueAdd, QueueRemove, QueuePause and QueuePenalty action references, current QueueMemberAdded, QueueMemberRemoved, QueueMemberPenalty and QueueMemberStatus event references, the branch-22 QueueMemberPause event reference, and the AMI v2 specification reviewed October 17, 2026; action response, queue and interface scope, membership event, pause or penalty event, later snapshot, device state, ringing, bridge, answer and caller outcome remain separate evidence boundaries; installed branch, loaded app_queue module, queue strategy, manager permissions and filters, generated FreePBX configuration, persistence and endpoint behavior remain deployment specific; no PBX, module, queue, member, configuration, manager account, session, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue-member add, remove, pause and penalty controls

Scope queue membership, pause and penalty actions to exact queue and interface identities, then verify events, snapshots, eligibility and call outcomes separately.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 QueueAdd, QueueRemove, QueuePause and QueuePenalty action references, current QueueMemberAdded, QueueMemberRemoved, QueueMemberPenalty and QueueMemberStatus event references, the branch-22 QueueMemberPause event reference, and the AMI v2 specification reviewed October 17, 2026; action response, queue and interface scope, membership event, pause or penalty event, later snapshot, device state, ringing, bridge, answer and caller outcome remain separate evidence boundaries; installed branch, loaded app_queue module, queue strategy, manager permissions and filters, generated FreePBX configuration, persistence and endpoint behavior remain deployment specific; no PBX, module, queue, member, configuration, manager account, session, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue-member control is accepted but agent state is wrong

Trace one disputed add, remove, pause or penalty change through exact scope, action response, event visibility, later queue snapshot, eligibility and call outcome.

Read guide →
Guide · Current branch-23-generated and branch-22 QueueReload, QueueRule, QueueReset and QueueStatus action references, the Asterisk queue-log guide, Asterisk 20 upgrade notes, the current official queuerules.conf sample and the AMI v2 specification reviewed October 17, 2026; configuration owner, stored source, generated files, selected reload scope, action response, raw rule result, completed later queue snapshot, statistics, historical logs, active callers and call outcomes remain separate evidence boundaries; the generated action pages do not document defaults for omitted QueueReload subsection fields or a QueueRule row and completion schema, so neither is invented; no PBX, module, queue, configuration, manager account, session, rule, statistic, report, caller, member, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue reload, rule inspection and statistics-reset controls

Scope QueueReload subsections, inspect named queue rules and treat QueueReset as an explicit statistics operation with separate runtime, history and call-outcome verification.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 QueueReload, QueueRule, QueueReset and QueueStatus action references, the Asterisk queue-log guide, Asterisk 20 upgrade notes, the current official queuerules.conf sample and the AMI v2 specification reviewed October 17, 2026; configuration owner, stored source, generated files, selected reload scope, action response, raw rule result, completed later queue snapshot, statistics, historical logs, active callers and call outcomes remain separate evidence boundaries; the generated action pages do not document defaults for omitted QueueReload subsection fields or a QueueRule row and completion schema, so neither is invented; no PBX, module, queue, configuration, manager account, session, rule, statistic, report, caller, member, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue reload or reset is accepted but state is wrong

Trace one disputed QueueReload, QueueRule or QueueReset transaction through exact scope, source and generated configuration, raw framing, later queue state, statistics and retained history.

Read guide →
Guide · Current branch-23-generated and branch-22 QueueChangePriorityCaller, QueueWithdrawCaller, QueueEntry and QueueStatus references, current QueueCallerJoin, QueueCallerLeave and QueueCallerAbandon event references, Asterisk 20 upgrade notes, the queue-log guide and the AMI v2 specification reviewed October 17, 2026; queue name, live channel identity, action response, later snapshot, lifecycle event, dialplan continuation, withdrawal data, historical record and caller outcome remain separate evidence boundaries; no default, range or persistence is inferred where the generated action pages do not document one; no PBX, module, queue, manager account, session, caller, channel, dialplan, event stream, log, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue caller priority and withdrawal controls

Change one waiting caller priority or request withdrawal with exact queue and channel identity, then verify response, later position, dialplan continuation and caller outcome separately.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 QueueChangePriorityCaller, QueueWithdrawCaller, QueueEntry and QueueStatus references, current QueueCallerJoin, QueueCallerLeave and QueueCallerAbandon event references, Asterisk 20 upgrade notes, the queue-log guide and the AMI v2 specification reviewed October 17, 2026; queue name, live channel identity, action response, later snapshot, lifecycle event, dialplan continuation, withdrawal data, historical record and caller outcome remain separate evidence boundaries; no default, range or persistence is inferred where the generated action pages do not document one; no PBX, module, queue, manager account, session, caller, channel, dialplan, event stream, log, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue caller priority or withdrawal does not take effect

Trace one disputed caller-control transaction through exact live channel identity, action response, completed later snapshot, asynchronous lifecycle, dialplan return and historical evidence.

Read guide →
Guide · Current branch-23-generated and branch-22 AMI QueueLog action and dialplan QueueLog application references, the official queue-log operation guide and AMI v2 specification reviewed October 17, 2026; request acceptance, the supplied identifiers, serialized row, active `queue_log` file, rotated files, alternate backends, parser ingestion, report visibility and the underlying call or agent event remain separate evidence boundaries; the generated action pages describe only ActionID and publish no field-validation, escaping, persistence, delivery or reporting guarantee; no PBX, module, manager account, session, queue, caller, member, log file, database, parser, report, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI QueueLog custom events and queue-log evidence

Add one explicitly identified custom queue-log entry, then verify request acceptance, serialized fields, storage, ingestion and reporting as separate facts.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 AMI QueueLog action and dialplan QueueLog application references, the official queue-log operation guide and AMI v2 specification reviewed October 17, 2026; request acceptance, the supplied identifiers, serialized row, active `queue_log` file, rotated files, alternate backends, parser ingestion, report visibility and the underlying call or agent event remain separate evidence boundaries; the generated action pages describe only ActionID and publish no field-validation, escaping, persistence, delivery or reporting guarantee; no PBX, module, manager account, session, queue, caller, member, log file, database, parser, report, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI QueueLog accepted but entry is missing or wrong

Trace one custom queue-log write through node identity, AMI response, exact serialized row, active and rotated storage, ingestion and reporting.

Read guide →
Asterisk · Current first-party Asterisk security-framework, logging, command, configuration and source evidence reviewed October 18, 2026. Security-event generation, res_security_log module state, dynamic SECURITY level registration, logger channel configuration, destination path, file write, rotation, downstream parser, alert and enforcement action remain separate evidence. A security event is not by itself proof of compromise, and a written record is not proof of a ban or alert. No host, module, logger channel, file, permission, event, parser, firewall, packet, account or call was inspected or tested

Asterisk security-event logging: generation, channel and custody evidence

Trace a security event from the producing subsystem through res_security_log, the dynamic SECURITY level, logger channel, file custody, rotation and downstream consumers.

Read guide →
Troubleshooting · Current first-party Asterisk security-framework, logging, command, configuration and source evidence reviewed October 18, 2026. Security-event generation, res_security_log module state, dynamic SECURITY level registration, logger channel configuration, destination path, file write, rotation, downstream parser, alert and enforcement action remain separate evidence. A security event is not by itself proof of compromise, and a written record is not proof of a ban or alert. No host, module, logger channel, file, permission, event, parser, firewall, packet, account or call was inspected or tested

Asterisk security events are missing, too noisy or not reaching enforcement

Separate event generation, res_security_log state, dynamic logging level, channel path, file custody, rotation, parser, alert and defensive action.

Read guide →