Traffic Measurement and Billing over Interconnection Trunks Sample Clauses

The 'Traffic Measurement and Billing over Interconnection Trunks' clause defines how telecommunications traffic exchanged between interconnected networks is measured and billed. It typically outlines the methods and equipment used to record call volumes, durations, or data usage across the interconnection points, and specifies how this information is used to calculate charges between the parties. By establishing clear procedures for traffic measurement and billing, this clause ensures accurate compensation for network usage and helps prevent disputes over traffic volumes or billing discrepancies.
POPULAR SAMPLE Copied 1 times
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 ▇▇▇▇ 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 ▇▇▇▇ 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 ▇▇▇▇ 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 ▇▇▇▇ 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
View SourceView Similar (281)
Traffic Measurement and Billing over Interconnection Trunks. 4.1 The Parties will provide each other with the proper call information, including all proper translations for routing between networks and any information necessary for billing. 4.2 Each Party reserves the right to audit, at its own expense, all traffic and any associated billing as specified in this Section of the Agreement, up to a maximum of two audits per calendar year to ensure that only Local Traffic is being routed on the Interconnection Trunks and that rates are being applied appropriately. Each Party agrees to provide the necessary Traffic data in conjunction with any such audit in a timely manner. 4.3 To the extent technically and economically feasible, each Party shall pass unaltered Calling Party Number (CPN) information on each call. The Parties agree that they will not populate the CPN field in the call detail record with a Wholesale Cust billing or local routing number but will utilize the s CPN or billing number. 4.3.1 Where possible, actual call detail records including the CPN, will be used by the terminating Party for purposes of auditing the scope of traffic. Where a terminating Party has the capability, it will use the actual call detail records including the CPN information associated with each specific call to identify traffic delivered by the other Party as either Local Traffic, or traffic that is not within the scope of this Agreement. 4.3.2 When a terminating Party receives insufficient call detail or the CPN is missing or masked, and therefore cannot determine whether the call is or is not within the scope of this Agreement, and if the percentage of traffic delivered with CPN and having sufficient detail is greater than 90% of total calls delivered, the calls without sufficient detail or CPN will be presumed to be in the same proportion as the calls having sufficient detail and CPN. If traffic delivered by one Party to the other Party has CPN and sufficient call detail on fewer than 90% of the calls, the terminating Party may provide written notice of a billing dispute to the other Party delivering such calls below the 90 percent threshold. Upon such notice, the Party delivering the traffic to the other Party (the "Delivering Party) shall have 30 days to investigate and correct the lack of CPN and report the date the problem was corrected to the other Party (th rminati provide evidence indicating the nature of calls that have insufficient call detail or lack a CPN. If the problem cannot be repaired within 30 days of the written...
View SourceView Similar (8)
Traffic Measurement and Billing over Interconnection Trunks. 4.1 Each Party shall calculate terminating interconnection minutes of use based on standard AMA recordings made within each Party's network, these recordings being necessary for each Party to generate bills to the other Party. In the event either Party cannot measure minutes terminating on its network, the other Party shall provide the measuring mechanism or the Parties shall otherwise agree on an alternate arrangement. Any disputes arising out of this Section may be resolved using EDR. 4.1.1 For the purposes of this agreement, minutes of use shall be measured in accordance with 47 C.F.R. § 69.2. Minutes of use over each individual trunk group will be totaled for the entire monthly b▇▇▇ period and then rounded to the next whole minute. 4.1.2 If CSPR fails to pass the ANI on any call, PRTC will b▇▇▇ CSPR as if the call were a toll call and will assess tandem charges. 4.2 For the purpose of permitting the delivering Party to identify ISP-Bound Traffic and to deliver such ISP-Bound Traffic to the receiving Party, within five (5) days after the Effective Date of this Agreement, each Party shall use its best efforts to deliver to the other Party in writing a true and complete list of all telephone numbers then in use by each Internet Service Provider served by that Party. Thereafter, each Party shall, in writing, update the list delivered to the other Party expressly and distinctly to reflect (i) the addition or restoration of one or more telephone numbers to be used by any Internet Service Provider served or to be served by that Party and/or (ii) the termination, whether temporarily or permanently, of one or more previously listed telephone numbers from use by any Internet Service Provider served by that Party. Any such update shall be delivered to the other Party reasonably in advance of the use or termination, as the case may be, of the subject telephone number by any Internet Service Provider served or to be served by the updating Party to permit the other Party to satisfy the requirements of this Agreement. Without limiting the scope or effectiveness of the foregoing, beginning three (3) months after the Effective Date of this Agreement and continuing thereafter at three (3) month intervals, each Party shall deliver to the other Party in writing a true and complete list of all telephone numbers then in use by each Internet Service Provider served by that Party. 4.3 Each Party reserves the right to audit all Traffic, up to a maximum of two audits per calend...
View Source
Traffic Measurement and Billing over Interconnection Trunks iFnofor rmbialltiniogn puornposes, each Party shall pass Calling Party Number (CPN) Interconnection at least ninety-five percent (95%) of calls carried over the Trunks.
View Source
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.
View SourceView Similar (5)

Related to Traffic Measurement and Billing over Interconnection Trunks

  • 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.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center. 2.4.3 On a semi-annual basis, Teleconex shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.‌‌‌‌‌‌‌ 2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5). 2.4.7 Two-Way Local Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards. 2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.

  • Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection. 2.1.1 Each Party, at its own expense, shall provide transport facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA selected by PNG.

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection. 1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.