<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> I recently upgraded my Asterisk system to Dahdi and now I have an echo <br> problem. <br> <br> I am running Asterisk 1.4.25 with Dahdi Complete 2.2.0, on a Digium <br> TE121B PCI express card with a HARDWARE echo cancellation module. All <br> this is housed on a CentOS 5.5 box, 2.6.18 Kernel. My incoming phone <br> service is an AT&T PRI (24 channel T1). <br> <br> My configs: <br> <br> ********chan_dahdi.conf********* <br> <br> [channels]<br> ; configuration for T1 card as PRI<br> language = en<br> <br> group = 1<br> echocancel = yes<br> echotraining = yes<br> signalling = pri_cpe<br> switchtype = 4ess<br> usecallerid = yes<br> context = incoming<br> channel => 1-23<br> <br> <br> ***********/etc/dahdi/system.conf************* <br> loadzone=us <br> defaultzone=us <br> span=1,0,0,esf,b8zs <br> bchan=1-23 <br> dchan=24 <br> <br> When I run dahdi_cfg -vvv I get the following:<br> <br> DAHDI Tools Version - 2.2.0<br> <br> DAHDI Version: 2.2.0.1<br> Echo Canceller(s): MG2<br> Configuration<br> ======================<br> <br> SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1)<br> <br> Channel map:<br> <br> Channel 01: Clear channel (Default) (Echo Canceler: none) (Slaves: 01)<br> Channel 02: Clear channel (Default) (Echo Canceler: none) (Slaves: 02)<br> Channel 03: Clear channel (Default) (Echo Canceler: none) (Slaves: 03)<br> Channel 04: Clear channel (Default) (Echo Canceler: none) (Slaves: 04)<br> Channel 05: Clear channel (Default) (Echo Canceler: none) (Slaves: 05)<br> Channel 06: Clear channel (Default) (Echo Canceler: none) (Slaves: 06)<br> Channel 07: Clear channel (Default) (Echo Canceler: none) (Slaves: 07)<br> Channel 08: Clear channel (Default) (Echo Canceler: none) (Slaves: 08)<br> Channel 09: Clear channel (Default) (Echo Canceler: none) (Slaves: 09)<br> Channel 10: Clear channel (Default) (Echo Canceler: none) (Slaves: 10)<br> Channel 11: Clear channel (Default) (Echo Canceler: none) (Slaves: 11)<br> Channel 12: Clear channel (Default) (Echo Canceler: none) (Slaves: 12)<br> Channel 13: Clear channel (Default) (Echo Canceler: none) (Slaves: 13)<br> Channel 14: Clear channel (Default) (Echo Canceler: none) (Slaves: 14)<br> Channel 15: Clear channel (Default) (Echo Canceler: none) (Slaves: 15)<br> Channel 16: Clear channel (Default) (Echo Canceler: none) (Slaves: 16)<br> Channel 17: Clear channel (Default) (Echo Canceler: none) (Slaves: 17)<br> Channel 18: Clear channel (Default) (Echo Canceler: none) (Slaves: 18)<br> Channel 19: Clear channel (Default) (Echo Canceler: none) (Slaves: 19)<br> Channel 20: Clear channel (Default) (Echo Canceler: none) (Slaves: 20)<br> Channel 21: Clear channel (Default) (Echo Canceler: none) (Slaves: 21)<br> Channel 22: Clear channel (Default) (Echo Canceler: none) (Slaves: 22)<br> Channel 23: Clear channel (Default) (Echo Canceler: none) (Slaves: 23)<br> Channel 24: D-channel (Default) (Echo Canceler: none) (Slaves: 24)<br> <br> 24 channels to configure.<br> <br> Setting echocan for channel 1 to none<br> Setting echocan for channel 2 to none<br> Setting echocan for channel 3 to none<br> Setting echocan for channel 4 to none<br> Setting echocan for channel 5 to none<br> Setting echocan for channel 6 to none<br> Setting echocan for channel 7 to none<br> Setting echocan for channel 8 to none<br> Setting echocan for channel 9 to none<br> Setting echocan for channel 10 to none<br> Setting echocan for channel 11 to none<br> Setting echocan for channel 12 to none<br> Setting echocan for channel 13 to none<br> Setting echocan for channel 14 to none<br> Setting echocan for channel 15 to none<br> Setting echocan for channel 16 to none<br> Setting echocan for channel 17 to none<br> Setting echocan for channel 18 to none<br> Setting echocan for channel 19 to none<br> Setting echocan for channel 20 to none<br> Setting echocan for channel 21 to none<br> Setting echocan for channel 22 to none<br> Setting echocan for channel 23 to none<br> Setting echocan for channel 24 to none<br> <br> <br> It is showing MG2 as the echo canceller, even though I don't have an echo canceller specified. Is that the harwdare module? Do I even need to specify an echo canceller in the configs if I have a hardware echo module? <div class="moz-signature">-- <br> <title></title> <p><font face="Arial, Helvetica, sans-serif"><b>Jason Baker<br> </b><font color="#660000"><span style=""><i>IT Coordinator</i></span></font></font></p> <font color="#000099" face="Arial, Helvetica, sans-serif"><b> Glastender, Inc.</b></font><br> <font size="2">5400 North Michigan Road<br> Saginaw, Michigan 48604 USA<br> Phone: 989.752.4275 ext. 228<br> Fax: 989.752.4276</font><br> <a href="http://www.glastender.com/">www.glastender.com</a> </div> </body> </html>
Jason, Echo Hellooo old buddy! Do you evefr go 4 the dCap? Your bud from the MD class. Al On Tue, Aug 25, 2009 at 4:43 PM, Jason Baker <jbaker at glastender.com> wrote:> I recently upgraded my Asterisk system to Dahdi and now I have an echo > problem. > > I am running Asterisk 1.4.25 with Dahdi Complete 2.2.0, on a Digium > TE121B PCI express card with a HARDWARE echo cancellation module. All > this is housed on a CentOS 5.5 box, 2.6.18 Kernel. My incoming phone > service is an AT&T PRI (24 channel T1). > > My configs: > > ********chan_dahdi.conf********* > > [channels] > ; configuration for T1 card as PRI > language = en > > group = 1 > echocancel = yes > echotraining = yes > signalling = pri_cpe > switchtype = 4ess > usecallerid = yes > context = incoming > channel => 1-23 > > > ***********/etc/dahdi/system.conf************* > loadzone=us > defaultzone=us > span=1,0,0,esf,b8zs > bchan=1-23 > dchan=24 > > When I run dahdi_cfg -vvv I get the following: > > DAHDI Tools Version - 2.2.0 > > DAHDI Version: 2.2.0.1 > Echo Canceller(s): MG2 > Configuration > =====================> > SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1) > > Channel map: > > Channel 01: Clear channel (Default) (Echo Canceler: none) (Slaves: 01) > Channel 02: Clear channel (Default) (Echo Canceler: none) (Slaves: 02) > Channel 03: Clear channel (Default) (Echo Canceler: none) (Slaves: 03) > Channel 04: Clear channel (Default) (Echo Canceler: none) (Slaves: 04) > Channel 05: Clear channel (Default) (Echo Canceler: none) (Slaves: 05) > Channel 06: Clear channel (Default) (Echo Canceler: none) (Slaves: 06) > Channel 07: Clear channel (Default) (Echo Canceler: none) (Slaves: 07) > Channel 08: Clear channel (Default) (Echo Canceler: none) (Slaves: 08) > Channel 09: Clear channel (Default) (Echo Canceler: none) (Slaves: 09) > Channel 10: Clear channel (Default) (Echo Canceler: none) (Slaves: 10) > Channel 11: Clear channel (Default) (Echo Canceler: none) (Slaves: 11) > Channel 12: Clear channel (Default) (Echo Canceler: none) (Slaves: 12) > Channel 13: Clear channel (Default) (Echo Canceler: none) (Slaves: 13) > Channel 14: Clear channel (Default) (Echo Canceler: none) (Slaves: 14) > Channel 15: Clear channel (Default) (Echo Canceler: none) (Slaves: 15) > Channel 16: Clear channel (Default) (Echo Canceler: none) (Slaves: 16) > Channel 17: Clear channel (Default) (Echo Canceler: none) (Slaves: 17) > Channel 18: Clear channel (Default) (Echo Canceler: none) (Slaves: 18) > Channel 19: Clear channel (Default) (Echo Canceler: none) (Slaves: 19) > Channel 20: Clear channel (Default) (Echo Canceler: none) (Slaves: 20) > Channel 21: Clear channel (Default) (Echo Canceler: none) (Slaves: 21) > Channel 22: Clear channel (Default) (Echo Canceler: none) (Slaves: 22) > Channel 23: Clear channel (Default) (Echo Canceler: none) (Slaves: 23) > Channel 24: D-channel (Default) (Echo Canceler: none) (Slaves: 24) > > 24 channels to configure. > > Setting echocan for channel 1 to none > Setting echocan for channel 2 to none > Setting echocan for channel 3 to none > Setting echocan for channel 4 to none > Setting echocan for channel 5 to none > Setting echocan for channel 6 to none > Setting echocan for channel 7 to none > Setting echocan for channel 8 to none > Setting echocan for channel 9 to none > Setting echocan for channel 10 to none > Setting echocan for channel 11 to none > Setting echocan for channel 12 to none > Setting echocan for channel 13 to none > Setting echocan for channel 14 to none > Setting echocan for channel 15 to none > Setting echocan for channel 16 to none > Setting echocan for channel 17 to none > Setting echocan for channel 18 to none > Setting echocan for channel 19 to none > Setting echocan for channel 20 to none > Setting echocan for channel 21 to none > Setting echocan for channel 22 to none > Setting echocan for channel 23 to none > Setting echocan for channel 24 to none > > > It is showing MG2 as the echo canceller, even though I don't have an echo > canceller specified. Is that the harwdare module? Do I even need to specify > an echo canceller in the configs if I have a hardware echo module? -- > > *Jason Baker > **IT Coordinator* > * Glastender, Inc.* > 5400 North Michigan Road > Saginaw, Michigan 48604 USA > Phone: 989.752.4275 ext. 228 > Fax: 989.752.4276 > www.glastender.com > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2009 - October 13 - 15 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090825/ebf4d03c/attachment.htm
Jason Baker wrote:> I recently upgraded my Asterisk system to Dahdi and now I have an echo > problem. > > I am running Asterisk 1.4.25 with Dahdi Complete 2.2.0, on a Digium > TE121B PCI express card with a HARDWARE echo cancellation module. All > this is housed on a CentOS 5.5 box, 2.6.18 Kernel. My incoming phone > service is an AT&T PRI (24 channel T1). > > My configs: > > ********chan_dahdi.conf********* > > [channels] > ; configuration for T1 card as PRI > language = en > > group = 1 > echocancel = yes > echotraining = yes > signalling = pri_cpe > switchtype = 4ess > usecallerid = yes > context = incoming > channel => 1-23 > > > ***********/etc/dahdi/system.conf************* > loadzone=us > defaultzone=us > span=1,0,0,esf,b8zs > bchan=1-23 > dchan=24 > > When I run dahdi_cfg -vvv I get the following: > > DAHDI Tools Version - 2.2.0 > > DAHDI Version: 2.2.0.1 > Echo Canceller(s): MG2 > Configuration > =====================> > SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1) > > Channel map: > > Channel 01: Clear channel (Default) (Echo Canceler: none) (Slaves: 01)<snip>> Channel 23: Clear channel (Default) (Echo Canceler: none) (Slaves: 23) > Channel 24: D-channel (Default) (Echo Canceler: none) (Slaves: 24) > > 24 channels to configure. > > Setting echocan for channel 1 to none<snip>> Setting echocan for channel 24 to none > > > It is showing MG2 as the echo canceller, even though I don't have an echo > canceller specified. Is that the harwdare module? Do I even need to specify an > echo canceller in the configs if I have a hardware echo module?MG2 is a software canceller. I don't think that line means that MG2 is being used on all your channels. If you look at the Channel map it says "(Echo Canceler: none)". If it had been set to MG2 you would see MG2 instead of none. You do not need to specify an echo canceller in system.conf when you have a hardware canceller. One thing I would check is to make sure asterisk is activating the echo canceller when a call is in progress. To do this execute "core show channels" at the asterisk command line (make sure someone on the system has placed a call on the PRI). Look for a DAHDI/#-x line. Then execute "dahdi show channel #" where # is the channel number. You'll get a screen full of output. Look for a line that looks like this (it will be near the end): Echo Cancellation: 128 taps unless TDM bridged, currently ON The "currently ON" is telling you that the echo canceller is active. You could try changing echotraining to no in chan_dahdi.conf as well. What were you running before you upgraded? -Dave