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
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.
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
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.
