Implementation guide
ONU Management Software for FTTH Operations
An ONU record becomes operationally valuable when its serial, PON position, optical state, service profile, physical location and subscriber ownership agree.
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.
Discover, provision, associate and diagnose supported ONUs with optical, PON, subscriber, location and billing context in ISPbills. Confirm the exact device, software version, provider contract and failure behavior in a representative environment before production rollout.
Discover and identify
Capture the serial and access location from a supported OLT without guessing customer ownership.
Authorize and associate
Apply the approved service profile and connect the ONU to the correct subscriber and location.
Diagnose and retire
Review optical and state history, then decommission equipment without leaving stale assignments.
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.
- Vendor, model and firmwareTest this requirement with representative data and retain the result in the implementation plan.
- Serial and PON labelingTest this requirement with representative data and retain the result in the implementation plan.
- VLAN and service-profile mappingTest this requirement with representative data and retain the result in the implementation plan.
- Optical thresholds and field verificationTest this requirement with representative data and retain the result in the implementation plan.
Implementation answers
Can ISPbills auto-discover ONUs?
Supported OLT integrations can expose unconfigured ONUs for review and guided provisioning.
Can one customer have multiple ONUs?
Modeling depends on the service design; validate customer, service and equipment cardinality during implementation.
Is every ONU feature vendor-neutral?
No. Available telemetry and write actions depend on the OLT vendor, model, firmware and driver.
Bring the actual routers, access design, billing rules and failure cases.
Explore the online workspace or ask ISPbills to review compatibility and migration scope.