Hi again,
Thanks for your answer, Stefan. In fact, ztcfg is automatically running from
the
startup script. Anyhow this seems harmless and not the cause of the problem. I
have
confirmed this with two other Asterisk servers, both having a zaptel card
installed
in them, but one running the same Debian Etch OS as the troublesome machine,
and
the other one running Fedora Core 6. In both cases I restricted the zaptel
modules
loaded to just ztdummy and modified zaptel.conf in order not to configure
anything.
Then I restarted zaptel and attempted to start Asterisk. In the first case I
obtained
the same error message as I reported before. In the case of the machine running
Fedora, Asterisk started normally (and it's worth to say that ztcfg does also
automatically run in it). So it is apparent that the problem involves Debian.
Greetings.
Aldo Sudak
>On Sat, Nov 01, 2008 at 11:03:09PM -0200, Aldo D. Sudak wrote:
>> Loading zaptel hardware modules: ztdummy.
>> Running ztcfg: done.
>
>There is no need to run ztcfg if you just want to use ztdummy.
>The call to ztcfg is probably just part of some standard init script.
>
>
>--
>Stefan Tichy ( asterisk2 at pi4tel dot de )
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
