Automatic Configuration
In this document, we'll show ways to automatically configure TR-069 on CPEs. There's no single format that fits every situation, especially since we're a continental-sized country, with providers using different protocols, different equipment brands, different device types, and different configuration methods.
In some scenarios the configuration is quick and practical, and unfortunately, in some cases, TR-069 needs to be configured CPE by CPE.
Configuration via OLT
Providers that use ONUs/ONTs from the same manufacturer as the OLT can take advantage of automatic TR-069 configuration. This is usually done by setting parameters together with profiles.
See the dedicated step-by-step guide at Configure TR-069 via OLT (OMCI), with tutorials by manufacturer:
- Huawei OLT — TR-069 via OMCI
- ZTE, Nokia, Fiberhome, Cianet OLTs (in progress)
In addition, some OLTs allow configuration via commands. In these cases, the provider can create a Script in Cpehub and run the configuration command(s) — see Create and use Scripts (OMCI).
Configuration via Preset
Providers that use device presets can have the TR-069 configuration written into the firmware.
This configuration method can be used on both ONUs/ONTs and WiFi routers. The only requirement is that the manufacturer provides a way to preset the device.
Here are some external resources from a few manufacturers:
- Huawei routers (WS52xx, AX2, AX3, etc.)
- Preset is done via HiConfig
- Download link
More details at Configure via Preset (firmware).
Configuration via DHCP
Providers that use a topology with DHCP dedicated to TR-069 can send parameters via Option 43, which not only provides the IP for the device to communicate over Layer 3, but also tells the device which ACS server it should connect to.
Unfortunately, this configuration method isn't standardized, since Option 43 is defined in RFC 2132 as "DHCP Options and Vendor Extensions" — meaning it's defined by the manufacturer itself, so each manufacturer can use a different parameter format.
In this case, you need to understand which device will be used, whether it accepts receiving the ACS URL via Option 43, and which format it expects.
The standard DHCP message exchange sequence looks like this:
If the device/server used by the manufacturer supports several Option 43 formats at the same time, it's possible to define multiple formats and configure different devices. However, some devices don't allow this configuration (Mikrotik doesn't accept multiple options with the same code); for these cases, Cpehub provides a DHCP Option 43 Generator that helps build the option value for each manufacturer.
The step-by-step guide is at Configure via DHCP Option 43.
Conclusion
Providers that don't fit any of the scenarios above will unfortunately only be able to use TR-069 by configuring their devices manually.
If you have any questions about this topic, we're available to talk and figure out how to set up configuration in your environment.