Mapping ARI events to imperative call flows

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

 



Alistair Cunningham wrote:

> If implementing this using ARI, we're going to get events such as 
> PlaybackFinished, ChannelDtmfReceived, and Hangup. When this happens, 
> how do we know where we are in the call flow and what to do next? 
> Several options spring to mind:

The great thing about ARI is that any of those methods could work. You
can use whatever is appropriate for you and your team.

Since the ARI interface is inherently asynchronous and event driven,
you'll probably find an event driven state machine easier to deal
with. But there's no reason why it has to be that way.

It will be interesting to see how apps get coded up as people start
really using the API.

-- 
David M. Lee
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at:  www.digium.com  & www.asterisk.org




[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