Choppy Audio R1T1

[goblin]

Hi there, i have 2 Rhino R1T1 cards with 2 diferente carriers, im using dahdi for configuration and i have been experiencing choppy audio, how can i start troubleshoting this issue?, is there a way for tracer a live call an see where is having the problem?

I add some information of my system to se if someone can guide me trough this issue.

Regards.


PBX in a Flash Version = 1.7.5.5 │
FreePBX Version = 2.8.1.4
Running Asterisk Version = Asterisk 1.8.2.1 Asterisk Source Version = 1.8.2.1
Dahdi Source Version = 2.4.0+2.4.0
Libpri Source Version = 1.4.11.5
IP Address = 192.168.X.X on eth0
Operating System = CentOS release 5.5 (Final)
Kernel Version = 2.6.18-194.32.1.el5 - 32 Bit

 

[euser4life]

Recently experienced issues... see this thread to see if it applies.... Did you purchase the cards recently.

http://pbxinaflash.com/community/threads/echo-on-local-calls-with-pri.10012/?t=10012

Here is what tipped me off.... In examining the dmesg output relevant to the card I saw:

R1T1: 1 DSP 1: G168 DSP Port Config failed res = 3 error = -138654224

 

[goblin]

Thank you euser4life, but we purchase this cards on last November, and my problem is that randomly, and are on two 800 numbers, local calls, so is not a pattern.

How do you got to this result?
R1T1: 1 DSP 1: G168 DSP Port Config failed res = 3 error = -138654224

And how can i test my box to see is not the Rhino card?

Tnx in advanced.

 

[euser4life]

From the command line issue

dmesg |more

dmesg |more

Then go through the output by hitting the space bar (goes to the next page of output) until you get to the portion that talks about dahdi and your r1t1. This output will let you know if your hardware echo cancellation is working.

So you have two separate cards in the same server? How do your interrupts look?

cat /proc/interrupts

 

[goblin]

Yes i have 2 R1T1 with 2 diferent carriers usin PRI EuroISDN, i recieve 2 800 numbers as inbound calls.

I cant check that today because my call center works M-F, i can provide you with that info on monday, or is the same thing with out traffic?

 

[euser4life]

It is the same thing... you can get that information anytime.

 

[goblin]

Here are my outputs....


dmesg |more

R1T1: 0 configured E1 by module_param
R1T1: pciaddr = fe411000
R1T1: claimed R1T1 PCI space
R1T1: mapped R1T1 PCI space to f82fe000
R1T1: Version 41
r1t1: 1 G168 DSP App file size = 50716 c61c
Failure to load DSP @ Address 0x00000080
R1T1: 1 DSP 1: G168 DSP App Loader Failed 4
R1T1: Spotted a Rhino: Rhino R1T1 E1/PRA version 41. Module Version 0.99.4rc1
ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 50
R1T1: 1 configured E1 by module_param
R1T1: pciaddr = fe410000
R1T1: claimed R1T1 PCI space
R1T1: mapped R1T1 PCI space to f8534000
R1T1: Version 41
Failure to load DSP @ Address 0x00000080
R1T1: 2 DSP 1: G168 DSP App Loader Failed 4
R1T1: Spotted a Rhino: Rhino R1T1 E1/PRA version 41. Module Version 0.99.4rc1

R1T1: Using HDB3/CCS coding/signaling 120 Ohms
R1T1: Calling startup (flags is 1003)
R1T1: Using HDB3/CCS coding/signaling 120 Ohms
R1T1: Calling startup (flags is 1003)

dahdi: Disabled echo canceller NLP because of CED rx detected on channel 2
dahdi: Disabled echo canceller NLP because of CED rx detected on channel 2

oot@pbx:~ $ cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 146543397 16136 16157 16199 IO-APIC-edge timer
1: 0 2 0 0 IO-APIC-edge i8042
8: 0 1 2 0 IO-APIC-edge rtc
9: 0 0 0 0 IO-APIC-level acpi
12: 4 0 0 0 IO-APIC-edge i8042
50: 4716 45486 31824377 114658350 IO-APIC-level r1t1
74: 126 0 0 6742605 PCI-MSI eth0
82: 47617535 49628836 876268 48408645 IO-APIC-level r1t1
177: 7 7 7 6 IO-APIC-level ehci_hcd:usb1
185: 6191287 3121125 10157 3646 IO-APIC-level ehci_hcd:usb2
209: 5194 0 401804 0 PCI-MSI ahci
233: 4696 44800 114620489 31864681 IO-APIC-level wanpipe1
NMI: 0 0 0 0
LOC: 146598638 146598439 146598636 146598635
ERR: 0
MIS: 0

 

[euser4life]

Looks like you found your issue.....

Call Rhino....