Ok, I wasn't confused, but I am now. Here's what I'm thinking. I'd like to continue to use the released version of asterisk-xxxx/configs/manager.config.sample, but we'll apply two sets of patches to that.
(1) patches that are generic for Astlinux (2) patches that are needed for the new Altweb interface Can you break that out into two sets for me? Thanks, -Philip Lonnie Abelbeck wrote: > Philip, > > Thanks, this is the custom manager.conf I was suggesting Darrick install. > > Complete manager.conf here: > http://lonnie.abelbeck.com/astlinux/manager.conf.txt > > Currently, the asterisk-gui package installs configs/manager.conf > (whether selected or not). I'm suggesting the above is 'safer' and > allows AMI to work with altweb. > > Lonnie > > > On Aug 21, 2008, at 3:30 PM, Philip Prindeville wrote: > >> A new 0.3 second delay is a bug. Regardless of their being a >> workaround, I'd still file a bug against it so it can be fixed. >> >> As for requiring the following changes: I can modify the asterisk.mk >> file so that it makes these changes if BR2_ALTERNATEWEB_v2 is set... >> >> I'll try to get that in tonight. >> >> Darrick and Kris: please hold off on the branching. >> >> -Philip >> >> >> Lonnie Abelbeck wrote: >>> Because it was bugging me..., new features include: (Version 1.0.05) >>> >>> I have been testing trunk, and noticed with the latest asterisk >>> (Asterisk 1.4.21.2), commands are 'slower' when accessed via the shell >>> as >>> asterisk -rx ... >>> >>> Sure enough, about 0.3 seconds of delay occurs between the command >>> output and the returning prompt. This really adds up with multiple >>> calls to asterisk in altweb, and was bugged me. Asterisk 1.4.18 does >>> not exhibit this behavior. >>> >>> The solution is for altweb to also support the manager interface (in >>> 1.0.05) as a method to issue commands to asterisk. Using the manager >>> interface solves the 0.3 second delay problem in the latest asterisk. >>> Possibly the 'proper' way to do it anyway. The previous "asterisk - >>> rx ..." is the default. >>> >>> But using the asterisk manager interface (AMI) requires the >>> manager.conf file to be properly configured. >>> >>> ---- manager.conf snippet ---- >>> [general] >>> enabled = yes >>> ;webenabled = yes >>> port = 5038 >>> bindaddr = 127.0.0.1 >>> >>> ; Web interface localhost user for AstLinux >>> ; >>> [webinterface] >>> secret = webinterface >>> deny=0.0.0.0/0.0.0.0 >>> permit=127.0.0.1/255.255.255.255 >>> read = command >>> write = command >>> ---- manager.conf snippet ---- >>> >>> For changes to the manager.conf to be applied, reboot/restart the >>> system. >>> >>> 1) A new Prefs tab option, under "Status Tab Options:" >>> >>> ___ Use Asterisk Manager Interface for Asterisk Commands >>> >>> When checked, the AMI is used to issue commands to asterisk, using >>> user/password 'webinterface'. Note that only connections from >>> localhost to localhost are allowed. >>> >>> When unchecked, the system shell issues "asterisk -rx ..." calls to >>> issue commands to asterisk. >>> >>> Downloads and Info: >>> http://lonnie.abelbeck.com/astlinux/info/webgui.php >>> >>> Enjoy, >>> Lonnie >>> >> > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
