Common use of Technical Requirements Clause in Contracts

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLI, BellSouth shall provide PLI with a list of the customer data items, which PLI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI data to the LIDB shall be solely at the direction of PLI. Such direction from PLI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI customer records will be missing from LIDB, as measured by PLI audits. BellSouth will audit PLI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI within one (1) business day of audit. Once reconciled records are received back from PLI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI in writing. 7.3.2.13 BellSouth shall provide PLI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI the screening information associated with LIDB Data Screening of PLI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI US LEC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 13.4.2.1 BellSouth shall process PLIUS LEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI US LEC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 13.4.2.2 Within two (2) weeks after a request by PLIUS LEC, BellSouth shall provide PLI US LEC with a list of the customer data items, items which PLI US LEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 13.4.2.6 All additions, updates and deletions of PLI US LEC data to the LIDB shall be solely at the direction of PLIUS LEC. Such direction from PLI US LEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇US LEC data upon US LEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI US LEC customer records will be missing from LIDB, as measured by PLI US LEC audits. BellSouth will audit PLI US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated PLI US LEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to PLI US LEC within one (1) business day of audit. Once reconciled records are received back from PLIUS LEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI US LEC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of PLIUS LEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 13.4.2.10 BellSouth shall provide PLI US LEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI US LEC and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of PLI US LEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI US LEC in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide PLI US LEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI US LEC the screening information associated with LIDB Data Screening of PLI US LEC data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI US LEC under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119. 7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with PLI US LEC customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI AFN any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIAFN’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI AFN what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIAFN, BellSouth shall provide PLI AFN with a list of the customer data items, which PLI AFN would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI AFN data to the LIDB shall be solely at the direction of PLIAFN. Such direction from PLI AFN will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇AFN data upon AFN’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI AFN customer records will be missing from LIDB, as measured by PLI AFN audits. BellSouth will audit PLI AFN records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI AFN contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI AFN within one (1) business day of audit. Once reconciled records are received back from PLIAFN, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI AFN to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIAFN’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI AFN with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI AFN and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI AFN data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI AFN in writing. 7.3.2.13 BellSouth shall provide PLI AFN performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI AFN the screening information associated with LIDB Data Screening of PLI AFN data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI AFN under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI AFN customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI <customer_short_name> any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLI<customer_short_name>’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI <customer_short_name> what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLI<customer_short_name>, BellSouth shall provide PLI <customer_short_name> with a list of the customer data items, which PLI <customer_short_name> would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI <customer_short_name> data to the LIDB shall be solely at the direction of PLI<customer_short_name>. Such direction from PLI <customer_short_name> will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇<customer_short_name> data upon <customer_short_name>’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI <customer_short_name> customer records will be missing from LIDB, as measured by PLI <customer_short_name> audits. BellSouth will audit PLI <customer_short_name> records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI <customer_short_name> contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI <customer_short_name> within one (1) business day of audit. Once reconciled records are received back from PLI<customer_short_name>, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI <customer_short_name> to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI<customer_short_name>’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI <customer_short_name> with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI <customer_short_name> and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI <customer_short_name> data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI <customer_short_name> in writing. 7.3.2.13 BellSouth shall provide PLI <customer_short_name> performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI <customer_short_name> the screening information associated with LIDB Data Screening of PLI <customer_short_name> data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI <customer_short_name> under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI <customer_short_name> customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI ITC^DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIITC^DeltaCom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ITC^DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIITC^DeltaCom, BellSouth shall provide PLI ITC^DeltaCom with a list of the customer data items, which PLI ITC^DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI ITC^DeltaCom data to the LIDB shall be solely at the direction of PLIITC^DeltaCom. Such direction from PLI ITC^DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇ITC^DeltaCom data upon ITC^DeltaCom’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one (1) hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ITC^DeltaCom customer records will be missing from LIDB, as measured by PLI ITC^DeltaCom audits. BellSouth will audit PLI ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI ITC^DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from PLIITC^DeltaCom, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI ITC^DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIITC^DeltaCom’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI ITC^DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI ITC^DeltaCom and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI ITC^DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI ITC^DeltaCom in writing. 7.3.2.13 BellSouth shall provide PLI ITC^DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ITC^DeltaCom the screening information associated with LIDB Data Screening of PLI ITC^DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ITC^DeltaCom under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI ITC^DeltaCom customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI MRC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIMRC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI MRC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIMRC, BellSouth shall provide PLI MRC with a list of the customer data items, which PLI MRC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI MRC data to the LIDB shall be solely at the direction of PLIMRC. Such direction from PLI MRC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇MRC data upon MRC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI MRC customer records will be missing from LIDB, as measured by PLI MRC audits. BellSouth will audit PLI MRC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI MRC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI MRC within one (1) business day of audit. Once reconciled records are received back from PLIMRC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI MRC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIMRC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI MRC with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI MRC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI MRC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI MRC in writing. 7.3.2.13 BellSouth shall provide PLI MRC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI MRC the screening information associated with LIDB Data Screening of PLI MRC data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI MRC customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI ITC^DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 15.4.2.1 BellSouth shall process PLIITC^DeltaCom’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ITC^DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 15.4.2.2 Within two (2) weeks after a request by PLIITC^DeltaCom, BellSouth shall provide PLI ITC^DeltaCom with a list of the customer data items, items which PLI ITC^DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 15.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 15.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 15.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 15.4.2.6 All additions, updates and deletions of PLI ITC^DeltaCom data to the LIDB shall be solely at the direction of PLIITC^DeltaCom. Such direction from PLI ITC^DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 15.4.2.7 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇ITC^DeltaCom data upon ITC^DeltaCom’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 15.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ITC^DeltaCom customer records will be missing from LIDB, as measured by PLI ITC^DeltaCom audits. BellSouth will audit PLI ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated PLI ITC^DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to PLI ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from PLIITC^DeltaCom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more 4 States Attachment 2 Clean 12-17-01 than 500 records are received, BellSouth will contact PLI ITC^DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 15.4.2.9 BellSouth shall perform backup and recovery of all of PLIITC^DeltaCom’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 15.4.2.10 BellSouth shall provide PLI ITC^DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI ITC^DeltaCom and BellSouth. 7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of PLI ITC^DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI ITC^DeltaCom in writing. 7.3.2.13 15.4.2.12 BellSouth shall provide PLI ITC^DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ITC^DeltaCom the screening information associated with LIDB Data Screening of PLI ITC^DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ITC^DeltaCom under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119. 7.3.2.14 15.4.2.13 BellSouth shall accept queries to LIDB associated with PLI ITC^DeltaCom customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 15.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 15.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI ▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLI▇▇▇.▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ▇▇▇.▇▇▇ what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLI▇▇▇.▇▇▇, BellSouth shall provide PLI ▇▇▇.▇▇▇ with a list of the customer data items, which PLI ▇▇▇.▇▇▇ would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI ▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of PLI▇▇▇.▇▇▇. Such direction from PLI ▇▇▇.▇▇▇ will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇.▇▇▇ data upon ▇▇▇▇ ▇▇▇▇ .▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by PLI ▇▇▇.▇▇▇ audits. BellSouth will audit PLI ▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI ▇▇▇.▇▇▇ contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI ▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from PLI▇▇▇.▇▇▇, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI ▇▇▇.▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLI▇▇▇.▇▇▇’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI ▇▇▇.▇▇▇ with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI ▇▇▇.▇▇▇ and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI ▇▇▇.▇▇▇ data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI ▇▇▇.▇▇▇ in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI ▇▇▇.▇▇▇ performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ▇▇▇.▇▇▇ at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ▇▇▇.▇▇▇ the screening information associated with LIDB Data Screening of PLI ▇▇▇.▇▇▇ data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ▇▇▇.▇▇▇ under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI ▇▇▇.▇▇▇ customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI FPB any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIFPB’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI FPB what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIFPB, BellSouth shall provide PLI FPB with a list of the customer data items, which PLI FPB would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI FPB data to the LIDB shall be solely at the direction of PLIFPB. Such direction from PLI FPB will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇FPB data upon FPB’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI FPB customer records will be missing from LIDB, as measured by PLI FPB audits. BellSouth will audit PLI FPB records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI FPB contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI FPB within one (1) business day of audit. Once reconciled records are received back from PLIFPB, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI FPB to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIFPB’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI FPB with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI FPB and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI FPB data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI FPB in writing. 7.3.2.13 BellSouth shall provide PLI FPB performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI FPB at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI FPB the screening information associated with LIDB Data Screening of PLI FPB data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI FPB under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI FPB customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI CCI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CCI what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLICCI, BellSouth shall provide PLI CCI with a list of the customer data items, which PLI CCI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI CCI data to the LIDB shall be solely at the direction of PLICCI. Such direction from PLI CCI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CCI data upon CCI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CCI customer records will be missing from LIDB, as measured by PLI CCI audits. BellSouth will audit PLI CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI CCI within one (1) business day of audit. Once reconciled records are received back from PLICCI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI CCI to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICCI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI CCI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI CCI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI CCI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI CCI in writing. 7.3.2.13 BellSouth shall provide PLI CCI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CCI the screening information associated with LIDB Data Screening of PLI CCI data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CCI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI CCI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 1.2.1 BellSouth also will offer to PLI CLEC any additional capabilities that are developed for LIDB LIBD during the life of this Agreement. 7.3.2.2 1.2.2 BellSouth shall process PLICLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CLEC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 1.2.3 Within two (2) weeks after a request by PLICLEC, BellSouth shall provide PLI CLEC with a list of the customer data items, items which PLI CLEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 1.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 1.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 1.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year.year.‌‌‌‌‌‌‌ 7.3.2.7 1.2.7 All additions, updates and deletions of PLI CLEC data to the LIDB shall be solely at the direction of PLICLEC. Such direction from PLI CLEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation). 7.3.2.8 1.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CLEC data upon CLEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 1.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CLEC customer records will be missing from LIDB, as measured by PLI CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated PLI CLEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to PLI CLEC within one (1) business day of audit. Once reconciled records are received back from PLICLEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI CLEC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 1.2.10 BellSouth shall perform backup and recovery of all of PLICLEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 1.2.11 BellSouth shall provide PLI CLEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI CLEC and BellSouth. 7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of PLI CLEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI CLEC in writing. 7.3.2.13 1.2.13.1 BellSouth shall provide PLI CLEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CLEC the screening information associated with LIDB Data Screening of PLI CLEC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CLEC under the BFR/NBR Process as set forth in Attachment 11.Bona Fide Request process.‌‌‌‌‌‌‌ 7.3.2.14 1.2.14 BellSouth shall accept queries to LIDB associated with PLI CLEC customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 1.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.within

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLILevel 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Level 3 what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLILevel 3, BellSouth shall provide PLI Level 3 with a list of the customer data items, which PLI Level 3 would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Level 3 data to the LIDB shall be solely at the direction of PLILevel 3. Such direction from PLI Level 3 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Level 3 data upon Level 3’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Level 3 customer records will be missing from LIDB, as measured by PLI Level 3 audits. BellSouth will audit PLI Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Level 3 within one (1) business day of audit. Once reconciled records are received back from PLILevel 3, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI Level 3 to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLILevel 3’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Level 3 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Level 3 and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Level 3 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Level 3 in writing. 7.3.2.13 BellSouth shall provide PLI Level 3 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Level 3 the screening information associated with LIDB Data Screening of PLI Level 3 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Level 3 under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Level 3 customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Unity Acquisition any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIUnity Acquisition’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Unity Acquisition what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIUnity Acquisition, BellSouth shall provide PLI Unity Acquisition with a list of the customer data items, which PLI Unity Acquisition would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Unity Acquisition data to the LIDB shall be solely at the direction of PLIUnity Acquisition. Such direction from PLI Unity Acquisition will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Unity Acquisition data upon Unity Acquisition’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Unity Acquisition customer records will be missing from LIDB, as measured by PLI Unity Acquisition audits. BellSouth will audit PLI Unity Acquisition records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Unity Acquisition contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Unity Acquisition within one (1) business day of audit. Once reconciled records are received back from PLIUnity Acquisition, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Unity Acquisition to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIUnity Acquisition’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Unity Acquisition with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Unity Acquisition and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Unity Acquisition data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Unity Acquisition in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Unity Acquisition performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Unity Acquisition at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Unity Acquisition the screening information associated with LIDB Data Screening of PLI Unity Acquisition data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Unity Acquisition under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Unity Acquisition customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI DPI Teleconnect any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIDPI Teleconnect’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI DPI Teleconnect what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIDPI Teleconnect, BellSouth shall provide PLI DPI Teleconnect with a list of the customer data items, which PLI DPI Teleconnect would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI DPI Teleconnect data to the LIDB shall be solely at the direction of PLIDPI Teleconnect. Such direction from PLI DPI Teleconnect will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇DPI Teleconnect data upon DPI Teleconnect’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI DPI Teleconnect customer records will be missing from LIDB, as measured by PLI DPI Teleconnect audits. BellSouth will audit PLI DPI Teleconnect records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI DPI Teleconnect contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI DPI Teleconnect within one (1) business day of audit. Once reconciled records are received back from PLIDPI Teleconnect, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI DPI Teleconnect to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIDPI Teleconnect’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI DPI Teleconnect with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI DPI Teleconnect and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI DPI Teleconnect data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI DPI Teleconnect in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI DPI Teleconnect performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI DPI Teleconnect at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI DPI Teleconnect the screening information associated with LIDB Data Screening of PLI DPI Teleconnect data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI DPI Teleconnect under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI DPI Teleconnect customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI CCI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CCI what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLICCI, BellSouth shall provide PLI CCI with a list of the customer data items, which PLI CCI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI CCI data to the LIDB shall be solely at the direction of PLICCI. Such direction from PLI CCI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CCI data upon CCI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CCI customer records will be missing from LIDB, as measured by PLI CCI audits. BellSouth will audit PLI CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI CCI within one (1) business day of audit. Once reconciled records are received back from PLICCI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI CCI to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICCI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI CCI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI CCI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI CCI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI CCI in writing. 7.3.2.13 BellSouth shall provide PLI CCI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CCI the screening information associated with LIDB Data Screening of PLI CCI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CCI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI CCI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Think 12 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIThink 12’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Think 12 what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIThink 12, BellSouth shall provide PLI Think 12 with a list of the customer data items, which PLI Think 12 would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Think 12 data to the LIDB shall be solely at the direction of PLIThink 12. Such direction from PLI Think 12 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Think 12 data upon Think 12’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Think 12 customer records will be missing from LIDB, as measured by PLI Think 12 audits. BellSouth will audit PLI Think 12 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Think 12 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Think 12 within one (1) business day of audit. Once reconciled records are received back from PLIThink 12, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Think 12 to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIThink 12’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Think 12 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Think 12 and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Think 12 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Think 12 in writing. 7.3.2.13 BellSouth shall provide PLI Think 12 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Think 12 at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Think 12 the screening information associated with LIDB Data Screening of PLI Think 12 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Think 12 under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Think 12 customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Nex-Phon any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLINex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Nex-Phon what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLINex-Phon, BellSouth shall provide PLI Nex- Phon with a list of the customer data items, which PLI Nex-Phon would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Nex-Phon data to the LIDB shall be solely at the direction of PLINex-Phon. Such direction from PLI Nex-Phon will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Nex-Phon data upon Nex- Phon’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Nex-Phon customer records will be missing from LIDB, as measured by PLI Nex-Phon audits. BellSouth will audit PLI Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Nex-Phon within one (1) business day of audit. Once reconciled records are received back from PLINex-Phon, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Nex-Phon to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLINex-Phon’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Nex-Phon with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Nex-Phon and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Nex-Phon data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Nex-Phon in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Nex-Phon performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Nex-Phon the screening information associated with LIDB Data Screening of PLI Nex-Phon data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Nex-Phon under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Nex-Phon customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI US South any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIUS South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI US South what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIUS South, BellSouth shall provide PLI US South with a list of the customer data items, which PLI US South would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI US South data to the LIDB shall be solely at the direction of PLIUS South. Such direction from PLI US South will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇US South data upon US South’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI US South customer records will be missing from LIDB, as measured by PLI US South audits. BellSouth will audit PLI US South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI US South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI US South within one (1) business day of audit. Once reconciled records are received back from PLIUS South, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI US South to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI in writing. 7.3.2.13 BellSouth shall provide PLI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI the screening information associated with LIDB Data Screening of PLI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.three

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI FeroNetworks any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIFeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI FeroNetworks what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIFeroNetworks, BellSouth shall provide PLI FeroNetworks with a list of the customer data items, which PLI FeroNetworks would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI FeroNetworks data to the LIDB shall be solely at the direction of PLIFeroNetworks. Such direction from PLI FeroNetworks will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇FeroNetworks data upon FeroNetworks’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI FeroNetworks customer records will be missing from LIDB, as measured by PLI FeroNetworks audits. BellSouth will audit PLI FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI FeroNetworks within one (1) business day of audit. Once reconciled records are received back from PLIFeroNetworks, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI FeroNetworks to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIFeroNetworks’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI FeroNetworks with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI FeroNetworks and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI FeroNetworks data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI FeroNetworks in writing. 7.3.2.13 BellSouth shall provide PLI FeroNetworks performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI FeroNetworks the screening information associated with LIDB Data Screening of PLI FeroNetworks data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI FeroNetworks under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI FeroNetworks customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Quality Telephone any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIQuality Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Quality Telephone what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIQuality Telephone, BellSouth shall provide PLI Quality Telephone with a list of the customer data items, which PLI Quality Telephone would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Quality Telephone data to the LIDB shall be solely at the direction of PLIQuality Telephone. Such direction from PLI Quality Telephone will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Quality Telephone data upon Quality Telephone’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Quality Telephone customer records will be missing from LIDB, as measured by PLI Quality Telephone audits. BellSouth will audit PLI Quality Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Quality Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Quality Telephone within one (1) business day of audit. Once reconciled records are received back from PLIQuality Telephone, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Quality Telephone to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIQuality Telephone’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Quality Telephone with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Quality Telephone and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Quality Telephone data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Quality Telephone in writing. 7.3.2.13 BellSouth shall provide PLI Quality Telephone performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Quality Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Quality Telephone the screening information associated with LIDB Data Screening of PLI Quality Telephone data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Quality Telephone under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Quality Telephone customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 8.2.1 BellSouth will offer to PLI GulfPines any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 8.2.2 BellSouth shall process PLI’s customer GulfPines’ Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI GulfPines what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 8.2.3 Within two (2) weeks after a request by PLIGulfPines, BellSouth shall provide PLI GulfPines with a list of the customer data items, which PLI GulfPines would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 8.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 8.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 8.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 8.2.7 All additions, updates and deletions of PLI GulfPines data to the LIDB shall be solely at the direction of PLIGulfPines. Such direction from PLI GulfPines will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI customer records will be missing from LIDB, as measured by PLI audits. BellSouth will audit PLI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI within one (1) business day of audit. Once reconciled records are received back from PLI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI in writing. 7.3.2.13 BellSouth shall provide PLI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI the screening information associated with LIDB Data Screening of PLI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Sail Networks any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLISail Networks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Sail Networks what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLISail Networks, BellSouth shall provide PLI Sail Networks with a list of the customer data items, which PLI Sail Networks would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Sail Networks data to the LIDB shall be solely at the direction of PLISail Networks. Such direction from PLI Sail Networks will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Sail Networks data upon Sail Networks’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Sail Networks customer records will be missing from LIDB, as measured by PLI Sail Networks audits. BellSouth will audit PLI Sail Networks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Sail Networks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Sail Networks within one (1) business day of audit. Once reconciled records are received back from PLISail Networks, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Sail Networks to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLISail Networks’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Sail Networks with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Sail Networks and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Sail Networks data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Sail Networks in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Sail Networks performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Sail Networks at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Sail Networks the screening information associated with LIDB Data Screening of PLI Sail Networks data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Sail Networks under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Sail Networks customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI BTI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIBTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI BTI what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIBTI, BellSouth shall provide PLI BTI with a list of the customer data items, which PLI BTI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI BTI data to the LIDB shall be solely at the direction of PLIBTI. Such direction from PLI BTI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇BTI data upon BTI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one (1) hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI BTI customer records will be missing from LIDB, as measured by PLI BTI audits. BellSouth will audit PLI BTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI BTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI BTI within one (1) business day of audit. Once reconciled records are received back from PLIBTI, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI BTI to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIBTI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI BTI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI BTI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI BTI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI BTI in writing. 7.3.2.13 BellSouth shall provide PLI BTI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI BTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI BTI the screening information associated with LIDB Data Screening of PLI BTI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI BTI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI BTI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI U-Dial any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIU-Dial’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI U-Dial what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIU-Dial, BellSouth shall provide PLI U-Dial with a list of the customer data items, which PLI U-Dial would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI U-Dial data to the LIDB shall be solely at the direction of PLIU-Dial. Such direction from PLI U-Dial will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇U-Dial data upon U-Dial’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI U-Dial customer records will be missing from LIDB, as measured by PLI U-Dial audits. BellSouth will audit PLI U-Dial records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI U-Dial contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI U-Dial within one (1) business day of audit. Once reconciled records are received back from PLIU-Dial, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI U-Dial to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIU-Dial’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI U-Dial with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI U-Dial and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI U-Dial data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI U-Dial in writing. 7.3.2.13 BellSouth shall provide PLI U-Dial performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI U-Dial at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI U-Dial the screening information associated with LIDB Data Screening of PLI U-Dial data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI U-Dial under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI U-Dial customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Gateway any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIGateway’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Gateway what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIGateway, BellSouth shall provide PLI Gateway with a list of the customer data items, which PLI Gateway would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Gateway data to the LIDB shall be solely at the direction of PLIGateway. Such direction from PLI Gateway will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Gateway data upon Gateway’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Gateway customer records will be missing from LIDB, as measured by PLI Gateway audits. BellSouth will audit PLI Gateway records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Gateway contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Gateway within one (1) business day of audit. Once reconciled records are received back from PLIGateway, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Gateway to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIGateway’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Gateway with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Gateway and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Gateway data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Gateway in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Gateway performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Gateway at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Gateway the screening information associated with LIDB Data Screening of PLI Gateway data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Gateway under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Gateway customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI OptiLink any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 13.4.2.1 BellSouth shall process PLIOptiLink’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI OptiLink what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 13.4.2.2 Within two (2) weeks after a request by PLIOptiLink, BellSouth shall provide PLI OptiLink with a list of the customer data items, items which PLI OptiLink would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 13.4.2.6 All additions, updates and deletions of PLI OptiLink data to the LIDB shall be solely at the direction of PLIOptiLink. Such direction from PLI OptiLink will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇OptiLink data upon OptiLink’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI OptiLink customer records will be missing from LIDB, as measured by PLI OptiLink audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI OptiLink records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated PLI OptiLink contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis- matches to PLI OptiLink within one (1) business day of audit. Once reconciled records are received back from PLIOptiLink, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI OptiLink to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of PLIOptiLink’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 13.4.2.10 BellSouth shall provide PLI OptiLink with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable time period as negotiated between PLI OptiLink and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of PLI OptiLink data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI OptiLink in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide PLI OptiLink performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI OptiLink at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI OptiLink the screening information associated with LIDB Data Screening of PLI OptiLink data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI OptiLink under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119. 7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with PLI OptiLink customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI ▇▇▇▇▇▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLI▇▇▇▇▇▇▇▇.▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ▇▇▇▇▇▇▇▇.▇▇▇ what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLI▇▇▇▇▇▇▇▇.▇▇▇, BellSouth shall provide PLI ▇▇▇▇▇▇▇▇.▇▇▇ with a list of the customer data items, which PLI ▇▇▇▇▇▇▇▇.▇▇▇ would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI ▇▇▇▇▇▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of PLI▇▇▇▇▇▇▇▇.▇▇▇. Such direction from PLI ▇▇▇▇▇▇▇▇.▇▇▇ will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇.▇▇▇ data upon ▇▇▇▇▇▇▇▇.▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ▇▇▇▇▇▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by PLI ▇▇▇▇▇▇▇▇.▇▇▇ audits. BellSouth will audit PLI ▇▇▇▇▇▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI ▇▇▇▇▇▇▇▇.▇▇▇ contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI ▇▇▇▇▇▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from PLI▇▇▇▇▇▇▇▇.▇▇▇, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI ▇▇▇▇▇▇▇▇.▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI in writing. 7.3.2.13 BellSouth shall provide PLI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI the screening information associated with LIDB Data Screening of PLI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.three

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI MTS Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIMTS Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI MTS Communications what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIMTS Communications, BellSouth shall provide PLI MTS Communications with a list of the customer data items, which PLI MTS Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI MTS Communications data to the LIDB shall be solely at the direction of PLIMTS Communications. Such direction from PLI MTS Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇MTS Communications data upon MTS Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI MTS Communications customer records will be missing from LIDB, as measured by PLI MTS Communications audits. BellSouth will audit PLI MTS Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI MTS Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI MTS Communications within one (1) business day of audit. Once reconciled records are received back from PLIMTS Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI MTS Communications to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIMTS Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI MTS Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI MTS Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI MTS Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI MTS Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI MTS Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI MTS Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI MTS Communications the screening information associated with LIDB Data Screening of PLI MTS Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI MTS Communications under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI MTS Communications customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Comm South any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIComm South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Comm South what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIComm South, BellSouth shall provide PLI Comm South with a list of the customer data items, which PLI Comm South would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Comm South data to the LIDB shall be solely at the direction of PLIComm South. Such direction from PLI Comm South will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Comm South data upon Comm South’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Comm South customer records will be missing from LIDB, as measured by PLI Comm South audits. BellSouth will audit PLI Comm South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Comm South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Comm South within one (1) business day of audit. Once reconciled records are received back from PLIComm South, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Comm South to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIComm South’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Comm South with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Comm South and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Comm South data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Comm South in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Comm South performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Comm South at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Comm South the screening information associated with LIDB Data Screening of PLI Comm South data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Comm South under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Comm South customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI BAK any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIBAK’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI BAK what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIBAK, BellSouth shall provide PLI BAK with a list of the customer data items, which PLI BAK would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI BAK data to the LIDB shall be solely at the direction of PLIBAK. Such direction from PLI BAK will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇BAK data upon BAK’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI BAK customer records will be missing from LIDB, as measured by PLI BAK audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI BAK records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI BAK contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI BAK within one (1) business day of audit. Once reconciled records are received back from PLIBAK, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI BAK to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIBAK’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI BAK with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI BAK and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI BAK data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI BAK in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI BAK performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI BAK at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI BAK the screening information associated with LIDB Data Screening of PLI BAK data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI BAK under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI BAK customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI ONS any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIONS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ONS what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIONS, BellSouth shall provide PLI ONS with a list of the customer data items, which PLI ONS would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI ONS data to the LIDB shall be solely at the direction of PLIONS. Such direction from PLI ONS will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇ONS data upon ONS’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ONS customer records will be missing from LIDB, as measured by PLI ONS audits. BellSouth will audit PLI ONS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI ONS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI ONS within one (1) business day of audit. Once reconciled records are received back from PLIONS, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI ONS to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIONS’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI ONS with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI ONS and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI ONS data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI ONS in writing. 7.3.2.13 BellSouth shall provide PLI ONS performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ONS at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ONS the screening information associated with LIDB Data Screening of PLI ONS data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ONS under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI ONS customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Nex-Phon any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLINex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Nex-Phon what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLINex-Phon, BellSouth shall provide PLI Nex- Phon with a list of the customer data items, which PLI Nex-Phon would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Nex-Phon data to the LIDB shall be solely at the direction of PLINex-Phon. Such direction from PLI Nex-Phon will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Nex-Phon data upon Nex- Phon’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Nex-Phon customer records will be missing from LIDB, as measured by PLI Nex-Phon audits. BellSouth will audit PLI Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Nex-Phon within one (1) business day of audit. Once reconciled records are received back from PLINex-Phon, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Nex-Phon to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLINex-Phon’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Nex-Phon with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Nex-Phon and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Nex-Phon data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Nex-Phon in writing. 7.3.2.13 BellSouth shall provide PLI Nex-Phon performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Nex-Phon the screening information associated with LIDB Data Screening of PLI Nex-Phon data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Nex-Phon under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Nex-Phon customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 1.2.1 BellSouth also will offer to PLI CLEC any additional capabilities that are developed for LIDB LIBD during the life of this Agreement. 7.3.2.2 1.2.2 BellSouth shall process PLICLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CLEC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 1.2.3 Within two (2) weeks after a request by PLICLEC, BellSouth shall provide PLI CLEC with a list of the customer data items, items which PLI CLEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 1.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 1.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 1.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 1.2.7 All additions, updates and deletions of PLI CLEC data to the LIDB shall be solely at the direction of PLICLEC. Such direction from PLI CLEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation). 7.3.2.8 1.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CLEC data upon CLEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 1.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CLEC customer records will be missing from LIDB, as measured by PLI CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated PLI CLEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to PLI CLEC within one (1) business day of audit. Once reconciled records are received back from PLICLEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI CLEC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 1.2.10 BellSouth shall perform backup and recovery of all of PLICLEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 1.2.11 BellSouth shall provide PLI CLEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI CLEC and BellSouth. 7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of PLI CLEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI CLEC in writing. 7.3.2.13 1.2.13.1 BellSouth shall provide PLI CLEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CLEC the screening information associated with LIDB Data Screening of PLI CLEC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CLEC under the BFR/NBR Process as set forth in Attachment 11Bona Fide Request process. 7.3.2.14 1.2.14 BellSouth shall accept queries to LIDB associated with PLI CLEC customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 1.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.within

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI ITC/\DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 15.4.2.1 BellSouth shall process PLI’s customer ITC/\DeltaCom's Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ITC/\DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 15.4.2.2 Within two (2) weeks after a request by PLIITC/\DeltaCom, BellSouth shall provide PLI ITC/\DeltaCom with a list of the customer data items, items which PLI ITC/\DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 15.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 15.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 15.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 15.4.2.6 All additions, updates and deletions of PLI ITC/\DeltaCom data to the LIDB shall be solely at the direction of PLIITC/\DeltaCom. Such direction from PLI ITC/\DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 15.4.2.7 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇’s ITC/\DeltaCom data upon ITC/\DeltaCom's request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 15.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ITC/\DeltaCom customer records will be missing from LIDB, as measured by PLI ITC/\DeltaCom audits. BellSouth will audit PLI ITC/\DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated PLI ITC/\DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to PLI ITC/\DeltaCom within one (1) business day of audit. Once reconciled records are received back from PLIITC/\DeltaCom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI ITC/\DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 15.4.2.9 BellSouth shall perform backup and recovery of all of PLI’s ITC/\DeltaCom's data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 15.4.2.10 BellSouth shall provide PLI ITC/\DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI ITC/\DeltaCom and BellSouth. 7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of PLI ITC/\DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI ITC/\DeltaCom in writing. 7.3.2.13 15.4.2.12 BellSouth shall provide PLI ITC/\DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ITC/\DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ITC/\DeltaCom the screening information associated with LIDB Data Screening of PLI ITC/\DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ITC/\DeltaCom under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119. 7.3.2.14 15.4.2.13 BellSouth shall accept queries to LIDB associated with PLI ITC/\DeltaCom customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 15.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 15.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI EPICUS any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIEPICUS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI EPICUS what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIEPICUS, BellSouth shall provide PLI EPICUS with a list of the customer data items, which PLI EPICUS would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI EPICUS data to the LIDB shall be solely at the direction of PLIEPICUS. Such direction from PLI EPICUS will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇EPICUS data upon EPICUS’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI EPICUS customer records will be missing from LIDB, as measured by PLI EPICUS audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI EPICUS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI EPICUS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI EPICUS within one (1) business day of audit. Once reconciled records are received back from PLIEPICUS, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI EPICUS to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIEPICUS’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI EPICUS with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI EPICUS and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI EPICUS data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI EPICUS in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI EPICUS performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI EPICUS at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI EPICUS the screening information associated with LIDB Data Screening of PLI EPICUS data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI EPICUS under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI EPICUS customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI PBT any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIPBT’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI PBT what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIPBT, BellSouth shall provide PLI PBT with a list of the customer data items, which PLI PBT would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI PBT data to the LIDB shall be solely at the direction of PLIPBT. Such direction from PLI PBT will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇PBT data upon PBT’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI PBT customer records will be missing from LIDB, as measured by PLI PBT audits. BellSouth will audit PLI PBT records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI PBT contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI PBT within one (1) business day of audit. Once reconciled records are received back from PLIPBT, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI PBT to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIPBT’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI PBT with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI PBT and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI PBT data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI PBT in writing. 7.3.2.13 BellSouth shall provide PLI PBT performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI PBT at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI PBT the screening information associated with LIDB Data Screening of PLI PBT data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI PBT under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI PBT customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI FeroNetworks any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIFeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI FeroNetworks what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIFeroNetworks, BellSouth shall provide PLI FeroNetworks with a list of the customer data items, which PLI FeroNetworks would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI FeroNetworks data to the LIDB shall be solely at the direction of PLIFeroNetworks. Such direction from PLI FeroNetworks will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇FeroNetworks data upon FeroNetworks’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI FeroNetworks customer records will be missing from LIDB, as measured by PLI FeroNetworks audits. BellSouth will audit PLI FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI FeroNetworks within one (1) business day of audit. Once reconciled records are received back from PLIFeroNetworks, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI FeroNetworks to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIFeroNetworks’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI FeroNetworks with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI FeroNetworks and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI FeroNetworks data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI FeroNetworks in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI FeroNetworks performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI FeroNetworks the screening information associated with LIDB Data Screening of PLI FeroNetworks data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI FeroNetworks under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI FeroNetworks customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Clearwave Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIClearwave Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Clearwave Communications what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIClearwave Communications, BellSouth shall provide PLI Clearwave Communications with a list of the customer data items, which PLI Clearwave Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Clearwave Communications data to the LIDB shall be solely at the direction of PLIClearwave Communications. Such direction from PLI Clearwave Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Clearwave Communications data upon Clearwave Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Clearwave Communications customer records will be missing from LIDB, as measured by PLI Clearwave Communications audits. BellSouth will audit PLI Clearwave Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Clearwave Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Clearwave Communications within one (1) business day of audit. Once reconciled records are received back from PLIClearwave Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Clearwave Communications to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIClearwave Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Clearwave Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Clearwave Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Clearwave Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Clearwave Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Clearwave Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Clearwave Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Clearwave Communications the screening information associated with LIDB Data Screening of PLI Clearwave Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Clearwave Communications under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Clearwave Communications customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Clearwave Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIClearwave Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Clearwave Communications what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIClearwave Communications, BellSouth shall provide PLI Clearwave Communications with a list of the customer data items, which PLI Clearwave Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Clearwave Communications data to the LIDB shall be solely at the direction of PLIClearwave Communications. Such direction from PLI Clearwave Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Clearwave Communications data upon Clearwave Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Clearwave Communications customer records will be missing from LIDB, as measured by PLI Clearwave Communications audits. BellSouth will audit PLI Clearwave Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Clearwave Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Clearwave Communications within one (1) business day of audit. Once reconciled records are received back from PLIClearwave Communications, BellSouth ▇▇▇▇▇▇▇▇▇ will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI Clearwave Communications to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIClearwave Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Clearwave Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Clearwave Communications and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Clearwave Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Clearwave Communications in writing. 7.3.2.13 BellSouth shall provide PLI Clearwave Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Clearwave Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Clearwave Communications the screening information associated with LIDB Data Screening of PLI Clearwave Communications data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Clearwave Communications under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Clearwave Communications customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI COMTECH21 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLICOMTECH21’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI COMTECH21 what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLICOMTECH21, BellSouth shall provide PLI COMTECH21 with a list of the customer data items, which PLI COMTECH21 would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI COMTECH21 data to the LIDB shall be solely at the direction of PLICOMTECH21. Such direction from PLI COMTECH21 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇COMTECH21 data upon COMTECH21’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI COMTECH21 customer records will be missing from LIDB, as measured by PLI COMTECH21 audits. BellSouth will audit PLI COMTECH21 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI COMTECH21 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI COMTECH21 within one (1) business day of audit. Once reconciled records are received back from PLICOMTECH21, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI COMTECH21 to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLICOMTECH21’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI COMTECH21 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI COMTECH21 and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI COMTECH21 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI COMTECH21 in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI COMTECH21 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI COMTECH21 at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI COMTECH21 the screening information associated with LIDB Data Screening of PLI COMTECH21 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI COMTECH21 under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI COMTECH21 customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Rent-A-Line any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIRent-A-Line’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Rent-A-Line what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIRent-A-Line, BellSouth shall provide PLI Rent-A-Line with a list of the customer data items, which PLI Rent-A-Line would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Rent-A-Line data to the LIDB shall be solely at the direction of PLIRent-A-Line. Such direction from PLI Rent-A-Line will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Rent-A-Line data upon Rent- A-Line’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Rent-A- Line customer records will be missing from LIDB, as measured by PLI Rent-A-Line audits. BellSouth will audit PLI Rent-A-Line records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Rent-A-Line contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Rent-A-Line within one (1) business day of audit. Once reconciled records are received back from PLIRent-A-Line, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Rent- A-Line to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIRent-A-Line’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Rent-A-Line with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Rent-A-Line and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Rent-A-Line data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Rent-A-Line in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Rent-A-Line performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Rent-A-Line at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Rent-A-Line the screening information associated with LIDB Data Screening of PLI Rent-A-Line data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Rent-A-Line under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Rent-A-Line customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Deland Actel any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIDeland Actel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Deland Actel what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIDeland Actel, BellSouth shall provide PLI Deland Actel with a list of the customer data items, which PLI Deland Actel would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Deland Actel data to the LIDB shall be solely at the direction of PLIDeland Actel. Such direction from PLI Deland Actel will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Deland Actel data upon Deland Actel’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Deland Actel customer records will be missing from LIDB, as measured by PLI Deland Actel audits. BellSouth will audit PLI Deland Actel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Deland Actel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Deland Actel within one (1) business day of audit. Once reconciled records are received back from PLIDeland Actel, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Deland Actel to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIDeland Actel’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Deland Actel with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Deland Actel and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Deland Actel data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Deland Actel in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Deland Actel performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Deland Actel at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Deland Actel the screening information associated with LIDB Data Screening of PLI Deland Actel data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Deland Actel under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Deland Actel customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Grande any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLI▇▇▇▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Grande what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIGrande, BellSouth shall provide PLI Grande with a list of the customer data items, which PLI Grande would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Grande data to the LIDB shall be solely at the direction of PLIGrande. Such direction from PLI Grande will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Grande data upon Grande’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Grande customer records will be missing from LIDB, as measured by PLI Grande audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI Grande records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Grande contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Grande within one (1) business day of audit. Once reconciled records are received back from PLIGrande, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Grande to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIGrande’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Grande with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Grande and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Grande data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Grande in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Grande performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Grande at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Grande the screening information associated with LIDB Data Screening of PLI Grande data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Grande under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Grande customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI MyLineToo any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIMyLineToo’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI MyLineToo what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIMyLineToo, BellSouth shall provide PLI MyLineToo with a list of the customer data items, which PLI MyLineToo would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI MyLineToo data to the LIDB shall be solely at the direction of PLIMyLineToo. Such direction from PLI MyLineToo will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇MyLineToo data upon MyLineToo’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI MyLineToo customer records will be missing from LIDB, as measured by PLI MyLineToo audits. BellSouth will audit PLI MyLineToo records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI MyLineToo contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI MyLineToo within one (1) business day of audit. Once reconciled records are received back from PLIMyLineToo, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI MyLineToo to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIMyLineToo’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI MyLineToo with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI MyLineToo and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI MyLineToo data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI MyLineToo in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI MyLineToo performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI MyLineToo at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI MyLineToo the screening information associated with LIDB Data Screening of PLI MyLineToo data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI MyLineToo under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI MyLineToo customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Telstar Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLITelstar Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Telstar Communications what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLITelstar Communications, BellSouth shall provide PLI Telstar Communications with a list of the customer data items, which PLI Telstar Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Telstar Communications data to the LIDB shall be solely at the direction of PLITelstar Communications. Such direction from PLI Telstar Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Telstar Communications data upon Telstar Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Telstar Communications customer records will be missing from LIDB, as measured by PLI Telstar Communications audits. BellSouth will audit PLI Telstar Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Telstar Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Telstar Communications within one (1) business day of audit. Once reconciled records are received back from PLITelstar Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Telstar Communications to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLITelstar Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Telstar Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Telstar Communications and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Telstar Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Telstar Communications in writing. 7.3.2.13 BellSouth shall provide PLI Telstar Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Telstar Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Telstar Communications the screening information associated with LIDB Data Screening of PLI Telstar Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Telstar Communications under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Telstar Communications customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLILevel 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Level 3 what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLI▇▇▇▇▇ ▇, BellSouth ▇▇▇▇▇▇▇▇▇ shall provide PLI Level 3 with a list of the customer data items, which PLI ▇▇▇▇▇ ▇ would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Level 3 data to the LIDB shall be solely at the direction of PLILevel 3. Such direction from PLI Level 3 will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇▇▇ ▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇▇▇ ▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Level 3 customer records will be missing from LIDB, as measured by PLI Level 3 audits. BellSouth will audit PLI Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Level 3 within one (1) business day of audit. Once reconciled records are received back from PLI▇▇▇▇▇ ▇, BellSouth ▇▇▇▇▇▇▇▇▇ will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI Level 3 to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLILevel 3’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Level 3 with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Level 3 and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Level 3 data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Level 3 in writing. 7.3.2.13 BellSouth shall provide PLI Level 3 performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Level 3 the screening information associated with LIDB Data Screening of PLI Level 3 data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Level 3 under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Level 3 customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Covad any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICovad’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Covad what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLICovad, BellSouth shall provide PLI Covad with a list of the customer data items, which PLI Covad would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Covad data to the LIDB shall be solely at the direction of PLICovad. Such direction from PLI Covad will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Covad data upon Covad’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Covad customer records will be missing from LIDB, as measured by PLI Covad audits. BellSouth will audit PLI Covad records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Covad contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Covad within one (1) business day of audit. Once reconciled records are received back from PLICovad, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI Covad to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICovad’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Covad with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Covad and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Covad data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Covad in writing. 7.3.2.13 BellSouth shall provide PLI Covad performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Covad at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Covad the screening information associated with LIDB Data Screening of PLI Covad data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Covad under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Covad customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI UTI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIUTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI UTI what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIUTI, BellSouth shall provide PLI UTI with a list of the customer data items, which PLI UTI would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI UTI data to the LIDB shall be solely at the direction of PLIUTI. Such direction from PLI UTI will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇UTI data upon UTI’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI UTI customer records will be missing from LIDB, as measured by PLI UTI audits. BellSouth will audit PLI UTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI UTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI UTI within one (1) business day of audit. Once reconciled records are received back from PLIUTI, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI UTI to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIUTI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI UTI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI UTI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI UTI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI UTI in writing. 7.3.2.13 BellSouth shall provide PLI UTI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI UTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI UTI the screening information associated with LIDB Data Screening of PLI UTI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI UTI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI UTI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI ITC/\DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 13.4.2.1 BellSouth shall process PLI’s customer ITC/\DeltaCom's Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ITC/\DeltaCom what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 13.4.2.2 Within two (2) weeks after a request by PLIITC/\DeltaCom, BellSouth shall provide PLI ITC/\DeltaCom with a list of the customer data items, items which PLI ITC/\DeltaCom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 13.4.2.6 All additions, updates and deletions of PLI ITC/\DeltaCom data to the LIDB shall be solely at the direction of PLIITC/\DeltaCom. Such direction from PLI ITC/\DeltaCom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇’s ITC/\DeltaCom data upon ITC/\DeltaCom's request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ITC/\DeltaCom customer records will be missing from LIDB, as measured by PLI ITC/\DeltaCom audits. BellSouth will audit PLI ITC/\DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated PLI ITC/\DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to PLI ITC/\DeltaCom within one (1) business day of audit. Once reconciled records are received back from PLIITC/\DeltaCom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI ITC/\DeltaCom to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of PLI’s ITC/\DeltaCom's data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 13.4.2.10 BellSouth shall provide PLI ITC/\DeltaCom with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI ITC/\DeltaCom and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of PLI ITC/\DeltaCom data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI ITC/\DeltaCom in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide PLI ITC/\DeltaCom performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ITC/\DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ITC/\DeltaCom the screening information associated with LIDB Data Screening of PLI ITC/\DeltaCom data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ITC/\DeltaCom under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119. 7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with PLI ITC/\DeltaCom customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Kinetix any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIKinetix’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Kinetix what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIKinetix, BellSouth shall provide PLI Kinetix with a list of the customer data items, which PLI Kinetix would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Kinetix data to the LIDB shall be solely at the direction of PLIKinetix. Such direction from PLI Kinetix will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Kinetix data upon Kinetix’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Kinetix customer records will be missing from LIDB, as measured by PLI Kinetix audits. BellSouth will audit PLI Kinetix records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Kinetix contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Kinetix within one (1) business day of audit. Once reconciled records are received back from PLIKinetix, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Kinetix to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIKinetix’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Kinetix with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Kinetix and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Kinetix data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Kinetix in writing. 7.3.2.13 BellSouth shall provide PLI Kinetix performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Kinetix at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Kinetix the screening information associated with LIDB Data Screening of PLI Kinetix data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Kinetix under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Kinetix customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICBX One-Stop’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CBX One-Stop what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLICBX One-Stop, BellSouth shall provide PLI CBX One-Stop with a list of the customer data items, which PLI CBX One-Stop would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI CBX One-Stop data to the LIDB shall be solely at the direction of PLICBX One-Stop. Such direction from PLI CBX One-Stop will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CBX One-Stop data upon CBX One-Stop’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CBX One-Stop customer records will be missing from LIDB, as measured by PLI CBX One- Stop audits. BellSouth will audit PLI CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI CBX One-Stop contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from PLICBX One-Stop, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI CBX One-Stop to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICBX One-Stop’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI CBX One-Stop with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI CBX One-Stop and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI CBX One-Stop data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI CBX One-Stop in writing. 7.3.2.13 BellSouth shall provide PLI CBX One-Stop performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CBX One-Stop the screening information associated with LIDB Data Screening of PLI CBX One-Stop data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CBX One-Stop under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI CBX One-Stop customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Micro-Comm any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIMicro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Micro-Comm what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIMicro-Comm, BellSouth shall provide PLI Micro-Comm with a list of the customer data items, which PLI Micro-Comm would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Micro-Comm data to the LIDB shall be solely at the direction of PLIMicro-Comm. Such direction from PLI Micro-Comm will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Micro-Comm data upon Micro-Comm’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Micro- Comm customer records will be missing from LIDB, as measured by PLI Micro-Comm audits. BellSouth will audit PLI Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Micro-Comm within one (1) business day of audit. Once reconciled records are received back from PLIMicro-Comm, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Micro-Comm to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIMicro-Comm’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Micro-Comm with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Micro-Comm and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Micro-Comm data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Micro-Comm in writing. 7.3.2.13 BellSouth shall provide PLI Micro-Comm performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Micro-Comm the screening information associated with LIDB Data Screening of PLI Micro-Comm data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Micro-Comm under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Micro-Comm customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI FLATEL any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIFLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI FLATEL what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIFLATEL, BellSouth shall provide PLI FLATEL with a list of the customer data items, which PLI FLATEL would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI FLATEL data to the LIDB shall be solely at the direction of PLIFLATEL. Such direction from PLI FLATEL will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇FLATEL data upon FLATEL’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI FLATEL customer records will be missing from LIDB, as measured by PLI FLATEL audits. BellSouth will audit PLI FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI FLATEL within one (1) business day of audit. Once reconciled records are received back from PLIFLATEL, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI FLATEL to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIFLATEL’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI FLATEL with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI FLATEL and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI FLATEL data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI FLATEL in writing. 7.3.2.13 BellSouth shall provide PLI FLATEL performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI FLATEL the screening information associated with LIDB Data Screening of PLI FLATEL data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI FLATEL under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI FLATEL customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Preferred any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIPreferred’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Preferred what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIPreferred, BellSouth shall provide PLI Preferred with a list of the customer data items, which PLI Preferred would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Preferred data to the LIDB shall be solely at the direction of PLIPreferred. Such direction from PLI Preferred will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Preferred data upon Preferred’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Preferred customer records will be missing from LIDB, as measured by PLI Preferred audits. BellSouth will audit PLI Preferred records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Preferred contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Preferred within one (1) business day of audit. Once reconciled records are received back from PLIPreferred, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Preferred to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIPreferred’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Preferred with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Preferred and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Preferred data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Preferred in writing. 7.3.2.13 BellSouth shall provide PLI Preferred performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Preferred at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Preferred the screening information associated with LIDB Data Screening of PLI Preferred data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Preferred under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Preferred customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Utility USA any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIUtility USA’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Utility USA what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIUtility USA, BellSouth shall provide PLI Utility USA with a list of the customer data items, which PLI Utility USA would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Utility USA data to the LIDB shall be solely at the direction of PLIUtility USA. Such direction from PLI Utility USA will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Utility USA data upon Utility USA’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Utility USA customer records will be missing from LIDB, as measured by PLI Utility USA audits. BellSouth will audit PLI Utility USA records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Utility USA contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Utility USA within one (1) business day of audit. Once reconciled records are received back from PLIUtility USA, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Utility USA to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIUtility USA’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Utility USA with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Utility USA and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Utility USA data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Utility USA in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Utility USA performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Utility USA at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Utility USA the screening information associated with LIDB Data Screening of PLI Utility USA data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Utility USA under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Utility USA customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI NationNET any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLINationNET’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI NationNET what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLINationNET, BellSouth shall provide PLI NationNET with a list of the customer data items, which PLI NationNET would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI NationNET data to the LIDB shall be solely at the direction of PLINationNET. Such direction from PLI NationNET will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇NationNET data upon NationNET’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI NationNET customer records will be missing from LIDB, as measured by PLI NationNET audits. BellSouth will audit PLI NationNET records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI NationNET contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI NationNET within one (1) business day of audit. Once reconciled records are received back from PLINationNET, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI NationNET to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLINationNET’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI NationNET with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI NationNET and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI NationNET data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI NationNET in writing. 7.3.2.13 BellSouth shall provide PLI NationNET performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI NationNET at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI NationNET the screening information associated with LIDB Data Screening of PLI NationNET data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI NationNET under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI NationNET customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI AmTel any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIAmTel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI AmTel what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIAmTel, BellSouth shall provide PLI AmTel with a list of the customer data items, which PLI AmTel would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI AmTel data to the LIDB shall be solely at the direction of PLIAmTel. Such direction from PLI AmTel will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇AmTel data upon AmTel’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI AmTel customer records will be missing from LIDB, as measured by PLI AmTel audits. BellSouth will audit PLI AmTel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI AmTel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI AmTel within one (1) business day of audit. Once reconciled records are received back from PLIAmTel, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI AmTel to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIAmTel’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI AmTel with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI AmTel and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI AmTel data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI AmTel in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI AmTel performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI AmTel at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI AmTel the screening information associated with LIDB Data Screening of PLI AmTel data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI AmTel under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI AmTel customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Symtelco any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLISymtelco’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Symtelco what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLISymtelco, BellSouth shall provide PLI Symtelco with a list of the customer data items, which PLI Symtelco would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Symtelco data to the LIDB shall be solely at the direction of PLISymtelco. Such direction from PLI Symtelco will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Symtelco data upon Symtelco’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Symtelco customer records will be missing from LIDB, as measured by PLI Symtelco audits. BellSouth will audit PLI Symtelco records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Symtelco contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Symtelco within one (1) business day of audit. Once reconciled records are received back from PLISymtelco, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Symtelco to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLISymtelco’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Symtelco with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Symtelco and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Symtelco data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Symtelco in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Symtelco performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Symtelco at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Symtelco the screening information associated with LIDB Data Screening of PLI Symtelco data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Symtelco under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Symtelco customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Cinergy any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICinergy’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Cinergy what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLICinergy, BellSouth shall provide PLI Cinergy with a list of the customer data items, which PLI Cinergy would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Cinergy data to the LIDB shall be solely at the direction of PLICinergy. Such direction from PLI Cinergy will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Cinergy data upon Cinergy’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Cinergy customer records will be missing from LIDB, as measured by PLI Cinergy audits. BellSouth will audit PLI Cinergy records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Cinergy contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Cinergy within one (1) business day of audit. Once reconciled records are received back from PLICinergy, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Cinergy to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICinergy’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Cinergy with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Cinergy and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Cinergy data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Cinergy in writing. 7.3.2.13 BellSouth shall provide PLI Cinergy performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Cinergy at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Cinergy the screening information associated with LIDB Data Screening of PLI Cinergy data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Cinergy under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Cinergy customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI NGTelecom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLINGTelecom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI NGTelecom what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLINGTelecom, BellSouth shall provide PLI NGTelecom with a list of the customer data items, which PLI NGTelecom would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI NGTelecom data to the LIDB shall be solely at the direction of PLINGTelecom. Such direction from PLI NGTelecom will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇NGTelecom data upon NGTelecom’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI NGTelecom customer records will be missing from LIDB, as measured by PLI NGTelecom audits. BellSouth will audit PLI NGTelecom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI NGTelecom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI NGTelecom within one (1) business day of audit. Once reconciled records are received back from PLINGTelecom, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI NGTelecom to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI in writing. 7.3.2.13 BellSouth shall provide PLI performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI the screening information associated with LIDB Data Screening of PLI data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.three

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Excel any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIExcel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Excel what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIExcel, BellSouth shall provide PLI Excel with a list of the customer data items, which PLI Excel would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Excel data to the LIDB shall be solely at the direction of PLIExcel. Such direction from PLI Excel will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Excel data upon Excel’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Excel customer records will be missing from LIDB, as measured by PLI Excel audits. BellSouth will audit PLI Excel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Excel contact person to resolve the status of the records and BellSouth AMENDMENT EXHIBIT 1 Attachment 2 Page 52 will update system appropriately. BellSouth will refer record of mismatches to PLI Excel within one (1) business day of audit. Once reconciled records are received back from PLIExcel, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Excel to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIExcel’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Excel with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Excel and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Excel data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Excel in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Excel performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Excel at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Excel the screening information associated with LIDB Data Screening of PLI Excel data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Excel under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Excel customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI OnePoint Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIOnePoint Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI OnePoint Communications what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIOnePoint Communications, BellSouth shall provide PLI OnePoint Communications with a list of the customer data items, which PLI OnePoint Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI OnePoint Communications data to the LIDB shall be solely at the direction of PLIOnePoint Communications. Such direction from PLI OnePoint Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇OnePoint Communications data upon OnePoint Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI OnePoint Communications customer records will be missing from LIDB, as measured by PLI OnePoint Communications audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI OnePoint Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI OnePoint Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI OnePoint Communications within one (1) business day of audit. Once reconciled records are received back from PLIOnePoint Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI OnePoint Communications to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIOnePoint Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI OnePoint Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI OnePoint Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI OnePoint Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI OnePoint Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI OnePoint Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI OnePoint Communications at least at parity with BellSouth Customer Data. BellSouth ▇▇▇▇▇▇▇▇▇ shall obtain from PLI OnePoint Communications the screening information associated with LIDB Data Screening of PLI OnePoint Communications data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI OnePoint Communications under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI OnePoint Communications customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI ConnectNow! any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIConnectNow!’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ConnectNow! what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIConnectNow!, BellSouth shall provide PLI ConnectNow! with a list of the customer data items, which PLI ConnectNow! would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI ConnectNow! data to the LIDB shall be solely at the direction of PLIConnectNow!. Such direction from PLI ConnectNow! will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇ConnectNow! data upon ConnectNow!’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ConnectNow! customer records will be missing from LIDB, as measured by PLI ConnectNow! audits. BellSouth will audit PLI ConnectNow! records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI ConnectNow! contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI ConnectNow! within one (1) business day of audit. Once reconciled records are received back from PLIConnectNow!, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI ConnectNow! to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIConnectNow!’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI ConnectNow! with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI ConnectNow! and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI ConnectNow! data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI ConnectNow! in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI ConnectNow! performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ConnectNow! at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ConnectNow! the screening information associated with LIDB Data Screening of PLI ConnectNow! data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ConnectNow! under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI ConnectNow! customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI AmeriMex any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIAmeriMex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI AmeriMex what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIAmeriMex, BellSouth shall provide PLI AmeriMex with a list of the customer data items, which PLI AmeriMex would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI AmeriMex data to the LIDB shall be solely at the direction of PLIAmeriMex. Such direction from PLI AmeriMex will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇AmeriMex data upon AmeriMex’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI AmeriMex customer records will be missing from LIDB, as measured by PLI AmeriMex audits. BellSouth will audit PLI AmeriMex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI AmeriMex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI AmeriMex within one (1) business day of audit. Once reconciled records are received back from PLIAmeriMex, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI AmeriMex to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIAmeriMex’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI AmeriMex with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI AmeriMex and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI AmeriMex data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI AmeriMex in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI AmeriMex performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI AmeriMex at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI AmeriMex the screening information associated with LIDB Data Screening of PLI AmeriMex data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI AmeriMex under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI AmeriMex customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Triarch Marketing any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLITriarch Marketing’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Triarch Marketing what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLITriarch Marketing, BellSouth shall provide PLI Triarch Marketing with a list of the customer data items, which PLI Triarch Marketing would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Triarch Marketing data to the LIDB shall be solely at the direction of PLITriarch Marketing. Such direction from PLI Triarch Marketing will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Triarch Marketing data upon Triarch Marketing’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Triarch Marketing customer records will be missing from LIDB, as measured by PLI Triarch Marketing audits. BellSouth will audit PLI Triarch Marketing records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Triarch Marketing contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Triarch Marketing within one (1) business day of audit. Once reconciled records are received back from PLITriarch Marketing, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Triarch Marketing to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLITriarch Marketing’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Triarch Marketing with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Triarch Marketing and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Triarch Marketing data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Triarch Marketing in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Triarch Marketing performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Triarch Marketing at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Triarch Marketing the screening information associated with LIDB Data Screening of PLI Triarch Marketing data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Triarch Marketing under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Triarch Marketing customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Excel PCHP any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIExcel PCHP’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Excel PCHP what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIExcel PCHP, BellSouth shall provide PLI Excel PCHP with a list of the customer data items, which PLI Excel PCHP would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Excel PCHP data to the LIDB shall be solely at the direction of PLIExcel PCHP. Such direction from PLI Excel PCHP will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Excel PCHP data upon Excel PCHP’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Excel PCHP customer records will be missing from LIDB, as measured by PLI Excel PCHP audits. BellSouth will audit PLI Excel PCHP records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Excel PCHP contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Excel PCHP within one (1) business day of audit. Once reconciled records are received back from PLIExcel PCHP, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Excel PCHP to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIExcel PCHP’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Excel PCHP with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Excel PCHP and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Excel PCHP data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Excel PCHP in writing. 7.3.2.13 BellSouth shall provide PLI Excel PCHP performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Excel PCHP at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Excel PCHP the screening information associated with LIDB Data Screening of PLI Excel PCHP data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Excel PCHP under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Excel PCHP customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Starlink any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIStarlink’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Starlink what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIStarlink, BellSouth shall provide PLI Starlink with a list of the customer data items, which PLI Starlink would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Starlink data to the LIDB shall be solely at the direction of PLIStarlink. Such direction from PLI Starlink will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Starlink data upon Starlink’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Starlink customer records will be missing from LIDB, as measured by PLI Starlink audits. BellSouth will audit PLI Starlink records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Starlink contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Starlink within one (1) business day of audit. Once reconciled records are received back from PLIStarlink, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI Starlink to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIStarlink’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Starlink with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Starlink and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Starlink data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Starlink in writing. 7.3.2.13 BellSouth shall provide PLI Starlink performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Starlink at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Starlink the screening information associated with LIDB Data Screening of PLI Starlink data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Starlink under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Starlink customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI OnePoint any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIOnePoint’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI OnePoint what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIOnePoint, BellSouth shall provide PLI OnePoint with a list of the customer data items, which PLI OnePoint would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI OnePoint data to the LIDB shall be solely at the direction of PLIOnePoint. Such direction from PLI OnePoint will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇OnePoint data upon OnePoint’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI OnePoint customer records will be missing from LIDB, as measured by PLI OnePoint audits. BellSouth will audit PLI OnePoint records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI OnePoint contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI OnePoint within one (1) business day of audit. Once reconciled records are received back from PLIOnePoint, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI OnePoint to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIOnePoint’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI OnePoint with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI OnePoint and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI OnePoint data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI OnePoint in writing. 7.3.2.13 BellSouth shall provide PLI OnePoint performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI OnePoint at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI OnePoint the screening information associated with LIDB Data Screening of PLI OnePoint data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI OnePoint under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI OnePoint customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI ProNet any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIProNet’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI ProNet what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIProNet, BellSouth shall provide PLI ProNet with a list of the customer data items, which PLI ProNet would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI ProNet data to the LIDB shall be solely at the direction of PLIProNet. Such direction from PLI ProNet will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇ProNet data upon ProNet’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI ProNet customer records will be missing from LIDB, as measured by PLI ProNet audits. BellSouth will audit PLI ProNet records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI ProNet contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI ProNet within one (1) business day of audit. Once reconciled records are received back from PLIProNet, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI ProNet to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIProNet’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI ProNet with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI ProNet and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI ProNet data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI ProNet in writing. 7.3.2.13 BellSouth shall provide PLI ProNet performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI ProNet at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI ProNet the screening information associated with LIDB Data Screening of PLI ProNet data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI ProNet under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI ProNet customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Southern Digital any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLISouthern Digital’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Southern Digital what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLISouthern Digital, BellSouth shall provide PLI Southern Digital with a list of the customer data items, which PLI Southern Digital would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Southern Digital data to the LIDB shall be solely at the direction of PLISouthern Digital. Such direction from PLI Southern Digital will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Southern Digital data upon Southern Digital’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one (1) hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Southern Digital customer records will be missing from LIDB, as measured by PLI Southern Digital audits. BellSouth will audit PLI Southern Digital records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Southern Digital contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Southern Digital within one (1) business day of audit. Once reconciled records are received back from PLISouthern Digital, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI Southern Digital to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLISouthern Digital’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Southern Digital with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Southern Digital and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Southern Digital data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Southern Digital in writing. 7.3.2.13 BellSouth shall provide PLI Southern Digital performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Southern Digital at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Southern Digital the screening information associated with LIDB Data Screening of PLI Southern Digital data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Southern Digital under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Southern Digital customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Nexus any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLINexus’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Nexus what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLINexus, BellSouth shall provide PLI Nexus with a list of the customer data items, which PLI Nexus would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Nexus data to the LIDB shall be solely at the direction of PLINexus. Such direction from PLI Nexus will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Nexus data upon Nexus’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Nexus customer records will be missing from LIDB, as measured by PLI Nexus audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI Nexus records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Nexus contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Nexus within one (1) business day of audit. Once reconciled records are received back from PLINexus, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI Nexus to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLINexus’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Nexus with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Nexus and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Nexus data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Nexus in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Nexus performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Nexus at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Nexus the screening information associated with LIDB Data Screening of PLI Nexus data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Nexus under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Nexus customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI US LEC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 13.4.2.1 BellSouth shall process PLIUS LEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI US LEC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 13.4.2.2 Within two (2) weeks after a request by PLIUS LEC, BellSouth shall provide PLI US LEC with a list of the customer data items, items which PLI US LEC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function function, and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 13.4.2.3 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked blocked, shall not exceed thirty (30) 30 minutes per year. 7.3.2.5 13.4.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) 12 hours per year. 7.3.2.6 13.4.2.5 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) 12 hours per year. 7.3.2.7 13.4.2.6 All additions, updates and deletions of PLI US LEC data to the LIDB shall be solely at the direction of PLIUS LEC. Such direction from PLI US LEC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 13.4.2.7 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇US LEC data upon US LEC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 13.4.2.8 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI US LEC customer records will be missing from LIDB, as measured by PLI US LEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated PLI US LEC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches mis-matches to PLI US LEC within one (1) business day of audit. Once reconciled records are received back from PLIUS LEC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI US LEC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 13.4.2.9 BellSouth shall perform backup and recovery of all of PLIUS LEC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; basis and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 13.4.2.10 BellSouth shall provide PLI US LEC with LIDB reports of data which are missing or contain errors, as well as any misrouted misroute errors, within a reasonable reason time period as negotiated between PLI US LEC and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of PLI US LEC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party party that is not authorized by PLI US LEC in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide PLI US LEC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI US LEC the screening information associated with LIDB Data Screening of PLI US LEC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI US LEC under the BFR/NBR Process as set forth in Bona Fide Request process of Attachment 119. 7.3.2.14 13.4.2.13 BellSouth shall accept queries to LIDB associated with PLI US LEC customer records records, and shall return responses in accordance with industry standards. 7.3.2.15 13.4.2.14 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 13.4.2.15 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI EZ Phone any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIEZ Phone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI EZ Phone what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIEZ Phone, BellSouth shall provide PLI EZ Phone with a list of the customer data items, which PLI EZ Phone would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI EZ Phone data to the LIDB shall be solely at the direction of PLIEZ Phone. Such direction from PLI EZ Phone will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇EZ Phone data upon EZ Phone’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI EZ Phone customer records will be missing from LIDB, as measured by PLI EZ Phone audits. BellSouth will audit PLI EZ Phone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI EZ Phone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI EZ Phone within one (1) business day of audit. Once reconciled records are received back from PLIEZ Phone, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI EZ Phone to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIEZ Phone’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI EZ Phone with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI EZ Phone and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI EZ Phone data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI EZ Phone in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI EZ Phone performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI EZ Phone at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI EZ Phone the screening information associated with LIDB Data Screening of PLI EZ Phone data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI EZ Phone under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI EZ Phone customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Covad any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICovad’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Covad what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLI▇▇▇▇▇, BellSouth shall provide PLI Covad with a list of the customer data items, which PLI Covad would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Covad data to the LIDB shall be solely at the direction of PLICovad. Such direction from PLI Covad will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Covad data upon Covad’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Covad customer records will be missing from LIDB, as measured by PLI Covad audits. BellSouth will audit PLI Covad records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Covad contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Covad within one (1) business day of audit. Once reconciled records are received back from PLICovad, BellSouth will update LIDB the same business day if less than 500 five hundred (500) records are received before 1:00 p.m. Central Time. If more than 500 five hundred (500) records are received, BellSouth will contact PLI ▇▇▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICovad’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Covad with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Covad and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Covad data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI ▇▇▇▇▇ in writing. 7.3.2.13 BellSouth shall provide PLI Covad performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Covad at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Covad the screening information associated with LIDB Data Screening of PLI Covad data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Covad under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Covad customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 one (1) second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI FLATEL any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIFLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI FLATEL what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIFLATEL, BellSouth shall provide PLI FLATEL with a list of the customer data items, which PLI FLATEL would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI FLATEL data to the LIDB shall be solely at the direction of PLIFLATEL. Such direction from PLI FLATEL will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇FLATEL data upon FLATEL’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI FLATEL customer records will be missing from LIDB, as measured by PLI FLATEL audits. BellSouth will audit PLI FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI FLATEL within one (1) business day of audit. Once reconciled records are received back from PLIFLATEL, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI FLATEL to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIFLATEL’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI FLATEL with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI FLATEL and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI FLATEL data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI FLATEL in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI FLATEL performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI FLATEL the screening information associated with LIDB Data Screening of PLI FLATEL data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI FLATEL under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI FLATEL customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Advantage Group any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIAdvantage Group’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Advantage Group what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIAdvantage Group, BellSouth shall provide PLI Advantage Group with a list of the customer data items, which PLI Advantage Group would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Advantage Group data to the LIDB shall be solely at the direction of PLIAdvantage Group. Such direction from PLI Advantage Group will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Advantage Group data upon Advantage Group’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Advantage Group customer records will be missing from LIDB, as measured by PLI Advantage Group audits. BellSouth will audit PLI Advantage Group records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Advantage Group contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Advantage Group within one (1) business day of audit. Once reconciled records are received back from PLIAdvantage Group, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Advantage Group to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIAdvantage Group’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Advantage Group with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Advantage Group and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Advantage Group data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Advantage Group in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Advantage Group performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Advantage Group at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Advantage Group the screening information associated with LIDB Data Screening of PLI Advantage Group data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Advantage Group under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Advantage Group customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Metro Teleconnect any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIMetro Teleconnect’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Metro Teleconnect what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIMetro Teleconnect, BellSouth shall provide PLI Metro Teleconnect with a list of the customer data items, which PLI Metro Teleconnect would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Metro Teleconnect data to the LIDB shall be solely at the direction of PLIMetro Teleconnect. Such direction from PLI Metro Teleconnect will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-auto- deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Metro Teleconnect data upon Metro Teleconnect’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Metro Teleconnect customer records will be missing from LIDB, as measured by PLI Metro Teleconnect audits. BellSouth will audit PLI Metro Teleconnect records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Metro Teleconnect contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Metro Teleconnect within one (1) business day of audit. Once reconciled records are received back from PLIMetro Teleconnect, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Metro Teleconnect to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIMetro Teleconnect’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Metro Teleconnect with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Metro Teleconnect and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Metro Teleconnect data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Metro Teleconnect in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Metro Teleconnect performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Metro Teleconnect at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Metro Teleconnect the screening information associated with LIDB Data Screening of PLI Metro Teleconnect data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Metro Teleconnect under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Metro Teleconnect customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI GSC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIGSC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI GSC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIGSC, BellSouth shall provide PLI GSC with a list of the customer data items, which PLI GSC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI GSC data to the LIDB shall be solely at the direction of PLIGSC. Such direction from PLI GSC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇GSC data upon GSC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI GSC customer records will be missing from LIDB, as measured by PLI GSC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI GSC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI GSC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI GSC within one (1) business day of audit. Once reconciled records are received back from PLIGSC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI GSC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIGSC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI GSC with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI GSC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI GSC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI GSC in writing. 7.3.2.13 BellSouth shall provide PLI GSC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI GSC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI GSC the screening information associated with LIDB Data Screening of PLI GSC data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI GSC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI GSC customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI Seven Bridges any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLI’s Seven ▇▇▇▇▇▇▇’▇ customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Seven Bridges what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLISeven Bridges, BellSouth shall provide PLI Seven Bridges with a list of the customer data items, which PLI Seven Bridges would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI Seven Bridges data to the LIDB shall be solely at the direction of PLISeven Bridges. Such direction from PLI Seven Bridges will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ Seven Bridges data upon Seven ▇▇▇▇ ▇▇▇▇’▇ ▇▇▇’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Seven Bridges customer records will be missing from LIDB, as measured by PLI Seven Bridges audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit PLI Seven Bridges records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Seven Bridges contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI Seven Bridges within one (1) business day of audit. Once reconciled records are received back from PLISeven Bridges, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth ▇▇▇▇▇▇▇▇▇ will contact PLI Seven ▇▇▇▇▇▇▇ to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLI’s Seven ▇▇▇▇▇▇▇’▇ data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth ▇▇▇▇▇▇▇▇▇ performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI Seven Bridges with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Seven Bridges and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI Seven Bridges data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Seven ▇▇▇▇▇▇▇ in writing. 7.3.2.13 BellSouth shall provide PLI Seven Bridges performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Seven Bridges at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Seven Bridges the screening information associated with LIDB Data Screening of PLI Seven Bridges data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Seven Bridges under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI Seven Bridges customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI BCFL any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLIBCFL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI BCFL what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLIBCFL, BellSouth shall provide PLI BCFL with a list of the customer data items, which PLI BCFL would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI BCFL data to the LIDB shall be solely at the direction of PLIBCFL. Such direction from PLI BCFL will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇BCFL data upon BCFL’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI BCFL customer records will be missing from LIDB, as measured by PLI BCFL audits. BellSouth will audit PLI BCFL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI BCFL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI BCFL within one (1) business day of audit. Once reconciled records are received back from PLIBCFL, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI BCFL to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLIBCFL’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI BCFL with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI BCFL and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI BCFL data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI BCFL in writing. 7.3.2.13 BellSouth shall provide PLI BCFL performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI BCFL at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI BCFL the screening information associated with LIDB Data Screening of PLI BCFL data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI BCFL under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI BCFL customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI AirCover any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIAirCover’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI AirCover what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIAirCover, BellSouth shall provide PLI AirCover with a list of the customer data items, which PLI AirCover would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI AirCover data to the LIDB shall be solely at the direction of PLIAirCover. Such direction from PLI AirCover will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇AirCover data upon AirCover’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI AirCover customer records will be missing from LIDB, as measured by PLI AirCover audits. BellSouth will audit PLI AirCover records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI AirCover contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI AirCover within one (1) business day of audit. Once reconciled records are received back from PLIAirCover, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI AirCover to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIAirCover’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI AirCover with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI AirCover and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI AirCover data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI AirCover in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI AirCover performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI AirCover at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI AirCover the screening information associated with LIDB Data Screening of PLI AirCover data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI AirCover under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI AirCover customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Micro-Comm any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLIMicro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Micro-Comm what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLIMicro-Comm, BellSouth shall provide PLI Micro-Comm with a list of the customer data items, which PLI Micro-Comm would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Micro-Comm data to the LIDB shall be solely at the direction of PLIMicro-Comm. Such direction from PLI Micro-Comm will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Micro-Comm data upon Micro-Comm’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Micro- Comm customer records will be missing from LIDB, as measured by PLI Micro-Comm audits. BellSouth will audit PLI Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Micro-Comm within one (1) business day of audit. Once reconciled records are received back from PLIMicro-Comm, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Micro-Comm to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLIMicro-Comm’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Micro-Comm with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Micro-Comm and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Micro-Comm data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Micro-Comm in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Micro-Comm performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Micro-Comm the screening information associated with LIDB Data Screening of PLI Micro-Comm data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Micro-Comm under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Micro-Comm customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI TeleConex any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLITeleConex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI TeleConex what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLITeleConex, BellSouth shall provide PLI TeleConex with a list of the customer data items, which PLI TeleConex would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI TeleConex data to the LIDB shall be solely at the direction of PLITeleConex. Such direction from PLI TeleConex will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇TeleConex data upon TeleConex’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI TeleConex customer records will be missing from LIDB, as measured by PLI TeleConex audits. BellSouth will audit PLI TeleConex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI TeleConex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI TeleConex within one (1) business day of audit. Once reconciled records are received back from PLITeleConex, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI TeleConex to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLITeleConex’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI TeleConex with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI TeleConex and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI TeleConex data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI TeleConex in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI TeleConex performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI TeleConex at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI TeleConex the screening information associated with LIDB Data Screening of PLI TeleConex data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI TeleConex under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI TeleConex customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI TWTC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLITWTC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI TWTC what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLITWTC, BellSouth shall provide PLI TWTC with a list of the customer data items, which PLI TWTC would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI TWTC data to the LIDB shall be solely at the direction of PLITWTC. Such direction from PLI TWTC will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇TWTC data upon TWTC’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI TWTC customer records will be missing from LIDB, as measured by PLI TWTC audits. BellSouth will audit PLI TWTC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI TWTC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI TWTC within one (1) business day of audit. Once reconciled records are received back from PLITWTC, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI TWTC to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLITWTC’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI TWTC with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI TWTC and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI TWTC data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI TWTC in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI TWTC performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI TWTC at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI TWTC the screening information associated with LIDB Data Screening of PLI TWTC data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI TWTC under the BFR/NBR Process as set forth in Attachment 11process. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI TWTC customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLICBX One-Stop’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CBX One-Stop what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLICBX One-Stop, BellSouth shall provide PLI CBX One-Stop with a list of the customer data items, which PLI CBX One-Stop would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI CBX One-Stop data to the LIDB shall be solely at the direction of PLICBX One-Stop. Such direction from PLI CBX One-Stop will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CBX One-Stop data upon CBX One-Stop’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CBX One-Stop customer records will be missing from LIDB, as measured by PLI CBX One- Stop audits. BellSouth will audit PLI CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI CBX One-Stop contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from PLICBX One-Stop, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI CBX One-Stop to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLICBX One-Stop’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI CBX One-Stop with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI CBX One-Stop and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI CBX One-Stop data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI CBX One-Stop in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI CBX One-Stop performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CBX One-Stop the screening information associated with LIDB Data Screening of PLI CBX One-Stop data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CBX One-Stop under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI CBX One-Stop customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to PLI Lightning Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process PLILightning Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI Lightning Communications what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 9.2.3 Within two (2) weeks after a request by PLILightning Communications, BellSouth shall provide PLI Lightning Communications with a list of the customer data items, which PLI Lightning Communications would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 9.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 9.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 9.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 9.2.7 All additions, updates and deletions of PLI Lightning Communications data to the LIDB shall be solely at the direction of PLILightning Communications. Such direction from PLI Lightning Communications will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 9.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇Lightning Communications data upon Lightning Communications’s request (e.g., to support fraud detection), via password-protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI Lightning Communications customer records will be missing from LIDB, as measured by PLI Lightning Communications audits. BellSouth will audit PLI Lightning Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI Lightning Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to PLI Lightning Communications within one (1) business day of audit. Once reconciled records are received back from PLILightning Communications, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. 1:00PM Central Time. If more than 500 records are received, BellSouth will contact PLI Lightning Communications to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 9.2.10 BellSouth shall perform backup and recovery of all of PLILightning Communications’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 9.2.11 BellSouth shall provide PLI Lightning Communications with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI Lightning Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of PLI Lightning Communications data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI Lightning Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide PLI Lightning Communications performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI Lightning Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI Lightning Communications the screening information associated with LIDB Data Screening of PLI Lightning Communications data in accordance with this requirement. BellSouth currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI Lightning Communications under the BFR/NBR Process process as set forth in Attachment 11. 7.3.2.14 9.2.14 BellSouth shall accept queries to LIDB associated with PLI Lightning Communications customer records and shall return responses in accordance with industry standards. 7.3.2.15 9.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 9.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) % of all messages under normal conditions as defined in industry standards.

