[asterisk-dev] Unified Asterisk Interface

[Jim Capp]

So, in other words, you are suggesting we write a core Asterisk app 
rather than using the AGI?

This makes sense, but it is a little scary.  I like the separation of 
AGI and AMI from Asterisk.
It allows us to build things without encumbering the server itself.

Can you recommend an app to take a look at as an example, something that 
a seasoned C programmer would be able to fathom while trying to learn 
Asterisk's core call handling?

Thanks,

Jim


Steven Critchfield wrote:
> On Mon, 2007-12-10 at 17:40 +0100, David Roden wrote:
>   
>> On Monday 10 December 2007 17:16:56 Jim Capp wrote:
>>
>>     
>>> Please check out the "asterisk-java" project:
>>>       
>> I am already using that. :)
>>
>> While it does indeed keep the low-level stuff away from me I still have to 
>> worry about synchronization issues between the two APIs in use. I wrote my 
>> own layer above asterisk-java so that at least these two APIs are hidden from 
>> my application but--as I said--I'd prefer if there was The One Asterisk API I 
>> could use instead. :)
>>
>> Would it be hard to include AMI commands like "ReadDTMF" that trigger 
>> DTMFReadEvents or DTMFReadResponses as soon as the user pressed a key?
>>     
>
> So here is an interesting thought for those who want to essentially
> rewrite core functionality, You have the source and can rewite the core.
>
> I'll quickly appologise for what looks like a flaming start to the
> message, it is meant to be taken with no attitude and as just a flat
> statement of fact.
>
> If you want access to the core call handling like AGI, why not create
> your app down in the core of asterisk. Then you also end up with access
> to all those events that are exposed up to AMI as well. 
>
> This one single API you wish to access is really in the core of
> asterisk.
>