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 95 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 94 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 93 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 92 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 91 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 90 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 89 | 07/11/2017 | During iconectiv LNPA transition testing of a local system, issues were discovered that impacts the execution and/or verification of an Industry Test Case (ITC) required for certification. These iss… | Download |
| PIM 88 | 07/12/2016 | Some Service Providers do not have a contact number to assist with porting fallout questions. Instead, the carriers rely on e-mail. There are not any documented guidelines around using email for po… | Download |
| PIM 87 | 03/30/2016 | LNPA WG Best Practices reflect the consensus of the working group regarding the preferred processes for porting. Best Practice 0004, N-1 Carrier Methodology Clarification, was originally submitted b… | Download |
| PIM 86 | 05/12/2015 | Originally submitted as per below, seeking consensus to amend the scope of this PIM to address overall challenges related to claims of an unauthorized port in order to develop one cohesive PIM and re… | Download |
| PIM 85 | 04/01/2015 | Consumers are experiencing negative porting experiences as a result of the lack of uniformity and clarity in processes that drives port completion timeframes. We are allowing resellers to validate on… | Download |
| PIM 84 | 12/05/2014 | There is not an industry defined process interval for Wireless to Wireline and Wireless to Wireless reseller ports. Reseller ports are not considered simple ports, they are complex. There is not a… | Download |
| PIM 83 | 01/06/2015 | Initially, a request was made by a number of Service Providers in the LNPA Working Group for Neustar to create a report that reflects all wireless Service Providers that have Long T1 and T2 Timers se… | Download |
| PIM 82 | 10/30/2012 | Due to the automated processing of large quantities of ports, there are occasions (rare, but can happen) that an Old Provider may have auto-issued a FOC and then their downstream systems may discover… | Download |
| PIM 81 | 10/16/2012 | It has come to the attention of Providers that a New Provider is using an NPAC modify message to unilaterally move up the port due date once the T1/T2 timers have been stopped due to both matching … | Download |
| PIM 80 | 10/04/2010 | A significant quantity of ported/pooled NPAC database records currently contain LRNs that are in a different LATA than their associated ported/pooled telephone numbers (TNs). This is resulting in cu… | Download |
| PIM 79 | 09/07/2010 | Item 1.) Url link inside BP36 which says, | Download |
| PIM 78 | 03/05/2010 | Per LNPA WG Recommendations, carriers will use the “standardized” LSR as developed by OBF for simple wireline-to-wireline and intermodal ports to support 1DP. Small carriers have until Feb. 2, 2011 … | Download |
| PIM 77 | 05/11/2010 | Porting delay problems, caused by a lack of communication/interaction between the ONSP and their OLSP (Reseller) during the data validation stage of the port, have been increasing in frequency. The … | Download |
| PIM 76 | 01/13/2010 | Inadequate notification by service providers when they make changes to their systems or processes that other service providers must use to request a customer service record or to initiate a request t… | Download |
| PIM 75 | 09/28/2009 | The LNPA-WG reached consensus on a best practice related to pass code/PIN verification (Best Practice 60). The best practice states that a provider cannot use a provider assigned pass code/PIN as val… | Download |
| PIM 74 | 01/13/2010 | Definition of the word sends in the LNP Provisioning Flows Narratives in the context of a response. | Download |
| PIM 73 | 09/08/2009 | The disconnection of the telephone number the customer would like ported creates significant delays/the inability of the NSP to port the number from the OSP. | Download |
| PIM 72 | 07/14/2009 | Requirement to provide security code/password/pin is causing significant delays in the ability of end users to port away from an existing provider because the end users do not know what the security … | Download |
| PIM 71 | 04/23/2009 | Allowing the OLSP to initiate the cancellation may cause an interruption in service and duplicate billing depending on the timing of the cancellation. | Download |
145 results returned
