Re: AMI or ARI?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



IMHO the ARI approach is the right one.  I've done something similar with ARI, ZeroMQ and PHP for an answering service.  Works very well.

Phil M

On Jul 25, 2015 6:04 AM, "Shahid H" <shahidh@xxxxxxxxx> wrote:
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@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev

_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev

[Index of Archives]     [Asterisk SS7]     [Asterisk Announcements]     [Asterisk Users]     [PJ SIP]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Linux API]

  Powered by Linux