FCC Internet Order Sample Clauses

FCC Internet Order. Order on Remand and Report and Order, In the Matter of Implementation of the Local Competition Provisions in the Telecommunications Act of 1996, Intercarrier Compensation for ISP Bound Traffic, FCC 01-131, CC Docket Nos. 96-98 and 99-68, (adopted April 18, 2001).
FCC Internet Order. ‌‌‌‌‌‌‌‌‌
FCC Internet Order. Order on Remand and Report and Order, In the Matter of Implementation of the

Related to FCC Internet Order

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

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • Nyiso and Connecting Transmission Owner Authority General.‌‌ NYISO or Connecting Transmission Owner may take whatever actions with regard to the New York State Transmission System or the Connecting Transmission Owner’s Attachment Facilities it deems necessary during an Emergency State in order to (i) preserve public health and safety, (ii) preserve the reliability of the New York State Transmission System or the Connecting Transmission Owner’s Attachment Facilities, (iii) limit or prevent damage, and (iv) expedite restoration of service. NYISO and Connecting Transmission Owner shall use Reasonable Efforts to minimize the effect of such actions or inactions on the Large Generating Facility or the Developer’s Attachment Facilities. NYISO or Connecting Transmission Owner may, on the basis of technical considerations, require the Large Generating Facility to mitigate an Emergency State by taking actions necessary and limited in scope to remedy the Emergency State, including, but not limited to, directing Developer to shut-down, start-up, increase or decrease the real or reactive power output of the Large Generating Facility; implementing a reduction or disconnection pursuant to Article 13.4.2; directing the Developer to assist with blackstart (if available) or restoration efforts; or altering the outage schedules of the Large Generating Facility and the Developer’s Attachment Facilities. Developer shall comply with all of the NYISO and Connecting Transmission Owner’s operating instructions concerning Large Generating Facility real power and reactive power output within the manufacturer’s design limitations of the Large Generating Facility’s equipment that is in service and physically available for operation at the time, in compliance with Applicable Laws and Regulations.

  • Unbundled Digital Loops 2.3.1 BellSouth will offer UDLs. UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service. 2.3.2 BellSouth shall make available the following UDLs, subject to restrictions set forth herein:

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