Implementation guide

Automatically Suspend and Restore Expired PPPoE Users

Automatic suspension affects a customer’s service, so the billing event, grace rule, active session and recovery path must be unambiguous. ISPbills keeps those decisions within the subscriber lifecycle.

Use the interface and documentation together.

The capture below shows the related ISPbills product area. Follow the linked documentation for current fields and prerequisites, then validate the exact device, provider, software version, failure path and rollback before production use.

ISPbills MikroTik monitoring interface with RouterOS device details
MikroTik monitoring view; available data depends on RouterOS access and configuration.

Plan the complete path, not one isolated setting.

Design safe MikroTik PPPoE expiry, suspension and reconnection workflows around billing status, grace periods, sessions and operator overrides. Confirm the exact device, software version, provider contract and failure behavior in a representative environment before production rollout.

01

Define eligibility

Specify due date, grace period, partial-payment and exception rules.

02

Apply the access change

Use the supported RouterOS or RADIUS workflow and record its result.

03

Restore safely

Verify the payment once, reverse the intended restriction and confirm the subscriber can reconnect.

Prove the boundaries before automating them.

Record expected results, failure signals, the person who can approve a change, and the rollback path. Product support depends on the deployed architecture and integration version.

  1. Timezone and billing cut-offTest this requirement with representative data and retain the result in the implementation plan.
  2. Active-session disconnect policyTest this requirement with representative data and retain the result in the implementation plan.
  3. Failed device action handlingTest this requirement with representative data and retain the result in the implementation plan.
  4. Manual exemption and audit trailTest this requirement with representative data and retain the result in the implementation plan.

Implementation answers

Must an active session be disconnected?

That depends on the policy and access architecture. A credential change may not affect an already active session without a disconnect or CoA.

Should every overdue account be suspended immediately?

No. Configure contractual grace, dispute, partial-payment and exemption rules before enforcement.

How is service restored?

A verified payment or approved override can make the account eligible, after which the configured access workflow restores service.

Validate with your own environment

Bring the actual routers, access design, billing rules and failure cases.

Explore the online workspace or ask ISPbills to review compatibility and migration scope.

Open online demoDiscuss your deployment