Callcentric and Google Voice Setup Guide (with CNAM)
SedonaSky:
Is Rick's problem specific to him or is everybody having intermmittant problems?
Can someone please reply to the questions from this post: http://www.obitalk.com/forum/index.php?topic=3640.msg58076#msg58076
Thank you
SteveInWA:
Quote from: SedonaSky on October 10, 2014, 09:11:24 pm
Is Rick's problem specific to him or is everybody having intermmittant problems?
Can someone please reply to the questions from this post: http://www.obitalk.com/forum/index.php?topic=3640.msg58076#msg58076
Thank you
Those original instructions include some outdated information, and some unnecessary steps on the local OBi device interface.
Rather than rehash the 2-year old instructions in an 11-page thread, or try to discuss your issue in the context of those instructions, what, exactly is your current problem?
Big picture:
Google Voice is now supported on OBi devices via a different, more secure authentication method, which is now officially approved by Google. Instructions on configuring your OBi using the new process are here: http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460As an alternative, if you want to take advantage of caller ID name service, via an inbound Callcentric phone number, you can add that CC forwarding number to your Google Voice account, disable direct inbound calls via Google Chat/OBi, and set up the CC number on a Service Provider slot on your OBi.In this scenario, you can, for example, use GV on SP1 as your default for OUTbound calls, and CC on SP2 as your default for INbound calls AND for E911 service.If you do this, you will pay CC $1.50/month for E911 service.Configuring the OBi for both GV and CC can be easily performed, using the OBiTALK portal pages; there is no need to use the OBi local web page interface for this purpose.
There was a recurring problem regarding caller ID being lost or displayed incorrectly on calls forwarded from Google Voice to numbers owned by Callcentric's own carrier, Telengy. That problem was fixed last week. There is a remaining, related problem that is intermittently happening with that same call path, causing delays or failures of forwarded calls reaching Telengy DIDs. I'm working on that right now with Rick and with Google engineering. I don't have an estimated time to resolve it, but I am optimistic, since the error data Rick supplied clearly aligns with carrier log data. Google is now working with the carriers to diagnose and resolve the failures.
Wildcatz:
Hi All
Seeing an interesting issue with Google Voice & Callcentric that led me to start a thread over @ Google yesterday. Specifically the issue I was seeing initially was that Private/Anonymous calls were being dumped into Google Voicemail even though all calls and groups were set to forward to my Callcentric number. After trying to isolate this yesterday (I tried many configurations and changes on both sides) I found that this erroneous routing was being caused by call treatments on my Callcentric account. Specifically if I set a call treatment to allow the Callcentric phone to ring (blocked or unblocked number) irregardless then sure enough the call routed through fine. However if I used ANY call treatment on the Callcentric end to say go straight to voicemail, send the call to another number, perform the telemarketer block etc the call would always default route to Google Voice voicemail and never be passed to Callcentric.
I know Callcentric are very aware of the issues with Google Voice and I raised a ticket as well (great Callcentric tech support as usual BTW) but what was strange to me is this has been working with my paid Callcentric DID for a long while. Also of interest was that yesterday when I was playing with the Google Voice account settings I actually got the call to be passed through once and then it never worked again even though the settings remained constant.
Just wondering if anyone else has seen this specific issue, knows of a workaround and if trying to do something at the hardware level, like use an OBI to bind Google Voice to 1 path and Callcentric to the other would allow some way of getting over this issue ?
Like many others I like having the Google Voice number as an intermediary if you will, something that you put on membership forms etc just in case telemarketers start to call :) So if others have another option to resolve this (maybe use a free DID and bind that ?) then I would appreciate the feedback as well.
Thanks and hope this was a good place to post this, didn't want to hijack the thread but this seemed very similar to issues I was seeing, Callcentric & Google Voice.
WC
Taoman:
Quote from: Wildcatz on February 03, 2015, 10:08:40 am
However if I used ANY call treatment on the Callcentric end to say go straight to voicemail, send the call to another number, perform the telemarketer block etc the call would always default route to Google Voice voicemail and never be passed to Callcentric.
I'm curious how you know this to be true? Have you actually looked at the Callcentric logs to make sure the call isn't actually being forwarded to Callcentric but that it just keeps ringing until GV voicemail picks up?
Google Voice doesn't support early media. Most of the Callcentric call treatments use early media. To test, make a Callcentric call treatment that currently isn't working with Google Voice. Then call your Callcentric DID directly (bypassing Google Voice) and what happens? It should work.
Wildcatz:
Thanks of your reply, I did try call treatment setup with tests made direct to the Callcentric number and they worked as expected. It appears to be the transport(s) between Google Voice and their carrier(s) and Callcentric which is a shame as like I said something appears to have changed as this was working fine to my paid Callcentric DID before. Call centric are their usual helpful and resourceful selves and certainly appreciate them looking into this too.
Navigation
[0] Message Index
[#] Next page
[*] Previous page