UK TDM400 and going from Asterisk 1.2 to 1.4

Hi,
I am having trouble getting my upgraded Asterisk server running with an Analogue FXO module.

Below is my zaptel.conf

loadzone=uk
defaultzone=uk
fxsks=4

And here is my zapata.conf

;Zapata telephony interface
;
; Configuration file
;
; You need to restart Asterisk to re-configure the Zap channel
; CLI> reload chan_zap.so
; will reload the configuration file,
; but not all configuration options are
; re-configured during a reload.

[channels]
language=en
context=analogue
signalling=fxs_ks
usecallerid=yes
cidsignalling=v23 ; Added for UK CLI detection
callerid=asreceived ; propagate the CID received from BT
cidstart=polarity ; Added for UK CLI detection
echocancel=yes
echocancelwhenbridged=yes
echotraining=128
echotraining=yes

rxgain=4 ;levels set to reduce echo
txgain=3 ;levels set to reduce echo
channel=>4

I’ve done extensive Googling and cannot find an answer. I did read it was some subtle change in the syntax of zapata.conf. Can anyone shed some light please?

Rob.

if you done an upgrade zaptel is renamed to dahdi and there is no more zaptel.conf

Hi,
Thanks for the reply. I upgraded to 1.4 from 1.2 I still need to use zaptel.

Regards,

Rob.

Hi

what does zttool show ? and what does zap show channels have to say ?
and finally anything in dmesg ?

Hi,
Well zttool does’nt appear to be installed. Is that a choice within the make menu?

Also zap show channels gives the output

mainserverCLI> zap show channels
Chan Extension Context Language MOH Interpret
pseudo analogue en default
4 analogue en default
The ‘zap show channels’ command is deprecated and will be removed in a future release. Please use ‘dahdi show channels’ instead.
mainserver
CLI>

My TDM400 has an FXO in channel 4, hence the cnannel 4 reference.

dmesg gives:

usb-storage: device scan complete
Module 3: Installed – AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules)
CSLIP: code copyright 1989 Regents of the University of California
ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2 loaded
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (module)
HiSax: Layer1 Revision 2.46.2.5
HiSax: Layer2 Revision 2.30.2.4
HiSax: TeiMgr Revision 2.20.2.3
HiSax: Layer3 Revision 2.22.2.3
HiSax: LinkLayer Revision 2.59.2.4
Adding 39078072k swap on /dev/hdc1. Priority:-1 extents:1 across:39078072k
EXT3 FS on md0, internal journal
loop: loaded (max 8 devices)
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
Registered Tormenta2 PCI
usbcore: registered new driver wcusb
Wildcard USB FXS Interface driver registered
INFO-xpp: revision trunk-r6058 MAX_XPDS=64 (8*8)
INFO-xpp: FEATURE: without BRISTUFF support
INFO-xpp: FEATURE: with PROTOCOL_DEBUG
INFO-xpp: FEATURE: with ECHO_SUPPRESSION
INFO-xpp: FEATURE: without XPP_EC_CHUNK
INFO-xpp: FEATURE: with sync_tick() from ZAPTEL
INFO-xpp_usb: revision trunk-r6058
usbcore: registered new driver xpp_usb
Registered tone zone 0 (United States / North America)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdd1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Registered tone zone 4 (United Kingdom)
usbcore: deregistering driver wcusb
usbcore: registered new driver wcusb
Wildcard USB FXS Interface driver registered
– Setting echo registers:
– Set echo registers successfully
– Setting echo registers:
– Set echo registers successfully
– Setting echo registers:
– Set echo registers successfully
– Setting echo registers:
– Set echo registers successfully
– Setting echo registers:
– Set echo registers successfully

It looks like the card is recognised, and lsmod gives the correct modules being loaded.

Rob.

why do yo need to use zaptel? dahdi is the new zaptel and your CLI gives the warning message
The ‘zap show channels’ command is deprecated and will be removed in a future release. Please use ‘dahdi show channels’ instead.
the commands are still there but zapata.conf is not scanned by the new versions so you need to use dahdi

what version of zaptel are you using? did you download a zaptel 1.4

Yes i did 1.4.12.1.

Hi

looks like its there, what are the issues you are having ?

Ian

Well this working great under 1.2, and I had a disk death on sunday and spent most of it getting RAID to work (that’s a sroty for another da) and I decided to gp upto 1.4.

I thought that DAHDI was ony required for 1.6? I’ll put DAHDI on tonight. Are there any gotchas for a standard BT POTS line to be aware of?

Rob.

dahdi is also requied for the new versions 1.4 they changed that

Yes no you mention it I do have a distant memory of this. Sugar.

Thanks guys,

Rob.