Frequently Asked Question
Overview
A ConfigID file is a file that uses the ConfigID to identify the configuration file. 3.x firmware ConfigID files take the following form:.cetis.cfg. The ConfigID is generally the extension or room number of a room. By default the phone prompts for a ConfigID after its MAC file is requested and/or downloaded. The ConfigID is not globally unique and is not known by the phone without programming. Unlike 1.x and 2.x phones, ConfigIDs in 3.x phones will persist without loading a configuration file. Ex:
Scenario with 1.x and 2.x:
1. Phone boots up and requests the user to input a ConfigID so it can go get configuration from the provisioning server.
2. User enters ConfigID.
3. Phone requests ConfigID file from server.
4. Provisioning server doesn't have the file.
5. Next time phone boots it will NOT request the configuration file again because the input previously entered by the user is forgotten.
Scenario with 3.x:
1.Phone boots up and requests the user to input a ConfigID so it can go get configuration from the provisioning server.
2. User enters ConfigID.
3. Phone requests ConfigID file from server.
4. Provisioning server doesn't have the file.
5. Next time phone boots it WILL request the configuration file again because the input previously entered by the user is remembered.
Scenarios
1. Easier staging - Installer can pre-program phones without needing access to configuration files as long as he knows what the ConfigID should be (generally just a derivative of the room number).
2. Easier adds and replaces - Staff doesn't have to wait for the phone to load its configuration file before unplugging and taking the phone to a room. Staff only needs a PoE port and doesn't even have to connect to the voice network/provisioning network.
Notes
1. Configuration file loaded should have the ConfigID field filled in correctly as with all Cetis phones. Otherwise the phone will overwrite the ConfigID to be blank and the phone will request a ConfigID on reboot events.
2. If ConfigID is not desired then disable it under Provisioning in the webUI or configuration file.