T1 IDENTIFICATION PROCEDURES Sample Clauses

T1 IDENTIFICATION PROCEDURES. During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.
AutoNDA by SimpleDocs
T1 IDENTIFICATION PROCEDURES. During the restoration of service after a disaster, AT&T may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, AT&T may be forced to "package" this traffic entirely differently than normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.
T1 IDENTIFICATION PROCEDURES. During the restoration of service after adisaster, AT&Tmay be forced to aggregate traffic for delivery to a CLEC. During this process, T1 trafficmay be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resourcews ill be limited, AT&Tmay be forced to "package" this traffic entirely differently than normally received by the CLECs. Therefore, amethod for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.
T1 IDENTIFICATION PROCEDURES. During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required. 7.0 ACRONYMS CO - Central Office (BellSouth) DS3 - Facility that carries 28 T1s (672 circuits) ECC - Emergency Control Center (BellSouth) CLEC - Competitive Local Exchange Carrier NMC - Network Management Center SWC - Serving Wire Center (BellSouth switch) T1 - Facility that carries 24 circuits Hurricane Information --------------------- During a hurricane, BellSouth will make every effort to keep CLECs updated on the status of our network. Information centers will be set up throughout BellSouth Telecommunications. These centers are not intended to be used for escalations, but rather to keep the CLEC informed of network related issues, area damages and dispatch conditions, etc. Hurricane-related information can also be found on line at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/network/disaster/dis_resp.htm. ---------------------------------------------------------------------- Information concerning Mechanized Disaster Reports can also be found at this website by clicking on CURRENT MDR REPORTS or by going directly to xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/network/disaster/mdrs.htm. ------------------------------------------------------------------ BST Disaster Management Plan

Related to T1 IDENTIFICATION PROCEDURES

  • No Reliance on Administrative Agent’s Customer Identification Program Each Lender acknowledges and agrees that neither such Lender, nor any of its Affiliates, participants or assignees, may rely on the Administrative Agent to carry out such Lender’s, Affiliate’s, participant’s or assignee’s customer identification program, or other obligations required or imposed under or pursuant to the USA Patriot Act or the regulations thereunder, including the regulations contained in 31 CFR 103.121 (as hereafter amended or replaced, the “CIP Regulations”), or any other Anti-Terrorism Law, including any programs involving any of the following items relating to or in connection with any of the Loan Parties, their Affiliates or their agents, the Loan Documents or the transactions hereunder or contemplated hereby: (i) any identity verification procedures, (ii) any recordkeeping, (iii) comparisons with government lists, (iv) customer notices or (v) other procedures required under the CIP Regulations or such other Laws.

  • Notification Procedures To address non-compliance, the receiving Competent Authority would notify the providing Competent Authority pursuant to Article 5 of the IGA. The notification procedures would differ depending upon whether the receiving Competent Authority seeks to address administrative or other minor errors or significant non-compliance.

Time is Money Join Law Insider Premium to draft better contracts faster.