HansaNet reads the customer list out of your RADIUS or billing panel and puts each customer on the ONU they hang off. One page then answers who is down, who is expiring, and who cannot be placed, and why.
Reading the book
Your billing panel already knows who pays for service. HansaNet reads your panel's customer list: username, name, phone, status, expiry and balance. Nothing is installed on the panel's side.
OneRadius works out of the box. Another panel takes a short one-time setup, which we do with you. The list refreshes regularly, and a customer is never dropped without your say. Your panel password is stored encrypted and never shown back, and you can run more than one panel side by side.
Putting a customer on an ONU
HansaNet matches each customer to the ONU their service runs through, from what your OLT already knows about the boxes on it and what your crew recorded at the drop. A customer that cannot be placed with confidence is left unmatched rather than guessed at. A wrong link sends a technician to the wrong house.
The customers page
The customers page is a directory and a fault list, not a mirror of your panel. Every row carries one state: online, dark, frozen, stale or unlinked. A customer behind a down OLT reads frozen, never dark.
An unmatched customer always carries a reason you can check against the panel:
- the panel's record is missing what the match needs;
- the customer has never been seen on any ONU;
- more than one ONU fits, and nothing settles it;
- the row is gone from the panel's latest list.
The unmatched count covers active customers only. The page sorts by expiry, and a filter narrows it to one panel. It is owner-only: the full book with phone numbers is the largest personal-data surface in the product.
One ONU, several customers. An apartment block or a family on one drop: each resident has their own account on the one ONU. HansaNet shows the customers behind an ONU, never one of them as the customer. A customer has at most one ONU; an ONU may have many customers.
On the OLT roster a shared ONU reads the number of customers rather than one name. One pin locates everyone behind the box, and a WhatsApp notice for the box reaches every resident. The bill does not move: several customers behind one ONU are one billable ONU. See pricing.
The subscriber profile
Every row opens the same profile, from the customers page, the roster, the map or the phone: what the OLT sees at the drop and what your panel says about the account, side by side, with the house, the photographs and the history. Where your crew and your panel hold different phone numbers, both are shown and labelled.
An unmatched customer opens the same profile, with the reason and what to do about it. When an ONU is replaced, the house is not, so HansaNet offers to move the customer's record to the new box, and only an owner's click applies it.
Customer notices read the same book, and a notice can be narrowed to one panel, so a bill reminder for one book never reaches the other's subscribers. See customer notices.
What it does not do
- It reads your panel. It does not write to the panel, take payments, or replace it.
- The panel's own latitude and longitude are ignored. A pin comes from the survey in the field app.
- An unclear match is never guessed. It stays unmatched with the reason printed.
- Expired customers often cannot be placed.
- Matching a customer from the subscriber's router is planned, not built. See TR-069 ACS.
- The customers page is owner-only. A worker sees one subscriber at a time, and a search by phone number never shows the number.
Put a probe on your plant tonight.
One setup .exe on a Windows machine in the rack, or a .deb on Linux. Rs 3 per ONU a month, no plans, no caps.