Print
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Notice:
Effective August 1, 2017 the role of Change Management Administrator (CMA) of the Local Number Portability Administration Working Group (LNPAWG) for all US Regions was transferred to Telcordia Technologies, Inc., d/b/a iconectiv.
To contact the iconectiv CMA or to be added/removed from the LNPAWG distribution list please email cma@iconectiv.numberportability.com.
Please note that on or about September 30, 2017 the collection and history of industry documents will be transferred to https://numberportability.com/. Stay tuned for further updates at upcoming LNPAWG meetings and conference calls.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Problems and Issues Management
In late 1999, the LNPA WG established a "problem identification and management process" (PIM) for LNP issues. The LNPA WG is not responsible for resolving all LNP problems. The LNPA WG does an initial evaluation of each LNP problem submitted, then either develops a resolution for the issue or refers the issue to the appropriate forum for resolution. The status of each LNP issue submitted is reported to the NANC on a regular basis.
The LNPA WG has developed issue submittal guidelines, an issue submittal form, process flows, and a tracking mechanism. Issues should be submitted to the LNPA WG, using the issue submittal form, at least two weeks before the LNPA WG meeting at which LNP issue's discussion is desired.
-
PIM 22
Customers have been taken out of service inadvertently in some cases when the New Service Provider continues with a port, that has been placed into Conflict by the Old Service Provider, after the 6 hour Conflict Resolution Timer has expired, instead of investigating why the port was placed into Conflict.
Download the document PIM 22
-
PIM 21
Ported-In TN records left behind in NPAC Database and in SPs Network after some SPs seize to provide Service (e.g., Bankruptcy). This will result in incomplete calls.
Download the document PIM 21
-
PIM 20
Porting after a code is returned from a carrier going out of business and scheduled for disconnect.
Download the document PIM 20
-
PIM 19
We have noticed there are a lot of Intra-provider ports from a pooling block to the same SPID and LRN.
Download the document PIM 19
-
PIM 18
The NANC flows and narratives for Local Number Portability need to be updated to accommodate wireless resellers and the different timeframes and business model for wireless service providers.
Download the document PIM 18
-
PIM 17
Some carriers offer both wireless and wireline services. With the integration of the wireless industry into Local Number Portability, there needs to be an efficient way for other carriers to determine whether a request to port a number comes from the wireline or the wireless division of that company.
Download the document PIM 17
-
PIM 16
Erroneous Local Exchange Routing Guide (LERG) Updates:
NPA/NXX codes are being marked as portable in LERG 6. The code holder is then porting directory numbers in, out and/or within that NPA/NXX code. After some porting activity has occurred, the code holder goes into LERG 6 and then changes the NPA/NXX from a portable code to an unportable code. Any directory numbers, which have been ported in that block of numbers, are stranded.
Download the document PIM 16
-
PIM 15
In order to change the NXX code “ownership” from one service provider to another in NPAC, any active ported numbers within that code must be deleted before the ownership change can be performed. This temporarily prevents these ported customers from receiving most calls until their subscription record is recreated.
Download the document PIM 15
-
PIM 14
When an NXX code containing ported telephone numbers is disconnected in the network, calls placed to those ported subscribers fail immediately before an LNP query can be performed in order to route on the NPA-NXX of the Location Routing Number (LRN).
Download the document PIM 14
-
PIM 11
A process for moving 1k blocks between switches, within the same company, within the same rate center using EDR functionality is needed to satisfy the FCC's requirement to manage TN inventory by rate center rather than wirecenter.
Download the document PIM 11