Additional Information; Features; Model Specific Configuration File - Aastra 6700i series Instruction Manual

Additional Information

Additional Information
Configuration Features

Model Specific Configuration File

In addition to the aastra.cfg and <mac>.cfg files, there is now a model specific config-
uration file that is requested after the aastra.cfg file is downloaded. The file is called
<model>.cfg, where "model" should be the same string that is used for the model
name (e.g. 6730i.cfg, 6731i.cfg, 6739i.cfg, 6753i.cfg, 6755i.cfg, 6757i.cfg, 6757iCT.cfg,
9143i.cfg, 9480i.cfg, 9480iCT.cfg).
When the phone starts up, it request configuration files in the following order:
1. aastra.cfg
2. <model>.cfg
3. <mac>.cfg
If the same parameter appears in more once in the above configuration files, the last
parameter/value read will be used (i.e., the following precedence rules will apply):
• Settings in the <model>.cfg file can overwrite aastra.cfg settings
• Settings in the <mac>.cfg file can overwrite <model>.cfg settings
The same download protocol and URL is used for the <model>.cfg file.
As with the aastra.cfg and <mac>.cfg, the <model>.cfg will be written to the
server.cfg on the phone. The server.cfg contents will be a concatenation of the aas-
tra.cfg, <model>.cfg, and <mac>.cfg, respectively.
Note:
The <model>.cfg file is only requested if the aastra.cfg file has been downloaded
successfully. If the <model>.cfg file does not exist on the server and/or has timed
out on the download, the phone will proceed to request download of the
<mac>.cfg file.
Administrators can also encrypt the <model>.cfg file using an Aastra-supplied
encryption tool called "anacrypt.exe" to create a <model>.tuz file.
7
RN-001037-02 REV03 – 06.2011