Common use of RESPONSIBILITIES OF PARTIES Clause in Contracts

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWER. BellSouth will not issue line-based calling cards in the name of MPOWER’s individual end users. In the event that MPOWER wants to include calling card numbers assigned by the MPOWER in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 3 contracts

Samples: Bellsouth® / Clec Agreement, Bellsouth® / Clec Agreement, Bellsouth / Clec Agreement

AutoNDA by SimpleDocs

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER CLEC-1 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERCLEC-1. BellSouth will not issue line-based calling cards in the name of MPOWERCLEC-1’s individual end users. In the event that MPOWER CLEC-1 wants to include calling card numbers assigned by the MPOWER CLEC-1 in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER CLEC-1 has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER CLEC-1 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. MPOWER CLEC-1 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 MPOWER CLEC-1 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. MPOWER CLEC-1 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 MPOWER CLEC-1 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER CLEC-1 and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER CLEC-1 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 MPOWERCLEC-1. 7. All data received from CLEC-1 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 CLEC-1 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 CLEC-1 and will forward them to CLEC-1 on a daily basis. 10. Transmission of message data between BellSouth and CLEC-1 will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and CLEC-1 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. CLEC-1 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 CLEC-1 to send data to BellSouth more than sixty (60) days past the message date(s), CLEC-1 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 CLEC-1 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 CLEC-1) identified and agreed to, the company responsible for creating the data (BellSouth or CLEC-1) 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 CLEC-1, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify CLEC-1 of the error condition. CLEC-1 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, CLEC-1 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 CLEC-1 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.

Appears in 3 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER VELOCITY 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERVELOCITY. BellSouth will not issue line-based calling cards in the name of MPOWERVELOCITY’s individual end usersEnd Users. In the event that MPOWER VELOCITY wants to include calling card numbers assigned by the MPOWER VELOCITY in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER VELOCITY has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 2 contracts

Samples: Clec Agreement, Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER ICG 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERICG. BellSouth will not issue line-based calling cards in the name of MPOWERICG’s individual end users. In the event that MPOWER ICG wants to include calling card numbers assigned by the MPOWER ICG in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER ICG has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER ICG 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. MPOWER ICG 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 MPOWER ICG 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. MPOWER ICG 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 MPOWER ICG 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER ICG and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER ICG 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 MPOWERICG. 7. All data received from ICG 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 ICG 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 ICG and will forward them to ICG on a daily basis.

Appears in 2 contracts

Samples: Telecommunications, Clec Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER IDS 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERIDS. BellSouth will not issue line-based calling cards in the name of MPOWER’s IDS’ individual end usersEnd Users. In the event that MPOWER IDS wants to include calling card numbers assigned by the MPOWER IDS in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. . Interconnection Agreement-AL/KY/LA/MS/TN D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER IDS has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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 Interconnection Agreement, including such revisions as may be made from time to time by BellSouth. 2. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.-AL/KY/LA/MS/TN

Appears in 2 contracts

Samples: Clec Agreement, Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWER. BellSouth will not issue line-based calling cards in the name of MPOWER’s individual end users. In the event that MPOWER wants to include calling card numbers assigned by the MPOWER in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Access One 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERAccess One. BellSouth will not issue line-based calling cards in the name of MPOWERAccess One’s individual end users. In the event that MPOWER Access One wants to include calling card numbers assigned by the MPOWER Access One in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Access One has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00Version1Q00:2/17/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Access One 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. MPOWER Access One 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 MPOWER Access One 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. MPOWER Access One 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 MPOWER Access One 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 MPOWER Access One and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Access One 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 MPOWERAccess One. 7. All data received from Access One 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 Access One that is to be placed on the CMDS network for distribution outside the BellSouth region will be handled in accordance with the Version1Q00:2/17/00 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 Access One and will forward them to Access One on a daily basis. 10. Transmission of message data between BellSouth and Access One will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Access One 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. Access One 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 Access One to send data to BellSouth more than sixty (60) days past the message date(s), Access One 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 Access One 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 Access One) identified and agreed to, the company responsible for creating the data (BellSouth or Access One) 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 Access One, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Access One of the error condition. Version1Q00:2/17/00 Access One 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, Access One 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 Access One 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.

