asterisk users - Aug 2010 - How to track a call result originated from originate AMI command

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 command to generate a call but I m
very confuse that I cannot able to track my
call.


The AMI events were very confusing and I m getting various events with
different uniqueid value.
For a single call I m getting events with four or five uniqueid.
I also filtered using specific channel but also I m getting events with
different uniqueid.


How can I find the below status for the call generated using originate
command through AMI events,
1. Answer
2. No Answer
3. Busy


Can any one help me for this.


Thanks,


Thiyagu VOIP
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100808/8bcd3073/attachment.htm

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, and unfortunately you have to rewrite most of your code for
every new release!

And regarding your question, I recommend you to use AGI for monitoring here
is some tips for you

   - in originate command use extension as destination.
   - create "failed" extension in same context.
   - you can include some variables in originate command which can be used
   later in dialplan.
   - use AGI scripts in "destination" and "failed"
extensions to get and
   save call status in database.

Regards

On Sun, Aug 8, 2010 at 6:10 PM, thiyagu venkatesan
<thiyagu.voip at gmail.com>wrote:
> 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 command to generate a call but I m
> very confuse that I cannot able to track my
> call.
>
>
> The AMI events were very confusing and I m getting various events with
> different uniqueid value.
> For a single call I m getting events with four or five uniqueid.
> I also filtered using specific channel but also I m getting events with
> different uniqueid.
>
>
> How can I find the below status for the call generated using originate
> command through AMI events,
> 1. Answer
> 2. No Answer
> 3. Busy
>
>
> Can any one help me for this.
>
>
> Thanks,
>
>
> Thiyagu VOIP
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>


-- 
Nasir Iqbal

ICT Innovations
http://www.ictinnovations.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100808/66731e90/attachment.htm

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 extension to
track hang ups. We set an action token variable to a unique value for each
originate and all the user events have this token so we can tie them back to the
original originate. We turn off most AMI read message classes to cut down on
packet volume.
-- 
Jim Dickenson
mailto:dickenson at cfmc.com

CfMC
http://www.cfmc.com/



On Aug 8, 2010, at 7:18 AM, Nasir Iqbal wrote:
> 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, and
unfortunately you have to rewrite most of your code for every new release!
> 
> And regarding your question, I recommend you to use AGI for monitoring here
is some tips for you
> in originate command use extension as destination.
> create "failed" extension in same context.
> you can include some variables in originate command which can be used later
in dialplan.
> use AGI scripts in "destination" and "failed"
extensions to get and save call status in database.
> Regards
> 
> On Sun, Aug 8, 2010 at 6:10 PM, thiyagu venkatesan <thiyagu.voip at
gmail.com> wrote:
> 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 command to generate a call but I m
very confuse that I cannot able to track my
> call.
> 
> 
> The AMI events were very confusing and I m getting various events with
different uniqueid value.
> For a single call I m getting events with four or five uniqueid.
> I also filtered using specific channel but also I m getting events with
different uniqueid.
> 
> 
> How can I find the below status for the call generated using originate
command through AMI events,
> 1. Answer
> 2. No Answer
> 3. Busy
> 
> 
> Can any one help me for this.
> 
> 
> Thanks,
> 
> 
> Thiyagu VOIP
> 
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> 
> 
> -- 
> Nasir Iqbal
> 
> ICT Innovations
> http://www.ictinnovations.com/
> 
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100808/3f7868f8/attachment.htm

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 <nasir at ictinnovations.com>
> 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, and unfortunately you have to rewrite most of your code for
> every new release!
>
> And regarding your question, I recommend you to use AGI for monitoring here
> is some tips for you
>
>    - in originate command use extension as destination.
>    - create "failed" extension in same context.
>    - you can include some variables in originate command which can be used
>    later in dialplan.
>    - use AGI scripts in "destination" and "failed"
extensions to get and
>    save call status in database.
>
> Regards
>

-- 
Loway - home of QueueMetrics - http://queuemetrics.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100809/f6b7e42a/attachment.htm