RADIUS Data Quotas: Check Enforcement Before Selling

WayaDesk / FreeRADIUS

Usage reporting and quota enforcement are different capabilities. A dashboard may show traffic totals without providing a reliable mechanism to stop access at a purchased limit. Selling a capped offer requires evidence of both.

Know LinkDesk’s current boundary

The documented product enforces supported data caps on local Hotspot voucher plans. It does not claim enforced data quotas for the RADIUS paths described in the current release. Do not advertise a RADIUS package with a guaranteed hard cap based only on an accounting total.

Write the required behaviour

If a quota is essential, specify the counting period, unit, reset rule and what happens at the threshold. Include reconnects, interrupted accounting and recovery in the requirement. These details determine whether a proposed implementation actually matches the commercial offer.

• Identify whether the package is time-based, traffic-based or both.
• Confirm the enforcement feature exists on the intended path.
• Keep unmet quota requirements visible in the purchase discussion.

Choose an honest offer

An operator can sell a service whose supported controls are clearly stated, or choose a different verified implementation for a strict quota requirement. The important point is that the customer receives the restriction and allowance described before payment.

Do not turn a report into a promise

Labelling a traffic total “remaining data” can imply enforcement that has not been established. Use labels that reflect the actual record. Ask for a live threshold demonstration before treating any future quota feature as ready for production sale.