AMI (Asterisk Manager Interface)

AMI stands for the Asterisk Manager Interface. It is the door through which outside software talks to Asterisk, the phone engine that runs VICIdial. Through AMI, a program can listen to a live stream of events, such as a call starting or ending, and it can also send commands back, like "start this call" or "hang that one up." Think of it as a control room window into the phone system: you can both see what is happening and reach in to make things happen.

VICIdial leans on AMI heavily. When the dialer decides to place a call, it sends an originate command over AMI to Asterisk. When a call connects or drops, AMI reports the event, including details like the Channel name, the Asterisk uniqueid of the call, and the Hangup cause that explains why it ended. The dialer reads all of this in real time to keep its screens, counters, and reports accurate. Without AMI, VICIdial would be flying blind, guessing at what the phone engine was doing.

AMI versus other interfaces

AMI is the older, text-based control channel. A newer option called ARI, the Asterisk REST Interface, gives developers a more modern way to build custom call logic from outside code. They are not rivals so much as different tools: AMI is great for monitoring events and firing simple commands, while ARI (Asterisk REST Interface) shines when you want fine-grained control over a single call's path. The Non-agent API in VICIdial sits on top of these layers to let outside systems trigger actions without anyone touching the phone engine directly.

You will rarely log into AMI by hand, but it is worth knowing it exists. If a custom integration or a transfer feature misbehaves, the AMI event log is often where the truth lives. A blocked AMI account, a wrong password, or a firewall closing the AMI port is a classic reason a dialer suddenly cannot place calls even though everything else looks fine.