asterisk users - Oct 2008 - Zaptel FXO offhook when connected to PSTN

I installed Trixbox and a TDM400P with 2 FXO and 2 FXS ports and am having
an annoying issue with the FXO ports. As soon as I plug either one into the
phone line it's as though the line is disconnected i.e. get disconnected
tone when trying to dial out, line is busy when dialling in.

The CLI shows the following:
trixbox1*CLI> zap show channel 4
Channel: 4
File Descriptor: 18
Span: 11*
Extension: 
Dialing: no
Context: from-pstn
Caller ID: 
Calling TON: 0
Caller ID name:
Destroy: 0
InAlarm: 1
Signalling Type: FXS Kewlstart
Radio: 0*
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no1*
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
Echo Cancellation: 128 taps unless TDM bridged, currently OFF Actual
Confinfo: Num/0, Mode/0x0000 Actual Confmute: No Hookstate (FXS only):
Onhook

When plugged in:
trixbox1*CLI> zap show channel 4
Channel: 4
File Descriptor: 18
Span: 11*
Extension: 
Dialing: noI
Context: from-pstn
Caller ID: I
Calling TON: 0
Caller ID name:
Destroy: 0
InAlarm: 0
Signalling Type: FXS Kewlstart
Radio: 0*
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no1*
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
Echo Cancellation: 128 taps unless TDM bridged, currently OFF Actual
Confinfo: Num/0, Mode/0x0000 Actual Confmute: No Hookstate (FXS only):
Offhook

When cable plugged in:
[Oct 20 09:02:56] DEBUG[2359] chan_zap.c: Monitor doohicky got event No more
alarm on channel 4 [Oct 20 09:02:56] NOTICE[2359] chan_zap.c: Alarm cleared
on channel 4

When cable unplugged:
[Oct 20 09:04:55] DEBUG[2359] chan_zap.c: Monitor doohicky got event Alarm
on channel 4 [Oct 20 09:04:55] WARNING[2359] chan_zap.c: Detected alarm on
channel 4: No Alarm [Oct 20 09:04:55] DEBUG[2359] chan_zap.c: disabled echo
cancellation on channel 4

I suspect this alarm status is normal behaviour?

vi /etc/zaptel.conf
# Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER)
fxoks=1
fxoks=2
fxsks=3
fxsks=4

# Global data

loadzone        = nz
defaultzone     = nz

vi /etc/asterisk/zapata.conf
;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300              ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines ;
;usedistinctiveringdetection=yes

sendcalleridafter=2
callerid=asreceived
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
;echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include genzaptelconf configs
#include zapata-auto.conf

vi /etc/asterisk/zapata-auto.conf
; Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit ; Zaptel
Channels Configurations (zapata.conf) ; ; This is not intended to be a
complete zapata.conf. Rather, it is intended ; to be #include-d by
/etc/zapata.conf that will include the global settings ;

; Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER) ;;;
line="1
WCTDM/0/0 FXOKS (In use)"
signalling=fxo_ks
callerid="Channel 1" <6001>
mailbox=6001
group=5
context=from-internal
channel => 1
calleridmailboxgroupcontext=default

;;; line="2 WCTDM/0/1 FXOKS (In use)"
signalling=fxo_ks
callerid="Channel 2" <6002>
mailbox=6002
group=5
context=from-internal
channel => 2
calleridmailboxgroupcontext=default

;;; line="3 WCTDM/0/2 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 3
context=default

;;; line="4 WCTDM/0/3 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 4
context=default

dmesg seems OK
zaptel: no version for "oslec_echo_can_traintap" found: kernel
tainted.
Zapata Telephony Interface Registered on major 196 Zaptel Version: 1.4.9.2-
Zaptel Echo Canceller: OSLEC Zaptap registered 'sample' char driver on
major
33 Freshmaker version: 73 Freshmaker passed register test Module 0:
Installed -- AUTO FXS/DPO Module 1: Installed -- AUTO FXS/DPO Module 2:
Installed -- AUTO FXO (FCC mode) Module 3: Installed -- AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)

lsmod | grep zaptel
zaptel                198328  20
xpp,wcusb,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,wct4xxp,tor2,wctdm
oslec                  13848  1 zaptel
crc_ccitt               6337  1 zaptel

-All 4 lights on the board are lit green.
-The FXS ports work fine.
-The issue occurs on both FXO ports (i.e. channel 3 and 4)

Any suggestions appreciated.

Cameron

On Mon, Oct 20, 2008 at 04:28:30PM +1300, CSB wrote:
> I installed Trixbox and a TDM400P with 2 FXO and 2 FXS ports and am having
> an annoying issue with the FXO ports. As soon as I plug either one into the
> phone line it's as though the line is disconnected i.e. get
disconnected
> tone when trying to dial out, line is busy when dialling in.
Err... it should be exactly the other way around. You should have an
alarm when you disconnect.

What version of zaptel is it?

  cat /sys/modules/zaptel/version
> 
> The CLI shows the following:
> trixbox1*CLI> zap show channel 4
> Channel: 4
> File Descriptor: 18
> Span: 11*
> Extension: 
> Dialing: no
> Context: from-pstn
> Caller ID: 
> Calling TON: 0
> Caller ID name:
> Destroy: 0
> InAlarm: 1
> Signalling Type: FXS Kewlstart
> Radio: 0*
> Owner: <None>
> Real: <None>
> Callwait: <None>
> Threeway: <None>
> Confno: -1
> Propagated Conference: -1
> Real in conference: 0
> DSP: no1*
> Relax DTMF: no
> Dialing/CallwaitCAS: 0/0
> Default law: ulaw
> Fax Handled: no
> Pulse phone: no
> Echo Cancellation: 128 taps unless TDM bridged, currently OFF Actual
> Confinfo: Num/0, Mode/0x0000 Actual Confmute: No Hookstate (FXS only):
> Onhook
> 
> When plugged in:
> trixbox1*CLI> zap show channel 4
> Channel: 4
> File Descriptor: 18
> Span: 11*
> Extension: 
> Dialing: noI
> Context: from-pstn
> Caller ID: I
> Calling TON: 0
> Caller ID name:
> Destroy: 0
> InAlarm: 0
It wasn't in alarm. Up until 1.4.22 there was no initial check for an
alarm on the channels at startup, hence the alarm status at startup
might be incorrect.
> Signalling Type: FXS Kewlstart
> Radio: 0*
> Owner: <None>
> Real: <None>
> Callwait: <None>
> Threeway: <None>
> Confno: -1
> Propagated Conference: -1
> Real in conference: 0
> DSP: no1*
> Relax DTMF: no
> Dialing/CallwaitCAS: 0/0
> Default law: ulaw
> Fax Handled: no
> Pulse phone: no
> Echo Cancellation: 128 taps unless TDM bridged, currently OFF Actual
> Confinfo: Num/0, Mode/0x0000 Actual Confmute: No Hookstate (FXS only):
> Offhook
> 
Is this Zaptel 1.4.11?
> When cable plugged in:
> [Oct 20 09:02:56] DEBUG[2359] chan_zap.c: Monitor doohicky got event No
more
> alarm on channel 4 [Oct 20 09:02:56] NOTICE[2359] chan_zap.c: Alarm cleared
> on channel 4
"alarm cleared" - no longer in alarm. This should not disconnect a
call.
But it should have not been in a call in the first place (though see the
above comment about initial alarm status).
> 
> When cable unplugged:
> [Oct 20 09:04:55] DEBUG[2359] chan_zap.c: Monitor doohicky got event Alarm
> on channel 4 [Oct 20 09:04:55] WARNING[2359] chan_zap.c: Detected alarm on
> channel 4: No Alarm [Oct 20 09:04:55] DEBUG[2359] chan_zap.c: disabled echo
> cancellation on channel 4
Again, exactly the reverse alarm than it should be.

To see the status of alarms: 

  cat /proc/zaptel/1 

If there is 'RED' on a channel, it is in alarm.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir