Common use of ODUF Physical File Characteristics Clause in Contracts

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: 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. 6.2.2 Data circuits (private line or dial-up) will be required between AT&T and NuVox for the purpose of data transmission when utilizing CONNECT: Direct. Where a dedicated line is required, NuVox will be responsible for ordering the circuit, and coordinating the installation with AT&T. NuVox will also be responsible for any charges associated with this line. CSU/DSU equipment required on the AT&T end to attach the line to the mainframe computer and to transmit data will be the responsibility of NuVox. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to NuVox. Additionally, all message toll charges associated with the use of the dial circuit by NuVox will be the responsibility of NuVox. Associated equipment on the AT&T end, including a modem, will be the responsibility of AT&T. All equipment, including modems and software, that is required on NuVox end for the purpose of data transmission will be the responsibility of NuVox. 6.2.3 If NuVox utilizes CONNECT: Enterprise Client for data file transmission, purchase of the CONNECT: Enterprise Client software will be the responsibility of NuVox.

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: :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. 6.2.2 Data circuits (private line or dial-up) will be required between AT&T and NuVox for the purpose of data transmission when utilizing CONNECT: :Direct. Where a dedicated line is required, NuVox will be responsible for ordering the circuit, and coordinating the installation with AT&T. NuVox will also be responsible for any charges associated with this line. CSU/DSU equipment required on the AT&T end to attach the line to the mainframe computer and to transmit data will be the responsibility of NuVox. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to NuVox. Additionally, all message toll charges associated with the use of the dial circuit by NuVox will be the responsibility of NuVox. Associated equipment on the AT&T end, including a modem, will be the responsibility of AT&T. All equipment, including modems and software, that is required on NuVox end for the purpose of data transmission will be the responsibility of NuVox. 6.2.3 If NuVox utilizes CONNECT: :Enterprise Client for data file transmission, purchase of the CONNECT: :Enterprise Client software will be the responsibility of NuVox. Page 57 of 321 6.3 ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one (1) message record or a maximum of ninety- nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack. 6.3.2 The OCN, From XXX, and Invoice Number will control the invoice sequencing. The From XXX will be used to identify to NuVox which AT&T XXX that is sending the message. AT&T and NuVox will use the invoice sequencing to control data exchange. AT&T will be notified of sequence failures identified by NuVox and resend the data as quickly as technically possible. The data will be packed using ATIS EMI records.

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: :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. 6.2.2 Data circuits (private line or dial-up) will be required between AT&T and NuVox for the purpose of data transmission when utilizing CONNECT: :Direct. Where a dedicated line is required, NuVox will be responsible for ordering the circuit, and coordinating the installation with AT&T. NuVox will also be responsible for any charges associated with this line. CSU/DSU equipment required on the AT&T end to attach the line to the mainframe computer and to transmit data will be the responsibility of NuVox. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to NuVox. Additionally, all message toll charges associated with the use of the dial circuit by NuVox will be the responsibility of NuVox. Associated equipment on the AT&T end, including a modem, will be the responsibility of AT&T. All equipment, including modems and software, that is required on NuVox end for the purpose of data transmission will be the responsibility of NuVox. 6.2.3 If NuVox utilizes CONNECT: :Enterprise Client for data file transmission, purchase of the CONNECT: :Enterprise Client software will be the responsibility of NuVox.