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 62

    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 limited to a maximum of 60 consecutive hours. Additionally, Trading Partners should provide 30 days notice of planned porting outages. If 30 days is not possible, a minimum of 14 days notice should be provided.

    Download the document PIM 62

  • PIM 61

    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 the document PIM 61

  • PIM 60

    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 exchange service with a tariffed Out of Calling Scope Service (either Remote Call Forward or Foreign Exchange Service) in conjunction with Socket's local exchange service. The LEC that is currently serving the customer is refusing to port the number on the grounds that the definition of number portability as defined in Section 147 U.S.C. 151 (30) is specifically defined as excluding attempts to change the serving location of the customer. The LEC is calling this "location portability" and is taking the position that it has no obligation to port a number if the customer's service location will change as a result of the number port.

    Download the document PIM 60

  • PIM 59

    Process for unlocking the 911 record.

    There is a problem in identifying a solidified process for unlocking the 911 record for VoIP carriers.

    Download the document PIM 59

  • PIM 58

    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 providers. However, in some cases the old service provider (OSP) contacts are not available, or the OSP refuses to make the code portable.

    Download the document PIM 58

  • PIM 57

    Attempting to port a consumer when a Reseller abruptly discontinues business and/or declares bankruptcy.

    Download the document PIM 57

  • PIM 56

    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 terminate or receive calls from those carrier's networks that did not provision their LNP databases.

    Download the document PIM 56

  • PIM 55

    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 out and delays.

    Download the document PIM 55

  • PIM 54

    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 the document PIM 54

  • PIM 53

    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 from their number inventory and they have re-assigned the TN to another customer.

    Download the document PIM 53