ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). 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. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery.
6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. 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 TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC.
6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to VMT via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (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
(1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth and VMT for the purpose of data transmission. Where a dedicated line is required, VMT will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. VMT will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be VMT’s responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to VMT. Additionally, all message toll charges associated with the use of the dial circuit by VMT will be the responsibility of VMT. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on VMT’s end for the purpose of data transmission will be the responsibility of VMT.
6.2.3 If VMT utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of VMT.
ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to 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.
6.2.2 Data circuits (private line or dial-up) will be required between BellSouth and Smart- Tel for the purpose of data transmission when utilizing CONNECT:Direct. Where a dedicated line is required, Smart-Tel will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Smart-Tel will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit data will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Smart-Tel. Additionally, all message toll charges associated with the use of the dial circuit by Smart-Tel will be the responsibility of Smart-Tel. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Smart-Tel end for the purpose of data transmission will be the responsibility of Smart-Tel.
6.2.3 If Smart-Tel utilizes Secure File Transfer Protocol (FTP) for data file transmission, purchase of the Secure File Transfer Protocol (FTP) software will be the responsibility of Smart-Tel.
ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to Quality Telephone 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.
6.2.2 Data circuits (private line or dial-up) will be required between BellSouth and Quality Telephone for the purpose of data transmission when utilizing CONNECT:Direct. Where a dedicated line is required, Quality Telephone will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Quality Telephone will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit data will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Quality Telephone. Additionally, all message toll charges associated with the use of the dial circuit by Quality Telephone will be the responsibility of Quality Telephone. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Quality Telephone end for the purpose of data transmission will be the responsibility of Quality Telephone.
6.2.3 If Quality Telephone utilizes Secure File Transfer Protocol (FTP) for data file transmission, purchase of the Secure File Transfer Protocol (FTP) software will be the responsibility of Quality Telephone.
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to Vertex via Secure File Transfer Protocol (FTP). 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. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth and Vertex for the purpose of data transmission. Where a dedicated line is required, Vertex will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Vertex will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be Vertex's responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Vertex. Additionally, all message toll charges associated with the use of the dial circuit by Vertex will be the responsibility of Vertex. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Vertex end for the purpose of data transmission will be the responsibility of Vertex.
6.2.3 If Vertex utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of Vertex.
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 Freedom via Secure File Transfer Protocol (FTP). 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. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth and Freedom for the purpose of data transmission. Where a dedicated line is required, Freedom will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Freedom will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be Freedom's responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Freedom. Additionally, all message toll charges associated with the use of the dial circuit by Freedom will be the responsibility of Freedom. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Freedom end for the purpose of data transmission will be the responsibility of Freedom.
6.2.3 If Freedom utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of Freedom.
ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to Ciera Network Systems, Inc. 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 BellSouth and Ciera Network Systems, Inc. for the purpose of data transmission when utilizing CONNECT:Direct. Where a dedicated line is required, Ciera Network Systems, Inc. will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. Ciera Network Systems, Inc. will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit data will be negotiated on an individual case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to Ciera Network Systems, Inc.. Additionally, all message toll charges associated with the use of the dial circuit by Ciera Network Systems, Inc. will be the responsibility of Ciera Network Systems, Inc.. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Ciera Network Systems, Inc. end for the purpose of data transmission will be the responsibility of Ciera Network Systems, Inc..
6.2.3 If Ciera Network Systems, Inc. utilizes CONNECT:Enterprise Client for data file transmission, purchase of the CONNECT:Enterprise Client software will be the responsibility of Ciera Network Systems, Inc..
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to Universal Telecom, Inc via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (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 willbe addressed during negotiations of thesdtiributionmedium.There will be a maximum of one (1) dataset per workday per OCN. If AT&T determines the Secure FTPMailbox is nearing capacity levels, AT&T maymove the customer to CONNECT:Direct file delivery.
6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between AT&T and Universal Telecom, Inc for the purpose of data transmission. Where a dedicated line is required, Universal Telecom, Inc will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. Universal Telecom, Inc will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be Universal TelecomIn, c’s responsibility. Where adial-up facilityis required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to Universal Telecom, Inc. Additionally, all message toll charges associated with the use of the dial circuit by Universal Telecom, Inc will be the rpeosnsibility of Universal Telceom, Inc. Associated equipment on the AT&T end, including amodem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on Universal Telecom, Inc’s end for the purpose of data tramnsission will be the repsonsibility of Universal Telecom, Inc.
6.2.3 If Universal Telecom, Inc utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of Universal Telecom, Inc.
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to <customer_short_name> via Secure File Transfer Protocol (FTP). 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. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
6.2.2 If the customer is moved, CONNECT:Direct data circuits (private line or dial-up) will be required between BellSouth and <customer_short_name> for the purpose of data transmission. Where a dedicated line is required, <customer_short_name> will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. <customer_short_name> will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be <customer_short_name>'s responsibility. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to <customer_short_name>. Additionally, all message toll charges associated with the use of the dial circuit by <customer_short_name> will be the responsibility of <customer_short_name>. Associated equipment on the BellSouth end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on <customer_short_name> end for the purpose of data transmission will be the responsibility of <customer_short_name>.
6.2.3 If <customer_short_name> utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of <customer_short_name>.
