This Echo problem was like Skype when I first got it a few years back .. but the
last year I have had NO echo .. so maybe dan should talk with Skype Suport
and ask them what they did
I've had my MJ for about a month and have been doing a lot of tweaking to get better sound quality. After getting a new router with qos and a new Panasonic phone I thought I was there, but then had the dreaded echo, but tried the *67 trick and now the echo is gone! I live in Georgia with a 770 area code.
I've been getting an echo for the last few days. I don't get it calling another MagicJack, nor to my cell phone, nor does the other party hear the echo, but I hear about a 1 second echo when I call my sbc land-line as well as other land-lines. My mom's MJ has this problem on an XP desktop, and I have this on my XPe client.
I tried the *67 work around and it does seem to stop the echo, though dialing *671*23-4567 is kinda a pain. Plus incoming calls from landlines have the echo on my side and there doesn't seem to be a work around for that.
booyah5 wrote:I've been getting an echo for the last few days. I don't get it calling another MagicJack, nor to my cell phone, nor does the other party hear the echo, but I hear about a 1 second echo when I call my sbc land-line as well as other land-lines. My mom's MJ has this problem on an XP desktop, and I have this on my XPe client.
I tried the *67 work around and it does seem to stop the echo, though dialing *671*23-4567 is kinda a pain. Plus incoming calls from landlines have the echo on my side and there doesn't seem to be a work around for that.
Don't expect too much from this service for $20.00 a year. You should have other means of making calls like a reliable cell phone. I have a cell phone (pay-as-you-go) and a cheap SIP softphone service for which I pay $10.00 a shot at .02 cents a minute in case I have to make a call to my job (which is in the echo area code) or in case of emergency.
Yeah I've been having bad echo lately on certain calls. Some have it, some don't. I'm debating on if it's worth me spending $100+ on a new phone that's on that Compatibility list for MJ. Hmmmmmmmmmmm.
At least in my case, its NOT the phone. I've switched from cordless to corded and back - no change. Also, if it was the phone, you'd have echo on ALL calls, not just some calls. Again, in my case its only calls within my own area code and occasionally adjacent area codes. Also, the echo goes away and comes back - its MJ's problem and not the phone.
@hsweiss,
It could still be the phone. Did you try an old rotary phone or an old analog pushbutton phone? I was reading in Whirlpool forums that alot of the expensive phones (Uniden) have echo and when they tried cheaper phones (Panasonic, General Electric), the echo was gone. I'm going to try an old analog phone later tonight and will post my results. If other people with this problem could also make these types of tests it would be beneficial to users on this forum.
I too still have the echo. I was chatting with tech support yesterday (unrelated issue - MJ would not authenticate with the SIP proxy) and did an "oh by the way" when they asked if there was anything else they could do for me. We tried a bunch of things including another computer (happened to have my laptop right there) - bottom line was nothing helped. The guy told me that he would send the specific numbers that I was complaining about to the "engineers to work on." Back to square one. BTW, I was trying to change my proxy server to see if I could get rid of the echo when I ran into the SIP authentication problem. I have a NY area code and MJ is using the NY proxy (proxy1.newyork.talk4free.com). I tried changing to the Baltimore proxy (proxy1.baltimore.talk4free.com) by playing with the hosts file. I don't know what they've changed (other threads talk about this working) but at least in my case, I couldn't make any calls and Wireshark was showing SIP authentication rejections. The tech support guy had to "refresh my account" (as he called it) to make things work again.
hsweiss wrote:I too still have the echo. I was chatting with tech support yesterday (unrelated issue - MJ would not authenticate with the SIP proxy) and did an "oh by the way" when they asked if there was anything else they could do for me. We tried a bunch of things including another computer (happened to have my laptop right there) - bottom line was nothing helped. The guy told me that he would send the specific numbers that I was complaining about to the "engineers to work on." Back to square one. BTW, I was trying to change my proxy server to see if I could get rid of the echo when I ran into the SIP authentication problem. I have a NY area code and MJ is using the NY proxy (proxy1.newyork.talk4free.com). I tried changing to the Baltimore proxy (proxy1.baltimore.talk4free.com) by playing with the hosts file. I don't know what they've changed (other threads talk about this working) but at least in my case, I couldn't make any calls and Wireshark was showing SIP authentication rejections. The tech support guy had to "refresh my account" (as he called it) to make things work again.
Just to comment on changing the proxy. I also tried this to no avail. I changed mine to proxy1.nashville.talk4free.com and the result was that it did nothing, no change, just the same echo. I just deleted it from my host file with no residual problems. I didn't try the analog phone yet being that it's to awkward to use anyway even if it worked. It would be nice if people in the 914, 718, or 845 area codes that don't have the echo (if there are any) to report what brand and type of phone they are using. This might or might not solve the issue for some people.
I just got my MJ but thought I would comment. Most of my calls have been pretty clear but I made one today that had a horrible echo.. It was in the same area code as other calls I've made (574) so maybe the problem is more telco provider (the call I made could have been in verizons area..not sure.?) specific than area code specific..? Seems to me like a problem that we probably can't do anything about like moisture in the telco lines or humidity or some such fiddle faddle.. Come to think of it it did rain a alot when I made the call with echo.. lol who knows...
I've had absolutely no change in my echo to calls within the same area code. I've emailed twice to Dan, Richard, Marvin (all the guys who've previously answered for Dan) - email seems to now be falling on blind eyes. No response at all. Maybe their tired of hearing about this? Anyone else have the problem cleared up in their locale?
Just curious - how goes the 'echo wars' with the rest of you?
Personally, every night I call a Home Depot automated answering system in the 718 area code to see if the echo is still there *before* I make any "real" calls. And up thru last night, I *still* have the #$@#@ echo on calls to 718 area code numbers (from my 718 area code magicjack).
I've gotten no more responses from the "dan - the inventor" email address. I got a few responses to try various things, and then an admission that they were "working on the problem" but that was several months ago and there's been no change.
Has anyone else seen any changes or like me, you're just living with the echo and using the *67x* dialing (which I must admit, still gets rid the the echo 100% of the time).
We have echo and it is choppy.. a whole mess of issues. We have two phones in the same house sharing the conenction. I have switched everyting onto the machine that has the working phone switching out parts to see what would work and what wouldnt. By putting that Mj on my computer I introduced the echo to my computer. I think the software on some MJ are corrupted, or do not install properly. As soon as I removed the software and reinstalled using the good MJ my phone after some tweaking was back to working.
It doesnt matter where we call on that line, it just stinks.
I made a mistake on Sun and dialed a 718 number w/o the *67 "fix." I figured I'd wait to hear the echo and just tell the other end I'd call them back. No echo!! Then I tried another 718 call - No ECHO. I would intermittently get echo on calls to 516 (Long Island) but I made 2 such calls yesterday and guess what - No ECHO!
Have they FINALLY figured it out and fixed this??? (I say excitedly hoping....)
Try lowering the volume of your headset or handset. It sounds like you've got a local problem. Tech support usually suggests a volume level of 1/3 max. Adjust as you see fit.
Either I'm doing something wrong, or they changed the function of *67
I tried dialing my cellphone - 678-xxx-xxxx by dialing *676*78-xxx-xxxx, it rang, beeped a couple of times and a voice said "You have reached the Ymax test number, this call was successful", then a couple more beeps, and it hung up.
It doesnt work for me. I have a work phone 919-733-xxxx which I tried to dial as *679*19-733-xxxx. After a few seconds a recording starts that says "You have reached the YMAX communications test number, the call succeeded".
Went out to the wiki and saw the info about inserting * in between the first and second digits. When I do this I hear silence for several seconds (no ringing) and then the dial tone. No dice for me.
gtburgin wrote:Went out to the wiki and saw the info about inserting * in between the first and second digits. When I do this I hear silence for several seconds (no ringing) and then the dial tone. No dice for me.
Try it a few more times, at different times. What you described is the same what happens when the number is busy.
The reason is MJ seems to drop the last digit when you add an *. Look at your softhone. Add the last digit and click send and pick up your phone. Works for me that way. A pain in the ass yes, but it does work..
Works for me, too. Yes, it is a pain - why doesn't MJ fix this? I don't know what adding the * does, but I'm sure MJ does. It would seem simple enough to just do that for everyone - problem solved. That just baffles me.
Does anyone have any ideas how to reduce echo on a SPA 2102? I have the echo suppression settings enabled under "Line 1" tab. Doesn't seem to help much. I occasionally get bad echos when making local calls (within 269 area code).
- B3
(Th*#i`~s sta`~tic i`#s m^aki~`ing me th*#ir~s`ty)
b3wh169 wrote:Does anyone have any ideas how to reduce echo on a SPA 2102? I have the echo suppression settings enabled under "Line 1" tab. Doesn't seem to help much. I occasionally get bad echos when making local calls (within 269 area code).
Try changing your proxy server. I had horrible echo when calling within the 718 area code but not others. When I changed to a non-NY proxy, the problem went away. Before I changed proxy servers, I had to exclusively use the *67 stuff (which no longer works with the version of the MJ software that is currently being used).