Common use of Network Management Clause in Contracts

Network Management. 3.13.1 CLEC and SBC ILLINOIS shall work cooperatively to install and maintain a reliable network. CLEC and SBC ILLINOIS shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability. 3.13.2 CLEC and SBC ILLINOIS shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. Routing of the respective Networks should be based on the routing outlined within the LERG, when technically feasible. 3.13.3 CLEC and SBC ILLINOIS shall participate in a joint engineering review of Trunk Usage Report data every six (6) months to identify changes needed in the trunking that exists between CLEC Switch Centers and SBC ILLINOIS Tandem Switches with the objectives of, (1) minimizing blocking, (2) optimizing trunk utilization, (3) identifying low trunk utilization, (4) identifying modifications to the existing trunk network to improve trunking efficiency. 3.13.4 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 SBC ILLINOIS will immediately notify each other of any protective control action planned or executed. 3.13.5 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the Parties. 3.13.6 CLEC and SBC ILLINOIS shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes. 3.13.7 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-hour contact number for Network Traffic Management issues to the other's surveillance management center.

Network Management. 3.13.1 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall work cooperatively to install and maintain a reliable network. CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability. 3.13.2 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. Routing of the respective Networks should be based on the routing outlined within the LERG, when technically feasible. 3.13.3 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall participate in a joint engineering review of Trunk Usage Report data every six (6) months to identify changes needed in the trunking that exists between CLEC AT&T Switch Centers and SBC ILLINOIS SBC-AMERITECH Tandem Switches with the objectives of, (1) minimizing blocking, (2) optimizing balancing trunk utilization, (3) identifying low trunk utilization, (4) identifying modifications to the existing trunk network to improve trunking efficiency. 3.13.4 Either Party may use protective network traffic management controls such as 7- 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 AT&T and SBC ILLINOIS SBC-AMERITECH will immediately notify each other of any protective control action planned or executed. 3.13.5 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the Parties. 3.13.6 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes. 3.13.7 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-hour contact number for Network Traffic Management issues to the other's surveillance management center.

Network Management. 3.13.1 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall work cooperatively to install and maintain a reliable network. CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability. 3.13.2 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. Routing of the respective Networks should be based on the routing outlined within the LERG, when technically feasible. 3.13.3 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall participate in a joint engineering review of Trunk Usage Report data every six (6) months to identify changes needed in the trunking that exists between CLEC AT&T Switch Centers and SBC ILLINOIS SBC-AMERITECH Tandem Switches with the objectives of, : (1) minimizing blocking, (2) optimizing balancing trunk utilization, (3) identifying low trunk utilization, (4) identifying modifications to the existing trunk network to improve trunking efficiency. 3.13.4 Either Party may use protective network traffic management controls such as 7- 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 AT&T and SBC ILLINOIS SBC-AMERITECH will immediately notify each other of any protective control action planned or executed. 3.13.5 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the Parties. 3.13.6 CLEC AT&T and SBC ILLINOIS SBC-AMERITECH shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes. 3.13.7 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-hour contact number for Network Traffic Management issues to the other's surveillance management center.

Network Management. 3.13.1 CLEC 3.1 Each Party to this Appendix will be responsible for the accuracy and SBC ILLINOIS shall quality of its data as submitted to the respective Parties involved. Where SS7 connections exist, each Party will include the Calling Party Number (CPN) that truly and accurately reflect the location of the end user that originated and/or dialed the call in the information transmitted to the other for each call being terminated on the other’s network. If one Party is passing CPN but the other Party is not properly receiving CPN, the Parties will work cooperatively to install correct the problem. Where SS7 connections exist and maintain a reliable networkthe percentage of calls passed with CPN is greater than ninety percent (90%), all calls without CPN exchanged between the Parties will be billed as either Section 251(b)(5) Traffic, ISP-Bound Traffic, FX Traffic, Optional EAS Traffic, or intraLATA Toll Traffic in direct proportion to the minutes of use (MOU) of calls exchanged with CPN. CLEC and SBC ILLINOIS shall If the percentage of calls passed with CPN is less than ninety percent (90%), all calls passed without CPN will be billed as intraLATA switched access. 3.2 The Parties will work cooperatively to implement this Appendix. The Parties will exchange appropriate information (e.g.for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agreeGovernment, escalation processes, etc.) to achieve this desired reliabilityresult. 3.13.2 CLEC and SBC ILLINOIS shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. Routing of the respective Networks should be based on the routing outlined within the LERG, when technically feasible. 3.13.3 CLEC and SBC ILLINOIS shall participate in a joint engineering review of Trunk Usage Report data every six (6) months to identify changes needed in the trunking that exists between CLEC Switch Centers and SBC ILLINOIS Tandem Switches with the objectives of, (1) minimizing blocking, (2) optimizing trunk utilization, (3) identifying low trunk utilization, (4) identifying modifications to the existing trunk network to improve trunking efficiency. 3.13.4 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 SBC ILLINOIS will immediately notify each other of any protective control action planned or executed. 3.13.5 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the Parties. 3.13.6 CLEC and SBC ILLINOIS shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes. 3.13.7 3.3 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-24- hour contact number for Network Traffic Management network traffic management issues to the other's surveillance management center. 3.4 Each Party maintains the right to implement protective network traffic management controls, such as "cancel to", "call gapping" or 7-digit and 10-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 3.5 Where the capability exists, either Party may implement originating or terminating traffic reroutes to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties 3.6 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 3.7 The Parties agree that, unless otherwise mutually negotiated, the quality of such network connections shall be equal to that of the existing facilities that are jointly provided by each Party. 3.8 Joint planning and forecasting responsibilities shall be governed by the underlying agreement.

