FXS Problem with R24FXX

btrent98
Posts: 6
Member Since:
2009-04-28

I'm running TrixBox CE 2.6.2.2 and have a R24FXX card with 4 FXO and 1 FXS modules installed. I've run setup-rhino and then setup-pstn. I've tested the first FXO port and can send and receive calls to a trunk (Zap channel 1). However, I can't get a dialtone or place/receive a call on the analog phone I've plugged into the first FXS port (Zap channel 9). I do have power connected to the card and the LEDs all seem to be in a reasonable state. From looking at the SureTeq site and searching around it seems that I should probably at least get dialtone, but all I get is a background 60-cycle hum. I can hear hook signals and dialtones when I press keys on the phone. I'm guess I not sure how to proceed from here. Note that the zapata_additional.conf I've attached below is trying to set the extension of the analog phone to 6009 (matching the entry for channel 9 in zapata-auto.conf). I've tried other extension settings as well, since I'm not sure whether to match that setting or not, but I get the same (non-)result. Any ideas?

CONTENTS OF 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: Rhino RCB24FXX/1 "Rhino RCB24FXX/1" (MASTER)
;;; line="1 FXO/1/0"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
context=default

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

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

;;; line="4 FXO/1/3"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 4
context=default

;;; line="5 FXO/1/4"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 5
context=default

;;; line="6 FXO/1/5"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 6
context=default

;;; line="7 FXO/1/6"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 7
context=default

;;; line="8 FXO/1/7"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 8
context=default

;;; line="9 FXS/1/8"
signalling=fxo_ks
callerid="Channel 9"
mailbox=6009
group=5
context=from-internal
channel => 9
callerid=
mailbox=
group=
context=default

;;; line="10 FXS/1/9"
signalling=fxo_ks
callerid="Channel 10"
mailbox=6010
group=5
context=from-internal
channel => 10
callerid=
mailbox=
group=
context=default

CONTENTS OF ZAPATA_ADDITIONAL.CONF:

;--------------------------------------------------------------------------------;
; Do NOT edit this file as it is auto-generated by trixbox. All modifications to ;
; this file must be done via the web gui. There are alternative files to make ;
; custom modifications. ;
;--------------------------------------------------------------------------------;
;

;;;;;;[6009]
signalling=fxo_ks
pickupgroup=
mailbox=6009@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
context=from-internal
callprogress=no
callgroup=
callerid=device
busydetect=no
busycount=7
accountcode=
channel=>9



satish.vagadia
Posts: 3
Member Since:
2009-05-22
Facing Exact Problem

Barry, I am getting same problem. I tried lots of alternative configurations but no luck :(.

I have 1 FXS and 5 FXO modules. After connecting the analog phone to one of the FXS port, I am getting shutter closing sound when the marching LEDs get off on PCI card.



jfinstrom
Posts: 2008
Member Since:
2007-03-07
Can you post the output of

Can you post the output of dmesg | grep crbfx

Thanks

--



satish.vagadia
Posts: 3
Member Since:
2009-05-22
Output of dmesg

rcbfx 1: Rhino PCI BAR0 60000000 IOMem mapped at f8952000
rcbfx 1: Waiting for response from card .........
rcbfx 1: Firmware Version 2.0
rcbfx 1: Firmware File Version is 2.0
rcbfx 1: Hardware version 11
rcbfx 1: G168 DSP App file size = 50928 c6f0
rcbfx 1: G168 DSP Ping DSP Version 106
rcbfx 1: G168 DSP Active and Servicing 12 Channels - fff
rcbfx 1: Starting DMA
rcbfx 1: Spotted a Rhino: Rhino RCB24FXX (6 modules)



satish.vagadia
Posts: 3
Member Since:
2009-05-22
More information

At a time of system booting and zaptel is not loaded (after giving command "sh /etc/init.d/zaptel stop") then left most LED on card is flashing.

once the driver is loaded (zaptel with rcbfx module) then LEDs is scrolling from left to right (the led is getting on and off from left to right) continuously, when right most led gets off then there is shutter closing sound on handset receiver.

Left = towards the output of card
Right = towards the inside direct where we give external power supply to rhino card

Hope, I am able to explain properly!!!



btrent98
Posts: 6
Member Since:
2009-04-28
Info you requested

I presume you meant "rcbfx", not, "crbfx". The output of "dmesg | grep crbfx" is nothing. The output of "dmesg | grep rcbfx" on my machine is very similar to what satish posted previously:

rcbfx 1: Rhino PCI BAR0 fdbff000 IOMem mapped at f8a00000
rcbfx 1: Waiting for response from card .........
rcbfx 1: Firmware Version 2.0
rcbfx 1: Firmware File Version is 2.0
rcbfx 1: Hardware version 10
rcbfx 1: G168 DSP App file size = 50928 c6f0
rcbfx 1: G168 DSP Ping DSP Version 106
rcbfx 1: G168 DSP Active and Servicing 10 Channels - 3ff
rcbfx 1: Starting DMA
rcbfx 1: Spotted a Rhino: Rhino RCB24FXX (5 modules)



jfinstrom
Posts: 2008
Member Since:
2007-03-07
All seems okay from there

All seems okay from there Next step is to have you roll back to 1.F to see what that does.. most of the changes in 2.0 are simply for FXO

1. Pull down the file:
wget http://ftp.rhinoequipment.com/Drivers/Firmware/RCBFX/1.15/rcbfx.f... -O /lib/firmware/rcbfx.fw
2. Stop Asterisk:
amportal stop
killall -9 asterisk
3. Unload the analog module
rmmod rcbfx
4. Reload the module forcing the firmware:
insmod $(modinfo rcbfx | grep filename | awk '{print $2}' ) force_fw=1
5. Load the channels in to zaptel:
ztcfg -vvv
6: Restart Asterisk

--



btrent98
Posts: 6
Member Since:
2009-04-28
No change

I followed your instructions, then rebooted to restart Asterisk. I grep'd through the dmesg output again and confirmed that firmware version 1.f was loaded.

No change on the behavior of my FXS extension. Hum but no dialtone, hear tones when keys are pressed and clicks going on/off hook.



jfinstrom
Posts: 2008
Member Since:
2007-03-07
btrent: go ahead ans submit

btrent: go ahead ans submit a ticket to helpdesk [at] rhinoequipment.com

--



btrent98
Posts: 6
Member Since:
2009-04-28
Thanks

I opened a ticket as you suggested. Thanks for your help.



Comment viewing options

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