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.
Appears in 2 contracts
Samples: General Terms and Conditions, General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 6.2.1 EODUF feed will be distributed to Vertex Aspire via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexAspire’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.
Appears in 2 contracts
Samples: General Terms and Conditions, General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 6.2.1 EODUF feed will be distributed to Vertex Express Connection via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexExpress Connection’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.
Appears in 1 contract
Samples: General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex Dialogica via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexDialogica’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.
Appears in 1 contract
Samples: General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex AIN/Birch via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexAIN/Birch’s Optional Daily Usage File (ODUF) ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (175 one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth AT&T determines the Secure FTP mailbox FTPmailbox is nearing capacity levels, BellSouth may AT&Tmay move the customer to CONNECT:Direct file delivery.
Appears in 1 contract
Samples: MFN Agreement
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex Talk for Less via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexTalk for Less’s Optional Daily Usage File (ODUF) ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (175 one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holiday. If BellSouth AT&T determines the Secure FTP mailbox is nearing capacity levels, BellSouth AT&T may move the customer to CONNECT:Direct file delivery.
Appears in 1 contract
Samples: psc.ky.gov
EODUF Physical File Characteristics. 7.2.1 6.2.1 EODUF feed will be distributed to Vertex Xxxxxxxx via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among Vertex’s Xxxxxxxx’x 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.
Appears in 1 contract
Samples: General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex Xxxxx via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among Vertex’s Xxxxx’x 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.
Appears in 1 contract
Samples: General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex Rent-A-Line via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexRent-A-Line’s Optional Daily Usage File (ODUF) ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (175 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.
Appears in 1 contract
Samples: General Terms and Conditions
EODUF Physical File Characteristics. 7.2.1 EODUF feed will be distributed to Vertex Xxxxxxxx Communications via Secure File Transfer Protocol (FTP). The EODUF messages will be intermingled among VertexXxxxxxxx Communications’s Optional Daily Usage File (ODUF) ODUF messages. The EODUF will be a variable block format. The data on the EODUF will be in a non-compacted EMI format (175 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.
Appears in 1 contract
Samples: General Terms and Conditions