[asterisk-app-dev] AMI or ARI?

Shahid H shahidh at gmail.com
Sat Jul 25 10:47:08 CDT 2015


Is it possible to use ChanSpy and AMD in ARI?

On Sat, Jul 25, 2015 at 3:27 PM, Ludovic Gasc <gmludo at gmail.com> wrote:

> We made a predictive dialer for some clients, our stack is based on
> Python, AsyncIO, API-Hour and Panoramisk.
> Instead of AMI, we use dialplan and FastAGI to track calls, because it's
> easier to have a context and to be async and multi-worker in the same time,
> for the best performances.
> We made a lot of daemons with AMI only, it was often complicated to track
> calls, even with CEL events and linkedid that helps a lot for that.
>
> I don't know if node.js is multiworker, however, it should be enough
> efficient for a size of callcenter like that.
>
> About AMI/ARI debate, AMI should be a little bit more efficient that ARI,
> however, I never benchmarked that.
> ARI is more consistent and if I understand correctly, some stuff are
> possible only with ARI.
> If you have no existing code, you can start with ARI easily.
>
> Have a nice week-end.
> --
> Ludovic Gasc (GMLudo)
> http://www.gmludo.eu/
>
> 2015-07-25 12:03 GMT+02:00 Shahid H <shahidh at gmail.com>:
>
>> Hi,
>>
>> I like to develop a predictive dialer system (Web base) to allow Admin to
>> create outbound or inbound campaigns
>>
>> I'm doing some technical research and I am trying to figure out shall I
>> use AMI or ARI?
>>
>> - Creating many outbound calls and monitor live calls on the web
>> (Ringing, Talking, Hang up their call)
>> - Originate many calls and put in specific queue (other word: campaign)
>> - Agent should be able to transfer a call - external or internal.
>> - Ability to set max ring time for each campaign
>> - Approx 300+ agents
>>
>> On the browser, I would like to use websocket to get real time
>> information about the call and actions.
>>
>> I am considering going with this approach: create a daemon with Node.js -
>> A daemon will connect to Asterisk via ARI and a daemon use websocket to
>> listen the events and such. A browser will also use websocket to
>> communicate with a Node.js daemon.
>>
>> Something like that: <browser (websocket)> --- <Node.js daemon & ARI
>> (websocket)> --- <Asterisk>
>>
>> Is this good approach?
>>
>> Thanks
>>
>> _______________________________________________
>> asterisk-app-dev mailing list
>> asterisk-app-dev at lists.digium.com
>> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
>>
>>
>
> _______________________________________________
> asterisk-app-dev mailing list
> asterisk-app-dev at lists.digium.com
> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20150725/34a9046e/attachment.html>


More information about the asterisk-app-dev mailing list