<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 10pt; color: #000000'>There might be some issues with you using /etc/asterisk/unstable, there are still some parts of the GUI that use a hardcoded '/etc/asterisk/'. If you find "dahdi_scan.conf" or "dahdi_guiread.conf" in /etc/asterisk/, just copy them to /etc/asterisk/unstable. That might resolve the issue. The last time I dealt with a similar issue it was because the GUI couldn't find the dahdi_scan.conf file and kept trying to run dahdi_scan. In your case, it might be running properly and just not writing the conf file to the appropriate dir. If that does work, you could modify the OUTPUTFILE in /var/lib/asterisk/scripts/detectdahdi.sh to reflect your appropriate config dir.<br><br>(GUI lesson)<br>If you actually had hardware the GUI would use these config files as almost a gateway to write to /etc/system/dahdi.conf just as it does when it writes to /etc/misdn.conf. Since Asterisk's http and config modules aren't programmed to pull configs from any directory other than the config dir, the GUI has to rig it with includes. You might see in the "guiread" file a line something like: #include ../dahdi/system.conf. It really should be /etc/dahdi/system.conf, especially in your case, but thats just the best way for the GUI to read the DAHDI config.<br><br>-- <br>Ryan Brindley <br>Digium, Inc. | Software Developer <br>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA <br>main: +1 256-428-6000 fax: +1 256-864-0464 <br>Check us out at: http://digium.com & http://asterisk.org<br><br>----- Original Message -----<br>From: "Christoph Krell" <christoph.krell@xidras.com><br>To: "Asterisk GUI project discussion" <asterisk-gui@lists.digium.com><br>Sent: Wednesday, July 1, 2009 7:43:27 AM GMT -06:00 US/Canada Central<br>Subject: Re: [asterisk-gui] GUI Infinite loop, no DAHDI installed<br><br>Ryan,<br><br>I've just installed DAHDI from svn. compiled and installed with no <br>errors, when i created configs it said:<br>~<br>DAHDI has been configured.<br><br>List of detected DAHDI devices:<br><br>driver should be 'cwain' but is actually 'hfcmulti'<br>driver should be 'cwain' but is actually 'hfcmulti'<br>pci:0000:05:08.0 cwain+ 1397:30b1 HFC-E1 ISDN E1 card<br>pci:0000:05:09.0 cwain+ 1397:30b1 HFC-E1 ISDN E1 card<br>~<br><br>I think that means "DAHDI was loaded but the HW uses mISDN", but thats <br>just the way we want it to be, right?<br>Then i restarted asterisk and checked the GUI again, but again its stuck <br>in a loop, only a few commands further:<br><br>unstable1*CLI><br> == Parsing '/etc/asterisk/unstable/manager.conf': Found<br> == HTTP Manager 'manager' logged on from 192.168.50.200<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Saving '/etc/asterisk/unstable/http.conf': Saved<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Saving '/etc/asterisk/unstable/http.conf': Saved<br> == Parsing '/etc/asterisk/unstable/extensions.conf': Found<br> == Parsing '/etc/asterisk/unstable/extensions.conf': Found<br> == Saving '/etc/asterisk/unstable/extensions.conf': Saved<br>~<br> == Parsing '/etc/asterisk/unstable/extensions.conf': Found<br> == Saving '/etc/asterisk/unstable/extensions.conf': Saved<br> == Parsing '/etc/asterisk/unstable/extensions.conf': Found<br> == Setting global variable 'FEATURES' to ''<br> == Setting global variable 'DIALOPTIONS' to ''<br> == Setting global variable 'RINGTIME' to '20'<br> == Setting global variable 'FOLLOWMEOPTIONS' to ''<br> == Setting global variable 'PAGING_HEADER' to 'Intercom'<br> -- Registered extension context 'nachtschaltung'<br> -- Added extension '1000' priority 1 to nachtschaltung<br> -- Added extension '1000' priority 2 to nachtschaltung<br>~<br> -- Added extension '1-CONGESTION' priority 1 to <br>macro-trunkdial-failover-0.3<br> -- Added extension '1-CONGESTION' priority 2 to <br>macro-trunkdial-failover-0.3<br> -- Added extension '1-out' priority 1 to macro-trunkdial-failover-0.3<br><br> == Parsing '/etc/asterisk/unstable/users.conf': Found<br>[Jul 1 14:38:17] WARNING[5316]: pbx.c:6347 ast_context_verify_includes: <br>Context 'ael-local' tries to include nonexistent context 'ael-parkedcalls'<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Saving '/etc/asterisk/unstable/http.conf': Saved<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Saving '/etc/asterisk/unstable/http.conf': Saved<br> == Parsing '/etc/asterisk/unstable/extensions.conf': Found<br> -- Executing [executecommand@asterisk_guitools:1] <br>System("Local/executecommand@asterisk_guitools-2345,2", "sh <br>/var/lib/asterisk/scripts/detectdahdi.sh") in new stack<br> -- Executing [executecommand@asterisk_guitools:1] <br>System("Local/executecommand@asterisk_guitools-bfbf,2", "dahdi_genconf") <br>in new stack<br> -- Executing [executecommand@asterisk_guitools:2] <br>Hangup("Local/executecommand@asterisk_guitools-2345,2", "") in new stack<br> == Spawn extension (asterisk_guitools, executecommand, 2) exited <br>non-zero on 'Local/executecommand@asterisk_guitools-2345,2'<br> -- Executing [executecommand@asterisk_guitools:2] <br>Hangup("Local/executecommand@asterisk_guitools-bfbf,2", "") in new stack<br> == Spawn extension (asterisk_guitools, executecommand, 2) exited <br>non-zero on 'Local/executecommand@asterisk_guitools-bfbf,2'<br> -- Executing [executecommand@asterisk_guitools:1] <br>System("Local/executecommand@asterisk_guitools-e3eb,2", "touch <br>/etc/asterisk/guipreferences.conf") in new stack<br> -- Executing [executecommand@asterisk_guitools:2] <br>Hangup("Local/executecommand@asterisk_guitools-e3eb,2", "") in new stack<br> == Spawn extension (asterisk_guitools, executecommand, 2) exited <br>non-zero on 'Local/executecommand@asterisk_guitools-e3eb,2'<br> -- Executing [executecommand@asterisk_guitools:1] <br>System("Local/executecommand@asterisk_guitools-b38c,2", "sh <br>/var/lib/asterisk/scripts/detectdahdi.sh") in new stack<br> -- Executing [executecommand@asterisk_guitools:2] <br>Hangup("Local/executecommand@asterisk_guitools-b38c,2", "") in new stack<br> == Spawn extension (asterisk_guitools, executecommand, 2) exited <br>non-zero on 'Local/executecommand@asterisk_guitools-b38c,2'<br> == Parsing '/etc/asterisk/unstable/http.conf': Found<br> == Saving '/etc/asterisk/unstable/http.conf': Saved<br><br>..thats where the loop starts again<br><br>theres no error or something, just looks like he doesn't remember that <br>he did the whole dahdi-guitools-things before. Any ideas?<br><br>Thanks in advance,<br>Christoph<br><br><br>Ryan Brindley schrieb:<br>> Christoph,<br>> I recently did some work when both mISDN and DAHDI are installed. You <br>> should be fine since you've installed mISDN before DAHDI. From what <br>> the hardware guru's told me, if you want mISDN to control the BRI <br>> cards all you need to make sure happens is that mISDN loads before <br>> DAHDI. And I think that'll happen for you because you installed mISDN <br>> before DAHDI. If not though, you can just change the load sequence in <br>> /etc/init.d/ (I think). I don't remember, but they knew the "command" <br>> to set priority.<br>><br>> -- <br>> Ryan Brindley <br>> Digium, Inc. | Software Developer <br>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA <br>> main: +1 256-428-6000 fax: +1 256-864-0464 <br>> Check us out at: http://digium.com & http://asterisk.org<br>><br>> ----- Original Message -----<br>> From: "Christoph Krell" <christoph.krell@xidras.com><br>> To: "Asterisk GUI project discussion" <asterisk-gui@lists.digium.com><br>> Sent: Tuesday, June 30, 2009 8:59:08 AM GMT -06:00 US/Canada Central<br>> Subject: Re: [asterisk-gui] GUI Infinite loop, no DAHDI installed<br>><br>> Ryan,<br>><br>> Thanks for your quick answer, it is nice to see that this list is<br>> maintained so well, keep up the good work!<br>><br>> Regarding DAHDI:<br>><br>> I am gonna try and install it, but I fear it will cause problems with<br>> the installed mISDN drivers for my E1-card, and with the new asterisk<br>> versions, mISDN tends to be very sensitive ;-)<br>> Is there a "light-installer" that only installes the asterisk-modules<br>> and the dummy-drivers?<br>><br>> Thanks for your help so far,<br>><br>> best regards,<br>> Christoph<br>><br>><br>><br>> Ryan Brindley schrieb:<br>> > Christoph,<br>> > Good news and bad news. Good first, you're not crazy nor doin anything<br>> > wrong, temporarily this can be avoided by installing DAHDI (if you<br>> > choose to do so, its not in the asterisk source, it has its own,<br>> > http://svn.asterisk.org/svn/dahdi/linux-complete/tags/2.2.0+2.2.0/).<br>> > It might be a good idea anyway if you decide to do anything involving<br>> > timing (such as music on hold and conference calls).<br>> ><br>> > Ok now the bad news, the world is ending. Just kidding. This is,<br>> > unfortunately, not the first time this issue has come up. Last time I<br>> > checked that part of the code, the GUI shouldn't even try to run<br>> > dahdi_genconf if dahdi isn't installed, but I guess there is something<br>> > still missing.<br>> ><br>> > If you can, report this issue at http://issues.asterisk.org (under the<br>> > Asterisk-GUI project) and I'll take a look at the code and find whats<br>> > causing this. But if you need something resolved immediately I'd just<br>> > install DAHDI and wait for the fix :-)<br>> > -- <br>> > Ryan Brindley <br>> > Digium, Inc. | Software Developer <br>> > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA <br>> > main: +1 256-428-6000 fax: +1 256-864-0464 <br>> > Check us out at: http://digium.com & http://asterisk.org<br>> ><br>> > ----- Original Message -----<br>> > From: "Christoph Krell" <christoph.krell@xidras.com><br>> > To: asterisk-gui@lists.digium.com<br>> > Sent: Tuesday, June 30, 2009 8:00:29 AM GMT -05:00 US/Canada Eastern<br>> > Subject: [asterisk-gui] GUI Infinite loop, no DAHDI installed<br>> ><br>> > Hi List,<br>> ><br>> > I just upgraded my old asterisk to 1.4.25.1, and i thought i give the<br>> > GUI a try since we need it to dynamically generate extension entries.<br>> ><br>> > I installed the GUI from the svn (GUI-version : SVN-branch-2.0-r4947),<br>> > but as soon as I try to log in, the GUI is stuck in a loop, it looks<br>> > like it trys to run dahdi_genconf, which then fails.<br>> ><br>> > I get the following in the CLI:<br>> > WARNING[14499]: app_system.c:107 system_exec_helper: Unable to execute<br>> > 'dahdi_genconf'<br>> ><br>> > I haven't even DAHDI installed. To check it, i ran make menuselect<br>> > again, and the chan_dahdi was not selected.<br>> ><br>> > I found some hints towards file restrictions, so I changed them, but it<br>> > didn't work.<br>> ><br>> > I would appreciate any help, thanks<br>> ><br>> > --<br>> ><br>> > Christoph Krell<br>> > Technik<br>> ><br>> ><br>> ><br>> ><br>> ><br>> ><br>> > --<br>> ><br>> > Christoph Krell<br>> > Technik<br>> ><br>> > <br>> ________________________________________________________________________________<br>> ><br>> > Xidras GmbH<br>> > Stockern 47<br>> > 3744 Stockern<br>> > Austria<br>> ><br>> > Tel: +43 (0) 2983 201-30507<br>> > Fax: +43 (0) 2983 201-305079<br>> > Email: christoph.krell@xidras.com<br>> > Web: http://www.xidras.com<br>> ><br>> > FN 317036 f | Landesgericht Krems | ATU64485024<br>> ><br>> > <br>> ________________________________________________________________________________<br>> ><br>> > VERTRAULICHE INFORMATIONEN!<br>> > Diese eMail enthält vertrauliche Informationen und ist nur für den<br>> > berechtigten<br>> > Empfänger bestimmt. Wenn diese eMail nicht für Sie bestimmt ist,<br>> > bitten wir Sie,<br>> > diese eMail an uns zurückzusenden und anschließend auf Ihrem <br>> Computer und<br>> > Mail-Server zu löschen. Solche eMails und Anlagen dürfen Sie weder<br>> > nutzen,<br>> > noch verarbeiten oder Dritten zugänglich machen, gleich in welcher Form.<br>> > Wir danken für Ihre Kooperation!<br>> ><br>> > CONFIDENTIAL!<br>> > This email contains confidential information and is intended for the<br>> > authorised<br>> > recipient only. If you are not an authorised recipient, please return<br>> > the email<br>> > to us and then delete it from your computer and mail-server. You may<br>> > neither<br>> > use nor edit any such emails including attachments, nor make them<br>> > accessible<br>> > to third parties in any manner whatsoever.<br>> > Thank you for your cooperation<br>> ><br>> > <br>> ________________________________________________________________________________<br>> ><br>> ><br>> ><br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > --Bandwidth and Colocation Provided by http://www.api-digital.com--<br>> ><br>> > asterisk-gui mailing list<br>> > To UNSUBSCRIBE or update options visit:<br>> > http://lists.digium.com/mailman/listinfo/asterisk-gui<br>> > ------------------------------------------------------------------------<br>> ><br>> > _______________________________________________<br>> > --Bandwidth and Colocation Provided by http://www.api-digital.com--<br>> ><br>> > asterisk-gui mailing list<br>> > To UNSUBSCRIBE or update options visit:<br>> > http://lists.digium.com/mailman/listinfo/asterisk-gui<br>><br>><br>><br>><br>><br>> _______________________________________________<br>> --Bandwidth and Colocation Provided by http://www.api-digital.com--<br>><br>> asterisk-gui mailing list<br>> To UNSUBSCRIBE or update options visit:<br>> http://lists.digium.com/mailman/listinfo/asterisk-gui<br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> --Bandwidth and Colocation Provided by http://www.api-digital.com--<br>><br>> asterisk-gui mailing list<br>> To UNSUBSCRIBE or update options visit:<br>> http://lists.digium.com/mailman/listinfo/asterisk-gui<br><br><br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by http://www.api-digital.com--<br><br>asterisk-gui mailing list<br>To UNSUBSCRIBE or update options visit:<br> http://lists.digium.com/mailman/listinfo/asterisk-gui</div></body></html>