<div dir="auto"><div>Right I understand that. Enum was proposed as a potential way to democratize routing and wouldn't be bound by the PSTN or centralized databases that was the ultimate goal. It had potential but failed to take off unfortunately due to non technical reasons :(<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2024, 4:10 PM Kidd Filby <<a href="mailto:kiddfilby@gmail.com">kiddfilby@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">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. <br clear="all"><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="font-family:tahoma,sans-serif">Kidd Filby<br>661.557.5640 (C)<br><a href="http://www.linkedin.com/in/kiddfilby" title="View public profile" name="m_-5192919700452564219_SignatureSanitizer_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter_SafeHtmlFilter_webProfileURL" target="_blank" rel="noreferrer">http://www.linkedin.com/in/kiddfilby</a></span> <br></div><div dir="ltr"><br></div><div dir="ltr"><br></div></div></div></div></div></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2024 at 12:47 chris via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank" rel="noreferrer">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>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. </div></div><div dir="auto"><div><div dir="auto"><br></div><div dir="auto">- chris</div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2024, 2:29 PM Shawn L via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank" rel="noreferrer">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 1, 2024 at 2:21 PM Mike Hammett via VoiceOps <<a href="mailto:voiceops@voiceops.org" rel="noreferrer noreferrer" target="_blank">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sorry, you're right.<br>
<br>
<br>
CNAM<br>
<br>
<br>
<br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
<a href="http://www.ics-il.com" rel="noreferrer noreferrer noreferrer" target="_blank">http://www.ics-il.com</a><br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
<a href="http://www.midwest-ix.com" rel="noreferrer noreferrer noreferrer" target="_blank">http://www.midwest-ix.com</a><br>
<br>
----- Original Message -----<br>
From: "Alex Balashov via VoiceOps" <<a href="mailto:voiceops@voiceops.org" rel="noreferrer noreferrer" target="_blank">voiceops@voiceops.org</a>><br>
To: "VoiceOps" <<a href="mailto:voiceops@voiceops.org" rel="noreferrer noreferrer" target="_blank">voiceops@voiceops.org</a>><br>
Sent: Friday, November 1, 2024 1:06:45 PM<br>
Subject: Re: [VoiceOps] Stale Caller ID<br>
<br>
Caller ID, or calling name (CNAM)?<br>
<br>
> On Nov 1, 2024, at 1:52 pm, Mike Hammett via VoiceOps <<a href="mailto:voiceops@voiceops.org" rel="noreferrer noreferrer" target="_blank">voiceops@voiceops.org</a>> wrote:<br>
> <br>
> How common is how stale of caller ID data? We have a customer that is complaining that they're getting the wrong data on their phone. They insist it's not a local directory. We've verified it works fine on other providers.<br>
> <br>
> <br>
> <br>
> -----<br>
> Mike Hammett<br>
> Intelligent Computing Solutions<br>
> <a href="http://www.ics-il.com" rel="noreferrer noreferrer noreferrer" target="_blank">http://www.ics-il.com</a><br>
> <br>
> <br>
> <br>
> Midwest Internet Exchange<br>
> <a href="http://www.midwest-ix.com" rel="noreferrer noreferrer noreferrer" target="_blank">http://www.midwest-ix.com</a><br>
> <br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org" rel="noreferrer noreferrer" target="_blank">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
-- <br>
Alex Balashov<br>
Principal Consultant<br>
Evariste Systems LLC<br>
Web: <a href="https://evaristesys.com" rel="noreferrer noreferrer noreferrer" target="_blank">https://evaristesys.com</a><br>
Tel: +1-706-510-6800<br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" rel="noreferrer noreferrer" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" rel="noreferrer noreferrer" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" rel="noreferrer noreferrer" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div></div></div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank" rel="noreferrer">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div></div>
</blockquote></div></div></div>