Jump to content

Google Voice


Recommended Posts

When the new hangouts app came out with SCE support, I decided to try and disable Google voice and let me say, the call quality is night and day better without Google voice. For others that have horrible call quality, maybe it's Google to blame vice sprint. My hate of Google grows with every new thing they touch (Reference Google maps)

 

Sent from my SPH-L710 using Tapatalk

 

 

Link to comment
Share on other sites

When the new hangouts app came out with SCE support, I decided to try and disable Google voice and let me say, the call quality is night and day better without Google voice. For others that have horrible call quality, maybe it's Google to blame vice sprint. My hate of Google grows with every new thing they touch (Reference Google maps)

 

Sent from my SPH-L710 using Tapatalk

Stupid autocorrect. I meant to say SMS support. And the reason Google Voice is important is because the new hangouts app SMS support doesn't support Google voice numbers until next year. The important point though is that Google voice kills voice quality

 

Sent from my SPH-L710 using Tapatalk

 

 

Link to comment
Share on other sites

Uh, despite its name, what does Google Voice have to do with voice quality?

 

AJ

  • Like 2
Link to comment
Share on other sites

Stupid autocorrect. I meant to say SMS support. And the reason Google Voice is important is because the new hangouts app SMS support doesn't support Google voice numbers until next year. The important point though is that Google voice kills voice quality

 

Sent from my SPH-L710 using Tapatalk

I have to agree with AJ.... Google Voice has nothing to do with your actual Voice calls... it's not a VoIP service, all it does is handle SMS (if you choose to allow it to do so) and voicemail.

Link to comment
Share on other sites

I have to agree with AJ.... Google Voice has nothing to do with your actual Voice calls... it's not a VoIP service, all it does is handle SMS (if you choose to allow it to do so) and voicemail.

And international calls. With google voice intergration international calls are routed through Gv or at least the charges.

Link to comment
Share on other sites

No, Google Voice does do some VoIP stuff. You can set up GrooveIP, or answer calls via GMail. With gvoice call forwarding or integration, all voice calls go through them at some point.

 

That being said, I've personally found my voice calls sound better using GrooveIP for VoIP calling.

Link to comment
Share on other sites

No, Google Voice does do some VoIP stuff. You can set up GrooveIP, or answer calls via GMail. With gvoice call forwarding or integration, all voice calls go through them at some point.

 

The VoIP capability is not Google Voice, per se.  Rather, it is Google Chat.  To use GrooVeIP, for example, you have to tick the box in your Voice settings to forward to Chat.

 

Honestly, the divisions among Google Voice, Chat, Talk, and Hangouts are quite confusing.  I think everything will be centralized soon within Hangouts -- maybe under yet a different name, though, as Hangouts sounds too slangy.  I am sure that Google would like to include a native VoIP client, but the wireless operators are basically implying, if not outright saying "Don't you dare do that."

 

AJ

  • Like 1
Link to comment
Share on other sites

Uh, despite its name, what does Google Voice have to do with voice quality?

 

AJ

 

If you have the Sprint/Google Voice integration, you can have your calls are at least partially routed through Google's servers (including calls made over the native sprint network and the native phone interface)  

 

You have the ability to initiate call recording, and it some cases, transfer calls from one phone to another or to gmail.  As well as have incoming calls simultaneously ring multiple locations.

 

Google will also intercept international calls and route them itself.

 

So it's certainly possible for GV to affect voice quality.

  • Like 1
Link to comment
Share on other sites

I have found that the Google Voice integration can sound ok and sometimes so bad I have to hang up and call again.

 

The same for incoming call, sometimes there is a beep every so many seconds, its weird, like someone pressed a key on their phone.

 

This is when the international integration is used from a Sprint phone in a sprint area, and also when in a roaming area.

 

To use the Google voice in a Sprint area, I just dial the +number directly.

 

To use Google voice in a  roaming area, I have to dial my own number and then the password and then the 011 number.

Can't use the Google voice +number dialing directly when roaming, have to be in a Sprint area.

 

