I created a set of Docker images running Asterisk and exposing AMI / ARI ports that i found to be quite useful for ARI / AMI development and regression.
As they are based on Docker with whaleware, adding new configuration files to roll your own dialplan / queues / voicemail etc is pretty easy. And you can run quite a lot on the same box to simulate clusters.
There is no SIP / RTP configured at the moment.
Maybe somebody else might find them useful. There is Asterisk 1.8, 11, 12 and 13. Thanks l.
Is there a mapping of AMI versions to Asterisk versions somewhere? For example, Asterisk 1.4 includes AMI version 1.0 (at least that's what I see when I connect to Ast 1.4 via telnet to the AMI port)
Also, doe the AMI version changes reflect changes to the AMI commands? If so, is there also a list of what commands changed by AMI version?
Is it possible to detect the failure of an agent to register with Asterisk via the AMI ?
When I try to register with Asterisk 1.4 using an invalid password I don't see any event in the AMI, but see this in the messages log:
[2013-10-05 22:05:03] NOTICE chan_sip.c: Registration from '"test"
Hello, i'm using AMI Originate action (with async=true) to send outgoing calls to a SIP trunk (using asterisk-java library to connect to AMI).
The problem is that in case of failed originate, OriginateResponse event is returning only the reason code which is sometimes not sufficient to determine the real cause of failure. Also, there's no way to link between the channel that was trying to dial and failed and the original Originate request, because OriginateResponse is issued only after the failed channel was hang up. Only successful OriginateResponse will contain the unique id of the established channel.
Is there any way that…
We're using Asterisk 1.8.0 to run a call centre. There is a Java process which talks to Asterisk through AMI, which is part of the software stack that presents a user interface to the call centre agents.
We're seeing a strange issue with AMI. Most of the time, it doesn't cause problems, because the Java code is written to cope with it, but occasionally it does, and, in rare cases, may even result in calls being dropped.
The main problem with the issue is that we haven't been able to reproduce it in a test environment, and that it's not that easy…
While doing a security audit on a system I maintain, I stumbled upon an unvalidated use of a variable to compose an Originate request to the local Asterisk instance via AMI. Taking as an example an earlier exploit for FreePBX, I realized that this, combined with Application: System as an injected value, could allow arbitrary code execution. I am in the process of fixing all instances of this bug in our system. However, there are third parties that plug into our system, and that reconfigure the manager.conf file to allow remote access to AMI logins that allow Originate (by default,…
Hi all, I have been playing with the AMI quite a bit lately - mostly debugging WombatDialer in production, but that's a different story - and I have been frustrated by the lack of a simple way to interact CLI-like with the AMI
itself. So I have decided to write something myself to make my life easier, or at least a bit less miserable.
The result is a little webapp that you can use as a sort of CLI-frontend to the AMI itself. It is not pretty, but pretty much effective. So I thought I could share it and make someone…
I write some php code in AMI to working with asterisk command. I don't know exactly what is the different between AMI and agi and witch one is better for my planning. Im planning to call party users that their number is is my panel on web. We have some operator and they can call party users via client softphone by clicking on their number, so they have to limited to call just listed number and restrict to call another number. how can do permission to this plan? and how can get stored call record in asterisk (IVR recorded voice)…
I have encountered a problem on an Ast 1.8 install where the AMI interface works fine (I can login and issues command to AMI directly using telnet), but when I use the JAMI/JAMA interface it fails. Using curl (HTTP) I can login fine to the JAMI, but as soon as I issue a second command it fails (despite saving session cookies and extending the httptimeout on the Asterisk side).
The two JAMI commands (login, then ping) are issued within 3 seconds of one another, so this should succeed (and it does on some other test systems). I read about this bug…
I want to track the number of calls up at any given time, through the AMI. I found the Link and Unlink commands as the most likely candidates - is that the right way?
Also, a comment on the wiki suggests that Link may be called several times for a single bridge if transcoding is required. That blows up accuracy of my count of course...