Implementation guide
RADIUS Accounting for ISP Subscriber Sessions
Accounting records explain when a session began, how it changed and why it ended. Their usefulness depends on stable identifiers, synchronized time and handling for missing or duplicated packets.
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.
Plan the complete path, not one isolated setting.
Understand RADIUS start, interim and stop records, session state, usage visibility and reconciliation for ISP access networks. Confirm the exact device, software version, provider contract and failure behavior in a representative environment before production rollout.
Start the session record
Capture subscriber, NAS, session identifier and assigned service context.
Accept interim updates
Refresh usage and session state at an interval appropriate to operations and scale.
Close or reconcile
Process stop and termination data, then detect sessions that became stale without a clean stop.
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.
- Acct-Session-Id stabilityTest this requirement with representative data and retain the result in the implementation plan.
- Interim interval and database loadTest this requirement with representative data and retain the result in the implementation plan.
- Duplicate packet handlingTest this requirement with representative data and retain the result in the implementation plan.
- Stale-session reconciliationTest this requirement with representative data and retain the result in the implementation plan.
Implementation answers
Are accounting packets guaranteed?
No. UDP delivery and device failure can produce missing or duplicate events, so reconciliation is required.
What is an interim update?
It is a periodic accounting record sent during an active session to refresh usage and state.
Can accounting replace flow telemetry?
No. RADIUS accounting describes access sessions; flow telemetry describes network conversations and traffic patterns.
Bring the actual routers, access design, billing rules and failure cases.
Explore the online workspace or ask ISPbills to review compatibility and migration scope.