TR-069 Protocol Support
8
41-001373-01 REV02 – 05.2014
Configuration Backup and Restore
Administrators can backup and restore the TR-069 configuration on the ACS server. The ACS server makes a request for a
log file upload and the phone responds to the request.
For a log file upload, the server sends the following parameters:
•
URL
•
File type
•
Username
•
Password
When the phone receives the request to backup, it uploads the file to the TFTP server with the name
“
MACADDRESS_local.cfg
”. The protocol supported for log file upload from CPE are HTTP, TFTP, and FTP.
Log File Download from CPE
The ACS server can make a request for a log file upload. For a log file upload, the server sends the following parameters:
•
URL
•
File type
•
Username
•
Password
When the phone receives this request, it will send the file to the TFTP server with the name
“
MACADDRESS_TIME_crash.log
”. The protocol supported for log file upload from CPE are HTTP, TFTP, and FTP.
Firmware Management
At any point, the ACS can trigger the CPE to upgrade its firmware image. The ACS sends asynchronous connection
requests, triggering the CPE to establish a transaction session to receive a download method to upgrade its firmware.
The ACS is only responsible for sending the download RPC and retrieving the TransferComplete RPC. The actions taken
by the CPE itself depend on the firmware upgrade mechanism, which is not defined by TR-069.
The Administrator can schedule a firmware upgrade from the ACS by properly configuring the ACS server. Once the ACS
server is configured, the phone will automatically upgrade the firmware.
The following is the process of how the phone upgrades the firmware:
•
The phone receives a download RPC from the ACS.
•
If the FileType argument is set to “1Firmware Upgrade Image”, a firmware upgrade is started
•
The phone checks the version of firmware:
–
If the version is identical to the actual version, the phone will abort the firmware upgrade
–
If the version is different of the actual version, the phone will upgrade/downgrade the firmware
•
If the firmware upgrade is successful, a reboot is initiated
Passive and Active Notification
The phones support active and passive notification. If a parameter is configured to "Active notification", when this
parameter is modified through the Aastra Web UI, an inform message with the new value of the parameter is sent to the
ACS (the phone does not wait for the periodic inform).
If a parameter is configured to "Passive notification", when this parameter is modified through the Aastra Web UI, the
new value of the parameter is sent to the ACS with the periodic inform.
If there is no notification set, no inform message is sent to inform the ACS when the value of the parameter is modified.
For any parameter, the notification type (Active, Passive, or None) is set on the ACS server.
