Hello Dan et al;
Thanks - Glen
Okay - what I want to do:
1. discover what functionality that the Asterisk 12 REST/AMI has - what would be the best way to do that please? I see the Wiki on Digium/Asterisk, but maybe I am looking in the wrong spots. It does not seem to be clear. Once I discover what it is capable of, then I can decide if I can use it with what we need to do.
2. Asterisk 12 - I noticed that the CLI commands seem to be a whole new 'language' almost. Is there a way to keep the old Asterisk 11 style and before CLI commands?
I think this is a good start for me.
Thanks - Glen
On 29 January 2014 09:14, Daniel Jenkins <dan.jenkins88@xxxxxxxxx> wrote:
On Wed, Jan 29, 2014 at 1:33 PM, Glen Millard <glenmillard@xxxxxxxxx> wrote:
Hello Folks;Hi Glenn,I am using Asterisk 11 and I'm wondering if there is some sort of API available for it? I know there is one for Asterisk 12, but I am not ready to upgrade at the moment.If I wanted to use some sort of API (Rest or otherwise) what are my options with Asterisk 11?Asterisk 11 doesn't have any of the the new ARI interface within it, Asterisk 11 has the AMI/AGI and AMI over HTTP interfaces.If I have to update to v12, I would want to continue using chan_sip as I don't really have the time for the learning curve to learn the new SIP stack at the moment.That's entirely possible! You don't have to use pjsip, chan_sip is still entirely there; just know that new features are much more likely to hit pjsip than chan_sipAny suggestions would be helpful.What kind of application are you planning on building? It may be that the ARI as it stands today wouldn't really work for you anyway - it's not full of "asterisk got a call in a queue" and "that calls now been answered by extension Y", it's designed to start being able to write a replacement for app_queue so that you can write your own business logic into a queueing mechanism. I hope in the future we get a nicer interface into some of the information the AMI gives you, but this isn't what the ARI gives right now.There are projects out there to help you with talking to the AMI, some of which probably put an HTTP interface on top of it, Asterisk even does this, but in my experience a REST HTTP interface is right for some things and just wouldn't work for others, which is why the ARI also utilises websockets.If you want any more advice, maybe you could let us know what kind of thing you'd be looking to build?Thanks - GlenDan_______________________________________________
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
