Virtual Collocation Interconnection Sample Clauses

The Virtual Collocation Interconnection clause establishes the terms under which one party may interconnect its equipment with another party’s network infrastructure without physically placing its own equipment on the premises. Instead, the service provider manages and maintains the necessary equipment on behalf of the interconnecting party, who accesses the network remotely. This arrangement is commonly used in telecommunications to facilitate network access while minimizing the need for physical space and on-site presence. The core function of this clause is to enable efficient network interconnection while reducing logistical and operational burdens associated with physical collocation.
Virtual Collocation Interconnection. When CLEC provides its own facilities or uses the facilities of a third party to an SBC-AMERITECH Tandem or, at CLEC’s option, End Office and wishes for SBC-AMERITECH to place transport terminating equipment at that location on CLEC’s behalf, CLEC may Interconnect using the provisions of Virtual Collocation as set forth in Article XII or applicable tariff. Virtual Collocation allows CLEC to choose the equipment vendor and does not require that CLEC be Physically Collocated.
View SourceView Similar (14)
Virtual Collocation Interconnection. When AT&T provides its own facilities or uses the facilities of a third party to an SBC-AMERITECH Tandem or, at AT&T’s option, End Office and wishes for SBC-AMERITECH to place transport terminating equipment at that location on AT&T’s behalf, AT&T may Interconnect using the provisions of Virtual Collocation as set forth in Article XII or applicable tariff. Virtual Collocation allows AT&T to choose the equipment vendor and does not require that AT&T be Physically Collocated.
View SourceView Similar (4)
Virtual Collocation Interconnection. 9.1 Subject to space availability and technical feasibility, PACIFIC will provide Virtual Collocation in accordance with the Act, the FCC rules promulgated thereunder (e.g., 47 C.F.R. § 51.323), and any Commission decision. Unless inconsistent with this Section 9, Virtual Collocation Interconnection will be provided as set forth in Pacific B▇▇▇'▇ interstate Virtual Collocation tariffs (Pacific B▇▇▇'▇ Tariff FCC No.128). 9.1.1 If Pac-West designates permitted telecommunications equipment for Virtual Collocation that is not set forth in Pacific B▇▇▇'▇ interstate tariff, the provisioning of such telecommunications equipment shall be handled in the same manner as is used by PACIFIC for provisioning non-tariffed equipment under its interstate Virtual Collocation tariffs; provided, however, that in no event shall PACIFIC be required to file any tariff, whether interstate or intrastate in jurisdiction. By way of example and not limitation, Pac-West would apply for, and PACIFIC would price, provide, and b▇▇▇ such telecommunications equipment as if under PACIFIC's interstate virtual collocation tariff. 9.2 When providing Virtual Collocation, PACIFIC will, at a minimum, install, maintain, and repair Virtual Collocation equipment for Pac-West within the same time periods and with failure rates that are no greater than those that apply to the performance of similar functions for comparable equipment of PACIFIC. 9.3 PACIFIC will provide Virtual Collocation in "Eligible Structures", as defined in Appendix PHYSICAL COLLOCATION, which may be added by written amendment to this Agreement and permit the Virtual Collocation of telecommunications equipment permitted by 47 U.S.C. § 251(c) (6), FCC rules promulgated thereunder (e.g., 47 C.F.R. § 51.323), and Commission decisions. 9.3.1 Notwithstanding any other provision hereof, PACIFIC is under no obligation to provide and shall not provide Virtual Collocation for any equipment that, by its nature or due to its characteristics and methods of operation, interferes with or impairs service over PACIFIC's network, equipment, or facilities, or the network, equipment, or facilities of any other person or entity; creates hazards for or cause damage to those networks, equipment, or facilities, the Premises, or the Eligible Structure; impairs the privacy of any communications carried in, from, or through the Eligible Structure; or creates hazards or cause physical harm to any person, entity, or the public. The terms "Premises" and "Elig...
View Source
Virtual Collocation Interconnection. 3.2.1 When LEVEL 3 provides its own facilities or uses the facilities of a 3rd party to a SBC-13STATE Tandem or End Office and requests that SBC-13STATE place transport terminating equipment at that location on LEVEL 3’s behalf, LEVEL 3 may Interconnect using the provisions of Virtual Collocation as set forth in Appendix Virtual Collocation or applicable state tariff. Virtual Collocation allows LEVEL 3 to choose the equipment vendor and does not require that LEVEL 3 be Physically Collocated.
View Source

Related to Virtual Collocation Interconnection

  • Interconnection Facilities 4.1.1 The Interconnection Customer shall pay for the cost of the Interconnection Facilities itemized in Attachment 2 of this Agreement. The NYISO, in consultation with the Connecting Transmission Owner, shall provide a best estimate cost, including overheads, for the purchase and construction of its Interconnection Facilities and provide a detailed itemization of such costs. Costs associated with Interconnection Facilities may be shared with other entities that may benefit from such facilities by agreement of the Interconnection Customer, such other entities, the NYISO, and the Connecting Transmission Owner. 4.1.2 The Interconnection Customer shall be responsible for its share of all reasonable expenses, including overheads, associated with (1) owning, operating, maintaining, repairing, and replacing its own Interconnection Facilities, and

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

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