Page 4 of 4 FirstFirst ... 234
Results 31 to 35 of 35

Thread: Outgoing callerid name

  1. #31
    Join Date
    May 2009
    Location
    Boerne, TX
    Posts
    20

    Default Re: Outgoing callerid name

    Quote Originally Posted by VOIPoTim View Post
    Yes, go ahead and re-open unless you got a response that it was resolved for you.
    I reopened the ticket yesterday and it appears that the changes have already propagated.

    I made a few calls and my outgoing caller id name appears to have returned. I am no longer "private call."

    Thanks!

  2. #32
    Join Date
    Jul 2009
    Posts
    13

    Default Re: Outgoing callerid name

    Quote Originally Posted by wthart View Post
    I reopened the ticket yesterday and it appears that the changes have already propagated.

    I made a few calls and my outgoing caller id name appears to have returned. I am no longer "private call."

    Thanks!
    Same here, seems to be working today.

  3. #33
    Join Date
    May 2011
    Posts
    15

    Default Re: Outgoing callerid name

    I sent a support request about this and was told "our primary carrier doesn't support this". Who is the primary carrier now?

  4. #34
    Join Date
    Jul 2011
    Posts
    4

    Default Re: Outgoing callerid name - NOT Supported with upstream carrier Bandwidth.com?

    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

  5. #35
    Join Date
    Jul 2011
    Posts
    4

    Default Re: Outgoing callerid name

    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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •