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 52
Carriers are receiving blocks in which the Intra-Service Provider ports (ISPs) have not been completed by the donor provider prior to being donated to the pool. These blocks should be considered unusable due to the issues and rippling effects caused when the receiving service provider begins to assign customers out of the block.
Download the document PIM 52
-
PIM 51
Currently a carrier can open a Code (NPA-NXX) for portability in the NPAC whether or not they own the NPA-NXX.
Download the document PIM 51
-
PIM 50
A large number of wire line to wireless ports fail the automated process because they are from large accounts where the customer service record (CSR) is too large to return on a CSR query. The CSR is needed to complete an LSR.
Download the document PIM 50
-
PIM 49
Service Providers do not have clear direction in the NANC flows regarding the proper porting procedure for Type 1 numbers
Download the document PIM 49
-
PIM 48
"Both the NIIF Company Specific Contact Directory and the National LNP Contact Directory are documents used by several companies to assist in troubleshooting LNP problems as well as for general intercompany contact information. During the course of using these directories it was suggested a new category for pos-port carrier-to-carrier support was necessary. In addition, some contact information is either missing or is not current for those that have submitted information. This PIM also suggests more publicity in order to get those carriers not listed would be encouraged to do so. "
Download the document PIM 48
-
PIM 47
The intention of this PIM is to discuss minimum industry intermodal standards for purging old/abandoned ports. This issue is related to WNPO Issue 04-13- 'Purge Old Port Requests with No Response' and OBF Wireless Committee issue 2665.
Download the document PIM 47
-
PIM 46
The existing NPAC Filter Management process only allows a filter to be applied for a particular NPA-NXX if that particular NPA-NXX has previously been entered into NPAC.
Download the document PIM 46
-
PIM 45
When there are errors in local service requests to port a number some service providers only respond identifying a single error. Additional LSRs and responses are required until all errors are finally cleared. This can result in a need to create many LSRs in order to clear all errors and complete a port.
Download the document PIM 45
-
PIM 44
Wire line carriers rules for developing a local service request (LSR) in order to port a number are unique to each carrier, dynamic and complex requiring dozens of different fields. Each carrier can set their own rules and requirements for porting numbers from them. Each field may be required to match exactly to the information as it appears in validation fields for both wire line and wireless ports. Any difference, even slight, can result in a port request being rejected. The number of validation fields for wire line LSR porting process makes it very difficult and costly to port numbers from wire line carriers. Porting to these complex requirements takes a great deal of time and typically requires manual intervention, which inhibits and discourages porting and the automation of the porting process.
Download the document PIM 44
-
PIM 43
Verizon Wireless has concerns about the volume of port transactions that the NPAC can process per second when mass changes need to be made and broadcasted to the industry. Now that wireless service providers are porting throughout the United States, Verizon Wireless expects that the volume of port transactions will increase in general, and mass changes may need to be made more frequently as well.
Download the document PIM 43