Need people with echo problems
i'm your man
Mon, 07/16/2007 - 10:16am
hello Kerry,
i have TB1.2.3 with TDM400 in my Labo test, with 2 FXO lines and 2FXS analog phones
i have also 2 other machines in a very important production environment (callcenter)
1st machine: inbound : 1 TE110p
2nd machine outbound :1 TE212P with integrated hardware echo-canceller (Nerver worked)
I have a PRI circuit that
Mon, 07/16/2007 - 10:32am
I have a PRI circuit that exhibits echo unless I use Mark II Aggressive echo cancellation in Zaptel. I can build a test box if you have something new to try. The 2.2 RPM that includes a patch for Octasic doesn't fail back to a working echo canceler, so I compile from source, or build my own RPM without Octasic.
- Jason
I have a home use machine TB
Mon, 07/16/2007 - 1:05pm
I have a home use machine TB 2.2, PIII600/512MB RAM with a TDM01B(I believe...it has 1 FXO) and SPA-2000 and 1 Linksys 942. I get echo on the analog line unless I turn the gain of the ZAP channeldown. The sip channel is fine with no echo and is a comfortable volume. I've tried adjusting it to no avail (using kerry's great guide) but I always have to have the analog line turned down so much that it is barely useable. I tried other echo cancelers (again using the echo cancelation guide), but the echo was worse and I went back to stock. I was considering using the Octastic soft echo product but am open to other suggestions.
i have tdm400
Mon, 07/16/2007 - 1:58pm
i have been having echo issues with tdm400 w/ 4fxo on one card and 1 fxo on the 2nd card.
we are running trixbox 2.2 with octastic in place. i have been able to capture the echo with the extension that is giving us the most trouble currently.
Chris knows about the server and could provide any details i don't know.
thanks
tsean
Ok, so here is what we have.
Wed, 07/18/2007 - 1:58pm
Ok, so here is what we have. We have a means of removing the currently installed zaptel, and then you can install the version of zaptel that you would like to use.
Keep in mind that this is the FIRST BETA of this process, so unless you know exactly what you are doing and can fix something if it goes badly, you might want to wait a few days. So for the more technical of you, here are some basic instructions, if you do not know what to do based on these instructions, again, please wait a few days because if something goes wrong, you can really hose up your phone system.
To start, this will all need to be done from the command line right now.
1. In your repos file, make sure that beta and devel are NOT enabled at this time.(from the repos file, not from the trixbox dashboard)
2. yum -y update asterisk zaptel
3. rpm -del zaptel-modules-2.6.9-34.0.2.EL
4. Enable the Devel repo (from the repos file, not from the trixbox dashboard)
You can now install the different available zaptel modules:
Octasic
yum install zaptel-echo_octasic-modules-2.6.9-34.0.2.EL
MKII
yum install zaptel-echo_mg2-modules-2.6.9-34.0.2.EL
OSLEC (Open Source Line Echo Cancelation -- NEW)
yum install zaptel-echo_oslec-modules-2.6.9-34.0.2.EL
If you want to try the OSLEC (please please test this) then you need to follow the rest of the steps below:
edit /etc/asterisk/zapata.conf and make sure echotraining is disabled
echocancel=yes
echocancelwhenbridged=no
;echotraining=400
Reboot your system. When you’re on an analog call you can type this command to watch the echo can in action.
cat /proc/oslec/info
I have a few installs with a tad bit of echo still...
Wed, 07/18/2007 - 2:42pm
tdm400 1FXO and 2FXS with Octastic Softecho. The echo is very intermittent. Also, I noticed on the last one that, also intermittently, there is that bit where there is echo for a few seconds then it clears up.
I need some advise about non Digium softecho and disabling echotraining. Should this be done in all cases, not just this new and improved kernel matching way?
With the Octasic, you will
Wed, 07/18/2007 - 3:55pm
With the Octasic, you will still need to run their register program and supply your license keys. Right now I suggest comparing OSLEC to MK2 to what you have running now. ESPECIALLY if you are running multiple channels please watch top to see what the CPU increase is with OSLEC.
As far as the echotraining I only know that with OSLEC you will get dead air if it is enabled.
Thanks, Kerry. A few typos
Wed, 07/18/2007 - 5:53pm
Thanks, Kerry. A few typos in there, but nothing that can't be fixed. In 2, did you mean to update just asterisk and zaptel? You listed asterisk twice, so I wondered if there was a third package that needed to be included in that step. In step 3, just a small typo (zero instead of a hyphen):
3. rpm -del zaptel-modules-2.6.9-34.0.2.EL
SRPMS coming soon for this?
- Jason
Here is the cleaner, step by
Thu, 07/19/2007 - 4:26pm
Here is the cleaner, step by step guide, again, please don't do this if you don't know how to fix something that breaks (or unless you are willing to pay me to fix it :) )
This is going to walk you through setting up the OSLEC echo cancelation system:
yum -y update asterisk zaptel
rpm -del zaptel-modules-2.6.9-34.0.2.EL
nano /etc/yum.repos.d/trixboxdevel.repo
-- change enabled=0 to enabled=1
ctrl-o ctrl-x
yum install zaptel-echo_oslec-modules-2.6.9-34.0.2.EL
nano /etc/asterisk/zapata.conf
-- diable echo training by commenting it out
;echotraining=400
reboot
When you’re on an analog call you can type this command to watch the echo can in action.
cat /proc/oslec/info
We switched to the olsec version
Fri, 07/20/2007 - 10:42pm
I had deployed Trixbox 2.2 at a clients with a Digium Wildcard TDM400P, using the standard zaptel modules. And we started getting really bad echo. I tried to use fxotune to correct it, but 1 phone/line wouldn't improve, it actually got worse the longer you talked on the line.
I switched it over to the oslec and as soon as I rebooted it was a night and day difference. I realized that there had been an echo on the other 3 phones that we hadn't realized was echo (now that it was gone we could hear the lack of echo). Also the Trixbox now disconnected the lines almost as soon as the remote line disconnected (it was taking ~5 seconds).
So, in short, the new oslec works great for us!
Oh and one other thing I noticed. We could hear more static on the lines, and the volume seemed louder. So I turned the phones volume down and that seemed to make them as clear and loud as they had been before we tried the oslec.
Queston
Sat, 07/21/2007 - 10:46am
How can you tell if the OSLEC is working, I'm still new to this. I've been trying to resolve echo issues for weeks. I've went throught the steps above, but still getting some echo, of course it could be me with the lack of knowlege on installing the OSLEC. Any more info on this would be great.
Mike
Constent Echo
Sun, 07/22/2007 - 5:44pm
I am having echo issues as well with the new version of the trixbox. I did not have any issues with 2.0 but when I moved to 2.2 I know have echo issues with my TDM400 with 2 analog modules. I am also running softecho as well but still have echo. The echo will sometimes go away after 6 seconds, but isn't it suppose to never be visible when using soft echo?
I'm really sorry guys but
Mon, 07/23/2007 - 8:06am
I'm really sorry guys but this is not a troubleshooting course on echo in this thread. I have posted the instructions on how to install it and if you are using OSLEC there is a command you can run during a call to know that its working. If you need more help than that then you might not want to be experimenting with these instructions just yet and you should post in the help forum. I am not trying to be rude here but I did say that if you don't know what you are doing, you should try this yet.
Just FYI I have had OSLEC
Thu, 07/26/2007 - 2:03pm
Just FYI I have had OSLEC set up for 2 months now at a site with a TDM400P and 3 PSTN lines with very good results (OSLEC and Zaptel installed from source). There was bad echo when using MG2 (I put lots of time into trying to tweak it, txgain, rxgain, fxotune and the whole bit) so we bought the Octware Softecho licenses which pretty much fixed it. When I discovered OSLEC I gave it a try just to test it and there didn't seem to be any noticeable difference between it and Octware and none of the users even noticed that anything changed! It also includes an echo sampling utility, I have sent the developer some sample files captured with it and also some feedback and I encourage any other testers to do the same as it will help him to improve OSLEC.
which zaptel should be loaded?
Sun, 07/29/2007 - 4:40am
Follow up
Mon, 07/30/2007 - 6:45am
The module switching worked for me, however I could never achieve "good" results using this method as Kerry described above. The modules would switch out fine, callers told me that I sounded "under water" or "in a helicopter" or "wurlitzer like" Even when I switched back to using just zaptel1.2.19-1 I ended up reloading 2.2, and restoring my config. Im going to try on a non-intel system tonite. I wont be able to test again until later tonight
Night and Day differnence.
Mon, 07/30/2007 - 3:27pm
Night and Day differnence. I've been having echo issues for 2 months. Have the tdm400p with 4 FXO channels. Tried differnent motherboards, downgraded trixbox, asterisk@home, nothing helped. Reading everything about echo cancelation nothing made a differnence. Installed OSLEC, NIGHT and DAY difference !!! Now I can continue and use Trixbox at the office. We go live in full production tomorrow.
Thanks
Mike
Good News!!
Tue, 07/31/2007 - 12:52pm
Ok, I was told today that in the past year that we have been running asterisk, that the phone has NEVER sounded this good before. This procedure worked, and was a smashing success so far! Thanks for your help Kerry. I am leaving this in place for sure now! The Octstatic drivers are worth it!
new update Getting braver or more dangerous!?
Tue, 07/31/2007 - 8:53pm
So I decided to give the OSLEC a run again tonight, since they were so bad, and the Octstatic was soo good, I had to believe that OSLEC didnt get a fair run. I was wrong. My POTS lines on the TDM400 suddenly ended up in a helicopter type situation. I reverted back to octstatic, and GASP - it wasnt working. I had to remove all the zaptel installs (I did this via the trixbox gui fyi :) ) and then yum -y install zaptel and then repeated the steps above, and now ocstatic is working again, and I am sold (good thing since I already paid) Please let me know if you guys make any progress on the OSLEC stuff. I would like to try it again. I really wonder if ocstatic is doing a good job of masking underlying problems on my box.
I thought it was odd
Wed, 08/01/2007 - 3:18pm
thats why I posted it. Actually, I was wrong too. I never got the system to recover. had to move everything to a new box this morning, and now my sip_additional.conf isnt updating properly either to boot. Obviously theres some other issue occurring with my system. For now, im sticking with octvqed until the next OSLEC release.
Ready to try anything at this point ;-)
Thu, 08/02/2007 - 1:35pm
I have a small physicians practice with an Asterisk box we put in for them. We have 8 Grandstream GXP-2000 phones, TDM400P with 4 FXO ports, running Asterisk 1.2.22, zaptel-1.2.18, and octvqe8-01.04.00-pr
We placed this system about 2 months ago (yes this physician is VERY patient) and had horrible echo to start, we deployed octvqed and it seemed to clear up the echo issue (mostly), but it has seemed to have creeped back in.
At COB, I am going to give this a shot and I'll let you know very quickly. I am pumped at the positive comments! :)
Rob
Robert M. Branch
Technology Evangelist
Report
Thu, 08/02/2007 - 6:14pm
Hi Kerry,
I can confirm the OSLEC rpm works great, but only when you're not running an SMP kernel. Obviously, it doesn't install into the SMP kernel module dir, so it fails miserably when under that config. But if I boot with the non-smp kernel, it works great!
This is with a Trixbox 2.2.3.
I noticed there were two zaptel rpms installed prior (both of which I deleted) - one for smp, and the other for non-smp. Why not make the one RPM do double-duty? That would be less confusing, especially if there are mixed modules.
Whatever the outcome, we -need- to have a plain zaptel (with its default EC) rpm installed. Requiring the non-free module just for a workable system isn't a good idea! :-)
Bob
FDarden: sounds like
Thu, 08/02/2007 - 6:17pm
FDarden: sounds like something didn't get properly installed or configured. This is confirmed by the fact that when you went back to octstatic, it also didn't work. Remember, you have to comment out the echo training timing for OSLEC to work. It does a very amazing job, even on a bad line that had hum on it.
Bob
echo with tdm400
Thu, 08/02/2007 - 8:30pm
i was experiencing an echo of my voice only with the tdm400 card. I installed oslec and same result.
i reinstalled, and while looking at the manual online for the tdm400 card, i realized that i did not plug in the power for the card.
i plugged it in, yum -y update ... and viola. no echo. works fantastic.
Well, I can't speak for Kerry or Fonality but...
Sat, 08/04/2007 - 8:14am
I really doubt they can "guarantee" that this will fix everything echo related. The trixbox Appliance is after all just a computer and Fonality has nothing at all to do with the Digium card.
Heck, I wouldn't expect a 100% guarantee on ANY analog card. Sure, the various EC solutions out there can work really well and if you attack the problem from different angles you can squash it in most cases, but if you do many installs you will eventually find a hard case that just doesn't want to go away. (If you stick with it and know what to look for and where you'll find the echo-gremlin hiding in the walls, but the little devils really know where to hide!)
If it concerns you too much then pop for a good hardware EC card. Rhino and Sangoma make some really nice ones. Your choice can be based on price, but don't forget expandability.
sip -> zap WORKS, zap to sip does not.
Wed, 08/08/2007 - 1:23am
Hi,
I tried the OSLEC and got into a problem
I have ZMA400P (TDM400 clone) with 1 FXS and 1FXO
With the OSLEC setup as described by kerry the following happened....
1. If I ring from a phone on the FXS port to a SIP extension all is good
2. If I ring from a SIP extension - can't hear anything on both devices
Any ideas? Has anyone done this particular test, eg SIP-ZAP ?
Luckily I got back to normal after playing with YUM and removing the new OSLEC modules ang going back.
Question on the TDM2400 series cards
Fri, 08/10/2007 - 5:16pm
Echo almost gone ...
Sat, 08/11/2007 - 12:58pm
I have two x100 oem cards ---- or not orignals
all echo is gone ...
I have Asterisk 1.2.23 and for zaptel :
zaptel-echo_oslec-modules-2.6.9-34.0.2.EL-1.2.19-2
zaptel-1.2.19-1
it seems most echo is gone ...!!!!
I have tdm cards in a another server I disconnected ... haven't tried that one yet .... soon I will
and post
Oslec echo cancelling
Mon, 08/13/2007 - 9:37am
On 3 systesm, I had terrible echo. I tried Octastic on 1 of the systems. It succeded in cancelling the echo; but, after talking on the phone for several minutes, the audio was lost an a very loud noise--sounding like static appeared (Trixbox 2.2 system) It sounded very much like timing was lost.
So, I tried Oslec on that system and it worked great.--Following Oslec instructions.
Since discovering your rpm, I've installed oslec on 3 systems with success. 2 systems installed and worked fine (TDM400 with 2 fxs & 2 fxo's) following the instructions you provided with no problem.
On the 3rd system no audio was present on Zap Line to Zap extension calls. I did not try or verify this as a problem with any of the SIP extensions. Zap extensions could call Zap extensions. I had to set EchoTraining=no for the ZAP extensions in addition to the zapata.conf modification.
Then, all was well.
Systems 1&2 are running Trixbox 2.2 with no modification (Freepbx 2.2.1). The 3rd system was running Trixbox 2.2.3 with Freepbx 2.2.2.
Quote:
This is going to walk
Tue, 08/14/2007 - 1:49pm
Quote:
This is going to walk you through setting up the OSLEC echo cancelation system:
yum -y update asterisk zaptel
rpm -del zaptel-modules-2.6.9-34.0.2.EL
nano /etc/yum.repos.d/trixboxdevel.repo
-- change enabled=0 to enabled=1
ctrl-o ctrl-x
yum install zaptel-echo_oslec-modules-2.6.9-34.0.2.EL
nano /etc/asterisk/zapata.conf
-- diable echo training by commenting it out
;echotraining=400
reboot
When you’re on an analog call you can type this command to watch the echo can in action.
cat /proc/oslec/info
Running 2.2.4, this walk through does not work for me. When zaptel-modules-2.6.9-34.0.2.EL is deleted Zaptel no longer works. During reboot i get "Module Zaptel Not Found". As soon as I re-install it, Zaptel works again, but OSLEC isn't enabled (?)
Any suggestions on how to get around this?
Wow!
Wed, 08/15/2007 - 12:10pm
What can I say? I have had horrid problems with the default echo-canceller in Trixbox 2.x on a TDM400P. I followed Kerry's excellent instructions and switched to OSLEC. It's night and day. I just ran several tests and there is no longer any echo to be heard. As far as I am concerned, this should be made the default as soon as possible.
Thanks,
Tim
OSLEC works great for non-SMP kernel, but not SMP kernel
Wed, 08/15/2007 - 11:03pm
FYI, OSLEC echo canceller is now available in Trixbox Release Repo
http://yum.trixbox.org/centos/4/RPMS/
Now it's easy to install OSLEC using yum
yum -y update asterisk zaptel
yum remove zaptel-modules-2.6.9-34.0.2.EL
yum install zaptel-echo_oslec-modules-2.6.9-34.0.2.EL
nano /etc/asterisk/zapata.conf
;echotraining=400 ;-- disable echo training by commenting it out
reboot
Above works great only if you manually boot into non-SMP kernel.
By default CentOS boots into SMP kernel, in this case you will not hear any difference in echo (because OSLEC for SMP is not installed yet). Since my DELL 440 Server has Core2 CPU, I want to install OSLEC for SMP kernel. as you can see from Release Repo, OSLEC for SMP is available, so I do
yum remove zaptel-modules-2.6.9-34.0.2.ELsmp
yum install zaptel-echo_oslec-modules-2.6.9-34.0.2.ELsmp
reboot
After reboot into SMP kernel, zaptel is not working, do a 'service zaptel start' give me this error message:
Loading zaptel framework: WARNING: Error inserting oslec (/lib/modules/2.6.9-34.0.2.ELsmp/extra/oslec.ko): Invalid module format
FATAL: Error inserting zaptel (/lib/modules/2.6.9-34.0.2.ELsmp/extra/zaptel.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Apart from undo above installs, does any one know how to fix this error?
RE: How can i disable echo cancellation on a call going to this
Thu, 08/16/2007 - 10:46pm
You may want to have a look at the following that I found on http://www.rowetel.com/ucasterisk/oslec:
3/ These options in zapata.conf are important:
echocancel=yes
echocancelwhenbridged=no
;echotraining=400The echocancelwhenbridged=no allows faxes to pass from FXS to FXO ports without interference from the echo canceller. This option is important for fax signals.
Make sure echotraining is disabled when using Oslec - this is not supported and if enabled will cause the channel to be silent (i.e. no audio will pass through).
Member Since:
2006-05-31