Appears in 1 contract

Samples: Bellsouth® / Clec Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Xxxxxxx 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERXxxxxxx. BellSouth will not issue line-based calling cards in the name of MPOWER’s Xxxxxxx’x individual end users. In the event that MPOWER Xxxxxxx wants to include calling card numbers assigned by the MPOWER Xxxxxxx in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Xxxxxxx has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Xxxxxxx 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. MPOWER Xxxxxxx shall furnish all relevant information required by BellSouth XxxxXxxxx for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to MPOWER Xxxxxxx 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. MPOWER Xxxxxxx 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 MPOWER Xxxxxxx 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Xxxxxxx and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Xxxxxxx 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 MPOWERXxxxxxx.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Xxxxxx 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERXxxxxx. BellSouth will not issue line-based calling cards in the name of MPOWER’s Xxxxxx’x individual end users. In the event that MPOWER Xxxxxx wants to include calling card numbers assigned by the MPOWER Xxxxxx in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Xxxxxx has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Xxxxxx 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. MPOWER Xxxxxx shall furnish all relevant information required by BellSouth XxxxXxxxx for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to MPOWER Xxxxxx 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. MPOWER Xxxxxx 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 MPOWER Xxxxxx 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Xxxxxx and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Xxxxxx 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 MPOWERXxxxxx. 7. All data received from Xxxxxx 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 Xxxxxx 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 Xxxxxx and will forward them to Xxxxxx on a daily basis. 10. Transmission of message data between BellSouth and Xxxxxx will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Xxxxxx 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. Xxxxxx 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 Xxxxxx to send data to BellSouth more than sixty (60) days past the message date(s), Xxxxxx 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 Xxxxxx 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 Xxxxxx) identified and agreed to, the company responsible for creating the data (BellSouth or Xxxxxx) 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 Xxxxxx, the entire pack containing the affected data will not be processed by BellSouth. XxxxXxxxx will notify Xxxxxx of the error condition. Xxxxxx 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, Xxxxxx 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 Xxxxxx 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.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER LS-One 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERLS-One. BellSouth will not issue line-based calling cards in the name of MPOWERLS-One’s individual end usersEnd Users. In the event that MPOWER LS-One wants to include calling card numbers assigned by the MPOWER LS-One in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER LS-One has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER ETS 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERETS. BellSouth will not issue line-based calling cards in the name of MPOWERETS’s individual end users. In the event that MPOWER ETS wants to include calling card numbers assigned by the MPOWER ETS in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER ETS has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER ETS 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. MPOWER ETS 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 MPOWER ETS 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. MPOWER ETS 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 MPOWER ETS 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 MPOWER ETS and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER ETS 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 MPOWERETS. 7. All data received from ETS 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 ETS that is to be placed on the CMDS network for distribution outside the BellSouth region will be handled in accordance with the agreement(s) Version1Q00:3/6/00 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 ETS and will forward them to ETS on a daily basis. 10. Transmission of message data between BellSouth and ETS will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and ETS 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. ETS 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 ETS to send data to BellSouth more than sixty (60) days past the message date(s), ETS 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 ETS 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 ETS) identified and agreed to, the company responsible for creating the data (BellSouth or ETS) 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 ETS, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify ETS of the error condition. ETS will correct the Version1Q00:3/6/00 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, ETS 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 ETS 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.

Appears in 1 contract

