Getting Caller ID Name to appear on Obi110 with Google Voice

(1/7) > >>

xtwister161:
I noticed that Google Voice does not forward the caller name, only the phone number.

There was a solution proposed, by having incoming calls forwarded from Google Voice to Callcentric or Anveo. This would display caller id, all outgoing calls would still go though Google Voice directly.  These were discussed here:
http://www.obitalk.com/forum/index.php?topic=3024
http://www.obitalk.com/forum/index.php?topic=3640

However, I never saw anyone bring up the fact that the reason I (and I'm sure many others) use Google Voice because of the voice quality and reliability.  If I have my incoming calls routed to my Obi110 from Google Voice though Callcentric (or any other company), won't this create a higher latency in the voice call?  Can't this also lower the quality of the call, as well as probably lower the reliability (percentage wise)?

I've never seen anyone bring up any of these concerns.  If the quality of the call is effected, then I don't think it would be worth it to reroute the call.

Any input would be appreciated.

gderf:
I forward my GV number to CC for exactly that reason - to get CNAM. I haven't experienced any latency or call quality problems. If I did, I wouldn't use it that way.

Why don't you try it yourself and see. AFAIK, you can still get up to two free CC DIDs.

xtwister161:
Quote from: gderf on April 17, 2015, 10:51:09 am

Why don't you try it yourself and see. AFAIK, you can still get up to two free CC DIDs.

I recently switched to GV from Future Nine, and the quality has significantly improved, I just don't want to jeopardize it.  I setup Anveo for my E911, so I'd probably use them if I did this.  But if I did, the actual voice call would technically take a longer path to get to the phone, correct?

gderf:
There is no jeopardy in forwarding your GV number to a CC DID. If you don't like it, just stop doing it. It takes seconds to move things around like this. It may take a fraction of a second longer for the phone to ring via a non-GV path, but that kind of difference is meaningless.

xtwister161:
Just found this interesting thread:
https://productforums.google.com/forum/#!topic/voice/veF9ZjKwlpw
Quote

if you use Callcentric as documented, Google Voice is working as designed, to forward calls to one of a user's selected forwarding targets.  It's a minimal path, and with a high-quality ISP connection at YOUR home/office, AND a high-quality telco (POTS or VoIP), it should sound no different than Google's native XMPP connection.  Remember, regardless of if you are using Google Voice/Chat via XMPP to the OBi, or using a VoIP provider, once the call is "set-up" using SIP or XMPP, the underlying traffic is over RTP...same protocol for both services, ignoring any tweaks to the protocol settings.
From his comments, it seems to be the same voice quality, so I may give Anveo a try.

I already have Anveo for E911.  Any reason I should switch to Callcentric?

Navigation

[0] Message Index

[#] Next page