Common use of ODUF Packing Specifications Clause in Contracts

ODUF Packing Specifications. 12.7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof one (1) message record or a maximumof 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 maximumof ninety-nine (99) packs and a minimumof one (1) pack. 12.7.3.2 The OCN, XxxxXXX, and InvoiceNumber will control the invoicesequencing. TheFromRAOwill be used to identify to CUSTOMERwhich AT&T XXX is sending the message. AT&T and CUSTOMERwill use the invoicesequencing to control data exchange. CUSTOMERwill notify AT&T of sequence failures identified by CUSTOMER and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: MBR Agreement

AutoNDA by SimpleDocs

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof minimum of one (1) message record or a maximumof ninety- 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 maximumof maximum of ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFrom XXX, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The From XXX will be used to identify to CUSTOMERwhich Covad which AT&T XXX is sending the message. AT&T and CUSTOMERwill Covad will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER Covad and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: MFN Agreement

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof aminimum of one (1) message record or a maximumof ninety- 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 maximumof ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFromRAO, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The FromRAOwill be used to identify to CUSTOMERwhich AIN/Birch which AT&T XXX is sending the message. AT&T and CUSTOMERwill AIN/Xxxxx will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER AIN/Birch and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Interconnection Adoption Agreement

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof minimum of one (1) message record or a maximumof ninety- 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 maximumof maximum of ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFrom XXX, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The From XXX will be used to identify to CUSTOMERwhich Serenity which AT&T XXX is sending the message. AT&T and CUSTOMERwill Serenity will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER Serenity and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Resale Agreement

ODUF Packing Specifications. 12.7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof minimum of one (1) message record or a maximumof 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 maximumof maximum of ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 The OCN, XxxxXXXFrom XXX, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The From XXX will be used to identify to CUSTOMERwhich CUSTOMER which AT&T XXX is sending the message. AT&T and CUSTOMERwill CUSTOMER will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill CUSTOMER will notify AT&T of sequence failures identified by CUSTOMER and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Clec Agreement

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof minimum of one (1) message record or a maximumof ninety- 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 maximumof maximum of ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFrom XXX, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The From XXX will be used to identify to CUSTOMERwhich CLEC which AT&T XXX is sending the message. AT&T and CUSTOMERwill CLEC will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER CLEC and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Interconnection Agreement

AutoNDA by SimpleDocs

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof minimum of one (1) message record or a maximumof ninety- 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 maximumof maximum of ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFrom XXX, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The From XXX will be used to identify to CUSTOMERwhich Talk for Less which AT&T XXX is sending the message. AT&T and CUSTOMERwill Talk for Less will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER Talk for Less and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Resale Agreement

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof aminimum of one (1) message record or a maximumof ninety- 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 maximumof ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFromRAO, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The FromRAOwill be used to identify to CUSTOMERwhich Communication Lines which AT&T XXX is sending the message. AT&T and CUSTOMERwill Communication Lines will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER Communication Lines and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Resale Agreement

ODUF Packing Specifications. 12.7.3.1 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimumof minimum of one (1) message record or a maximumof ninety- 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 maximumof maximum of ninety-nine (99) packs and a minimumof minimum of one (1) pack. 12.7.3.2 6.3.2 The OCN, XxxxXXXFrom XXX, and InvoiceNumber Invoice Number will control the invoicesequencinginvoice sequencing. TheFromRAOwill The From XXX will be used to identify to CUSTOMERwhich <<customer_short_name>> which AT&T XXX is sending the message. AT&T and CUSTOMERwill <<customer_short_name>> will use the invoicesequencing invoice sequencing to control data exchange. CUSTOMERwill notify AT&T will be notified of sequence failures identified by CUSTOMER <<customer_short_name>> and AT&T will resend the data as appropriate.

Appears in 1 contract

Samples: Interconnection Adoption Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!