Switching System Hierarchy Sample Clauses

Switching System Hierarchy. 4.2.1 For purposes of this Article IV, each of the following Central Office Switches shall be designated as a “Primary Switch”: (a) Each access Tandem Ameritech operates in the LATA; (b) The initial switch Requesting Carrier employs to provide Telephone Exchange Service in the LATA; (c) Any access Tandem Requesting Carrier may establish for provision of Exchange Access in the LATA; and (d) Any additional switch Requesting Carrier may subsequently employ to provide Telephone Exchange Service in the LATA which Requesting Carrier may at its sole option designate as a Primary Switch; provided that the total number of Requesting Carrier Primary Switches for a LATA may not exceed the total number of Ameritech’s Primary Switches for that LATA. To the extent Requesting Carrier chooses to designate any additional switch as a Primary Switch, it shall provide notice to Ameritech of such designation at least ninety (90) days in advance of the date on which Requesting Carrier activates such switch as a Primary Switch. 4.2.2 Each Central Office Switch operated by the Parties which is not designated as a Primary Switch pursuant to Section IV.2.1 shall be designated as a “Secondary Switch”. 4.2.3 For purposes of Requesting Carrier routing traffic to Ameritech, sub-tending arrangements between Ameritech Primary Switches and Ameritech Secondary Switches shall be the same as the access Tandem/End Office sub-tending arrangements which Ameritech maintains for those switches. For purposes of Ameritech routing traffic to Requesting Carrier, subtending arrangements between Requesting Carrier Primary Switches and Requesting Carrier Secondary Switches shall be the same as the access Tandem/End Office sub-tending arrangements which Requesting Carrier maintains for those switches. 4.2.4 Either Party may unilaterally reclassify its Central Office Switch as either a Primary Switch or Secondary Switch provided that such Party provides the other Party written notice thereof not less than one hundred and eighty (180) days prior to such reclassification.
Sample 1Sample 2See All (15)
AutoNDA by SimpleDocs
Switching System Hierarchy. For purposes of routing AWS traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic. For purposes of routing Verizon traffic to AWS, the subtending arrangements between AWS Tandem Switches (or functional equivalent) and AWS End Office Switches (or functional equivalent) shall be the same as the Tandem/End Office subtending arrangements (or functional equivalent) which AWS maintains for the routing of its own or other carriers’ traffic.
Sample 1Sample 2Sample 3
Switching System Hierarchy. 18 5.3 Trunk Group Architecture and Traffic Routing............. 19 5.4 Signaling................................................ 20 5.5
Sample 1
Switching System Hierarchy. 5.2.1 For purposes of this Section 5.0, each of the following Central Office Switches shall be designated as a "Primary Switch": (a) Each Access Tandem BA operates in the LATA; (b) The initial switch FOCAL employs to provide Telephone Exchange Service in the LATA; (c) Any Access Tandem FOCAL may establish for provision of Exchange Access in the LATA;
Sample 1
Switching System Hierarchy. 5.2.1 For purposes of this Section 5.0 each of the following Central Office Switches shall be designated as a "Primary Switch": (a) Each Access Tandem Ameritech operates in the LATA; (b) The initial switch Focal employs to provide Telephone Exchange Service in the LATA; (c) Any Access Tandem Focal may establish for provision of Exchange Access in the LATA; and (d) Any additional switch Focal may subsequently employ to provide Telephone Exchange Service in the LATA which Focal may at its sole option designate as a Primary Switch; provided that the total number of Focal Primary Switches for a LATA may not exceed the total number of Ameritech s Primary Switches for that LATA. To the extent Focal chooses to designate any additional switch as a Primary Switch, it shall provide notice to Ameritech of such designation at least ninety (90) days in advance of the date on which Focal activates such switch as a Primary Switch. 5.2.2 Each Central Office Switch operated by the Parties which is not designated as a Primary Switch pursuant to Section 5.2.1 shall be designated as a "Secondary Switch". 5.2.3 For purposes of Focal routing traffic to Ameritech, sub- tending arrangements between Ameritech Primary Switches and Ameritech Secondary Switches shall be the same as the Access Tandem/End Office subtending- arrangements which Ameritech maintains for those switches. For purposes of Ameritech routing traffic to Focal, subtending arrangements between Focal Primary Switches and Focal Secondary Switches shall be the same as the Access Tandem/End Office sub-tending arrangements which Focal maintains for those switches.
Sample 1
Switching System Hierarchy. 5.2.1 For purposes of this Section 5.0, each of the following Central Office Switches shall be designated as a "Primary Switch": (a) Each Access Tandem NYNEX operates in the LATA; (b) The initial switch XXXXXX FIBER employs to provide Telephone Exchange Service in the LATA; (c) Any Access Tandem XXXXXX FIBER may establish for provision of Exchange Access in the LATA; (d) Any additional switch XXXXXX FIBER may subsequently employ to provide Telephone Exchange Service in the LATA which XXXXXX FIBER may at its sole option designate as a Primary Switch; provided that the total number of XXXXXX FIBER Primary Switches for a LATA may not exceed the total number of NYNEX Primary Switches for that LATA. To the extent XXXXXX FIBER chooses to designate any additional switch as a Primary Switch, it shall provide notice to NYNEX of such designation at least ninety (90) days in advance of the date on which XXXXXX FIBER activates such switch as a Primary Switch; and (e) Any additional tandem switch NYNEX may subsequently employ to provide access and/or sector traffic capacity within a LATA. Traffic destined to sub-tending Secondary Switches routed via such a tandem(s) would be determined by network requirements and notice made available to all LECs at least one hundred-eighty (180) days prior to service introduction.
Sample 1
Switching System Hierarchy. Either Party may deploy End Office switches, Tandem switches, or combination End Office Tandem switches as required to meet their respective network design requirements.
Sample 1
AutoNDA by SimpleDocs

Related to Switching System Hierarchy

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Switching All of the negotiated rates, terms and conditions set forth in this Section pertain to the provision of local and tandem switching.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation 35.5.1. The charges that CLEC shall pay to Sprint for Collocation are set forth in Table Two of this Agreement. 35.6. Call Related Databases 6.1. The charges that CLEC shall pay to Sprint for Call Related Databases purchased pursuant to Part J are set forth in Table One of this Agreement.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Service Levels All service level requirements will be set forth in Exhibit A (“XXXX.xxx Referral Service Level Requirements”). Recipient Xxxxxx agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the XXXX.xxx Referral Service Level Requirements in effect at the time XXXX.xxx identifies the Referral to Recipient Broker/Agent.

  • Service Areas HHSC authorizes the MA Dual SNP to add the MA Product to Texas service areas that are not identified in Attachment C, Proposed MA Product Service Areas, provided it receives prior CMS approval and complies with the notice requirements specified in this Agreement.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!