Frequently Asked Question
Partial Config Files
Last Updated 2 years ago
Overview
Config Files provide the settings that a phone needs to work with the network and phone system. 3.x phones have a configuration filename of .cetis.cfg for easy provisioning of the phones from a provisioning server. Each configuration file has a version header and many sections (approx. 17 or so). Under each section are grouped the relevant settings and values for those settings. The format being the following:
The version part of the version number controls whether the file is considered a 3.x file. All 3.x phones only accept files with '3' as the version number. The sequence part of the version number controls what iteration of the file it is, and is used when determining if a configuration file is newer than the current configuration file on the phone. For instance a sequence of .1001 is higher than a sequence number of .1000. The sequence number is checked when updates are received from the configuration server after a normal reboot or update time. Sequence number is not checked when the configuration is manually imported, or the **77*123*# command is used to force retrieval of a configuration file.
A Partial Config File is a file that only has the version header and 1 or more sections of a configuration file with the setting/value pairs for that section(s). This is a possible configuration, but Cetis' recommends that all configuration files be fully planned out, and regenerated to avoid mistakes. The usage of a partial config file generally means one of the following:
1. Phones have been manually configured and/or configuration files manually uploaded.
2. No provisioning server was originally used.
3. Configuration tools were not used and therefore new configuration files cannot be generated without re-doing configuration.
Any of these options generally mean that configuration has not be documented and controlled systematically. This has the potentially for errors and more difficulties as phones need changes or new phones are added. However, if you are not able to fix the above, or do not need to generate new configuration files, partial config files might help save some time.
Sample Scenarios
1. Dial Plan has changed and there are no configuration files to change (as per reasons above). This could involve lots of typing. Or you can do the following:
- Test new dial plan on one phone.
- Export the configuration file.
- Leave the version header alone.
- Delete all sections except [Digitial_Map]
- Load that partial configuration file manually into each phone.
Warning: Partial Config usage is provided as an example. If you are using a partial config to solve a problem, test it extensively, as we do not recommend this as a good deployment model.