Yes I have read it, and what I see is that this guy was also including the line “echocanceller=oslec,1-2” same as me, but unfortunately for me does not work, this is the way where I obtain the invalid argument message…
I can go far with my problem, I dismiss my installed hardware echo canceller (beacuse I am unable to make it work) and then when I try with oslec same result. Actually Im with mg2 but wanna use hwec or oslec.
To diagnose your issue you should start to provide a little bit more information about your system (updated or not? are you running FreePBX Distro 4.211.64-7 or what?)/FreePBX Modules (updated or not?)/Which Kernel Modules were loaded? …more or less as reported on the comments of that Ticket.
What happens if, from CLI, you run: dahdi_cfg -vvv ?
What happens if, from CLI, you run: yum list dahdi-linux* (and also yum list dahdi-tools*) ?
What happens if, from CLI, you run: lsmod|grep dahdi ?
Did you check (using tail -f) the freepbx.log while configuring DAHDi on GUI just to see what really happens?
On the contrary…FreePBX Distro, which is based on CentOS (the latest Track 4 uses CentOS 6.4 as operative system over which Asterisk and FreePBX run), has a DAHDI implementation which supports OSLEC as per Ticket I showed you (I can also state that my system, a FreePBX 4.211.64-7, is currently working with that Software Echo Canceller on a HFC-S “Cologne Chip” based ISDN PCI Card without any problem).
You’re not running FreePBX Distro but AsteriskNow with FreePBX added: despite AsteriskNow is CentOS based too there would be other parts that differ (DAHDI rpm? Kernel?).
the oslec module needs to be in the staging part of the dahdi code when you compile it, some distro’s do that, some don’t.
One answer is to download the digium dahdi code , add the oslec code to the source tree (recipes out there in google land) and then “make” and “make install” dahdi and its ancilliary binary tools.
The dahdi module needs to be compiled against your running kernel, so any arbitrary rpm that you try and install it from will either work . . . or not depending on what your kernel is and how the module in the rpm was compiled