How to Change your proxy

[IanNoga]

If you want to change your proxy there is a forum that includes links to a WIKI article about the magicJack which includes step by step instructions on how to change your proxy.

http://www.dslreports.com/forum/r218176 ... ange-howto

[IanNoga]

Here is the direct link in order to find out how to change your proxy in order to better your call quality and eliminate the "choppy voice."

http://en.wikibooks.org/wiki/MagicJack/ ... y_proxy.3F

[az2008]

Here is the direct link in order to find out how to change your proxy in order to better your call quality and eliminate the "choppy voice."

http://en.wikibooks.org/wiki/MagicJack/ ... y_proxy.3F

Choppy voice can be caused by more than that. The FAQ section at that site has a how-to for fixing choppy voice. That how-to links to the proxy-change how-to as one of the possible contributors.

The proxy-change how-to needs to be updated because three people have reported that even though the changed the proxy, the vms/RTP connections were still occurring from the old region (they didn't change to the new region of the new proxy). So, it may need to be changed to include some info about blocking the vms servers too.

It's getting complicated because it seems like Dan is eliminating the vms1, 2, 3 hostnames. And, many MJ hosts can't be nslookup'ed any more. So, the process in the how-to will be to repeatedly watch which vms server IP is being used, and if it's in the old region, block it too, and restart.

When I blocked a vms address for an incoming call, to force it to come in from a different region, it behaved oddly. It never rang on my computer. Went to voice mail immediately a couple times, and then began to work. It seemed to take awhile for the MJ server to figure out it needed to contact me differently.

All of this would have worked better if Dan hadn't stopped using hostnames (which could be remapped in the host file). But, what's interesting about this is that it demonstrates MJ's "fail over" capability isn't working right. All we're doing is exercising that capability. The fact that it gets confused isn't proof that the solution doesn't work, but that MJ's failover doesn't work. If a proxy or vms server became inaccessible for some reason (network issue), it would perform just as badly as it does when we make those servers inaccessible on purpose.

So, Dan didn't intend it. But, he's revealing more flaws in the service.

Mark