Customer to ONU mapping
Know which device belongs to the subscriber before troubleshooting or making service decisions.
Fiber operations
Put fiber context beside the customer record where support can use it.
OLT and ONU information does not replace dedicated network engineering tools, but selected device context beside the subscriber can make billing and support work much faster.
WORKFLOW FOCUSOLT & ONU Management for ISP Billing
Evaluate this use case together with customer lifecycle, finance and network ownership—not as an isolated feature.
What to evaluate
Operational questions that matter in this workflow.
These are practical considerations for comparing software and designing your deployment.
RX power context
Where supported by the OLT, optical power information can help identify likely fiber-side problems.
PON and OLT visibility
Keep basic topology context accessible to support teams.
Learned MAC information
Use device-side learned MAC context where available to support troubleshooting.
History for recurring issues
Current state is useful; historical context can be even more useful when faults are intermittent.
Billing and network together
The value comes from seeing device context beside package, payment and subscriber history.
Why the connection matters
Subscriber state affects more than one department.
A payment can change service state. A support issue can depend on session or ONU context. A reseller collection belongs to a financial hierarchy. Sweet Billing is structured around those relationships.
Billingcycle & ledger
AccessPPPoE / Hotspot
NetworkMikroTik / OLT
Customerportal / support
Fiber operations
Why OLT and ONU Context Belongs Beside ISP Billing Data
Why subscriber billing becomes more useful when OLT, ONU, RX power and device context are connected to the customer record.
Read practical guide