Fix Magic Jack Problems by Tweaking and Changing Your Proxy Settings

Distinguishing/Changing Your MagicJack Proxy to fix call quality issues

MagicJack is selling quickly all around the nation. This is incredible for the parent organization, yet can introduce difficulties for the customers that buy the gadget, especially on the off chance that you live in one of their jam-packed business sectors (for example for me in Atlanta). I've been chipping away at a few hints and deceives to advance MagicJack and fix some basic issues, and this one unravels the issue referenced previously. In the wake of encountering a few pops and splits in my calls, I began contemplating whether perhaps the MagicJack worker was somewhat over-burden, and provided that this is true, was there an approach to change the worker. In the wake of scouring through each program choice, I understood that there wasn't an approach to indicate an alternate worker from inside the MagicJack application, yet having a decent comprehension of systems administration, I was certain I could discover a few stunts.

After experimentation, I found that if a MagicJack worker wasn't accessible, it naturally steered to the following accessible worker, so for my situation, if the Atlanta worker was down for reasons unknown, I would be consequently directed to the following nearest worker, or Memphis, TN. To make MagicJack believe that Atlanta was down, I made a phony course on my PC that highlighted a non-existent worker, and once MagicJack decided it couldn't interface with Atlanta, true to form, I was steered to Memphis. I leaped out of energy after understanding that the quality was currently PERFECT. There were no more pops or breaks, and none of my call beneficiaries were grumbling of static. This tip to enhance MagicJack and fix some regular issues is the one I expected to discard my home telephone bill. Only an admonition, these next not many advances are truly specialized, so please make an effort to remain cautious, or request that a nerd companion help you out!

Discover your intermediary to fix basic MagicJack issues

To viably improve MagicJack and fix call quality issues, you have to initially distinguish the intermediary worker that you are utilizing. The means beneath layout how to distinguish the intermediary and vms workers that MagicJack is as of now utilizing to finish calls:

Stage 1) Download the application pmdump from http://www.ntsecurity.nu/tool compartment/pmdump/ - pmdump lets you dump the memory from a specific cycle; this is the means by which we will get the intermediary worker

Stage 2) Start MagicJack

Stage 3) Identify MagicJack's cycle ID (PID)

an) Open an order brief (start->run->cmd).

b) Execute pmdump - list

c) Find "magicjack.exe" in the yield. Note the number related with it (typically 3 to 4 digits).

Stage 4) Make in any event one call

Stage 5) Using the order brief and PID as portrayed above, execute: pmdump [pid] magicjack.txt

Stage 6) Open magicjack.txt utilizing a word processor and quest for the string: s=ENSResip

For instance, in the event that you associate with the Atlanta intermediary, you should see:

o= 390440284 IN IP4 216.234.78.8

s=ENSResip

c=IN IP4 216.234.78.20

Note the IP addresses for both the intermediary and the vms workers (216.234.78.8 for intermediary and 216.234.78.20 for vms).

So you've discovered your intermediary, presently the time has come to transform it

Windows has an incredible inherent capacity for setting up "courses" for workers. As I referenced before in the article, the following stunt to upgrade MagicJack and fix call quality issues is making MagicJack imagine that the Atlanta worker is down, so it will default to the following accessible worker. Utilizing the "course" order, you can set the Atlanta intermediary and vms workers to a non-existent IP address on your nearby organization (if your PC is 192.168.1.2, you could utilize anything in that run, so 192.168.1.39). To do this, run the accompanying order from the order brief:

course include [ip of proxy] veil 255.255.255.255 192.168.1.39 - p

course include [ip of vms] veil 255.255.255.255 192.168.1.39 - p

The order above will tell your PC that the MagicJack intermediary worker is really at 192.168.1.39, which is an awful location, so MagicJack will attempt the following accessible, and ideally less occupied, worker. The - p alternative advises your PC to keep the course relentless, or recall it after a reboot. In the event that you need to utilize a particular intermediary worker (for example you conclude that the Austin, Texas worker is the most perfect), you essentially rehash the cycle above, however block EVERY intermediary worker, aside from the one you need to utilize.

GizmoGuide.net gives considerably more tips, deceives, and changes for upgrading MagicJack and different devices. Additionally an incredible wellspring of innovation news, contraption audits, and item sees.

Search This Blog

Harvey and Caldwell

Fix Magic Jack Problems by Tweaking and Changing Your Proxy Settings

Comments

Post a Comment

Popular posts from this blog

7 Wonders Board Game Review

A Young Teacher's Guide To Educational Games

Tips For eBay Sellers - Getting That First Bid