Will GoogleVoice stop working on all deployed OBi devices after May 15?
giqcass:
I have not personally had any issues with an IpKall number. My thought here is if you aren't having trouble then just leave everything alone. I would also try to keep things as simple as possible. For reliability I have been forwarding my IpKall number directly to my Obi. I wish Google would allow us to forward directly to a sip address. That would remove a lot of issues. If you are willing to port your number Anveo and Callcentric provide most Google Voice call routing capabilities for a small price. They even have a few extra services. Localphone in my opinion remains an excellent choice for outbound calling but it offers no bells or whistles for inbound routing. That is why I choose to use them as an outbound only service.
telecomm:
Quote from: SteveInWA on December 11, 2013, 08:33:14 pm
Quote from: telecomm on December 11, 2013, 11:56:46 am
Thanks, I got a free DID from IPKall today. I tested it and my results are not that good. Sometimes the call comes through, other times it does not. I have the free IPKall and the free Callcentric DIDs setup so my GV number rings them via my Callcentric SIP, but still they only work part of the time. I have tested seperatly, without GV (direct DID), and still the same unreliability. Good thing about GV is at least the VM will go on and ask the caller to leave a message for those calls that never ring for me.
I wonder if going through Callcentric direct would provide more reliability? To pay for a plan to include incoming and outgoing calls on a non free DID line.
I have this setup for my wife with her business. She does not seem to think she is losing calls and all go to GV voice mail, but I wonder. Her internet is via ATT UVerse, if that even matters, and mine is WOW. I will have to go to her office and test, and if I find the same thing, switch to a more reliable method and just pay the 20 bucks or so a month. Of course, I welcome all ideas.
As of today, I would not recommend using either IPKall or Callcentric's free DID numbers as Google Voice forwarding destinations. Google's carrier is experiencing problems connecting to these numbers, resulting in various symptoms, including incorrect or missing caller ID data, delays in connecting, or failure to connect. I've escalated this issue to Google, but I am not optimistic it will be fixed in the near term. Some Anveo users are experiencing the same problem. From what we've seen so far, Callcentric's paid DIDs, (in other words, DIDs you select in your area code of choice, and pay a monthly fee to maintain) work fine as forwarding targets for GV. Speculation (and only speculation at this time) is that the cause is the least-cost routing being used by GV's CLEC (carrier) to connect to the CLECs providing the free DIDs. Because this routing can be different from one call to the next, some users' free DIDs seem to work sometimes, and sometimes not, and some users' DIDs always or never work.
My own opinion as of today is that it is a waste of time to experiment further with swapping free DIDs until the CLECs resolve the issues.
Thanks! Any idea why paid DIDs might be working better? I think I will try that just in case, at least for the office phone.
telecomm:
Quote from: giqcass on December 11, 2013, 08:54:53 pm
I have not personally had any issues with an IpKall number. My thought here is if you aren't having trouble then just leave everything alone. I would also try to keep things as simple as possible. For reliability I have been forwarding my IpKall number directly to my Obi. I wish Google would allow us to forward directly to a sip address. That would remove a lot of issues. If you are willing to port your number Anveo and Callcentric provide most Google Voice call routing capabilities for a small price. They even have a few extra services. Localphone in my opinion remains an excellent choice for outbound calling but it offers no bells or whistles for inbound routing. That is why I choose to use them as an outbound only service.
Thanks. Would you mind pointing me in the right direction on how to direct forward the Ipkall # to the Obi?
SteveInWA:
Quote from: telecomm on December 12, 2013, 04:57:22 am
Thanks! Any idea why paid DIDs might be working better? I think I will try that just in case, at least for the office phone.
I believe it is because the problem may exist in the choice of call routing between Google's local exchange carrier (CLEC), and Callcentric's CLEC, http://www.telengy.net that owns the blocks of DIDs CC is issuing for free. CC leases their paid DIDs from several other CLECs (depending on the location of the "rate center" or local calling exchange of the DID). It's always possible that those DIDs will suffer the same fate at some point, but there haven't been any reports of problems so far on CC's paid DIDs.
I'm going to go off-topic here, to say that, on the Google Voice Forum, we regularly try to discourage people from using GV for business purposes. There's no direct customer support from Google, and when things go wrong (like this, or worse, when your clients can't reach you), it can damage your business financially, and damage your reputation for responsiveness. Decide if the small amount of money saved is worth your risk.
gderf:
Quote from: telecomm on December 12, 2013, 05:00:41 am
Thanks. Would you mind pointing me in the right direction on how to direct forward the Ipkall # to the Obi?
See: https://www.obitalk.com/forum/index.php?topic=1292.0
No idea if it works or not I have my IPKall number forwarded to my free Callcentric IP Freedom account which is registered on my OBi.
Navigation
[0] Message Index
[#] Next page
[*] Previous page