That was exactly what I was lamenting - that some common distros do not send
every event, so that AMI ends up being less than reliable. If AMi sends all
events, then it's really trivial to track calls :)
l.
2010/8/9 Motiejus Jakštys desired@gmail.com
On Mon, Aug 9, 2010 at 12:08 PM, Lenz
BTW, using the most common Asterisk distros out there that happen to sport a
very complex dialplan, we see a lot of lost events, so that tracking calls
on the basis of AMI observation alone becomes practically impossible.
:-(
l.
2010/8/8 Nasir Iqbal na...@ictinnovations.com
Hi,
On Mon, Aug 9, 2010 at 12:08 PM, Lenz Emilitri lenz.lo...@gmail.com wrote:
BTW, using the most common Asterisk distros out there that happen to sport a
very complex dialplan, we see a lot of lost events, so that tracking calls
on the basis of AMI observation alone becomes practically
Hi All,
I want to track a call that is originated using originate AMI command
through AstManProxy server.
I m using AstManProxy server and I developed an AstManProxy client.
By using my AstManClient program I can able to login AstManProxy server.
Now I can able to issue/send originate
Hi,
Confusing! you are not alone here. Actually there is no unified
development approach exist in Asterisk, every module, application introduce
a new way to handle same things!! And the monitoring is most difficult
part! you have to write different parsing algos to get each bit of
information,
We track status of calls and many other actions using user events in our
dialplan. The dial and queue commands allow for either agi or macros to be
executed just before a connection is made. Use option g in dial to allow one to
execute a user event after the dial command finishes. Use the h