Technical Requirements. 7.3.2.1 BellSouth will offer to PLI CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process PLICBX One-Stop’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to PLI CBX One-Stop what additional functions (if any) are performed by LIDB in the BellSouth network. 7.3.2.3 Within two (2) weeks after a request by PLICBX One-Stop, BellSouth shall provide PLI CBX One-Stop with a list of the customer data items, which PLI CBX One-Stop would have to provide in order to support each required LIDB function. The list shall indicate which data items are essential to LIDB function and which are required only to support certain services. For each data item, the list shall show the data formats, the acceptable values of the data item and the meaning of those values. 7.3.2.4 BellSouth shall provide LIDB systems for which operating deficiencies that would result in calls being blocked shall not exceed thirty (30) minutes per year. 7.3.2.5 BellSouth shall provide LIDB systems for which operating deficiencies that would not result in calls being blocked shall not exceed twelve (12) hours per year. 7.3.2.6 BellSouth shall provide LIDB systems for which the LIDB function shall be in overload no more than twelve (12) hours per year. 7.3.2.7 All additions, updates and deletions of PLI CBX One-Stop data to the LIDB shall be solely at the direction of PLICBX One-Stop. Such direction from PLI CBX One-Stop will not be required where the addition, update or deletion is necessary to perform standard fraud control measures (e.g., calling card auto-deactivation). 7.3.2.8 BellSouth shall provide priority updates to LIDB for ▇▇▇ ▇▇▇▇ ▇▇▇▇ ▇▇▇CBX One-Stop data upon CBX One-Stop’s request (e.g., to support fraud detection), via password-password- protected telephone card, facsimile, or electronic mail within one hour of notice from the established BellSouth contact. 7.3.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of PLI CBX One-Stop customer records will be missing from LIDB, as measured by PLI CBX One- Stop audits. BellSouth will audit PLI CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated PLI CBX One-Stop contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to PLI CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from PLICBX One-Stop, BellSouth will update LIDB the same business day if less than 500 records are received before 1:00 p.m. Central Time. If more than 500 records are received, BellSouth will contact PLI CBX One-Stop to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 BellSouth shall perform backup and recovery of all of PLICBX One-Stop’s data in LIDB including sending to LIDB all changes made since the date of the most recent backup copy, in at least the same time frame BellSouth performs backup and recovery of BellSouth data in LIDB for itself. Currently, BellSouth performs backups of the LIDB for itself on a weekly basis; and when a new software release is scheduled, a backup is performed prior to loading the new release. 7.3.2.11 BellSouth shall provide PLI CBX One-Stop with LIDB reports of data which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between PLI CBX One-Stop and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of PLI CBX One-Stop data in LIDB by BellSouth personnel that are outside of established administrative and fraud control personnel, or by any other Party that is not authorized by PLI CBX One-Stop in writing. 7.3.2.13 BellSouth shall provide PLI CBX One-Stop performance of the LIDB Data Screening function, which allows a LIDB to completely or partially deny specific query originators access to LIDB data owned by specific data owners, for Customer Data that is part of an NPA-NXX or ▇▇▇-0/1XX wholly or partially owned by PLI CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from PLI CBX One-Stop the screening information associated with LIDB Data Screening of PLI CBX One-Stop data in accordance with this requirement. BellSouth ▇▇▇▇▇▇▇▇▇ currently does not have LIDB Data Screening capabilities. When such capability is available, BellSouth shall offer it to PLI CBX One-Stop under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with PLI CBX One-Stop customer records and shall return responses in accordance with industry standards. 7.3.2.15 BellSouth shall provide mean processing time at the LIDB within 0.50 seconds under normal conditions as defined in industry standards. 7.3.2.16 BellSouth shall provide processing time at the LIDB within 1 second for ninety-nine percent (99%) of all messages under normal conditions as defined in industry standards.