TR-069 Technote

About This Technote

This technote gives a brief introduction of TR-069 and instructions of how to enable TR-069 on Yeastar VoIP gateways. The technote also provides RPC methods supported on Yeastar VoIP gateways.

Supported VoIP Gateways and firmware version:

  • TA1600/2400/3200 (
  • TA400/800 (
  • TB200/400 (

* TR-069 will be supported on the following gateways soon:

  • TA410/810
  • TA1610/2410/3210


What is TR-069?

TR-069 (Technical Report 069) is a Broadband Forum (formerly known as DSL Forum) technical specification entitled CPE WAN Management Protocol (CWMP). It defines an application layer protocol for remote management of end-user devices. As a bidirectional SOAP/HTTP-based protocol, it provides the communication between customer-premises equipment (CPE) and Auto Configuration Servers (ACS). It includes both a safe auto configuration and the control of other CPE management functions within an integrated framework. The protocol addresses different Internet access devices such as modems, routers, gateways, set-top boxes, and VoIP-phones for the end-users.


Figure 1 TR-069 Schematic Design

Why Use TR-069?

With TR-069, Service Providers can use one common platform to manage, through the Internet, all of their Customer Premise Devices, no matter the device nor the manufacturer.
This common application has never been achieved before due to CPE vendors creating proprietary mechanisms for management.

What is the Scope of the Remote Management?

Auto provisioning is used to provide configuration information to multiple Yeastar VoIP gateways, while remote management takes this one step further.

  • Auto Provision

This mechanism allows Yeastar devices auto-provisioning at the time of initial connection, and the ability to re-provision at any subsequent time. The ACS can also check the provision status (success or failure).

  • Reboot and Reset the devices

Yeastar devices can be rebooted and reset by using the mechanisms established by TR-069.

  • Firmware Management

The Yeastar device firmware could be updated by downloading the firmware file from the ACS.TR-069 also provides mechanisms for version identification and file download initiation (ACS initiated downloads and optional phone initiated downloads). The ACS can be notified of the success or failure of a file downloading.

  • Monitoring CPEs’ Status & Performance

With RPC methods GetParameterValues and GetParameterAttributes, the ACS could monitor Yeastar CPEs’ status and performance statistics. A set of mechanisms defined in TR-069 allow Yeastar CPEs to actively notify the ACS of changes.

  • Configuring CPEs’ parameters

Settings on Yeastar CPEs can be configured remotely on ACS by sending a RPC method.

TR-069 Configurations on Yeastar VoIP Gateways

TR-069 feature is disabled on Yeastar VoIP gateways by default. You can enable the feature on the gateways’ Web user interface.
Path: Gateway Network Preferences TR-069 Settings
Enable TR-069 and configure the parameters in the corresponding fields, if configured correctly, the gateway will establish the TR-069 session with the ACS.

Figure 2 TR-069 Settings on Yeastar Devices

Table 1 Description of TR-069 Settings

Supported TR-069 RPC Methods
A RPC (Remote Procedure Call) mechanism is used for bi-directional communication between a CPE device and an ACS. An ACS can get or set parameters to configure and monitor the CPE by using the RPC methods.
The following table provides a description of supported TR-069 RPC methods by Yeastar devices.

Table 2 Supported TR-069 RPC Methods

Data Model

Most of the configuration and diagnostics is performed through setting and retrieving the value of the Yeastar CPEs’ parameters. These are organized in a well defined hierarchical structure that is more or less common to all device models.

For more information about the common and customized Yeastar devices’ parameters, please refer to Yeastar_TR-069_DataModel.xlsx. Each of the parameters is marked as writable or non-writable.
Please contact Yeastar technical support for the data model file.

ACS Information

Every ACS is different, but as TR-069 is a standard, ACS vendors should work properly as well once the connection is established. Several ACS have been tested with Yeastar CPEs and work properly.

  • Axiros Axess
  • IoT (Internet of Things)
  • Friendly ACS

Standards Compliance
Yeastar CPEs support the following standards listed below. For more information about the standards, please refer to Broadband Forum website.

  • TR-069

  • TR-098

  • TR-104 (Compliant with SIP)

  • TR-111 (Device Gateway Association & Connection Request via NAT Gateway)

Have more questions? Submit a request


Please sign in to leave a comment.