[Asterisk-bsd] TDM400P - odd issues

[Roy Hooper]

Update:  Nothing on the FreeBSD side made it work.  Linux (Ubuntu  
server with Zaptel 1.4.5.1) worked fine the first time.

I'm at a loss as to what I might be able to do to try to move back to  
FreeBSD.

Cheers,
Roy


On 1-Sep-07, at 1:36 PM, Roy Hooper wrote:

> Hi,
>
> I'm running a TDM400P with 2xFXS and 1xFXO on an AMD64 dual-core
> machine (Nvidia chipset motherboard) running in i386 mode on FreeBSD
> 6.2.  I had been experiencing intermittent problems with the TDM400
> setup.  The old problem I used to see was that channel 2 (2nd FXS)
> would have battery but no dialtone, and channel 4 (FXO) would be able
> to place outbound calls, but would miss incoming rings/callerid and
> not pickup.  Channel 1 (FXS) would work just fine.  This used to
> happen every few weeks.  Recently, it was happening every few days,
> before the new problem cropped up...
>
> Today, my wife reported an even weirder problem:  any attempts to use
> the FXO would result in really loud static/noise after the FXS was
> joined to the FXO, and a the outbound dialing did not occur.  I
> checked, and the analog line works perfectly.
>
> Here's what I've tried:
> - I tried a power cycle.  Same problem.
> - I upgraded the zaptel driver to the latest port (1.4.6) and
> asterisk.  Same problem.
> - I upgraded asterisk.  Same problem.
>
> Unfortunately, I can't recall what previous port versions I had
> installed, but they weren't very old, and the first problem persisted
> through several versions of the ports for both asterisk and the
> zaptel driver.
>
> I now have:
>
> # Installed ports
> asterisk-1.4.9_1    An Open Source PBX and telephony toolkit
> zaptel-1.4.6_2      A FreeBSD Driver for FXO, FXS, BRI and PRI
> Telephony Cards
> asterisk-addons-1.4.2 GPL modules for the Asterisk Open Source PBX
>
> # uname -imrs
> FreeBSD 6.2-RELEASE-p6 i386 GENERIC
>
> # zfcfg
> Keyword: [fxoks], Value: [1-2]
> Keyword: [fxsks], Value: [4]
> Keyword: [loadzone], Value: [us]
> Keyword: [defaultzone], Value: [us]
>
>
> Additionally, I have the following /usr/local/etc/asterisk/
> zapata.conf for the FXO:
>
> context=incoming
> rxgain=1.0
> txgain=1.0
> signalling=fxs_ks
> ringtimeout=8000
> immediate=no
> callprogress=yes
> busydetect=yes
> busycount=6
> echocancel=yes
> echocancelwhenbridged=yes
> echotraining=yes
> channel => 4
>
> I also tried:
>
> context=incoming
> rxgain=1.0
> txgain=1.0
> signalling=fxs_ks
> ringtimeout=8000
> immediate=no
> echocancel=yes
> channel => 4
>
> and the static/noise was even louder.
>
> Here's my zttest output:
>
> --- Results after 319 passes ---
> Best: 100.000000 -- Worst: 99.963379 -- Average: 99.996020
>
> # Driver load output
> Sep  1 12:55:01 kerplunk kernel: Zapata Telephony Interface
> Registered on major 196
> Sep  1 12:55:01 kerplunk kernel: Echo Canceller: MG2
> Sep  1 12:55:01 kerplunk kernel: FXS device: vendor=e159 device=1
> subvendor=b1d9
> Sep  1 12:55:01 kerplunk kernel: wcfxs0: <Wildcard TDM400P REV I>
> port 0xa800-0xa8ff mem 0xd2101000-0xd2101fff irq 18 at device 8.0 on
> pci5
> Sep  1 12:55:01 kerplunk kernel: FXS Attach for wcfxs0: deviceID :
> 0xe159
> Sep  1 12:55:01 kerplunk kernel: wcfxs0: [FAST]
> Sep  1 12:55:01 kerplunk kernel: Freshmaker version: 73
> Sep  1 12:55:01 kerplunk kernel: Freshmaker passed register test
> Sep  1 12:55:04 kerplunk kernel: Module 0: Installed -- AUTO FXS
> Sep  1 12:55:04 kerplunk kernel: Module 1: Installed -- AUTO FXS
> Sep  1 12:55:04 kerplunk kernel: ProSLIC sanity check failed
> Sep  1 12:55:04 kerplunk kernel: Module 2: Not installed
> Sep  1 12:55:04 kerplunk kernel: Module 3: Installed -- AUTO FXO
> Sep  1 12:55:04 kerplunk kernel: Found a Wildcard TDM: Wildcard
> TDM400P REV I (4 modules)
> Sep  1 12:55:05 kerplunk kernel: Registered tone zone 0 (United
> States / North America)
>
> Left to test:
> - upgrade to latest 6.2 RELENG version.
> - non-SMP kernel.
> - Linux :-(
>
> I'm beginning to suspect bad hardware.
>
> Cheers,
> Roy
>
>