Segregating and Tracking FX Traffic Clause Samples

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 & ▇▇▇▇▇, 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.
View SourceView Similar (59)
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.
View SourceView Similar (9)
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.
View Source
Segregating and Tracking FX Traffic 
View SourceView Similar (55)

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.

  • Secure Information Handling and Transfers 7.1 Physical and electronic handling, processing and transferring of DWP Data, including secure access to systems and the use of encryption where appropriate.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.