Samples: Bellsouth® / Clec Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER ALLTEL 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERALLTEL. BellSouth will not issue line-based calling cards in the name of MPOWERALLTEL’s individual end users. In the event that MPOWER ALLTEL wants to include calling card numbers assigned by the MPOWER ALLTEL in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER ALLTEL has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER toALLTEL 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. MPOWER ALLTEL 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 MPOWER toALLTEL 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. MPOWER ALLTEL must have its own unique XXX code. Requests for establishment of XXX RAO status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from MPOWER ALLTEL 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 RAO code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER ALLTEL and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER ALLTEL 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 MPOWERALLTEL. 7. All data received from ALLTEL 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.

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Money To Go 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERMoney To Go. BellSouth will not issue line-based calling cards in the name of MPOWERMoney To Go’s individual end users. In the event that MPOWER Money To Go wants to include calling card numbers assigned by the MPOWER Money To Go in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Money To Go has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Money To Go 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. MPOWER Money To Go 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 MPOWER Money To Go 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. MPOWER Money To Go 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 MPOWER Money To Go 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Money To Go and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Money To Go 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 MPOWERMoney To Go.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Unity 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERUnity. BellSouth will not issue line-based calling cards in the name of MPOWERUnity’s individual end users. In the event that MPOWER Unity wants to include calling card numbers assigned by the MPOWER Unity in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Unity has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Unity 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. MPOWER Unity 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 MPOWER Unity 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. MPOWER Unity 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 MPOWER Unity 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Unity and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Unity 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 MPOWERUnity. 7. All data received from Unity 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 Unity 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 Unity and will forward them to Unity on a daily basis. 10. Transmission of message data between BellSouth and Unity will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Unity 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. Unity 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 Unity to send data to BellSouth more than sixty (60) days past the message date(s), Unity 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 Unity 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 Unity) identified and agreed to, the company responsible for creating the data (BellSouth or Unity) 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 Unity, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Unity of the error condition. Unity 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, Unity 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 Unity 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.

Appears in 1 contract

