Long Term Number Portability. (“LNP”). The Parties agree to provide LNP on a reciprocal basis using Location Routing Number (LRN) as the means to port and route calls to ported numbers in accordance with the FCC and Commission guidelines applicable to LNP.
Long Term Number Portability. (“LNP”).
XIII.9.1 The Parties shall migrate existing methods of providing INP to LNP as soon as practically possible but no later than the date provided for by the FCC or Commission. Once LNP is available on a given MSA, neither Party shall be required to provide INP in that MSA.
XIII.9.2 In addition to those MSAs in which LNP is required, beginning January 1, 1999, Requesting Carrier may request that Ameritech offer LNP at any Central Office in the Ameritech region. Requesting Carrier may request LNP in a non-LNP Central Office through either the Bona Fide Request process or, if Requesting Carrier places an order for Local Number Portability in an non-LNP Central Office, placement of such order shall be deemed a request by Requesting Carrier for Ameritech to implement LNP in that Central Office.
XIII.9.3 The Parties agree to provide LNP in accordance with rules and regulations as from time to time prescribed by the FCC and/or the Commission and the terms and conditions set forth in their respective effective tariff(s).
XIII.9.4 Party A may cancel all line-based calling cards and shall delete all LIDB listings for ported numbers.
XIII.9.5 Requesting Carrier shall use the Provisioning EI to submit orders for LNP to Ameritech. Ameritech’s obligation to process Requesting Carrier’s Non-Electronic Orders for LNP, and the rates, terms and conditions applicable to such orders, shall be as described in Section 10.13.2
Long Term Number Portability. The Parties will follow the LNP provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. In addition, the Parties agree to follow the LNP ordering procedures established at the OBF. The Parties shall provide LNP on a reciprocal basis. A Customer of one Party ("Party A") elects to become a Customer of the other Party ("Party B"). The Customer elects to utilize the original telephone number(s) corresponding to the Telephone Exchange Service(s) it previously received from Party A, in conjunction with the Telephone Exchange Service(s) it will now receive from Party B. After Party B has received authorization from the Customer in accordance with Applicable Law and sends an LSR to Party A, Parties A and B will work together to port the Customer's telephone number(s) from Party A's network to Party B's network. When a telephone number is ported out of Party A's network, Party A will remove any non-proprietary line based calling card(s) associated with the ported number(s) from its Line Information Database (LIDB). Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or Party B's Customer. When a Customer of Party A ports their telephone numbers to Party B and the Customer has previously secured a reservation of line numbers from Party A for possible activation at a future point, these reserved but inactive numbers may be ported along with the active numbers to be ported provided the numbers have been reserved for the Customer. Party B may request that Party A port all reserved numbers assigned to the Customer or that Party A port only those numbers listed by Party B. As long as Party B maintains reserved but inactive numbers ported for the Customer, Party A shall not reassign those numbers. Party B shall not reassign the reserved numbers to another Customer. When a Customer of Party A ports their telephone numbers to Party B, in the process of porting the Customer's telephone numbers, Party A shall implement the ten-digit trigger feature where it is available. When Party A receives the porting request, the unconditional trigger shall be applied to the Customer's line before the due date of the porting activity. When the ten-digit unconditional trigger is not available, Party A and Party B must coordinate the disconnect activity. The Parties shall furnish each other with the Jurisdiction Information Parameter (JIP) in the Initial Address Message (IAM), containing a ...
