[Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO

[Bruce Komito]

There is a known problem with the first port on the TDM400P.  For me, the
problem resulted in randomly dropped calls on the FXO port, which was
plugged into position 1.  Since you only have two daughterboards, try
using positions 2-3-4 and don't use position 1, and see of that solves
your problem.

Bruce Komito
High Sierra Networks, Inc.
www.servers-r-us.com
(775) 284-5800 ext 115


On Wed, 19 May 2004, David Creemer wrote:

> Hi-
>
> I'm totally stumped configuring my TDM400P with one FXS and one FXO
> module. Before I got the FXO module, I used to have an X101P, and
> everything was working very well. Now * doesn't seem to recognize the
> FXO channel. I've searched the wiki and the list archives. Stock Debian
> 3.0 stable installation. Any advice? Thanks.
>
> -- David
>
>
> Here's my configuration:
>
> modprobe zaptel
> modprobe wcfxs
>
> report no errors.
>
> box:/etc/asterisk# ztcfg -vv
>
> Zaptel Configuration
> ======================
>
>
> Channel map:
>
> Channel 01: FXO Kewlstart (Default) (Slaves: 01)
> Channel 02: FXS Kewlstart (Default) (Slaves: 02)
>
> 2 channels configured.
>
> ---------------
>
> So it looks like things are OK so far. Here's the relevant portion of
> my zaptel.conf:
>
> defaultzone=us
> # load FXO X100P channel 1, kewlstart signalling
> # turned off, card removed
> #fxsks=1
> # load FXS TDM400P channel 1, kewlstart signalling
> fxoks=1
> # load FXO TDM400P channel 2, kewlstart signalling
> fxsks=2
>
>
> And here's what dmesg reports:
>
> Zapata Telephony Interface Registered on major 196
> PCI: Found IRQ 12 for device 00:09.0
> Freshmaker version: 63
> Freshmaker passed register test
> Module 0: Installed -- AUTO FXS
> Module 1: Not installed
> Module 2: Installed -- AUTO FXO
> Module 3: Not installed
> Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)
> Registered tone zone 0 (United States / North America)
>
> -----------------------------------------------
>
> the relevant portions of my zapata.conf are:
>
> [channels]
> language=en
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> busydetect=yes
> callprogress=yes
>
> ; interfaces for internal analog phones
> signalling=fxo_ks
> threewaycalling=yes
> transfer=yes
> group=1
> context=from-internal
> callerid="Creemer" <01>
> channel => 1
> mailbox=01
>
> ; interfaces to the external PSTN line
> signalling=fxs_ks
> context=from-pstn
> group=2
> channel => 2
>
> -----------------------------------------------
>
> starting asterisk gives:
> [chan_zap.so] => (Zapata Telephony w/PRI)
>    == Parsing '/etc/asterisk/zapata.conf': Found
> May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated
> conferencing on 1, with 0 conference users
>      -- Registered channel 1, FXO Kewlstart signalling
> May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to
> specify channel 2: No such device
> May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open
> channel 2: No such device
> here = 0, tmp->channel = 2, channel = 2
> May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to
> register channel '2'
> May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource:
> chan_zap.so: load_module failed, returning -1
>    == Unregistered channel type 'Tor'
>    == Unregistered channel type 'Zap'
>      -- Unregistered channel 1
>      -- Unregistered channel 2
> May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading
> module chan_zap.so failed!
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at 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
>