[VoiceOps] Caller ID name discrepancies between carriers
matthewb at aitech.net
Tue Mar 28 12:40:08 EDT 2017
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.
On Tue, Mar 28, 2017 at 11:28 AM, Carlos Alvarez <caalvarez at gmail.com>
> 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
> 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
> VoiceOps mailing list
> VoiceOps at voiceops.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps