[asterisk-dev] AstriDevCon - PineMango

[Nir Simionovich]

bmd:
>Nir Simionovich wrote:
>> I know for fact that carriers in Israel hadn't adopted Asterisk fully
>> due to its lack of RADIUS/DIAMETER support.

>Before we can begin on this project, we need to change the way we think
>about Asterisk.  Asterisk doesn't have perl, python, ruby, .Net, ftp,
>smtp, POP3, pam, firefox, MS Word, Outlook, Exchange, SalesForce.com,
>SugarCRM, 37signals, Google Docs, Excel, or Facebook support either.

Ok, I may be a little thick here, but I fail to see the relation between
RADIUS/DIAMETER and the application layers you had specified. It is one 
thing to be compatible and using RADIUS/DIAMETER as your AA providers,
and being integrated with high-level applications like Firefox, Word or

>There's two ways to fix this:

>1) Fire up vi and write it all in C as a module for Asterisk.  This has
>been the traditional approach, and the various features in Asterisk done
>this way are testaments to the efforts and vitality of the community.  I
>just happen to believe it's the wrong way to do it.

I think we agree on the above.

>2) Give Asterisk a flexible programming API such that this functionality
>can be done outside of Asterisk in a development framework.  Apache +
>Rails is a great example of this.  Does Rails diminish the importance of
>Apache?  It does a bit, but imagine how diminished Apache would be if
>you couldn't use Rails with it because it didn't expose enough of an API.

I think we also agree on the above, too.

However, there is a high difference between providing a high-level, rails
type API for Asterisk - which will be used primarily for Voice Application
development (at least as much as I can look at it) and providing an AA API
for allowing people to develop pluggable AA modules. 

/Nir S