Updating extensions conf online dating rules meeting

just as i was thinking that digium would let go of the asterisk-gui project after switching to freepbx as default.

The AD support in Samba 4.0 and later is optional and does not replace any of the PDC features.

Has anyone found a fix or solution for this loop after upgrading? == Spawn extension (asterisk_guitools, executecommand, 1) exited non-zero on 'Local/[email protected]_guitools-9c1a,2' == Parsing '/etc/asterisk/guipreferences.conf': Found == Parsing '/etc/asterisk/meetme.conf': Found == Parsing '/etc/asterisk/asterisk.conf': Found == Parsing '/etc/asterisk/http.conf': Found == Saving '/etc/asterisk/http.conf': Saved == Parsing '/etc/asterisk/http.conf': Found == Parsing '/etc/asterisk/http.conf': Found == Saving '/etc/asterisk/http.conf': Saved == Parsing '/etc/asterisk/extensions.conf': Found -- Executing [[email protected]_guitools:1] System("Local/[email protected]_guitools-08c7,2", "dahdi_genconf") in new stack [Jan 25 ] WARNING[3269]: app_system.c:107 system_exec_helper: Unable to execute 'dahdi_genconf' Somebody any ideas?

I upgraded the GUI to the newest version 4474/4475, and I now I am unable to get into the configuration at all. Best regards Al I think that's the reason If you use dahdi, be sure to have dahdi-tools installed (the /etc/dahdi will be created) If not, reinstall asterisk without dahdi support, then the gui should not check for dahdi stuff.

cyril How would I load an older version of the gui? I performed a restore of the data from my production server to use to test. I initiated a reboot and couldn't login to the gui.

I ran an update where it checked out version 4474, and now I'm having the exact same issue again. Hello, Not with previous gui program, I am having some issues with 1.4.23.

Leave a Reply