Common use of Meet Point Billing Clause in Contracts

Meet Point Billing. A. Meet Point Billing (MPB), as supported by Multiple Exchange Carrier Access Billing (MECAB) guidelines, shall mean the exchange of billing data relating to jointly provided switched access calls and Intermediary Traffic. MECAB refers to the document prepared by the Billing Committee of the Ordering and Billing Forum (OBF), which functions under the auspices of the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solutions (ATIS). The MECAB document, published by Telcordia as Special Report SR-BDS-000983, contains the recommended guidelines for the billing of Switched Access Traffic and Intermediary Traffic provided by two or more telecommunications carriers. Subject to Carrier providing all necessary information, BellSouth agrees to participate in MPB for Switched Access Traffic (as described in BellSouth’s Tariffs) and Intermediary Traffic. In the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇ agrees to keep BellSouth whole for such traffic as stipulated in Section VII C. above. BellSouth shall pass Electronic Message Interface (EMI) 1101 call records to Carrier at no charge. Depending on the delivery medium selected by Carrier, appropriate charges for that delivery medium will be applied. Notwithstanding the foregoing, for purposes of MPB, where either or both of the originating or terminating carrier of Intermediary Traffic does not have MPB capability, Section VII C. will apply. B. Information required from Carriers participating in MPB with BellSouth includes, but is not limited to: (1) Regional Accounting Office code (▇▇▇), (2) Operating Company Number (OCN) per state for each entity to be billed (if an C. MPB will be provided for Switched Access Traffic and Intermediary Traffic at the access tandem level only. Parties utilizing MPB must subscribe to access tandem level interconnections with BellSouth and must deliver all Intermediary Traffic to BellSouth over such access tandem level interconnections. Additionally, exchange of records will necessitate both the originating and terminating networks to subscribe to dedicated NXX codes, which can be identified as belonging to the originating and terminating network. NPA/NXX codes are presented in the Local Exchange Routing Guide (LERG) in association with a specific switch Common Language Location Identification (CLLI). Under national programming rules associated with Carrier Access Billing Systems (CABS), each CLLI is associated with a single rate center. Additionally, (i) if the Carrier has Type 2A and Non-Type 2A NPA/NXX codes associated with a single CLLI or, (ii) if the CLLI is associated with additional NPA/NXX codes with rate centers outside of BellSouth’s service area or, (iii) if the Type 2A NPA/NXX code or CLLI home on a non-BellSouth SHA “00” tandem or are in a disassociated LATA, then those NPA/NXX codes and CLLI codes will not be included in MPB and Switched Access Traffic and Intermediary Traffic associated with those NPA/NXX codes will continue to be billed in accordance with the provisions of Section VII C. When converting to MPB, if Carrier has NPA/NXX codes with more than a single rate center terminating to a given CLLI, Carrier must provide BellSouth with information stating which BellSouth rate center will be associated with the CLLI. MPB is not available when the access tandem at which the Parties have interconnected does not have the capability to measure actual traffic. D. In a MPB environment, when Carrier utilizes services provided by BellSouth that are necessary to deliver certain types of calls (e.g. Local Number Portability queries and 800 Data Base queries), Carrier will be billed applicable charges as set forth in BellSouth’s federal or state access tariffs, as appropriate. In the alternative, Carrier may perform the appropriate database queries prior to delivery of such traffic to BellSouth. E. Participation in MPB is outside the reciprocal compensation requirements of this Agreement. Under MPB, Carrier will compensate BellSouth at the rate set forth in Section VII.C of this Agreement for Carrier originated Intermediary Traffic. Meet Point Billing to IXCs for jointly provided switched access traffic will be consistent with the most current MECAB billing guidelines. F. Exchange of records will begin no earlier than ninety days (90) from the later of the date the contract is signed or the date that all necessary information as defined in Section VIII.B above is provided. Once Carrier sets up MPB arrangements for Intermediary Traffic, Intermediary Traffic will be subject to only the $.002 per minute Intermediary Charge (or such other rate ordered by the state), and Third Party Termination Charges shall not apply. Notwithstanding the foregoing, in the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇ agrees to keep BellSouth whole for such traffic as stipulated in Section VII C. above. MPB as described in this Section VIII anticipates that Carrier will enter into interconnection or traffic exchange agreements with Third Party Carriers who terminate traffic originated by Carrier. ▇▇▇▇▇▇▇ will be liable to BellSouth for any charges, costs and fees BellSouth may incur for delivering Carrier’s Intermediary Traffic.

Meet Point Billing. A. For purposes of this Agreement, Meet Point Billing (MPB)Billing, as supported by Multiple Exchange Carrier Access Billing (MECAB) guidelines, shall mean the exchange of billing data relating to jointly provided switched access calls and/or calls transiting BellSouth's network from an originating telecommunications carrier other than BellSouth and Intermediary Traffic. MECAB refers terminating to a telecommunications carrier other than BellSouth or the document prepared by the Billing Committee of the Ordering and Billing Forum (OBF), which functions under the auspices of the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solutions (ATIS). The MECAB document, published by Telcordia as Special Report SR-BDS-000983, contains the recommended guidelines for the billing of Switched Access Traffic and Intermediary Traffic provided by two or more originating telecommunications carrierscarrier. Subject to Carrier AWS providing all necessary information, BellSouth agrees to participate in MPB for Switched Access Traffic (as described in BellSouth’s Tariffs) and Intermediary Traffic. In the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇▇▇ agrees to keep BellSouth whole participate in Meet Point Billing for such traffic as stipulated which transits it’s network when both the originating and terminating parties participate in Section VII C. aboveMeet Point Billing with BellSouth. BellSouth shall pass Electronic Message Interface (EMI) 1101 Traffic from a network which does not participate in Meet Point Billing will be delivered by ▇▇▇▇▇▇▇▇▇, however, call records for traffic originated and/or terminated by a non-Meet Point Billing network will not be delivered to Carrier at no charge. Depending on the delivery medium selected by Carrier, appropriate charges for that delivery medium will be applied. Notwithstanding the foregoing, for purposes of MPB, where either or both of the originating or and/or terminating carrier of Intermediary Traffic does not have MPB capability, Section VII C. will applynetwork. B. Parties participating in Meet Point Billing with BellSouth are required to provide information necessary for BellSouth to identify the parties to be billed. Information required from Carriers participating in MPB with BellSouth for Meet Point Billing includes, but is not limited to: ; (1) Regional Accounting Office code (▇▇▇), (2) Operating Company Number (OCN), (3) per state a unique Access Carrier Name Abbreviation (ACNA), (4) Percent Interstate Usage (PIU), (5) Percent Local Usage (PLU), (6) 800 Service Percent Interstate Usage or default of 50%, and (7) Billing Interconnection Percentage. A default Billing Interconnection Percentage of 95% BellSouth and 5% AWS will be used if AWS does not file with NECA to establish a Billing Interconnection Percentage. AWS must support Meet Point Billing for each entity to all intermediary calls in accordance with Mechanized Exchange Carrier Access Billing (MECAB) guidelines. The Parties acknowledge that the exchange of 1150 records will not be billed (if anrequired. C. MPB Meet Point Billing will be provided for Switched Access Traffic and Intermediary Traffic traffic which transits BellSouth’s network at the access tandem level only. Parties utilizing MPB must desiring Meet Point Billing will subscribe to access tandem level interconnections (Type 2A Interconnection) with BellSouth and must will deliver all Intermediary Traffic to BellSouth over such access tandem level interconnections. Additionally, exchange of records will necessitate both the originating and terminating networks to subscribe to dedicated NXX codes, which can be identified as belonging to the originating and terminating network. NPA/NXX codes are presented in the Local Exchange Routing Guide (LERG) in association with a specific switch Common Language Location Identification (CLLI). Under national programming rules associated with Carrier Access Billing Systems (CABS), each CLLI is associated with a single rate center. Additionally, (i) if the Carrier has Type 2A and Non-Type 2A NPA/NXX codes associated with a single CLLI or, (ii) if the CLLI is associated with additional NPA/NXX codes with rate centers outside of BellSouth’s service area or, (iii) if the Type 2A NPA/NXX code or CLLI home on a non-BellSouth SHA “00” tandem or are in a disassociated LATA, then those NPA/NXX codes and CLLI codes will not be included in MPB and Switched Access Traffic and Intermediary Traffic associated with those NPA/NXX codes will continue to be billed in accordance with the provisions of Section VII C. When converting to MPB, if Carrier has NPA/NXX codes with more than a single rate center terminating to a given CLLI, Carrier must provide BellSouth with information stating which BellSouth rate center will be associated with the CLLI. MPB is not available when the access tandem at tandem, in which the Parties have interconnected interconnection occurs, does not have the capability to measure actual trafficrecord messages and either surrogate or self-reporting of messages and minutes of use occur, Meet Point Billing will not be possible and will not occur. The Parties will work cooperatively to develop and enhance processes to deal with messages handled on a surrogate or self- reporting basis. D. In a MPB Meet Point Billing environment, when Carrier utilizes services a party actually uses a service provided by BellSouth that are necessary to deliver certain types of calls (e.g. Local Number Portability queries and 800 Data Base queries)▇▇▇▇▇▇▇▇▇, Carrier said party will be billed applicable charges for miscellaneous usage charges, as set forth defined in BellSouth’s federal or FCC No.1 and appropriate state access tariffs, as appropriate. In the alternative, Carrier may perform the appropriate database queries prior to delivery of such traffic to BellSouth.(i.e. E. Participation in MPB Meet Point Billing is outside the reciprocal compensation requirements of this Agreement. Under MPBMeet Point Billing, Carrier as defined in VI. A above, will compensate result in AWS compensating BellSouth at the intermediary rate set forth in Section VII.C V. D of this Agreement for Carrier originated Intermediary Traffictraffic delivered to BellSouth’s network, which terminates to another telecommunications carrier. Meet Point Billing to IXCs for jointly provided switched access Switched Access Service traffic will be occur consistent with the most current MECAB billing guidelines. F. Exchange Commencement of exchange of records will begin no earlier than ninety days (90) from the later of the date the contract is signed or the date that all necessary information as defined in Section VIII.B above is provided. Once Carrier sets up MPB arrangements for Intermediary Traffic, Intermediary Traffic will be subject to only the $.002 per minute Intermediary Charge (or such other rate ordered by the state), and Third Party Termination Charges shall not apply. Notwithstanding the foregoing, in the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇ agrees to keep BellSouth whole for such traffic as stipulated in Section VII C. above. MPB as described in this Section VIII anticipates that Carrier will enter into interconnection or traffic exchange agreements with Third Party Carriers who terminate traffic originated by Carrier. ▇▇▇▇▇▇▇ will be liable to BellSouth for any charges, costs and fees BellSouth may incur for delivering Carrier’s Intermediary Traffic.sixty

Meet Point Billing. A. For purposes of this Agreement, Meet Point Billing (MPB)Billing, as supported by Multiple Exchange Carrier Access Billing (MECAB) guidelines, shall mean the exchange of billing data relating to which details jointly provided switched access calls and Intermediary Traffic. MECAB refers calls transiting BellSouth's network from an originating telecommunications carrier other than BellSouth and terminating to a telecommunications carrier other than BellSouth or the document prepared by the Billing Committee of the Ordering and Billing Forum (OBF), which functions under the auspices of the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solutions (ATIS). The MECAB document, published by Telcordia as Special Report SR-BDS-000983, contains the recommended guidelines for the billing of Switched Access Traffic and Intermediary Traffic provided by two or more originating telecommunications carrierscarrier. Subject to Carrier providing all necessary information, BellSouth agrees to participate in MPB Meet Point Billing for Switched Access Traffic (as described traffic which transits it’s network when both the originating and terminating parties participate in Meet Point Billing with BellSouth and/or originate and/or terminate switched access traffic to carrier via BellSouth’s Tariffs) and Intermediary Traffic. In the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇ agrees to keep BellSouth whole for such traffic as stipulated in Section VII C. above's network. BellSouth shall pass Electronic Message Interface (EMI) 1101 call provide billable records to Carrier at no charge. Depending on upon the delivery medium selected by Carrier, appropriate charges for that delivery medium will be applied. Notwithstanding the foregoingTraffic from a network which does not participate in Meet Point Billing will be delivered by BellSouth, however, call records for purposes of MPB, where either or both of traffic originated and/or terminated by a non-Meet Point Billing network will not be delivered to the originating or and/or terminating carrier of Intermediary Traffic does not have MPB capability, Section VII C. will apply. B. network. Parties participating in Meet Point Billing with BellSouth are required to provide information necessary for BellSouth to identify the parties to be billed. Information required from Carriers participating in MPB with BellSouth includes, but is not limited to: (1) for Meet Point Billing includes Regional Accounting Office code (▇▇▇), (2) and Operating Company Number (OCN) per state state. The following information is required for each entity billing in a Meet Point Billing environment and includes, but is not limited to; (1) a unique Access Carrier Name Abbreviation (ACNA), (2) Percent Interstate Usage, (3) Percent Local Usage, (4) 800 Service Percent Interstate Usage or default of 50%, and (5) Billing Interconnection Percentage. A default Billing Interconnection Percentage of 95% BellSouth and 5% Carrier will be used if Carrier does not file with NECA to establish a Billing Interconnection Percentage other than default. Carrier must support Meet Point Billing for all intermediary calls in accordance with Mechanized Exchange Carrier Access Billing (MECAB) guidelines. The parties acknowledge that the exchange of 1150 records will not be billed (if anrequired. C. MPB B. Meet Point Billing will be provided for Switched Access Traffic and Intermediary Traffic traffic which transits BellSouth’s network at the access tandem level only. Parties utilizing MPB must Where Carrier desires Meet Point Billing, Carrier will subscribe to access tandem level interconnections with BellSouth and must BellSouth. Carrier will deliver all Intermediary Traffic transit traffic to BellSouth over such access tandem level interconnections. Carrier may continue to establish End-Office interconnections, however, billable records will not be provided by BellSouth to Carrier for traffic delivered to Carrier by this facility. Additionally, exchange of records will necessitate both the originating and terminating networks to subscribe to dedicated NXX codes, which can be identified as belonging to the originating and terminating network. NPA/NXX codes are presented in the Local Exchange Routing Guide (LERG) in association with a specific switch Common Language Location Identification (CLLI). Under national programming rules associated with Carrier Access Billing Systems (CABS), each CLLI is associated with a single rate center. Additionally, (i) if the Carrier has Type 2A and Non-Type 2A NPA/NXX codes associated with a single CLLI or, (ii) if the CLLI is associated with additional NPA/NXX codes with rate centers outside of BellSouth’s service area or, (iii) if the Type 2A NPA/NXX code or CLLI home on a non-BellSouth SHA “00” tandem or are in a disassociated LATA, then those NPA/NXX codes and CLLI codes will not be included in MPB and Switched Access Traffic and Intermediary Traffic associated with those NPA/NXX codes will continue to be billed in accordance with the provisions of Section VII C. When converting to MPB, if Carrier has NPA/NXX codes with more than a single rate center terminating to a given CLLI, Carrier must provide BellSouth with information stating which BellSouth rate center will be associated with the CLLI. MPB is not available when the access tandem at tandem, in which the Parties have interconnected interconnection occurs, does not have the capability to measure actual traffic.record messages and D. In a MPB environment, when Carrier utilizes services provided by BellSouth that are necessary to deliver certain types of calls (e.g. Local Number Portability queries and 800 Data Base queries), Carrier will be billed applicable charges as set forth in BellSouth’s federal or state access tariffs, as appropriate. In the alternative, Carrier may perform the appropriate database queries prior to delivery of such traffic to BellSouth. E. C. Participation in MPB Meet Point Billing is outside the reciprocal compensation requirements of this Agreementagreement. Under MPBMeet Point Billing, as defined in VII. A above, under this Section will result in Carrier will compensate compensating BellSouth at the intermediary rate set forth in Section VII.C VI. D of this Agreement for Carrier originated Intermediary Traffictraffic delivered to BellSouth’s network, which terminates to a third party network. Meet Point Billing to IXCs for jointly provided switched access traffic will be occur consistent with the most current MECAB billing guidelines. F. Exchange D. Commencement of exchange of records will begin no earlier than ninety sixty days (90) from the later of date of, the date the contract is signed or the date that all necessary information as defined in Section VIII.B VII. A above is provided. The date the Parties begin the exchange of records process will be the date that the percentages in Section VI. D of this Agreement will no longer be applied to determine what percentage of the non-local traffic delivered by BellSouth to Carrier shall be subject to Non-Local Intermediary charges. Once Carrier sets up MPB has established, as between it and BellSouth, meet-point billing arrangements for Intermediary TrafficTransit Traffic from Non-party Carriers, Intermediary Transit Traffic will be subject only to only the $.002 per minute Intermediary Charge (or such other rate ordered by the state), and Third Party Termination Charges shall not apply. Notwithstanding the foregoing, in the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇ agrees to keep BellSouth whole for such traffic as stipulated in Section VII C. above. MPB as described in this Section VIII anticipates that Carrier will enter into interconnection or traffic exchange agreements with Third Party Carriers who terminate traffic originated by Carrier. ▇▇▇▇▇▇▇ will be liable to BellSouth for any charges, costs and fees BellSouth may incur for delivering Carrier’s Intermediary Traffic.the

Meet Point Billing. A. For purposes of this Agreement, Meet Point Billing (MPB)Billing, as supported by Multiple Exchange Carrier Access Billing (MECAB) guidelines, shall mean the exchange of billing data relating to jointly provided switched access calls and/or calls transiting BellSouth's network from an originating telecommunications carrier other than BellSouth and Intermediary Traffic. MECAB refers terminating to a telecommunications carrier other than BellSouth or the document prepared by the Billing Committee of the Ordering and Billing Forum (OBF), which functions under the auspices of the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solutions (ATIS). The MECAB document, published by Telcordia as Special Report SR-BDS-000983, contains the recommended guidelines for the billing of Switched Access Traffic and Intermediary Traffic provided by two or more originating telecommunications carrierscarrier. Subject to Carrier providing all necessary information, BellSouth agrees to participate in MPB for Switched Access Traffic (as described in BellSouth’s Tariffs) and Intermediary Traffic. In the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇▇▇ agrees to keep BellSouth whole participate in Meet Point Billing for such traffic as stipulated in Section VII C. above. BellSouth shall pass Electronic Message Interface (EMI) 1101 call records to Carrier at no charge. Depending on the delivery medium selected by Carrier, appropriate charges for that delivery medium will be applied. Notwithstanding the foregoing, for purposes of MPB, where either or which transits it’s network when both of the originating or and terminating carrier of Intermediary parties participate in Meet Point Billing with BellSouth. Traffic does not have MPB capability, Section VII C. will apply.from a B. Parties participating in Meet Point Billing with BellSouth are required to provide information necessary for BellSouth to identify all parties to be billed. Information required from Carriers participating in MPB with BellSouth includes, for Meet Point Billing includes but is not limited to: (1) Regional Accounting Office code (▇▇▇), (2) Operating Company Number (OCN) and/or Company Code (CC) per state for each entity to be billed (if anan OCN/CC is not available for each billed entity BST will render a single bill to Carrier), (3) a unique Access Carrier Name Abbreviation (ACNA), (4) Percent Interstate Usage, (5) Percent Local Usage, (6) 800 Service Percent Interstate Usage or default of 50%, (7) Billing Interconnection Percentage, and, (8) a Screening Telephone Number (STN) from a dedicated NXX associated with each Trunk Group subscribed to by Carrier. A default Billing Interconnection Percentage of 1% BellSouth and 99% Carrier will be used if Carrier does not file with NECA to establish a Billing Interconnection Percentage other than default. Carrier must support Meet Point Billing for all intermediary calls in accordance with Mechanized Exchange Carrier Access Billing (MECAB) guidelines. The parties acknowledge that the exchange of 1150 records will not be required. C. MPB Meet Point Billing will be provided for Switched Access Traffic and Intermediary Traffic traffic which transits BellSouth’s network at the access tandem level only. Parties utilizing MPB must desiring Meet Point Billing will subscribe to access tandem level interconnections (Type 2A Interconnections) with BellSouth and must will deliver all Intermediary Traffic transit traffic to BellSouth over such access tandem level interconnections. Additionally, exchange of records will necessitate both the originating and terminating networks to subscribe to dedicated NXX codescodes having rate centers within BellSouth’s franchised service area, which can be identified as belonging to the originating and terminating network. NPA/NXX codes are presented in the Local Exchange Routing Guide (LERG) in association with a specific switch Common Language Location Identification (CLLI). Under national programming rules associated with Carrier Access Billing Systems (CABS), each CLLI is associated with a single rate center. Additionally, (i) if the Carrier has Type 2A and Non-Type 2A NPA/NXX codes associated with a single CLLI or, (ii) if the CLLI is associated with additional NPA/NXX codes with rate centers outside of BellSouth’s service area or, (iii) if the Type 2A NPA/NXX code or CLLI home on a non-BellSouth SHA “00” tandem or are in a disassociated LATA, then those NPA/NXX codes and CLLI codes will not be included in MPB and Switched Access Traffic and Intermediary Traffic associated with those NPA/NXX codes will continue to be billed in accordance with the provisions of Section VII C. When converting to MPB, if Carrier has NPA/NXX codes with more than a single rate center terminating to a given CLLI, Carrier must provide BellSouth with information stating which BellSouth rate center will be associated with the CLLI. MPB is not available when the access tandem at in which the Parties have interconnected interconnection occurs does not have the capability to measure actual trafficrecord messages, and either surrogate or self-reporting of messages and minutes of use occur, Meet Point Billing will not be possible and will not occur. The parties will work cooperatively to develop and enhance processes to deal with messages handled on a surrogate or self-reporting basis. D. In a MPB Meet Point Billing environment, when Carrier utilizes services a party actually uses a service provided by BellSouth that are necessary ▇▇▇▇▇▇▇▇▇, and said party desires to deliver certain types of calls participate in Meet Point Billing with BellSouth, said party will be billed for miscellaneous usage charges, as defined in BellSouth’s FCC No.1 and appropriate state access tariffs, (e.g. i.e. Local Number Portability queries and 800 Data Base queries), Carrier will be billed applicable charges as set forth in BellSouth’s federal or state access tariffs, as appropriate. In the alternative, Carrier may perform the appropriate database queries prior to delivery of such traffic to BellSouth.Base E. Participation in MPB Meet Point Billing is outside the reciprocal compensation requirements of this Agreement. Under MPBMeet Point Billing, as defined in paragraph A above, under this Section will result in Carrier will compensate compensating BellSouth at the intermediary rate set forth in Section VII.C VI. D of this the Agreement for Carrier originated Intermediary Traffictraffic delivered to BellSouth’s network, which terminates to a third party network. Meet Point Billing to IXCs for jointly provided switched access traffic will be occur consistent with the most current MECAB billing guidelines. F. Exchange Commencement of exchange of records will begin no earlier than ninety days (90) days from the later date of the date the contract is signed or the date that all necessary information as defined in Section VIII.B paragraph B above is provided. Once The date the Parties begin the exchange of records process will be the date that the percentages in Section VI.D of the Agreement will no longer be applied to determine what percentage of the non-local traffic delivered to BellSouth by Carrier sets up MPB arrangements for Intermediary Traffic, Intermediary Traffic will shall be subject to only the $.002 per minute Non-Local Intermediary Charge (or such other rate ordered by the state), and Third Party Termination Charges shall not apply. Notwithstanding the foregoing, in the event a Third Party Carrier continues to charge BellSouth for Carriers’ Intermediary Traffic, ▇▇▇▇▇▇▇ agrees to keep BellSouth whole for such traffic as stipulated in Section VII C. above. MPB as described in this Section VIII anticipates that Carrier will enter into interconnection or traffic exchange agreements with Third Party Carriers who terminate traffic originated by Carrier. ▇▇▇▇▇▇▇ will be liable to BellSouth for any charges, costs and fees BellSouth may incur for delivering Carrier’s Intermediary Traffic.