Problem With Callcentric Incoming Caller ID
sdb-:
It is probably a carrier generic number. Perhaps supplied by the GV carrier to fake an intra-LATA or intra-State call.
I noticed that when my localphone account calls my IPKall DID I get a generic carrier CID. Localphone cannot call my GV number. But when I use my cell to call my GV number and it forwards to my IPKall DID then I get the proper CID. A few weeks ago those tests all operated correctly and I haven't changed anything.
Studly:
Are most people who have GV forwarded to a free NY Callcentric number still having problems with the incoming caller ID? I was considering getting a free NY Callcentric number, and forwarding my GV line to it, just to get incoming caller ID with name. I'm reconsidering now, unless the problem has been resolved.
lhm.:
It has not been resolved.
MikeHObi:
Quote from: Studly on December 18, 2013, 05:13:52 pm
Are most people who have GV forwarded to a free NY Callcentric number still having problems with the incoming caller ID? I was considering getting a free NY Callcentric number, and forwarding my GV line to it, just to get incoming caller ID with name. I'm reconsidering now, unless the problem has been resolved.
Note, this isn't only a Callcentric issue. Anveo also has issues with their cheap DID's. This is really a google issue.
sdb-:
I saw problems a week or two ago with an IPKall DID as well. Before and since then it has been working great.
Navigation
[0] Message Index
[#] Next page
[*] Previous page