I've never had other companies return disconnected numbers that were
ported away from our blocks, and never had any mechanism by which to do
the same for our own. We just age them and reuse them.
I cannot imagine that the LNP database would be useful for anything
other than where to route the
I was thinking if carriers didn't do one they wouldn't do the other. Are
you thinking that they may report TNs in the Re-assigned Number database
but still leave all their TNs in NPAC? I can see how that would cause
problems for the iconectiv's PortData service. Unless they have a way to
I can't speak for every carrier, but I do know from experience that not
everyone updates NPAC when numbers are disconnected. I know of CLECs that
only ever programmed their 1K blocks and handled the
Assign/Disconnect/Age/Available lifecycle internally.
Calvin Ellison
Systems Architect
iconectiv has a service called "PortData Comply for Marketers" that you
can get access to. They also offer "PortData Source for Law Enforcement"
and "PortData Validate". These services require a subscription to the
NPAC database, but you don't have to be a service provider to get them.
As long
More data for our Call Analytics/Anti-Robocall Filter: the Reassigned
Numbers Database. In our case, we'd want to use this for real-time call
analytics on every single ANI & DNIS that crosses our network, querying the
database using to determine if a number should be in Aging status
(disconnected
