[asterisk-bugs] [DAHDI-linux 0014995]: DAHDI_ATTACH_ECHOCAN failed on channel 1: Invalid argument(22)

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Sep 30 19:55:13 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14995 
====================================================================== 
Reported By:                sruffell
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   14995
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   text
Priority:                   normal
Status:                     acknowledged
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2009-04-29 10:37 CDT
Last Modified:              2010-09-30 19:55 CDT
====================================================================== 
Summary:                    DAHDI_ATTACH_ECHOCAN failed on channel 1: Invalid
argument(22)
Description: 
On Gentoo, it appears that the kernel is not configured to allow auto
loading of modules.  This prevents the DAHDI_ATTACH_ECHOCAN from loading
the software echo canceler requested in the /etc/dahdi/system.conf file,
and the result is an error like:

"DAHDI_ATTACH_ECHOCAN failed on channel 1: Invalid argument(22)" 

To work around this the "dahdi_echocan_<name of echocan>" could be added
to /etc/dahdi/modules

I.e.  If you have mg2 configured as the echo canceler in
/etc/dahdi/system.conf, add the line "dahdi_echocan_mg2" to
/etc/dahdi/modules.
====================================================================== 

---------------------------------------------------------------------- 
 (0127574) sruffell (administrator) - 2010-09-30 19:55
 https://issues.asterisk.org/view.php?id=14995#c127574 
---------------------------------------------------------------------- 
mancy: You must be hitting something different if just switching to mg2
fixed the problem for you.  My guess is that OSLEC wasn't built properly. 
Try just 'modprobe dahdi_echocan_oslec' and see what errors, if any, show
up when running dmesg. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-30 19:55 sruffell       Note Added: 0127574                          
======================================================================




More information about the asterisk-bugs mailing list