A third party is involving in the voice routing, can't recall which it is.

Link to comment
Share on other sites

I have found that the Google Voice integration can sound ok and sometimes so bad I have to hang up and call again.

 

The same for incoming call, sometimes there is a beep every so many seconds, its weird, like someone pressed a key on their phone.

 

This is when the international integration is used from a Sprint phone in a sprint area, and also when in a roaming area.

 

To use the Google voice in a Sprint area, I just dial the +number directly.

 

To use Google voice in a  roaming area, I have to dial my own number and then the password and then the 011 number.

Can't use the Google voice +number dialing directly when roaming, have to be in a Sprint area.

 

A third party is involving in the voice routing, can't recall which it is.

 

Broadband.com iirc

Link to comment
Share on other sites

Bandwidth.com used to be the underlying carrier for GV but I believe the last time I checked it was Level 3, maybe it depends on the number. I can check numbers if anyone is interested using a basic telecom tool I have access to for work. (I work for the 4th largest carrier in the country). Level 3 is a major league carrier, but all this means is that they are terminating the call on the pstn or public switched telephone network, or even more basic converting it from voip to "standard" analog.

 

I am a GV (sprint integration) user and I have noticed call quality issues as well. I have also perceived a delay in getting ring-back, it seems like the calls take longer to set up. I believe that Sprint phones are actually dialing into some type of server, delivering a terminating number to that server and then waiting for the server to make a call to the final terminating number and then that server bridges the two together. 

 

Likely that server is owned by Google. Google is then converting calls to voip and then delivering them in packet form to Level 3 who does the rest. It is possible that this is not accurate, but I bet it is. 

Link to comment
Share on other sites

.....

I am a GV (sprint integration) user and I have noticed call quality issues as well. I have also perceived a delay in getting ring-back, it seems like the calls take longer to set up. I believe that Sprint phones are actually dialing into some type of server, delivering a terminating number to that server and then waiting for the server to make a call to the final terminating number and then that server bridges the two together. 

 

...

 

I've seen the same thing as I brought up in this thread:

 

http://s4gru.com/index.php?/topic/4927-connection-lag-when-making-phone-calls/

Taking a long time for ring-back, many times missing calls, missing and late texts.  I've turned off Google Voice integration and will try just forwarding my voicemail to GV instead.  The integration (for me, anyway) just doesn't work well enough to be trusted.

Link to comment
Share on other sites

I have transitioned from full integration to voicemail integration only for the same reasons. 

 

Also, I did run both of my google voice numbers through Neustar and both are with Bandwidth.com. I would have bet seeing Level 3 at some point but maybe I was wrong...

Link to comment
Share on other sites

I am sure that Google would like to include a native VoIP client, but the wireless operators are basically implying, if not outright saying "Don't you dare do that."

 

Which is weird, because it's data that most of the operators are trying to cap. Voice and SMS is a giveaway, a mirror image of the situation 5 years ago. You'd figure they'd want people using as much data as they could charge for, capacity allowing.

Link to comment
Share on other sites

I am sure that Google would like to include a native VoIP client, but the wireless operators are basically implying, if not outright saying "Don't you dare do that."

 

AJ

 

They're allowing VoIP calls over GV in the new iOS Hangouts app:

 

http://lifehacker.com/google-hangouts-for-ios-adds-free-voice-calling-1449196714

 

I don't know why they haven't implemented it yet in Android, but you can bet it's coming.

Link to comment
Share on other sites

They're allowing VoIP calls over GV in the new iOS Hangouts app:

 

http://lifehacker.com/google-hangouts-for-ios-adds-free-voice-calling-1449196714

 

I don't know why they haven't implemented it yet in Android, but you can bet it's coming.

 

Possibly waiting until the middle of the 2014, when all the third party apps (Groove IP etc) are kicked off.

Link to comment
Share on other sites

Uh, despite its name, what does Google Voice have to do with voice quality?

 

AJ

 

Pretty sure it is handled differently.  When I was playing around with running my own voip gateway, I noticed increased latency when using Google voice integration vs when not.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...