In late 1999, the LNPA WG, now known as the Number Portability Industry Forum (NPIF), established a “Problem Identification and Management” process (PIM) for Number Portability (NP) issues. The group, made up of Number Portability Industry members, developed:
The NPIF is not responsible for resolving all NP problems. The NPIF performs an initial evaluation of each problem/issue submitted, then either develops a resolution for the issue or refers it to the appropriate forum for resolution. Issues submitted (PIM) are tracked in the PIMs Tracking Matrix.
Issues should be submitted to the NPIF using the Problem/Issue Identification and Description Form, at least two weeks before the NPIF meeting at which Number Portability issue's discussion is desired.
| Title | Date | Description | Document |
|---|---|---|---|
| PIM 15 | 06/21/2001 | 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. T... | Download |
| PIM 14 | 04/27/2001 | 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... | Download |
| PIM 13 | 04/27/2001 | OSP removes switch translations on or near due date, and the number has not been ported to the new Service Provider. | Download |
| PIM 12 | 04/19/2001 | Some Operator Service functions will not be properly applied in a Wireless Number Portability environment. | Download |
| PIM 11 | 03/24/2001 | 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 ra... | Download |
| PIM 10 | 02/21/2001 | The lack of standards regarding the routing and charging of calls to ported numbers is causing the CLECs to assign an inordinate number of LRNs to each switch site. | Download |
| PIM 09 | 01/19/2001 | LNP calls failing resulting in trouble tickets. | Download |
| PIM 08 | 10/25/2000 | Telephone numbers get ported from a specific JIP with the incorrect LRN which route customer to wrong receiving office. | Download |
| PIM 07 | 11/19/1999 | There are continuing issues involving the on-going effects on a region of a Service Provider’s association to NPAC being down. This can, in some instances, cripple the entire region. | Download |
| PIM 06 | 12/07/1999 | The process of updating 9-1-1 Address Location Identification (ALI) databases, due to Local Number Portability (LNP), should be done utilizing the unlock/migrate process found in the NENA LNP stand... | Download |
| PIM 05 | 12/07/1999 | There are certain instances where customer lines are ported in error i.e. “Inadvertent Porting”. There are several circumstances under which this may occur. | Download |
| PIM 04 | 11/19/1999 | Need details for how working packet service affects number ranges in context for number pooling. | Download |
| PIM 03 | 11/08/1999 | A CLEC tries to port an incorrect number. We deny the port, but due to the timers, the port goes through. Our customer is taken out of service. | Download |
| PIM 02 | 09/14/1999 | The Slow Horse Sub-committee is in the process of developing an availability requirement for service provider LSMS systems. It is the purpose of this document to define the service provider mainten... | Download |
| PIM 01 | 07/10/2003 | The PIM primarily addresses the issue of porting a number served by a reseller, a scenario not addressed by the original NANC process flows. The proposed flows address all wireline and wireless LNP... | Download |
140 results returned
