Common use of Other Interim Portability Provisions Clause in Contracts

Other Interim Portability Provisions. 13.7.1 Party B shall become the Customer of Record for the original Party A’s telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( “EMR”) containing detailed records associated with the calls reflected on the billing statement. 13.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBT's data for its Customers. CBT shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedule. 13.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- service time. 13.7.5 The Parties will provide SS7 functionalities ( e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 When any INP method is used for Intermedia Customers, both the ported numbers and shadow numbers shall be stored in the 911/ALI database, to the extent that the database is capable of storing both numbers. Intermedia shall have the right to verify the accuracy of its information in the 911/ALI databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT shall make available to Intermedia Customers the same 9 -1-1 capabilities as CBT makes available to its Customers. 13.7.7 When any INP method is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant to a separate agreement between CBT and Intermedia. 13.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.

Other Interim Portability Provisions. 13.7.1 Party B shall become the Customer of Record for the original Party A’s telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- to-third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( (“EMR”) containing detailed records associated with the calls reflected on the billing statement. 13.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBT's data for its Customers. CBT shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedule. 13.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( (e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- of-service time. 13.7.5 The Parties will provide SS7 functionalities ( (e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 When any INP method is used for Intermedia ICG Customers, both the ported numbers and shadow numbers shall be stored in the 911/ALI database, to the extent that the database is capable of storing both numbers. Intermedia ICG shall have the right to verify the accuracy of its information in the 911/ALI databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT shall make available to Intermedia ICG Customers the same 9 -19-1-1 capabilities as CBT makes available to its Customers. 13.7.7 When any INP method is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant to a separate agreement between CBT and IntermediaICG. 13.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( (e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.

Other Interim Portability Provisions. 13.7.1 XIII.7.1 Party B shall become the Customer of Record for the original Party A’s 's telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- to-third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( “("EMR”") containing detailed records associated with the calls reflected on the billing statement, as generated by the Ameritech Electronic Billing System ("AEBS"). 13.7.2 XIII.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT Ameritech will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBTAmeritech's data for its Customers. CBT Ameritech shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedulewithout charge. 13.7.3 XIII.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( (e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 XIII.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- service time. 13.7.5 The Parties XIII.7.5 Ameritech will provide SS7 functionalities ( (e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 XIII.7.6 When any INP method RCF is used for Intermedia 21st Century Customers, both the ported numbers and shadow RCF numbers shall be stored in the 911/ALI PSAP database, to the extent that the database is capable of storing both numbers. Intermedia 21st Century shall have the right to verify the accuracy of its information in the 911/ALI PSAP databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT Ameritech shall make available to Intermedia 21st Century Customers the same 9 -19-1-1 capabilities as CBT Ameritech makes available to its Customers. 13.7.7 XIII.7.7 When any INP method RCF is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant provider. If Party B has not blocked outclear call, Party A must provide call records (e.g. third-party call collect or calling card calls) to 21st Century for billing and collection from the Customer. Party A shall send a separate agreement between CBT and IntermediaCARE transaction to notify the appropriate IXC that access is no longer provided by Party A for that number. 13.7.8 XIII.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( (e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.

Other Interim Portability Provisions. 13.7.1 Party B shall become the Customer of Record for the original Party A’s telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- to-third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( (“EMR”) containing detailed records associated with the calls reflected on the billing statement. 13.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBT's data for its Customers. CBT shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedule. 13.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( (e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- of-service time. 13.7.5 The Parties will provide SS7 functionalities ( (e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 When any INP method is used for Intermedia Adelphia Customers, both the ported numbers and shadow numbers shall be stored in the 911/ALI database, to the extent that the database is capable of storing both numbers. Intermedia Xxxxxxxx shall have the right to verify the accuracy of its information in the 911/ALI databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT shall make available to Intermedia Adelphia Customers the same 9 -19-1-1 capabilities as CBT makes available to its Customers. 13.7.7 When any INP method is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant to a separate agreement between CBT and IntermediaAdelphia. 13.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( (e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.

Other Interim Portability Provisions. 13.7.1 Party B shall become the Customer of Record for the original Party A’s =s telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- to-third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( “EMR”(AEMR@) containing detailed records associated with the calls reflected on the billing statement. 13.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBT's data for its Customers. CBT shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedule. 13.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( (e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- of-service time. 13.7.5 The Parties will provide SS7 functionalities ( (e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 When any INP method is used for Intermedia Sprint Customers, both the ported numbers and shadow numbers shall be stored in the 911/ALI database, to the extent that the database is capable of storing both numbers. Intermedia Sprint shall have the right to verify the accuracy of its information in the 911/ALI databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT shall make available to Intermedia Sprint Customers the same 9 -19-1-1 capabilities as CBT makes available to its Customers. 13.7.7 When any INP method is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant to a separate agreement between CBT and IntermediaSprint. 13.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( (e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.

Other Interim Portability Provisions. 13.7.1 Party B shall become the Customer of Record for the original Party A’s telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- to-third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( (“EMR”) containing detailed records associated with the calls reflected on the billing statement. 13.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBT's data for its Customers. CBT shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedule. 13.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( (e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- of-service time. 13.7.5 The Parties will provide SS7 functionalities ( (e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 When any INP method is used for Intermedia Customers, both the ported numbers and shadow numbers shall be stored in the 911/ALI database, to the extent that the database is capable of storing both numbers. Intermedia shall have the right to verify the accuracy of its information in the 911/ALI databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT shall make available to Intermedia Customers the same 9 -19-1-1 capabilities as CBT makes available to its Customers. 13.7.7 When any INP method is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant to a separate agreement between CBT and Intermedia. 13.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.

Other Interim Portability Provisions. 13.7.1 Party B shall become the Customer of Record for the original Party A’s =s telephone number(s), subject to the RCF or DID or other applicable arrangements that are provided pursuant to a Bona Fide Request. Party A shall use its reasonable efforts to provide Party B with a consolidated billing statement for all collect and billed-to- to-third-number calls associated with those numbers, with sub-account detail by retained number. Such billing statement shall be delivered in a mutually agreed format via either paper, Electronic File Transfer, daily magnetic tape or monthly magnetic tape. Party A shall provide to Party B the Exchange Message Record ( “EMR”(A EMR@ ) containing detailed records associated with the calls reflected on the billing statement. 13.7.2 Unless otherwise mutually agreed to in the Implementation Plan, Party A may cancel line-based calling cards and shall, as directed by Party B, update its LIDB listings for retained numbers, subject to RCF or DID. CBT will include billing number information associated with numbers used for INP arrangements from its network in its LIDB and will store and administer such data in the same manner as CBT's data for its Customers. CBT shall provide responses to on-line queries to the stored information for the purpose of calling card validation, fraud control and billed numbers screening at the rates shown in the Pricing Schedule. 13.7.3 If a Customer elects to move its Telephone Exchange Service back to Party A during the continuance of the RCF or DID arrangement, Party A shall notify Party B of the Customer's termination of service with Party B and the Customer's instructions regarding its telephone number(s) within two (2) Business Days of receiving notification from the Customer. Subject to procedures generally performed by Party A for potential new Customers ( (e.g., credit checks, receipts of deposit), Party A shall reinstate service to the Customer, cancel the RCF or DID or other applicable arrangement currently being provisioned, or redirect the RCF or DID or other applicable arrangement pursuant to the Customer's instructions at that time. 13.7.4 At the time a Party requests RCF or DID, the other Party shall disclose to the other requesting Party any technical or capacity limitations that would prevent use of a requested INP implementation in a particular switching office. Both Parties shall cooperate in the process of porting numbers to minimize Customer out-of- of-service time. 13.7.5 The Parties will provide SS7 functionalities ( (e.g., TCAP messages for CLASS Features) where such functionalities are available and it is technically feasible to provide such functionalities in conjunction with Interim Number Portability. Nothing in this Section 13.7.5 shall require a Party to develop new capabilities to support TCAP messages for Interim Number Portability. 13.7.6 When any INP method is used for Intermedia Sprint Customers, both the ported numbers and shadow numbers shall be stored in the 911/ALI database, to the extent that the database is capable of storing both numbers. Intermedia Sprint shall have the right to verify the accuracy of its information in the 911/ALI databases. To the extent technically feasible, and subject to the other terms and conditions of this Article XIII, CBT shall make available to Intermedia Sprint Customers the same 9 -19-1-1 capabilities as CBT makes available to its Customers. 13.7.7 When any INP method is used to port a Customer, the donor provider must maintain the Line Information Database (LIDB) record for that number to reflect appropriate conditions as reported to it by the porting service provider pursuant to a separate agreement between CBT and IntermediaSprint. 13.7.8 Neither Party shall be required to provide Number Portability for non-geographic services ( (e.g., 500 and 900 NPAs, 976 NXX number services and coin telephone numbers) under this Agreement. 13.7.9 Party A shall send a CARE 2231 transaction to notify the appropriate IXC that access is no longer provided by Party A for that number.