Common use of RESPONSIBILITIES OF PARTIES Clause in Contracts

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to New Phone by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by New Phone.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to TCI by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by XxxxXxxxx and agreed to by TCI.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: : 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. 3.01. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. 3.02. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s 's reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s 's individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. 3.03. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. 3.04. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. (a) Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. (b) Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 3.05. BST will provide seven days per week, 24 hours per day, fraud control and detection services. These services include, but are not limited to, such features as sorting Calling Card Fraud detection according to domestic or international calls in order to assist the pinpointing of possible theft or fraudulent use of Calling Card numbers; monitoring xxxx-to-third number and collect calls made to numbers in BST's LIDB, provided such information is included in the LIDB query, and establishing Account Specific Thresholds, at BST's sole discretion, when necessary. Local Exchange Company understands and agrees BST will administer all data stored in the LIDB, including the data provided by Local Exchange Company pursuant to this Agreement, in the same manner as BST's data for BST's end user customers. BST shall not be responsible to Local Exchange Company for any lost revenue which may result from BST's administration of the LIDB pursuant to its established practices and procedures as they exist and as they may be changed by BST in its sole discretion from time to time.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Cbeyond by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by Cbeyond.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Al-Call by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by Al-Call.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Max-Tel by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Southern Light by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by Southern Light.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company Easycomm will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange CompanyEasycomm. BST will not issue line- line-based calling cards in the name of Local Exchange CompanyEasycomm’s individual end users. In the event that Local Exchange Company Easycomm wants to include calling card numbers assigned by the Local Exchange Company Easycomm in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company Easycomm has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to TCI by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by TCI.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or DC01/HEITJ/117073.1 special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. DC01/HEITJ/117073.1 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Al-Call by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by Al-Call.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Intermedia by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth. 2 Intermedia shall furnish all relevant information required by BellSouth for the provision of XXX Hosting, CATS and NICS.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to MET Communications by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth. 2 MET Communications shall furnish all relevant information required by BellSouth for the provision of XXX Hosting, CATS and NICS. 3 Applicable compensation amounts will be billed by BellSouth to MET Communications on a monthly basis in arrears. Amounts due from one Party to the other (excluding adjustments) are payable within thirty (30) days of receipt of the billing statement. 4 MET Communications must have its own unique XXX code. Requests for establishment of XXX status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from MET Communicationsto the BellSouth XXX Hosting coordinator at least eight (8) weeks prior to the proposed effective date. The proposed effective date will be mutually agreed upon between the Parties with consideration given to time necessary for the completion of required Telcordia (formerly BellCore) functions. XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MET Communications and will coordinate all associated conversion activities. 5 BellSouth will receive messages from MET Communications that are to be processed by BellSouth, another LEC or CLEC in the BellSouth region or a LEC outside the BellSouth region.

