[Asterisk-Users] Problems with TDM400P and asterisk on Linux 2.6

[Nigel Smith]

Hi there,

I have a TDM400P (1 x fxs, 1 x fxo) which I'm attempting to run on linux 
2.6 (gentoo), without much success at the moment. I have previously had 
it working on a 2.4 installation, but when I moved to a new box and 
installed a 2.6-based system, it failed to work. In both cases I'm using 
whatever (libpri, zaptel, asterisk)  is checked out by default (I assume 
that means HEAD) in cvs.

I am having trouble working out whether the TDM400P is properly 
configured, and is communicable from user-space (specifically, 
asterisk). zttool does not tell me anything useful (not that I really 
know how to use it).

The wctdm + zaptel modules are loading OK, and ztcfg -vvv gives the 
following:

----------------------------------------------------------
Zaptel Configuration
======================


Channel map:

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

2 channels configured.
----------------------------------------------------------

so I assume that the card is there (as in functioning), recognised by 
the kernel, and I know that the devices (I'm using udev) are there also:

----------------------------------------------------------
localhost root # ls -la /dev/zap
total 0
drwxr-xr-x   2 root root        0 Mar 16 22:12 .
drwxr-xr-x  21 root root        0 Mar 16 11:13 ..
crws-----T   1 root root 196,   1 Mar 16 22:12 1
crws-----T   1 root root 196,   2 Mar 16 22:12 2
crws-----T   1 root root 196,   3 Mar 16 22:12 3
crws-----T   1 root root 196,   4 Mar 16 22:12 4
crws-----T   1 root root 196, 254 Mar 16 22:12 channel
crws-----T   1 root root 196,   0 Mar 16 22:12 ctl
crws-----T   1 root root 196, 255 Mar 16 22:12 pseudo
crws-----T   1 root root 196, 253 Mar 16 22:12 timer
localhost root # ls -la /dev/zaptel
crw-rw----  1 root root 196, 253 Mar 16 22:12 /dev/zaptel
localhost root #
----------------------------------------------------------

I am running asterisk as root.

Now, when asterisk starts, this section indicates to me that it is at 
least recognising the configuration I have specified for the TDM400P

----------------------------------------------------------
.
.
.
 [chan_zap.so] => (Zapata Telephony w/PRI)
  == Parsing '/etc/asterisk/zapata.conf': Found
    -- Registered channel 1, FXO Kewlstart signalling
    -- Registered channel 4, FXS Kewlstart signalling
    -- Automatically generated pseudo channel
  == Registered channel type 'Zap' (Zapata Telephony Driver w/PRI)
  == Manager registered action ZapTransfer
  == Manager registered action ZapHangup
  == Manager registered action ZapDialOffhook
  == Manager registered action ZapDNDon
  == Manager registered action ZapDNDoff
  == Manager registered action ZapShowChannels
.
.
.
----------------------------------------------------------


When I make an incoming call, the following is produced:

----------------------------------------------------------
*CLI>     -- Accepting AUTHENTICATED call from 210.80.176.12:
       > requested format = alaw,
       > requested prefs = (),
       > actual format = speex,
       > host prefs = (speex|ilbc|gsm|lpc10|g723),
       > priority = mine
    -- Executing Ringing("IAX2/899060288642 at 89906028864-16384", "") in 
new stack
    -- Executing Dial("IAX2/899060288642 at 89906028864-16384", 
"Zap/1|15|Ttm") in new stack
Mar 17 11:16:54 WARNING[26117]: channel.c:1931 ast_request: No 
translator path exists for channel type Zap (native 68) to 512
Mar 17 11:16:54 NOTICE[26117]: app_dial.c:936 dial_exec_full: Unable to 
create channel of type 'Zap' (cause 0)
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing VoiceMail("IAX2/899060288642 at 89906028864-16384", 
"u1000") in new stack
Mar 17 11:16:54 NOTICE[26117]: channel.c:1731 ast_set_write_format: 
Unable to find a path from gsm to speex
Mar 17 11:16:54 WARNING[26117]: file.c:790 ast_streamfile: Unable to 
open vm-theperson (format speex): No such file or directory
  == Spawn extension (from-sip, s, 3) exited non-zero on 
'IAX2/899060288642 at 89906028864-16384'
    -- Hungup 'IAX2/899060288642 at 89906028864-16384'
----------------------------------------------------------

Would anyone be able to point me in the right direction? I really don't 
know why it can't recognise the Zap channel, or what the messages mean 
in the log immediately above.

Thanks in advance,
Nigel