Common use of Denial/Restoral OSS Charge Clause in Contracts

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> provides customer_name>>_provides a list of customers to be denied and restored, rather than an LSRLSR , each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> SouthEast provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> Knology provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> VELOCITY provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> NOW provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> provides Xxxxx-4-U_provides a list of customers to be denied and restored, rather than an LSRLSR , each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> Xxxxxxxx provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> XXXxxxx.xxx provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 8.3.1 In the event <<customer_name>> ONS provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> COMTECH21 provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> FeroNetworks provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> 1-800-RECONEX provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> C.M. provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> NOW provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> LS-One provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>customer_short_name> provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 6.7.3.1 In the event <<customer_name>> CTES provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> Xxxxxxxx.Xxx provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> Nex-Phon provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> Preferred provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> 1-800 RECONEX, Inc. provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event <<customer_name>> Advantage Group provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> SBCT provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> Community provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> Xxxxxxx provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> NAS provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 8.3.1 In the event <<customer_name>> C.M. provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, and therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> Communication Services Integrated, Inc. provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.

Denial/Restoral OSS Charge. 2.13.3.1 In the event <<customer_name>> LINEDRIVE provides a list of customers to be denied and restored, rather than an LSR, each location on the list will require a separate PON and, therefore will be billed as one LSR per location.