Common use of Procedures for Providing LNP (Long-term Number Portability Clause in Contracts

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 Ordering And Billing Forum (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 a letter of agency (LOA) from an end user customer and sends a 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. It is Party B’s responsibility to maintain a file of all LOAs and Party A may request, upon reasonable notice, a copy of the LOA. 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 end user 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 Parameter (JIP) in the Initial Address Message (IAM), containing a Local Exchange Routing Guide (LERG)-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches. 15.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 15.2.7, and translations will be changed in the Parties’ switches to open those NXXs for database queries in all applicable LNP capable offices within the LATA of the given switch(es). On a prospective basis, all newly deployed switches will be equipped with LNP capability and so noted in the LERG. 15.2.7 All NXXs assigned to LNP capable switches are to be designated as portable unless a NXX(s) has otherwise been designated as non-portable. Non-portable NXXs include NXX codes assigned to paging, cellular and wireless services; codes assigned for internal testing and official use and any other NXX codes required to be designated as non-portable by the rules and regulations of the FCC. NXX codes assigned to mass calling on a choked network may not be ported using LNP technology but are portable using methods established by the NANC and adopted by the FCC. On a prospective basis, newly assigned codes in switches capable of porting shall become commercially available for porting with the effective date in the network. 15.2.8 Both Parties’ use of LNP shall meet the performance criteria specified by the FCC. Both Parties will act as the default carrier for the other Party in the event that either Party is unable to perform the routing necessary for LNP.

Procedures for Providing LNP (Long-term Number Portability. The Parties will follow the LNP provisioning process and procedures recommended by the North American Numbering Council (NANC) and adopted by the FCC, as well as those established by the East Coast Local Number Portability Operations Team. In addition, the Parties agree to follow the LNP NP ordering procedures established at the Ordering And and Billing Forum (OBF). The Parties shall provide LNP on a reciprocal basis. 15.2.1 14.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 a letter of agency (LOA) appropriate authorization in accordance with Applicable Law from an end user customer and sends a 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. It is Party B’s responsibility to maintain a file of all LOAs such authorizations and Party A may request, upon reasonable notice, a copy verification of the LOAapplicable authorization. 15.2.2 14.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 14.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 end user customer. 15.2.4 14.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 ten10-digit unconditional trigger feature where it is available. When Party A receives the porting request, the 10-digit unconditional trigger shall be applied to the customer’s line before no later than 11:59 p.m. (local time) on the due business day preceding the scheduled port date and Party A shall leave the 10-digit unconditional trigger in place until 11:59 p.m. (local time) of the confirmed due date. Such use of the 10-digit unconditional trigger is considered a non-coordinated number port and will enable Party B to satisfy its customers’ requests for weekend or off-business hours porting activity. without coordinated assistance from Party A. 14.2.5 When the ten10-digit unconditional trigger is not available, Party A and Party B must coordinate the disconnect activity. For the purposes of such coordination and in response to a specific Customer request for special handling where issues of public safety are involved, either Party may request weekend or off-business hour coordination of LNP. In such instances and subject to the limitations identified in Subsection 14.2.5.1 below, either Party, as applicable, will process LNP orders, port numbers during off-business hours on weekdays, Saturdays, and Sundays, and provide off-business hours technical and operational support to resolve problems that may occur during such coordinated number porting activity as it would do so for its own Customers that are similarly situated. 15.2.5 14.2.5.1 The availability of weekend and/or off-business hours coordination of LNP is subject to each of the following limitations: (i) Weekend and/or off-business hour porting will only be considered on orders that require coordination, i.e., where no 10-digit unconditional trigger is available. (ii) Requests for weekend and non-business hour due dates on number portability orders must be negotiated in advance of submitting the LSR. (iii) Both Parties shall maintain personnel to perform the tasks required during the weekend and off-business hour porting to which they agree, including the removal of the telephone number translations at a specified time and restoration of original service if the problems occur during the porting process. (iv) Number porting may not be available certain hours on Sundays due to NPAC maintenance down time as reported by NPAC. (v) If either Party schedules system maintenance during off-business hours that impacts the ability to complete the work involved for a scheduled porting event, such Party will advise the other of the system down time and reschedule the porting activity to a mutually agreeable date. 14.2.6 The Parties shall furnish each other with the Jurisdiction Information Parameter (JIP) in the Initial Address Message (IAM), containing a Local Exchange Routing Guide (LERG)-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches. 15.2.6 14.2.7 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 15.2.714.2.8, and translations will be changed in the Parties’ switches to open those NXXs for database queries in all applicable LNP capable offices within the LATA of the given switch(es). On a prospective basis, all newly deployed switches will be equipped with LNP capability and so noted in the LERG. 15.2.7 14.2.8 All NXXs assigned to LNP capable switches are to be designated as portable unless a NXX(s) has otherwise been designated as non-portable. Non-portable NXXs include NXX codes assigned to paging, cellular and wireless services; codes assigned for internal testing and official use and any other NXX codes required to be designated as non-portable by the rules and regulations of the FCC. NXX codes assigned to mass calling on a choked network may not be ported using LNP technology but are portable using methods established by the NANC and adopted by the FCC. On a prospective basis, newly assigned codes in switches capable of porting shall become commercially available for porting with the effective date in the network. 15.2.8 14.2.9 Both Parties’ use of LNP shall meet the performance criteria specified by the FCC. Both Parties will act as the default carrier for the other Party in the event that either Party is unable to perform the routing necessary for LNP. 14.2.10 TCG and Verizon may mutually agree to additional or different terms for the use of the LRN 10-digit unconditional trigger.

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 Ordering And Billing Forum (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 a letter of agency (LOA) authorization from an end user customer the Customer in accordance with Applicable Law and sends a an LSR to Party A, Parties A and B will work together to port the customerCustomer’s telephone number(s) from Party A’s network to Party B’s network. It is Party B’s responsibility to maintain a file of all LOAs and Party A may request, upon reasonable notice, a copy of the LOA. 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 customerCustomer. 15.2.3 When a customer Customer of Party A ports their telephone numbers to Party B and the customer 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 customerCustomer. Party B may request that Party A port all reserved numbers assigned to the customer 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 customerCustomer, Party A shall not reassign those numbers. Party B shall not reassign the reserved numbers to another end user customerCustomer. 15.2.4 When a customer Customer of Party A ports their telephone numbers to Party B, in the process of porting the customerCustomer’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 customerCustomer’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 Parameter (JIP) in the Initial Address Message (IAM), containing a Local Exchange Routing Guide (LERG)-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches. 15.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 15.2.7, and translations will be changed in the Parties’ switches to open those NXXs for database queries in all applicable LNP capable offices within the LATA of the given switch(es). On a prospective basis, all newly deployed switches will be equipped with LNP capability and so noted in the LERG. 15.2.7 All NXXs assigned to LNP capable switches are to be designated as portable unless a NXX(s) has otherwise been designated as non-non- portable. Non-portable NXXs include NXX codes assigned to paging, cellular and wireless services; codes assigned for internal testing and official use and any other NXX codes required to be designated as non-portable by the rules and regulations of the FCC. NXX codes assigned to mass calling on a choked network may not be ported using LNP technology but are portable using methods established by the NANC and adopted by the FCC. On a prospective basis, newly assigned codes in switches capable of porting shall become commercially available for porting with the effective date in the network. 15.2.8 Both Parties’ use of LNP shall meet the performance criteria specified by the FCC. Both Parties will act as the default carrier for the other Party in the event that either Party is unable to perform the routing necessary for LNP.