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

Asterisk AMI AOCMessage uses the wrong channel or charge, or no AOC event appears

Find the first divergence across manager framing, live channel identity, message phase, units or currency encoding, AOC event delivery, signaling support and remote presentation.

Reviewed 2026-10-26Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 AOCMessage references, current and Asterisk 22 AOC-S, AOC-D and AOC-E event references, and the AMI v2 specification were reviewed October 26, 2026; installed release, channel technology, channel identity, driver support, Advice of Charge signaling, rating authority, currency and unit policy, manager permissions, event delivery and remote presentation remain deployment-specific; no PBX, manager session, action, channel, charge, tariff, bill, carrier, endpoint, packet, signaling exchange, display or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one action and one symptom

Record node, release, manager identity and authority, ActionID, exact Channel or ChannelPrefix, live channel inventory, Uniqueid, MsgType, charge fields, raw response, AOC event stream, call phase and authorized downstream observation. Redact subscriber, association and monetary data in routine logs.

Classify the first symptom as rejected action, missing channel, wrong first prefix match, invalid phase fields, wrong units, wrong currency scale, no AOC event, event on a different channel, protocol not sent, remote rejection or display mismatch.

Resolve the target before changing charge fields

Re-enumerate the live channel and verify its complete name and Uniqueid immediately before sending. If ChannelPrefix was used, list every current prefix match and confirm which first match Asterisk selected. Never repair ambiguity by lengthening a guessed prefix while calls are changing.

A channel may rename, optimize away, transfer or end between discovery and control. Rebuild the current identity map; do not use Linkedid or caller ID as proof of the exact leg.

Validate the message-type contract

Check MsgType first. AOC-S rate fields belong to one or more ChargedItem groups. AOC-D and AOC-E use ChargeType, with currency and unit requirements. A field that is meaningful for one phase must not be interpreted as evidence for another.

For AOC-D, confirm Total versus SubTotal and the limited billing-ID set. For AOC-E, preserve the optional charging-association ID or number and plan as distinct fields instead of merging them into a subscriber label.

Recalculate units, currency and scales exactly

For unit charging, confirm contiguous intended indices, the required index-zero amount and each optional unit type. For currency charging, record the positive integer amount, multiplier and the post-truncation currency name separately. Do not compare a rendered decimal until the raw amount and multiplier agree.

For AOC-S duration, verify Time, TimeScale, ChargingType and any valid step-function Granularity pair. For volume or special-code rates, verify the required unit or code rather than substituting a duration field.

Separate AOC event delivery from remote presentation

Match the expected AOC-S, AOC-D or AOC-E event to the exact channel identity and time. If the action succeeds but the event is absent, inspect manager read class, event selection, filters, parser framing and reconnect gaps before altering call logic.

An event is Asterisk-side evidence that the AOC message was sent; it is not carrier acknowledgement, endpoint display proof or invoice validation. Continue through channel-driver and protocol evidence only where policy permits, then inspect the intended device or charging consumer separately.

Repair the first proved boundary and retest once

Correct only the first demonstrated fault: manager authority, framing, current channel identity, prefix ambiguity, MsgType, field group, unit index, amount, multiplier, total type, association data, event subscription, driver support or downstream presentation. Preserve the authorized charging source; do not improvise tariffs.

Retest with one disposable call plus a wrong-channel and invalid-field negative control. Remove temporary captures and retain sanitized evidence. No PBX, channel, charge, tariff, event, packet, endpoint, display, invoice or live call was inspected or tested.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 AOCMessage references, current and Asterisk 22 AOC-S, AOC-D and AOC-E event references, and the AMI v2 specification were reviewed October 26, 2026; installed release, channel technology, channel identity, driver support, Advice of Charge signaling, rating authority, currency and unit policy, manager permissions, event delivery and remote presentation remain deployment-specific; no PBX, manager session, action, channel, charge, tariff, bill, carrier, endpoint, packet, signaling exchange, display or live call was inspected or tested

Asterisk AMI AOCMessage: charge, channel and event evidence

Generate Advice of Charge signaling without confusing channel selection, AOC-S, AOC-D or AOC-E structure, encoded units or currency, AMI acceptance, AOC events, remote presentation or billing authority.

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 Latest API CHANNEL_EXISTS, CHANNELS and CHANNEL references, CLI channel-operation and Local-channel optimization documentation, AMI CoreShowChannels surfaces and the upstream func_channel implementation were reviewed October 19, 2026. The generated API pages reported branch 23; installed branch, loaded modules, channel drivers, names, unique IDs, linked IDs, Local optimization, permissions, timing and call outcomes remain deployment specific. No PBX, module, dialplan, channel, bridge, manager session, packet, media stream or live call was inspected or tested

Asterisk channel inventory, identity and lifetime

Treat a channel list as a changing observation, distinguish name from unique identity, and revalidate the exact leg before an authorized operation.

Read guide →
Troubleshooting · Current Asterisk Latest API CHANNEL_EXISTS, CHANNELS and CHANNEL references, CLI channel-operation and Local-channel optimization documentation, AMI CoreShowChannels surfaces and the upstream func_channel implementation were reviewed October 19, 2026. The generated API pages reported branch 23; installed branch, loaded modules, channel drivers, names, unique IDs, linked IDs, Local optimization, permissions, timing and call outcomes remain deployment specific. No PBX, module, dialplan, channel, bridge, manager session, packet, media stream or live call was inspected or tested

Asterisk channel exists, then disappears or maps to the wrong call

Freeze one observation window, distinguish channel name, Uniqueid and Linkedid, then locate creation, rename, Local optimization, bridge change or hangup.

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 · Operational guidance; Asterisk 22 / FreePBX 17 where applicable

Least privilege for PBX users and integrations

Separate the right to register, place calls, administer the PBX and read sensitive data.

Read guide →
Hub

VoIP troubleshooting

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

Explore topic →