[Asterisk-Users] ztdummy loading: unable to specify channel 1

[Eric Wieling]

ztdummy doesn't need any zap config.  just remove the zaptel.conf

On Thu, 2003-09-25 at 14:38, Senad Jordanovic wrote:
> Hi,
> 
> I have enabled ztdummy in order to have * compile it.
> I can modprobe ztdummy with no problems.
> 
> The sole reason, i need ztdummy is to heve musiconhold and meetme working.
> 
> However when I start *, it says this and does not start.
> 
> ----------------------------------------------------------------------------
> ----------------------
>   == Parsing '/etc/asterisk/zapata.conf': Found
> WARNING[16384]: File chan_zap.c, Line 582 (zt_open): Unable to specify
> channel 1: No such device or address
> ERROR[16384]: File chan_zap.c, Line 4891 (mkintf): Unable to open channel 1:
> No such device or address
> here = 0, tmp->channel = 0, channel = 1
> ERROR[16384]: File chan_zap.c, Line 6638 (load_module): Unable to register
> channel '1'
> WARNING[16384]: File loader.c, Line 301 (ast_load_resource): chan_zap.so:
> load_module failed, returning -1
> WARNING[16384]: File loader.c, Line 396 (load_modules): Loading module
> chan_zap.so failed!
> ----------------------------------------------------------------------------
> --------------------------------------------------
> 
> 
> 
> Senad
> 
> ______________________________________________________________________
> ****
> NOTE:  An attachment was deleted from this part of the message,
> because it failed one or more checks by the virus scanning system.
> See the attached sanitization log for more details or contact your
> system administrator.
> 
> The removed attachment's name was:
> 
> 	winmail.dat
> 
> It might be a good idea to contact the sender and warn them that
> their system is infected.
> ****
-- 
Sample configs and more: http://www.fnords.org/~eric/asterisk/

BTEL Consulting
+1-850-484-4535 x2111 (Pensacola)
+1-504-595-3916 x2111 (New Orleans)
+1-877-677-9643 x2111 (Toll Free)


-- 
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1064519340"):
  SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
    Match (names="unnamed.txt", rule="1"):
      ScanFile (file="/tmp/att-3f7346ac-A9B-unnamed.txt"):
        Scan succeeded, file is clean.

      Enforced policy: unknown

    Match (names="unnamed.txt", rule="3"):
      Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.79 2003/06/19 19:22:00 bre Exp $