cant get card to work!
Submitted by 2cancall on Thu, 07/10/2008 - 8:32am.
Hi,
Im having a problem getting a R4FXO-EC card to work.
Everyting appears to be correct , if i do a ztcfg I get this--
Zaptel Version: 1.4.10.1
Echo Canceller: OSLEC
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)
4 channels to configure.
I notice it says 4 channels TO configure, not 4 channels configured.
However I have signalling = fxs_ks & channel => 1-4 etc. setup in my zapata-auto.conf correctly.
When I use the card it goes through to zap/g0 and tries to dial, but I just hear silence with a regular soft "click" every second
any ideas?
A couple of things to check/try
Thu, 07/10/2008 - 8:46am
Hi Andy,
I've installed the Rhino 8 FXO card in the past. Here's a couple of things that I would try/verify.
1. Ensure your /etc/asterisk/zapata.conf reflects the channels configured.
2. You may try configuring the Zaptel Trunk by channel (example - instead of g0, try 1 for trunk 1, 2 for trunk 2, etc.....
Just some suggestions.
Good luck and best regards,
Luis
The channels on the R4FXO go
Thu, 07/10/2008 - 8:52am
The channels on the R4FXO go from bottom to top (main board up) Asterisk does not interpret line presence so it is likely dialing out a dead line as it doesn't care.
Recommendations
Thu, 07/10/2008 - 10:19am
Andy,
I've only experienced the issue you're referring to, when I either:
1. Had my outbound route configured incorrectly.
2. Didn't have dialtone on the corresponding port on the FXO card.
My recommendation would be to verify both.
Make sure that you have dialtone all the way through the cable(s) that actually connect to the FXO ports on the card. It appears that the FXO channels have been installed/configured from the information in your previous posting.
Again, good luck!
Best regards,
Luis
There is definitely a
Fri, 07/11/2008 - 9:14am
There is definitely a dialtone on the lines, and zaptel is configured correctly as the asterisk console shows the zap channel connected everytime i dial.
I have noticed a strange thing though - when I run zttool I get this result-
1234
TxA 0000
TxB 1111
TxC 0000
TxD 1111
RxA 0000
RxB 1111
RxC 0000
RxD 0000
Now I may be wrong, but isnt 0101 0100 an invalid result? its not a listed one that I can find!
I should be getting 0101 0101 when the card is idle
Run cat /proc/interrupts
Fri, 07/11/2008 - 9:32am
Run cat /proc/interrupts twice and post the output of both. It seems the interrupts may not be running which would cause those bottom bits not to refresh. Also if you could post the output of dmesg | grep rcbfx
Thanks.
interrupts 1st time-
Fri, 07/11/2008 - 1:37pm
interrupts 1st time-
CPU0 CPU1
0: 16965483 0 IO-APIC-edge timer
1: 2 0 IO-APIC-edge i8042
8: 1 0 IO-APIC-edge rtc
9: 1 0 IO-APIC-level acpi
12: 5 0 IO-APIC-edge i8042
14: 151419 611 IO-APIC-edge ide0
169: 0 0 IO-APIC-level uhci_hcd:usb4
177: 17211 16921407 IO-APIC-level Rhino RCB4FXO
209: 0 0 IO-APIC-level uhci_hcd:usb1, ehci_hcd:usb5
217: 0 0 IO-APIC-level uhci_hcd:usb2
225: 87843 0 IO-APIC-level uhci_hcd:usb3, libata
233: 67 31746 PCI-MSI eth0
NMI: 0 0
LOC: 16965071 16965105
ERR: 0
MIS: 0
2nd Time-
CPU0 CPU1
0: 17003810 0 IO-APIC-edge timer
1: 2 0 IO-APIC-edge i8042
8: 1 0 IO-APIC-edge rtc
9: 1 0 IO-APIC-level acpi
12: 5 0 IO-APIC-edge i8042
14: 151761 611 IO-APIC-edge ide0
169: 0 0 IO-APIC-level uhci_hcd:usb4
177: 17211 16959728 IO-APIC-level Rhino RCB4FXO
209: 0 0 IO-APIC-level uhci_hcd:usb1, ehci_hcd:usb5
217: 0 0 IO-APIC-level uhci_hcd:usb2
225: 88059 0 IO-APIC-level uhci_hcd:usb3, libata
233: 67 31849 PCI-MSI eth0
NMI: 0 0
LOC: 17003398 17003432
ERR: 0
MIS: 0
dmesg-
rcbfx 1: Rhino PCI BAR0 fd9ff000 IOMem mapped at f8c0a000
rcbfx 1: Waiting for response from card .........
rcbfx 1: Firmware Version 1.f
rcbfx 1: Firmware File Version is 1.f
rcbfx 1: Hardware version 11
rcbfx 1: G168 07 04 DSP Loader file size = 170 App file size = 48414
rcbfx 1: G168 DSP Ping DSP Version 106
rcbfx 1: G168 DSP Active and Servicing 4 Channels - f
rcbfx 1: Starting DMA
rcbfx 1: Spotted a Rhino: Rhino RCB4FXO (4 channels)
I got the same problem too
Wed, 07/23/2008 - 6:45am
Hello Andy
I have exactly the same issue here too. did you got the solution for this problem please let me know. Last time I installed exactly the same card on same hardware. what I found is that install trixbox 2.4. update the rhino drivers using instructions available on rhino website. then update the zapel configuration for pstn and the cards were up and running. but this time it does not work at all. i am getting silence for both incoming and outgoing as well. please help me if you got the solution.
thanks
Rajesh
Andy,
I can understand your
Wed, 07/23/2008 - 8:02am
Andy,
I can understand your frustration with the situation, but I think you're giving Rhino a bad rap... When I had an issue, I called their tech support line and they offered to remote into the box to look at it and we resolved the issue in about 10 minutes. You have no one to blame but yourself for deploying a box to a remote site without testing the hardware. Is this remote site across the city or across the country or across the world? It may be painful to make a trip to a remote site for one PCI port swap, but you can consider hiring a computer tech local to the area to coordinate with you and Rhino tech support to resolve the issue. I would imagine that 1 hour or local computer tech time would be less than the cost of a plane ticket or an unhappy customer. I gave you the fix that worked for me earlier in the forum, but you threw out the option because it is a remote site (something you didn't indicate until after I made the suggestion). The more information you can give us, the better your results will be. We're all assuming that these are US lines... is that correct?
-Chris
Hang on - the box WAS tested
Wed, 07/23/2008 - 8:15am
Hang on - the box WAS tested and working before taking on site!
Originally this was on TB 2.6.0.7, but the update to 2.6.1 had new rhino drivers & setup utility built in, and since then it hasnt worked at all.
We're in the UK, so its UK line configuration etc.
However, as I said, everything worked before taking it out, and on site the lines are live and working. Just the card isnt picking up incoming lines, or dialling out properly.
Its not easy to go to the remote site, when they are using the system as well as downtime is involved. Thats why I need to look at this remotely, out of office hours when they are not using it.
OK... so you took a working
Wed, 07/23/2008 - 8:34am
OK... so you took a working production system and did a field upgrade remotely? Since the system was working previously, let's work under the assumption that there are no hardware issues...
1. Have you called Rhino support? They are really easy to work with.
2. Did you have a backup of the 2.6.0.7 system you could use instead?
3. Are the lines all analog, or are they mostly SIP with analog backup?
4. If they are all analog, it sounds like the system is down anyway and working on it should not be an issue.
5. If they are using SIP trunks, why not put in a temp server so that you can work on the primary one unfettered... This may be difficult depending on the size of the system, but you haven't given us any dimensioning information on your system other than that we know you have 4 analog lines...
6. When you upgraded zaptel etc. with to go to 2.6.1 did you remove the old rhino drivers before running the script again??
Hope this helps,
Chris
Member Since:
2006-10-26