MagicJack/Support Resources/How-To/Proxy Find2

Following is background information on the servers the MagicJack softphone connects to, how to identify the specific regional server you are connected to, and how to identify all available regional servers.

After obtaining this information, you can use it to change your proxy to a different region.

Background
MagicJack connects to a few servers which fall into two basic categories:

SIP and RTP servers
These are the main servers used by Magicjack.


 * SIP protocol connections go to a "proxy" server.
 * This connection occurs when you start MagicJack. It carries control information. For example, when a call occurs, the SIP connection carries the information instructing the softphone to open a RTP (vms) connection.
 * The UDP ports this connection uses are commonly referred to as 5060 and/or 5070. But, MagicJack only seems to open a connection to 5070.
 * RTP protocol connections go to a "vms" server.
 * This connection occurs when you place or receive a call. It carries the voice traffic.
 * This connection is always to a UDP port in the range of 10000 to 30000 on the RTP/vms server.

These servers exist across the US. Their locations seem to correlate to YMAX POP locations. MagicJack area codes seem to be associated with particular regional servers. But, MagicJack will connect to a different region's if it is unable to connect to the regional server it is normally associated with.

It seems that the RTP/vms server used by MagicJack is always in the same region as the SIP/proxy server. Therefore, if you know your SIP/proxy server you can safely assume your RTP/vms server. (Ex. If your SIP server is proxy1.phoenix.talk4free.com, then your RTP server should be vms1.phoenix.talk4free.com.).

Administrative servers
MagicJack connects to the following servers for administrative purposes:


 * prov1.talk4free.com - Provisioning (TCP ports 80 & 443)
 * 911.talk4free.com - Enhanced 911 (TCP port 80)
 * upgrade.talk4free.com - Upgrades (TCP port 80)
 * render.talk4free.com - Advertisements (TCP port 80)
 * mls.softjoys.com - Decryption of stored parameters? (TCP port 5002)

The above hostnames may resolve to the same IP address, and/or multiple IP addresses. Use nslookup to check this.

Identify your proxy
You can identify which proxy you are connected to using the following method:

Windows

Preparation

 * 1) Download pmdump from http://www.ntsecurity.nu/toolbox/pmdump/.
 * 2) Start MagicJack
 * 3) Identify MagicJack's process ID (PID).
 * 4) * Open a DOS (command) window.
 * 5) * Execute pmdump -list
 * 6) * Find "magicjack.exe" in the output. Note the number associated with it.
 * 7) Make at least one call. (Ex. to the special echo-test number: 909-390-0003.).

Final steps
pmdump {pid} mj_dump.txt s=ENSResip
 * 1) Using the DOS (command) window and PID as described above, execute:
 * 1) Open mj_dump.txt using a text editor like textpad.
 * 2) Search for the string:

That string occurs at the start of a line. And it occurs within repeating blocks of data, like a repeating pattern. In these blocks you will find lines starting with o= and c=. These lines contain the IP address of the SIP/proxy and RTP/vms servers respectively.

For example, if you connect to the Phoenix proxy, you should see:

o=- {nnnnnnnnnn} {nnnnnnnnnn} IN IP4 66.104.81.70 s=ENSResip c=IN IP4 66.104.81.75

You can use nslookup to resolve both IP addresses to hostnames, revealing the regional SIP/proxy and RTP/vms servers you are presently using.

Keep in mind that the server you connect to may change from time to time. Ex. If MagicJack is unable to connect to a regional server, it will try a different region. This feature is what allows you to force MagicJack to connect to a different regional server.

Preparation

 * 1) Download and install WireShark from http://www.wireshark.org/
 * 2) Run WireShark to watch all the packets in and out of your computer on the interface you use to connect to your router.
 * 3) Start magicJack if its not running.  Or if it is running, just make a call.
 * 4) Watch WireShark -you should see SIP connections being made.  The IP address of the SIP connections should match one of the proxies listed below.
 * 5) Alternatively, use nslookup in a DOS (command prompt) box to lookup the name of the machine whose IP address you've identified.

