Local Number Portability Administration

08/20/07

     

 

Best Practices Document

Item Number 42
Topic: Carriers taking back numbers that have been ported out because their systems do not reflect a valid FOC was sent
Date Logged 8/31/06
Date Modified  
Related Regulation / Document Ref

PIM 53 v5.doc

Related Issue  
Reported to NANC?  
Recommended Change to Requirements?  
Submitted by LNPA-WG
Decisions / Recommendations
There have been instances of carriers 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.

This PIM addresses instances where it was the intent of the end user to port to the New SP.

  • Providers should not arbitrarily port back numbers without attempting to contact and work with the New SP to resolve any disputes/issues related to the port.
  • For an activated port that is disputed by the Old SP or not recognized in the systems of the Old SP, if it is determined that it was in fact the intent of the end user to port his/her number to the New SP, both providers should work together in resolving any systems true-up issues, e.g. reissuance of any necessary LSRs, when possible, without impacting the end user’s service.
  • In the case of a double assignment, between the two end users involved, the end user with the longer continuous service with that number shall retain the number, unless otherwise agreed to by the providers involved.
  • In any case of an inadvertent port, defined here as a port where it was not the intention of the end user to port his/her number to the New SP, both providers will work together to restore the end user’s service with the Old SP as quickly as possible, regardless of the time interval between activation of the inadvertent port and discovery of the inadvertent port.

The PIM 53 Service Provider Contact file contains numbers/sites to be used by other providers to contact the applicable service provider to address PIM 53-related issues.

 

   

This site was last updated 08/20/07