Billing and RADIUS must stay aligned
When billing says a customer paid but RADIUS still blocks them, support loses time and customers lose trust. ISPAgents should connect billing state, payments, and RADIUS policy with visible evidence.
RADIUS billing workflows
| Workflow | ISPAgents role | |---|---| | Plan mapping | Map service packages to groups, profiles, rate limits, or access policies. | | Suspension | Change access state for overdue subscribers according to operator rules. | | Restoration | Restore paid customers through RADIUS or CoA where supported. | | Accounting | Use session context and customer history for support and NOC visibility. | | Hybrid rollout | Keep existing FreeRADIUS or move selected sites to managed RADIUS. |
Access evidence
Support should see username, NAS, policy, service plan, last payment, last automation result, and the reason for blocked or restored service.
FAQ
Does ISPAgents require managed RADIUS?
No. ISPAgents can support existing FreeRADIUS, managed RADIUS, MikroTik direct control, and custom connectors.
Can RADIUS and MikroTik direct control coexist?
Yes. Many networks need both patterns for different sites, packages, or legacy workflows.