The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate.
Appears in 4 contracts
Sources: Resale Agreement, Resale Agreement, Resale Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Your Communication Connection which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Your Communication Connection will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Your Communication Connection and resend the data as appropriate.
Appears in 2 contracts
Sources: Clec Agreement, Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Max-Tel which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Max-Tel will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Max-Tel and resend the data as appropriate.
Appears in 2 contracts
Sources: Clec Agreement, Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> ▇▇▇▇▇-4-U which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> ▇▇▇▇▇-4-U will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> ▇▇▇▇▇-4-U and resend the data as appropriate.
Appears in 2 contracts
Sources: Resale Agreement, Resale Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Xspedius which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> Xspedius will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> ▇▇▇▇▇▇▇▇ and resend the data as appropriate.
Appears in 2 contracts
Sources: Clec Agreement, Interconnection Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Intermedia which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> Intermedia will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Intermedia and resend the data as appropriate.
Appears in 1 contract
Sources: Bellsouth® / Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Source One Communications which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Source One Communications will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Source One Communications and resend the data as appropriate.
Appears in 1 contract
Sources: Resale Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>customer_short_name> which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>customer_short_name> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>customer_short_name> and resend the data as appropriate. The data will be packed using ATIS EMI records.
Appears in 1 contract
Sources: Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Pinnacle which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> Pinnacle will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Pinnacle and resend the data as appropriate.
Appears in 1 contract
Sources: Interconnection Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> e.spire which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> e.spire will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> e.spire and resend the data as appropriate.
Appears in 1 contract
Sources: Bellsouth® / Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Annox which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Annox will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Annox and resend the data as appropriate.
Appears in 1 contract
Sources: Resale Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Source One Communications which BellSouth ▇▇▇ is sending the message. BellSouth ▇▇▇▇▇▇▇▇▇ and <<customer_name>> Source One Communications will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Source One Communications and resend the data as appropriate.
Appears in 1 contract
Sources: Resale Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Think 12 which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Think 12 will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Think 12 and resend the data as appropriate. The data will be packed using ATIS EMI records.
Appears in 1 contract
Sources: Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> InterCept which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> InterCept will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> InterCept and resend the data as appropriate.
Appears in 1 contract
Sources: Interconnection Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Navigator which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Navigator will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Navigator and resend the data as appropriate.
Appears in 1 contract
Sources: Telecommunications
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Level 3 which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> Level 3 will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> ▇▇▇▇▇ ▇ and resend the data as appropriate.
Appears in 1 contract
Sources: Interconnection Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Accutel which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> Accutel will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Accutel and resend the data as appropriate.
Appears in 1 contract
Sources: Interconnection Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Express Connection which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> Express Connection will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Express Connection and resend the data as appropriate.
Appears in 1 contract
Sources: Clec Agreement
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> Teligent which BellSouth ▇▇▇ that is sending the message. BellSouth and <<customer_name>> Teligent will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> Teligent and resend the data as appropriate.
Appears in 1 contract
Sources: Telecommunications
The OCN, From ▇▇▇, and Invoice Number will control the invoice sequencing. The From ▇▇▇ will be used to identify to <<customer_name>> ▇▇▇▇▇▇▇▇▇▇.▇▇▇, Inc. which BellSouth ▇▇▇ is sending the message. BellSouth and <<customer_name>> ▇▇▇▇▇▇▇▇▇▇.▇▇▇, Inc. will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> ▇▇▇▇▇▇▇▇▇▇.▇▇▇, Inc. and resend the data as appropriate.
Appears in 1 contract
Sources: Clec Agreement