asterisk users - Oct 2005 - zaptel + RH3?

Hmmm we have this TDM400 with one FXO module on it, we're using it for 
testing purposes.

I can:

modprobe zaptel

modprobe wctdm

and these get load fine as stated in /var/log/messages

Oct 29 05:09:17 monitor kernel: Module 0: Installed -- AUTO FXO (FCC mode)
Oct 29 05:09:17 monitor kernel: Module 1: Not installed
Oct 29 05:09:17 monitor kernel: Module 2: Not installed
Oct 29 05:09:17 monitor kernel: Module 3: Not installed


However when I run ztcfg -vvvv I get an error:

[root@monitor dev]# ztcfg -vvv

Zaptel Configuration
=====================

Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)

1 channels configured.

Notice: Configuration file is /etc/zaptel.conf
line 147: Unable to open master device '/dev/zap/ctl'



See how it says it can't open the master device /dev/zap/ctl. Well this is 
because that device doesn't exist..

[root@monitor dev]# ls -ald zap*
crw-------  1 root root 196,   1 Oct 29 05:09 zap1
crw-------  1 root root 196,   2 Oct 29 05:09 zap2
crw-------  1 root root 196,   3 Oct 29 05:09 zap3
crw-------  1 root root 196,   4 Oct 29 05:09 zap4
crw-------  1 root root 196, 254 Oct 29 05:09 zapchannel
crw-------  1 root root 196,   0 Oct 29 05:09 zapctl
crw-------  1 root root 196, 255 Oct 29 05:09 zappseudo
crw-------  1 root root 196, 253 Oct 29 05:09 zaptimer


I can manualy create the /dev/zap directory and then make symbolic links 
to /dev/zap/ctl using /dev/zapctl and make a symbolic link to 
/dev/zap/channel by linking to /dev/zapchannel etc...

This will make the card work just fine, I have tested this on another 
linux box and the same thing happened.

If I add this symbolic link creation into the statup scripts then like I 
said zaptel working fine, however this is obviously not the right way to 
fix this issue.

Suggestions?


-=Linsys=-

IntrusionSec.com
#1 Hacker Gamez Web Site On the Internet
http://www.intrusionsec.com
linsys@intrusionsec.com

-------------------------------------------------
When Your Life Flashes Before Your Eyes
When You Die, Does That Include The Part
Where Your Life Flashes Before Your Eyes?
-------------------------------------------------

asterisk-users-bounces@lists.digium.com wrote on 10/29/2005 04:01:26 PM:
> If I add this symbolic link creation into the statup scripts then like I 
> said zaptel working fine, however this is obviously not the right way to 
> fix this issue.
Are you doing "make config" when you compile Zaptel?  It does all of
this
for you...

Tim Massey
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20051029/64028869/attachment.htm

If you have 2.6 kernel and/or are using udev, you want to check 
README.Linux26 and README.udev in zaptel, if you haven't already done so.
>
> Hmmm we have this TDM400 with one FXO module on it, we're using it for 
> testing purposes.
>
> I can:
>
> modprobe zaptel
>
> modprobe wctdm
>
> and these get load fine as stated in /var/log/messages
>
> Oct 29 05:09:17 monitor kernel: Module 0: Installed -- AUTO FXO (FCC mode)
> Oct 29 05:09:17 monitor kernel: Module 1: Not installed
> Oct 29 05:09:17 monitor kernel: Module 2: Not installed
> Oct 29 05:09:17 monitor kernel: Module 3: Not installed
>
>
> However when I run ztcfg -vvvv I get an error:
>
> [root@monitor dev]# ztcfg -vvv
>
> Zaptel Configuration
> =====================>
>
> Channel map:
>
> Channel 01: FXS Kewlstart (Default) (Slaves: 01)
>
> 1 channels configured.
>
> Notice: Configuration file is /etc/zaptel.conf
> line 147: Unable to open master device '/dev/zap/ctl'
>
>
>
> See how it says it can't open the master device /dev/zap/ctl. Well this
is
> because that device doesn't exist..
>
> [root@monitor dev]# ls -ald zap*
> crw-------  1 root root 196,   1 Oct 29 05:09 zap1
> crw-------  1 root root 196,   2 Oct 29 05:09 zap2
> crw-------  1 root root 196,   3 Oct 29 05:09 zap3
> crw-------  1 root root 196,   4 Oct 29 05:09 zap4
> crw-------  1 root root 196, 254 Oct 29 05:09 zapchannel
> crw-------  1 root root 196,   0 Oct 29 05:09 zapctl
> crw-------  1 root root 196, 255 Oct 29 05:09 zappseudo
> crw-------  1 root root 196, 253 Oct 29 05:09 zaptimer
>
>
> I can manualy create the /dev/zap directory and then make symbolic links 
> to /dev/zap/ctl using /dev/zapctl and make a symbolic link to 
> /dev/zap/channel by linking to /dev/zapchannel etc...
>
> This will make the card work just fine, I have tested this on another 
> linux box and the same thing happened.
>
> If I add this symbolic link creation into the statup scripts then like I 
> said zaptel working fine, however this is obviously not the right way to 
> fix this issue.
>
> Suggestions?
>
>
> -=Linsys=-
>
> IntrusionSec.com
> #1 Hacker Gamez Web Site On the Internet
> http://www.intrusionsec.com
> linsys@intrusionsec.com
>
> -------------------------------------------------
> When Your Life Flashes Before Your Eyes
> When You Die, Does That Include The Part
> Where Your Life Flashes Before Your Eyes?
> -------------------------------------------------
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users@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