Mitel 6800 Series, Administrator'S Manual, Page: 750 / 1113

Mitel 6800 Series SIP Phone Release 4.2.0 SP2 Administrator Guide
A-8
SETTING PARAMETERS IN CONFIGURATION FILES
You can set specific configuration parameters in the configuration files for configuring you IP
phone. The
startup.cfg, <model>.cfg,
and
<mac>.cfg
files are stored on the server. The
startup.cfg
file stores global IP phone configuration settings.
The
<model>.cf
g file contains model specific information. The
<mac>.cfg
file stores
configuration settings specific to the IP phone with that MAC address. When you restart the IP
phone, these files are downloaded to the phone.
If you make changes to the phone configuration, the changes are stored in a local configuration
on the phone (not on the server).
Configuration changes made to the
<model>.cfg
file override the configuration settings in the
startup.cfg
file. Configuration changes made to the
<mac>.cfg
file override the configuration
settings in the
<model>.cfg
and
startup.cfg
files.
Reference
For information about configuration file precedence, see Chapter 1, the section, “Configuration
File Precedence” on page 1-25.
This section includes the following types of configurable parameters:
• Operational, Basic, and Advanced Parameters on page A-9
• Mapping Key Settings on page A-216
• Softkey/Programmable Key/Keypad Key/Expansion Module Key/Hard Key Parameters on
page A-221
• Advanced Operational Parameters on page A-284
• Troubleshooting Parameters on page A-318
Note:
In releases previous to 4.0.0 SP1, the "startup.cfg" file was named "aastra.cfg".
Apart from the file names, the "startup.cfg" file acts as an identical replacement for the
"aastra.cfg" file. Releases including and above 4.0.0 SP1 support both the "startup.cfg"
and "aastra.cfg" files, but if the "startup.cfg" file is available, the phone will disregard the
"aastra.cfg" file (if available). The "aastra.cfg" file will be used if the "startup.cfg" file is
unavailable and will continue to be supported going forward to ensure backwards
compatibility with existing customer deployments.
Note:
Configuration parameters that you enter in the configuration files are NOT case
sensitive.