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. 2009-08-03 PIM Conference Call Notes.pdf
| Title | Date | Description | Document |
|---|---|---|---|
| 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. Th... | 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... | 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 v... | 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 securit... | 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 |
| PIM 70 | 11/11/2008 | In today's version of the NANC flows, both slides 1 and 2 indicate the LSR-FOC process should be used for the processing of ALL intermodal ports (both wireless and wireline). This needs to be revis... | Download |
| PIM 69 | 10/15/2008 | The process for porting telephony service when bundled with Digital Subscriber Line (DSL) service in some cases requires the customer to contact the current service provider requesting the DSL be s... | Download |
| PIM 68 | 08/18/2008 | A carrier created a very large quantity of ISP subscription versions (aka TN ports) in their pooled 1K blocks with the same routing information carried at the block level over a short time period, ... | Download |
| PIM 67 | 05/02/2008 | The Verizon Wireless Network Repair Bureau (NRB) is experiencing a marked increase in the number of trouble tickets opened for Intercarrier SMS problems related to customers who have Ported In thei... | Download |
| PIM 66 | 08/24/2007 | Mass Updates made by NPAC do not persist any modify request data. | Download |
| PIM 65 | 08/28/2007 | In the current notification prioritization, there is no way to indicate priority levels for the notifications generated upon the disconnection of NPBs. These disconnects can potentially generate th... | Download |
| PIM 64 | 08/24/2007 | LTI initiated transactions are broadcast to the SOAs | Download |
| PIM 63 | 08/09/2007 | The issue is that some carriers are requiring that the customer have service for 30 days before they will approve a port out request. According to the FCC Mandate, a Service provider can refuse to ... | Download |
| PIM 62 | 07/05/2007 | Planned maintenance activities are a necessary part of doing business, however the length of outages impacting the ability of Service Providers to port numbers through their systems needs to be lim... | Download |
| PIM 61 | 05/25/2007 | Out-dated dial-up access to the LTI (Low Tech Interface) is producing slow and unreliable compliance with mandated FCC number porting requirements and procedures. | Download |
| PIM 60 | 03/07/2007 | Socket Telecom ("Socket") is attempting to port numbers away from a LEC to serve a customer that wishes to change its local service provider. Socket will be replacing the customer's current local e... | Download |
| PIM 59 | 11/09/2006 | Process for unlocking the 911 record. | Download |
| PIM 58 | 10/30/2006 | Some end users are unable to port their telephone numbers because the NXX code is not opened for portability in the NPAC SMS. Usually, this can be resolved by communication between the two service ... | Download |
| PIM 57 | 08/14/2006 | Attempting to port a consumer when a Reseller abruptly discontinues business and/or declares bankruptcy. | Download |
| PIM 56 | 05/03/2006 | While all carriers receive updates in their LSMS when porting customers, some carriers are not provisioning their LNP databases correctly. When this scenario occurs, customers are not able to termi... | Download |
| PIM 55 | 05/08/2006 | Intermodal porting faces a challenge in the form of a process gap between the wireless and wireline carriers after a confirmation has been received. The 2 processes are not in synch, causing fall o... | Download |
| PIM 54 | 04/28/2006 | Comcast is requesting NANC support a standard porting interval for wireline to wireline and wireline to wireless of one day based on certain criteria | Download |
| PIM 53 | 02/27/2006 | Carriers are taking back numbers that have been ported out several months or even years because their systems do not reflect a valid FOC was sent. In many cases they have not removed the number fro... | Download |
126 results returned
© 2019 iconectiv, all rights reserved
