<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0"
 xmlns:blogChannel="http://backend.userland.com/blogChannelModule"
>

<channel>
<title>Topic &#x27;Call quality GV vs voip.ms on Android.&#x27; in forum &#x27;VOIP Tech Chat&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Call-quality-GV-vs-voipms-on-Android-28149162</link>
<description></description>
<language>en</language>
<pubDate>Sat, 26 Mar 2022 13:53:08 EDT</pubDate>
<lastBuildDate>Sat, 26 Mar 2022 13:53:08 EDT</lastBuildDate>

<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28156786</link>
<description><![CDATA[JeanInNepean posted : <div class="bquote"><said>said by <a href="/profile/986668" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=986668');">conwaytwt</a>:</said><p>1) capitalization counts, so the ping command should be <code>ping -i 0.02 -s 192 -c 500 server.voip.ms</code> (lowercase "i") </p></div>Oops... Indeed. That was my tablet trying to correct me... <br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28156786</guid>
<pubDate>Sun, 31 Mar 2013 22:51:14 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28155297</link>
<description><![CDATA[conwaytwt posted : <div class="bquote"><said>said by <a href="/profile/1843659" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1843659');">JeanInNepean</a>:</said><p>You should ping the voip.ms servers you are using and report your numbers... on Linux, I use ping -I 0.02 -s 192 -c 500 server.voip.ms. this is the same throughput as a G.711u call.<br> </p></div>I've been following the discussion and thought I would note two things -- <br><br>1) capitalization counts, so the ping command should be <code>ping -i 0.02 -s 192 -c 500 server.voip.ms</code> (lowercase "i") [well, it is in Ubuntu. It might be different in other distros.]<br><br>2) I have had some weird one-way packet loss between my ISP and voip.ms servers in Texas that ONLY seems to affect UDP, so you would never see the problem occur with a ping. Switching <code>traceroute</code> between UDP (default on linux) and TCP makes the strangeness show up, and seems to indicate the problem is in an intermediate server at one of the hops. Nobody at voip.ms has been able to see the problem, and I haven't brought it to the attention of my ISP. I just work around it by avoiding the houston and dallas servers.<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28155297</guid>
<pubDate>Sun, 31 Mar 2013 09:53:04 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28155249</link>
<description><![CDATA[JeanInNepean posted : The tunnel sound is usually caused by echo at both ends of the communication when the latency is very short. Try toggling your echo cancellation to see if it helps. Software echo cancellation can cause more echo than it eliminates in some cases...<br><br>But when you say words are skipped, this is probably because you have high packet losses. Not sure why you would only have this problem with voip.ms though (is Google Voice using a redundant protocol?) You should ping the voip.ms servers you are using and report your numbers... on Linux, I use ping -I 0.02 -s 192 -c 500 server.voip.ms. this is the same throughput as a G.711u call.<br><br>I'm with voip.ms running CSipSimple on Android. Audio quality has been excellent so far. I've turned off echo cancellation and, since I'm on DSL, my packet loss is pretty much 0% all the time...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28155249</guid>
<pubDate>Sun, 31 Mar 2013 09:06:18 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28155082</link>
<description><![CDATA[SCADAGeo posted : Have you considered performing a site survey?<br><br><a href="http://play.google.com/store/apps/details?id=com.farproc.wifi.analyzer&hl=en">Google play: Wifi Analyzer by farproc</a> is a nice tool (free, no adware).<br><br>Another nice tool is <a href="https://play.google.com/store/apps/details?id=girsas.wifiradar">Google play: WiFi Radar by  Paul Girsas</a> (free, adware).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28155082</guid>
<pubDate>Sun, 31 Mar 2013 03:15:12 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154700</link>
<description><![CDATA[dks7 posted : ts wifi for sure as I have no cellular plan on the phone. And its not an overload issue as I have tried it after a fresh boot with very little stuff running.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154700</guid>
<pubDate>Sat, 30 Mar 2013 22:38:25 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154684</link>
<description><![CDATA[JoeSchmoe007 posted : <div class="bquote"><said>said by <a href="/profile/1016283" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1016283');">dks7</a>:</said><p>So for a month or so I have been a voip.ms subscriber, and have been less than pleased with call quality. I am using the premium routing, but the call quality is the same using either. Very lackluster. <br><br>People sometimes have a hard time hearing me, sometimes words are skipped, I've been told it often sounds like I am talking in a tunnel or something.<br><br>I have tried sipdroid, csipsimple, 3cx, bria and the likes. All have been identical. I am now using GrooVe IP using google voice and a free number, and the sound quality using the same phone and same wifi at home is outstandingly clear on both ends.<br><br>I do not know what to make of this, I am sorely dissapointed in voip.ms, or VOIP in general, except GV. I am not sure if its the protocol, codec, provider, or what but something is sorely amiss. I have 30/4mbit bandwidth and excellent pings and low jitter to losangeles and seattle pops. Both provide the exact same quality, I am hoping maybe one of you fine fellas can shed some light on this situation and help me to get the call quality to an acceptable level, as it is now its almost unusable.<br><br>I am using an HTC Droid Incredible, the original from verizon.<br> </p></div>I have the same phone as you and Callcentric and Anveo have very good sound quality (I use 3CXPhone). My internet connection is 15/2.<br><br>Could this be something with your phone (CPU overloaded or memory starvation) and/or WiFi?<br><br>Just to double-check: you are sure you are connecting via WiFi? Because over 3G results are never going to be good.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154684</guid>
<pubDate>Sat, 30 Mar 2013 22:32:13 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154578</link>
<description><![CDATA[cb14 posted : GV has been charging for calls to other countries than US/CAN  from the very beginning. I just found neither their rates nor the call quality convincing.<br>People from other countries can easily sign up for free GV accounts either when they visit US or using their friends/relatives in the US. Also, getting Obi is not a problem in most countries, you just may pay significantly more for it.<br>I found the call quality AND service reliability surprising and certainly not worse than from SIP providers.<br>Their choice of numbers/exchanges got worse but when i signed up, it was better than from just about any SIP provider.<br>It is a piece of cake even for a complete layman to configure Obi for GV- if you can write and send an e-mail you can do that. Not so with some SIP providers. It can be very frustrating and turned off a lot of people.<br>GV on Obi seems to be far less susceptible for NAT issues( which can be extremely frustrating with some VOIP hostile routers/gateways)) than SIP  providers, another very important point for an average plug and play user.<br>On the down side, I experienced the GV call treatments and all other whistles and bells to be to unreliable for my purposes and simply use the service for plain calls in and out( especially out).<br>As mentioned, there is NO customer service whatsoever.<br>And off course, the issue of a corporate mogul killing the business of small and innovative VOIP providers. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154578</guid>
<pubDate>Sat, 30 Mar 2013 21:31:48 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154429</link>
<description><![CDATA[PX Eliezer1 posted : <div class="bquote"><said>said by <a href="/profile/780972" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=780972');">WhyADuck</a>:</said><p>....Google Voice is a pretty popular service, unlike Google Reader.  I'd be surprised if Google discontinues it.  They may try to charge for it someday, but they have to be VERY careful....<br> </p></div>Your post and analysis is excellent.  I would just observe that GV already does charge (for calls outside US/Canada for example).<br><br><div class="bquote"><said>said by <a href="/profile/780972" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=780972');">WhyADuck</a>:</said><p>But that said, one wonders what's happening to commercial VoIP companies.  There's someone in my family that's had phone service with a particular VoIP provider for years, and never had a bit of trouble with them, until this last year.  Suddenly he's seeing a high rate of non-completed calls, both incoming and outgoing. <br></p></div>Here I must disagree with you.<br><br>Your relative has trouble with ONE company (you said a "particular" provider) and you are impugning the whole field (you said "commercial VoIP companies"---plural).   :hmm:<br><br>This is the very reason that I dislike underachieving providers---they give everyone else a bad name.<br><br>Perhaps your relative should try a different provider.  As you know, this can be done without yet having to port their current number.   :)<br><br>I have no problem with making or receiving calls with CallCentric, used at 2 locations with different equipment.<br><br>I also have had no problems recently making calls on CallWithUs (2 locations), or Vitelity (one location).   <br><br><i>If folks are not getting satisfaction, <br>it is up to them to take some action.</i><br><small>--<br>CallCentric business and home, CallWithUs, Gizmo5, Swiftvox, Windows PX, PaleMoon browser, Gigaset A580IP, Panasonic KX-TGP551, Linksys, Grandstream, Ixquick search, Detroit, Norfolk, Metropolis NY, Gotham City NJ.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28154429</guid>
<pubDate>Sat, 30 Mar 2013 20:14:32 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152881</link>
<description><![CDATA[WhyADuck posted : You're asking a question that to a few people is akin to asking whether one religion is better than another.  They have already made a choice and they are going to cite any reason they can to defend it.  And then there are the Google haters, who will try anything they can to dissuade you from using anything Google.  They may in fact have some valid points, but you can find reasons to hate almost every large corporation without trying too hard.<br><br>Google Voice is a pretty popular service, unlike Google Reader.  I'd be surprised if Google discontinues it.  They may try to charge for it someday, but they have to be VERY careful because they could easily cross the line into fitting the definition of a "telephone company" and that would bring a number of issues that they've not had to deal with (such as the need to offer 911 service, and the need to have an actual, responsive customer service department).<br><br>But that said, one wonders what's happening to commercial VoIP companies.  There's someone in my family that's had phone service with a particular VoIP provider for years, and never had a bit of trouble with them, until this last year.  Suddenly he's seeing a high rate of non-completed calls, both incoming and outgoing.  On some days if he tries to use that service he has to dial three or four times before the call will actually go through, assuming it will go through at all.  By the way, we verified it's not the VoIP device the company provided, because on the days when the problem is at its worst, even when he turns on call forwarding incoming calls don't go through.<br><br>Only reason he hasn't dropped the service yet is because he doesn't want to lose the number he's had for years.  Google Voice considers it a landline number and won't port it (in fact they won't even port mobile numbers in his area) and he really doesn't want to jump to another commercial VoIP provider and maybe wind up in a similar situation, but if there was a way he could port that number to some service that would translate it to SIP for a reasonable one time fixed porting charge I'm sure he'd do it.  I don't know what Google's aversion is to porting landlines is but we wish they'd get over it, particularly since they seem to have completely run out of numbers in many phone exchanges and even some entire area codes.<br><br>He and I both have Obihai devices now and we have found Google Voice to be pretty reliable for incoming and outgoing (in his case, much more than the commercial provider), with the caveat that they (Google Voice) don't do 911, don't have anything resembling a functional customer service department, and won't pass "early media" (voice information before actually "answering" the call, such as telephone company number change announcements).  I'm not saying that's what you should do but they have worked out pretty well for us, and unlike Google Voice, Obihai actually does have good customer service.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152881</guid>
<pubDate>Sat, 30 Mar 2013 02:10:22 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152720</link>
<description><![CDATA[OZO posted : <div class="bquote"><said>said by <a href="/profile/1016283" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1016283');">dks7</a>:</said><p>csimple worked ok except when a call came in i cannot answer it, the green icon moves and aknowledges im touching it, but still refuses to answer the call using android 2.3.4. So I refuse to use it.<br> </p></div>Running CSipSimple on Android 2.2 I can see, that when phone is in deep sleep mode CSS can miss incoming calls. Later on it may start to ring, but the time for accepting the call is already gone... :( I've tired it with Android 4.1.2 and it looks like it can finally handle it. Too bad that I can not run Android 4.1.2 for many other reasons and have to return back to 2.2, where CSipSimple is not a reliable phone at all...<br><small>--<br>Keep it simple, it'll become complex by itself...</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152720</guid>
<pubDate>Sat, 30 Mar 2013 00:09:15 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152439</link>
<description><![CDATA[XCOM posted : <div class="bquote"><said>said by <a href="/profile/1841613" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1841613');">VexorgTR</a>:</said><p>Google voice creeps me out.........<br><br><p><div style='z-index:0; text-align:center;display:block;' class='youtube_div'><iframe width='560' height='315' src="https://www.youtube.com/embed/hrontojPWEE?autoplay=0&origin=www.dslreports.com" frameborder="0" allowfullscreen></iframe></div></p><center>&raquo;<a href="http://youtu.be/hrontojPWEE" >youtu.be/hrontojPWEE</a></center><br> </p></div>And <b>you</b> creep out google.<br><small>--<br>[nUll@dcypher ~]$</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152439</guid>
<pubDate>Fri, 29 Mar 2013 22:14:30 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152365</link>
<description><![CDATA[dks7 posted : csimple worked ok except when a call came in i cannot answer it, the green icon moves and aknowledges im touching it, but still refuses to answer the call using android 2.3.4. So I refuse to use it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152365</guid>
<pubDate>Fri, 29 Mar 2013 21:45:48 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152184</link>
<description><![CDATA[brawney posted : I have only begun to tinker with voip.ms and csipsimple on my Motorola Photon.  It seems to work ok.  I used the voip.ms "built-in" configuration in csipsimple. voip.ms is in the app's "world wide provider" list.<br><br>I have it configured to use PCMU codec and I have only tested using wifi (not 3g or 4g). csipsimple has a lot of settings you can tinker with and you might want to check on their google group for help.<br><br>I have not used this setup a lot, so I could run into troubles too.  I just wanted to give you the info I know about csipsimple.  Good luck.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152184</guid>
<pubDate>Fri, 29 Mar 2013 20:38:22 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152147</link>
<description><![CDATA[VexorgTR posted : Google voice creeps me out.........<br><br><p><div style='z-index:0; text-align:center;display:block;' class='youtube_div'><iframe width='560' height='315' src="https://www.youtube.com/embed/hrontojPWEE?autoplay=0&origin=www.dslreports.com" frameborder="0" allowfullscreen></iframe></div></p><center>&raquo;<a href="http://youtu.be/hrontojPWEE" >youtu.be/hrontojPWEE</a></center>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28152147</guid>
<pubDate>Fri, 29 Mar 2013 20:25:22 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28151295</link>
<description><![CDATA[PX Eliezer1 posted : <div class="bquote"><said>said by <a href="/profile/755055" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=755055');">OZO</a>:</said><p>I've heard (but it could be wrong), that Groove IP uses speex codec, which is more appropriate to use over WiFi connections. That may explain the difference in call quality...<br> </p></div>QFT and a good point.<br><br><div class="bquote"><said>said by <a href="/profile/755055" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=755055');">OZO</a>:</said><p>VoIP.ms offers very limited set of codecs. <br> </p></div>Pretty similar to their peers, they offer G.711u, G.729, and GSM.  That should cover the basics for most VoIP users other than for WiFi.  <br><br>Few if any of the typical VoIP providers offer the Speex codec....]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28151295</guid>
<pubDate>Fri, 29 Mar 2013 14:59:39 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28151238</link>
<description><![CDATA[OZO posted : <div class="bquote"><said>said by <a href="/profile/1016283" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1016283');">dks7</a>:</said><p>So for a month or so I have been a voip.ms subscriber, and have been less than pleased with call quality. I am using the premium routing, but the call quality is the same using either. Very lackluster.<br> </p></div>Call quality, using both volume and premium routing, is the same. You pay premium for the <i>routing</i>, not for the call quality. <br><br>Call quality depends on the codecs used. VoIP.ms offers very limited set of codecs. I've heard (but it could be wrong), that Groove IP uses speex codec, which is more appropriate to use over WiFi connections. That may explain the difference in call quality...<br><small>--<br>Keep it simple, it'll become complex by itself...</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28151238</guid>
<pubDate>Fri, 29 Mar 2013 14:40:33 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150697</link>
<description><![CDATA[PX Eliezer1 posted : <div class="bquote"><said>said by <a href="/profile/1659473" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1659473');">DaveSin</a>:</said><p>Like Mazilo, I'm curious why folks are paying for residential VOIP services, when it can be had for free. <br> </p></div>Well, Toro laid out several good reasons.<br><br>A few more I can think of---<br><br>a)  What Google doth give, it can take away.  [Recent example:  Google Reader].<br>&raquo;<A HREF="http://bits.blogs.nytimes.com/2013/03/14/the-end-of-google-reader-sends-internet-into-an-uproar/" >bits.blogs.nytimes.com/2 &middot;&middot;&middot; -uproar/</A><br><br>b)  I'd prefer to pay my own way, rather than depend on the fickleness of a corporate boardroom.<br><br>c)  TANSTAAFL (popularized by Robert A. Heinlein and Milton Friedman).<br><br>d)  GV does not provide 911.<br><br>e)  GV is an indirect service unless one also uses the services of Obi or Simonics, which are not officially acknowledged or endorsed by Google and which Google could choose to block at any time for reasons of their own.<br><br>f)  GV has not even a pretense of customer service.<br><br>g) GV has done no further innovation at all.  <br><br>h)  The companies that DO innovate, such as Anveo, CallCentric, Voip.MS, and others, should be supported.<br><br>i)  Those companies offer lots of services that GV does not.<br><br>j)  Last but not least:<br>&raquo;<A HREF="/forum/r28148824-Internet-and-or-GoogleVoice-Security-Issue">Internet and/or GoogleVoice Security Issue</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150697</guid>
<pubDate>Fri, 29 Mar 2013 11:55:58 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150624</link>
<description><![CDATA[DaveSin posted : As far as reliability goes, Google Voice has been more reliable than most paid VOIP providers mentioned on this Forum.  Since I have used GV on an OBI110, I can't remember once not be able to place or receive calls via GV.  I know there was one issue with VM notification.  I have also use GV with Asterisk and there were one or two points in time where a patch was required.<br><br>Like Mazilo, I'm curious why folks are paying for residential VOIP services, when it can be had for free.  I still use VOIP.ms for business lines, but have multiple GV accounts on my IP Phone and OBi110!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150624</guid>
<pubDate>Fri, 29 Mar 2013 11:21:35 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150532</link>
<description><![CDATA[mazilo posted : I could understand your points. If one wants something to work reliably, then go with some VoSP that doesn't support BYOD. of course, that will be more expensive. But then, <b>WHY PAY FOR SOMETHING THAT CAN BE HAD FOR FREE</b>.<br><small>--<br><b>don't</b> and <b>stop</b> are the ONLY two 4-letter words considered offensive to men, but not when used together.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150532</guid>
<pubDate>Fri, 29 Mar 2013 10:49:10 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150427</link>
<description><![CDATA[toro posted : I can think of a few reasons:<br>- not everybody trusts Google to handle their calls<br>- not everybody lives in US, and can get a number local to them through GV<br>- not everybody has access easily to to buy an OBi ATA<br>- not everybody has the skills or wants to build an Asterisk or Freeswitch PBX and keep patching it every time Google changes something in their protocol<br>- some people don't care if they have to pay a few cents for a call, especially if it's low volume<br>That's just my opinion though.<br><br>Edit: a couple more :)<br>- for some people the phone is extremely important and needs to be reliable. When they pick up the phone there needs to be a dial tone and the call should get connected. They don't want to learn something has just changed and they need to patch their PBX or upgrade their OBi firmware to fix it. Or maybe they don't mind this but their non-technical wifes don't want to put up with that :)<br>- some people (like me) make few or no calls to US/Canada destinations and much more to overseas destinations that may be more expensive with GV than with other providers<br><br><small>--<br>Providers (through asterisk): voip.ms, freephoneline, smartcall.ro, ipcomms, callcentric. Hardware: Vonage VDV21, Moto VT2x42, Linksys SPA series, Grandstream HT series, Panasonic KX-TGP5x0<br>&raquo;<A HREF="http://www.voipfan.net" >www.voipfan.net</A></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150427</guid>
<pubDate>Fri, 29 Mar 2013 10:17:13 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150382</link>
<description><![CDATA[mazilo posted : I just never understand why anyone wants pay for something of a less quality service while a better quality service can be had for free. For me (YMMV), I have been using GV (formerly GrandCentral) since day one and never pay for all the calls. AFAICT, the quality of a GV call is far better than the quality of a pure traditional PSTN (analog to analog) phone call, particularly on a call across continents. I have friends who use FreeSWITCH + an ATA and OBi-1x0 devices with GV service live in Asia and Australia. The calls I made to their GV lines are very good with an exception of some admissible delays.<br><small>--<br><b>don't</b> and <b>stop</b> are the ONLY two 4-letter words considered offensive to men, but not when used together.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28150382</guid>
<pubDate>Fri, 29 Mar 2013 09:59:49 EDT</pubDate>
</item>
<item>
<title>Re: Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28149927</link>
<description><![CDATA[dks7 posted : Dang 55 views, and no thoughts? :( lol]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Call-quality-GV-vs-voipms-on-Android-28149927</guid>
<pubDate>Fri, 29 Mar 2013 04:05:03 EDT</pubDate>
</item>
<item>
<title>Call quality GV vs voip.ms on Android.</title>
<link>http://www.dslreports.com/forum/Call-quality-GV-vs-voipms-on-Android-28149162</link>
<description><![CDATA[dks7 posted : So for a month or so I have been a voip.ms subscriber, and have been less than pleased with call quality. I am using the premium routing, but the call quality is the same using either. Very lackluster. <br><br>People sometimes have a hard time hearing me, sometimes words are skipped, I've been told it often sounds like I am talking in a tunnel or something.<br><br>I have tried sipdroid, csipsimple, 3cx, bria and the likes. All have been identical. I am now using GrooVe IP using google voice and a free number, and the sound quality using the same phone and same wifi at home is outstandingly clear on both ends.<br><br>I do not know what to make of this, I am sorely dissapointed in voip.ms, or VOIP in general, except GV. I am not sure if its the protocol, codec, provider, or what but something is sorely amiss. I have 30/4mbit bandwidth and excellent pings and low jitter to losangeles and seattle pops. Both provide the exact same quality, I am hoping maybe one of you fine fellas can shed some light on this situation and help me to get the call quality to an acceptable level, as it is now its almost unusable.<br><br>I am using an HTC Droid Incredible, the original from verizon.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Call-quality-GV-vs-voipms-on-Android-28149162</guid>
<pubDate>Thu, 28 Mar 2013 20:32:59 EDT</pubDate>
</item>
</channel>
</rss>
