Common use of Network Architecture Clause in Contracts

Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 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. 2.3 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. 2.4 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 shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties. 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. 2.5 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.

Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 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. 2.3 Each Party maintains the right to implement protective network traffic management controls, such as "cancel to", "call gapping" or 7-digit and 10- 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-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. 2.4 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 shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties. . 2.5 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. 2.5 2.6 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. 2.7 Within thirty (30) days from the Effective Date of this Agreement, the Parties agree to have met and developed joint planning and forecasting responsibilities which are applicable to services described in this Agreement. Either Party may delay processing the other Party’s service orders should the Parties not perform obligations as specified in this Section. Such responsibilities shall include but are not limited to the following: 2.7.1 The Parties will establish periodic reviews of network and technology plans and will notify one another no later than six (6) months in advance of changes that would impact either Party's provision of services. 2.7.2 The Parties will furnish to each other, information that provides for state-wide annual forecasts of order activity, in-service quantity forecasts, and facility/demand forecasts. 2.7.3 The Parties will develop joint forecasting responsibilities for traffic utilization over trunk groups and yearly forecasted trunk quantities. 2.7.4 The Parties shall notify each other promptly of changes greater than ten percent (10%) to current forecasts (increase or decrease) that generate a shift in the demand curve for the following forecasting period. 2.8 The Parties agree that if either Party establishes additional tandems in an exchange, the other Party may also connect to the additional tandems, and must re-home traffic upon industry notification if either Party establishes a tandem to relieve the first tandem of call congestion.

Network Architecture. 2.1 3.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 3.2 All traffic will be exchanged between the Parties in Time Division Multiplexing (TDM) format unless otherwise mutually agreed upon by the Parties. 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-hour contact number for network traffic management issues to the other's surveillance management center. 2.3 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- 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. 2.4 3.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 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-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. 2.5 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 AT&T-21STATE’s network is partly comprised of End Office Switches, Local Only Tandem Switches (AT&T-10STATE), Local/IntraLATA Tandem Switches, Local/Access Tandem Switches and Access Tandem Switches. AT&T-21STATE’s network architecture in any given local Exchange Area and/or LATA can vary markedly from another local Exchange Area/LATA. The Parties will agree to a physical architecture plan for a specific Interconnection area. A physical architecture plan will, at a minimum, include the location of CARRIER’s switch(es) and AT&T-21STATE’s End Office Switch(es) and/or Tandem Switch(es) to be interconnected, the facilities that will connect the two (2) networks and which Party will provide (be financially responsible for) the Interconnection facilities. 3.9 Either Party may install a soft switch in its territory to deliver services to its requesting customers. 3.10 If the existing digital switch and the new soft switch will be operational at the same time, the new soft switch common language locator identification (“CLLI”) code will have the same first eight characters as the existing digital switch. 3.11 The soft switch will have individually assigned Location Routing Number (LRN) code and will be contained in LERG. 3.12 If the existing digital switch and the new soft switch will be operational at the same time, the Parties agree that no new V&H coordinates for the soft switch will be established, and the V&H coordinates of the soft switch Host and Remote pseudo CLLI codes will be the same as those of the existing Parties digital switch. The actual V&H coordinates for the gateway may or may not be the same coordinates as the host pseudo CLLI code. Both Parties agree that such V&H assignment method will not require any new or modification to existing billing percentages (BPs) used for compensation as described in this Agreement, unless otherwise agreed to in writing by both Parties. 3.13 When the soft switch is in another LATA, Party will assign pseudo CLLI codes by using the existing first 8 characters of the exchange for the established meet point in the LATA. The soft switch gateway may or may not be in the same LATA as the pseudo host and/or remote CLLI being established. 3.14 A pseudo CLLI will have the same V&H coordinates as the existing digital switch. 3.15 The Parties agree that they will not create a pseudo host/remote arrangement whereby neither the host nor remote is in the LATA in which the Party directly or indirectly interconnects with the other Party.

Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 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 24 -hour contact number for network traffic management issues to the other's surveillance management center. 2.3 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. 2.4 Where the capability exists, originating or terminating te rminating traffic reroutes may be implemented by either Party 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. 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 impa ct 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. 2.5 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.

Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 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 issues to the other's surveillance management center. 2.3 Each Party maintains the right to implement protective network traffic management controls, such as "cancel to", "call gapping" or 7-digit and 10- 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-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. 2.4 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 shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties. The Parties shall cooperate and share pre-pre- planning information regarding cross-network call-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. 2.5 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.

Network Architecture. 2.1 3.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 3.2 All traffic will be exchanged between the Parties in Time Division Multiplexing (TDM) format unless otherwise mutually agreed upon by the Parties. 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-hour contact number for network traffic management issues to the other's surveillance management center. 2.3 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- 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. 2.4 3.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 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-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. 2.5 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 Each Party has a network that is partly comprised of End Office Switches, Local Only Tandem Switches (AT&T- 10STATE only), Local/IntraLATA Tandem Switches, Local/Access Tandem Switches and Access Tandem Switches. Each Party’s network architecture in any given local Exchange Area and/or LATA can vary markedly from another local Exchange Area/LATA. The Parties will agree to a physical architecture plan for a specific Interconnection area. A physical architecture plan will, at a minimum, include those necessary details for the Parties to interconnect and which Party will provide (be financially responsible for the Interconnection facilities. 3.9 Either Party may install a soft switch in its territory to deliver services to its requesting customers. 3.10 If the existing digital switch and the new soft switch will be operational at the same time, the new soft switch common language locator identification (“CLLI”) code will have the same first eight characters as the existing digital switch. 3.11 The soft switch will have individually assigned Location Routing Number (LRN) code and will be contained in LERG. 3.12 If the existing digital switch and the new soft switch will be operational at the same time, the Parties agree that no new V&H coordinates for the soft switch will be established, and the V&H coordinates of the soft switch Host and Remote pseudo CLLI codes will be the same as those of the existing digital switch. The actual V&H coordinates for the gateway may or may not be the same coordinates as the host pseudo CLLI code. Both parties agree that such V&H assignment method will not require any new or modification to existing billing percentages (BPs) used for compensation as described in this Agreement. 3.13 When the soft switch is in another LATA, a Party will assign pseudo CLLI codes by using the existing first 8 characters of the exchange for the established meet point in the LATA. The soft switch gateway may or may not be in the same LATA as the pseudo host and/or remote CLLI being established. 3.14 A pseudo CLLI will have the same V&H coordinates as the existing digital switch. 3.15 The Parties agree that they will not create a pseudo host/remote arrangement whereby neither the host nor remote is in the LATA in which the Party directly or indirectly interconnects with the other Party.

Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 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 the other Party with a 24-hour contact number for network traffic management issues to the other's surveillance management centerissues. 2.3 Each Party maintains the right to implement protective network traffic management controls, such as "cancel to", "call gapping" or 7-digit and 10- 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. 2.4 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 shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties. Each Party shall notify the other Party of any originating or terminating traffic reroutes within a reasonable period of time. 2.5 The Parties shall cooperate and share pre-planning information regarding cross-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. 2.5 2.6 Neither Party shall use any Interconnection, Resale Service, Network Element, function, facility, product or service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of the other Party, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier's facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 2.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 PartyAMERITECH WISCONSIN and MH Telecom.

Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result. 2.2 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. 2.3 Each Party maintains the right to implement protective network traffic management controls, such as "cancel to", "call gapping" or 7-digit and 10- 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-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. 2.4 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 shall not be used to circumvent normal trunk servicing. Such alternative routing shall be used only when mutually agreed to by the Parties. 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. 2.5 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.