Kevin P. Fleming wrote: > Dave Fullerton wrote: > >> It is true that this method would require more configuration work and >> that it would probably throw people off who were used to the old method. >> However, I don't agree that it leaves more room for error. The current >> system, IMHO, has a certain amount of ambiguity to it. If I inherit a >> production system from someone, I can't tell for sure what the echo >> canceller setup is just by looking at system.conf. I have to look at >> system.conf and then know if hardware echo can is present. Aside from >> opening the case or looking at dmesg output, I'm not even sure how to >> see if a hardware echocan is present or not. > > The dahdi_scan tool will tell you whether hardware echocans are present > or not, among other methods. >
I tried that, but I didn't see anything that specified whether the echo canceller was present. Here's the output, can you tell me what I should be looking for? r...@srv210394:~# dahdi_scan [1] active=yes alarms=OK description=T2XXP (PCI) Card 0 Span 1 name=TE2/0/1 manufacturer=Digium devicetype=Wildcard TE220 (4th Gen) location=Board ID Switch 0 basechan=1 totchans=24 irq=16 type=digital-T1 syncsrc=2 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=B8ZS,AMI framing_opts=ESF,D4 coding=B8ZS framing=ESF [2] active=yes alarms=OK description=T2XXP (PCI) Card 0 Span 2 name=TE2/0/2 manufacturer=Digium devicetype=Wildcard TE220 (4th Gen) location=Board ID Switch 0 basechan=25 totchans=24 irq=16 type=digital-T1 syncsrc=2 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=B8ZS,AMI framing_opts=ESF,D4 coding=B8ZS framing=ESF Thanks, Dave _______________________________________________ -- 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