Samples: Resale Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER NewSouth 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERNewSouth. BellSouth will not issue line-based calling cards in the name of MPOWERNewSouth’s individual end users. In the event that MPOWER NewSouth wants to include calling card numbers assigned by the MPOWER NewSouth in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER NewSouth has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER NewSouth 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. MPOWER NewSouth 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 MPOWER NewSouth 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. MPOWER NewSouth 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 MPOWER NewSouth 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 MPOWER NewSouth and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER NewSouth 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 MPOWERNewSouth. 7. All data received from NewSouth 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 NewSouth 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)).

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER TLX 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERTLX. BellSouth will not issue line-based calling cards in the name of MPOWERTLX’s individual end users. In the event that MPOWER TLX wants to include calling card numbers assigned by the MPOWER TLX in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER TLX has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER TLX 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. MPOWER TLX 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 MPOWER TLX 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. MPOWER TLX 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 MPOWER TLX 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER TLX and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER TLX 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 MPOWERTLX.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER CLEC-1 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERCLEC-1. BellSouth will not issue line-based calling cards in the name of MPOWERCLEC-1’s individual end users. In the event that MPOWER CLEC-1 wants to include calling card numbers assigned by the MPOWER CLEC-1 in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER CLEC-1 has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER CLEC-1 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. MPOWER CLEC-1 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 MPOWER CLEC-1 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. MPOWER CLEC-1 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 MPOWER CLEC-1 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER CLEC-1 and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER CLEC-1 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 MPOWERCLEC-1.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Centennial 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERCentennial. BellSouth will not issue line-based calling cards in the name of MPOWERCentennial’s individual end users. In the event that MPOWER Centennial wants to include calling card numbers assigned by the MPOWER Centennial in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Centennial has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Centennial 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. MPOWER Centennial 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 MPOWER Centennial 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. MPOWER Centennial 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 MPOWER Centennial 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Centennial and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Centennial 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 MPOWERCentennial.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Community 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERCommunity. BellSouth will not issue line-based calling cards in the name of MPOWERCommunity’s individual end users. In the event that MPOWER Community wants to include calling card numbers assigned by the MPOWER Community in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Community has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Community 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. MPOWER Community 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 MPOWER Community 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. MPOWER Community 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 MPOWER Community 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Community and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Community 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 MPOWERCommunity. 7. All data received from Community 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 Community 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 Community and will forward them to Community on a daily basis. 10. Transmission of message data between BellSouth and Community will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Community 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. Community 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 Community to send data to BellSouth more than sixty (60) days past the message date(s), Community 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 Community 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 Community) identified and agreed to, the company responsible for creating the data (BellSouth or Community) 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 Community, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Community of the error condition. Community 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, Community 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 Community 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.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Express 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERExpress. BellSouth will not issue line-based calling cards in the name of MPOWERExpress’s individual end users. In the event that MPOWER Express wants to include calling card numbers assigned by the MPOWER Express in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Express has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Express 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. MPOWER Express 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 MPOWER Express 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. MPOWER Express 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 MPOWER Express 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Express and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Express 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 MPOWERExpress. 7. All data received from Express 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 Express 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 Express and will forward them to Express on a daily basis. 10. Transmission of message data between BellSouth and Express will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Express 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. Express 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 Express to send data to BellSouth more than sixty (60) days past the message date(s), Express 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 Express 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 Express) identified and agreed to, the company responsible for creating the data (BellSouth or Express) 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 Express, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Express of the error condition. Express 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, Express 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 Express 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.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Pyramid 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERPyramid. BellSouth will not issue line-based calling cards in the name of MPOWERPyramid’s individual end users. In the event that MPOWER Xxxxxxx wants to include calling card numbers assigned by the MPOWER Pyramid in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Pyramid has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Pyramid 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. MPOWER Pyramid 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 MPOWER Pyramid 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. MPOWER Pyramid must have its own unique XXX code. Requests for establishment of XXX RAO status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from MPOWER Pyramid 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 RAO code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Pyramid and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Pyramid 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 MPOWERPyramid. 7. All data received from Pyramid 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 Pyramid 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 Pyramid and will forward them to Pyramid on a daily basis. 10. Transmission of message data between BellSouth and Pyramid will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Pyramid 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. Pyramid 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

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Accutel 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERAccutel. BellSouth will not issue line-based calling cards in the name of MPOWERAccutel’s individual end users. In the event that MPOWER Accutel wants to include calling card numbers assigned by the MPOWER Accutel in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Accutel has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Accutel 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. MPOWER Accutel 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 MPOWER Accutel 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. MPOWER Accutel 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 MPOWER Accutel 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Accutel and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Accutel 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 MPOWERAccutel.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Light Networks 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERLight Networks. BellSouth will not issue line-based calling cards in the name of MPOWERLight Networks’s individual end users. In the event that MPOWER Light Networks wants to include calling card numbers assigned by the MPOWER Light Networks in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Light Networks has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Light Networks 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. MPOWER Light Networks 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 MPOWER Light Networks 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. MPOWER Light Networks 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 MPOWER Light Networks 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Light Networks and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Light Networks 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 MPOWERLight Networks.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Pointecom 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERPointecom. BellSouth will not issue line-based calling cards in the name of MPOWERPointecom’s individual end users. In the event that MPOWER Pointecom wants to include calling card numbers assigned by the MPOWER Pointecom in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Pointecom has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Pointecom 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. MPOWER Pointecom 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 MPOWER Pointecom 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. MPOWER Pointecom 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 MPOWER Pointecom 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Pointecom and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Pointecom 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 MPOWERPointecom.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Express Title 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERExpress Title. BellSouth will not issue line-based calling cards in the name of MPOWERExpress Title’s individual end users. In the event that MPOWER Express Title wants to include calling card numbers assigned by the MPOWER Express Title in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Express Title has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Express Title 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. MPOWER Express Title 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 MPOWER Express Title 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. MPOWER Express Title 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 MPOWER Express Title 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 MPOWER Express Title and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Express Title 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 MPOWERExpress Title. 7. All data received from Express Title 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 Express Title 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 Express Title and will forward them to Express Title on a daily basis. 10. Transmission of message data between BellSouth and Express Title will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Express Title 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. Express Title 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 Express Title to send data to BellSouth more than sixty (60) days past the message date(s), Express Title 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 Express Title 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 Express Title) identified and agreed to, the company responsible for creating the data (BellSouth or Express Title) 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 Express Title, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Express Title of the error condition. Express Title 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, Express Title 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 Express Title 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.

