[asterisk-users] How to get call progress events from WebSocket connected to Asterisk 12 ARI events API
Jim Fathman
jfathman at esi-estech.com
Thu Sep 12 10:21:56 CDT 2013
Joshua,
Thanks, I am really looking forward to the new REST API support. I know it
will take a while to get all the pieces in place.
I don't know what the Digium vision is for the REST API, but what I would
like to see is a simple WebSocket connection that can receive granular
events for all the call activity on the Asterisk server. This would allow
a Node.js application to know everything that is happening so it could
support UC web apps that also connect to the Node.js server.
If the ARI has enough granularity to let the Node.js application make
real-time call control decisions and manage call progress and features,
then the Asterisk servers(s) could be used as SIP and media edge devices
with third party call control running on the Node.js platform.
Jim
On Thu, Sep 12, 2013 at 10:07 AM, Joshua Colp <jcolp at digium.com> wrote:
> Jim Fathman wrote:
>
>> Hello,
>>
>
> Bonjour!
>
>
> I am experimenting with Asterisk 12.0.0 alpha1. I have a couple of SIP
>> phones working. Good. I can retrieve data using curl to interact with
>> the new Asterisk REST API (ARI). Good.
>>
>> Now I want to use the new ARI events API, which requires a WebSocket
>> connection. I am using Node.js for the client, and have a stable
>> connection to ARI events on the Asterisk 12 server.
>>
>> What I hope for is that my Node.js client will receive call related
>> events in JSON format messages as call activity occurs on the Asterisk
>> server. But I don't know how to request this information via the API.
>>
>> Do I need to specify something in the query string used for the initial
>> WebSocket connection? Or do I need to send some kind of event
>> subscription messages within the WebSocket once connected?
>>
>
> David Lee (ARI man supreme) is currently working on an issue [1] which
> covers support for subscribing for this information for delivery over the
> WebSocket connection in a branch [2]. I'd expect this to be integrated into
> 12 within a few weeks. I believe it should cover what you want to do.
>
> [1] https://issues.asterisk.org/**jira/browse/ASTERISK-22451<https://issues.asterisk.org/jira/browse/ASTERISK-22451>
> [2] http://svn.digium.com/svn/**asterisk/team/dlee/ASTERISK-**
> 22451-ari-subscribe/<http://svn.digium.com/svn/asterisk/team/dlee/ASTERISK-22451-ari-subscribe/>
>
> Cheers,
>
> --
> Joshua Colp
> Digium, Inc. | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at: www.digium.com & www.asterisk.org
>
> --
> ______________________________**______________________________**_________
> -- 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<http://lists.digium.com/mailman/listinfo/asterisk-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130912/f66bd1d8/attachment.htm>
More information about the asterisk-users
mailing list