I have set up an OBi110 at my in-laws. I created a temporary GV # for them to use it as a trial, and routed all outgoing calls through this #. The existing landline was connected to the FXO port on the OBi110 so they could still receive incoming calls over that #. They decided they were satisfied with the quality of the GV service and so we followed the instructions
here to port their landline # to a T-Mobile prepaid cellphone.
That port has now completed, and yet I am still getting the error from GV: "Ooops! We currently don't support porting from your carrier. We apologize and are working on adding support for more carriers."
I've been researching this and have found many other people that have had this issue, but I am first wondering if it simply takes some time before GV recognizes the # now as a T-Mobile # rather than still with my landline carrier (Blue Ridge Communications). I've read posts that it doesn't. But I called T-Mobile and they said that while the port is complete, it may take another 24 hours before all the info gets transitioned. Currently when I ring the # I believe it is calling both locations. For sure it still dials the old landline. I don't actually get T-Mobile coverage where I am, so I can't confirm that it rings the cellphone, but I am receiving text messages from T-Mobile that indicate the # works.
It's a 570-629 # and appears to be owned by
Verizon. Some have said only "broadband.com" #'s are portable, but this clearly isn't true - I think 99% of the people who port their #'s successfully didn't show their #'s as being connected in any way to "broadband.com" either through localcallingguide or through
telcodata.us. So I'm not sure where that bit of info originated from.
EDIT: I meant to say "BANDWIDTH.COM", the point remains the same.
1. Is it possible that even after a successful port to T-Mobile, that it may take additional time for the needed info to transition so that GV port will stop giving the above error message?
2. If the error continues, is it possible a landline flag of some sort is still mistakenly set, and is there someone I can now contact at T-Mobile to correct this? I know this has been suggested in other posts, but there's always speculation in these types of threads - I'm wondering if anyone has anything more substantial.
3. If there ends up being no way to port the number from T-Mo to GV, is there another intermediary I can port it to which would then make it portable to GV? I suppose it would have to be another mobile provider, as these are the only #'s that can port to GV.
4. If not, then is there a free or cheap "forwarding" service which I can port the number into, which would simply forward all incoming calls from that # to a new GV #? This
ringshuffle.com looks like it would be great if I was able to port a number into them. Wouldn't help with outgoing CID, but at least then they could still receive all their calls.
5. I see that the number
can be successfully ported to Callcentric. Presumably it could also be ported to Anveo,
voip.ms, voipo, vitelity, etc. If there ends up being no way to port to GV, and we decide to simply use one of these other providers, then can someone comment on which would likely end up being cheapest annually, for an average senior couple who makes and receives a dozen calls per day, perhaps spending 30-60 minutes per day on the phone, although often significantly less. 99% of all calls are made to/from the 48 inland U.S. I've tried to put together cost comparisons for each of these, and it's not as easy to determine as I thought it might be.
Anveo appears that it could offer the cheapest rates for their purposes if they limit outgoing calls. From what I gather, I could get a free port, and then it would cost $2 per month for unlimited incoming calls, and $.01/minute for outgoing calls in the 48 inland U.S. e911 for an additional $.80/month.
Voipo appears to be $6.21 per month for incoming/outgoing if I pay 2 years in advance. Their site doesn't seem to indicate any pricing options besides this. This may be best without worrying about limiting outgoing calls.
Voip.ms lists their outgoing rates by country, they'd end up paying .0105 per minute outgoing in the U.S. Incoming calls appear to cost about the same, although there also appears to be some plan available for between $4.95 to $6.95 per month. Incoming costs are not as clear as outgoing costs on their website.
Vitelity is $7.95 per month for unlimited in/out in U.S.
Callcentric looks like it would be the most expensive just glancing quickly at their site.
Anyway, I'm hoping that tomorrow the GV port goes through, but I need to explore the alternatives so they can keep their # which they've had for over 20 years (yes, I've found and read posts which suggested older numbers are less likely to be portable. But this just seems like more speculation).