Common use of ODUF Physical File Characteristics Clause in Contracts

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 ConnectNow! via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 BudgeTel via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 EveryCall via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 My-Tel via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The 7.2.1 ODUF will be distributed to CI2 FPB via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 NuStar via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 CityNet via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 QuantumShift via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Premier via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 NGTelecom via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Telstar Prepaid via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 VarTec via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Newcomm via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 International Telnet via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-non- compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Conextel via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Gateway via CONNECT:Direct or Secure File Transfer Protocol (FTP) Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 JCM via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 MidState Telecommunications via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Solution Telecom via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-non- compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Globe via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 The Phone Connection via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-non- compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Telephone One via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Dialtone & More via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-non- compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 C A Networks via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Paramount via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Big River via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 TelSouth via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 C & M Total Communications via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 DSL via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Knology via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 MYLINETOO via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 CM Tel via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Connect Paging via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Home Phone via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 MCI via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 MC3 Telecom via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 AllSouth Phone via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 EZ Phone via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 DPI via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Smart-Tel via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Ring Connection via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-non- compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Andrex via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Think 12 via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 Buy-Tel via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to CI2 BSE via CONNECT:Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.