Running ztcfg: ZT_CHANCONFIG failed on channel

Asterisk Asterisk Support
1

Config:FC8, Asterisk 1.4.22-rc5, Zaptel 1.4.12.1, libpri 1.4.5
Digium TDM422E (2fxo, 2fxs, echo cancellation)

Just received and installed my tdm422. Card is recognized but not configured by modules. tdm user manual says lspci should display 8005 for TDM410 series but I get 800b: Any problem there or just outdated docs?

lspci -n | grep d161

01:02.0 0200: d161:800b (rev 11)

My zaptel.conf:
fxoks=1,2
fxsks=3,4
loadzone = us
defaultzone=us

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. xpp_usb.
No hardware timing source found in /proc/zaptel, loading ztdummy
Running ztcfg: ZT_CHANCONFIG failed on channel 1: No such device or address (6)
[FAILED]

ztcfg -vv

Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration

Channel map:

Channel 01: FXO Kewlstart (Default) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)

4 channels to configure.

ZT_CHANCONFIG failed on channel 1: No such device or address (6)

Only troubleshooting I can find on this is to check my fxo/fxs ports are configured properly (fxo port uses fxs signaling). Got that, check. (Actually I tried configuring both ways to make sure, no difference).

I do have power connected directly to the TDM422 card.

Only thing in /proc/zaptel is the ztdummy driver. Nothing in /var/log/messages except for modules loading:

Sep 26 20:02:16 ibm3 kernel: Zapata Telephony Interface Registered on major 196
Sep 26 20:02:16 ibm3 kernel: Zaptel Version: 1.4.12.1
Sep 26 20:02:16 ibm3 kernel: Zaptel Echo Canceller: MG2
Sep 26 20:02:17 ibm3 kernel: Registered Tormenta2 PCI
Sep 26 20:02:17 ibm3 kernel: usbcore: registered new interface driver wcusb
Sep 26 20:02:17 ibm3 kernel: Wildcard USB FXS Interface driver registered
Sep 26 20:02:17 ibm3 kernel: INFO-xpp: revision trunk-r6058 MAX_XPDS=64 (8*8)
Sep 26 20:02:17 ibm3 kernel: INFO-xpp: FEATURE: without BRISTUFF support
Sep 26 20:02:17 ibm3 kernel: INFO-xpp: FEATURE: with PROTOCOL_DEBUG
Sep 26 20:02:17 ibm3 kernel: INFO-xpp: FEATURE: with ECHO_SUPPRESSION
Sep 26 20:02:17 ibm3 kernel: INFO-xpp: FEATURE: without XPP_EC_CHUNK
Sep 26 20:02:17 ibm3 kernel: INFO-xpp: FEATURE: with sync_tick() from ZAPTEL
Sep 26 20:02:17 ibm3 kernel: INFO-xpp_usb: revision trunk-r6058
Sep 26 20:02:17 ibm3 kernel: usbcore: registered new interface driver xpp_usb
Sep 26 20:02:20 ibm3 kernel: ztdummy: High Resolution Timer started, good to go

I appreciate any clues. Thanks.

2

I had an issue where the card was sort of being recognized but had the same error, I moved it to another PCI slot and it worked perfectly…

3

I had it in an IBM 1u server, only 1 slot. But I tried it in another machine and it works fine.

So do these digium cards have compatibility issues? They work in some mobos and not others?

Has anyone else seen pci slot and/or mobo compatibility issues?

4

I am not sure about that, but I think the pci slot I tried first was bad, I havent put anything else in it to test

5

Hi

From a clean boot with no intervention what does

zttool show ?
lsmod say ?
dmesg say ?

Also what does the modprobe .conf have in it to do with zaptel

Ian

6

Well it’s working now. I put the card back in my 1u IBM to obtain the info requested by ianplan, booted and now it’s recognized and working. I poked and prodded the power cord into the tdm power molex a little more firmly thinking that could have been the problem. I’m not sure why it wasn’t working before nor why it is now. Thanks for assistance. I’ll report back if I see any further issues. Here’s what it shows now for the record:

lspci -n |grep d161

01:02.0 0200: d161:8005 (rev 11)

Notice lspci shows 8005 not 800b as before.

ztcfg -vv

Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration

Channel map:

Channel 01: FXO Kewlstart (Default) (Slaves: 01)
Channel 02: FXO Kewlstart (Default) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)

cat /proc/zaptel/1

Span 1: WCTDM/0 “Wildcard TDM410P Board 1” (MASTER)
IRQ misses: 5

       1 WCTDM/0/0 FXOKS 
       2 WCTDM/0/1 FXOKS 
       3 WCTDM/0/2 FXSKS RED
       4 WCTDM/0/3 FXSKS RED

lsmod|egrep “zap|^wc”

wcusb 16640 0
wctdm 36812 0
wcfxo 13984 0
wcte11xp 25120 0
wct1xxp 15648 0
wcte12xp 62560 0
wct4xxp 286592 0
wctdm24xxp 114816 0
zaptel 187044 12 xpp,wcusb,wctdm,wcfxo,wcte11xp,wct1xxp,wcte12xp,wct4xxp,tor2,wctdm24xxp
crc_ccitt 6081 1 zaptel

dmesg|egrep -i “zap|^wc”

Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.12.1
Zaptel Echo Canceller: MG2
firmware: requesting zaptel-fw-vpmadt032.bin
wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to compensate.
wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to compensate.
INFO-xpp: FEATURE: with sync_tick() from ZAPTEL
wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to compensate.
wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to com

7

Hi

May be working but [quote]IRQ misses: 5 [/quote] is not good news.

Ian

8

Please explain?

9

yes please do explain.

My thought (from a little research) is that the card is a slower piece of technology than the PCI bus it is connected to, and these message are just indicating the hoops that linux is having to jump through to sync them.

On an older technology, IRQ conflicts would be an issue (and may well be here) but we have hundreds of IRQ’s available, not just the 16 or so from the old X86 days.