Identify all available proxies
Using the same steps described above in Identify your proxy, search the memory dump for: transport=udp. This will reveal a list of IP addresses of regional SIP/proxy servers. These addresses can be converted to hostnames using nslookup. The resulting hostnames should correspond to the list of YMAX POP locations.

Note: As of Jan. 28, many of these IP addresses cannot be resolved by nslookup. Please use the list below to cross reference an IP address to a proxy server.

Using that list of proxy IP addresses, you can force MagicJack to connect to a specific regional server.

The following list of regional proxy servers is provided for comparison only. This information changes over time. For example, over the past six months (since the creation of this how-to), the IP addresses of the Atlanta, Los Angeles, Miami and New York proxy servers changed. The following list may be updated from time to time. However, you should always obtain the current list of proxy IP addresses using the procedure described earlier in this section.

216.234.78.8   proxy1.atlanta.talk4free.com 67.107.82.70   proxy1.austin.talk4free.com 67.111.250.134 proxy1.baltimore.talk4free.com 67.91.233.134  proxy1.boston.talk4free.com 216.234.66.8   proxy01.boston.talk4free.com 216.234.69.8   proxy1.chicago.talk4free.com 67.88.10.198   proxy1.cleveland.talk4free.com 66.104.96.198  proxy1.columbus.talk4free.com 67.107.71.134  proxy1.dallas.talk4free.com 67.107.71.134  proxy01.dallas1.talk4free.com (checked 10/28/2010) 207.155.164.198 proxy1.denver.talk4free.com 67.91.177.70   proxy1.detroit.talk4free.com 67.88.84.6     proxy1.houston.talk4free.com 216.234.74.8   proxy01.houston.talk4free.com (added 3/5/2011) 67.90.80.134   proxy1.lasvegas.talk4free.com 216.234.70.8   proxy1.losangeles.talk4free.com 67.91.96.134   proxy1.memphis.talk4free.com 216.234.79.8   proxy1.miami.talk4free.com 67.88.183.70   proxy1.minneapolis.talk4free.com 67.90.152.70   proxy1.nashville.talk4free.com 216.234.77.8   proxy01.nashville.talk4free.com 67.106.133.198 proxy1.newark.talk4free.com 216.234.65.8   proxy01.newark.talk4free.com 216.234.64.8   proxy1.newyork.talk4free.com 216.234.64.128 iproxy01.newyork.talk4free.com (added 9/16/2011) 216.234.67.8   proxy1.philadelphia.talk4free.com 66.104.81.70   proxy1.phoenix.talk4free.com 66.104.81.77   vms03.phoenix.talk4free.com 67.88.11.6     proxy1.pittsburgh.talk4free.com 67.88.208.198  proxy1.portland.talk4free.com 67.109.32.70   proxy1.sacramento.talk4free.com 67.108.236.70  proxy1.saltlakecity.talk4free.com 67.111.81.6    proxy1.sandiego.talk4free.com 64.1.213.70    proxy1.sanfrancisco.talk4free.com 67.88.218.6    proxy1.seattle.talk4free.com 67.110.56.198  proxy1.stlouis.talk4free.com 67.90.16.6     proxy1.tampa.talk4free.com 67.90.177.70   proxy1.washington.talk4free.com 216.234.68.8   proxy01.washington.talk4free.com
 * 1) Jan 24, 2009 - Verified.
 * 2) Jan 28, 2009 - Verified. Baltimore absent. Leaving it in the list for now.
 * 3) Feb 17, 2009 - Verified. Baltimore still absent. Chicago changed from 71.5.91.70. Philadelphia changed from 71.5.113.6.
 * 4) Feb 23, 2009 - Baltimore proxy1 (67.111.250.134) and vms1 (67.111.250.139) both alive and answering pings
 * 5) Mar 5, 2009 - Verified. Baltimore still absent.

67.91.177.79-?