Problems and Issues Management
In late 1999, the LNPA WG, now known as the Number Portability Industry Forum (NPIF), established a "Problem Identification and Management" (PIM) process for Number Portability (np) issues. The group, made up of Number Portability Industry members, developed:
- Issue submittal guidelines (PIM Process Scope)
- Issue submittal form (Problem/Issue Identification and Description Form)
- Issue referral form (Problem/Issue Referral Cover Letter)
- Process flows (PIM Process Flow Narratives and PIM Process Flow Graphics)
- Tracking mechanism (PIMs Tracking Matrix)
The NPIF is not responsible for resolving all Number Portability 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 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.
|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 du…
|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…
|The NPAC Testbed hardware platform does not reflect a production environment to support volume performance tests.
|Will retailers have access to the porting database to determine which carriers/markets customers can port into and out of?
|"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…
|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).
|Customers have been taken out of service inadvertently in some cases when the New Service Provider continues with a port, that has been placed into Conflict by the Old Service Provider, after the 6 h…
|Ported-In TN records left behind in NPAC Database and in SPs Network after some SPs seize to provide Service (e.g., Bankruptcy). This will result in incomplete calls.
|Porting after a code is returned from a carrier going out of business and scheduled for disconnect.
|We have noticed there are a lot of Intra-provider ports from a pooling block to the same SPID and LRN.
|The NANC flows and narratives for Local Number Portability need to be updated to accommodate wireless resellers and the different timeframes and business model for wireless service providers.
|Some carriers offer both wireless and wireline services. With the integration of the wireless industry into Local Number Portability, there needs to be an efficient way for other carriers to determi…
|Erroneous Local Exchange Routing Guide (LERG) Updates:
|In order to change the NXX code “ownership” from one service provider to another in NPAC, any active ported numbers within that code must be deleted before the ownership change can be performed. Thi…
|When an NXX code containing ported telephone numbers is disconnected in the network, calls placed to those ported subscribers fail immediately before an LNP query can be performed in order to route o…
|OSP removes switch translations on or near due date, and the number has not been ported to the new Service Provider.
|Some Operator Service functions will not be properly applied in a Wireless Number Portability environment.
|A process for moving 1k blocks between switches, within the same company, within the same rate center using EDR functionality is needed to satisfy the FCC's requirement to manage TN inventory by rate…
|The lack of standards regarding the routing and charging of calls to ported numbers is causing the CLECs to assign an inordinate number of LRNs to each switch site.
|LNP calls failing resulting in trouble tickets.
|Telephone numbers get ported from a specific JIP with the incorrect LRN which route customer to wrong receiving office.
|There are continuing issues involving the on-going effects on a region of a Service Provider’s association to NPAC being down. This can, in some instances, cripple the entire region.
|The process of updating 9-1-1 Address Location Identification (ALI) databases, due to Local Number Portability (LNP), should be done utilizing the unlock/migrate process found in the NENA LNP standar…
|There are certain instances where customer lines are ported in error i.e. “Inadvertent Porting”. There are several circumstances under which this may occur.
|Need details for how working packet service affects number ranges in context for number pooling.