It's actually beyond just caching with Targus, they also allow their customers to submit changes (read: overrides) to their database which also contribute to the problem. In Targus's favor, they are trying to do a good thing but as other posters have mentioned, it's an amazingly complex system with more carrier to carrier variation than just about any other feature out there. I think the cell phone providers are smart to just flat out not implement it. The best thing you can really do is have the person at the far end that is seeing the wrong CNAM entry complain to their own carrier. In my experience people that make a provider money have better leverage than the competitors. -Scott -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins Sent: Wednesday, October 06, 2010 6:18 PM To: Alex Balashov Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Outbound Caller-ID Name Issue on Certain Carriers On 10/06/2010 05:33 PM, Alex Balashov wrote:
Yeah, not everybody uses the same CNAM lookup providers, and there's a lot of caching going on.
Characteristically, the most accurate and up-to-date database is the one the ILEC uses; many of these VoIP ITSPs and CLECs use other third parties, and either they or the third party do a fair bit of caching and questionable update processes to save money on CNAM dips.
The whole thing's pretty stupid; it should just be canceled.
99% of it comes back to: http://www.targusinfo.com/solutions/identification/caller_name/ Syniverse uses these guys. Verisign always used its STPs and GTT to route you to the direct CNAM databases and get you the right data from the proper industry databases. Targus does not do that, despite their ironically written website they're 99% of the CNAM problem in this nation. TNS used to use them, but recently moved to their recently acquired Verisign network for caller ID with name data so they no longer have the issue either. AT&T (upper and lower case AT&T, that is) don't have this issue, nor do the ILECs obviously. -Paul _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops