EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Image Access via FTP. The EODUF messages will be intermingled among Image Access’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to OneTone via FTP. The EODUF messages will be intermingled among OneTone’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among Vertex’s Optional Daily Usage File (ODUF) messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Universal Telecom, Inc via FTP. The EODUF messages will be intermingled among Universal Telecom, Inc’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If AT&T determines the Secure FTP mailbox is nearing capacity levels, AT&Tmay move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Talk for Less via FTP. The EODUF messages will be intermingled among Talk for Less’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If AT&T determines the Secure FTP mailbox is nearing capacity levels, AT&T may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to <<customer_short_name>> via FTP. The EODUF messages will be intermingled among <<customer_short_name>>’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If AT&T determines the Secure FTP mailbox is nearing capacity levels, AT&T may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Credit Loans via FTP. The EODUF messages will be intermingled among Credit Loans’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to France Telecom via FTP. The EODUF messages will be intermingled among France Telecom’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Ohio County Networks via FTP. The EODUF messages will be intermingled among Ohio County Networks’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If BellSouth determines the Secure FTP mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Snap Telecommunications via FTP. The EODUFmessages will be intermingled among Snap Telecommunications’s ODUF messages. The EODUF will be a variable block format. The data on the EODUF 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 holiday. If AT&T determines the Secure FTPmailbox is nearing capacity levels, AT&T maymove the customer to CONNECT:Direct file delivery.