Appears in 1 contract

Samples: Telecommunications

AutoNDA by SimpleDocs

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Knology 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERKnology. BellSouth will not issue line-based calling cards in the name of MPOWERKnology’s individual end usersEnd Users. In the event that MPOWER Xxxxxxx wants to include calling card numbers assigned by the MPOWER Knology in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Xxxxxxx has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Colmena 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERColmena. BellSouth will not issue line-based calling cards in the name of MPOWERColmena’s individual end users. In the event that MPOWER Colmena wants to include calling card numbers assigned by the MPOWER Colmena in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Colmena has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Colmena 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. MPOWER Colmena shall furnish all relevant information required by BellSouth XxxxXxxxx for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to MPOWER Colmena 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. MPOWER Colmena 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 MPOWER Colmena 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Colmena and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Colmena 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 MPOWERColmena. 7. All data received from Colmena 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 Colmena 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 Colmena and will forward them to Colmena on a daily basis. 10. Transmission of message data between BellSouth and Colmena will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Colmena 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. Colmena 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 Colmena to send data to BellSouth more than sixty (60) days past the message date(s), Colmena 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 Colmena 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 Colmena) identified and agreed to, the company responsible for creating the data (BellSouth or Colmena) 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 Colmena, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Colmena of the error condition. Colmena 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, Colmena 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 Colmena 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.

Appears in 1 contract

Samples: Resale Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Knology 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, BellSouth 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 BellSouth 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 BellSouth’s 's reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERKnology. BellSouth will not issue line-based calling cards in the name of MPOWER’s Knology's individual end usersEnd Users. In the event that MPOWER Knology wants to include calling card numbers assigned by the MPOWER Knology in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Knology has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00Attachment 1 Page 29 EXHIBIT D Optional Daily Usage File ------------------------- 1. XXX HostingUpon written request from Knology, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER by BellSouth will be provide the Optional Daily Usage File (ODUF) service to Knology pursuant to the terms and conditions set forth 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 BellSouthsection. 2. MPOWER Knology shall furnish all relevant information required by BellSouth for the provision of XXX Hosting, CATS and NICSthe Optional Daily Usage File. 3. Applicable compensation amounts The Optional Daily Usage Feed will be contain billable messages that were carried over the BellSouth Network and processed in the BellSouth Billing System, but billed by BellSouth to MPOWER on a monthly basis in arrearsKnology customer. Amounts due from one Party to the other (excluding adjustments) are payable within thirty (30) days of receipt Charges for delivery of the billing statementOptional Daily Usage File will appear on Knology's monthly bills. The charges are as set forth in Exhibit A to this Attachment. 4. MPOWER must have its own unique XXX codeThe Optional Daily Usage Feed will contain both rated and unrated messages. Requests for establishment of XXX status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from MPOWER to the BellSouth XXX Hosting coordinator at least eight (8) weeks prior to the proposed effective date. The proposed effective date All messages will be mutually agreed upon between in the Parties with consideration given to time necessary standard Alliance for the completion of required Telcordia Telecommunications Industry Solutions (formerly BellCoreATIS) functions. BellSouth will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER and will coordinate all associated conversion activitiesEMI record format. 5. Messages that error in Knology's billing system will be the responsibility of Knology. If, however, Knology should encounter significant volumes of errored messages that prevent processing by Knology within its systems, BellSouth will receive messages from MPOWER that are work with the to be processed by BellSouth, another LEC or CLEC in determine the BellSouth region or a LEC outside source of the BellSouth regionerrors and the appropriate resolution. 6. BellSouth will perform invoice sequence checking, standard EMI format editing, and balancing of message data with The following specifications shall apply to the EMI trailer record counts on all data received from MPOWEROptional Daily Usage Feed.

Appears in 1 contract

Samples: Telecommunications (Knology Inc)

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Knology 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERKnology. BellSouth will not issue line-based calling cards in the name of MPOWERKnology’s individual end usersEnd Users. In the event that MPOWER Knology wants to include calling card numbers assigned by the MPOWER Knology in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Knology has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Z-Tel 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERZ-Tel. BellSouth will not issue line-based calling cards in the name of MPOWERZ-Tel’s individual end users. In the event that MPOWER Z-Tel wants to include calling card numbers assigned by the MPOWER Z-Tel in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Z-Tel has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Z-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. 2. MPOWER Z-Tel 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 MPOWER Z-Tel 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. MPOWER Z-Tel 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 MPOWER Z-Tel 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 MPOWER Z-Tel and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Z-Tel 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 MPOWERZ-Tel.

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Oltronics 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWEROltronics. BellSouth will not issue line-based calling cards in the name of MPOWEROltronics’s individual end users. In the event that MPOWER Xxxxxxxxx wants to include calling card numbers assigned by the MPOWER Oltronics in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Oltronics has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Oltronics 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. MPOWER Oltronics 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 MPOWER Oltronics 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. MPOWER Oltronics 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 MPOWER Oltronics 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Oltronics and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Oltronics 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 MPOWEROltronics. 7. All data received from Oltronics 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 Oltronics 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 Oltronics and will forward them to Oltronics on a daily basis. 10. Transmission of message data between BellSouth and Oltronics will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Oltronics 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. Oltronics 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 Oltronics to send data to BellSouth more than sixty (60) days past the message date(s), Oltronics 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 Oltronics 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 Oltronics) identified and agreed to, the company responsible for creating the data (BellSouth or Oltronics) 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 Oltronics, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Oltronics of the error condition. Oltronics 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, Oltronics 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 Oltronics 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.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER NA Communications 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERNA Communications. BellSouth will not issue line-based calling cards in the name of MPOWERNA Communications’s individual end users. In the event that MPOWER NA Communications wants to include calling card numbers assigned by the MPOWER NA Communications in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER NA Communications has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER NA 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. MPOWER NA 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 MPOWER NA 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. MPOWER NA 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 MPOWER NA Communications 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 MPOWER NA Communications and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER NA Communications 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 MPOWERNA Communications.

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Birch 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERBirch. BellSouth will not issue line-based calling cards in the name of MPOWER’s Xxxxx’x individual end users. In the event that MPOWER Xxxxx wants to include calling card numbers assigned by the MPOWER Birch in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Birch has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Birch 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. MPOWER Xxxxx 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 MPOWER Birch 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. MPOWER Birch 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 MPOWER Birch 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Birch and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Birch 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 MPOWERBirch.

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Pathnet 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERPathnet. BellSouth will not issue line-based calling cards in the name of MPOWERPathnet’s individual end users. In the event that MPOWER Pathnet wants to include calling card numbers assigned by the MPOWER Pathnet in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Pathnet has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Pathnet 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. MPOWER Pathnet 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 MPOWER Pathnet 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. MPOWER Pathnet 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 MPOWER Pathnet 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Pathnet and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Pathnet 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 MPOWERPathnet. 7. All data received from Pathnet 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 Pathnet 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 Pathnet and will forward them to Pathnet on a daily basis. 10. Transmission of message data between BellSouth and Pathnet will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Pathnet 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. Pathnet 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 Pathnet to send data to BellSouth more than sixty (60) days past the message date(s), Pathnet 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 Pathnet 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 Pathnet) identified and agreed to, the company responsible for creating the data (BellSouth or Pathnet) 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 Pathnet, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify Pathnet of the error condition. Pathnet 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, Pathnet 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 Pathnet 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.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER BTI 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERBTI. BellSouth will not issue line-based calling cards in the name of MPOWERBTI’s individual end users. In the event that MPOWER BTI wants to include calling card numbers assigned by the MPOWER BTI in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER BTI has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER BTI 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. MPOWER BTI 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 MPOWER BTI 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. MPOWER BTI 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 MPOWER BTI 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER BTI and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER BTI 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 MPOWERBTI. 7. All data received from BTI 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 BTI 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 BTI and will forward them to BTI on a daily basis. 10. Transmission of message data between BellSouth and BTI will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and BTI 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. BTI 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 BTI to send data to BellSouth more than sixty (60) days past the message date(s), BTI 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 BTI 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 BTI) identified and agreed to, the company responsible for creating the data (BellSouth or BTI) 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 BTI, the entire pack containing the affected data will not be processed by BellSouth. BellSouth will notify BTI of the error condition. BTI 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, BTI 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 BTI 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.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER MPC 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERMPC. BellSouth will not issue line-based calling cards in the name of MPOWERMPC’s individual end users. In the event that MPOWER MPC wants to include calling card numbers assigned by the MPOWER MPC in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER MPC has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER MPC 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. MPOWER MPC shall furnish all relevant information required by BellSouth XxxxXxxxx for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to MPOWER MPC 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. MPOWER MPC 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 MPOWER MPC 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.eight

