atcomsystems.ca/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Wrong caller ID showing on calls from here

We have an old Avaya definity G3siv11. 11 or 12 months ago we changed our name from name1 to name2.
I have notified all our carriers and LSP's of our new name.
Most of the time we get the new name on the caller ID's of the folks being called, but not always.
At first I thought it was just folks having Name1 in the memory of the device at the farend gettiing the call.
After the test calls I'm not so sure I'm right.
Where in my system does the name show up that out pulses to called party id's?
AT&T says everything is good but,we have a pri with 3 t-1's. Could one of those still have the old name?

The problem with incorrect info on your outbound Caller ID is probably caused by the carrier at the receiving end of the call. The carrier that delivers a call to a premise is on the hook for having the correct data in their data base. You can holler at your provider, but at best all they can do is rattle the cages of the other carriers.

Funny how this situation keeps coming up. What I can't understand is why the complete CID information isn't sent by the originating carrier with the call setup to the receiving carrier then to the called party. What's with this data base nonsense? No wonder CID information is useless in many cases.

-Hal

Nowhere. There is no means for ANY system to send the calling party name. To be more specific, it is impossible and illegal to manipulate such information. The service providers on the delivering end of the data stream are the culprits for not having paid their subscription to the national database.

There's just no other way for this to be occurring.

Not disagreeing with you but it does get manipulated. I can and have told service providers what name I want the CID to display for both land lines and cells. Apparently it can go farther than that judging from the CID you see when telemarketers call.

But again, why does there need to be a national database? You're beginning to make me think there is a sinister motive for there to be a database that contains the names of every phone number.

-Hal

Turns out that local calls are not right either.
Yesterday I had another unrelated complaint the the caller id was showing up with a name of a person who hasn't been here in several years.
To cure the problem I'm changing the isdn public unknown table to reflect our main number on those stations having difficulty.
So far that seems to work.

That would be my suggestion as well; check all of your tables and options that would send out CID to the carrier. It sounds as though they have left control of CID up to the PBX.


To expand upon this further...most carriers these days (probably with the adoption of VoIP-based switches as their back end) have allowed PBX's control of the outpulsing CID. It's definitely offered from the SIP trunking providers we work with, as well as Comcast PRI service and I know that it's been part of conversations with other CLECs. Some only allow number, others allow name and number manipulation. Doesn't mean that the destination carrier will display the modified data, but at least it is possible.

I do also agree that the databasse methodology is antiquated and obsurd when making changes.

We've been fighting for two months to get a customer's CNAME updated in said database and propagated to all carriers. All because the carrier screwed up when inputting the order and chose something off the wall to display.

Something about that doesn't seem right. They aren't using our data, because if they did we would like it.
They must be using data pulled up several years ago. Kind of like a little of this and a little of that. Nothing consistant.... Frustrating....

On your station forms are you sending name and number?

...bob...

"They must be using data pulled up several years ago. Kind of like a little of this and a little of that. Nothing consistant.... Frustrating...."

That's precisely the problem.

We sometimes have that issue around here in WNY with a former cable company turned telco. Their data base gets whacked and they'll send old info, even info that was current before an area code overlay that happened in this area a few years ago.