Network Management. 3.13.1 CLEC and SBC ILLINOIS shall work cooperatively to install and maintain a reliable network. CLEC and SBC ILLINOIS shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability. 3.13.2 CLEC and SBC ILLINOIS shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. Routing of the respective Networks should be based on the routing outlined within the LERG, when technically feasible. 3.13.3 CLEC and SBC ILLINOIS shall participate in a joint engineering review of Trunk Usage Report data every six (6) months to identify changes needed in the trunking that exists between CLEC Switch Centers and SBC ILLINOIS Tandem Switches with the objectives of, (1) minimizing blocking, (2) optimizing trunk utilization, (3) identifying low trunk utilization, (4) identifying modifications to the existing trunk network to improve trunking efficiency. 3.13.4 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 SBC ILLINOIS will immediately notify each other of any protective control action planned or executed. 3.13.5 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the Parties. 3.13.6 CLEC and SBC ILLINOIS shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes. 3.13.7 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-hour contact number for Network Traffic Management issues to the other's surveillance management center. 11-13-03 3.14.1 911 Arrangements are arrangements for routing 911 calls from CLEC Customers to the appropriate Public Safety Answering Point (“PSAP”), passing certain customer information for display at the PSAP answering station based on the class of 911 service (Basic 911 or E911) deployed in the area. SBC ILLINOIS shall provide 911 Arrangements to CLEC as described in this Section 3.14 in each exchange in which: (i) CLEC is authorized to provide local exchange services, and (ii) SBC ILLINOIS is the 911 service provider. The provisions in this Section 3.14 apply only to 911 Arrangements provided as Ancillary Functions. 911 functionality for Unbundled Network Element Combinations and for Local Service Resale shall be governed by provisions in Article 9 (Access to Unbundled Network Elements) and Article 10 (Resale at Wholesale Rates) of this Agreement. In providing 911 Arrangements to CLEC, SBC ILLINOIS shall comply with all laws, rules and regulations concerning emergency services.

Network Management. 3.13.1 CLEC and SBC ILLINOIS AT&T 4-STATE shall work cooperatively to install and maintain a reliable network. CLEC and SBC ILLINOIS AT&T 4-STATE shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability. 3.13.2 CLEC and SBC ILLINOIS AT&T 4-STATE shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. Routing of the respective Networks should be based on the routing outlined within the LERG, when technically feasible. 3.13.3 CLEC and SBC ILLINOIS AT&T 4-STATE shall participate in a joint engineering review of Trunk Usage Report data every six (6) months to identify changes needed in the trunking that exists between CLEC Switch Centers and SBC ILLINOIS AT&T 4-STATE Tandem Switches with the objectives of, (1) minimizing blocking, (2) optimizing trunk utilization, (3) identifying low trunk utilization, (4) identifying modifications to the existing trunk network to improve trunking efficiency. 3.13.4 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 SBC ILLINOIS AT&T 4-STATE will immediately notify each other of any protective control action planned or executed. 3.13.5 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the Parties. 3.13.6 CLEC and SBC ILLINOIS AT&T 4-STATE shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes. 3.13.7 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a 24-hour contact number for Network Traffic Management issues to the other's surveillance management center.