Hello
Since TDM cards are known for being particular when it comes
to motherboards (PCI 2.2, etc.), I was wondering if there is a utility
that can check that the Zaptel driver works OK and can tell if the TDM
card is compatible?
That way, if an FXO module is not reporting an incoming call, we'd
know it's because of the Zaptel driver, and not something elsewhere.
Are "dmesg", "lspci -v", "ztcfg -vv" and
"zttool" the only tools
available to investigate this issue?
Thank you.
=================
PS: I'm using an OpenVox clone of the Digium card, with just one FXO
module. With the FXO module installed on plug #1, here's what I tried
so far. Note that "ztcfg -vv" says "1 channels to
configure.", while
Digium cards apparently say ""1 channels configured":
================= # dmesg
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.7
Zaptel Echo Canceller: MG2
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKD] -> GSI 12 (level,
low) -> IRQ 12
Freshmaker version: 71
Freshmaker passed register test
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Not installed
Module 2: Not installed
Module 3: Not installed
Found a Wildcard TDM: Wildcard TDM400P REV E/F (1 modules)
[...]
usbcore: registered new driver wcusb
Wildcard USB FXS Interface driver registered
Registered tone zone 2 (France)
================= # lspci -v
00:0f.0 Communication controller: Tiger Jet Network Inc. Tiger3XX
Modem/ISDN interface
Subsystem: Unknown device b100:0003
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at c400 [size=256]
Memory at dfffe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
================= # cat /etc/zaptel.conf
fxsks=1
loadzone=fr
defaultzone=fr
================= # ztcfg -vvvv
Zaptel Version: 1.4.7
Echo Canceller: MG2
Configuration
Channel map:
Channel 01: FXS Kewlstart (Default) (Slaves: 01)
1 channels to configure.
================= # cat zapata.conf
[channels]
language=fr
context=my-phones
usecallerid=yes
hidecallerid=no
immediate=no
signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
channel=>1
================= # cat /etc/asterisk/extensions.conf
[general]
[globals]
[my-phones]
exten => s,1,Verbose(yes!)
================= # service zaptel restart
Unloading zaptel hardware drivers:.
Loading zaptel framework: [ OK ]
Waiting for zap to come online...OK
Loading zaptel hardware modules: tor2.
wct4xxp.
wcte12xp.
wct1xxp.
wcte11xp.
wctdm24xxp.
wcfxo.
wctdm.
wcusb.
Running ztcfg: [ OK ]
================= # service asterisk restart
Shutting down asterisk: Asterisk ended with exit status 0
Asterisk shutdown normally.
[ OK ]
Starting asterisk: [ OK ]
================= # asterisk -vvvvvvvvvvr
asterisk*CLI>
================Here, I call into the OpenVox card from a cellphone, but nothing
is
shown in the Asterisk console :-/
Tzafrir Cohen
2008-Jan-08 18:29 UTC
[asterisk-users] [Zaptel] Checking that TDM card works?
On Tue, Jan 08, 2008 at 07:06:17PM +0100, Vincent wrote:> Hello > > Since TDM cards are known for being particular when it comes > to motherboards (PCI 2.2, etc.), I was wondering if there is a utility > that can check that the Zaptel driver works OK and can tell if the TDM > card is compatible? > > That way, if an FXO module is not reporting an incoming call, we'd > know it's because of the Zaptel driver, and not something elsewhere. > > Are "dmesg", "lspci -v", "ztcfg -vv" and "zttool" the only tools > available to investigate this issue? > > Thank you. > =================> > PS: I'm using an OpenVox clone of the Digium card, with just one FXO > module. With the FXO module installed on plug #1, here's what I tried > so far. Note that "ztcfg -vv" says "1 channels to configure.", while > Digium cards apparently say ""1 channels configured":This change is simply due to different versions of Zaptel. Zaptel >1.4.6 prints "to configure" because this message is printed (and has always been prinetd) before the configuration is actually applied. And hence fooled poor users into believing that their channels were properly configured.> ================= # cat zapata.conf > [channels] > language=fr > context=my-phones > usecallerid=yes > hidecallerid=no > immediate=no > > signalling=fxs_ks > echocancel=yes > echocancelwhenbridged=yes > channel=>1 > > ================= # cat /etc/asterisk/extensions.conf > [general] > > [globals] > > [my-phones] > exten => s,1,Verbose(yes!)In the Asterisk CLI run: core set verbose 3 And then see what happens when a call comes in. Basically you miss an action to do after the Verbose line. Alternatively, what is the output of: cat /proc/zaptel/* asterisk -rx 'zap show channels' -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
On Tue, 2008-01-08 at 19:06 +0100, Vincent wrote:> Are "dmesg", "lspci -v", "ztcfg -vv" and "zttool" the only tools > available to investigate this issue?I always find that looking at the files that are generated under /proc/zaptel is very enlightening as far as showing what the zaptel drivers are seeing. -- Jared Smith Community Relations Manager Digium, Inc.
On Tue, 08 Jan 2008 13:43:50 -0500, Jared Smith <jsmith at digium.com> wrote:>I always find that looking at the files that are generated >under /proc/zaptel is very enlightening as far as showing what the >zaptel drivers are seeing.Thanks for the tip.
On Wed, 9 Jan 2008 12:05:34 +0200, Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:>wcfxo is not needed. > >Basically all you need is: > > modprobe <your_card_s_driver> > >This also pulls all of its dependencies (e.g: zaptel) > > modprobe wctdmThanks, but on AstLinux, the modules are not unloaded: ======pbx admin # /etc/init.d/zaptel stop pbx admin # lsmod Module Size Used by wctdm 31552 1 wcfxo 11424 0 zaptel 188604 6 wctdm,wcfxo hdlc 22528 1 zaptel syncppp 15300 1 hdlc ppp_generic 28692 1 zaptel ====== Why would an init script not remove modules?
Tzafrir Cohen
2008-Jan-09 11:39 UTC
[asterisk-users] [Zaptel] Checking that TDM card works?
On Wed, Jan 09, 2008 at 12:26:46PM +0100, Vincent wrote:> On Wed, 9 Jan 2008 12:05:34 +0200, Tzafrir Cohen > <tzafrir.cohen at xorcom.com> wrote: > >wcfxo is not needed. > > > >Basically all you need is: > > > > modprobe <your_card_s_driver> > > > >This also pulls all of its dependencies (e.g: zaptel) > > > > modprobe wctdm > > Thanks, but on AstLinux, the modules are not unloaded: > > ======> pbx admin # /etc/init.d/zaptel stop > > pbx admin # lsmod > Module Size Used by > wctdm 31552 1 > wcfxo 11424 0 > zaptel 188604 6 wctdm,wcfxo > hdlc 22528 1 zaptel > syncppp 15300 1 hdlc > ppp_generic 28692 1 zaptel > ======> > Why would an init script not remove modules?That depends on how the script in astlinux works. What does it do? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Darrick Hartman (lists)
2008-Jan-09 12:01 UTC
[asterisk-users] [Zaptel] Checking that TDM card works?
Vincent wrote:> On Wed, 9 Jan 2008 12:05:34 +0200, Tzafrir Cohen > <tzafrir.cohen at xorcom.com> wrote: >> wcfxo is not needed. >> >> Basically all you need is: >> >> modprobe <your_card_s_driver> >> >> This also pulls all of its dependencies (e.g: zaptel) >> >> modprobe wctdm > > Thanks, but on AstLinux, the modules are not unloaded: > > ======> pbx admin # /etc/init.d/zaptel stop > > pbx admin # lsmod > Module Size Used by > wctdm 31552 1 > wcfxo 11424 0 > zaptel 188604 6 wctdm,wcfxo > hdlc 22528 1 zaptel > syncppp 15300 1 hdlc > ppp_generic 28692 1 zaptel > ======> > Why would an init script not remove modules?Vincent, Come on over to the astlinux mailing list (on our sourceforge page). It will be easier to handle any Astlinux specific questions over there. But look in your /etc/rc.conf file for the ZAPMODS variable. You should have that variable set to: ZAPMODS="wctdm" Beyond that, as long as Asterisk is not running, issuing service zaptel stop should remove all zaptel related modules. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com