[Telegraph-users] Telegraph Update

[Jonathan Palley]

Hi Rapple -
   In my brief playing around with it, here's where I'm currently at:

- Asterisk's "AGI" is basically equivalent to event_socket outbound  
(http://wiki.freeswitch.org/wiki/Event_socket_outbound)
- AMI is again basically equivalent to the XML-RPC
- AMI Events is like event_socket inbound

For integrating it into Telegraph I've begun experimenting with
- Namespacing the AGI/AMI specific code into an Asterisk namespace
- Writing a CallConnection class for event_socket outbound.  So far,  
I believe we can expose the same functions the Telegraph DSL depends  
upon in a FreeSWITCH CallConnection class.  Then of course you have  
the Asterisk/FreeSWITCH specific functions, but those are just passed  
straight through to the view code so it shouldn't be a problem.
- Doing something similar with the AMI stuff.  The AMI->XML-RPC  
shouldn't be too painful as its completely wrapped in Telegraph with  
the CRUD interface.  Although I'm afraid the Telegraph implementation  
of that wrapper may be a bit too Asterisk influenced.  We'll see.   
I'm not sure of the DRb stuff is necessary with FreeSWITCH or not.  I  
imagine not.
The AMI Events is very similar in FreeSWITCH, so again, I think that  
will work out.

I've made a bit of progress on 1 & 2.  I'll make a branch and try to  
check some stuff in in a few days.

Rabble, anyone else using FreeSWITCH in any projects that you can use  
to play around with this stuff?

Jonathan


On Aug 13, 2007, at 1:55 PM, evan wrote:

> I've been playing with freeswitch for a while and i have to say i
> really like it too. I've thought about how to integrate it with
> telegraph, but i haven't come up with anything really good. It does
> have res_ruby embedded ruby support, but it's fallen out of date and
> is in need of a maintainer.
>
> -rabble
>
> On 8/12/07, Jonathan Palley <jpalley at gmail.com> wrote:
>> Folks -
>>    Just wanted to give you a quick update on a few things
>>
>> a) If you are using AMI functions, please download the latest
>> ami_server.rb file.  There was a small bug with threading if you had
>> a lot of rails processes hitting the DRb proxy at once that
>> occasionally caused it to choke.   With this fix we've been handling
>> a fair amount of traffic (can't release exact numbers) and its been
>> singing along nicely.
>>
>> b) We've been seriously evaluating FreeSWITCH within my company.  As
>> you are all aware, Asterisk has multiple, uh, frustration points, and
>> you've got to love the way FreeSWITCH is architected.  Furthermore,
>> if you consider the kind of voice/web apps Telegraph is designed for
>> (and we make) FreeSWITCH is really the better choice than a PBX such
>> as Asterisk.  The good news is that I believe we can implement
>> FreeSWITCH support into Telegraph with complete compatibility on both
>> the AMI/AMI Events and AGI fronts as long as you were using the
>> Telegraph DSL.  This will certainly be my goal as we don't want to
>> change both our Rails code and our backend server at the same time.
>>
>> Any thoughts on this/FreeSWITCH?  Anyone checked it out?  I would
>> highly recommend you take a look.
>>
>>
>> I'm currently thinking we want to get the FreeSWITCH support in,
>> cleanup some of the requested features (i.e. helper support) and then
>> try to get an "official" release out.
>>
>> Any thoughts would be appreciated -
>>
>> Jonathan
>> _______________________________________________
>> Telegraph-users mailing list
>> Telegraph-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/telegraph-users
>>