(Sorry for the way-late response to this short thread...) We use rami in production on an Asterisk 1.2.3 server, and have had basically zero problems at least since 1.2.3 was released.
rami and ruby's built in RPC provide a very easy to use proxy, if you have multiple clients which all need access to the AMI as we do. But yeah, I'd expect Asterisk has diverged a lot since rami was last updated. I did a round of refactoring at the time we were initially developing our screen pop app, but none of it has had to change in over a year. Alan Ferrency pair Networks, Inc. [EMAIL PROTECTED] On Wed, 1 Nov 2006, snacktime wrote: > On 11/1/06, Rajkumar S <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Any one using Rubi asterisk manager interface > > http://rubyforge.org/projects/rami/ ? > > > > How stable/usable it is? > > It probably hasn't seen much use. I created that back when I was just > learning ruby, so it could probably use some refactoring as well. > And If anything has changed in the asterisk manager protocol that > would be an issue also. I created it against the beta version at the > time, can't remember what that was. > > Chris _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
