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

Asterisk AMI bridge-technology inventory, suspend and unsuspend evidence

Inventory registered bridge technologies and bound suspend or unsuspend changes to future bridge selection without treating action acceptance as proof of active-bridge, media or call behavior.

Reviewed 2026-10-28Current branch-23-generated and Asterisk 22 BridgeTechnologyList, BridgeTechnologySuspend and BridgeTechnologyUnsuspend action documentation, current bridge-core source, BridgeList, BridgeInfo, bridge concepts, AMI v2 and network-security guidance were reviewed October 28, 2026; installed Asterisk and FreePBX versions, downstream patches, compiled and loaded bridge modules, registered technology names, capabilities, priorities, suspension state, manager permissions, active bridges, channel membership, media topology and call outcomes remain deployment-specific; no PBX, FreePBX system, module, bridge technology, manager account, credential, bridge, channel, packet, media frame, endpoint or live call was inspected or testedAdvancedDocumentation based · not lab tested

Establish node, release and change authority first

Record the responding node, exact Asterisk branch and maintenance release, package or build provenance, process start time, loaded bridge modules, authenticated manager identity, action permissions and local and UTC time. Preserve the requested technology name exactly as returned; do not substitute a module filename, bridge type, application label or assumed media mode.

BridgeTechnologyList, BridgeTechnologySuspend and BridgeTechnologyUnsuspend have existed since Asterisk 12. Their presence in current and Asterisk 22 generated documentation is interface evidence, not proof that a particular compiled or loaded technology exists on one host.

Close the inventory with the actual list boundary

Action: BridgeTechnologyList accepts an optional ActionID. The current bridge-core source begins a list, emits BridgeTechnologyListItem frames and ends with BridgeTechnologyListComplete; each item includes BridgeTechnology, BridgeType, BridgePriority and BridgeSuspended, while the terminal frame reports ListItems.

Retain the initial response, every item and the matching terminal event under one ActionID. A first row, manager success response, socket quiet interval or collector timeout is not a completed inventory. Preserve unknown fields because later maintenance releases may add them.

Interpret names, capabilities, priority and suspension separately

BridgeTechnology is the registered implementation name. BridgeType describes advertised capabilities, BridgePriority is the selection preference exposed by the inventory, and BridgeSuspended is the current consideration state. None of those fields alone identifies an application, a bridge instance, its channels or its media path.

Several technologies can be eligible for a requested bridge. Selection depends on the bridge requirements and available implementations; a higher-looking priority is not a promise that every future bridge will use that technology.

Bound suspend and unsuspend to future bridge creation

BridgeTechnologySuspend takes one exact BridgeTechnology and marks it suspended, preventing subsequently created bridges from using it. The Asterisk bridging documentation explicitly says existing bridges using that technology are not affected. BridgeTechnologyUnsuspend makes the technology eligible for consideration again for subsequently created bridges.

Neither action moves an existing bridge, requires a named replacement, restarts a module, drains calls or proves that a later bridge can be created. Action acceptance, the changed inventory flag and an observed new bridge remain separate evidence.

Verify configuration state and runtime bridge state independently

After an authorized change, repeat a complete BridgeTechnologyList transaction and compare the exact technology row. Use BridgeList or BridgeInfo only for separately bounded bridge-instance observations, retaining bridge unique ID, reported technology, type, channel membership and timestamp.

An existing bridge that retains the suspended technology is expected behavior, not evidence that suspension failed. A later bridge using a different technology shows one runtime selection; it does not prove media flowed, features worked, endpoints heard audio or the call completed.

Change narrowly and disclose the untested boundary

Use a dedicated, source-restricted AMI identity with only the required manager classes. Capture a pre-change completed inventory, one approved mutation, its response, a post-change completed inventory and any separately authorized new-bridge observation. Have a rollback owner and avoid changing the last eligible technology for required bridge capabilities without a maintenance plan.

No PBX, FreePBX system, module, bridge technology, manager account, credential, bridge, channel, packet, media frame, endpoint or live call was inspected or tested. Documentation and source review do not establish deployment availability, compatibility, safe fallback or laboratory validation.

Sources & applicability

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

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

Continue your research

Hub

Asterisk

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

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

Asterisk AMI, ARI and AGI: choose the control boundary

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

Read guide →
Guide · 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 →
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 →
Guide · Current first-party Asterisk ARI bridge, mixing, holding, operations, event-model and recording documentation reviewed October 9, 2026; no HTTP server, ARI user, Stasis application, bridge, channel, endpoint, socket, packet, media frame, playback, recording, DTMF result or call was inspected or tested

Asterisk ARI bridges: ownership, membership and media topology

Choose a mixing or holding bridge deliberately, keep it inside the intended Stasis application and prove channel membership separately from media behavior.

Read guide →
Guide · Operational guidance; Asterisk 22 / FreePBX 17 where applicable

Least privilege for PBX users and integrations

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

Read guide →
Troubleshooting · Current branch-23-generated and Asterisk 22 BridgeTechnologyList, BridgeTechnologySuspend and BridgeTechnologyUnsuspend action documentation, current bridge-core source, BridgeList, BridgeInfo, bridge concepts, AMI v2 and network-security guidance were reviewed October 28, 2026; installed Asterisk and FreePBX versions, downstream patches, compiled and loaded bridge modules, registered technology names, capabilities, priorities, suspension state, manager permissions, active bridges, channel membership, media topology and call outcomes remain deployment-specific; no PBX, FreePBX system, module, bridge technology, manager account, credential, bridge, channel, packet, media frame, endpoint or live call was inspected or tested

Asterisk AMI bridge technology is missing, suspended or selects differently

Trace one bridge-technology contradiction through release, module registration, manager framing, exact technology identity, suspension state, capability requirements and a separately observed bridge instance.

Read guide →