Outgoing callerid name

**wthart** · 03-17-2010 06:35 PM

Tim-

I reported this problem on 3/4/2010 with ticket # EZI-948180. My caller id name did work; but, I have my been told and verified that it only shows private call. It has been this way for several months.

I am not in a position to see if it is now working; but I will check on Friday.

Should I reopen the this ticket?

Thanks

Tyler

**VOIPoTim** · 03-17-2010 06:51 PM

Originally Posted by wthart

Tim-

I reported this problem on 3/4/2010 with ticket # EZI-948180. My caller id name did work; but, I have my been told and verified that it only shows private call. It has been this way for several months.

I am not in a position to see if it is now working; but I will check on Friday.

Should I reopen the this ticket?

Thanks

Tyler

Yes, go ahead and re-open unless you got a response that it was resolved for you.

**frankd1** · 03-19-2010 01:53 PM

Just curious... any idea on the significant difference in time it takes to propagate CNAM LIDB changes for different providers? Our number with Cost Plus propagated within a day or two, and our number w/ L3 is still waiting (5+ days after the record change).

I'm fine waiting for the L3 # to propagate, but I was curious if it was just a policy difference between carriers (i.e. Cost Plus will upload record changes daily, L3 only does it once a week or two), or if there's some significant difference in their network architectures that allows some to be more nimble than others.

Again, just curious...

**VOIPoTim** · 03-19-2010 02:10 PM

Originally Posted by frankd1

Just curious... any idea on the significant difference in time it takes to propagate CNAM LIDB changes for different providers? Our number with Cost Plus propagated within a day or two, and our number w/ L3 is still waiting (5+ days after the record change).

I'm fine waiting for the L3 # to propagate, but I was curious if it was just a policy difference between carriers (i.e. Cost Plus will upload record changes daily, L3 only does it once a week or two), or if there's some significant difference in their network architectures that allows some to be more nimble than others.

Again, just curious...

It's all up the the provider. Level3 is the most difficult provider in the industry to get to do anything and takes weeks to process simple requests.

That's why we're in the process of moving all numbers away from them when there is a viable alternative. I've never met anyone that likes to deal with them

Within the next 3-6 months we hope to be Level3-free except rural areas where they are the only one with coverage.

**wthart** · 03-19-2010 03:03 PM

Originally Posted by VOIPoTim

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!

**ellinj** · 03-19-2010 04:35 PM

Originally Posted by wthart

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.

**djrobx** · 05-28-2011 12:05 PM

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

**rChaz** · 07-27-2011 02:42 PM

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

**rChaz** · 07-27-2011 07:25 PM

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