[VoiceOps] Stale Caller ID

Tue Nov 5 11:42:55 EST 2024

Whole lot of missed opportunities with S/S that would have made it actually useful.

From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Daniel White via VoiceOps
Sent: Tuesday, November 5, 2024 10:41 AM
To: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Stale Caller ID

NOTE: This is an external message. Please use caution when replying, opening attachments or clicking on any links in this e-mail.

WARNING: Replies to this message will go to voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>. If you believe this is malicious or are unsure if this is correct, please report it using the Report Phish button and our analysts will investigate it.
There was a missed opportunity with STIR/SHAKEN to put the CNAM on the originating side.  If I have to attest the validity of the call, then I should be able to attest the validity of the CNAM I send with it.

[atheral-logo]<https://atheral.com/>

Daniel White
Co-Founder

phone: +1 (702) 470-2770
direct: +1 (702) 470-2766

Jawaid Bazyar via VoiceOps<mailto:voiceops at voiceops.org>
November 3, 2024 at 7:29 AM
Hi,

let's think about this a bit..

only the carrier that owns the number (according to LNP database etc.) knows what the CNAM data should be
only that carrier should be able to edit CNAM data

currently, as Kidd noted, terminating carriers look up the data (from one of numerous incomplete repositories of CNAM data)
And if the database isn't the same one that the owning carrier publishes in then the data is just bad - cached, out of date, etc.

How much are you all paying for CNAM data lookup on a monthly basis?

The thing in the Internet world that this is the closest to, is DNS, and that's free to publish into and free to query. The costs of running the system are distributed.

The key difference is how the system knows who controls a record and has the right to update it. Which is a more or less solved problem.

So then it comes down to the technical means to get existing switches / PBXs etc to query the data. And to query the legacy databases during a transition time.

Jawaid

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Kidd Filby via VoiceOps<mailto:voiceops at voiceops.org>
November 1, 2024 at 2:10 PM
In US PSTN-speak…. CallerID/name is a terminating feature, unlike Canada which is an Originating feature (data sent from caller). Until that changes, we are at the mercy of cached data by providers who don’t refresh/update their data. Unless Everyone dips the same exact database, which I don’t see happening anytime soon, there will be inconsistencies between carriers/providers.

Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
chris via VoiceOps<mailto:voiceops at voiceops.org>
November 1, 2024 at 12:47 PM
It's too bad ENUM never took off. Would have been great to dip the number get direct sip uri, get a url/pointer to caller id/cnam data etc. Not to mention direct peering without so many hops.

- chris

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Shawn L via VoiceOps<mailto:voiceops at voiceops.org>
November 1, 2024 at 12:28 PM
Unfortunately, you're at the mercy of the call-ed party's carrier.  A lot of providers maintain their own database, and only periodically update it. I suspect this is a hold-over from when dips were expensive.  That carrier may, or may not update their databases regularly.  For esample when I call one of our consultants, my caller id comes up on his phone as the person who had my DID 20+ years ago, well before we had a relationship with the consultant.  The correct information is being sent from our switch, and Neustar has the correct information, but his provider (I think verizon) is sending something that's completely wrong.

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Mike Hammett via VoiceOps<mailto:voiceops at voiceops.org>
November 1, 2024 at 12:20 PM
Sorry, you're right.

CNAM

-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

Midwest Internet Exchange
http://www.midwest-ix.com

----- Original Message -----
From: "Alex Balashov via VoiceOps" <voiceops at voiceops.org><mailto:voiceops at voiceops.org>
To: "VoiceOps" <voiceops at voiceops.org><mailto:voiceops at voiceops.org>
Sent: Friday, November 1, 2024 1:06:45 PM
Subject: Re: [VoiceOps] Stale Caller ID

Caller ID, or calling name (CNAM)?

NOTICE: This e-mail is only intended for the person(s) to whom it is addressed and may contain confidential information. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of GTT Communications Inc or any of its affiliates. If you have received this e-mail in error, please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person.
All quotes, offers, proposals and any other information in the body of this email is subject to, and limited by, the terms and conditions, signed service agreement and/or statement of work
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20241105/ac55e3be/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9961 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20241105/ac55e3be/attachment-0001.png>