Common use of Procedures for Providing LNP ( 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 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 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 14.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 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 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 14.2.715.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 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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 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 Customercustomer. 15.2.3 14.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 Customerend user customer. 15.2.4 14.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 14.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 14.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 14.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 14.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 14.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 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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 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 Customercustomer. 15.2.3 14.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 Customerend user customer. 15.2.4 14.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 14.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 14.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 14.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 14.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-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.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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 Customerend user customer. 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 14.2.715.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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 Customerend user customer. 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 14.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 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 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 14.2.715.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 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 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 authorization from the Customer in accordance with Applicable Law an end user customer and sends an a 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. 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 Customerend user customer. 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 14.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 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. 15.2.9 Neither Party shall charge the other Party for LNP orders.

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 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 14.2.715.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.

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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 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 Customercustomer. 15.2.3 14.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 Customerend user customer. 15.2.4 14.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 14.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 14.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 14.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 14.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 14.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 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 6.3.1 If a Customer of one Party ("Party A") A elects to become a Customer of the other Party ("Party B"). The Customer elects B and to utilize the original telephone number(s) corresponding to the Telephone Exchange Service(sservice(s) it previously received from Party A, in conjunction with the Telephone Exchange Service(sservice(s) it will now receive from Party B. After B then, upon Party B has received receiving authorization from the Customer in accordance with Applicable Law and sends sending an LSR LNP order 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 6.3.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 the Customer. 15.2.3 6.3.3 When a Customer of Customer’s number is ported between the Parties, the Parties will follow the 911 Guidelines recommended by the National Emergency Number Association (“NENA”) with regard to emergency services databases. 6.3.4 When Party A ports their telephone numbers of its Customer 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 6.3.5 NXX Codes 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 portable in accordance with FCC rules 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, regulations except as noted in 14.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 permitted 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 same FCC 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 networkregulations. 15.2.8 Both Parties’ use of 6.3.6 The Parties shall ensure that all switches, whether currently owned or hereafter acquired, are upgraded to facilitate LNP shall meet to the performance criteria specified extent required 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 LNPFCC rules and regulations.

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 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 14.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.codes 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 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 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 14.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 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 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 14.2.715.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 give n 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 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 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 14.2.715.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.

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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 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 Customercustomer. 15.2.3 14.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 Customerend user customer. 15.2.4 14.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 14.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 LERG)- assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches. 15.2.6 14.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 14.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 14.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 14.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 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.original 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 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 14.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.become 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 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 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 14.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-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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 Customer.end user customer.‌‌‌‌‌‌‌ 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 14.2.715.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”). 14.2.1 The Parties will follow the LNP provisioning process recommended by the North American Numbering Council following steps shall apply: (NANC1) 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 ; (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. After B; (3) after Party B has received authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user Customer, and sends 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. 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 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 number(s) to Party B and the Customer has previously secured a reservation of line numbers number(s) from Party A for possible activation at a future point, these reserved but inactive numbers number(s) may be ported along with the active numbers number(s) to be ported provided the numbers number(s) have been reserved for the Customer. Party B may request that Party A port all reserved numbers number(s) assigned to the Customer or that Party A port only those numbers number(s) listed by Party B. As long as Party B maintains reserved but inactive numbers number(s) ported for the Customer, Party A shall not reassign those numbersnumber(s). Party B shall not reassign the reserved numbers number(s) to another end user Customer. 15.2.4 14.2.4 When a Customer of Party A ports their telephone numbers number(s) to Party B, in the process of porting the Customer’s telephone numbersnumber(s), Party A shall implement the ten-digit unconditional trigger feature where it is available. When Party A receives the porting request, the ten-digit 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 14.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 LERG-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP-capable switches.‌‌ 14.2.6 Both Parties shall provide updates to the Local Exchange Routing Guide (LERG) at least forty-five days prior to the LNP capable switches. 15.2.6 Where LNP effective date and will identify the portable switches and NXXs. When an office is commercially availableequipped with LNP, the NXXs in the office shall be defined as portable, except as noted in 14.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 LERGswitches. 15.2.7 14.2.7 All NXXs assigned to LNP capable switches are to be designated as portable unless a NXX(s) an NXXs 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 14.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 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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 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 Customercustomer. 15.2.3 14.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 Customerend user customer. 15.2.4 14.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 14.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 14.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 14.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 14.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 14.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 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.North 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 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 14.2.715.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.and 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 recommended by the North American Numbering Council (NANCNA NC) 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 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 14.2.715.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 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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 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 Customercustomer. 15.2.3 14.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 Customerend user customer. 15.2.4 14.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 14.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.a 15.2.6 14.2.6 Where LNP is commercially available, the NXXs in the office shall be defined as portable, except as noted in 14.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 14.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 14.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 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.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 14.2.715.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 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 authorization a letter of agency (LOA) from the Customer in accordance with Applicable Law an end user customer and sends an a 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 Customerend user customer. 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 14.2.715.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-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 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 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 14.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.