Jump to content

Google Voice integration & international calling


Bob Newhart

Recommended Posts

I have google voice integrated with my Sprint cell.

It works great, the google voicemail/sms is great using their app and online.

 

While roaming today in the building at work, I tried to dial an international number, I got the message "Verizon Wireless, international dialing is not enabled on your account".

 

When I'm not roaming, I can't connect to an international number either.

 

I contacted Sprint international support to see if I needed to enable international dialing. I was told this

 

" If I enable the service, then it is a guarantee that you are going to get charges from us since I have to remove google voice to add international services. Unfortunately you are not able to have both on your line."

 

 

Any ideas, anyone else use this google voice international dialing?

I use it from the google voice/chat site all the time.

Link to comment
Share on other sites

Glad your problem was solved but I still wanted to mention that you still might want to consider using localphone.com and that way you can have different local or domestic US long distance numbers for the different international numbers you dial. Works awesome and it's much cheaper than Sprint's rates. There's no charge for the local numbers and they also have a standard calling card service too. With somelocal exchanges they can even forward texts from your local numbers to their associated international contacts at a cost much lower than Sprint's.

Link to comment
Share on other sites

It just doesn't work when I'm roaming, can that be fixed?

 

Why should it work while you are roaming? Then, both you and Sprint are subject to not only roaming costs but also international dialing costs set by the roaming carrier. Complaints would ensue.

 

AJ

Link to comment
Share on other sites

Why should it work while you are roaming? Then, both you and Sprint are subject to not only roaming costs but also international dialing costs set by the roaming carrier. Complaints would ensue.

 

AJ

 

I don't understand what you mean here. Why should it not?

 

My cell/google is fully integrated, which means my cell number = google voice number.

 

When not roaming, I dial an international number (eg: +471233321273), it connects to Google's services, it uses my domestic Sprint cell minutes. It takes the minutes from allotted bucket of cell plan minutes, and then Google charges me for the international fee, 2 cents per minute.

 

When roaming on VZW, I get that that VZW message.

 

When roaming on VZW, I can dial my own cell number, enter my google voice PIN, press 2, and dial an international number.

 

If I don't have my cell fully integrated, only partly. I can configure the phone to dial all or international numbers via a google voice access number. It would be totally transparent to me dialing.

 

http://www.google.co...levoice/sprint/

I use option one.

 

--

GoWireless, I don't use Sprint's rates, I use Google's.

Link to comment
Share on other sites

I don't understand what you mean here. Why should it not?

 

My cell/google is fully integrated, which means my cell number = google voice number.

 

Sprint is the only domestic carrier that offers this level of Google Voice integration. Kudos to Sprint. But my guess is that, while roaming on VZW, Google Voice attempts to dial the international number directly. And that prompts the error message. If so, it might actually work better with separate cellphone and Google Voice numbers.

 

AJ

Link to comment
Share on other sites

Is your google voice app set to dial international calls

I've sometimes had a problem when I try to dial an international call the sprint will block it, and I check my app and it is not set for google voice to be the default for international calls.

Link to comment
Share on other sites

Google Voice has changed and uses your cell phone minutes and not VOIP. The call is initially setup by dialing a google number, but it doesn't always work.

 

 

They did this to make the call connect faster. So it will always use your cell phone minutes and charge you for the international call.

I don't understand why they made the change from using your data usage. Google seems to think that making the connection faster is what people want, when I believe most people want to use their data plan instead of phone minutes.

Link to comment
Share on other sites

Sprint is the only domestic carrier that offers this level of Google Voice integration. Kudos to Sprint. But my guess is that, while roaming on VZW, Google Voice attempts to dial the international number directly. And that prompts the error message. If so, it might actually work better with separate cellphone and Google Voice numbers.

 

I'm not too sure how it works, I think Sprint passes the call off to Google.

I know when its fully integrated it doesn't dial two numbers, just the one.

So when on VZW the carrier doesn't let me call internationally directly, like you suggested.

Make sense, thanks.

 

Is your google voice app set to dial international calls

I've sometimes had a problem when I try to dial an international call the sprint will block it, and I check my app and it is not set for google voice to be the default for international calls.

 

My cell is fully integrated, so my cell # equals the google voice #.

All calls go via Google by the way of sprint, no access number is called like when it is partly integrated. In their help as option #2, I'm using Option#1.

 

Google Voice has changed and uses your cell phone minutes and not VOIP. The call is initially setup by dialing a google number, but it doesn't always work.

 

They did this to make the call connect faster. So it will always use your cell phone minutes and charge you for the international call.

I don't understand why they made the change from using your data usage. Google seems to think that making the connection faster is what people want, when I believe most people want to use their data plan instead of phone minutes.

 

Data is not used, its a cell voice call when using the cell phone. (Not using a voip app)

 

When I use google voice/chat online on my chromebook in the browser, it does use just data.

The voice quality when using that is very good, very clear.

Link to comment
Share on other sites

Sorry, I'm using option #2.

 

http://www.google.com/googlevoice/sprint/

 

http://www.sprint.com/landings/googlevoice/?ECID=vanity:googlevoice

 

"How does this affect International calling?

International calls placed from your handset will be placed and billed through Google Voice at Google Voice's low rates. You will need Google Voice calling credit to place those calls."

Link to comment
Share on other sites

@JoeJoeJoe: OK, I see what you mean when you say that the calls are being billed by Google using their rates, though as an aside I do wonder what is Sprint's incentive to pass off intl calling revenue to Google. Hmmmm...?

 

BTW, yes, Google does have cheap international calling rates though localphone's rates still tend to be on average about half of what Google charges. That, coupled with their local numbers assignment which are diallable from multiple phones makes them very convenient to use regardless of carrier(s). I do have a google voice number also but for now I've decided not to integrate with Sprint. Maybe some day...

 

Link to comment
Share on other sites

FYI, I saw an answer about this issue.

 

Sprint/Google should post this information on their websites.

 

Sprint / GV integration is accomplished by back-end network connectivity between Sprint, Google, and their shared VoIP telephony provider, bandwidth.com. Integration only works when you are on the Sprint network. Attempting to place or receive calls while roaming on another carrier's CDMA network is not compatible with integration, because integration is dependent on call routing between Sprint and the VoIP network.

  • Like 1
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

  • Similar Content

  • 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...