Google Voice to CallCentric Delayed Fowarding Rings
chilirock:
For now, I've turned off the Call Forwarding to the CallCentric number and turned on Google Chat. I lose the CNAM even though I'm paying for it, but at least I get my incoming calls. I created a help ticket with CallCentric. CallCentric's response was that it was likely a Google Voice issue. So I posted a help topic similar to this on over on the Google Voice Forum.
SteveInWA:
Quote from: chilirock on February 13, 2017, 06:27:53 am
For now, I've turned off the Call Forwarding to the CallCentric number and turned on Google Chat. I lose the CNAM even though I'm paying for it, but at least I get my incoming calls. I created a help ticket with CallCentric. CallCentric's response was that it was likely a Google Voice issue. So I posted a help topic similar to this on over on the Google Voice Forum.
Neither party is interested in further troubleshooting this issue. It has a long history (years) of finger-pointing.
Perhaps Taoman could open a ticket with RingTo/Bandwidth, but aside from that, there's nothing that can be done.
djjazzy28:
Just now checked fwd to CC from my GV number, and it rang almost instantly! 1700 hrs 2/13. My CC number is a 646 area code. Gonna keep it forwarded for now and see if GV forwards to CC in a timely manner. Just tested it again right before I post this, and it rang instantly again. Hope it stays like this.
SteveInWA:
Thanks for the update.
Yah, my two CC/Telengy Area Code 845 numbers are ringing immediately today. Chalk it up to another classic telco answer, "Humm, it's working now."
Taoman:
Likewise. Forwarding to Callcentric from GV appears to be back to normal.
Navigation
[0] Message Index
[#] Next page
[*] Previous page