NPA-NXX Combinations in the TFNRegistry

Key Notes:

• The Terminating Point Master (TPM) (rate center info) report and LERG (holds routing info) are used as a guideline for determining the action necessary to confirm the NPA/NXX request. These should match; however, it is possible that a value could be missing in one. The TFNRegistry™ (tfnregistry.somos.com) mapping is based on the TPM report. The TPM report is updated monthly in the TFNRegistry. It is normally updated the 3^rd weekend of the month. However; this is subject to change. We can advise Resp Org users if they want to know when to update the NPA-NXXs records to match the current validation, they can do this during the 4^th week of the month.
• It is the responsibility of the service provider (Resp Org, LEC, etc.) and North American Numbering Plan Administrator (NANPA) to enter the data into a special database when the new or changed values occur. This database is then used to create the TPM report which then the same information gets updated in the LERG.
• Download a copy of the LERG (currentlerg) to your Desktop and open the file in Microsoft Access. Use the tables to find the NPA/NXX combinations. To access the LERG, access the Help Desk's Share Point > File Server > LERG

Work / Technical Steps:

• The NPA/NXX combination(s) is not in the TFNRegistry:

1. Confirm that the requested NPA/NXX is valid in the LERG first then check that it doesn’t already exist in the TFNRegistry on the NPA-NXX-LATA Information (NXL) page.
2. If it is in the LERG and it is not in the NXL page, take a screenshot of the section of the LERG and of the NXL page. If it is not in the LERG and not on the NXL page, no screen shots are needed. Continue to step 3.
3. If it is or is not in the LERG, confirm that it is not part of a scheduled NPA Overlay on the NPA Code Opening / Overlay (NCO) page. If it is part of a scheduled NPA Overlay notify the customer that it is. Create a ticket, assign it to yourself and resolve it. Now, if it is in the LERG and not on the NXL nor NCO pages, take a screen shot of the NCO page and continue to step 5. If it is not in the LERG and not on the NXL nor the NCO pages, continue to step 4.
4. If it is not in the LERG and is not on the NXL nor the NCO pages, notify the customer that it can't be added. Create a ticket, assign it to yourself and resolve it.
5. If it is in the LERG, and it is not on the NXL (or the NXL page does not match what the LERG has (e.g. NPA-NXX listed under the wrong LATA listed in the TFNRegistry)) nor NCO pages in the TFNRegistry, create a ticket with the following information, add the screen shots of the LERG, NXL and NCO pages to it and submit the ticket to Software Support (see table at the end of this section).
6. Software Support will check the TPM report. If the combination is not listed in the TPM report, it will not be added. If it is, it will be added.
7. Once the ticket has been returned from Software Support, the Help Desk analyst will reach out to the customer to advise that it has been added or explain why the combination cannot be added based on a verification of the existing TPM report data and then resolve the ticket.

Ticketing System	Zendesk
Macro Name	INC - NXL - Issue - Missing NPA-NXX Combination - Software Support
Assigned Group	Somos Software Support
Subject (default text)	INC - NXL - Issue - Missing NPA-NXX Combination - Software Support
Internal Note (default text)	Environment: <Production or Sandbox> Issue: A Resp Org reported NPA-NXX, <XXX-XXX>, is listed on the LERG, but it is not on the NXL page and the user wants to have this corrected. Please see attached screenshots of LERG and the NXL & NCO pages and add NPA-NXX, <XXX-XXX> to the NXL page.