TDM800P Echo Cancellation Not Detected

depster · June 14, 2011, 3:11pm

TDM800 card was previously installed in different hardware with AsteriskNow 2.7. That box has been decommissioned and the card moved to new hardware with the FreePBX distro.

Upon configuring the system it appears that the hardware echo cancellation board is not being detected. The following is a portion of dmesg:

dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.4.0 PCI: Enabling device 0000:02:0b.0 (0014 -> 0017) PCI: Found IRQ 9 for device 0000:02:0b.0 PCI: Sharing IRQ 9 with 0000:00:1f.4 wctdm24xxp 0000:02:0b.0: Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp 0000:02:0b.0: Port 2: Installed -- AUTO FXO (FCC mode) wctdm24xxp 0000:02:0b.0: Port 3: Installed -- AUTO FXO (FCC mode) wctdm24xxp 0000:02:0b.0: Port 4: Installed -- AUTO FXO (FCC mode) wctdm24xxp 0000:02:0b.0: Port 5: Installed -- AUTO FXO (FCC mode) wctdm24xxp 0000:02:0b.0: Port 6: Installed -- AUTO FXS/DPO wctdm24xxp 0000:02:0b.0: Port 7: Not installed wctdm24xxp 0000:02:0b.0: Port 8: Not installed wctdm24xxp 0000:02:0b.0: Failed to load the firmware. wctdm24xxp 0000:02:0b.0: Found a Wildcard TDM: Wildcard TDM800P (0 BRI spans, 6 analog channels) dahdi_transcode: Loaded. INFO-xpp: revision Unknown MAX_XPDS=64 (8*8) INFO-xpp: FEATURE: without BRISTUFF support INFO-xpp: FEATURE: with PROTOCOL_DEBUG INFO-xpp: FEATURE: with sync_tick() from DAHDI INFO-xpp_usb: revision Unknown usbcore: registered new driver xpp_usb dahdi: Registered tone zone 0 (United States / North America) wctdm24xxp 0000:02:0b.0: -- Setting echo registers: wctdm24xxp 0000:02:0b.0: -- Set echo registers successfully wctdm24xxp 0000:02:0b.0: -- Setting echo registers: wctdm24xxp 0000:02:0b.0: -- Set echo registers successfully wctdm24xxp 0000:02:0b.0: -- Setting echo registers: Bluetooth: HIDP (Human Interface Emulation) ver 1.1 i2c /dev entries driver NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver ip_tables: (C) 2000-2006 Netfilter Core Team eth0: no IPv6 routers present dahdi_echocan_mg2: Registered echo canceler 'MG2'

I have scanned through the configuration files and have not come across any lines commenting out anything to do with echo cancellation.

Ideas?

depster · June 16, 2011, 3:48pm

Installed DAHDI v.2.4.1.2+2.4.1 and hardware echo board was detected.

Any reason why the repo doesn’t hold this version?

tonyclewis · June 16, 2011, 3:50pm

Because we were testing them. We just published those RPM’s and are working on the upgrade script today or tomorrow that will upgrade dahdi and a few other things.

stonet · June 16, 2011, 4:39pm

I am right in the middle of installing the Distro on a new box using a disc I burnt a week or soo ago for version 1.8.1.4. I just got a message that the specified dahdi firmware package does not exist. I did not abort the installation and have left it to procede.

Sounds like this is associated with the above, will the upgrade script put this right?

stonet · June 16, 2011, 5:41pm

I should have included the fail message text above:

You have specified the package ‘dahdi-firmware-2.0.0.1_centos5’ should be installed. This package does not exist. Would you like to continue or abort the installation?

tonyclewis · June 16, 2011, 5:45pm

Yes 1 of our 3 yum servers was not syncing correct. I am working on recovering that now and getting it back up and than publishing the upgrade.

stonet · June 16, 2011, 5:52pm

I left things to install while I went to have lunch and came back to find this error message:

There was an error running your transaction, for the following reason(s): file conflicts

Reboot

I re-booted and the system came back with the grub> prompt.

I have installed the Distro on several other systems and had no problems. As you are working on various things with dahdi and the like I am wondering if these problems are associated or if there is something else unrelated that is causing these problems?

stonet · June 16, 2011, 5:54pm

Thanks Tony, my last message crossed with yours. I will wait until you have things sorted before doing anything else.

tonyclewis · June 16, 2011, 9:03pm

Guys

Newest upgrade is published that fixes the dahdi-firmware issue. Please upgrade.

http://www.freepbx.org/forum/freepbx-distro/distro-discussion-help/release-versions

Also the 1.8.4.x disk that has been out for a few weeks of the ISO will automatically still work and install this latest release.

Thanks for the feedback.

stonet · June 20, 2011, 6:08pm

Everything working great again, just installed two systems.

pinazo · June 21, 2011, 3:03pm

When I upgrade DAHDI through Admin Module, I get this error after the process:
exit: 1
found language dir fr for directory, not installed on system, skipping
Failed to backup old config: Permission denied
[FATAL] INSERT INTO dahdi_spans (span, framing, definedchans, coding, signalling, switchtype, syncsrc, lbo, pridialplan, prilocaldialplan, group, context) VALUES [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘’ at line 1]

Trace Back:

/var/www/html/admin/modules/dahdiconfig/functions.inc.php:1107 die_freepbx()
[0]: INSERT INTO dahdi_spans (span, framing, definedchans, coding, signalling, switchtype, syncsrc, lbo, pridialplan, prilocaldialplan, group, context) VALUES [nativecode=1064 ** You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘’ at line 1]

/var/www/html/admin/modules/dahdiconfig/functions.inc.php:461 dahdi_cards->write_spans()

/var/www/html/admin/modules/dahdiconfig/functions.inc.php:184 dahdi_cards->load()

/var/www/html/admin/modules/dahdiconfig/functions.inc.php:34 dahdi_cards->dahdi_cards()

/var/lib/asterisk/bin/retrieve_conf:399 dahdiconfig_conf->dahdiconfig_conf()

1 error(s) occurred, you should view the notification log on the dashboard or main screen to check for more details.

And in the FreePBX notices:

Symlink from modules failed Ignore this

retrieve_conf failed to sym link:
/etc/asterisk/chan_dahdi.conf from dahdiconfig/etc
This can result in FATAL failures to your PBX. If the target file exists and not identical, the symlink will not occur and you should rename the target file to allow the automatic sym link to occur and remove this error, unless this is an intentional customization.
Added 16 hours, 54 minutes ago
(retrieve_conf.SYMLINK)

tonyclewis · May 11, 2012, 7:05pm

Yes the old Echo Cancellation modules for analog cards used a special firmware that will not compile with Dahdi 2.6 is what I have been told by numerous people.

tonyclewis · May 11, 2012, 7:06pm

Have you tried rebooting. I wonder if it just never loaded the new dahdi after the upgrade. Also check the update logs to see if their are any errors.

stonet · May 11, 2012, 7:38pm

I had already reboooted the system after the upgrade so don’t think that was the problem, however, the very strange thing is that I just took the system down to remove the echo canceller module to return it to Digium and when the system came back up it is now showing dahdi 2.6.1 and the software mg2 canceller has kicked in and the echo has disappeared.

stonet · May 11, 2012, 6:37pm

I spoke to Digium support, they are sending me a replacement hardware echo canceller module, they believe it may be a hardware/software incompatibility as the echo canceller is four years old. I am impressed, they are doing this free of charge.

The proof of the pudding will be in the eating when I get the new module we will know if that is indeed the problem.

It would still be good to know why I have not gone to dahdi 2.6.1 with the upgrade?

stonet · May 11, 2012, 5:27pm

I had noticed this as well, have checked that I am definitely on 1.811.210.57-2 but a dahdi show version from the asterisk command line shows DAHDI Version: 2.6.0 Echo Canceller: HWEC, MG2. It is interesting that it does recognize the hardware canceller is present although the firmware has not loaded. I did a fxotune and that has dropped the echo to a level where it is possible to talk but it is still there.

I did upgrade from the scripts and it would seem that Dahdi has not gone to 2.6.1, I wonder why?

