Incoming calls go straight to VM when cell phone turned off
A_Friend:
Quote from: LTN1 on August 09, 2018, 09:43:12 am
I really don't care if someone is using AT&T, Verizon or Screw You service. What I understand is that this post is about Sprint and GV. Coming in here with AT&T problems for a SPRINT issue isn't directly answering the OP with a Sprint and GV problem. Since the OP hasn't returned, I'm not sure where he is at.
All I know is that until the evidence points elsewhere, SteveInWA has answered the OP's SPRINT and GV issue. All other answers contradicting Steve is not on point.
Not entirely. Steve did say, "Conditional call forwarding works with Google Voice with all of the big four major US mobile carriers." So, the implication can be reasonably assumed to mean they all work the same. Hence, a failure with AT&T would seem significant and on topic.
Anyway, more to the point, has the OP found a resolution to his problem, and if so, what?
LTN1:
Is SteveInWA correct with issues beyond Sprint/GV? Maybe not. However, the main issue here is the OP's Sprint and GV problem. Steve, so far, has the most experience with the Sprint/GV issue, having worked with this specifically with GV for years. He is more persuasive on THIS issue than some forum newbie with an AT&T problem and so-called solution not directly related to the original post.
GPz1100:
Quote from: LTN1 on August 09, 2018, 10:20:18 am
Is SteveInWA correct with issues beyond Sprint/GV? Maybe not. However, the main issue here is the OP's Sprint and GV problem. Steve, so far, has the most experience with the Sprint/GV issue, having worked with this specifically with GV for years. He is more persuasive on THIS issue than some forum newbie with an AT&T problem and so-called solution not directly related to the original post.
With narcissistic responses such as this, if I were the OP I wouldn't bother coming back.
I don't think it's an att issue, rather a google issue because google engineer's can't seem to leave well enough alone, always implementing some sort of change which results in [un]intended side effects. Every few months something breaks in one form or another.
I relayed my experience, just because it goes against the way system should work does not make my solution wrong. Regardless, what exactly is your contribution in this thread besides trolling?
LTN1:
Quote from: GPz1100 on August 09, 2018, 11:50:08 am
Quote from: LTN1 on August 09, 2018, 10:20:18 am
Is SteveInWA correct with issues beyond Sprint/GV? Maybe not. However, the main issue here is the OP's Sprint and GV problem. Steve, so far, has the most experience with the Sprint/GV issue, having worked with this specifically with GV for years. He is more persuasive on THIS issue than some forum newbie with an AT&T problem and so-called solution not directly related to the original post.
With narcissistic responses such as this, if I were the OP I wouldn't bother coming back.
I don't think it's an att issue, rather a google issue because google engineer's can't seem to leave well enough alone, always implementing some sort of change which results in [un]intended side effects. Every few months something breaks in one form or another.
I relayed my experience, just because it goes against the way system should work does not make my solution wrong. Regardless, what exactly is your contribution in this thread besides trolling?
You don't understand how to use the true definition of narcissism. I have Sprint and GV on one of my family's cell phone and can confirm that for that phone (obviously I can't speak for all phones), the issue is exactly as Steve describes. A simple fix for Sprint and GV integration--but you have to at least have Sprint (not AT&T) to test that solution.
Now go away.
A_Friend:
Allow me to interject a related experience, which might also serve as a feature request for Google Voice.
Because I'm distributing incoming calls to 2 SIP URIs and a cellphone, I obviously couldn't use GV for the distribution, so I'm forwarding it to a Callcentric DID (okay, so now technically I'm effectively distributing it to one DID, one URI, and a cellphone) where I use their "Call Treatments" to do the distribution, specifically a simultaneous ring.
It worked great most of the time, except when I was in the subway, or the local cell tower was on the fritz or the battery on my thirsty little LG ran out. When that happened, the cell service would announce I wasn't available and hang up. Well, Callcentric has a feature where you can selectively set "Push "1" to accept call" for each destination in the group. I just set that for the cell phone and that fixed it right up. Doesn't matter if the phone is on, off, or out of signal. The SIP lines ring. If you answer with the cell phone, you get a brief message to press 1 to accept. As I'm mostly answering on a SIP line anyway, it's a minor inconvenience at worst. If nobody answers, it goes to GV voicemail. (I had the voicemail on the cell disabled.)
Now, wouldn't that "Push 1" seem to be a nice feature to add to Google Voice?
Navigation
[0] Message Index
[#] Next page
[*] Previous page