I sent a support request about this and was told "our primary carrier doesn't support this". Who is the primary carrier now?
I'm a new VOIPo customer & ported my longtime land line (Verizon) phone number last week. My outgoing Caller ID has now been changed from my name to a local city name. Not happy. I saw in a couple threads here that, although not officially supported by VOIPo, "Due to increased volume and growth, we've had more leverage and have worked with some of our primary carriers to expand its availability. As a result, we now offer Outgoing Caller ID Name in approximately 98% of our Coverage Area for new and ported numbers"
My upstream carrier is now Bandwidth.com (per tnid.org), which forum posts indicate will work with VOIPo on caller ID names, and VOIPo has dealt with them since 2006.
I submitted a support request to VOIPo and the response was:
"We do not support Outbound Caller ID Name because our upstream carrier partner in your area does not support it or allow us to set it. They only support showing the city. If they begin to offer it in the future, we will make it available." Status: Closed
This is very disappointing - I don't want people screening my calls because they don't recognize the ID.
Edit: See the next post for further explanation
Last edited by rChaz; 08-10-2011 at 07:50 PM. Reason: delayed post finally posted
Ok, this thread explains the issue/status clearly (12-22-2010 post #7 by VOIPoTim):
VoIPo outgoing CNAM
http://forums.voipo.com/showthread.p...-outgoing-CNAM
It would be nice if this were part of the FAQ so it would be easier to know what to expect for Outgoing CID Name after a port. Prior to porting I expected that since my name was already in the CNAM databases, it would stay there. Verizon apparently maintained the database I was in & wiped it upon the port. So now I'm just a city, sigh...
Bookmarks