I've been using Google Voice with CallCentric as our phone service for the past 2.5 years and things have worked pretty well. Some people have had trouble calling me and the call quality hasn't always been the best, but I've always accepted that as a reasonable trade-off for a phone service running at under $5.00 a month.

Over the past few months however, I've been having trouble with Google Voice ringing our numbers. When I call a number through the Google Voice web site, it now takes tens of seconds to ring my phone. It used to be almost instantaneous - in fact, I used to chuckle to myself at how quickly Google Voice could ring the number after I pushed the "Call" button. But now, with no change on my part, there's this huge delay. Possibly related to this, more incoming calls aren't ringing our home phone before going to voice mail - perhaps the delay on that end is so long that it's just not reaching the phone before the timeout happens and the caller is sent to our voice mail.

My wife, who is at home during the day and has to deal with the brunt of this not working well, is getting tired of the hassle. We'd regret having to leave the Google Voice features which we've come to appreciate (people need to only know one number, central place for voice mail, etc.).

Here's my setup (let me know if I'm missing something helpful - I'm certainly no VoIP expert):

  1. I have a CallCentric DID number.
  2. I have a Linksys SPA 2102 router that I configured to make and receive calls via the CallCentric service. This works very well if Google Voice is not used.
  3. I have Google Voice number that is configured to forward numbers to my CallCentric number.
  4. In addition to the CallCentric number I mention above, we also have an emergency cell phone that Google Voice forwards to, but it's never on. I've tested it some now to do a bit of research for this post, and it also has intermittent delays. I would guess that this probably rules out CallCentric as the bottleneck.

Is there something that has changed with Google Voice this year causing us these issues? Is there something that I might be doing wrong?

  • I was wondering if you ever managed to solve this problem. I have the exact same setup as you (except an Obi instead of the SPA2102 that you have), and everything was fine with me until last week. Now all of a sudden, there's the huge delay in ringing, and I'm trying to figure out why.
    – PonyEars
    Nov 22, 2013 at 0:50
  • I don't use Callcentric anymore. I've replaced it with Obi (an Obi110, to be specific) and have been very happy with it. The call quality is better than what we had with Callcentric.
    – firebush
    Jan 19, 2014 at 4:47
  • Yes, it's the same with me: GV via Obi is better quality than Callcentric. However, GV will be terminating their xmpp service in a few months this year, at which point the Obi will stop working with GV unless you pay them a fee. So I'm still looking for an alternative in the longer term.
    – PonyEars
    Jan 19, 2014 at 6:46
  • Update: I found that all I had to do was change my phone number with Callcentric a couple of times until I found one that works 100% well with google voice.
    – PonyEars
    Mar 20, 2014 at 22:26

1 Answer 1


Callcentric acknowledges issues with Google Voices, and says the issues are not on their end.

Pasted from the link above:

Are there any known issues with Callcentric and GoogleVoice?

At this time we have identified that GoogleVoice has trouble forwarding and placing calls to random Callcentric numbers. The symptoms include:

Lost calls Dropped calls Incorrect callerID Anonymous callerID

We would like to make it clear that there is no difference in quality nor functionality between free numbers and paid numbers offered by Callcentric. Customers experiencing these GoogleVoice issues will note that they can reliably receive incoming calls directly on their Callcentric numbers when GoogleVoice is not involved.

Based on our industry experience and extensive testing/troubleshooting; we believe this issue may be due to the outgoing carrier being used by GoogleVoice potentially using poorer quality routes. We are currently working with GoogleVoice on this issue to try to attain additional information and also to see what changes can be made on their end (GoogleVoice) to resolve the problem satisfactorily.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.