[VoiceOps] NRUF 502

[Mary Lou Carey]

The only companies required to report NRUFs are the companies whose name 
appears as the code holder or block holder on the NANPA / Pooling report 
and in the LERG. The purpose of the NRUF report is to forecast the 
future need for 10K and 1K NXX blocks down to the rate center level. 
Utilization which is reported on the U1 page is broken down into 5 
different categories. (Assigned, Intermediate, Reserved, Aging, and 
Admin). The number of TNs ported from each block is NOT reported on.

Since only the carrier of record on the NAS / PAS reports has to file 
NRUFs, they are also the only companies that report on Intermediate 
numbers. Intermediate numbers only indicate the number of TNs "leased" 
from each block that are being resold through other wholesale carriers. 
What's reported on NPAC by SPID will never match up with the NRUF 
because the SPID is not tracked on the NRUF. Only the name of the 
carrier each block was originally signed to.


MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111

On 2024-03-24 07:25 PM, Mike Hammett via VoiceOps wrote:
> https://www.nationalnanpa.com/pdf/NRUF/GeoJobAid.pdf
> 
> “Resold” services should also be treated like ported numbers,
> meaning the carrier transferring the service to another carrier or
> non-carrier entity should classify the numbers as “Assigned” and
> the numbers should not be counted by the receiving carrier.  These
> numbers should not be considered intermediate numbers because the
> intermediate classification only applies to blocks of numbers obtained
> from or given to another carrier or non-carrier entity for future
> assignment.  Numbers transferred with resold services already have
> established customer assignments and therefore cannot be used for
> future assignment.
> 
> So it seems like if I transfer a block to someone else (anyone but an
> end-user) for them to maintain in inventory or we receive a block of
> number from someone else, then that's an intermediate number. If it's
> on a ones-and-twos basis, fulfilled per end-user request, then it's an
> assigned number. That seems difficult to maintain an accurate count
> of. If I request numbers from VoIP.MS, Bandwidth, Peerless, etc., it's
> an assigned number.
> 
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
> 
> Midwest Internet Exchange
> http://www.midwest-ix.com
> 
> -------------------------
> 
> From: "Mike Hammett" <voiceops at ics-il.net>
> To: "Mike Hammett" <voiceops at ics-il.net>
> Cc: "voiceops" <voiceops at voiceops.org>
> Sent: Sunday, March 24, 2024 6:39:12 PM
> Subject: Re: [VoiceOps] NRUF 502
> 
> What are some examples of when someone would report intermediate
> numbers? The documentation gives a technical answer, but not a
> real-world example.
> 
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
> 
> Midwest Internet Exchange
> http://www.midwest-ix.com
> 
> -------------------------
> 
> From: "Mike Hammett via VoiceOps" <voiceops at voiceops.org>
> To: "voiceops" <voiceops at voiceops.org>
> Sent: Monday, January 22, 2024 6:11:06 PM
> Subject: [VoiceOps] NRUF 502
> 
> I'm just learning about NRUF 502.
> As I read the documentation (and some Googling):
> Every phone number in the blocks I have are either Assigned,
> Intermediate, Reserved, Aging, or Administrative.
> Ported out numbers count as assigned.
> Returned ported numbers are available.
> I do this for blocks that I got from NANPA.
> I do not do it for ported numbers.
> 
> I'm supposed to be able to tell in Neustar SOA what numbers have
> disconnected. I've reached out to them to figure out how to do that. I
> couldn't find documentation that was direct enough for me to know it
> was the right thing.
> 
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
> 
> Midwest Internet Exchange
> http://www.midwest-ix.com
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops