Restrictive Controls Sample Clauses

Restrictive Controls. Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps set at appropriate levels on traffic toward each other's network, when required, to protect the public switched network from congestion due to facility failures, switch congestion, or failure or focused overload. CLEC and CenturyLink will immediately notify each other of any protective control action planned or executed.
View SourceView Similar (122)
Restrictive Controls. 3.12.1.1 Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps set at appropriate levels on traffic toward each other's network, when required, to protect the public switched network from congestion due to facility failures, switch congestion, or failure or focused overload. Charter and CenturyTel will immediately notify each other of any protective control action planned or executed.
View SourceView Similar (26)
Restrictive Controls. 10.1.1 Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps set at appropriate levels on traffic toward each other's network, when required, to protect the public switched network from congestion due to facility failures, switch congestion, or failure or focused overload. TCAL and TDS TELECOM will immediately notify each other of any protective control action planned or executed.
View SourceView Similar (16)
Restrictive Controls. Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps set at appropriate levels on traffic toward each other's network, when required, to protect the public switched network from congestion due to facility failures, switch congestion, or failure or focused overload. Pac-West and PACIFIC will immediately notify each other of any protective control action planned or executed.
View Source
Restrictive Controls. 6 --------------------- 12.2 Expansive Controls .............................................6 ---------- 12.3 Mass Calling ...................................................6 ----- APPENDIX ITR (TRUNKING REQUIREMENTS) This Appendix provides descriptions of the trunking requirements for CLEC and NEVADA interconnection. The attached scenarios depict the recommended trunk groups for local, intraLATA toll, interLATA "meet point" and mass calling, E911 and Operator Services Interconnection. All references to incoming and outgoing trunk groups are from the perspective of CLEC.
View Source

Related to Restrictive Controls

  • Personal Controls a. Employee Training. All workforce members who assist in the performance of functions or activities on behalf of COUNTY in connection with Agreement, or access or disclose PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, must complete information privacy and security training, at least annually, at CONTRACTOR’s expense. Each workforce member who receives information privacy and security training must sign a certification, indicating the member’s name and the date on which the training was completed. These certifications must be retained for a period of six (6) years following the termination of Agreement.

  • Administrative Controls The Contractor must have the following controls in place: a. A documented security policy governing the secure use of its computer network and systems, and which defines sanctions that may be applied to Contractor staff for violating that policy. b. If the Data shared under this agreement is classified as Category 4, the Contractor must be aware of and compliant with the applicable legal or regulatory requirements for that Category 4 Data. c. If Confidential Information shared under this agreement is classified as Category 4, the Contractor must have a documented risk assessment for the system(s) housing the Category 4 Data.

  • Agreement Controls The terms and conditions of this Master Agreement control over the terms and conditions contained in an Approved Service Order – even if the Approved Service Order expressly states that it is intended to control. Any conflicting terms and conditions in an Approved Service Order are invalid and unenforceable.