Implementation guide
WISP Billing Software for Fixed Wireless Operators
WISP operations cross commercial and radio-network boundaries. ISPbills connects subscriber packages and collections to supported access, tower, device and support context.
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.
Connect fixed-wireless subscriber billing with MikroTik, RADIUS, towers, sectors, device monitoring, payments and support operations. Confirm the exact device, software version, provider contract and failure behavior in a representative environment before production rollout.
Model the service
Associate the subscriber, site, sector, access device, package and billing cycle.
Control authenticated access
Use supported MikroTik and RADIUS workflows for policy and sessions.
Investigate impact
Review customer and network state together when a sector, router or payment event changes service.
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.
- Tower and sector inventoryTest this requirement with representative data and retain the result in the implementation plan.
- CPE and router compatibilityTest this requirement with representative data and retain the result in the implementation plan.
- AAA redundancyTest this requirement with representative data and retain the result in the implementation plan.
- Power and backhaul monitoringTest this requirement with representative data and retain the result in the implementation plan.
Implementation answers
Is ISPbills only for fiber ISPs?
No. ISPbills supports fixed-wireless, wired, fiber and hotspot operating models.
Can WISPs use MikroTik and RADIUS?
Yes. Both RouterOS API and centralized FreeRADIUS workflows are supported.
Does it include tower monitoring?
ISPbills can retain site and device monitoring context; confirm the exact devices and signals required.
Bring the actual routers, access design, billing rules and failure cases.
Explore the online workspace or ask ISPbills to review compatibility and migration scope.