Caller ID name (CNAM) issue when forwarding GV to Callcentric
VOIPisGreat:
In the past year and a half there has been a couple extensive periods that GV weren't properly forwarding to the Callcentric free DID, with delayed/no ring or/and wrong callerID. Just a few days ago I again had a few calls didn't ring the Callcentric DID.
So it's great when it works, but definitely not something you'd like to rely on.
Rick:
I also had some issues a few days back. And, the issues are not just for Callcentric free DIDs, they are for all CC DIDs. In short, GV doesn't reliably forward calls to CC. That's not going to change.
ceg3:
Quote from: Rick on May 07, 2015, 06:20:29 am
I also had some issues a few days back. And, the issues are not just for Callcentric free DIDs, they are for all CC DIDs. In short, GV doesn't reliably forward calls to CC. That's not going to change.
I wonder if you think it worth giving up the CNAM by way of CC to insure more reliable GV, based on your experience.
oecra:
I would. CNAM is useless if the calls aren't even going through.
Taoman:
Quote from: oecra on May 04, 2015, 10:02:19 am
I gave up on CC and started using Simonics for incoming CNAM. Seems to be working fine so far.
I also use the Simonics GV gateway. I use CC only as failover now. For a one time fee of $5.99 you get CNAM and forwarding to SIP URI if desired. I register to the Simonics SIP server and I also forward via SIP URI to my VoIP.ms account for an additional failover route.
I experience less latency using the Simonics GV gateway than with either my CC or IPComms DIDs. So for me it's about more than just CNAM. I also get higher quality calls and SIP URI forwarding.
Navigation
[0] Message Index
[#] Next page
[*] Previous page