UC Software 4.0.0 or later:
Since UCS 4.0.0 the phone can import configuration files via the Web Interface. For more information please check => here <=
This is useful in order to add configuration changes to an individual phone with Parameters that are not available to change via the Web Interface or the Phone GUI.
The expected format would be an XML file with the .cfg as a file extension.
Some community replies or the Admin Guide contain individual parameters.
Simply open a compatible editor like Notepadd++ and paste the parameter into it:
Any configuration file needs to start with a < chevron and end with a /> forward-slash chevron
Simply save this with any name ending with .cfg and import using the above menu
Older than UC Software 4.0.0 or Provisioning Server:
Each released version of SIP or UCS software contains the relevant supported configuration files that, depending on the software Version, are needed to provision the phone.
NOTE: Do not ever mix configuration files from previous versions with newer versions!
Since the appearance of newer phone models, older phones have been classed as legacy phones, and the newer phones software now may contain a sip_(Version of Sip).cfg and a phone1_(Version of Sip).cfg
This allows a mix of phones and guarantees backwards capability.
NOTE: Please consult the SIP / UCS Admin Guide matching your software version!
UCS 3.3.0 removed the need for this and the phone does only need to download either the templates files listed in the \Config subdirectory or any self-created files that had been listed within the CONFIG_FILES=" " section of a 000000000000.cfg or manually created <mac>.cfg.
Example file's from within the \Config subdirectory within UCS 3.3.0:
The user must specify the files that should be loaded via the CONFIG_FILES="" section as these are not automatically loaded.
For more details please check => here <=
NOTE: The files within the \Config are only templates and individual parameters can be copied & pasted into a manually created file(s) instead!
In the above example the parameter
is disabled aka ="0".
This matches the factory configuration so specifying the file within the config_files="" section would not actually make any changes unless this applications.cfg file would be modified.
Manually creating a configuration file:
NOTE: Please note that the configuration file must be XML conform or the phone will ignore it!
In order to change the standard value of a single parameter it is easier to create an individual file.
The example parameter used in below is se.rt.enabled="1"
If 0, the ringtone feature is not enabled on the phone. If 1 (default), the ringtone feature is enabled.
Using UCS 3.3.0 or newer (check the matching admin guide) the parameter is contained in the template file features.cfg.
Above shows an individual file stored as rt.cfg and the value changed from the factory default 1 into 0.
Only the individual Phone with this MAC address will load this parameter.
NOTE: Substitution placeholders can be used as shown => here <=
When a user wants to provision and automate the configuration of a large number of phones they could utilize the attached excel spreadsheet to do so.
For the steps below please familiarize yourself with the Poly Admin Guide for the phone model in question. Poly support suggest using an editor like Notepad++
prov.polling.enabled="1" prov.polling.mode="random" prov.polling.period="86400" prov.polling.time="03:00" prov.polling.timeRandomEnd="05:00"
Each phone will now boot out of the box from the DHCP Server and find it's DHCP Option and search first for its own Mac address.cfg file and then skip this step and download the 000000000000.cfg instead.
Whilst parsing the 000000000000.cfg it will check the config_files section and load the general.cfg and then next automatically substitute the [PHONE_MAC_ADDRESS] part and replace this with its own Mac address-individual.cfg and load this.
NOTE: The above information is supplied to help users but Poly cannot be held responsible for any of the attached files. If you require support please work with your Poly reseller as outlined => here <=