Common use of ODUF Pack Rejection Clause in Contracts

ODUF Pack Rejection. 6.4.1 Covad will notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Covad will not be required to return the actual rejected data to AT&T. Rejected packs will be corrected and retransmitted to Covad by AT&T.

ODUF Pack Rejection. 6.4.1 Covad will AIN/Birchwill notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard populated).Standard ATIS EMI error codes will be errorcodes willbe used. Covad AIN/Birch will not be required to return the actual rejected data to AT&T. Rejected packs will be corrected and retransmitted to Covad AIN/Birch by AT&T.

ODUF Pack Rejection. 6.4.1 Covad Communication Lines will notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard Standadr ATIS EMI error codes will be used. Covad Communication Lines will not be required to return the actual rejected data to AT&T. Rejected packs will be corrected and retransmitted to Covad Communication Lines by AT&T.

ODUF Pack Rejection. 6.4.1 Covad will CUSTOMERwill notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-of- balance condition on grand totals, ,invalid data populateddatapopulated). Standard ATIS EMI ATISEMI error codes will be used. Covad will not be CUSTOMERwill notbe required to return the actual rejected data to AT&T. Rejected packs will be corrected and correctedand retransmitted to Covad CUSTOMER by AT&T.

ODUF Pack Rejection. 6.4.1 Covad Premier will notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard Satndard ATIS EMI error codes will codewsill be used. Covad Premier will not be required to return the actual rejected data to AT&T. Rejected packs will be corrected packilsl bwe correcet d and retransmitted to Covad Premier by AT&T.

ODUF Pack Rejection. 6.4.1 Covad CUSTOMER will notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Covad CUSTOMER will not be required to return the actual rejected data to AT&T. Rejected packs will be corrected and retransmitted to Covad CUSTOMER by AT&T.

ODUF Pack Rejection. 6.4.1 Covad Serenity will notify AT&T within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Covad Serenity will not be required to return the actual rejected data to AT&T. Rejected packs will be corrected and retransmitted to Covad Serenity by AT&T.