Custom button labels and call logs not backed up

CM 4.0 and later and Avaya Utility Server 6x and later

If the “Set BRURI http://xxx.xx.xx.xx/directory” is not edited in the 46xxsettings.txt file to point to a directory path where all the button labels should be stored, all the customized labels modified on the phones and historical call logs will be lost after a reboot or a network outage.

The BRURI settings in the 46xxsettings.txt file are specified to point to the directory path of the backup folder, prior to initially customizing the button labels. Once the BRURI is set, the backup process would compare what it has in the PBX to the current status of the labels and would back up only what it would see as a change.

Note that when using the Avaya Utility server port 81 is used for HTTP write access from the phone to the Utility Server.

We can check the BURI from a Linux server on the same network as the Utility server, below is a command we can use from Communication Manager in Linux to see what if anything our BRURI setting is set to, for example, say our Utility server is The command we execute is shown below in bold.

admin@server1> curl | grep BRURI

SET BRURI http://util-01:81/PhoneBackup

We can see that our Utility server at is the destination for our IP phones and on the server util-01, we are using PhoneBackup as the directory.


In this case, we did not have the BRURI setting set correctly on the 46xxsettings.txt file. Because of this, the IP phones were not able to back up their call logs.

For example, The 46xxsettings.txt file has a “Set BRURI http://xxx.xx.xx.xx/backup” entry, where “xx.xx.xx.xx” is the IP Address of the HTTP
server and the /backup is where the Extdata.txt file (extension) of the button label is stored. The BRURI needs to be set up with the HTTP
server address, and the directory path to backup folder prior to customizing the button labels on the 96xx series IP phones.


Adjust the 46xxsettings.txt file to have the BRURI setting uncommented and pointed at a server that supports writing to a directory using HTTP from the Avaya phones.
The video examples in this article use an Avaya Utility server that is set up to allow phones to back up to the /var/www/http/PhoneBackup directory via port 81.
Note that when setting the BRURI parameter we do not need the /var/www/http/ portion of the directory string, we only need the PhoneBackup directory to be set in the 46xxsettings.txt file. The phones have to be rebooted for them to read in this setting.

If your Utility Server is not supporting backups on port 81 then run the following command from Linux which will allow the Utility server to accept HTTP requests from the phones.


We can now see on our Utility server the text files that the phones backup.


Use the command display button-label <ext#> to see all of the current customized labels in the PBX. An asterisk before the label
indicates that it is a customized label

Be sure to set up your BRURI settings on your HTTP server to point to the directory path of the folder you created to have your button
labels of each extension stored prior to customizing all your button labels on the phones. A manual backup option is enabled on the
phones to allow you to backup your button labels as well
Was this article helpful?
Thank you!