Procedures for Providing LNP ( Clause Samples

The "Procedures for Providing LNP" clause outlines the specific steps and requirements that parties must follow to implement Local Number Portability (LNP) services. It typically details the process for requesting, approving, and executing the transfer of telephone numbers between service providers, including timelines, necessary documentation, and coordination protocols. By establishing clear procedures, this clause ensures a smooth and efficient transition for customers wishing to retain their phone numbers when switching providers, thereby minimizing service disruptions and disputes.
Procedures for Providing LNP (. “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. 15.2.1 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. 15.2.2 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. 15.2.3 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. 15.2.4 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. 15.2.5 The Parties shall furnish each other with the Jurisdiction Information...
View SourceView Similar (90)
Procedures for Providing LNP (. The Parties shall follow the Local Number Portability provisioning process recommended by the North American Numbering Council (“NANC”) and adopted by the FCC. In addition, the Parties agree to follow the Local Number Portability ordering procedures established at the Ordering and Billing Forum (“OBF”). 13.2.1 The Parties shall work cooperatively to port customer’s telephone number(s) using LNP. 13.2.2 When a telephone number is ported from Party A’s network using LNP, Party A shall remove any non-proprietary line-based calling cards associated with the ported number(s) from its LIDB. Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or the customer. 13.2.3 When a customer of Party A ports their telephone number(s) to Party B, in the process of porting the customer’s telephone numbers, Party A shall implement the ten-digit trigger feature where it’s available. When Party A receives the porting request, the unconditional trigger shall be applied to the customer’s line prior to the due date of the porting activity. When the ten digit unconditional trigger is not available, the Parties must coordinate the disconnect activity. 13.2.4 The Parties shall include the Jurisdictional Information Parameter (“JIP”) in the Initial Address Message (“IAM”) that contains the LERG-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches.
View SourceView Similar (21)
Procedures for Providing LNP (. The Parties will follow the long-term Number Portability provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. In addition, the Parties agree to follow the long-term Number Portability ordering procedures established at the Ordering And Billing Forum (OBF).
View SourceView Similar (8)
Procedures for Providing LNP (. (“Long-term Number Portability”) 20.2.1 The following steps shall apply: (1) a Customer of one Party ("Party A") elects to become a Customer of the other Party ("Party B"); (2) 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; (3) after Party B has received authorization from an end user Customer, and sent 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.
View SourceView Similar (3)
Procedures for Providing LNP (. “Local Number Portability”) 9.2.1 An End User of one Party (“Party A”) elects to become an End User of the other Party (“Party B”). The End User elects to utilize the original telephone number(s) corresponding to the Telephone Exchange Service(s) it currently receives from Party A, in conjunction with the Telephone Exchange Service(s) it will now receive from Party B. After Party B sends an LSR to Party A and Party A has verified the validity of received LSR, 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. It is Party B’s responsibility to comply with applicable law concerning the change of local service provider including LOA, if applicable. When a telephone number is ported out of Party A’s network, Party A will remove any information including non-proprietary line based calling card(s) and blocks (etc.) associated with the ported number(s) from its Line Information Database (“LIDB”). Establishment of any LIDB services or blocks (etc.) rests solely with Party B.
View SourceView Similar (2)
Procedures for Providing LNP (. The Parties shall follow the Local Number Portability provisioning process recommended by the North American Numbering Council (“NANC”) and adopted by the FCC. In addition, the Parties agree to follow the Local Number Portability ordering procedures established at the Ordering and Billing Forum (“OBF”). 13.2.1 The Parties shall work cooperatively to port customer’s telephone number(s) using LNP. 13.2.2 Party B will provide Party A with a Firm Order Confirmation (“FOC”) for each port order by 5:00 p.m. of the next Business Day after Party B’s receipt of that order. The FOC must contain Party B’s commitment date for order completion (“Committed Due Date”), which shall be within three (3) days after issuance of the FOC, or within a different time interval agreed upon by the Implementation Team, unless Party A requested a longer interval.
View SourceView Similar (2)
Procedures for Providing LNP (. “Local Number Portability”). The Parties will follow the LNP provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. The Parties shall provide LNP on a reciprocal basis.
View SourceView Similar (2)
Procedures for Providing LNP (. 13.2.1 The Parties shall follow the Local Number Portability provisioning process recommended by the North American Numbering Council (“NANC”) and adopted by the FCC. In addition, the Parties agree to follow the Local Number Portability ordering procedures established at the Ordering and Billing Forum (“OBF”). 13.2.1.1 The Parties shall work cooperatively to port customer’s telephone number(s) using LNP. 13.2.1.2 When a telephone number is ported from Party A’s network using LNP, Party A shall remove any non-proprietary line-based calling cards associated with the ported number(s) from its LIDB. Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or the customer. 13.2.1.3 When a customer of Party A ports their telephone number(s) to Party B, in the process of porting the customer’s telephone numbers, Party A shall implement the ten-digit trigger feature where it’s available. When Party A receives the porting request, the unconditional trigger shall be applied to the customer’s line prior to the due date of the porting activity. When the ten digit unconditional trigger is not available, the Parties must coordinate the disconnect activity. The Parties shall include the Jurisdictional Information Parameter (“JIP”) in the Initial Address Message (“IAM”) that contains the LERG-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches. The switch’s LRN software determines if the called party is in a portable NXX. If the called party is in a portable NXX, a query is launched to the LNP database to determine whether or not the called number is ported. When the called number with a portable NXX is ported, an LRN is returned to the switch that launched the query. Per industry standards, the LRN appears in the CdPN (Called Party Number) field of the SS7 message and the called number then appears in the GAP (Generic Address Parameter) field. When the called number with a portable NXX is not ported, the call is completed as in the pre-LNP environment. The FCI (Forward Call Identifier) field’s entry is changed from 0 to 1 by the switch triggering the query when a query is made, regardless of whether the called number is ported or not. The N-1 carrier (N carrier is the responsible Party for terminating call to the End User) has the responsibility to determine if a query is required, to launch the query, and to route the call to the switch or network in which the tele...
View Source
Procedures for Providing LNP (. (“Long-term Number Portability”) 20.2.1 The following steps shall apply: (1) a Customer of one Party ("Party A") elects to become a Customer of the other Party ("Party B"); (2) 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; (3) after Party B has received authorization from an end user Customer, and sent 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. 20.2.2 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. 20.2.3 When a Customer of Party A ports their telephone number(s) to Party B and the Customer has previously secured a reservation of line number(s) from Party A for possible activation at a future point, these reserved but inactive number(s) may be ported along with the active number(s) to be ported provided the number(s) have been reserved for the Customer. Reserved telephone numbers are non-working telephone numbers assigned to a specific Customer to be used at a later time. The numbers are assigned to the Customer either via Tariff or other contractual arrangement between the Customer and the service provider. Party B may request that Party A port all reserved number(s) assigned to the Customer or that Party A port only those number(s) listed by Party
View Source

Related to Procedures for Providing LNP (

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations. 15.4.1 If Party B desires to have LNP capability deployed in an End Office of Party A, which is not currently capable, Party B shall issue a LNP request to Party A. Party A will respond to the Party B, within ten (10) days of receipt of the request, with a date for which LNP will be available in the requested End Office. Party A shall proceed to provide for LNP in compliance with the procedures and timelines set forth in FCC ▇▇-▇▇▇, ▇▇▇▇▇▇▇▇▇ 80, and FCC 97-74, Paragraphs 65 through 67. 15.4.2 The Parties acknowledge that each can determine the LNP-capable End Offices of the other through the Local Exchange Routing Guide (LERG). In addition, the Parties shall make information available upon request showing their respective LNP-capable End Offices, as set forth in this Section 15.4.

  • Hiring Procedures Nothing contained in this Article 4 shall impair any of the rights of the Employer to hire new or additional employees to meet the employment needs of the Employer, in accordance with the terms and provisions of this collective bargaining Agreement or to meet the obligations of the Employer under Article 2, Section H of this Agreement or to take affirmative steps to comply with any requirements under any applicable Federal or State law prohibiting discrimination in employment.