Appears in 1 contract

Samples: Telecommunications

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER CCI 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERCCI. BellSouth will not issue line-based calling cards in the name of MPOWERCCI’s individual end usersEnd Users. In the event that MPOWER CCI wants to include calling card numbers assigned by the MPOWER CCI in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER CCI has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER 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. MPOWER 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 MPOWER 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. MPOWER 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 MPOWER 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 MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER 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 MPOWER.

Appears in 1 contract

Samples: Telecommunications Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER USA Digital 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERUSA Digital. BellSouth will not issue line-based calling cards in the name of MPOWERUSA Digital’s individual end users. In the event that MPOWER USA Digital wants to include calling card numbers assigned by the MPOWER USA Digital in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER USA Digital has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER USA Digital 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. MPOWER USA Digital 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 MPOWER USA Digital 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. MPOWER USA Digital 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 MPOWER USA Digital 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER USA Digital and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER USA Digital 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 MPOWERUSA Digital.

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER DV2 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERDV2. BellSouth will not issue line-based calling cards in the name of MPOWERDV2’s individual end users. In the event that MPOWER DV2 wants to include calling card numbers assigned by the MPOWER DV2 in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER DV2 has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER DV2 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. MPOWER DV2 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 MPOWER DV2 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. MPOWER DV2 must have its own unique XXX code. Requests for establishment of XXX RAO status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from MPOWER DV2 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 RAO code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER DV2 and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER DV2 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 MPOWERDV2.

Appears in 1 contract

Samples: Clec Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Level 3 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERLevel 3. BellSouth will not issue line-based calling cards in the name of MPOWERLevel 3’s individual end users. In the event that MPOWER Level 3 wants to include calling card numbers assigned by the MPOWER Level 3 in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Level 3 has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Level 3 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. MPOWER Level 3 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 MPOWER Level 3 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. MPOWER Level 3 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 MPOWER Level 3 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 MPOWER Level 3 and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Level 3 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 MPOWERLevel 3. 7. All data received from Level 3 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 Level 3 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 Level 3 and will forward them to Level 3 on a daily basis. 10. Transmission of message data between BellSouth and Level 3 will be via CONNECT:Direct. 11. All messages and related data exchanged between BellSouth and Level 3 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. Level 3 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

Appears in 1 contract

Samples: Interconnection Agreement

RESPONSIBILITIES OF PARTIES. A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER Network Telephone 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, BellSouth 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 BellSouth 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 BellSouth’s reasonable control. BellSouth 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, BellSouth will issue line-based calling cards only in the name of MPOWERNetwork Telephone. BellSouth will not issue line-based calling cards in the name of MPOWERNetwork Telephone’s individual end users. In the event that MPOWER Network Telephone wants to include calling card numbers assigned by the MPOWER Network Telephone in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth 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 BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER Network Telephone has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00. 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER Network Telephone 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. MPOWER Network Telephone 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 MPOWER Network Telephone 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. MPOWER Network Telephone 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 MPOWER Network Telephone 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 XxxxXxxxx will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER Network Telephone and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER Network Telephone 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 MPOWERNetwork Telephone.

Appears in 1 contract

Samples: Interconnection Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!