Segregating and Tracking FX Traffic Sample Clauses

Segregating and Tracking FX Traffic. 6.5.2.4.1 For AT&T-21STATE, the terminating carrier is responsible for separately identifying IntraLATA Virtual FX, Dedicated FX and FX-type traffic from other types of Intercarrier traffic for compensation purposes. The terminating carrier will be responsible for providing the originating carrier with an FX usage summary which includes a ten (10) digit telephone number level detail of the MOUs terminated to FX Telephone Numbers on its network each month (or in each applicable billing period, if not billed monthly), or by any means mutually agreed by the Parties. 6.5.2.4.2 Terminating carrier will not assess compensation charges to the Voice FX MOU and ISP FX MOU in AT&T-21STATE. 6.5.2.4.3 In AT&T-21STATE either Party may request an audit of the FX Usage Summary or the FX Factor on no fewer than thirty (30) Business Day’s written Notice and any audit shall be accomplished during normal business hours at the office of the Party being audited. Such audit must be performed by a mutually agreed-to auditor paid for by the Party requesting the audit. If mutual agreement cannot be reached, the Parties shall use one of the following independent auditors: PricewaterhouseCoopers, Ernst & Young, KPMG, or Deloitte Touche Tohmatsu (Big-4 Auditors). Selection of the Big-4 Auditor shall be made by the Party requesting the audit and the selected Big-4 Auditor must be independent as determined by current accounting and auditing standards promulgated by the appropriate accounting governing body. Such audits shall be requested within six
Segregating and Tracking FX Traffic. 6.5.2.4.1 For AT&T-21STATE, the terminating carrier is responsible for separately identifying IntraLATA Virtual FX, Dedicated FX and FX-type traffic from other types of Intercarrier traffic for compensation purposes. The terminating carrier will be responsible for providing the originating carrier with an FX usage summary which includes a ten (10) digit telephone number level detail of the MOUs terminated to FX Telephone Numbers on its network each month (or in each applicable billing period, if not billed monthly), or by any means mutually agreed by the Parties. 6.5.2.4.2 Terminating carrier will not assess compensation charges to the Voice FX MOU and ISP FX MOU in AT&T-21STATE. 6.5.2.4.3 In AT&T-21STATE either Party may request an audit of the FX Usage Summary or the FX Factor on no fewer than thirty (30) Business Day’s written Notice and any audit shall be accomplished during normal business hours at the office of the Party being audited. Such audit must be performed by a mutually agreed-to auditor paid for by the Party requesting the audit. If mutual agreement cannot be reached, the Parties shall use one of the following independent auditors: PricewaterhouseCoopers, Ernst & Xxxxx, KPMG, or Deloitte Touche Tohmatsu (Big-4 Auditors). Selection of the Big- 4 Auditor shall be made by the Party requesting the audit and the selected Big-4 Auditor must be independent as determined by current accounting and auditing standards promulgated by the appropriate accounting governing body. Such audits shall be requested within six (6) months of having received the FX Usage Summary or the FX Factor and associated usage from the other Party and may not be requested more than twice per year, once per calendar year, unless the audit finds there has been a five percent (5%) or higher net error or variance in calculations, in which case a subsequent audit is required. Based upon the audit, previous compensation, billing and/or settlements will be adjusted for the past six (6) months. 6.5.2.4.3.1 If the FX factor is adjusted based upon the audit results, the adjusted FX factor will apply for the six (6) month period following the completion of the audit. If, as a result of the audit, either Party has overstated the FX factor or underreported the FX Usage by five percent (5%) or more, that Party shall reimburse the auditing Party for the cost of the audit and will pay for the cost of a subsequent audit which is to happen within nine (9) months of the initial audit.
Segregating and Tracking FX Traffic. For AT&T-21STATE, the terminating carrier is responsible for separately identifying IntraLATA Virtual FX, Dedicated FX and FX-type traffic from other types of Intercarrier traffic for compensation purposes. The terminating carrier will be responsible for providing the originating carrier with an FX usage summary which includes a ten (10) digit telephone number level detail of the MOUs terminated to FX Telephone Numbers on its network each month (or in each applicable billing period, if not billed monthly), or by any means mutually agreed by the Parties.
Segregating and Tracking FX Traffic. 3.10.2.1 For SBC-12STATE, the terminating carrier is responsible for separately identifying IntraLATA Virtual FX, Dedicated FX, and FX-type Traffic from other types of Intercarrier traffic for compensation purposes. The terminating carrier will be responsible for providing the originating carrier with an FX Usage Summary which includes a ten (10) digit telephone number level detail of the minutes of use terminated to FX Telephone Numbers on its network each month (or in each applicable billing period, if not billed monthly), or by any means mutually agreed by the Parties. 3.10.2.2 Terminating carrier will not assess compensation charges to the Voice FX MOU and ISP FX MOU in SBC-2STATE, SBC MIDWEST REGION 5-STATE, SBC Arkansas, SBC Kansas, SBC Missouri and SBC Texas where such traffic is subject to a Bill and Keep arrangement. 3.10.2.3 Originating carrier will apply the appropriate originating access charges to both the Voice FX MOU and ISP FX MOU in SBC Oklahoma. 3.10.2.4 For SBC Connecticut, FX traffic must be identified as voice FX and ISP FX. SBC Connecticut will work with Trinsic Communications, Inc. in reviewing its data to determine the volume of IntraLATA FX traffic being exchanged for an agreed- upon period of time. The parties may agree to use traffic studies, retail sales of Dedicated FX lines, or any other agreed method of estimating the FX traffic to be assigned a factor. Once the data review is completed, the Parties will estimate the percentage of minutes of use that is attributable to FX traffic. For SBC Connecticut ISP FX percentage will be assigned (“PIFX”) and voice FX percentage will be assigned (“PVFX”). The PIFX and PVFX (“FX factor”) will be used in lieu of providing the actual minutes of use data. This plan will be applied on an individual CLEC basis.
Segregating and Tracking FX Traffic 

Related to Segregating and Tracking FX Traffic

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • CUTTING AND PATCHING The Contractor shall be responsible for cutting, fitting or patching required to complete the Work or to make its parts fit together properly.

  • Open and Transparent Consistent with ICANN’s expressed mission and core values, ICANN shall operate in an open and transparent manner.