June 05, 2020, 03:57:18 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1] 2
  Print  
Author Topic: CID Problem  (Read 17153 times)
wpbear
Jr. Member
**
Posts: 21


« on: February 09, 2014, 09:47:29 pm »

I have setup GV to IPKAL to Localphone to Obi100.

If I dial GV the CID shows a random 206 number.

If I dial the IPKALL # direct then I get the actual CID number as I expect.

My IPKALL # is a 425 area code not 206.

This is a new problem in the past few days, it was working with proper CID for the past few weeks.

Logged
gderf
Sr. Member
****
Posts: 489



« Reply #1 on: February 10, 2014, 05:52:26 am »

I have seen this a few times, it comes and goes.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
wpbear
Jr. Member
**
Posts: 21


« Reply #2 on: February 10, 2014, 07:45:43 pm »

If I wanted to port my GV # out so I can keep my GV #; where is the cheapest place.  So tired of Google messing things up.
Logged
cluckercreek
Full Member
***
Posts: 153


« Reply #3 on: February 10, 2014, 07:54:29 pm »

Obivoice is porting GV #'s for free with their service. You can't get cheaper than free. Grin
Logged
jazzy
Jr. Member
**
Posts: 55


« Reply #4 on: February 14, 2014, 07:25:00 pm »

I have setup GV to IPKAL to Localphone to Obi100.

If I dial GV the CID shows a random 206 number.

If I dial the IPKALL # direct then I get the actual CID number as I expect.

My IPKALL # is a 425 area code not 206.

This is a new problem in the past few days, it was working with proper CID for the past few weeks.


I have the same problem right now.  All calls to GV > IPKALL# show CID as 206-682-0185
If I call my IPKALL # directly, the CID is correct.  This started happening this past week, prior to that
calls to GV>IPKALL# were passing the CID correctly.  Is this now a permanent thing? or will it clear up and start to work again.  My IPKALL # is area code 206.  I read somewhere that the 206-682-0185 is a GV #.  Which meant that  my original GV CID got mangled when forwarding to IPKALL.  Is that
what's happening? 
Logged
gderf
Sr. Member
****
Posts: 489



« Reply #5 on: February 14, 2014, 07:27:44 pm »

I am seeing this also, but it's not happening all the time.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
wpbear
Jr. Member
**
Posts: 21


« Reply #6 on: February 17, 2014, 10:53:38 am »

That's the same number my CID has been showing.
Logged
MikeHObi
Sr. Member
****
Posts: 322



« Reply #7 on: February 18, 2014, 12:02:19 pm »

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.
Logged

Obi202 user & Obi100 using Anveo and Callcentric.
SteveInWA
Hero Member & Beta Tester
*****
Posts: 6057



« Reply #8 on: February 19, 2014, 08:42:19 pm »

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/1316844
  • WAIT 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.
« Last Edit: February 19, 2014, 08:56:48 pm by SteveInWA » Logged

--Steve

Google Voice Forum Product Expert

https://support.google.com/voice/community
Johnny
Full Member
***
Posts: 103


« Reply #9 on: February 20, 2014, 02:13:50 pm »

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.....
Logged
J4545
Newbie
*
Posts: 10


« Reply #10 on: February 21, 2014, 05:52:09 pm »

I have a GV number that forwards to my office landline, my cell, and an Obi100.

I also have a Callcentric "Pay-Per-Call" number on the Obi, which gives me outgoing calls for 2 cents a minute and E-911.

Finally an Android Talkatone free number that is yet another destination for GV calls.

Obi says: "...your OBi will continue working as it does today – with calls to your Google Voice number ringing the phone and use of Google’s service for connecting calls to the numbers you dial."

When XMPP goes away I was hoping I could just forward GV to the Callcentric number on the Obi.

So is there some reason I need to port my GV number?

Thank you very much for any info and suggestions.

« Last Edit: February 21, 2014, 07:30:47 pm by J4545 » Logged
gderf
Sr. Member
****
Posts: 489



« Reply #11 on: February 21, 2014, 06:29:21 pm »


When XMPP goes away I was hoping I could just forward GV to the Callcentric number on the Obi.

XMPP isn't used to do this now, so the end of XMPP is irrelevant for this aspect of your service.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
J4545
Newbie
*
Posts: 10


« Reply #12 on: February 21, 2014, 06:36:04 pm »

My understanding is my Obi will no longer say "SP1:  Google Voice™ Account" after May. I thought that was because it used XMPP to make that connection to GV.
Logged
gderf
Sr. Member
****
Posts: 489



« Reply #13 on: February 21, 2014, 06:38:40 pm »

Once XMPP is shut down, you can delete your SP1. Forwarding GV to a DID doesn't use XMPP or your SP1 that is configured for GV.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
J4545
Newbie
*
Posts: 10


« Reply #14 on: February 21, 2014, 06:44:58 pm »

Great, that's what I thought. So I'm still not seeing any reason to port out of GV.

From GV's point of view it is just going to keep on forwarding my number to various phone numbers. I would rather have my total system decoupled into independent components anyway.
Logged
gderf
Sr. Member
****
Posts: 489



« Reply #15 on: February 21, 2014, 06:48:24 pm »

There is no reason to port out of GV for incoming calls so long as you have one or more forwards to one or more DIDs that work to your satisfaction.

The larger problem is making outgoing calls with GV once XMPP is shut off.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
J4545
Newbie
*
Posts: 10


« Reply #16 on: February 21, 2014, 07:29:26 pm »

Thanks all for the clarifications.

Nothing is free. If it appears to be free, then it is a loss-leader or a market exploration and data collection effort. I always knew GV would change or even go away completely.

I think I can somehow survive paying Callcentric 2 cents a minute when I want to make a call from my Obi Wink Just the entertainment value of a build-your-own communication system is worth it.
Logged
gderf
Sr. Member
****
Posts: 489



« Reply #17 on: February 21, 2014, 07:35:57 pm »

You can do better than 2 cents a minute just about anywhere. In some case a lot better.
Logged

Help me OBiHai PhoneOBi. You’re my only hope.
carl
Sr. Member
****
Posts: 453


« Reply #18 on: February 21, 2014, 08:24:19 pm »

Great, that's what I thought. So I'm still not seeing any reason to port out of GV.


Hmm, have you read other postings/threads on this and other forums?  GV, including GV forwarding , is becoming increasingly unreliable.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 6057



« Reply #19 on: February 21, 2014, 09:21:42 pm »

Great, that's what I thought. So I'm still not seeing any reason to port out of GV.

From GV's point of view it is just going to keep on forwarding my number to various phone numbers. I would rather have my total system decoupled into independent components anyway.

I posted about porting out for this reason:  Many OBi customers bought the device expecting to use it with a Google-issued, or ported-into-GV phone number, as if GV was a "free phone company".  They may not have cared about, or made use of, the many other features of GV.  It never was a free phone company, and now that third-party direct access via XMPP is being shut down, some of those people will be unhappy.  Those people now have a choice:  port their GV phone number to an actual VoIP Internet Telephone Service Provider (ITSP), or keep the number with GV, and use a SIP VoIP carrier as a GV forwarding destination on their GV account, and on their OBi box.  One way or the other, it's time to make a decision and to take action now, not wait.

This has been discussed in great detail elsewhere on the forums.  My point was regarding timing, with some added tips for success.
Logged

--Steve

Google Voice Forum Product Expert

https://support.google.com/voice/community
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC