Cannot hear caller after a couple of minutes

Having issues with your magicJack? Post here, and we'll try to help you out!

Moderators: Bill Smith, Pilot

Post Reply
dd5087
MagicJack Newbie
Posts: 3
Joined: Sun Jan 31, 2010 10:49 am

Cannot hear caller after a couple of minutes

Post by dd5087 »

Running MJ on a Thin Client and my Internet speeds never drop below 3 Mbps down and 2 Mbps up, so this is not a PC load or internet speed issue. The call starts fine but a couple of minutes into the call, I can no longer hear the caller. It's just dead. They can still hear me because I tell them to call me on my cell and they immediately do. This happens on the majority of calls, a few calls don't experience the problem. Anyone have any idea what this problem is? It's bad enough to make me consider moving on to something else.
VaHam
Dan Should Pay Me
Posts: 851
Joined: Wed Feb 13, 2008 8:02 pm

Re: Cannot hear caller after a couple of minutes

Post by VaHam »

dd5087 wrote:Running MJ on a Thin Client and my Internet speeds never drop below 3 Mbps down and 2 Mbps up, so this is not a PC load or internet speed issue. The call starts fine but a couple of minutes into the call, I can no longer hear the caller. It's just dead. They can still hear me because I tell them to call me on my cell and they immediately do. This happens on the majority of calls, a few calls don't experience the problem. Anyone have any idea what this problem is? It's bad enough to make me consider moving on to something else.
It sounds as though you have an RTP problem. Signaling takes place on the lower ports 80,443,5060,5070 but the audio paths are on changing higher numbered UDP ports (10000-65535).

Since your call starts out ok then your router must be opening the higher RTP port ok initially but later is having NAT issues.

Since your running a thin client you can test to see if it is router NAT issue by placing the thin client temporarily in the DMZ. Just don't commit any changes to the thin client until after you have removed the TC from the DMZ and rebooted it to clear out any nasties which my have come in while it was in the DMZ. If your calls work fine then it is defiantly a NAT issue.

If your using the windows firewall on your thin client make sure you have the UPnP framework checked as an exception. Most modern routers will open the higher port and keep it open for you using UPnP.

Also, to be safe, make sure the windows firewall has an exception entry for Magicjack. That entry is typically to C:\Documents and Settings\Administrator\Application Data\mjusbsp\magicJack.exe on a thin client. You can click on Add in the firewall manager and navigate to the magicjack.exe and enable it that way if it is not already an option to check in the firewall list of exceptions.

If these are set ok then perhaps there is a problem in your router's UPnP setup.
Sad Times Ahead for this Obamanation !!!! Psalms 109:8
Diggs
Dan isn't smart enough to hire me
Posts: 268
Joined: Fri May 14, 2010 2:57 pm

Post by Diggs »

Make sure your USB ports are not set to power saving and go to sleep.
greendl
MagicJack Newbie
Posts: 3
Joined: Sun Aug 24, 2008 8:55 pm

Post by greendl »

I have this problem also after a a couple years of use it started in the last 6 months. I have MJ under its own user account in windows 7

It sometimes happens to me when I first dial out or answer. Usually the only remedy is to restart the MJ software and then it works fine - temporarily.

It works the same under two different routers and I did make sure the USB ports aren't using power saving.

It seems like a software problem but my MJ won't work with my laptop or from the motherboard USB ports - only a powered USB hub so I wonder if a new device would solve my problems.

update:
After an hour with live chat explaining how it would not work with another computer they agreed to send me a replacement for $10 S/H
English_Jean
magicJack Apprentice
Posts: 21
Joined: Fri Jun 13, 2008 2:50 pm

Post by English_Jean »

I've had the same problem for about two-three months. Rebooting corrects it for a while but it's getting more frequent.
Post Reply