Upgraded from 1.2 to 1.4 and FXO lines stop working

Asterisk Asterisk Support
1

Hiya,
I am having some fun and games with upgrading from 1.2 to 1.4. I am using a pair of FXO modules to take a couple of analogue BT lines here in the UK.

I upgraded to 1.4 and they have stopped working. Now the output of ztcfg -vv is now:

server:/etc# ztcfg -vvvvvvvvvvvvvvvvvvvvv

Zaptel Version: 1.4.6
Echo Canceller: MG2
Configuration

Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)

2 channels to configure.

server:/etc#

The contents of zaptel.conf is:

Zaptel Configuration File

This file is parsed by the Zaptel Configurator, ztcfg

loadzone=uk
defaultzone=uk
fxsks=1-2

And zapata.conf is:

;
; 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
usecallerid=yes
cidsignalling=v23
callerid=asreceived
cidstart=polarity
echocancel=yes
echotraining=yes
rxgain=0
txgain=0

; Define channels
context=horeca
signalling=fxs_ks
channel=>1

context=bottlebox
signalling=fxs_ks
channel=>2

Hope someone know what’s wrong. Doen lots of digging and come up with nothing.

Cheers,

Rob.

2

I have never set up a box in the UK so I can’t relate 100% how ever your ztcfg output seems fine. What happens when you try to make a call ?

3

Wel ztcfg seems to be saying that I have something yet to set up. I went back to 1.2 and is says that two channels are configured, rather than two channels to configure as it does in my screen capture.

Also when the analogue lines ring, nothing it being passed to the nominated context.

Perhaps this is a thing whereby I have to do a deep clean of 1.2. Is there a howto for that?

Cheers,

Rob.

4

I personally do not like 1.4.X. Try asking on the users list (lists.digium.com).