Common use of Technical Requirements Clause in Contracts

Technical Requirements. 7.3.2.1 BellSouth will offer to MRC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to 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 MRC, BellSouth shall provide MRC with a list of the customer data items, which 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 MRC data to the LIDB shall be solely at the direction of MRC. Such direction from 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 MRC customer records will be missing from LIDB, as measured by MRC audits. BellSouth will audit MRC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC within one (1) business day of audit. Once reconciled records are received back from MRC, 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 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 MRC’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 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 MRC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of 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 MRC in writing. 7.3.2.13 BellSouth shall provide 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 MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC the screening information associated with LIDB Data Screening of 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 MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with 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 MRC 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 MRCUS 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 MRC 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 MRCUS LEC, BellSouth shall provide MRC US LEC with a list of the customer data items, items which MRC 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 MRC US LEC data to the LIDB shall be solely at the direction of MRCUS LEC. Such direction from MRC 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 MRC US LEC data upon MRCUS 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 MRC US LEC customer records will be missing from LIDB, as measured by MRC US LEC audits. BellSouth will audit MRC US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated MRC 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 MRC US LEC within one (1) business day of audit. Once reconciled records are received back from MRCUS 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 MRC 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 MRCUS 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 MRC 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 MRC US LEC and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of MRC 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 MRC US LEC in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide MRC 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 MRC US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC US LEC the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC AFN any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCAFN’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCAFN, BellSouth shall provide MRC AFN with a list of the customer data items, which MRC 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 MRC AFN data to the LIDB shall be solely at the direction of MRCAFN. Such direction from MRC 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 MRC AFN data upon MRCAFN’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 MRC AFN customer records will be missing from LIDB, as measured by MRC AFN audits. BellSouth will audit MRC AFN records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC AFN contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC AFN within one (1) business day of audit. Once reconciled records are received back from MRCAFN, 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 MRC 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 MRCAFN’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 MRC 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 MRC AFN and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC AFN in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC AFN at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC AFN the screening information associated with LIDB Data Screening of MRC 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 MRC AFN under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC ITC^DeltaCom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCITC^DeltaCom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCITC^DeltaCom, BellSouth shall provide MRC ITC^DeltaCom with a list of the customer data items, which MRC 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 MRC ITC^DeltaCom data to the LIDB shall be solely at the direction of MRCITC^DeltaCom. Such direction from MRC 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 MRC ITC^DeltaCom data upon MRCITC^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 MRC ITC^DeltaCom customer records will be missing from LIDB, as measured by MRC ITC^DeltaCom audits. BellSouth will audit MRC ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC ITC^DeltaCom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from MRCITC^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 MRC 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 MRCITC^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 MRC 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 MRC ITC^DeltaCom and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC ITC^DeltaCom in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ITC^DeltaCom the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCITC^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 MRC 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 MRCITC^DeltaCom, BellSouth shall provide MRC ITC^DeltaCom with a list of the customer data items, items which MRC 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 MRC ITC^DeltaCom data to the LIDB shall be solely at the direction of MRCITC^DeltaCom. Such direction from MRC 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 MRC ITC^DeltaCom data upon MRCITC^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 MRC ITC^DeltaCom customer records will be missing from LIDB, as measured by MRC ITC^DeltaCom audits. BellSouth will audit MRC ITC^DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated MRC 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 MRC ITC^DeltaCom within one (1) business day of audit. Once reconciled records are received back from MRCITC^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 MRC 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 MRCITC^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 MRC 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 MRC ITC^DeltaCom and BellSouth. 7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of MRC 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 MRC ITC^DeltaCom in writing. 7.3.2.13 15.4.2.12 BellSouth shall provide MRC 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 MRC ITC^DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ITC^DeltaCom the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC <customer_short_name> any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRC<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 MRC <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 MRC<customer_short_name>, BellSouth shall provide MRC <customer_short_name> with a list of the customer data items, which MRC <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 MRC <customer_short_name> data to the LIDB shall be solely at the direction of MRC<customer_short_name>. Such direction from MRC <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 MRC <customer_short_name> data upon MRC<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 MRC <customer_short_name> customer records will be missing from LIDB, as measured by MRC <customer_short_name> audits. BellSouth will audit MRC <customer_short_name> records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC <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 MRC <customer_short_name> within one (1) business day of audit. Once reconciled records are received back from MRC<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 MRC <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 MRC<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 MRC <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 MRC <customer_short_name> and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC <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 MRC <customer_short_name> in writing. 7.3.2.13 BellSouth shall provide MRC <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 MRC <customer_short_name> at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC <customer_short_name> the screening information associated with LIDB Data Screening of MRC <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 MRC <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 MRC <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 MRC PLI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCPLI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCPLI, BellSouth shall provide MRC PLI with a list of the customer data items, which MRC 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 MRC PLI data to the LIDB shall be solely at the direction of MRCPLI. Such direction from MRC 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 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 MRC PLI customer records will be missing from LIDB, as measured by MRC PLI audits. BellSouth will audit MRC PLI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC PLI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC PLI within one (1) business day of audit. Once reconciled records are received back from MRCPLI, 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 MRC 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 MRCPLI’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 MRC 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 MRC PLI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC PLI in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC PLI at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC PLI the screening information associated with LIDB Data Screening of MRC 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 MRC PLI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC Seven Bridges any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRC’s Seven ▇▇▇▇▇▇▇’▇ customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCSeven Bridges, BellSouth shall provide MRC Seven Bridges with a list of the customer data items, which MRC 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 MRC Seven Bridges data to the LIDB shall be solely at the direction of MRCSeven Bridges. Such direction from MRC 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 MRC Seven Bridges data upon MRC’s Seven ▇▇▇▇▇▇▇’▇ 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 MRC Seven Bridges customer records will be missing from LIDB, as measured by MRC Seven Bridges audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC Seven Bridges records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Seven Bridges contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Seven Bridges within one (1) business day of audit. Once reconciled records are received back from MRCSeven 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 MRC 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 MRC’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 MRC 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 MRC Seven Bridges and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Seven ▇▇▇▇▇▇▇ in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Seven Bridges at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Seven Bridges the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Micro-Comm any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCMicro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCMicro-Comm, BellSouth shall provide MRC Micro-Comm with a list of the customer data items, which MRC 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 MRC Micro-Comm data to the LIDB shall be solely at the direction of MRCMicro-Comm. Such direction from MRC 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 MRC Micro-Comm data upon MRCMicro-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 MRC Micro- Comm customer records will be missing from LIDB, as measured by MRC Micro-Comm audits. BellSouth will audit MRC Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Micro-Comm within one (1) business day of audit. Once reconciled records are received back from MRCMicro-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 MRC 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 MRCMicro-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 MRC 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 MRC Micro-Comm and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Micro-Comm in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Micro-Comm the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRC’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 MRC 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 MRCITC/\DeltaCom, BellSouth shall provide MRC ITC/\DeltaCom with a list of the customer data items, items which MRC 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 MRC ITC/\DeltaCom data to the LIDB shall be solely at the direction of MRCITC/\DeltaCom. Such direction from MRC 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 MRC ITC/\DeltaCom data upon MRC’s 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 MRC ITC/\DeltaCom customer records will be missing from LIDB, as measured by MRC ITC/\DeltaCom audits. BellSouth will audit MRC ITC/\DeltaCom records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated MRC 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 MRC ITC/\DeltaCom within one (1) business day of audit. Once reconciled records are received back from MRCITC/\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 MRC 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 MRC’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 MRC 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 MRC ITC/\DeltaCom and BellSouth. 7.3.2.12 15.4.2.11 BellSouth shall prevent any access to or use of MRC 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 MRC ITC/\DeltaCom in writing. 7.3.2.13 15.4.2.12 BellSouth shall provide MRC 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 MRC ITC/\DeltaCom at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ITC/\DeltaCom the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCEPICUS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCEPICUS, BellSouth shall provide MRC EPICUS with a list of the customer data items, which MRC 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 MRC EPICUS data to the LIDB shall be solely at the direction of MRCEPICUS. Such direction from MRC 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 MRC EPICUS data upon MRCEPICUS’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 MRC EPICUS customer records will be missing from LIDB, as measured by MRC EPICUS audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC EPICUS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC EPICUS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC EPICUS within one (1) business day of audit. Once reconciled records are received back from MRCEPICUS, 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 MRC 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 MRCEPICUS’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 MRC 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 MRC EPICUS and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC EPICUS in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC EPICUS at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC EPICUS the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCUnity Acquisition’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCUnity Acquisition, BellSouth shall provide MRC Unity Acquisition with a list of the customer data items, which MRC 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 MRC Unity Acquisition data to the LIDB shall be solely at the direction of MRCUnity Acquisition. Such direction from MRC 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 MRC Unity Acquisition data upon MRCUnity 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 MRC Unity Acquisition customer records will be missing from LIDB, as measured by MRC Unity Acquisition audits. BellSouth will audit MRC Unity Acquisition records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Unity Acquisition contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Unity Acquisition within one (1) business day of audit. Once reconciled records are received back from MRCUnity 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 MRC 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 MRCUnity 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 MRC 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 MRC Unity Acquisition and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Unity Acquisition in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Unity Acquisition at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Unity Acquisition the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC PBT any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCPBT’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCPBT, BellSouth shall provide MRC PBT with a list of the customer data items, which MRC 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 MRC PBT data to the LIDB shall be solely at the direction of MRCPBT. Such direction from MRC 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 MRC PBT data upon MRCPBT’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 MRC PBT customer records will be missing from LIDB, as measured by MRC PBT audits. BellSouth will audit MRC PBT records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC PBT contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC PBT within one (1) business day of audit. Once reconciled records are received back from MRCPBT, 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 MRC 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 MRCPBT’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 MRC 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 MRC PBT and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC PBT in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC PBT at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC PBT the screening information associated with LIDB Data Screening of MRC 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 MRC PBT under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC 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 MRCAdvantage Group’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCAdvantage Group, BellSouth shall provide MRC Advantage Group with a list of the customer data items, which MRC 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 MRC Advantage Group data to the LIDB shall be solely at the direction of MRCAdvantage Group. Such direction from MRC 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 MRC Advantage Group data upon MRCAdvantage 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 MRC Advantage Group customer records will be missing from LIDB, as measured by MRC Advantage Group audits. BellSouth will audit MRC Advantage Group records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Advantage Group contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Advantage Group within one (1) business day of audit. Once reconciled records are received back from MRCAdvantage 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 MRC 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 MRCAdvantage 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 MRC 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 MRC Advantage Group and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Advantage Group in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Advantage Group at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Advantage Group the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC FLATEL any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCFLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCFLATEL, BellSouth shall provide MRC FLATEL with a list of the customer data items, which MRC 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 MRC FLATEL data to the LIDB shall be solely at the direction of MRCFLATEL. Such direction from MRC 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 MRC FLATEL data upon MRCFLATEL’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 MRC FLATEL customer records will be missing from LIDB, as measured by MRC FLATEL audits. BellSouth will audit MRC FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC FLATEL within one (1) business day of audit. Once reconciled records are received back from MRCFLATEL, 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 MRC 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 MRCFLATEL’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 MRC 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 MRC FLATEL and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC FLATEL in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC FLATEL the screening information associated with LIDB Data Screening of MRC 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 MRC FLATEL under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCAmTel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCAmTel, BellSouth shall provide MRC AmTel with a list of the customer data items, which MRC 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 MRC AmTel data to the LIDB shall be solely at the direction of MRCAmTel. Such direction from MRC 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 MRC AmTel data upon MRCAmTel’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 MRC AmTel customer records will be missing from LIDB, as measured by MRC AmTel audits. BellSouth will audit MRC AmTel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC AmTel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC AmTel within one (1) business day of audit. Once reconciled records are received back from MRCAmTel, 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 MRC 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 MRCAmTel’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 MRC 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 MRC AmTel and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC AmTel in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC AmTel at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC AmTel the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 1.2.1 BellSouth also will offer to MRC 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 MRCCLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCLEC, BellSouth shall provide MRC CLEC with a list of the customer data items, items which MRC 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 MRC CLEC data to the LIDB shall be solely at the direction of MRCCLEC. Such direction from MRC 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 MRC CLEC data upon MRCCLEC’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 MRC CLEC customer records will be missing from LIDB, as measured by MRC CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated MRC 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 MRC CLEC within one (1) business day of audit. Once reconciled records are received back from MRCCLEC, 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 MRC 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 MRCCLEC’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 MRC 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 MRC CLEC and BellSouth. 7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CLEC in writing. 7.3.2.13 1.2.13.1 BellSouth shall provide MRC 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 MRC CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CLEC the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Telstar Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCTelstar Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCTelstar Communications, BellSouth shall provide MRC Telstar Communications with a list of the customer data items, which MRC 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 MRC Telstar Communications data to the LIDB shall be solely at the direction of MRCTelstar Communications. Such direction from MRC 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 MRC Telstar Communications data upon MRCTelstar 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 MRC Telstar Communications customer records will be missing from LIDB, as measured by MRC Telstar Communications audits. BellSouth will audit MRC Telstar Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Telstar Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Telstar Communications within one (1) business day of audit. Once reconciled records are received back from MRCTelstar 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 MRC 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 MRCTelstar 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 MRC 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 MRC Telstar Communications and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Telstar Communications in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Telstar Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Telstar Communications the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCComm South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCComm South, BellSouth shall provide MRC Comm South with a list of the customer data items, which MRC 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 MRC Comm South data to the LIDB shall be solely at the direction of MRCComm South. Such direction from MRC 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 MRC Comm South data upon MRCComm 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 MRC Comm South customer records will be missing from LIDB, as measured by MRC Comm South audits. BellSouth will audit MRC Comm South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Comm South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Comm South within one (1) business day of audit. Once reconciled records are received back from MRCComm 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 MRC 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 MRCComm 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 MRC 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 MRC Comm South and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Comm South in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Comm South at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Comm South the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC FPB any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCFPB’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCFPB, BellSouth shall provide MRC FPB with a list of the customer data items, which MRC 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 MRC FPB data to the LIDB shall be solely at the direction of MRCFPB. Such direction from MRC 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 MRC FPB data upon MRCFPB’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 MRC FPB customer records will be missing from LIDB, as measured by MRC FPB audits. BellSouth will audit MRC FPB records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC FPB contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC FPB within one (1) business day of audit. Once reconciled records are received back from MRCFPB, 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 MRC 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 MRCFPB’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 MRC 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 MRC FPB and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC FPB in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC FPB at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC FPB the screening information associated with LIDB Data Screening of MRC 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 MRC FPB under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC ONS any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCONS’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCONS, BellSouth shall provide MRC ONS with a list of the customer data items, which MRC 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 MRC ONS data to the LIDB shall be solely at the direction of MRCONS. Such direction from MRC 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 MRC ONS data upon MRCONS’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 MRC ONS customer records will be missing from LIDB, as measured by MRC ONS audits. BellSouth will audit MRC ONS records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC ONS contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC ONS within one (1) business day of audit. Once reconciled records are received back from MRCONS, 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 MRC 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 MRCONS’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 MRC 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 MRC ONS and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC ONS in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC ONS at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ONS the screening information associated with LIDB Data Screening of MRC 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 MRC ONS under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC Cinergy any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCinergy’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCinergy, BellSouth shall provide MRC Cinergy with a list of the customer data items, which MRC 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 MRC Cinergy data to the LIDB shall be solely at the direction of MRCCinergy. Such direction from MRC 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 MRC Cinergy data upon MRCCinergy’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 MRC Cinergy customer records will be missing from LIDB, as measured by MRC Cinergy audits. BellSouth will audit MRC Cinergy records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Cinergy contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Cinergy within one (1) business day of audit. Once reconciled records are received back from MRCCinergy, 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 MRC 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 MRCCinergy’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 MRC 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 MRC Cinergy and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Cinergy in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Cinergy at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Cinergy the screening information associated with LIDB Data Screening of MRC 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 MRC Cinergy under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC NGTelecom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCNGTelecom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCNGTelecom, BellSouth shall provide MRC NGTelecom with a list of the customer data items, which MRC 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 MRC NGTelecom data to the LIDB shall be solely at the direction of MRCNGTelecom. Such direction from MRC 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 MRC NGTelecom data upon MRCNGTelecom’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 MRC NGTelecom customer records will be missing from LIDB, as measured by MRC NGTelecom audits. BellSouth will audit MRC NGTelecom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC NGTelecom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC NGTelecom within one (1) business day of audit. Once reconciled records are received back from MRCNGTelecom, 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 MRC 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 MRC’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 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 MRC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of 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 MRC in writing. 7.3.2.13 BellSouth shall provide 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 MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC the screening information associated with LIDB Data Screening of 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 MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with 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.three

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to MRC 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 MRCRent-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 MRC 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 MRCRent-A-Line, BellSouth shall provide MRC Rent-A-Line with a list of the customer data items, which MRC 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 MRC Rent-A-Line data to the LIDB shall be solely at the direction of MRCRent-A-Line. Such direction from MRC 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 MRC Rent-A-Line data upon MRCRent- 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 MRC Rent-A- Line customer records will be missing from LIDB, as measured by MRC Rent-A-Line audits. BellSouth will audit MRC Rent-A-Line records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC 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 MRC Rent-A-Line within one (1) business day of audit. Once reconciled records are received back from MRCRent-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 MRC 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 MRCRent-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 MRC 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 MRC Rent-A-Line and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Rent-A-Line in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Rent-A-Line at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Rent-A-Line the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCTeleConex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCTeleConex, BellSouth shall provide MRC TeleConex with a list of the customer data items, which MRC 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 MRC TeleConex data to the LIDB shall be solely at the direction of MRCTeleConex. Such direction from MRC 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 MRC TeleConex data upon MRCTeleConex’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 MRC TeleConex customer records will be missing from LIDB, as measured by MRC TeleConex audits. BellSouth will audit MRC TeleConex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC TeleConex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC TeleConex within one (1) business day of audit. Once reconciled records are received back from MRCTeleConex, 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 MRC 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 MRCTeleConex’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 MRC 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 MRC TeleConex and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC TeleConex in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC TeleConex at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC TeleConex the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC FeroNetworks any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCFeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCFeroNetworks, BellSouth shall provide MRC FeroNetworks with a list of the customer data items, which MRC 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 MRC FeroNetworks data to the LIDB shall be solely at the direction of MRCFeroNetworks. Such direction from MRC 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 MRC FeroNetworks data upon MRCFeroNetworks’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 MRC FeroNetworks customer records will be missing from LIDB, as measured by MRC FeroNetworks audits. BellSouth will audit MRC FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC FeroNetworks within one (1) business day of audit. Once reconciled records are received back from MRCFeroNetworks, 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 MRC 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 MRCFeroNetworks’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 MRC 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 MRC FeroNetworks and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC FeroNetworks in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC FeroNetworks the screening information associated with LIDB Data Screening of MRC 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 MRC FeroNetworks under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC BTI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCBTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCBTI, BellSouth shall provide MRC BTI with a list of the customer data items, which MRC 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 MRC BTI data to the LIDB shall be solely at the direction of MRCBTI. Such direction from MRC 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 MRC BTI data upon MRCBTI’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 MRC BTI customer records will be missing from LIDB, as measured by MRC BTI audits. BellSouth will audit MRC BTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC BTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC BTI within one (1) business day of audit. Once reconciled records are received back from MRCBTI, 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 MRC 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 MRCBTI’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 MRC 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 MRC BTI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC BTI in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC BTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC BTI the screening information associated with LIDB Data Screening of MRC 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 MRC BTI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC U-Dial any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCU-Dial’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCU-Dial, BellSouth shall provide MRC U-Dial with a list of the customer data items, which MRC 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 MRC U-Dial data to the LIDB shall be solely at the direction of MRCU-Dial. Such direction from MRC 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 MRC U-Dial data upon MRCU-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 MRC U-Dial customer records will be missing from LIDB, as measured by MRC U-Dial audits. BellSouth will audit MRC U-Dial records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC U-Dial contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC U-Dial within one (1) business day of audit. Once reconciled records are received back from MRCU-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 MRC 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 MRCU-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 MRC 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 MRC U-Dial and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC U-Dial in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC U-Dial at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC U-Dial the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCGateway’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCGateway, BellSouth shall provide MRC Gateway with a list of the customer data items, which MRC 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 MRC Gateway data to the LIDB shall be solely at the direction of MRCGateway. Such direction from MRC 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 MRC Gateway data upon MRCGateway’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 MRC Gateway customer records will be missing from LIDB, as measured by MRC Gateway audits. BellSouth will audit MRC Gateway records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Gateway contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Gateway within one (1) business day of audit. Once reconciled records are received back from MRCGateway, 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 MRC 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 MRCGateway’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 MRC 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 MRC Gateway and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Gateway in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Gateway at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Gateway the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCOptiLink’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCOptiLink, BellSouth shall provide MRC OptiLink with a list of the customer data items, items which MRC 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 MRC OptiLink data to the LIDB shall be solely at the direction of MRCOptiLink. Such direction from MRC 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 MRC OptiLink data upon MRCOptiLink’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 MRC OptiLink customer records will be missing from LIDB, as measured by MRC OptiLink audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC OptiLink records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated MRC 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 MRC OptiLink within one (1) business day of audit. Once reconciled records are received back from MRCOptiLink, 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 MRC 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 MRCOptiLink’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 MRC 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 MRC OptiLink and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of MRC 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 MRC OptiLink in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide MRC 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 MRC OptiLink at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC OptiLink the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC CCI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCCI, BellSouth shall provide MRC CCI with a list of the customer data items, which MRC 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 MRC CCI data to the LIDB shall be solely at the direction of MRCCCI. Such direction from MRC 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 MRC CCI data upon MRCCCI’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 MRC CCI customer records will be missing from LIDB, as measured by MRC CCI audits. BellSouth will audit MRC CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC CCI within one (1) business day of audit. Once reconciled records are received back from MRCCCI, 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 MRC 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 MRCCCI’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 MRC 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 MRC CCI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CCI in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CCI the screening information associated with LIDB Data Screening of MRC 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 MRC CCI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC 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 MRCCLEC’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCLEC, BellSouth shall provide MRC CLEC with a list of the customer data items, items which MRC 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 MRC CLEC data to the LIDB shall be solely at the direction of MRCCLEC. Such direction from MRC 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 MRC CLEC data upon MRCCLEC’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 MRC CLEC customer records will be missing from LIDB, as measured by MRC CLEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC CLEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches mis-matches and provide this data to a designated MRC 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 MRC CLEC within one (1) business day of audit. Once reconciled records are received back from MRCCLEC, 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 MRC 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 MRCCLEC’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 MRC 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 MRC CLEC and BellSouth. 7.3.2.12 1.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CLEC in writing. 7.3.2.13 1.2.13.1 BellSouth shall provide MRC 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 MRC CLEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CLEC the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCCBX 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 MRC 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 MRCCBX One-Stop, BellSouth shall provide MRC CBX One-Stop with a list of the customer data items, which MRC 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 MRC CBX One-Stop data to the LIDB shall be solely at the direction of MRCCBX One-Stop. Such direction from MRC 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 MRC CBX One-Stop data upon MRCCBX 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 MRC CBX One-Stop customer records will be missing from LIDB, as measured by MRC CBX One- Stop audits. BellSouth will audit MRC CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC 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 MRC CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from MRCCBX 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 MRC 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 MRCCBX 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 MRC 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 MRC CBX One-Stop and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CBX One-Stop in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CBX One-Stop the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCLightning Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCLightning Communications, BellSouth shall provide MRC Lightning Communications with a list of the customer data items, which MRC 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 MRC Lightning Communications data to the LIDB shall be solely at the direction of MRCLightning Communications. Such direction from MRC 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 MRC Lightning Communications data upon MRCLightning 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 MRC Lightning Communications customer records will be missing from LIDB, as measured by MRC Lightning Communications audits. BellSouth will audit MRC Lightning Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Lightning Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Lightning Communications within one (1) business day of audit. Once reconciled records are received back from MRCLightning 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 MRC 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 MRCLightning 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 MRC 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 MRC Lightning Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Lightning Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Lightning Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Lightning Communications the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Think 12 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCThink 12’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCThink 12, BellSouth shall provide MRC Think 12 with a list of the customer data items, which MRC 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 MRC Think 12 data to the LIDB shall be solely at the direction of MRCThink 12. Such direction from MRC 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 MRC Think 12 data upon MRCThink 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 MRC Think 12 customer records will be missing from LIDB, as measured by MRC Think 12 audits. BellSouth will audit MRC Think 12 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Think 12 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Think 12 within one (1) business day of audit. Once reconciled records are received back from MRCThink 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 MRC 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 MRCThink 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 MRC 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 MRC Think 12 and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Think 12 in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Think 12 at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Think 12 the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCNex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCNex-Phon, BellSouth shall provide MRC Nex- Phon with a list of the customer data items, which MRC 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 MRC Nex-Phon data to the LIDB shall be solely at the direction of MRCNex-Phon. Such direction from MRC 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 MRC Nex-Phon data upon MRCNex- 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 MRC Nex-Phon customer records will be missing from LIDB, as measured by MRC Nex-Phon audits. BellSouth will audit MRC Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Nex-Phon within one (1) business day of audit. Once reconciled records are received back from MRCNex-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 MRC 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 MRCNex-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 MRC 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 MRC Nex-Phon and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Nex-Phon in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Nex-Phon the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC US South any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCUS South’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCUS South, BellSouth shall provide MRC US South with a list of the customer data items, which MRC 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 MRC US South data to the LIDB shall be solely at the direction of MRCUS South. Such direction from MRC 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 MRC US South data upon MRCUS 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 MRC US South customer records will be missing from LIDB, as measured by MRC US South audits. BellSouth will audit MRC US South records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC US South contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC US South within one (1) business day of audit. Once reconciled records are received back from MRCUS 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 MRC 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 MRC’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 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 MRC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of 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 MRC in writing. 7.3.2.13 BellSouth shall provide 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 MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC the screening information associated with LIDB Data Screening of 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 MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with 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.three