RESPONSIBILITIES OF PARTIES. A. 3.01. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. 3.02. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. 3.03. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. 3.04. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. (a) Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. (b) Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 3.05. BST will provide seven days per week, 24 hours per day, fraud control and detection services. These services include, but are not limited to, such features as sorting Calling Card Fraud detection according to domestic or international calls in order to assist the pinpointing of possible theft or fraudulent use of Calling Card numbers; monitoring xxxx-to-third number and collect calls made to numbers in BST’s LIDB, provided such information is included in the LIDB query, and establishing Account Specific Thresholds, at BST’s sole discretion, when necessary. Local Exchange Company understands and agrees BST will administer all data stored in the LIDB, including the data provided by Local Exchange Company pursuant to this Agreement, in the same manner as BST’s data for BST’s end user customers. BST shall not be responsible to Local Exchange Company for any lost revenue which may result from BST’s administration of the LIDB pursuant to its established practices and procedures as they exist and as they may be changed by BST in its sole discretion from time to time. 3.06. Local Exchange Company understands that BST currently has in effect numerous billing and collection cents with various interexchange carriers and billing clearing houses. Local Exchange Company further understands that these billing and collection customers of BST query BST’s LIDB to determine whether to accept various billing options from end users. Additionally, Local Exchange Company understands that presently BST has no method to differentiate between BST’s own billing and line data in the LIDB and such data which it includes in the LIDB on Local Exchange Company’s behalf pursuant to this Agreement. Therefore, until such time as BST can and does implement in its LIDB and its supporting systems the means to differentiate Local Exchange Company’s data from BST’s data and the parties to this Agreement execute appropriate amendments hereto, the following terms and conditions shall apply: (a) The Local Exchange Company agrees that it will accept responsibility for telecommunications services billed by BST for its billing and collection customers for Local Exchange Customer’s end user accounts which are resident in LIDB pursuant to this Agreement Local Exchange Company authorizes BST to place such charges on Local Exchange Company’s xxxx from BST and agrees that it shall pay all such charges. Charges for which Local Exchange Company hereby takes responsibility include, but are not limited to, collect and third number calls. (b) Charges for such services shall appear on a separate BST xxxx xxxx identified with the name of the entity for which BST is billing the charge. (c) Local Exchange Company shall have the responsibility to render a billing statement to its end users for these charges, but Local Exchange Company’s obligation to pay BST for the charges billed shall be independent of whether Local Exchange Company is able or not to collect from Local Exchange Company’s end users. (d) BST shall not become involved in any disputes between Local Exchange Company and the entities for which BST performs billing and collection. BellSouth will not issue adjustments for charges billed on behalf of an entity to Local Exchange Company. It shall be the responsibility of the Local Exchange Company and the other entity to negotiate and arrange for any appropriate adjustments.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 RAO Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Al-Call by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by Al-Call.

