Caller ID name discrepancies between carriers

On occasion we have a problem where CNAM is shown incorrectly by one or two destination carriers. Most often it has been Cox and T-Mobile, because they seem to cache CNAM "forever." Today it's Verizon wireless. They are showing an ancient name for one client. We changed it at least three years ago. Our carrier for that number is Onvoy. Should we open a ticket with them? I'm guessing I'd have no success calling Verizon. I have been able to call Cox when they are screwed up, but probably only because I have a direct NOC number.

The traditional logic has been "open a ticket with the terminating side". However-- the reality is that most originating carriers (including Inteliquent/Onvoy/Vitelity/Broadvox/360 Networks) have relationships with multiple CNAM database vendors and can engage them directly to correct an error if you initiate a ticket. ~Matthew On Tue, Mar 28, 2017 at 11:28 AM, Carlos Alvarez <caalvarez at gmail.com> wrote:
On occasion we have a problem where CNAM is shown incorrectly by one or two destination carriers. Most often it has been Cox and T-Mobile, because they seem to cache CNAM "forever." Today it's Verizon wireless. They are showing an ancient name for one client. We changed it at least three years ago.
Our carrier for that number is Onvoy. Should we open a ticket with them? I'm guessing I'd have no success calling Verizon. I have been able to call Cox when they are screwed up, but probably only because I have a direct NOC number.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (2)
-
caalvarez@gmail.com
-
matthewb@aitech.net