Echo
Moderators: Bill Smith, Pilot
If you have echo, try Tigerjet's Echo Cancellation Utility. Works for me.
http://www.tjnet.com/software/index.htm
http://www.tjnet.com/software/index.htm
- strndedinalska
- Dan isn't smart enough to hire me
- Posts: 230
- Joined: Mon Jan 21, 2008 4:39 am
- Location: Alaska
Turn down the volume on the speaker and microphone to zero. I know it shouldn't have anything to do with echo on a regular telephone, but somehow, it feeds back. That should solve your problem.
Windows Vista and Laptop with XP SP2 on the road. Occasionally, a Mac if my Windows machine isn't working.
[quote="tvland"]I don't have a solution for this. However, I do experience an echo. What I hear is myself talking. Usually, the line quality is bad when the echo happens. I have this problem with USA phone numbers. Canadian phone numbers seem much clearer and no echo.[/quote]
I've been having a similar problem - but only on calls to New York (718 area code). The MJ has a 718 area code but I don't live in NY. Calls to 410 or 443 in Maryland work fine - no echo (or very little and not a bother). But to New York 718 - its horrible. For a while, a hang-up and call-back would solve the problem but for the past week or so, its always there. I worked with tech support for about an hour last night rebooting, rebooting the router, forcing a MJ update, changing sound parameters, removing registry entries to reinstall MJ, inserting MJ w/o the USB extension cord, looking for the msg711.acm codec, etc.
Nothing worked - calls to 410 were clean but calls to 718 still had massive echo. Tech support asked which providers I was calling (both 718 and 410 are Verizon) and he was going to submit the issue and the numbers to "the concern department" and he wanted me to try again in an hour (but that was getting too late so I'll try again tonight).
In case it doesn't work tonight - has anyone seen this sort of behavior and has anyone got any suggestions beyond what the tech support guy had me do? Does this sound like a MJ problem as opposed to something on my end?
I've been having a similar problem - but only on calls to New York (718 area code). The MJ has a 718 area code but I don't live in NY. Calls to 410 or 443 in Maryland work fine - no echo (or very little and not a bother). But to New York 718 - its horrible. For a while, a hang-up and call-back would solve the problem but for the past week or so, its always there. I worked with tech support for about an hour last night rebooting, rebooting the router, forcing a MJ update, changing sound parameters, removing registry entries to reinstall MJ, inserting MJ w/o the USB extension cord, looking for the msg711.acm codec, etc.
Nothing worked - calls to 410 were clean but calls to 718 still had massive echo. Tech support asked which providers I was calling (both 718 and 410 are Verizon) and he was going to submit the issue and the numbers to "the concern department" and he wanted me to try again in an hour (but that was getting too late so I'll try again tonight).
In case it doesn't work tonight - has anyone seen this sort of behavior and has anyone got any suggestions beyond what the tech support guy had me do? Does this sound like a MJ problem as opposed to something on my end?
-
- Dan isn't smart enough to hire me
- Posts: 234
- Joined: Fri Jun 20, 2008 5:16 pm
- Location: Dallas, TX
If your getting clear calls to one area code and not another, the issue is on MJ's end...not yours. Something in thier server routing or the phone exchange system is messed up in that area.
You can also test this by calling some area codes, say from a phone book.....a company, etc. Since your not being charged, when the party answers, just say you dialed the wrong number and tell them your sorry for the mistake. This way, you can test how your phone works in other area codes other than the ones your trying to call.
You can also test this by calling some area codes, say from a phone book.....a company, etc. Since your not being charged, when the party answers, just say you dialed the wrong number and tell them your sorry for the mistake. This way, you can test how your phone works in other area codes other than the ones your trying to call.
MJ admits problems with Verizon in NY
Agreed that its MJ's problem. Last night it still had the echo to 718 but to no other area code that I tried. I too came up with the idea to just started calling stores in various parts of the country and Canada to test the echo (www.homedepot.com and www.homedepot.ca are great to get phone numbers). No echo in any other area code tried other than 718 and 516 (Long Island - adjacent to the 718 area code in NY). MJ tech support tried to get me to repeat all the usual stuff (e.g., pull out MJ, disconnect phone, reinsert MJ, reconnect phone, restart router, etc) but I told him I've been there and done that. To their credit, he transferred me "up the chain" to another support tech who as much admitted that MJ is having problems with calls to Verizon in NY and they are working on it. He told me that he would send the info to the "engineers to work on" and that I should be patient for 24-48 hours. We'll see.
-
- Dan isn't smart enough to hire me
- Posts: 234
- Joined: Fri Jun 20, 2008 5:16 pm
- Location: Dallas, TX
Well, I've still got echo on *all* calls to the 718 area code - BAD ECHO. I've chatted with tech support several more times and they told me yesterday the problem would be cleared up in 4-5 hours (it wasn't). I just chatted with them again and immediately they want to start troubleshooting my end of the connection but I tell them "been there, done that" and then throw them a quote from one of the chat transcripts I emailed to myself a few days again which says they are having problems with calls to Verizon in 718. Today they told me "the engineers are working on" and I should try again later. When I pressed them for a time of resolution they would not commit - only that "the engineers are working on it." They also admitted that anyone making calls to the 718 area code (parts of New York City) are experiencing echo so its not just me. This has been going on now for more than a week and has rendered MJ essentially useless for the bulk of our calls - driving us back to finding the one or two spots where our cell phones work. Ugh.....
I have the same problems with the area code 302. Which is my own area code that my phone number is. Only in that area code do I get an echo. If I call a number in that area code that has VOIP I do not get the echo. I try the 718 area code and do not get the echo. Tha only area I get it is in the 302 area.
Wow - that's very interesting. My MJ has a 718 number and I get the echo in calls to 718 (sometimes to 516 which is geographically adjacent to 718). However, I'm not physically located in 718's area. So it appears that the echo is present on what would be considered LOCAL calls. Wonder what's going on with the way they are controlling the echo cancellation?
Thanks to other posts I found on this forum I tried the *67 "trick" to see if I could get rid of the horrible echo. Sure enough, it did!!! I'm a happy camper (no thanks to MJ tech support). If I dial 718-xxx-xxxx I still get an echo (even if I just call a home depot that has an auto-attendant pick up the phone - if I talk to the answering machine I hear an echo). But if I dial *677*18xxx-xxxx there is NO echo.
Echo in the local calling area seems to be the theme here. While I'm not physically located in NY, I have a NY 718 area code and that's where I get the echo. Another poster had the same problem in the 302 area code (Delaware I think). Now you have the same problem. Seems like MJ has a *major* problem that they're aren't fessing up to.
As for the *67 trick - I searched this site and found that someone was having a problem dialing somewhere in Alaska and another poster told him to try a different route using * codes. The suggestion is to use *67 (which normally turns off caller ID) followed by the 1st digit of the area code followed by * and then the rest of the number.
See the following post for details - and like I said, this worked for me last night:
http://www.phoneservicesupport.com/area ... ght=alaska
As for the *67 trick - I searched this site and found that someone was having a problem dialing somewhere in Alaska and another poster told him to try a different route using * codes. The suggestion is to use *67 (which normally turns off caller ID) followed by the 1st digit of the area code followed by * and then the rest of the number.
See the following post for details - and like I said, this worked for me last night:
http://www.phoneservicesupport.com/area ... ght=alaska
Echo
I tried the Echo Cancellation Utility from TigerJet and it didn't seem to work for me? Then this is where it gets interesting tried uninstalling the program and it removed fine but left my MJ on speaker and when I go to softphone I can't click phone settings so I get sound through computer speakers and not through phone? I had to restore to a day earlier but now I am stuck with this program. So be careful installing this. I even tried reboting and uninstalling MJ from USB and magicfix update and still wouldn't reinstall what the unistall of this program removed? I f anyone finds a way of removing this without destroying my MJ software let me know. Also I am in the (302) Delaware aea code with echo problems,Rick
I also tried the TigerJet echo cancellation - and like for you it didn't do squat for me either. I did send a note to Dan complaining about this and got a reply from "Marvin" answering for Dan asking me to run dxdiag and then restart MJ. That didn't do anything either. On a follow-up, another guy responding for Dan said they were working on the problem. That was more than a week ago. I tried a call tonight and got massive echo which I was able to get rid of by using *67.
I also tried the TigerJet echo cancellation - and like for you it didn't do squat for me either. I did send a note to Dan complaining about this and got a reply from "Marvin" answering for Dan asking me to run dxdiag and then restart MJ. That didn't do anything either. On a follow-up, another guy responding for Dan said they were working on the problem. That was more than a week ago. I tried a call tonight and got massive echo which I was able to get rid of by using *67.
Can you please forward this information to the higher ups in charge of magicjack. I've been getting a continually worsening echo in the 914 and 845 area codes of southeastern new york for about three months now. I talked to 12 or 13 tech chat people who could not help me. I tried all of their solutions none of which worked. I tried unplugging and plugging back in both my modem and the magicjack device, I have installed the latest updates, I turned both the speaker and mic volumes all the way down. I tried insalling the echo cancellation utility from the tigerjet website which did not work at all, it was enabled (icon turned green). I have deleted folders and changed permissions in the registry, all of which I had to undo because it didn't work. The blue light IS on and magicjack works when dialing out to other area codes for instance, 800 numbers work fine. Long distance works fine. My phone number is in 845 area code. I have read in the forum that 718 also has echo and also is in the southeastern NY area. They suggested in the forum that this is an issue with routing and Verizon. Can you please verify this or if you don't know, can you please forward this information to the higher ups so that it gets prioritized. I have mentioned this to the other chat representatives if they could do this but I don't know if they did or not.
Just to clarify, I hear myself talking right after I talk. It also seems to be getting louder or more pronounced as of lately.
I have cable 15 mbps down, 2 mbps up. I'm on Windows XP sp3 Thanks.
Just to clarify, I hear myself talking right after I talk. It also seems to be getting louder or more pronounced as of lately.
I have cable 15 mbps down, 2 mbps up. I'm on Windows XP sp3 Thanks.
Yep - that's what I did when I sent email to Dan (as in the MJ "inventor" Dan Borislow) and a couple of his minions responded to me. I've heard from them (as well as tech support chat) that they know about echo problems with Verizon but I've never heard what they're doing about it. One of the tech chat folks said it would be cleared up in a few days, another said in a few hours. I've given up with them after having reported this problem several times to tech chat and to Dan. Using *67 allows me to make echo-free calls so as long as that trick works, I'm a relatively happy camper - it certainly beats using my cell phone after 8pm standing outside trying to get more than 2 bars of signal.
Is yours still working? Mine was working for about a day with no echo after a magicJack upgrade but now it's back to the same old echo. The *67 trick that people in this forum are buzzing about is NO solution, not even for $20 dollars per year; it's awkward to dial and incoming calls will still have the echo. Also, it works with me only for the 845 area code and not 914. I suspect there's some bullshit going on involving Verizon and magicJack and hope it gets addressed, deliberated and resolved soon.Just tried some calls to the 718 area code w/o using the *677* trick - I was amazed to hear NO echo! Yeah - they've finally fixed it (at least for tonight)!!
No, mine stopped working about 7pm (EDT) Sun - the same old *bad* echo was back again. I didn't use MJ on Sat (we were out and about so I used my cell phone) so I don't know when it reverted. But when I called back using *677*18xxx-xxxx it worked fine - no echo and decent voice quality - not quite as good as it was on Fri night when i was able to just dial 781-xxx-xxxx and had not echo, but good enough.
Did you try the Echo Canceler?kkshelton wrote:Any thoughts about addressing echo on incoming calls?
Tried and failed (see previous posts). Its still running on my machine but it does nothing to solve this echo problem. Its definitely not on this end - MJ has acknowledged that they have problems with Verizon calls. They obviously did something the other day because the echo was gone but it came back Sun and its still there as of 5 min ago when I last tried it w/o using the *67 hack.
I pinged "Dan" again for a resolve to this problem (which I still have if I don't use *67). I got a reply from "Richard" who said:
Please try the following upgrade for the magicJack to see if that helps the problem with the audio quality.
http://upgrade.talk4free.com/upgrade/20 ... pgrade.exe
Run the upgrade with the magicJack plugged in. When done, restart the computer and then make some calls with the magicJack.
Sincerely,
Richard
magicJack Tech Support Manager
I thought I'd share this in case it works for others - unfortunately it didn't do anything for me. Echo is still there. Not clear what the upgrade fixed. I responded to "Dan" and told them it didn't work. So far, no response.
Please try the following upgrade for the magicJack to see if that helps the problem with the audio quality.
http://upgrade.talk4free.com/upgrade/20 ... pgrade.exe
Run the upgrade with the magicJack plugged in. When done, restart the computer and then make some calls with the magicJack.
Sincerely,
Richard
magicJack Tech Support Manager
I thought I'd share this in case it works for others - unfortunately it didn't do anything for me. Echo is still there. Not clear what the upgrade fixed. I responded to "Dan" and told them it didn't work. So far, no response.
I'll check mine later when I get home. I had more email with Richard from tech support who said they were looking into echo cancellation issues with Verizon in the 718 area code. I replied telling him that I new of the same problems in (at least) the 302, 914, and 845 area codes. Maybe they found the problem?
Thanks for including the 914, 845 area codes in your correspondence with the higher ups.hsweiss wrote:I'll check mine later when I get home. I had more email with Richard from tech support who said they were looking into echo cancellation issues with Verizon in the 718 area code. I replied telling him that I new of the same problems in (at least) the 302, 914, and 845 area codes. Maybe they found the problem?
Unfortunately I tried calling again in the 845 area code after I read your post and the echo is back again not two or three hours later. It seems even worse too. We can only hope that they are testing things and it will be back to normal soon.
Still have echo
Ditto - I still have echo. I won't say its worse than it was, but it certainly isn't any better.
My # area code 949 - echo on all calls
I have an echo, the other end does not hear. I can hear myself a fraction of a second after speaking. I have tried the things listed here.
Just wanted to let you all know that 949 is my dialing out number. I have an echo on every call... I have called several area codes in Florida, CA, 800 numbers, Arizona.
Any luck anyone?
Mari
Just wanted to let you all know that 949 is my dialing out number. I have an echo on every call... I have called several area codes in Florida, CA, 800 numbers, Arizona.
Any luck anyone?
Mari
Fixed
I installed the 'update' listed in this thread for July 2008, and the echo is completely gone from the both the phone and the USB headset. I have had my MJ 1 week today. Go figure; I am not complaining. I found no "UPDATES" on the MJ site. How did one get this url for the updates? How will we know in the future if there are updates?
I tried to access other directories for this URL talk4free, but no luck.
Thanks,
Mari
I tried to access other directories for this URL talk4free, but no luck.
Thanks,
Mari
That's because you downgraded to a lower number version, so for your particular circumstance, something in the July version is working for you that's not working for me. I already tried downgrading from a few links that I found but no luck. All upgrades are automatically downloaded and installed in your MJ upon startup so you don't have to worry about finding it anywhere. Hope yours keeps working.
-
- MagicJack Contributor
- Posts: 52
- Joined: Sun May 18, 2008 3:12 pm
I don't hear an echo but other person does
I tried both of the tips I have found on the forum 1) turned the volume down to zero and 2) installed TJEC but one person I talk to insists that he hears an echo on his end. He is not using MJ but Verizon. Any suggestions?
Thanks. Joe
Thanks. Joe
What you think of me is none of my business.
-
- magicJack Apprentice
- Posts: 24
- Joined: Sun Aug 03, 2008 12:46 pm
Re: I don't hear an echo but other person does
I've suffered with the same problem. I had my daughter call me using MJ to a Verizon line during "heavy echo season." If she just dialed 718-251-xxxx she got massive echo. When she dialed *677*18-251-xxxx she had no echo but I had some echo on my Verizon end. We also tried playing around with the volume sliders - made no difference what-so-ever. I did find that last night I had some echo on my end calling a 212 (Manhattan) number but if I talked with lower volume, it was almost imperceptible.magicjackjoe wrote:I tried both of the tips I have found on the forum 1) turned the volume down to zero and 2) installed TJEC but one person I talk to insists that he hears an echo on his end. He is not using MJ but Verizon. Any suggestions?
Thanks. Joe
Given that the echo went away over the weekend but came back Mon morning, they must be working on it. I sent another note to "Dan" (I've actually been getting responses from "Richard" from tech support) to tell them that it went away but came back. So far no reply.Mudgemania wrote:Help us Mr. Wizard... we really like our MagicJack's.