RESPONSIBILITIES OF PARTIES. A. 3.01. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. 3.02. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s 's reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s 's individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. 3.03. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. 3.04. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. (a) Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. (b) Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 3.05. BST will provide seven days per week, 24 hours per day, fraud control and detection services. These services include, but are not limited to, such features as sorting Calling Card Fraud detection according to domestic or international calls in order to assist the pinpointing of possible theft or fraudulent use of Calling Card numbers; monitoring bill-xx-third number and collect calls made to numbers in BST's LIDB, provided such information is included in the LIDB query, and establishing Account Specific Thresholds, at BST's sole discretion, when necessary. Local Exchange Company understands and agrees BST will administer all data stored in the LIDB, including the data provided by Local Exchange Company pursuant to this Agreement, in the same manner as BST's data for BST's end user customers. BST shall not be responsible to Local Exchange Company for any lost revenue which may result from BST's administration of the LIDB pursuant to its established practices and procedures as they exist and as they may be changed by BST in its sole discretion from time to time.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. Page 29 EXHIBIT C 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to Premiere by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth. 2. Premiere shall furnish all relevant information required by BellSouth for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to Premiere on a monthly basis in arrears. Amounts due from one Party to the other (excluding adjustments) are payable within thirty (30) days of receipt of the billing statement. 4. Premiere must have its own unique XXX code. Requests for establishment of XXX status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from Premiere to the BellSouth XXX Hosting coordinator at least eight (8) weeks prior to the proposed effective date. The proposed effective date will be mutually agreed upon between the Parties with consideration given to time necessary for the completion of required Telcordia (formerly BellCore) functions. BellSouth will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of Premiere and will coordinate all associated conversion activities. 5. BellSouth will receive messages from Premiere that are to be processed by BellSouth, another LEC or CLEC in the BellSouth region or a LEC outside the BellSouth region. 6. BellSouth will perform invoice sequence checking, standard EMI format editing, and balancing of message data with the EMI trailer record counts on all data received from Premiere. 7. All data received from Premiere that is to be processed or billed by another LEC or CLEC within the BellSouth region will be distributed to that LEC or CLEC in accordance with the agreement(s) which may be in effect between BellSouth and the involved LEC or CLEC. 8. All data received from Premiere that is to be placed on the CMDS network for distribution outside the BellSouth region will be handled in accordance with the agreement(s) which may be in effect between BellSouth and its connecting contractor (currently Telcordia (formerly BellCore)). 9. BellSouth will receive messages from the CMDS network that are destined to be processed by Premiere and will forward them to Premiere on a daily basis. 10. Transmission of message data between BellSouth and Premiere will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Premiere will be formatted in accordance with accepted industry standards for EMI formatted records and packed between appropriate EMI header and trailer records, also in accordance with accepted industry standards. 12. Premiere will ensure that the recorded message detail necessary to recreate files provided to BellSouth will be maintained for back-up purposes for a period of three (3) calendar months beyond the related message dates. 13. Should it become necessary for Premiere to send data to BellSouth more than sixty (60) days past the message date(s), Premiere will notify BellSouth in advance of the transmission of the data. If there will be impacts outside the BellSouth region, BellSouth will work with its connecting contractor and Premiere to notify all affected Parties. 14. In the event that data to be exchanged between the two Parties should become lost or destroyed, both Parties will work together to determine the source of the problem. Once the cause of the problem has been jointly determined and the responsible Party (BellSouth or Premiere) identified and agreed to, the company responsible for creating the data (BellSouth or Premiere) will make every effort to have the affected data restored and retransmitted. If the data cannot be retrieved, the responsible Party will be liable to the other Party for any resulting lost revenue. Lost revenue may be a combination of revenues that could not be billed to the end users and associated access revenues. Both Parties will work together to estimate the revenue amount based upon historical data through a method mutually agreed upon. The resulting estimated revenue loss will be paid by the responsible Party to the other Party within three (3) calendar months of the date of problem resolution, or as mutually agreed upon by the Parties. 15. Should an error be detected by the EMI format edits performed by BellSouth on data received from Premiere, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Premiere of the error condition. Premiere will correct the error(s) and will resend the entire pack to BellSouth for processing. In the event that an out-of-sequence condition occurs on subsequent packs, Premiere will resend these packs to BellSouth after the pack containing the error has been successfully reprocessed by BellSouth. 16. In association with message distribution service, BellSouth will provide Premiere with associated intercompany settlements reports (CATS and NICS) as appropriate. 17. In no case shall either Party be liable to the other for any direct or consequential damages incurred as a result of the obligations set out in this agreement.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company Comm South will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange CompanyComm South. BST will not issue line- line-based calling cards in the name of Local Exchange CompanyComm South’s individual end users. In the event that Local Exchange Company Comm South wants to include calling card numbers assigned by the Local Exchange Company Comm South in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company Comm South has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. Page 30 EXHIBIT C 1. RAO Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to OnePoint by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth. 2. OnePoint shall furnish all relevant information required by BellSouth for the provision of RAO Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to OnePoint on a monthly basis in arrears. Amounts due from one Party to the other (excluding adjustments) are payable within thirty (30) days of receipt of the billing statement. 4. OnePoint must have its own unique RAO code. Requests for establishment of RAO status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from OnePoint to the BellSouth RAO Hosting coordinator at least eight (8) weeks prior to the proposed effective date. The proposed effective date will be mutually agreed upon between the Parties with consideration given to time necessary for the completion of required Telcordia (formerly BellCore) functions. BellSouth will request the assignment of an RAO code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of OnePoint and will coordinate all associated conversion activities. 5. BellSouth will receive messages from OnePoint that are to be processed by BellSouth, another LEC or CLEC in the BellSouth region or a LEC outside the BellSouth region. 6. BellSouth will perform invoice sequence checking, standard EMI format editing, and balancing of message data with the EMI trailer record counts on all data received from OnePoint. 7. All data received from OnePoint that is to be processed or billed by another LEC or CLEC within the BellSouth region will be distributed to that LEC or CLEC in accordance with the agreement(s) which may be in effect between BellSouth and the involved LEC or CLEC. 8. All data received from OnePoint that is to be placed on the CMDS network for distribution outside the BellSouth region will be handled in accordance with the agreement(s) which may be in effect between BellSouth and its connecting contractor (currently Telcordia (formerly BellCore)). 9. BellSouth will receive messages from the CMDS network that are destined to be processed by OnePoint and will forward them to OnePoint on a daily basis. 10. Transmission of message data between BellSouth and OnePoint will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and OnePoint will be formatted in accordance with accepted industry standards for EMI formatted records and packed between appropriate EMI header and trailer records, also in accordance with accepted industry standards. 12. OnePoint will ensure that the recorded message detail necessary to recreate files provided to BellSouth will be maintained for back-up purposes for a period of three (3) calendar months beyond the related message dates. 13. Should it become necessary for OnePoint to send data to BellSouth more than sixty (60) days past the message date(s), OnePoint will notify BellSouth in advance of the transmission of the data. If there will be impacts outside the BellSouth region, BellSouth will work with its connecting contractor and OnePoint to notify all affected Parties. 14. In the event that data to be exchanged between the two Parties should become lost or destroyed, both Parties will work together to determine the source of the problem. Once the cause of the problem has been jointly determined and the responsible Party (BellSouth or OnePoint) identified and agreed to, the company responsible for creating the data (BellSouth or OnePoint) will make every effort to have the affected data restored and retransmitted. If the data cannot be retrieved, the responsible Party will be liable to the other Party for any resulting lost revenue. Lost revenue may be a combination of revenues that could not be billed to the end users and associated access revenues. Both Parties will work together to estimate the revenue amount based upon historical data through a method mutually agreed upon. The resulting estimated revenue loss will be paid by the responsible Party to the other Party within three (3) calendar months of the date of problem resolution, or as mutually agreed upon by the Parties. 15. Should an error be detected by the EMI format edits performed by BellSouth on data received from OnePoint, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify OnePoint of the error condition. OnePoint will correct the error(s) and will resend the entire pack to BellSouth for processing. In the event that an out-of-sequence condition occurs on subsequent packs, OnePoint will resend these packs to BellSouth after the pack containing the error has been successfully reprocessed by BellSouth. 16. In association with message distribution service, BellSouth will provide OnePoint with associated intercompany settlements reports (CATS and NICS) as appropriate.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company Express Connection will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange CompanyExpress Connection. BST will not issue line- line-based calling cards in the name of Local Exchange CompanyExpress Connection’s individual end users. In the event that Local Exchange Company Express Connection wants to include calling card numbers assigned by the Local Exchange Company Express Connection in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company Express Connection has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company Advantel will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange CompanyAdvantel. BST will not issue line- line-based calling cards in the name of Local Exchange CompanyAdvantel’s individual end users. In the event that Local Exchange Company Advantel wants to include calling card numbers assigned by the Local Exchange Company Advantel in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company Advantel has identified the billing number as one which should not be billed for collect or third number calls, or both.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Al-Call by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by XxxxXxxxx and agreed to by Al-Call.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to Connect! by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by Connect!.

RESPONSIBILITIES OF PARTIES. A. BST will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The Local Exchange Company will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BST shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BST shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BST’s reasonable control. BST will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BST will issue line-based calling cards only in the name of Local Exchange Company. BST will not issue line- line-based calling cards in the name of Local Exchange Company’s individual end users. In the event that Local Exchange Company wants to include calling card numbers assigned by the Local Exchange Company in the BST LIDB, a separate agreement is required. C. BST will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BST is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BST, and where the last four digits (PIN) are a security code assigned by BST. 2. Determine whether the Local Exchange Company has identified the billing number as one which should not be billed for collect or third number calls, or both. 1 XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non-Intercompany Settlement System (NICS) services provided to BroadRiver by BellSouth will be in accordance with the methods and practices conforming to accepted industry standards during the term of this Agreement, including such revisions as may be made from time to time by BellSouth and agreed to by BroadRiver.