Aspectos pedagógicos del aprendizaje motor

This section focuses on describing the environment that the TeleMatrix hospitality SIP phones will usually be installed within.

Users

The requirements for phone installation and configuration are focused first on the needs of two types of users, the installer and the administrator. The guest is not a “user” in this discussion. Installer The Installer wants to place phones quickly, easily and reliably. This user has

limited technical knowledge and mainly wants to avoid complication. Anyone placing or replacing a phone in a room is acting in the role of Installer. Administrator This person creates the configurations and is the local person who has

knowledge of how the system should work. The administrator has control of the network and IPBX configuration as well as the phone configurations. This role might be split among two or more people. The administrator wants to be able to control and configure all phones from a central point. The

configuration of hundreds of phones is inherently complex and the

administrator wants tools that simplify this as much as possible. He needs to be able to find the configuration of a given phone quickly and determine what configuration is active in the phone. He needs to be able to update the configuration of one or more phones easily from a central point.

Environment

The relevant parts of the environment for configuration and installation are as follows.

Phones There will be several models of phone at any property. Each phone may have unique requirements for its own configuration, even when all are provided by TMX. We are concerned only with TMX VOIP phones here. Any analog phones or non-TMX VOIP phones on the property are out of the scope of this document. The phones are customized for the property in various ways including custom face plates.

Every phone has a web UI from which the configuration can be modified using a browser. Every phone has a keypad UI using the 12 key keypad for entering and retrieving critical information.

IPBX The VOIP phone switch. The phones register with the IPBX to form the phone system on the property. The IPBX has a configuration which must match up with the phone configuration.

TFTP Server The TFTP Server will hold the configuration files for the phones. It is addressed via IP.

PMS Property Management System. The PMS and the IPBX must communicate for various reasons. The phones do not communicate directly to the PMS, only indirectly through the IPBX. The PMS knows a phone only indirectly by its extension or room number.

Room A room may have one or more phones installed. They may be of different types. Each phone will have its own configuration. Each phone will be connected to the network. There may be multiple types of room, standard, deluxe, executive, suite, etc. The phones in a room are part of a group and have the same extension number.

Network The layer 2 network as it appears to the phone may be a simple LAN or a VLAN. Lower end properties are likely to have only a single LAN which carries voice and other traffic. Bigger properties are likely to have multiple VLANs. The phones and IPBX will communicate via IP and will use IP addresses to reach each other. The phones will obtain IP addresses, the TFTP server address and VLAN assignments from a DHCP server.

Mass Configuration Utility This tool creates the configuration files for the phones. The tool must store the configurations in editable form. The configuration files are ultimately placed on the TFTP Server for download by the phones. DHCP Servers Each LAN or VLAN must have its own DHCP server. The DHCP servers

provide at a minimum, an IP address, DNS server addresses and the TFTP Server address to each phone as it powers up. In addition, DHCP may provide a voice VLAN id (DHCP Option 132) and DSCP (DHCP Option 133) and TOS values for voice traffic (DHCP Option 134). (*Support for the DHCP Options is not available in the TeleMatrix SIP phones at this time.*)

Tasks

The main tasks carried out by the users are the source of the requirements for the system. Configuration Creation

Using a representative SIP phone (3300IP/9600IP), the Administrator creates a

configuration for the phones. The phone configuration must be created in concert with the IPBX configuration because IDs in the phone and IPBX configurations associate a phone with an extension in the IPBX.

The phone configuration file is essentially a database of information describing the configuration. When the configuration is complete, the Administrator can use the Mass Configuration Utility (MCU) to write the multiple configuration files for all or a selection of phones to be loaded on the TFTP server.

The MCU must generate a ConfigID for each phone configured. The configuration files written to the TFTP Server will be named <ConfigID>.<phone type>.txt. (xxxx.3300ip.txt) The ConfigID will be constructed from the room number and building.

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.

Phone Replacement

When replacing a phone with a new, unconfigured phone, the procedure is the same as for initial installation. An Installer can reset the replacement phone to factory defaults and then proceed as in a new installation.