Technical Requirements. 7.3.2.1 BellSouth will offer to MRC Kinetix any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCKinetix’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCKinetix, BellSouth shall provide MRC Kinetix with a list of the customer data items, which MRC 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 MRC Kinetix data to the LIDB shall be solely at the direction of MRCKinetix. Such direction from MRC 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 MRC Kinetix data upon MRCKinetix’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 MRC Kinetix customer records will be missing from LIDB, as measured by MRC Kinetix audits. BellSouth will audit MRC Kinetix records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Kinetix contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Kinetix within one (1) business day of audit. Once reconciled records are received back from MRCKinetix, 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 MRC 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 MRCKinetix’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 MRC 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 MRC Kinetix and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Kinetix in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Kinetix at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Kinetix the screening information associated with LIDB Data Screening of MRC 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 MRC Kinetix under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCNexus’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCNexus, BellSouth shall provide MRC Nexus with a list of the customer data items, which MRC 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 MRC Nexus data to the LIDB shall be solely at the direction of MRCNexus. Such direction from MRC 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 MRC Nexus data upon MRCNexus’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 MRC Nexus customer records will be missing from LIDB, as measured by MRC Nexus audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC Nexus records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Nexus contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Nexus within one (1) business day of audit. Once reconciled records are received back from MRCNexus, 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 MRC 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 MRCNexus’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 MRC 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 MRC Nexus and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Nexus in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Nexus at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Nexus the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCMyLineToo’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCMyLineToo, BellSouth shall provide MRC MyLineToo with a list of the customer data items, which MRC 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 MRC MyLineToo data to the LIDB shall be solely at the direction of MRCMyLineToo. Such direction from MRC 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 MRC MyLineToo data upon MRCMyLineToo’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 MRC MyLineToo customer records will be missing from LIDB, as measured by MRC MyLineToo audits. BellSouth will audit MRC MyLineToo records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC MyLineToo contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC MyLineToo within one (1) business day of audit. Once reconciled records are received back from MRCMyLineToo, 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 MRC 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 MRCMyLineToo’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 MRC 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 MRC MyLineToo and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC MyLineToo in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC MyLineToo at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC MyLineToo the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCTriarch Marketing’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCTriarch Marketing, BellSouth shall provide MRC Triarch Marketing with a list of the customer data items, which MRC 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 MRC Triarch Marketing data to the LIDB shall be solely at the direction of MRCTriarch Marketing. Such direction from MRC 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 MRC Triarch Marketing data upon MRCTriarch 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 MRC Triarch Marketing customer records will be missing from LIDB, as measured by MRC Triarch Marketing audits. BellSouth will audit MRC Triarch Marketing records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Triarch Marketing contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Triarch Marketing within one (1) business day of audit. Once reconciled records are received back from MRCTriarch 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 MRC 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 MRCTriarch 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 MRC 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 MRC Triarch Marketing and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Triarch Marketing in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Triarch Marketing at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Triarch Marketing the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Excel PCHP any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCExcel PCHP’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCExcel PCHP, BellSouth shall provide MRC Excel PCHP with a list of the customer data items, which MRC 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 MRC Excel PCHP data to the LIDB shall be solely at the direction of MRCExcel PCHP. Such direction from MRC 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 MRC Excel PCHP data upon MRCExcel 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 MRC Excel PCHP customer records will be missing from LIDB, as measured by MRC Excel PCHP audits. BellSouth will audit MRC Excel PCHP records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Excel PCHP contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Excel PCHP within one (1) business day of audit. Once reconciled records are received back from MRCExcel 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 MRC 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 MRCExcel 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 MRC 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 MRC Excel PCHP and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Excel PCHP in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Excel PCHP at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Excel PCHP the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRC▇▇▇▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCGrande, BellSouth shall provide MRC Grande with a list of the customer data items, which MRC 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 MRC Grande data to the LIDB shall be solely at the direction of MRCGrande. Such direction from MRC 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 MRC Grande data upon MRCGrande’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 MRC Grande customer records will be missing from LIDB, as measured by MRC Grande audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC Grande records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Grande contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Grande within one (1) business day of audit. Once reconciled records are received back from MRCGrande, 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 MRC 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 MRCGrande’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 MRC 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 MRC Grande and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Grande in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Grande at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Grande the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCCOMTECH21’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCOMTECH21, BellSouth shall provide MRC COMTECH21 with a list of the customer data items, which MRC 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 MRC COMTECH21 data to the LIDB shall be solely at the direction of MRCCOMTECH21. Such direction from MRC 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 MRC COMTECH21 data upon MRCCOMTECH21’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 MRC COMTECH21 customer records will be missing from LIDB, as measured by MRC COMTECH21 audits. BellSouth will audit MRC COMTECH21 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC COMTECH21 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC COMTECH21 within one (1) business day of audit. Once reconciled records are received back from MRCCOMTECH21, 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 MRC 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 MRCCOMTECH21’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 MRC 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 MRC COMTECH21 and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC COMTECH21 in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC COMTECH21 at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC COMTECH21 the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC Quality Telephone any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCQuality Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCQuality Telephone, BellSouth shall provide MRC Quality Telephone with a list of the customer data items, which MRC 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 MRC Quality Telephone data to the LIDB shall be solely at the direction of MRCQuality Telephone. Such direction from MRC 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 MRC Quality Telephone data upon MRCQuality 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 MRC Quality Telephone customer records will be missing from LIDB, as measured by MRC Quality Telephone audits. BellSouth will audit MRC Quality Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Quality Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Quality Telephone within one (1) business day of audit. Once reconciled records are received back from MRCQuality 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 MRC 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 MRCQuality 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 MRC 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 MRC Quality Telephone and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Quality Telephone in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Quality Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Quality Telephone the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC Nex-Phon any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCNex-Phon’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCNex-Phon, BellSouth shall provide MRC Nex- Phon with a list of the customer data items, which MRC 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 MRC Nex-Phon data to the LIDB shall be solely at the direction of MRCNex-Phon. Such direction from MRC 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 MRC Nex-Phon data upon MRCNex- 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 MRC Nex-Phon customer records will be missing from LIDB, as measured by MRC Nex-Phon audits. BellSouth will audit MRC Nex-Phon records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Nex-Phon contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Nex-Phon within one (1) business day of audit. Once reconciled records are received back from MRCNex-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 MRC 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 MRCNex-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 MRC 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 MRC Nex-Phon and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Nex-Phon in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Nex-Phon at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Nex-Phon the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC ▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process MRC▇▇▇.▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC ▇▇▇.▇▇▇ 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 MRC▇▇▇.▇▇▇, BellSouth shall provide MRC ▇▇▇.▇▇▇ with a list of the customer data items, which 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 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 MRC ▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of MRC▇▇▇.▇▇▇. Such direction from 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 9.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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of MRC ▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by MRC ▇▇▇.▇▇▇ audits. BellSouth will audit MRC ▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC ▇▇▇.▇▇▇ contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC ▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from MRC▇▇▇.▇▇▇, 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 MRC ▇▇▇.▇▇▇ 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 MRC▇▇▇.▇▇▇’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 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 MRC ▇▇▇.▇▇▇ and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of 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 MRC ▇▇▇.▇▇▇ in writing. 7.3.2.13 9.2.13 BellSouth shall provide 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 MRC ▇▇▇.▇▇▇ at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ▇▇▇.▇▇▇ the screening information associated with LIDB Data Screening of 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 MRC ▇▇▇.▇▇▇ 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 MRC ▇▇▇.▇▇▇ 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 MRC 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 MRCAirCover’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCAirCover, BellSouth shall provide MRC AirCover with a list of the customer data items, which MRC 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 MRC AirCover data to the LIDB shall be solely at the direction of MRCAirCover. Such direction from MRC 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 MRC AirCover data upon MRCAirCover’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 MRC AirCover customer records will be missing from LIDB, as measured by MRC AirCover audits. BellSouth will audit MRC AirCover records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC AirCover contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC AirCover within one (1) business day of audit. Once reconciled records are received back from MRCAirCover, 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 MRC 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 MRCAirCover’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 MRC 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 MRC AirCover and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC AirCover in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC AirCover at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC AirCover the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC Southern Telcom any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCSouthern Telcom’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC Southern Telcom 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 MRCSouthern Telcom, BellSouth shall provide MRC Southern Telcom with a list of the customer data items, which MRC Southern Telcom 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 MRC Southern Telcom data to the LIDB shall be solely at the direction of MRCSouthern Telcom. Such direction from MRC Southern Telcom 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 Southern Telcom data upon MRCSouthern Telcom’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 MRC Southern Telcom customer records will be missing from LIDB, as measured by MRC Southern Telcom audits. BellSouth will audit MRC Southern Telcom records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Southern Telcom contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Southern Telcom within one (1) business day of audit. Once reconciled records are received back from MRCSouthern Telcom, 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 MRC Southern Telcom 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 MRCSouthern Telcom’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 MRC Southern Telcom 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 MRC Southern Telcom and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC Southern Telcom 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 MRC Southern Telcom in writing. 7.3.2.13 BellSouth shall provide MRC Southern Telcom 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 MRC Southern Telcom at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Southern Telcom the screening information associated with LIDB Data Screening of MRC Southern Telcom 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 MRC Southern Telcom under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC Southern Telcom 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 MRC UTI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCUTI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCUTI, BellSouth shall provide MRC UTI with a list of the customer data items, which MRC 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 MRC UTI data to the LIDB shall be solely at the direction of MRCUTI. Such direction from MRC 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 MRC UTI data upon MRCUTI’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 MRC UTI customer records will be missing from LIDB, as measured by MRC UTI audits. BellSouth will audit MRC UTI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC UTI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC UTI within one (1) business day of audit. Once reconciled records are received back from MRCUTI, 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 MRC 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 MRCUTI’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 MRC 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 MRC UTI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC UTI in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC UTI at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC UTI the screening information associated with LIDB Data Screening of MRC 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 MRC UTI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCClearwave Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCClearwave Communications, BellSouth shall provide MRC Clearwave Communications with a list of the customer data items, which MRC 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 MRC Clearwave Communications data to the LIDB shall be solely at the direction of MRCClearwave Communications. Such direction from MRC 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 MRC Clearwave Communications data upon MRCClearwave 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 MRC Clearwave Communications customer records will be missing from LIDB, as measured by MRC Clearwave Communications audits. BellSouth will audit MRC Clearwave Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Clearwave Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Clearwave Communications within one (1) business day of audit. Once reconciled records are received back from MRCClearwave 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 MRC 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 MRCClearwave 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 MRC 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 MRC Clearwave Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Clearwave Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Clearwave Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Clearwave Communications the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Clearwave Communications any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCClearwave Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCClearwave Communications, BellSouth shall provide MRC Clearwave Communications with a list of the customer data items, which MRC 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 MRC Clearwave Communications data to the LIDB shall be solely at the direction of MRCClearwave Communications. Such direction from MRC 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 MRC Clearwave Communications data upon MRCClearwave 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 MRC Clearwave Communications customer records will be missing from LIDB, as measured by MRC Clearwave Communications audits. BellSouth will audit MRC Clearwave Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Clearwave Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Clearwave Communications within one (1) business day of audit. Once reconciled records are received back from MRCClearwave 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 MRC 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 MRCClearwave 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 MRC 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 MRC Clearwave Communications and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Clearwave Communications in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Clearwave Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Clearwave Communications the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC Preferred any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCPreferred’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCPreferred, BellSouth shall provide MRC Preferred with a list of the customer data items, which MRC 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 MRC Preferred data to the LIDB shall be solely at the direction of MRCPreferred. Such direction from MRC 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 MRC Preferred data upon MRCPreferred’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 MRC Preferred customer records will be missing from LIDB, as measured by MRC Preferred audits. BellSouth will audit MRC Preferred records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Preferred contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Preferred within one (1) business day of audit. Once reconciled records are received back from MRCPreferred, 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 MRC 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 MRCPreferred’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 MRC 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 MRC Preferred and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Preferred in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Preferred at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Preferred the screening information associated with LIDB Data Screening of MRC 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 MRC Preferred under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC 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 MRCUtility USA’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCUtility USA, BellSouth shall provide MRC Utility USA with a list of the customer data items, which MRC 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 MRC Utility USA data to the LIDB shall be solely at the direction of MRCUtility USA. Such direction from MRC 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 MRC Utility USA data upon MRCUtility 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 MRC Utility USA customer records will be missing from LIDB, as measured by MRC Utility USA audits. BellSouth will audit MRC Utility USA records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Utility USA contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Utility USA within one (1) business day of audit. Once reconciled records are received back from MRCUtility 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 MRC 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 MRCUtility 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 MRC 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 MRC Utility USA and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Utility USA in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Utility USA at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Utility USA the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCMicro-Comm’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCMicro-Comm, BellSouth shall provide MRC Micro-Comm with a list of the customer data items, which MRC 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 MRC Micro-Comm data to the LIDB shall be solely at the direction of MRCMicro-Comm. Such direction from MRC 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 MRC Micro-Comm data upon MRCMicro-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 MRC Micro- Comm customer records will be missing from LIDB, as measured by MRC Micro-Comm audits. BellSouth will audit MRC Micro-Comm records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Micro-Comm contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Micro-Comm within one (1) business day of audit. Once reconciled records are received back from MRCMicro-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 MRC 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 MRCMicro-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 MRC 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 MRC Micro-Comm and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Micro-Comm in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Micro-Comm at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Micro-Comm the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 8.2.1 BellSouth will offer to MRC DukeNet any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 8.2.2 BellSouth shall process MRCDukeNet’s customer Customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC DukeNet 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 MRCDukeNet, BellSouth shall provide MRC DukeNet with a list of the customer data items, which MRC DukeNet 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 MRC DukeNet data to the LIDB shall be solely at the direction of MRCDukeNet. Such direction from MRC DukeNet 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 8.2.8 BellSouth shall provide priority updates to LIDB for MRC DukeNet data upon MRCDukeNet’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 8.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of MRC DukeNet customer records will be missing from LIDB, as measured by MRC DukeNet audits. BellSouth will audit MRC DukeNet records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated MRC DukeNet contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches mis-matches to MRC DukeNet within one (1) business day of audit. Once reconciled records are received back from MRCDukeNet, 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 MRC DukeNet to negotiate a time frame for the updates, not to exceed three (3) business days. 7.3.2.10 8.2.10 BellSouth shall perform backup and recovery of all of MRCDukeNet’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 8.2.11 BellSouth shall provide MRC DukeNet with LIDB reports of data data, which are missing or contain errors, as well as any misrouted errors, within a reasonable time period as negotiated between MRC DukeNet and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of 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 MRC in writing. 7.3.2.13 BellSouth shall provide 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 MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC the screening information associated with LIDB Data Screening of 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 MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with 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 9.2.1 BellSouth will offer to MRC 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 MRCDPI Teleconnect’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCDPI Teleconnect, BellSouth shall provide MRC DPI Teleconnect with a list of the customer data items, which MRC 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 MRC DPI Teleconnect data to the LIDB shall be solely at the direction of MRCDPI Teleconnect. Such direction from MRC 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 MRC DPI Teleconnect data upon MRCDPI 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 MRC DPI Teleconnect customer records will be missing from LIDB, as measured by MRC DPI Teleconnect audits. BellSouth will audit MRC DPI Teleconnect records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC DPI Teleconnect contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC DPI Teleconnect within one (1) business day of audit. Once reconciled records are received back from MRCDPI 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 MRC 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 MRCDPI 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 MRC 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 MRC DPI Teleconnect and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC DPI Teleconnect in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC DPI Teleconnect at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC DPI Teleconnect the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC CCI any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCCI’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCCI, BellSouth shall provide MRC CCI with a list of the customer data items, which MRC 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 MRC CCI data to the LIDB shall be solely at the direction of MRCCCI. Such direction from MRC 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 MRC CCI data upon MRCCCI’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 MRC CCI customer records will be missing from LIDB, as measured by MRC CCI audits. BellSouth will audit MRC CCI records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC CCI contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC CCI within one (1) business day of audit. Once reconciled records are received back from MRCCCI, 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 MRC 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 MRCCCI’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 MRC 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 MRC CCI and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CCI in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC CCI at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CCI the screening information associated with LIDB Data Screening of MRC 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 MRC CCI under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCLevel 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCLevel 3, BellSouth shall provide MRC Level 3 with a list of the customer data items, which MRC 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 MRC Level 3 data to the LIDB shall be solely at the direction of MRCLevel 3. Such direction from MRC 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 MRC Level 3 data upon MRCLevel 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 MRC Level 3 customer records will be missing from LIDB, as measured by MRC Level 3 audits. BellSouth will audit MRC Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Level 3 within one (1) business day of audit. Once reconciled records are received back from MRCLevel 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 MRC 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 MRCLevel 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 MRC 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 MRC Level 3 and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Level 3 in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Level 3 the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCFeroNetworks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCFeroNetworks, BellSouth shall provide MRC FeroNetworks with a list of the customer data items, which MRC 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 MRC FeroNetworks data to the LIDB shall be solely at the direction of MRCFeroNetworks. Such direction from MRC 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 MRC FeroNetworks data upon MRCFeroNetworks’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 MRC FeroNetworks customer records will be missing from LIDB, as measured by MRC FeroNetworks audits. BellSouth will audit MRC FeroNetworks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC FeroNetworks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC FeroNetworks within one (1) business day of audit. Once reconciled records are received back from MRCFeroNetworks, 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 MRC 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 MRCFeroNetworks’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 MRC 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 MRC FeroNetworks and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC FeroNetworks in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC FeroNetworks at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC FeroNetworks the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC 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 MRCUS 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 MRC 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 MRCUS LEC, BellSouth shall provide MRC US LEC with a list of the customer data items, items which MRC 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 MRC US LEC data to the LIDB shall be solely at the direction of MRCUS LEC. Such direction from MRC 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 MRC US LEC data upon MRCUS 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 MRC US LEC customer records will be missing from LIDB, as measured by MRC US LEC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC US LEC records in LIDB against Data Base Administration System (DBAS) DBAS to identify record mismatches and provide this data to a designated MRC 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 MRC US LEC within one (1) business day of audit. Once reconciled records are received back from MRCUS 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 MRC 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 MRCUS 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 MRC 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 MRC US LEC and BellSouth. 7.3.2.12 13.4.2.11 BellSouth shall prevent any access to or use of MRC 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 MRC US LEC in writing. 7.3.2.13 13.4.2.12 BellSouth shall provide MRC 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 MRC US LEC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC US LEC the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Covad any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCovad’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRC▇▇▇▇▇, BellSouth shall provide MRC Covad with a list of the customer data items, which MRC 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 MRC Covad data to the LIDB shall be solely at the direction of MRCCovad. Such direction from MRC 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 MRC Covad data upon MRCCovad’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 MRC Covad customer records will be missing from LIDB, as measured by MRC Covad audits. BellSouth will audit MRC Covad records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Covad contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Covad within one (1) business day of audit. Once reconciled records are received back from MRCCovad, 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 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 MRCCovad’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 MRC 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 MRC Covad and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC ▇▇▇▇▇ in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Covad at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Covad the screening information associated with LIDB Data Screening of MRC 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 MRC Covad under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC 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 MRCFLATEL’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCFLATEL, BellSouth shall provide MRC FLATEL with a list of the customer data items, which MRC 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 MRC FLATEL data to the LIDB shall be solely at the direction of MRCFLATEL. Such direction from MRC 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 MRC FLATEL data upon MRCFLATEL’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 MRC FLATEL customer records will be missing from LIDB, as measured by MRC FLATEL audits. BellSouth will audit MRC FLATEL records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC FLATEL contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC FLATEL within one (1) business day of audit. Once reconciled records are received back from MRCFLATEL, 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 MRC 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 MRCFLATEL’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 MRC 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 MRC FLATEL and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC FLATEL in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC FLATEL at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC FLATEL the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCBX 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 MRC 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 MRCCBX One-Stop, BellSouth shall provide MRC CBX One-Stop with a list of the customer data items, which MRC 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 MRC CBX One-Stop data to the LIDB shall be solely at the direction of MRCCBX One-Stop. Such direction from MRC 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 MRC CBX One-Stop data upon MRCCBX 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 MRC CBX One-Stop customer records will be missing from LIDB, as measured by MRC CBX One- Stop audits. BellSouth will audit MRC CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC 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 MRC CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from MRCCBX 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 MRC 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 MRCCBX 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 MRC 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 MRC CBX One-Stop and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CBX One-Stop in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CBX One-Stop the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC ▇▇▇▇▇▇▇▇.▇▇▇ any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process MRC▇▇▇▇▇▇▇▇.▇▇▇’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC ▇▇▇▇▇▇▇▇.▇▇▇ 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 MRC▇▇▇▇▇▇▇▇.▇▇▇, BellSouth shall provide MRC ▇▇▇▇▇▇▇▇.▇▇▇ with a list of the customer data items, which 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 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 MRC ▇▇▇▇▇▇▇▇.▇▇▇ data to the LIDB shall be solely at the direction of MRC▇▇▇▇▇▇▇▇.▇▇▇. Such direction from 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 9.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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of MRC ▇▇▇▇▇▇▇▇.▇▇▇ customer records will be missing from LIDB, as measured by MRC ▇▇▇▇▇▇▇▇.▇▇▇ audits. BellSouth will audit MRC ▇▇▇▇▇▇▇▇.▇▇▇ records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC ▇▇▇▇▇▇▇▇.▇▇▇ contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC ▇▇▇▇▇▇▇▇.▇▇▇ within one (1) business day of audit. Once reconciled records are received back from MRC▇▇▇▇▇▇▇▇.▇▇▇, 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 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 MRC’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 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 MRC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of 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 MRC in writing. 7.3.2.13 BellSouth shall provide 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 MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC the screening information associated with LIDB Data Screening of 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 MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with 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.three

Technical Requirements. 7.3.2.1 9.2.1 BellSouth will offer to MRC 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 MRCMTS Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCMTS Communications, BellSouth shall provide MRC MTS Communications with a list of the customer data items, which MRC 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 MRC MTS Communications data to the LIDB shall be solely at the direction of MRCMTS Communications. Such direction from MRC 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 MRC MTS Communications data upon MRCMTS 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 MRC MTS Communications customer records will be missing from LIDB, as measured by MRC MTS Communications audits. BellSouth will audit MRC MTS Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC MTS Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC MTS Communications within one (1) business day of audit. Once reconciled records are received back from MRCMTS 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 MRC 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 MRCMTS 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 MRC 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 MRC MTS Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC MTS Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC MTS Communications at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC MTS Communications the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 8.2.1 BellSouth will offer to MRC 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 MRC’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 MRC 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 MRCGulfPines, BellSouth shall provide MRC GulfPines with a list of the customer data items, which MRC 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 MRC GulfPines data to the LIDB shall be solely at the direction of MRCGulfPines. Such direction from MRC 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 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 MRC customer records will be missing from LIDB, as measured by MRC audits. BellSouth will audit MRC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC within one (1) business day of audit. Once reconciled records are received back from MRC, 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 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 MRC’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 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 MRC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of 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 MRC in writing. 7.3.2.13 BellSouth shall provide 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 MRC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC the screening information associated with LIDB Data Screening of 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 MRC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with 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 MRC Level 3 any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCLevel 3’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRC▇▇▇▇▇ ▇, BellSouth ▇▇▇▇▇▇▇▇▇ shall provide MRC Level 3 with a list of the customer data items, which 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 MRC Level 3 data to the LIDB shall be solely at the direction of MRCLevel 3. Such direction from MRC 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 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 MRC Level 3 customer records will be missing from LIDB, as measured by MRC Level 3 audits. BellSouth will audit MRC Level 3 records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Level 3 contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Level 3 within one (1) business day of audit. Once reconciled records are received back from MRC▇▇▇▇▇ ▇, 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 MRC 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 MRCLevel 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 MRC 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 MRC Level 3 and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Level 3 in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Level 3 at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Level 3 the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC Covad any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCovad’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCCovad, BellSouth shall provide MRC Covad with a list of the customer data items, which MRC 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 MRC Covad data to the LIDB shall be solely at the direction of MRCCovad. Such direction from MRC 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 MRC Covad data upon MRCCovad’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 MRC Covad customer records will be missing from LIDB, as measured by MRC Covad audits. BellSouth will audit MRC Covad records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Covad contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Covad within one (1) business day of audit. Once reconciled records are received back from MRCCovad, 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 MRC 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 MRCCovad’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 MRC 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 MRC Covad and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Covad in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Covad at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Covad the screening information associated with LIDB Data Screening of MRC 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 MRC Covad under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC Pilgrim Telephone any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 9.2.2 BellSouth shall process MRCPilgrim Telephone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC Pilgrim Telephone 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 MRCPilgrim Telephone, BellSouth shall provide MRC Pilgrim Telephone with a list of the customer data items, which MRC Pilgrim 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 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 MRC Pilgrim Telephone data to the LIDB shall be solely at the direction of MRCPilgrim Telephone. Such direction from MRC Pilgrim 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 9.2.8 BellSouth shall provide priority updates to LIDB for MRC Pilgrim Telephone data upon MRCPilgrim 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 9.2.9 BellSouth shall provide LIDB systems such that no more than 0.01% of MRC Pilgrim Telephone customer records will be missing from LIDB, as measured by MRC Pilgrim Telephone audits. BellSouth will audit MRC Pilgrim Telephone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Pilgrim Telephone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC Pilgrim Telephone within one (1) business day of audit. Once reconciled records are received back from MRCPilgrim Telephone, 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 MRC Pilgrim Telephone 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 MRCPilgrim 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 9.2.11 BellSouth shall provide MRC Pilgrim 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 MRC Pilgrim Telephone and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC Pilgrim 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 MRC Pilgrim Telephone in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC Pilgrim 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 MRC Pilgrim Telephone at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Pilgrim Telephone the screening information associated with LIDB Data Screening of MRC Pilgrim 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 MRC Pilgrim Telephone 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 MRC Pilgrim Telephone 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 MRC GSC any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCGSC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCGSC, BellSouth shall provide MRC GSC with a list of the customer data items, which MRC 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 MRC GSC data to the LIDB shall be solely at the direction of MRCGSC. Such direction from MRC 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 MRC GSC data upon MRCGSC’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 MRC GSC customer records will be missing from LIDB, as measured by MRC GSC audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC GSC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC GSC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC GSC within one (1) business day of audit. Once reconciled records are received back from MRCGSC, 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 MRC 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 MRCGSC’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 MRC 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 MRC GSC and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC GSC in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC GSC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC GSC the screening information associated with LIDB Data Screening of MRC 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 MRC GSC under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCExcel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCExcel, BellSouth shall provide MRC Excel with a list of the customer data items, which MRC 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 MRC Excel data to the LIDB shall be solely at the direction of MRCExcel. Such direction from MRC 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 MRC Excel data upon MRCExcel’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 MRC Excel customer records will be missing from LIDB, as measured by MRC Excel audits. BellSouth will audit MRC Excel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC 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 MRC Excel within one (1) business day of audit. Once reconciled records are received back from MRCExcel, 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 MRC 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 MRCExcel’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 MRC 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 MRC Excel and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Excel in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Excel at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Excel the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCSail Networks’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCSail Networks, BellSouth shall provide MRC Sail Networks with a list of the customer data items, which MRC 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 MRC Sail Networks data to the LIDB shall be solely at the direction of MRCSail Networks. Such direction from MRC 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 MRC Sail Networks data upon MRCSail 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 MRC Sail Networks customer records will be missing from LIDB, as measured by MRC Sail Networks audits. BellSouth will audit MRC Sail Networks records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Sail Networks contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Sail Networks within one (1) business day of audit. Once reconciled records are received back from MRCSail 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 MRC 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 MRCSail 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 MRC 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 MRC Sail Networks and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Sail Networks in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Sail Networks at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Sail Networks the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC CBX One-Stop any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCCBX 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 MRC 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 MRCCBX One-Stop, BellSouth shall provide MRC CBX One-Stop with a list of the customer data items, which MRC 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 MRC CBX One-Stop data to the LIDB shall be solely at the direction of MRCCBX One-Stop. Such direction from MRC 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 MRC CBX One-Stop data upon MRCCBX 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 MRC CBX One-Stop customer records will be missing from LIDB, as measured by MRC CBX One- Stop audits. BellSouth will audit MRC CBX One-Stop records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC 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 MRC CBX One-Stop within one (1) business day of audit. Once reconciled records are received back from MRCCBX 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 MRC 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 MRCCBX 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 MRC 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 MRC CBX One-Stop and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC CBX One-Stop in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC CBX One-Stop at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC CBX One-Stop the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCEZ Phone’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCEZ Phone, BellSouth shall provide MRC EZ Phone with a list of the customer data items, which MRC 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 MRC EZ Phone data to the LIDB shall be solely at the direction of MRCEZ Phone. Such direction from MRC 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 MRC EZ Phone data upon MRCEZ 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 MRC EZ Phone customer records will be missing from LIDB, as measured by MRC EZ Phone audits. BellSouth will audit MRC EZ Phone records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC EZ Phone contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC EZ Phone within one (1) business day of audit. Once reconciled records are received back from MRCEZ 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 MRC 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 MRCEZ 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 MRC 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 MRC EZ Phone and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC EZ Phone in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC EZ Phone at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC EZ Phone the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCDeland Actel’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCDeland Actel, BellSouth shall provide MRC Deland Actel with a list of the customer data items, which MRC 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 MRC Deland Actel data to the LIDB shall be solely at the direction of MRCDeland Actel. Such direction from MRC 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 MRC Deland Actel data upon MRCDeland 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 MRC Deland Actel customer records will be missing from LIDB, as measured by MRC Deland Actel audits. BellSouth will audit MRC Deland Actel records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Deland Actel contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Deland Actel within one (1) business day of audit. Once reconciled records are received back from MRCDeland 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 MRC 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 MRCDeland 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 MRC 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 MRC Deland Actel and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Deland Actel in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Deland Actel at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Deland Actel the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC Starlink any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCStarlink’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCStarlink, BellSouth shall provide MRC Starlink with a list of the customer data items, which MRC 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 MRC Starlink data to the LIDB shall be solely at the direction of MRCStarlink. Such direction from MRC 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 MRC Starlink data upon MRCStarlink’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 MRC Starlink customer records will be missing from LIDB, as measured by MRC Starlink audits. BellSouth will audit MRC Starlink records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Starlink contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Starlink within one (1) business day of audit. Once reconciled records are received back from MRCStarlink, 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 MRC 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 MRCStarlink’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 MRC 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 MRC Starlink and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Starlink in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Starlink at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Starlink the screening information associated with LIDB Data Screening of MRC 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 MRC Starlink under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC OnePoint any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCOnePoint’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCOnePoint, BellSouth shall provide MRC OnePoint with a list of the customer data items, which MRC 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 MRC OnePoint data to the LIDB shall be solely at the direction of MRCOnePoint. Such direction from MRC 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 MRC OnePoint data upon MRCOnePoint’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 MRC OnePoint customer records will be missing from LIDB, as measured by MRC OnePoint audits. BellSouth will audit MRC OnePoint records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC OnePoint contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC OnePoint within one (1) business day of audit. Once reconciled records are received back from MRCOnePoint, 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 MRC 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 MRCOnePoint’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 MRC 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 MRC OnePoint and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC OnePoint in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC OnePoint at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC OnePoint the screening information associated with LIDB Data Screening of MRC 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 MRC OnePoint under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCSymtelco’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCSymtelco, BellSouth shall provide MRC Symtelco with a list of the customer data items, which MRC 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 MRC Symtelco data to the LIDB shall be solely at the direction of MRCSymtelco. Such direction from MRC 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 MRC Symtelco data upon MRCSymtelco’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 MRC Symtelco customer records will be missing from LIDB, as measured by MRC Symtelco audits. BellSouth will audit MRC Symtelco records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Symtelco contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Symtelco within one (1) business day of audit. Once reconciled records are received back from MRCSymtelco, 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 MRC 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 MRCSymtelco’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 MRC 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 MRC Symtelco and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Symtelco in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC Symtelco at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Symtelco the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 9.2.1 BellSouth will offer to MRC 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 MRCTWTC’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCTWTC, BellSouth shall provide MRC TWTC with a list of the customer data items, which MRC 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 MRC TWTC data to the LIDB shall be solely at the direction of MRCTWTC. Such direction from MRC 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 MRC TWTC data upon MRCTWTC’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 MRC TWTC customer records will be missing from LIDB, as measured by MRC TWTC audits. BellSouth will audit MRC TWTC records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC TWTC contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC TWTC within one (1) business day of audit. Once reconciled records are received back from MRCTWTC, 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 MRC 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 MRCTWTC’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 MRC 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 MRC TWTC and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC TWTC in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC TWTC at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC TWTC the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 BellSouth will offer to MRC ProNet any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCProNet’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCProNet, BellSouth shall provide MRC ProNet with a list of the customer data items, which MRC 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 MRC ProNet data to the LIDB shall be solely at the direction of MRCProNet. Such direction from MRC 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 MRC ProNet data upon MRCProNet’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 MRC ProNet customer records will be missing from LIDB, as measured by MRC ProNet audits. BellSouth will audit MRC ProNet records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC ProNet contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC ProNet within one (1) business day of audit. Once reconciled records are received back from MRCProNet, 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 MRC 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 MRCProNet’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 MRC 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 MRC ProNet and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC ProNet in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC ProNet at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ProNet the screening information associated with LIDB Data Screening of MRC 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 MRC ProNet under the BFR/NBR Process as set forth in Attachment 11. 7.3.2.14 BellSouth shall accept queries to LIDB associated with MRC 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 MRC Southern Digital any additional capabilities that are developed for LIDB during the life of this Agreement. 7.3.2.2 BellSouth shall process MRCSouthern Digital’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCSouthern Digital, BellSouth shall provide MRC Southern Digital with a list of the customer data items, which MRC 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 MRC Southern Digital data to the LIDB shall be solely at the direction of MRCSouthern Digital. Such direction from MRC 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 MRC Southern Digital data upon MRCSouthern 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 MRC Southern Digital customer records will be missing from LIDB, as measured by MRC Southern Digital audits. BellSouth will audit MRC Southern Digital records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC Southern Digital contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC Southern Digital within one (1) business day of audit. Once reconciled records are received back from MRCSouthern 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 MRC 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 MRCSouthern 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 MRC 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 MRC Southern Digital and BellSouth. 7.3.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC Southern Digital in writing. 7.3.2.13 BellSouth shall provide MRC 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 MRC Southern Digital at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC Southern Digital the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCOnePoint Communications’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCOnePoint Communications, BellSouth shall provide MRC OnePoint Communications with a list of the customer data items, which MRC 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 MRC OnePoint Communications data to the LIDB shall be solely at the direction of MRCOnePoint Communications. Such direction from MRC 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 MRC OnePoint Communications data upon MRCOnePoint 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 MRC OnePoint Communications customer records will be missing from LIDB, as measured by MRC OnePoint Communications audits. BellSouth ▇▇▇▇▇▇▇▇▇ will audit MRC OnePoint Communications records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC OnePoint Communications contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC OnePoint Communications within one (1) business day of audit. Once reconciled records are received back from MRCOnePoint 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 MRC 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 MRCOnePoint 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 MRC 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 MRC OnePoint Communications and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC OnePoint Communications in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC OnePoint Communications at least at parity with BellSouth Customer Data. BellSouth ▇▇▇▇▇▇▇▇▇ shall obtain from MRC OnePoint Communications the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCConnectNow!’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCConnectNow!, BellSouth shall provide MRC ConnectNow! with a list of the customer data items, which MRC 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 MRC ConnectNow! data to the LIDB shall be solely at the direction of MRCConnectNow!. Such direction from MRC 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 MRC ConnectNow! data upon MRCConnectNow!’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 MRC ConnectNow! customer records will be missing from LIDB, as measured by MRC ConnectNow! audits. BellSouth will audit MRC ConnectNow! records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC ConnectNow! contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth will refer record of mismatches to MRC ConnectNow! within one (1) business day of audit. Once reconciled records are received back from MRCConnectNow!, 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 MRC 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 MRCConnectNow!’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 MRC 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 MRC ConnectNow! and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC ConnectNow! in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC ConnectNow! at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC ConnectNow! the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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 MRC 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 MRCAmeriMex’s customer records in LIDB at least at parity with BellSouth customer records, with respect to other LIDB functions. BellSouth shall indicate to MRC 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 MRCAmeriMex, BellSouth shall provide MRC AmeriMex with a list of the customer data items, which MRC 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 MRC AmeriMex data to the LIDB shall be solely at the direction of MRCAmeriMex. Such direction from MRC 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 MRC AmeriMex data upon MRCAmeriMex’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 MRC AmeriMex customer records will be missing from LIDB, as measured by MRC AmeriMex audits. BellSouth will audit MRC AmeriMex records in LIDB against Data Base Administration System (DBAS) to identify record mismatches and provide this data to a designated MRC AmeriMex contact person to resolve the status of the records and BellSouth will update system appropriately. BellSouth ▇▇▇▇▇▇▇▇▇ will refer record of mismatches to MRC AmeriMex within one (1) business day of audit. Once reconciled records are received back from MRCAmeriMex, 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 MRC 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 MRCAmeriMex’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 MRC 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 MRC AmeriMex and BellSouth. 7.3.2.12 9.2.12 BellSouth shall prevent any access to or use of MRC 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 MRC AmeriMex in writing. 7.3.2.13 9.2.13 BellSouth shall provide MRC 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 MRC AmeriMex at least at parity with BellSouth Customer Data. BellSouth shall obtain from MRC AmeriMex the screening information associated with LIDB Data Screening of MRC 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 MRC 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 MRC 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.