[VoiceOps] IAM callername instead of CNAM

David Birnbaum davidb at pins.net
Thu Feb 4 11:55:09 EST 2010

One could argue that limited caching is acceptable (a day?  a week?)  Six months 
is a bit inappropriate.



On Thu, 4 Feb 2010, Lee Riemer wrote:

> Sounds like CNAM caching.
> On 2/4/2010 10:13 AM, Carlos Alvarez wrote:
>> On 2/4/10 7:59 AM, David Birnbaum wrote:
>>> It sure sounds like it.  TWTC is "cheating", I suppose, and depriving
>>> the rightful owner of that number of their CNAM revenue (should you take
>>> the carrier view of things).
>>> Regardless of what the "best" answer is, in the US all carriers are
>>> supposed to deliver CNAM by dipping the central database, paying the
>>> owning carrier, and delivering the result to their subscriber. But
>>> that's really a discussion for another thread.
>> Another "cheater" that has a very annoying policy...  Cox Communications 
>> seems to have a 6-18 month lag in their CNAM update policy.  I really don't 
>> know how they do it (download and store all CNAM?), but all CNAM changes 
>> take a very long time to reach their customers.  It's a source of constant 
>> complaints when our customers (businesses) call their homes (Cox) and get 
>> an old CNAM.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

More information about the VoiceOps mailing list