Tom, I believe with 2.6 you need to specify the echo canceler used. In the past, if none was specified a default was used. That behavior changed and you must now specify one in the DAHDI system.conf
Examples: echocanceller=hwec,<channels> (if you have hardware ec) . Other options include mg2, kb1 Hope that gets you in the right direction. Darrick -----Original Message----- From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] Sent: Friday, August 17, 2012 3:23 AM To: 'AstLinux Users Mailing List' Subject: Re: [Astlinux-users] [Astlinux-devel] AstLinux 1.0.4 Released > Any DAHDI syslog errors with AstLinux 1.0.4 ? Looks like it might be the echo canceller: wctdm24xxp 0000:00:0e.0: Error pinging DSP (2) This error is not present in 1.0.2. > From the asterisk prompt "dahdi restart" any errors with AstLinux 1.0.4 ? ingrampbx*CLI> dahdi restart Destroying channels and reloading DAHDI configuration. Initial softhangup of all DAHDI channels complete. Final softhangup of all DAHDI channels complete. == Unregistered channel -2 == Unregistered channel 1 == Unregistered channel 2 == Parsing '/etc/asterisk/chan_dahdi.conf': Found [Aug 17 09:04:55] WARNING[2919]: chan_dahdi.c:1313 dahdi_open: Unable to specify channel 1: Device or resource busy -- Reconfigured channel 1, FXS Kewlstart signalling -- Reconfigured channel 2, FXS Kewlstart signalling -- Automatically generated pseudo channel == Parsing '/etc/asterisk/users.conf': Found Not sure if that WARNING is a concern. I have no other DAHDI boxes with which to compare. > From the CLI prompt "show-union", any dahdi files/modules shown ? Not exactly DAHDI, but the echo canceller again: /oldroot/mnt/asturw/lib /oldroot/mnt/asturw/lib/firmware /oldroot/mnt/asturw/lib/firmware/zaptel-fw-vpmadt032.bin > Possibly "dahdi_tool" from the CLI might shed some light. Compare > results 1.0.2 vs. 1.0.4 1.0.2 and 1.0.4 both give: Current Alarms: No alarms. Sync Source: Internally clocked IRQ Misses: 3 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 4/ 2/ 2 > Possibly a DAHDI config error effects you with DAHDI 2.6 and not with DAHDI 2.5. Maybe a UK thing. Possibly. No idea what, though. I'll check my DAHDI config. Thanks for the help. Any other ideas? Do you think the "Error pinging DSP" could point towards something? Could the VPMADT032 have failed? I had major problems with that module back at Astlinux 0.7.2, and it related to the driver for that module. Thanks Tom ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
