26/1531-ANF 901 14 Uen S 2019-10-18 16
M
ANAGING IP PHONE SW
8 MANAGING IP PHONE SW
8.1 PHONE SOFTWARE AND CONFIGURATION FILES ON
THE SOFTWARE SERVER
If any configuration file or firmware is changed on the software server, the phones are
updated when restarted. The following files need to be stored on the software server:
<phone model>.st
The application firmware (software) for the phones. The names of the application
files are:
• 6920.st, 6930.st, and 6940.st
• 6863i.st, 6865i.st, 6867i.st, 6869i.st and 6873i.st
• 6730i.st, 6731i.st, 6735i.st 6737i.st and 6739i.st
• 53i.st, 55i.st and 57i.st (for 6753i, 6755i and 6757i)
aastra.cfg/startup.cfg
This file contains the configuration parameters for all phone models in the
system. The configuration file has to be adapted for each installation.
This file is created in IP Phone Configuration File task in MX-ONE Service Node
Manager. If it is not possible to use MX-ONE Service Node Manager, the
aastra.cfg/startup.cfg template must be used which is stored in MX-ONE under
/etc/opt/eri_sn/aastraSIPphones/.
aastra.tuz/startup.tuz
This is the encrypted aastra.cfg/startup.cfg file. The phone uses http protocol to
fetch this file. The configuration file has to be adapted for each installation and
then it has to be encrypted, see section 19.1 Encrypted Configuration Files on
page 69.
<phone model>.cfg
This file contains configuration parameters for the key layout for each phone
model. The names of the configuration files are:
6920.cfg, 6930.cfg, 6940.cfg,
6863i.cfg, 6865i.cfg, 6867i.cfg, 6869i.cfg,
6873i.cfg, 6730i.cfg, 6731i.cfg, 6735i.cfg, 6737i.cfg, 6739i.cfg,
6753i.cfg, 6755i.cfg, 6757i.cfg
The settings in <phone model>.cfg will override the settings in
aastra.cfg/startup.cfg..
This file is created in IP Phone Configuration File task in MX-ONE Service Node
Manager. If it is not possible to use MX-ONE Service Node Manager, the
<phone model>.cfg template must be used which is stored in MX-ONE under
/etc/opt/eri_sn/aastraSIPphones/.
<phone model>.tuz
This is the encrypted model specific configuration file. The configuration file has
to be adapted for each installation and then it has to be encrypted, see 19.1
Encrypted Configuration Files on page 69.
<mac>.cfg
When this file is used, it is possible to get unique parameter settings per tele-
phone. This file is optional and the file looks similar to the aastra.cfg/startup.cfg
To Next Page
Loading...
