<DIV>I had a similar problem... every time I rebooted, ztcfg didn't run. I found that by running "make config" from the Zaptel source directory this problem was corrected. I had skipped this step in my original setup.</DIV>
<DIV> </DIV>
<DIV>My /etc/rc.local has two entries:</DIV>
<DIV>modprobe wct4xxp<BR>safe_asterisk<BR></DIV>
<DIV>The current Asterisk Business Edition has a script that makes the rc.local entries unneeded... but I found that I still had to manually run the "make config" command to guarantee that Asterisk would automatically recover from a reboot.</DIV>
<DIV> </DIV>
<DIV>Mark</DIV>
<DIV> </DIV>
<DIV>Mark A. Vince</DIV>
<DIV><A href="mailto:mavince@optonline.net">mavince@optonline.net</A></DIV>
<DIV> </DIV>
<DIV>> Message: 15<BR>> Date: Wed, 4 Oct 2006 16:26:27 -0400<BR>> From: "Shea, Matt" <MATT.SHEA@ONSTAR.COM><BR>> Subject: RE: [asterisk-users] UPDATE: Zaptel problems<BR>> To: "Asterisk Users Mailing List - Non-Commercial Discussion"<BR>> <ASTERISK-USERS@LISTS.DIGIUM.COM><BR>> Message-ID:<BR>> <E251C4244455254CBF8F7F03465B43A30175779B@USRN4EX0ONS01.ONSTAR.AD.GM.COM><BR>> <BR>> Content-Type: text/plain; charset="US-ASCII"<BR>> <BR>> I found a workaround, inspired by Colin's suggestion to move the <BR>> startupto the rc.local file. It turned that his exact <BR>> suggestion didn't work<BR>> in my situation. I subsequently discovered, though, that after Zaptel<BR>> and Asterisk started in the boot sequence in the usual way, all <BR>> I had to<BR>> do for the Zaptel drivers to fully kick in was re-run ztcfg. <BR>> So, as of<BR>> now, the rc scripts are all in place in the usual way with the <BR>> followingline added to /etc/rc.local:<BR>> <BR>> runuser -l -c ztcfg -s /bin/bash root<BR>> <BR>> Now it's starting properly, but I'm not really all that happy <BR>> that I<BR>> have to put a jury-rigged workaround in place. If anyone has <BR>> the real<BR>> solution, I'd certainly like to hear it.<BR>> <BR>> Thanks for all the suggestions so far.<BR>> <BR>> Matt<BR>> <BR>> <BR>> -----Original Message-----<BR>> From: asterisk-users-bounces@lists.digium.com<BR>> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of <BR>> Shea, Matt<BR>> Sent: Wednesday, October 04, 2006 2:35 PM<BR>> To: Asterisk Users Mailing List - Non-Commercial Discussion<BR>> Subject: RE: [asterisk-users] Zaptel problems<BR>> <BR>> Hmmm,<BR>> <BR>> It appears ztcfg is not being run. Any ideas why?<BR>> <BR>> Matt<BR>> <BR>> <BR>> -----Original Message-----<BR>> From: asterisk-users-bounces@lists.digium.com<BR>> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Bernardo<BR>> Vieira<BR>> Sent: Wednesday, October 04, 2006 12:40 PM<BR>> To: Asterisk Users Mailing List - Non-Commercial Discussion<BR>> Subject: Re: [asterisk-users] Zaptel problems<BR>> <BR>> -----BEGIN PGP SIGNED MESSAGE-----<BR>> Hash: SHA1<BR>> <BR>> Is ztcfg running at boot after the zaptel modules have been loaded?<BR>> What's the output of ztcfg?<BR>> <BR>> <BR>> Shea, Matt wrote:<BR>> > I'm running Asterisk/Zaptel on a Fedora Core 4 machine. The <BR>> software> runs ok with one exception. Zaptel appears to load OK <BR>> on bootup, but<BR>> > when you check it on login, zttool still shows red/nop alarms <BR>> on the<BR>> T1<BR>> > lines. I have to manually start it again for the alarms to <BR>> disappear> and the T1 lines to function properly. I've updated <BR>> the drivers to<BR>> > 1.2.9.1 and double checked my configuration files to no <BR>> effect. Any<BR>> > suggestions will be much appreciated.<BR>> > <BR>> > <BR>> > <BR>> > Matt<BR>> > <BR>> > <BR>> > <BR>> > <BR>> ><BR>> -----------------------------------------------------------------<BR>> -------<BR>> > <BR>> > _______________________________________________<BR></DIV>