Jump to content

Google Hangouts w/Voice (Was Google Voice)


COZisBack

Recommended Posts

I had an unexpected experience last night with this. I am not fully integrated. I have a separate Google Voice number and I simply use Google Voice as my Sprint voicemail.

 

I do have the new Hangouts and the new Hangouts dialer. I had set it up to receive GV text messages, voicemails and incoming phone calls through Hangouts on the phone.

 

Receiving GV incoming phone calls through Hangouts created an interesting result. When I get an incoming Sprint call on my Sprint number the phone rings and if I don't answer it then it rolls to Google Voice voicemail as expected. However, once it rolled then I received a new incoming phone call through Hangouts from my GV number and I had to wait for that call to expire before the caller could actually leave a voicemail message.

 

It appears that Google Voice is not distinguishing between no answer call forward from the Sprint line and an incoming call. It is ringing the Hangouts app in both circumstances. I'm going to play around with some of the call rules and see if there is a way to overcome this.

I ended up setting my GV account to Do Not Disturb. The only side effect I can see is that text messages sent to the GV number do not produce a notification on the phone. But since I use my GV # for voice mail only, that's fine with me.

 

With DND set to ON, all calls to the GV # go straight to voice mail, which is what I want.

Link to comment
Share on other sites

I noticed that when I send SMS via sprint, hangouts also shows a duplicate message from google voice. The recipient doesn't get two messages though, any idea what's causing it?

 

Sent from my VS980 4G using Tapatalk

You can set SMS to default to sending from Google Voice (which is the same number if you are Sprintegrated), should eliminate the duplicates

[Edit: doesn't seem to work]

Edited by djw39
Link to comment
Share on other sites

hangouts was updated again yesterday. I applied the update. the lag on contacts is gone and I can now choose the number that Hangouts (GV# from Sprint) sends the SMS from. Cool.

 

I am using my Verizon S4 and continue to use the Google Voice App to force all calls being made from my Verizon S4 to come from my Sprint GV#.

 

I can send an MMS from Hangouts (on Verizon S4) and it comes from my Sprint GV#, but the picture is not directly displayed to the receiving number. they get an encrypted link, they click the link and the MMS shows fine. So Hangouts sending MMS from my Sprint GV# kinda works.

 

however... receiving MMS in Hangouts (on Verizon S4) with my Sprint GV# does not work. the MMS continue to go to my actual Sprint phone.

 

Has anyone (using a similar setup) gotten the receiving MMS to work tweaking the APN setting inside Hangouts?

 

Sent from my SCH-I545 using Tapatalk

Link to comment
Share on other sites

I don't like the calling from Hangouts. I like how the Google Voice app let's me choose between Making all calls from my Google Voice number or ask me every time I make a call.

 

This gives me the option to choose from making calls from my Verizon number or my Sprint GV#.

 

If seems to me if I enable the dialer in Hangouts, all my calls will go through Hangouts. Which is not good. The purpose of me getting the Verizon service and my S4 is for rock solid voice/data coverage with no dropped calls and call clarity.

 

I use Wi-Fi Calling with my Sprint S4 720T and VoIP at my job...trust me... making regular calls from Hangouts, after the newness has worn off, will eventually be irritating. Perhaps not... but my experience has been mostly good with Wi-Fi Calling and VoIP, but at times there as been delays and call interference, where the other party has said... "I couldn't hear you, your voice was breaking up."

 

As long as Google keeps the Google Voice App alive and kicking... I will use that for my Voice calling on my Verizon phone and now I will use Hangouts for my SMS.

  • Like 1
Link to comment
Share on other sites

I finally got my merge finished. I thought I saw this in the thread somewhere but couldn't find it. When you have the box checked to ring hangout for incoming calls I can not answer in hangout because I lose data. Was there a work around for this?

Link to comment
Share on other sites

I am assuming you have downloaded the Hangouts Dialer? If so..keep in mind.. the Hangouts Dialer is on its initial release. Probably quite buggy.

 

Yes. I haven't had any issues calling out. Just when I receive a call it still comes through the normal phone as well as attempts Hangout.

Link to comment
Share on other sites

What do you want to happen? Calls answered by your phone or hangouts?

 

Sent from my SCH-I545 using Tapatalk

 

On my phone would like to try using hangout so i can keep my data live.

Link to comment
Share on other sites

Then just remove the dialer. Once I removed the hangouts dialer, the option inside hangouts about answering calls no longer exists.

 

I want the option to answer through hangout without it hitting the normal feature.

Link to comment
Share on other sites

I noticed that when I send SMS via sprint, hangouts also shows a duplicate message from google voice. The recipient doesn't get two messages though, any idea what's causing it?

 

Sent from my VS980 4G using Tapatalk

 

Yesterday, I didn't have this problem.  All my sms in Hangouts said sent "via Google Voice".  Overnight something changed because now I have the duplicate issue as well. I hadn't changed any of my settings.

Link to comment
Share on other sites

Yesterday, I didn't have this problem. All my sms in Hangouts said sent "via Google Voice". Overnight something changed because now I have the duplicate issue as well. I hadn't changed any of my settings.

That's how it happened to me. I didn't change anything and then next day it was showing the duplicates.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Its just a bug that will eventually get worked out. Yesterday I sent a text to my daughter. The Hangouts app said I sent the text SIX times. My daughter said she only received one message. In time, I am sure Google will get most bugs worked out.

 

Sent from my SCH-I545 using Tapatalk

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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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