I have a home system COMPLETELY dedicated to MJ (small laptop running nothing but MJ software, ethernet connected to Linksys router with no other PC's competing for bandwidth). The MJ is on port 1 of the router which is set to High priority in the router's QOS config.
Not always but very often in the evenings the inbound voice quality is total CRAP. Its garbled almost beyond recognition. The person at the other end says they hear me fine with no garbling. It appears the problem is only with the inbound data flow. It doesnt matter whether the call was originated by me or the other end, the inbound voice is garbled. Sometimes the call starts off clear and then becomes more and more garbled. Im in the Raleigh NC area and perhaps it is over subscribed. Im about ready to give up on this "TOY". I can't believe folks with businesses would actually risk their customer communications on this flaky service.
I have not yet bitten the hard to swallow bullet of trying to load tomato (or some such sophisticated QOS) on my router. Im trying to figure out if the issue is the regional server I'm attached to or my router firmware. Its hard to imagine its a router issue since the problem is only with inbound voice and the router is doing nothing but routing the MJ data. Any ideas? Should I try to change the regional server? or try something else?
Inbound Voice is garbled...
Moderators: Bill Smith, Pilot
forgot to mention that I have a cable modem internet connection. My cable data service is the cheaper "DSL-lite" which supposedly mimics the same throughput as a DSL line. I would think this should not be an issue since at the time of the calling issues, there is no other applications running on my home system that would be receiving data over the internet.
Re: Inbound Voice is garbled...
I would try changing the proxy server as described on the wiki FAQ.gtburgin wrote:Should I try to change the regional server? or try something else?
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).
Also, the wiki FAQ on finding/changing the proxy needs some changes because it appears MJ is changing their system.
You need to make sure the vms server changes when you block the proxy. The "find" how-to shows how to find both the proxy and vms IP address. When you block the proxy, you'd repeat the find process and make sure both change. (Some people have reported that even though the blocked the proxy address, and went to a different region's proxy, the original region's vms server was still being used. There are reasons not to block the vms server if you don't have to.).
A lot of MJ servers can't be nslookup'ed. You should be able to match up the proxy IP address to the list shown in the "find" how-to. But, you may not be able to lookup the IP address of the vms server. So, even though you see it change, you may not know for sure if it really changed to a different region. But, if the IP address changes considerably, it should be safe to assume it changed. (I.e., if it only changes from x.x.x.72 to x.x.x.73, then it's probably in the original region that you blocked the proxy for).
Mark
You need to make sure the vms server changes when you block the proxy. The "find" how-to shows how to find both the proxy and vms IP address. When you block the proxy, you'd repeat the find process and make sure both change. (Some people have reported that even though the blocked the proxy address, and went to a different region's proxy, the original region's vms server was still being used. There are reasons not to block the vms server if you don't have to.).
A lot of MJ servers can't be nslookup'ed. You should be able to match up the proxy IP address to the list shown in the "find" how-to. But, you may not be able to lookup the IP address of the vms server. So, even though you see it change, you may not know for sure if it really changed to a different region. But, if the IP address changes considerably, it should be safe to assume it changed. (I.e., if it only changes from x.x.x.72 to x.x.x.73, then it's probably in the original region that you blocked the proxy for).
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).
BTW: You may have to go through a few proxies to find a region with better voice quality. See my tests tonight: http://www.phoneservicesupport.com/post31091.html#31091
Mark
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).
If so many proxies are having a chop problem I dont see how the company can avoid massive cancellations especially by those within the initial grace period. Most folks buying a MJ would be unwilling or unable to jump through all the technical hoops to change proxy servers. They'll just contact tech support, get totally frustrated with the chat "script robots" and then cancel. I am COMPLETELY dissatisfied with this crappy product. I thank god I only bought one year of service. Its like the company is operating a telecom ponzi scheme where money from early adopters is funding massive advertising (instead of scaling up the network) to take in as many suckers as possible with no regard for the long term reputation of the product or company.
I agree. You have to work at it. But, if a person is willing to work at it, they can save some pretty good money (for as long as it lasts).gtburgin wrote:Most folks buying a MJ would be unwilling or unable to jump through all the technical hoops to change proxy servers.
You can find some good proxies. Minneapolis has been a consistently good one (for the past week or two I've tested).
Things may improve. It seems MJ is changing things right now. For example, Seattle was really bad a few days ago. It was very good tonight.
Mark
See the MagicJack Wiki (FAQ, How-To, history and more).