[VoiceOps] IAM callername instead of CNAM

Paul Timmins paul at timmins.net
Thu Feb 4 11:40:30 EST 2010

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.

Usually this is because they're using data from TargusInfo that is 
woefully outdated, based on Directory data, or a number of other issues.

Syniverse and TNS use this data for their SS7 based CNAM products (as 
well as their IP based ones, if I recall).

Thus those who use those providers will often see such discrepancies.

Very frustrating.


More information about the VoiceOps mailing list