Anveo for ObiTalk (Approved Service Provider)
c3c3:
My data point for porting:
3/9 unlocked GV port out
3/13 sent porting form
3/14 Anveo acknowledged porting request
3/21 GV approved port out
3/24 Anveo email: porting almost complete
3/27 number switched to Anveo
Incoming caller ID to that ported number had a strange "empty...." string. An email to Anveo support fixed that very quickly.
MikeHObi:
Quote from: c3c3 on March 27, 2014, 01:01:05 pm
My data point for porting:
3/9 unlocked GV port out
3/13 sent porting form
3/14 Anveo acknowledged porting request
3/21 GV approved port out
3/24 Anveo email: porting almost complete
3/27 number switched to Anveo
Incoming caller ID to that ported number had a strange "empty...." string. An email to Anveo support fixed that very quickly.
For me was similar.
3/17/2014 8pm Unlock GV Number and Request Port from Aveo.
3/18/2014 2pm Anveo Acknowledges Receipt of request.
3/25/2014 Notice and New Number appears from Anveo + charge for 11 months and 1 prorated.
3/27/2014 Port complete. Number no longer in google voice and calls now ring into Anveo.
I also have a strange "empty" string on CID. Anveo is checking into it. They claim it is an issue with the provider not completing the port properly.
c3c3:
AlanB, did you have the "empty" string issue? Since both MikeHObi and I have/had the same problem, that should be a systematic issue.
Both numbers are still in my Anveo account. Now that the porting form has a checkbox for number replacement, I'll wait a few days to see if that will be done automatically.
MikeHObi:
Quote from: MikeHObi on March 27, 2014, 01:52:30 pm
For me was similar.
3/17/2014 8pm Unlock GV Number and Request Port from Aveo.
3/18/2014 2pm Anveo Acknowledges Receipt of request.
3/25/2014 Notice and New Number appears from Anveo + charge for 11 months and 1 prorated.
3/27/2014 Port complete. Number no longer in google voice and calls now ring into Anveo.
I also have a strange "empty" string on CID. Anveo is checking into it. They claim it is an issue with the provider not completing the port properly.
Issue is now fixed with CID. Only was a problem for a couple hours and Anveo got it fixed. Note this is my 3rd number with them, first one ever ported. The other numbers never had this issue so I think it is something with how their carrier is handling the port. I believe they use Bandwidth.com which is the same place my number was with when attached to Google Voice.
ericab:
when i ported my ATT landline into Anveo about 2 weeks ago, i had the same thing happen with 'emptyXXXXXXXXX'
it disappeared on its own in exactly 24 hours, and required no intervention fom anveo.
Navigation
[0] Message Index
[#] Next page
[*] Previous page