OpenVox A400P12 FXS problem

andyb2000
Posts: 13
Member Since:
2006-11-18

Hi all,
I've just got my new A400P card, with 2 FXO and 1 FXS. Plan is to terminate two POTS, and connect one legacy old phone handset (no option to change this unfortunately).

So, I've got the card working, done all the zap stuff, and the two FXO ports are working fine, inbound and outbound, callerid and all that works (here in the UK).

However, I'm not even getting a dial-tone when I connect up a phone handset to the FXS port. It appears to be there/working, calls try to ring the extension, etc just nothing on the phone itself. Have tried changing the phone, sockets, etc and still nothing.
I've been very careful not to connect the FXS port to anything other than the phone handsets, etc as I've read about the voltage spikes from the POTS causing the cards to fry, etc.

Can anyone offer any suggestions? Here are the details of the system:

software versions:
trixbox CE 2.6.1.1

Logging when calling the extension shows what you expect:

Quote:
VERBOSE[25011] logger.c: -- Executing [s@macro-dial:7] Dial("Local/203@from-internal-aecf,2", "ZAP/3||trM(auto-bl
kvm)") in new stack
VERBOSE[25011] logger.c: -- Called 3
VERBOSE[25008] logger.c: -- Local/203@from-internal-aecf,1 is ringing
VERBOSE[25011] logger.c: -- Zap/3-1 is ringing
VERBOSE[25011] logger.c: -- Zap/3-1 is ringing

(Zap/3-1 is the FXS port being on port 3 on the A400 card)

/etc/zaptel.conf

Quote:
# Span 1: WCTDM/0 "Wildcard TDM400P REV E/F Board 1" (MASTER)
fxsks=1
fxsks=2
fxoks=3
loadzone = uk
defaultzone = uk

/etc/asterisk/zapata.conf

Quote:
[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
cidsignalling=v23 ; Added for UK CLI detection
cidstart=polarity ; Added for UK CLI detection
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=incoming
#include zapata-auto.conf
group=1
;Include AMP configs
#include zapata_additional.conf

/etc/asterisk/zapata-auto.conf

Quote:
; Span 1: WCTDM/0 "Wildcard TDM400P REV E/F Board 1" (MASTER)
;;; line="1 WCTDM/0/0"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
context=default

;;; line="2 WCTDM/0/1"
signalling=fxs_ks
callerid=asreceived
group=1
context=from-zaptel
channel => 2
context=default

;;; line="3 WCTDM/0/2"
signalling=fxo_ks
callerid="Channel 3" <6003>
mailbox=6003
group=5
context=from-internal
channel => 3

/etc/asterisk/zapata_additional.conf

Quote:
;;;;;;[203]
signalling=fxo_ks
record_out=Adhoc
record_in=Adhoc
mailbox=203@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
dial=ZAP/3
context=from-internal
callprogress=no
callerid=device <203>
busydetect=no
busycount=7
accountcode=
channel=>3

Thanks in advance, hope I've given enough info for somebody to spot my mistakes!

Regards,

Andy



huebs73
Posts: 93
Member Since:
2006-09-27
Some things to check

I am not totally positive, because I don't think you will see any activity in your CLI output with verbosity without power, but make sure you have power to the card. This is required for the FXS modules only. Again, not sure, becuase I have never looked at the output with a card and an FXS module installed without power, but I am a disbtributor for Openvox here in the states and this is a common item overlooked. After that, I would check the FXS module itself by replacing/swapping out. Could be a bad module. Of course change out the line cord from the A400P output to the phone, and also perhaps try another phone. Hope you get it working, but if not, send an e-mail to Openvox support and they will work with you.



andyb2000
Posts: 13
Member Since:
2006-11-18
Hmm, Well checking further,

Hmm,
Well checking further, power is definately fine, and everything else looks OK. I also have done a few further tests:

[trixbox1.localdomain zaptel-1.4.11]# ./fxstest /dev/zap/3 stats
TIP: -5.6400 Volts
RING: -53.7680 Volts
VBAT: -62.7920 Volts
[trixbox1.localdomain zaptel-1.4.11]# ./fxstest /dev/zap/3 ring
Ringing phone...
Phone is ringing...
[trixbox1.localdomain zaptel-1.4.11]# ./fxstest /dev/zap/3 stats
TIP: -5.6400 Volts
RING: -53.7680 Volts
VBAT: -62.7920 Volts
[trixbox1.localdomain zaptel-1.4.11]# ./fxstest /dev/zap/3 polarity
Twiddling polarity...
Polarity is forward...
Polarity is reversed...
Polarity is forward...
[trixbox1.localdomain zaptel-1.4.11]# ./fxstest /dev/zap/3 stats
TIP: -5.6400 Volts
RING: -53.7680 Volts
VBAT: -62.7920 Volts
[trixbox1.localdomain zaptel-1.4.11]#

So as you can see, I think all that is fine. Any more ideas anyone??



SkykingOH
Posts: 2597
Member Since:
2007-12-17
Did you compile fxstest on

Did you compile fxstest on the system? I did not think it was included with the distribution.

--

Scott

aka "Skyking"



andyb2000
Posts: 13
Member Since:
2006-11-18
Yeah, did a manual compile,

Yeah, did a manual compile, which was a real pain, as many libraries and other items were missing, so did various yum installs/compiles (I've used linux for many years now, so am familiar with the process).

** would be nice to have something like trixbox-debug as a package, that installed things like fxstest, zap sources, asterisk sources, things like that for debugging problems, dev's?? **



andyb2000
Posts: 13
Member Since:
2006-11-18
OK, my bad. I've finally

OK, my bad.
I've finally found when work was carried out in the building, the phone cable had been damaged.

Apologies to everyone, its working fine.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.