[asterisk-users] Zaptel / TDM400P card stopped working

Paul Hales pdhales at optusnet.com.au
Mon Dec 15 00:07:54 CST 2008


Have you tried loading the zaptel driver for your card manually?

PaulH


Langdon Stevenson wrote:
> Hi
>
> I have a Dell PE2300 with a Digium TDM400P line card in it (with one 
> module to handle an inbound phone line).  This is running on a Fedora 8 
> system with Asterisk 1.4.21.2-1.fc8
>
> This system has been working nicely for about 12 months.  After a recent 
> move of office and relocation of the server Asterisk is back on line, 
> but the TDM line card has stopped working.
>
> I have spent half a day working through Google search results, but no 
> luck so far.
>
>
> The command:
>
>    lspci -v
>
> produces:
>
> <snip>
>
>    02:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
>    interface
>      Subsystem: Unknown device b1d9:0001
>      Flags: bus master, medium devsel, latency 32, IRQ 5
>      I/O ports at e400 [size=256]
>      Memory at f9ffd000 (32-bit, non-prefetchable) [size=4K]
>      Capabilities: [40] Power Management version 2
>      Kernel modules: hisax
>
>
> The IRQ is not in use by any other device, so there is no conflict (this 
> seems to be a common problem).  The card has always been detected as a 
> Tiger3XX.  What stands out here to me is:
>
>      Kernal modules: hisax
>
> I don't believe that this was the case when I first installed the card 
> (but it was over a year ago, so I may be wrong).  The hisax driver is 
> blacklisted in /etc/modprobe.d/blacklist.
>
>
> The command:
>
>    lsmod
>
> produces:
>
> Module                  Size  Used by
> xt_dscp                 6465  0
> rfcomm                 32721  0
> l2cap                  21953  9 rfcomm
> bluetooth              47013  6 rfcomm,l2cap
> autofs4                20933  2
> fuse                   47837  1
> tun                    12613  0
> sunrpc                154785  3
> nf_conntrack_netbios_ns     6593  0
> iptable_nat             8777  0
> nf_nat                 18393  1 iptable_nat
> iptable_mangle          6849  0
> nf_conntrack_ipv4      11849  5 iptable_nat,nf_nat
> xt_state                6209  2
> nf_conntrack           51221  5 
> nf_conntrack_netbios_ns,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state
> ipt_REJECT              6977  2
> ipt_LOG                 9285  4
> iptable_filter          6849  1
> ip_tables              14033  3 iptable_nat,iptable_mangle,iptable_filter
> xt_tcpudp               6977  33
> ip6t_REJECT             7617  2
> ip6table_filter         6593  1
> ip6_tables             15057  1 ip6table_filter
> x_tables               15557  9 
> xt_dscp,iptable_nat,xt_state,ipt_REJECT,ipt_LOG,ip_tables,xt_tcpudp,ip6t_REJECT,ip6_tables 
>
> ipv6                  238277  25 ip6t_REJECT
> dm_multipath           18505  0
> parport_pc             26725  0
> parport                32173  1 parport_pc
> floppy                 52229  0
> i2c_piix4              11473  0
> i2c_core               20949  1 i2c_piix4
> pcspkr                  6593  0
> e100                   33997  0
> mii                     8385  1 e100
> dcdbas                 10465  0
> sr_mod                 17541  0
> cdrom                  33249  1 sr_mod
> sg                     31605  0
> ata_piix               19397  0
> libata                131937  1 ata_piix
> raid1                  22593  2
> dm_snapshot            18661  0
> dm_zero                 5825  0
> dm_mirror              19521  0
> dm_log                 12229  1 dm_mirror
> dm_mod                 48265  8 
> dm_multipath,dm_snapshot,dm_zero,dm_mirror,dm_log
> aic7xxx               101753  15
> scsi_transport_spi     23233  1 aic7xxx
> sd_mod                 26329  20
> scsi_mod              123917  6 
> sr_mod,sg,libata,aic7xxx,scsi_transport_spi,sd_mod
> raid456               121681  1
> async_xor               7361  1 raid456
> async_memcpy            6209  1 raid456
> async_tx                9869  3 raid456,async_xor,async_memcpy
> xor                    18633  2 raid456,async_xor
> ext3                  110281  2
> jbd                    41045  1 ext3
> mbcache                10309  1 ext3
> uhci_hcd               22993  0
> ohci_hcd               22853  0
> ehci_hcd               32845  0
>
>
> The command:
>
>    ztcfg -v
>
> produces:
>
>    Notice: Configuration file is /etc/zaptel.conf
>    line 0: Unable to open master device '/dev/zap/ctl'
>
>    1 error(s) detected
>
>
> The command:
>
>    ls -al /dev/ | grep zap
>
> produces nothing
>
>
>
> So, I am left wondering what has changed and why the Zaptel drivers are 
> no longer loading.
>
> Can anyone suggest to me how I might go about troubleshooting this issue?
>
> Langdon
>
> _______________________________________________
> -- 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
>   



More information about the asterisk-users mailing list