CID Problem
gderf:
I am seeing this also, but it's not happening all the time.
wpbear:
That's the same number my CID has been showing.
MikeHObi:
For now I have just switched to forwarding to google chat with voice and will live without CNAME. Google voice has become just way too unreliable with forwarding to both Callcentric and Anveo. For the past 2 weeks I've been having it forward through Anveo had numerous reports of call termination problems. I'm jealous of those not experiencing similar issues. I think for the home line I'll probably just port the GV number down to Anveo when it comes time.
SteveInWA:
An observation/opinion, and a suggestion:
IPKall is simply junk. Their numbers have all been recycled through many users, often used for GV for a short time, then abandoned, creating a mess in Google's database. Google blocks numbers after a certain number of these recycled uses, to prevent abuse of their system for spam calling, harassment, or other unwanted activity. I have no idea why you are seeing that Seattle number as caller ID, but it is neither in Google's CLEC or IPKall's systems. It's a former Qwest number: http://tnid.us/lookup/2066820185/ likely ported into oblivion and erroneously being displayed.
Caller ID is sent by the first LEC to put the call onto the PSTN. That's GV's CLEC, bandwidth.com, in this case. IPKall is mangling it upon receipt; it's their screw-up. Whichever ITSP you happen to use via SIP forwarding (localphone, Callcentric, Anveo, etc), is just a pass-through; they have no involvement whatsoever in altering the CID. The fact that IPKall doesn't act as a true phone service provider, but requires sponging off of some actual ITSP, is even more reason to avoid them.
For all you folks holding out until the last minute to port out of GV: don't wait. Do it now. Think about it: porting out of GV, as it exists today, is a crap shoot. Many users experience problems with their ported-out number remaining stuck in Google's CLEC database, interfering with the ability of inbound callers reaching the number after it's been ported. Sometimes, this gets cleared up automatically after Google runs a periodic batch job to catch such problems. Sometimes, it never gets fixed. There is no customer support at all from Google to resolve these issues.
If you wait until May 15th, there will be a gigantic flood of ports-out, guaranteeing delays, even more problems, and less likelihood of getting them fixed. You will suffer the consequences.
So, the time for action is now. Getting stuck in the cycle searching for the cheapest, or even free phone service is foolhardy. Pick a service provider and go for it.
*Keys to success when porting out of GV:
Read and follow the directions: https://support.google.com/voice/answer/1316844WAIT several days AFTER you receive confirmation from Google that your number is unlocked, before submitting a request to the gaining carrier to take your number. Although GV says your number is unlocked, bandwith.com has been slow to actually unlock it. If you try too soon, your new (gaining) carrier's port request will be rejected.When submitting a request to your new (gaining) carrier, use your 10-digit GV phone number as the account number, and your VM PIN as the account PIN. Important: if you originally had a GV-issued phone number, and later ported in your own number, then abandoned the GV-issued number, you may need to use the original GV-issued number as your account number. We're not sure how to know if this applies; it's just been observed to work under some circumstances.Do not "churn" your port (do not cancel and resubmit repeatedly when you get impatient). Wait for the port to either succeed or fail. If it fails, it will be canceled by the system.
Be patient. Prayer and/or animal sacrifice might be necessary.
Johnny:
SteveInWA,
Excellent advice.
I am doing exactly as you suggested and am porting out now.
In fact I have already ported out a few GV numbers and have run into problems doing so.
Your advice about waiting a few days after "unlocking" your GV number is great advice. I didn't realize this, and two times my ports were rejected for not "unlocking" the number first, when in fact, I had "unlocked" the number before starting the port.
Also, as you mentioned, one of my ports didn't quite complete entirely and I had some messages and calls going to one carrier and some going to my GV account. Finally after a lot of haggling, GV released my number and the port completed.
The GV online forums aren't much help when you have problems.
So, in conclusion, I would definitely recommend people follow your advice as to porting out now, but some folks just can't let go.
Good luck if you decide to ride it out.
Me? I'm getting off now.....
Navigation
[0] Message Index
[#] Next page
[*] Previous page