[Asterisk-Users] * @ Home: All Circuits busy

[Dan Littlejohn]

I got these errors and my hardware is working so I do not think they
are an issue

Hint: insmod errors
&
Removing zaptel module:  zaptel: Device or resource busy

What about the ztdummy module?

Dan

On 6/8/05, maoleson at mchsi.com <maoleson at mchsi.com> wrote:
> Dean,
> 
> Here are the results of the genzaptelconf -s -d.  As you can see, it is
> throwing some errors, but I am a bit of a newbie so any help you could provide
> would be greatly appreciated!
> 
> [root at asterisk1 /]# genzaptelconf -s -d
> 
> 
> STOPPING ASTERISK
> Asterisk ended with exit status 0
> Asterisk shutdown normally.
> 
> Disconnected from Asterisk server
> Asterisk Stopped
> 
> STOPPING FOP SERVER
> FOP Server Stopped
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> Unloading zaptel hardware drivers:
> Removing zaptel module:  zaptel: Device or resource busy
>                                                            [FAILED]
> Loading zaptel framework:                                  [  OK  ]
> Waiting for zap to come online ...OK
> Loading zaptel hardware modules:
> Running ztcfg:                                             [  OK  ]
> 
> SETTING FILE PERMISSIONS
> Permissions OK
> 
> STARTING ASTERISK
> Asterisk Started
> 
> STARTING FOP SERVER
> FOP Server Started
> 
> ** SIP/200 in position 2
> ** SIP/201 in position 3
> ** SIP/202 in position 4
>    Chan Extension  Context         Language   MusicOnHold
>  pseudo            from-pstn       en
> Verbosity is at least 3
> [root at asterisk1 /]#
> [root at asterisk1 /]#
> 
> 
> Thanks,
> Marc
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>