1. When replacing a phone with one that has been used previously the phone will not prompt for the ConfigID. Once configured, a phone will have a password in place. When the replacement phone is put in place and powered up, the Installer must enter a password and may then set the new ConfigID into the phone. It then loads the new configuration file and resets, coming up under the new configuration. The Installer then verifies that the phone is up and working in the correct extension..

Configuration Files

Different phone models may require different formats in their configuration files. For that reason, two or more configuration files may be generated for a given phone, if two different models might be used in that location. A model designation must be part of the

configuration file name. (Example: 3300IP phones have configuration files of 3300IP.txt,

9600IP phones have 9600IP.txt, etc)

Using the Mass Configuration Tool

The purpose of the TeleMatrix Mass Configuration Utility is to allow the installer to program a single phone to work within the network and then create multiple files (a unique one for each phoneset). After you have created the first known good working phone config file, others are made by copying and substituting the values that need to be changed into other unique config files.

Saving a Template Configuration file

After thoroughly configuring a phone to work satisfactorily, it is time to save it and use it for creating multiple files (one for each phone endpoint).

In the Web UI of your known good sample phone, go to Config Manage. - Select "Right Click Here to Save As Config File (.txt). Select a directory and save

Building Configuration Files

The following information is required for the process of building multiple configuration files: 1. The complete numbering plan for the phones to be installed.

What are the building numbers if more than one? What are the floor numbers?

What are the room numbers?

Are the rooms differentiated? (For example, suites vs. standard rooms. How many phones are in each type of room? What is the extension number of each phone in each room?)

2. There are two SIP lines on each phone. How should each be configured, given the extension number?

3. What should the IP address settings be? We can set the phones to a static IP address that will correlate easily with the extension or room number. This will make future maintenance easier. IP address can be left empty and DHCP used, of course.

4. The items above will all be different on each phone. The items below will probably be constant. If they are not, that may necessitate more than one configuration template. If that is so, please make it clear.

5. What are the gateway address and DNS addresses? These might be handled by DHCP? 6. What is the SIP Registrar address and port? Is there a SIP Proxy? (unlikely)

7. Is the phone on a tagged VLAN? If so, what is the VLAN ID and priority? What should the DSCP setting be for voice packets?

8. What is the address of the TFTP server in the system? Using the TFTP server on the Mitel 3300ICP is a known, working and available way to go if installing on a Mitel controller.

9. What dial termination rules are appropriate? Something like this is probably needed: Item1 rule :0

Item2 rule :[1-8]xxx Item3 rule :911 Item4 rule :9911

Item5 rule :91xxxxxxxxxx

10. What should the MWI number be set to? 11. What should the 10 softkeys be set to?

Once these things are known, a template can be produced and reproduced for each phone. They are then loaded onto the phone via the process below.

The Mass Configuration Utility is available for TeleMatrix partners, as a tool to facilitate building their own multiple config files. If you have a mass configuration subscription agreement on file with TeleMatrix, you may send your template to [email protected] and have the files built for you.

IMPORTANT: When manually creating any new configuration file, the file version (top line of config file) must be incremented.

Example: <<VOIP CONFIG FILE>>Version:2.0003 must become

Loading Configuration Files

6. Attach POE (Power Over Ethernet) to the 3300IP or 9600IP WAN port

7. Connect an Ethernet cable from the phone’s LAN port to a computer with a web browser 8. Open a web browser and point it to http://192.168.10.1 (default IP address for 3300IP) 9. Alternatively, if it has acquired a new IP address from the network find that IP with * * 4 7 # 10. Type is username admin and password admin

At the bottom of the screen is Update Configuration Click on the Browse button to select a configuration file to load onto the phone. Configuration files are .txt files. They can be named anything, but generally follow the naming convention of room#.phonemodel#.txt

Eg: 1041.3300ip.txt

Select the file you want to load for that phone: In this case we are loading extension

1041.3300ip.txt indicating that extension 1041s configuration will load on to a 3300IP model phone.

After 20 seconds or so, the phone will be rebooted: at this time you can refresh your screen by reloading the web URL. Log back into the phone (192.168.10.1 admin / admin) to check that your update was successful. The default page is Current Status you can check that the SIP Line 1 is indeed updated to the correct extension at the correct server. [email protected]