<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16705" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Hi again,</FONT></DIV><FONT size=2>
<DIV><BR>Thanks for your answer, Stefan. In fact, ztcfg is automatically running
from the <BR>startup script. Anyhow this seems harmless and not the cause of the
problem. I have <BR>confirmed this with two other Asterisk servers, both having
a zaptel card installed <BR>in them, but one running the same Debian Etch OS as
the troublesome machine, and <BR>the other one running Fedora Core 6. In both
cases I restricted the zaptel modules </DIV>
<DIV>loaded to just ztdummy and modified zaptel.conf in order not to configure
anything. <BR>Then I restarted zaptel and attempted to start Asterisk. In the
first case I obtained <BR>the same error message as I reported before. In the
case of the machine running <BR>Fedora, Asterisk started normally (and it's
worth to say that ztcfg does also </DIV>
<DIV>automatically run in it). So it is apparent that the problem involves
Debian.</DIV>
<DIV> </DIV>
<DIV>Greetings.</DIV>
<DIV> </DIV>
<DIV>Aldo Sudak</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2><BR>>On Sat, Nov 01, 2008 at 11:03:09PM -0200, Aldo D.
Sudak wrote:<BR>>> Loading zaptel hardware modules: ztdummy.<BR>>>
Running ztcfg: done.<BR>><BR>>There is no need to run ztcfg if you just
want to use ztdummy.<BR>>The call to ztcfg is probably just part of some
standard init script.<BR>><BR>><BR>>-- <BR>>Stefan Tichy (
asterisk2 at pi4tel dot de )</FONT></DIV></BODY></HTML>