Telematrix SIP Phone, Руководство администратора, Страница: 32 / 55

sipsupport@telematrix.net Page 32 www.telematrix.net
The steps are below.
•
Create the new configuration in the MCU.
•
Create a set of phone-templates. A phone template is a configuration file that is
complete and tested for 1 extension. It is created by editing the configuration through the
GUI or by editing a configuration file directly. After the phone is fully tested, upload the
working configuration file to your PC.
•
Create a set of room-templates. Each template describes a room that will be identically
equipped and configured. For example, the Executive room-template might designate 3
phones, the “cordless beside” phone-template, executive-desk template and the
bathroom template.
•
Create the Buildings, Floors and Room numbers. Define what buildings exist. Define
how many floors are in the buildings and what the floors are “named”. Each room must
be associated with a room-template.
•
Generate phone configuration. Once the above information is set, a single operation can
generate the actual phone configurations. A room with 3 phone-templates in its room-
template will result in the 3 phone configuration records. A phone configuration will
contain a full, individually modifiable phone configuration. The values will have been set
according to the room-template and phone-template.
•
Generate configuration files. When all the phone configurations are correct, the
administrator can write out all the configuration files out to a directory, perhaps directly to
the TFTP home directory.
The administrator can modify individual phone configurations. If a phone-template is changed,
the Administrator must re-generate the configuration files to propagate the changes to the
individual phone configurations. Whenever a change is made directly to a phone configuration,
a flag is set in the record, so exceptions are always known.
Phone Installation
Installation is the placement of a new unconfigured phone in a room. Using an installation
plan, the Installer selects the type and number of phones for the room. Face plates are
installed at this time if the faceplates are room specific. Each phone is placed, connected
to the network and powered up. The phone will obtain an IP address and the TFTP Server
address from DHCP. The phone, because no ConfigID is yet configured, will prompt the
Installer for the ConfigID. The installer enters the ConfigID through the keypad. Once the
ConfigID is entered, the phone will use the TFTP Server to load the proper configuration
file. The phone will then reset and bring itself up under the new configuration. The phone
should display indications that it is up on the correct extension and is registered. The
Installer then conducts whatever tests are deemed necessary.
If a phone fails to come up correctly, the Installer will make only minimal efforts to
troubleshoot the problem. A second phone will then be tried. If that too fails, the problem
will be escalated to the Administrator as a probable error in the configuration. If the second
phone succeeds, the first will be marked DOA and set aside.
The ConfigID should be a predictable combination of codes so that the Installer does not
need a voluminous list of ConfigIDs. For example, the bathroom phone in room 1206 could
have a ConfigID of 91206, the bedside phone 71206 and the desk phone 81206. If the
phone type string for this phone is “3300ip”, then the configuration file name for the
bathroom phone would be 91206.3300ip.txt.