For those using QoS, previous discussions have said MagicJack uses UDP destination ports:
- 5070 (for proxy1/SIP)
- A port in the range in 10000-20000 (for vms1/RTP).
Investigating this topic concerning TCPviewer (http://www.phoneservicesupport.com/post30425.html#30425) I noticed a call connected to vms1/RTP port 26244.
So, the 10000-20000 rule isn't true any more. It might be 10000-30000.
Anyway, there have been a lot of comments lately about MJ quality deteriorating. Those using QoS should check this connection to make sure it's in the port range they assumed it would be. If this is wrong, it will cause performance to deteriorate worse than using no QoS. In my case, the connection fell to *Lowest* priority.
Those using Hawking Broadband Booster don't have to worry about this. I don't think they do anything to configure it.
I'll update the wiki info.
Mark
IMPORTANT: QoS update (MJ uses more ports!!!)
Moderators: Bill Smith, Pilot
IMPORTANT: QoS update (MJ uses more ports!!!)
See the MagicJack Wiki (FAQ, How-To, history and more).
Thanks for the heads up Mark (aka - az2008).
I was wondering why my MJ call quality deteriorated the past couple of weeks even though I am using a dedicated MJ thin client with a Linksys WRT54GL flashed with Tomato and QoS set up per your instructions.
I did a quick check tonight and it looks like the original 10000-20000 rule isn't true any more, like you said. Per my screenshot tonight, my MJ RTP voice port ended up being 22914 and was under the lowest classification.
I've adjusted mine to 10000-30000 and it seems to have resolved the problem (for now at least).

After setting RTP voice to 10000-30000, MJ is back in the Highest classification.

I was wondering why my MJ call quality deteriorated the past couple of weeks even though I am using a dedicated MJ thin client with a Linksys WRT54GL flashed with Tomato and QoS set up per your instructions.
I did a quick check tonight and it looks like the original 10000-20000 rule isn't true any more, like you said. Per my screenshot tonight, my MJ RTP voice port ended up being 22914 and was under the lowest classification.
I've adjusted mine to 10000-30000 and it seems to have resolved the problem (for now at least).

After setting RTP voice to 10000-30000, MJ is back in the Highest classification.

Re: IMPORTANT: QoS update (MJ uses more ports!!!)
Hi,az2008 wrote: Those using Hawking Broadband Booster don't have to worry about this. I don't think they do anything to configure it.
I've noticed a deterioration in call quality the past week or so to the point MJ is not usable, I have to call back on a land line. I'm using a Hawkings Broadband Booster and I've got QOS turned off on my Linksys WRT150N router turned off (and I'm hardwired to the router). So there is something else going on such as congestion on the Internet, conversations are broken up and choppy. It's worse during the day, goes away late at night when traffic is lower.
At myvoipspeed.visualware.com I'm getting MOS scores of 3.9 which seems decent.
Re: IMPORTANT: QoS update (MJ uses more ports!!!)
I agree. I went through 6-8 proxies and found a lot of variation. Some proxies (Seattle) were completely unusable. You might try changing your proxy as described on the wiki FAQ. I found Minneapolis worked well. But, if a few hundred people read this and change to it, that might not be true any longer.tony wrote: So there is something else going on such as congestion on the Internet, conversations are broken up and choppy. It's worse during the day, goes away late at night when traffic is lower.
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).
-
shurasama1283
- MagicJack Newbie
- Posts: 2
- Joined: Thu Jan 29, 2009 5:37 am
here's a link that could help, it's also someone who has done tests on UDP ports that might be used in magic jack:
http://www.moushigo.com/index.php/2009/ ... -settings/

http://www.moushigo.com/index.php/2009/ ... -settings/
I think he's talking about a commercial network which doesn't allow outbound activity. That he had to open ports going out of the firewall.shurasama1283 wrote:here's a link that could help, it's also someone who has done tests on UDP ports that might be used in magic jack:
MJ connects to destination UDP port 5070 for SIP (the proxy1 server). And, a UDP port in the range of 10000-30000 for RTP (what is often called the vms1 server, but MJ seems to be changing the server names right now). That was 10000-20000 until recently.
It also connects to other MJ server ports when the softphone starts. Such as to the provisioning and 911 server(s). Those ports could be in different ranges. For the purpose of QoS, it doesn't matter. And, for the purpose of firewalls, because the softphone initiates the connection it doesn't matter.
The only time it would matter is if someone has a very secure network, denying access to the external access except to traffic they allow.
Or, the recent Linksys routers with the buggy firmware.
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).
QOS RTP Port Range
I thought I'd post this since this forum has been so helpful in solving the many sound quality issues over my 1 1/2 years of use.
I recently noticed, at least in the San Francisco Bay area, that MJ connects to the UDP port as high as 45344. So I had to change the QOS rtp port range to reflect this. So now I use 10000-46000. If you use Tomato firmware 1.23 just check the detail page and make sure you have "Automatically Resolve Addresses" checked at the bottom to see what your range should be. I had to do this many times because it changed throughout the day before I found the highest port it used. Do this after you make an Echo test call using their 909 number or after making any call using the MJ.
Also plugging the MJ directly into the rear USB port off of the motherboard, as opposed to a front, case mounted USB port, made a noticeable difference in sound quality for me.
I recently noticed, at least in the San Francisco Bay area, that MJ connects to the UDP port as high as 45344. So I had to change the QOS rtp port range to reflect this. So now I use 10000-46000. If you use Tomato firmware 1.23 just check the detail page and make sure you have "Automatically Resolve Addresses" checked at the bottom to see what your range should be. I had to do this many times because it changed throughout the day before I found the highest port it used. Do this after you make an Echo test call using their 909 number or after making any call using the MJ.
Also plugging the MJ directly into the rear USB port off of the motherboard, as opposed to a front, case mounted USB port, made a noticeable difference in sound quality for me.