Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius 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.
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement Amendment
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius 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. Xxxxxxxx will incur an OSS charge for an accepted LSR that is later canceled by Xxxxxxxx . Note: Supplements or clarifications to a previously billed LSR will not incur another OSS charge.
Appears in 2 contracts
Samples: Clec Agreement, Interconnection Agreement
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius Xxxxx 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.
Appears in 1 contract
Samples: Resale Agreement
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius X. 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, and therefore will be billed as one LSR per location.
Appears in 1 contract
Samples: Resale Agreement
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius Xxxx Communications 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.
Appears in 1 contract
Samples: Telecommunications
Denial/Restoral OSS Charge. 2.13.3.1 8.3.1 In the event Xspedius Xxxx 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.
Appears in 1 contract
Samples: Interconnection Agreement
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius Xxxx 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.
Appears in 1 contract
Samples: Clec Agreement
Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event Xspedius Xxxx 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.
Appears in 1 contract
Samples: Interconnection Agreement
Denial/Restoral OSS Charge. 2.13.3.1 14.3.1 In the event Xspedius Xxx.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.
Appears in 1 contract
Samples: Interconnection Agreement
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius Xxxx Communications 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.
Appears in 1 contract
Samples: Clec Agreement
Denial/Restoral OSS Charge. 2.13.3.1 In the event Xspedius Xxx.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.
Appears in 1 contract
Samples: Clec Agreement