stonet · May 11, 2012, 1:59am

I have just installed a Digium AEX800 card in a system at Distro 1.811.210.57-2. I am experiencing heavy echo. It seems to me that the firmware for the hardware echo canceler has not loaded. This looks like a similar problem to the one discussed in this thread. Does anyone have any insight into this.

Here is the relevant dmesg output:

dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.5.0.1
ACPI: PCI Interrupt 0000:08:08.0[A] -> GSI 40 (level, low) -> IRQ 210
wctdm24xxp 0000:08:08.0: Port 1: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 2: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 3: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 4: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 5: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 6: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 7: Installed – AUTO FXO (FCC mode)
eth0: no IPv6 routers present
wctdm24xxp 0000:08:08.0: Port 8: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Failed to load the firmware.
wctdm24xxp 0000:08:08.0: Found a Wildcard TDM: Wildcard AEX800 (0 BRI spans, 8 analog channels)
dahdi_transcode: Loaded.
INFO-xpp: revision Unknown MAX_XPDS=64 (88)
INFO-xpp: FEATURE: without BRISTUFF support
INFO-xpp: FEATURE: with PROTOCOL_DEBUG
INFO-xpp: FEATURE: with sync_tick() from DAHDI
INFO-xpp_usb: revision Unknown
usbcore: registered new driver xpp_usb
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
ip_tables: © 2000-2006 Netfilter Core Team
usbcore: deregistering driver xpp_usb
NOTICE-xpp: toplevel_release
dahdi_transcode: Unloaded.
wctdm24xxp 0000:08:08.0: Freed a Wildcard
ACPI: PCI interrupt for device 0000:08:08.0 disabled
dahdi: Telephony Interface Unloaded
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.6.0
PCI: Enabling device 0000:08:08.0 (0140 -> 0143)
ACPI: PCI Interrupt 0000:08:08.0[A] -> GSI 40 (level, low) -> IRQ 210
wctdm24xxp 0000:08:08.0: Failed to load the firmware.
wctdm24xxp 0000:08:08.0: Port 1: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 2: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 3: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 4: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 5: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 6: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 7: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Port 8: Installed – AUTO FXO (FCC mode)
wctdm24xxp 0000:08:08.0: Found a Wildcard TDM: Wildcard AEX800 (0 BRI spans, 8 analog channels)
dahdi_transcode: Loaded.
INFO-xpp: revision Unknown MAX_XPDS=64 (88)
INFO-xpp: FEATURE: with PROTOCOL_DEBUG
INFO-xpp: FEATURE: with sync_tick() from DAHDI
INFO-xpp_usb: revision Unknown
usbcore: registered new driver xpp_usb
wctdm24xxp 0000:08:08.0: – Setting echo registers:
wctdm24xxp 0000:08:08.0: – Set echo registers successfully
wctdm24xxp 0000:08:08.0: – Setting echo registers:
wctdm24xxp 0000:08:08.0: – Set echo registers successfully
wctdm24xxp 0000:08:08.0: – Setting echo registers:
wctdm24xxp 0000:08:08.0: – Set echo registers successfully

depster · May 11, 2012, 11:26am

It appears that you are still running DAHDI 2.6.0. 1.811.210.57-2 should have upgraded you to DAHDI 2.6.1.

Did you install FreePBX Distro recently, or have you been running the upgrade scripts?

stonet · May 29, 2012, 10:37pm

Just to close this off, I received the hardware echo canceller module from digium and firmware loaded correctly and it is working just fine.

stonet · June 22, 2012, 1:53pm

Digium replaced the old VPMADT032 module with a VPMOCT032 module which cured the problem, however, when I upgraded another system I encountered the same problem, firmware not loading to a VPMADT032 module.

This time when I contacted Digium they asked if they could look at the system as the VPMADTO32 module should be compatible with the latest Dahdi version so I granted them access to the system.

Digium advised that they were unable to find the firmware for the VPMADT032 module on the system and that they were able to load the firmware once they had corrected this.

It seems to me that the Distro may only be pulling firmware for the VPMOCT032 and not for the VPMADT032.

Has anyone encountered a similar problem?