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 32
Wireless carriers are not receiving customer service records (CSRs) from all wire line network service providers when a reseller is the local service provider. Wireless port requests do not collect the needed information to complete a wire line local service request (LSR). The CSR is a primary source of information needed to complete the LSR and port the number.
Download the document PIM 32
-
PIM 31
"Wireless cannot process ""Jeopardizes"" following confirms from wireline service providers when they are not able to meet the original due date and time."
Download the document PIM 31
-
PIM 30
There is differing interpretation of N-1 Number Portability Querying responsibilities, and whether wireless carriers are obligated to perform default NP Queries when the N-1 carrier fails to dip the call.
Download the document PIM 30
-
PIM 29
Due to inconsistent inter-modal processes some customers are experiencing loss of service between disconnects and activations.
Download the document PIM 29
-
PIM 28
When porting between wireless and wireline there is an interface difference between WPRR (wireless) and FOC (wireline). FOC allows for a due date and time change on confirms. WPRR does not allow a due date and time change on confirms. When wireline send a FOC with DDT change on a confirm the wireless carrier's cannot process the change and does not allow port to complete.
Download the document PIM 28
-
PIM 27
There is no way to get an SV out of Cancel Pending status other than waiting out the timers. The timers could take up to 24 business hours (two 9-hour Cancel Pending timers plus 6-hour Conflict timer --9+9+6=24 business hours).
Download the document PIM 27
-
PIM 26
The NPAC Testbed hardware platform does not reflect a production environment to support volume performance tests.
Download the document PIM 26
-
PIM 25
Will retailers have access to the porting database to determine which carriers/markets customers can port into and out of?
Download the document PIM 25
-
PIM 24
"Blocks that are being assigned to Service Providers are either contaminated when they are donated as a non-contaminated block or the blocks have been contaminated over 10%. This is causing customers to be out of service or blocks being exchanged for a less contaminated or non-contaminated block. In addition when the PA has assigned a block, at times the block is being rejected in the NPAC for not having the NXX as opened in the NPAC as portable. "
Download the document PIM 24
-
PIM 23
The LRNs, NXX data, and NXX-X data and effective dates of the data in the NPAC are not always in synch with those in the Telcordia Business Integrated Routing and Rating Database System (BIRRDS).
Download the document PIM 23