Professional Documents
Culture Documents
sipsupport@telematrix.net
Page 1
www.telematrix.net
About this document This How-To-Guide is intended for Customer Service and Technical Installation Personnel involved in the installation and maintenance of TeleMatrix SIP Endpoints.
sipsupport@telematrix.net
Page 2
www.telematrix.net
Table of Contents Overview .............................................................................................................................................5 Software & Hardware Setup .......................................................................................................5 Device Limitations ..........................................................................................................................5 Mitel 3300ICP Setup Notes..........................................................................................................6
Network Requirements ..................................................................................................................6 Assumptions for the 3300 ICP programming ..............................................................................6 Licensing and Option Selection - SIP Licensing.........................................................................7 Multiline IP Set Configuration .......................................................................................................8 Class of Service Assignment ........................................................................................................9 SIP Device Capabilities Assignment ..........................................................................................11 Station Service Assignment ........................................................................................................12 Multiline Set Key Assignment .....................................................................................................13
sipsupport@telematrix.net
Page 3
www.telematrix.net
sipsupport@telematrix.net
Page 4
www.telematrix.net
Overview
The first section of this document provides a reference for configuring the Mitel 3300 ICP to host the Telematrix single line corded 3300IP and/or cordless 9600IP-DECT SIP phone endpoints. The different devices can be configured in various configurations depending on your VoIP solution. This document covers a basic setup with required option setup.
Variant 3300 ICP MXe platform 9600IP Single Line DECT/Cordless SIP Phone 3300IP Single Line Corded SIP Phone
Device Limitations
This is a list of problems or not supported features when the Telematrix 3300IP phone is connected to the Mitel 3300.
Problem Description Unable to transfer calls using device based setup (Supervised or Unsupervised) 9600IP non-Display phone Busy Signal is delayed for approximately 10 seconds.
sipsupport@telematrix.net
Page 5
www.telematrix.net
Network Requirements
There must be adequate bandwidth to support the voice over IP. As a guide, the Ethernet bandwidth is approx 85 Kb/s per G.711 voice session and 29 Kb/s per G.729 voice session (assumes 20ms packetization). As an example, for 20 simultaneous SIP sessions, the Ethernet bandwidth consumption will be approx 1.7 Mb/s for G.711 and 0.6Mb/s. Almost all Enterprise LAN networks can support this level of traffic without any special engineering. Please refer to the 3300 Engineering guidelines for further information. For high quality voice, the network connectivity must support a voice-quality grade of service (packet loss <1%, jitter < 30ms, one-way delay < 80ms).
sipsupport@telematrix.net
Page 6
www.telematrix.net
sipsupport@telematrix.net
Page 7
www.telematrix.net
sipsupport@telematrix.net
Page 8
www.telematrix.net
sipsupport@telematrix.net
Page 9
www.telematrix.net
sipsupport@telematrix.net
Page 10
www.telematrix.net
Figure 5 SIP Device Capabilities Assignment Features work with Device Based or System Based, but we recommend System Based to allow for use of Feature Access Codes and greater flexibility.
sipsupport@telematrix.net
Page 11
www.telematrix.net
sipsupport@telematrix.net
Page 12
www.telematrix.net
sipsupport@telematrix.net
Page 13
www.telematrix.net
sipsupport@telematrix.net
Page 14
www.telematrix.net
Enable/Disable Device Based call features by going Advance > Call Service or SIPConfiguration > Advanced Set
If all settings are correct you will see register status Registered and you can begin to make calls.
sipsupport@telematrix.net
Page 15
www.telematrix.net
The scope of this document is to provide the basic screenshots necessary to quickly configure the guest phone for basic registration and show the user where to program voicemail retrieval keys and speed dials. Our example 9600IP phone is programmed as extension 1234 The VoIP -> SIP Configuration Screen
Server address of the IP/PBX, extension number/account name, phone number and display name, enable register and enable message waiting indication are all programmed here.
sipsupport@telematrix.net
Page 16
www.telematrix.net
The Network WAN/LAN ports may be configured for DHCP or Static Network -> WAN Config:
If used as a lobby phone, program ring-down to a specific number with the hotline field.
Advance -> Call Service Setting menu
Speed dial and Touchlite Message Retrieval keys are programmed in Advance -> Memory Key
sipsupport@telematrix.net
Page 17
www.telematrix.net
MWI Number is the field for programming the Red Message Waiting Touchlite. In this example, it is programmed to dial number (7001) on the IP/PBX for retrieving voicemail messages.
sipsupport@telematrix.net
Page 18
www.telematrix.net
Quality of Service and VLAN Tagging are found under Advance -> QOS
Below is a valid example of setting a Voice VLAN of 302 and a data VLAN of 301
sipsupport@telematrix.net
Page 19
www.telematrix.net
Changing the default LAN IP Address of 192.168.10.1 is possible under Network -> LAN Config In order to enable VLAN, you must enable Bridge and disable NAT and DHCP Service as below:
This setting wont take effect unless you save the config and reboot the device
sipsupport@telematrix.net
Page 20
www.telematrix.net
Manual Programming - Submerged Keys and programming the Phone from the LCD
There are 2 submerged keys (above the 10 speed dial keys/underneath the faceplate). The left (store) key is used to store speed dials as well as enter the internal menu to check status and program the phone. 1. Speed Dial: To program a speed dial, Press the store keypress a speed dial keythen press the digits you want stored there. 2. Internal Menu: To enter the phones internal menu, hold down the left (store) key for three seconds. At that time, you will be prompted to enter the password (default password = 123) then press the other key (right key = flash) to enter the LCD navigation menu.
Vol up key navigates up Vol Down key navigates down Right/Flash key is Enter Left/Store key is Escape (back out of that menu option) Redial Key is for changing values The * (asterisk) is used as a .(dot) for IP address entry (eg: press 72* to get 72. when entering IP address)
To determine the IP address assigned to the phone, Navigate to Config -> Network -> WAN -> Status using the keys and process outlined above.
3300ICP Notes
If there are no telephone directory assignments for the extension, then extension displays twice when you call it. If you do not hear Music On Hold (on a 3300ICP) you may need to change a setting in the SIP Devices Capability Assignment Select Prevent the Use of IP Address 0.0.0.0 in SDP Messages to YES
sipsupport@telematrix.net
Page 21
www.telematrix.net
Configuring VLANs
Because there is no LCD display, and the phone has the capability to act as a switch, receiving IP addresses on the WAN port and serving IP addresses on the LAN port, there are some quirks to the 9600ip interface that make it difficult to set the QOS parameters (VLAN ID.) The VLAN cannot be set unless the phones LAN interface is in Bridge Mode. The procedures below should always allow you configure the phone correctly. The Phones factory defaults set the WAN interface to DHCP and the LAN interface to Bridge Mode with NAT and DHCP Service ON. (These last two should be OFF when Bridge Mode is ON.) Assumptions: Phone should be in WAN DHCP mode on VLAN 30 with priority 6.
Configuring the Phone via web interface with a Prepared Configuration File
Connect the phone to a port where it will have a DHCP server available. Connect your PC to a port that is on the same network (LAN or VLAN) as the phone. The phone should have a DHCP address. Find the IP address of the phone. Browse and login to the phone via web UI. Go to Config Manage. Hit the Browse button under Update Configuration. Select the prepared Configuration File on your PC. Hit the update button. The UI will no longer be active, as the phone resets. The phone will reset and come up under the new configuration. Since the new configuration may have a VLAN ID enabled, the phone must be connected to a port where the VLAN is supported or it will not come up and connect to the server. In the configuration file, these (<----) are the settings addressed below in the directions for configuration through the UI. <LAN CONFIG MODULE> Lan Ip :192.168.10.1 Lan NetMask :255.255.255.0 Bridge Mode :1 <---<DHCP CONFIG MODULE> Enable DHCP Server :0 <----
sipsupport@telematrix.net
Page 22
www.telematrix.net
Enable DNS Relay :1 DHCP Update Flag :0 TFTP Server :0.0.0.0 <NAT CONFIG MODULE> Enable Nat :0 <---Enable Ftp ALG :1 Enable H323 ALG :0 Enable PPTP ALG :1 Enable IPSec ALG :1 <QOS CONFIG MODULE> Enable VLAN :1 Enable diffServ :1 DiffServ Value :46 VLAN ID :30 802.1P Value :6 VLAN Recv Check :0 Data VLAN ID :254 Data 802.1P Value :0 Diff Data Voice :0 <---<---<---<---<---<---<----
sipsupport@telematrix.net
Page 23
www.telematrix.net
Quality of Service and VLAN Tagging are found under Advance -> QOS
Below is a valid example of setting a Voice VLAN of 302 and a data VLAN of 301
sipsupport@telematrix.net
Page 24
www.telematrix.net
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. IMPORTANT: When creating any new configuration file, the file version (top line of config file) must be incremented. Ex: <<VOIP CONFIG FILE>>Version:2.0003 must become <<VOIP CONFIG FILE>>Version:2.0004
sipsupport@telematrix.net
Page 26
www.telematrix.net
Next Navigate to, and select the Config Manage tab on the left
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
sipsupport@telematrix.net
Page 27
www.telematrix.net
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.
Press Update buttonthe phone will load the new file and reboot
sipsupport@telematrix.net
Page 28
www.telematrix.net
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. 1041@10.62.1.2
The TeleMatrix SIP phone sets support configuration file downloads via DHCP Option 66 in Firmware version th V1.7.219.232 (November 8, 2008) and later (Sept 5 code DOES NOT). The files have a naming convention of 1234.3300ip.txt (1234 being the varying DN/Extension number of each individual phone. The 3300ip.txt naming convention is used for both the 3300IP and 9600IP phones. When creating a new configuration file, the file version (top line of config file) must be incremented. Ex: <<VOIP CONFIG FILE>>Version:2.0003 must become <<VOIP CONFIG FILE>>Version:2.0004 When the phone Boots up, phones with a display will ask for a Config ID. Using the example of 1234.3300ip.txt, the installer would press the following keys: 1234# At that point, the phone will retrieve the configuration file from the tftp server IP address (as specified in the 3300ICP ESM form DHCP Options). The phone will then reboot with a new configuration. IP Address of phone is verbally read out 29 **47# sipsupport@telematrix.net Page when the user presses the keys www.telematrix.net
Administrator
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. The TFTP Server will hold the configuration files for the phones. It is addressed via IP.
TFTP Server
sipsupport@telematrix.net
Page 30
www.telematrix.net
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. 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. 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.
Room
Network
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.
sipsupport@telematrix.net
Page 31
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 roomtemplate 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.
sipsupport@telematrix.net
Page 32
www.telematrix.net
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)
sipsupport@telematrix.net
Page 33
www.telematrix.net
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 sipsupport@telematrixusa.com 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 <<VOIP CONFIG FILE>>Version:2.0004
sipsupport@telematrix.net
Page 34
www.telematrix.net
Next Navigate to, and select the Config Manage tab on the left
sipsupport@telematrix.net
Page 35
www.telematrix.net
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.
Press the Update buttonthe phone will load the new file and reboot
sipsupport@telematrix.net
Page 36
www.telematrix.net
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. 1041@10.62.1.2
Implementing the TFTP server resident in the Mitel 3300ICP allows that:
1. Phones can be setup simply from the room with a series of key presses. 2. Example placing/powering the phone and pressing 1234# will cause the phone to retrieve 1234.3300ip.txt, which in this example is the phones config file. 3. Phones can receive firmware upgrades periodically when new features are added or bugs are detected and fixed
sipsupport@telematrix.net
Page 37
www.telematrix.net
4. Hotel staff can easily replace a defective phone simply by following the steps
referenced above in 1 a. The alternative is to manually upgrade the TeleMatrix SIP phonesets by logging into each phones web user interface (UI) browse to the web interface of the phone and manually upgrade through the System -> Upgrade Create a new configuration file for the phone with the following mini-config added to the already existing phone configuration. This new configuration would then reside on the local tftp server, along with the firmware file used for the upgrade. This will work on phones with firmware supporting DHCP Option 66, dated 30 October 2008 and later.
<AUTOUPDATE CONFIG MODULE> Auto Image Server :192.168.0.50 (Replace with your TFTP server where the phone configuration files are placed) Auto Image Name :21b4V1_7_237_235T20081206001533.z - (The new firmware file will have a name like this) Auto Image User : Auto Image Password: Auto Image Protocol:2 Download Username :user Download password :pass Download Server IP :0.0.0.0 Config File Name :1234.3300IP.txt - (Extension 1234 in this example) Config File Key : Download Protocol :1 Download Mode :0 Download Interval :1
In a Mitel 3300ICP environment the TFTP Server is a folder/subdirectory best reached by using FTP into the 3300ICPs IP address. At that point place the IP Phones configuration files into the tftp subdirectory. Step 1 - Implement the Mitel 3300ICP TFTP server scenario described below: Step 2 Configure the Mitel 3300ICP and place files on its native TFTP server. Step 3 - As new firmware and configuration files are deemed necessary, replace the TeleMatrix IP Phone config files again with an incremented version (2.0003 becomes 2.0004) and a config module specifying the new firmware file is added. Use the TeleMatrix Mass Configuration Tool to create multiple files Step 4 - Cycle the power on phones one at a time OR cycle the power on the POE forcing all the phones to reboot if that is ever deemed a safe option. Result: The 3300IP or 9600IP phones will boot, grab their same expected config file ( example: 1234.3300ip.txt), but this time they will download new firmware, reboot again and be upgraded AND continue working as before. This was tested and should work as long as the phone can truly reach and download via tftp.
sipsupport@telematrix.net
Page 38
www.telematrix.net
sipsupport@telematrix.net
Page 39
www.telematrix.net
Step 2 Configure the Mitel 3300ICP and place files on its native TFTP server.
Specify the tftp server name in the Mitel 3300ICP controller. This is done under DHCP Options
sipsupport@telematrix.net
Page 40
www.telematrix.net
sipsupport@telematrix.net
Page 41
www.telematrix.net
Using Microsoft IE, type in your Mitel 3300ICP controllers IP address in to the browser: Eg ftp://10.20.0.2
sipsupport@telematrix.net
Page 42
www.telematrix.net
After the challenge, you will arrive at the root of the FTP server
sipsupport@telematrix.net
Page 43
www.telematrix.net
You will want to view the files on the controller with Windows Explorer View -> Open FTP Site in Windows Explorer
Now you can see the hidden directories: The tftp subdirectory is heredoubleclick to enter.
sipsupport@telematrix.net
Page 44
www.telematrix.net
Open a second window of Windows Explorer and browse to where you have the Configuration files for the TeleMatrix IP Phones. Select the config files and drag and drop into the tftp directory
sipsupport@telematrix.net
Page 45
www.telematrix.net
Step 3 - As new firmware and configuration files are deemed necessary, replace the TeleMatrix IP
Phone config files again with an incremented version (2.0003 becomes 2.0004) and a config module specifying the new firmware file is added. Use the TeleMatrix Mass Configuration Tool to create multiple files
Step 4 - Cycle the power on phones one at a time OR cycle the power on the POE forcing all the phones to reboot if that is ever deemed a safe option.
Result: The 3300IP or 9600IP phones will boot, grab their same expected config file ( example: 1234.3300ip.txt), but this time they will download new firmware, reboot again and be upgraded AND continue working as before. This was tested and should work as long as the phone can truly reach and download via tftp.
sipsupport@telematrix.net
Page 46
www.telematrix.net
In the boot-up process the TeleMatrix SIP phones can receive information (via DHCP Option 66) telling the phone where the TFTP server is (in the form of an IP address) 1. Download and Install TFTPD32 - http://tftpd32.jounin.net/tftpd32.html 2. Setup local network on the PC running TFTPD32
sipsupport@telematrix.net
Page 47
www.telematrix.net
Additional Option is set to 66the IP address to its right is the TFTP serverin this case 192.168.10.1the same machine running the server.
4. Select the folder where the TFTP server will pull files from
5. Place all the config files xxx.3300ip.txt and/or the firmware file in the specified directory (in this case C:\Program Files\Tftpd32)
6. That should be all the setup needed for the PC running the TFTP server. 7. The next step is to plug a phone into a POE switch connected to the PC wait for the Config ID challenge, then input the configID followed by #. The phone will then grab the corresponding file off the TFTP server (the file must be located in the TFTP serving folder. Example: 1234.3300ip.txt will be the configuration file downloaded when you input 1 2 3 4 # at the Config Id challenge.
Updating Firmware
If you are only updating firmware, the following <AUTOUPDATE CONFIG MODULE> is a template for a small configuration file specifically to update firmware. This can be used standalone, or can be added to the phones complete configuration file. <<VOIP CONFIG FILE>>Version:2.0004
sipsupport@telematrix.net Page 48
<AUTOUPDATE CONFIG MODULE> Auto Image Server :192.168.10.25 (Your TFTP server where the phone configuration files
are placed)
Auto Image Name : 3300SIP-1.8.0-513.z - (The new firmware file name.) Auto Image User : (tftp does not use authentication, but ftp and http do) Auto Image Password: Auto Image Protocol:2 <AUTOUPDATE CONFIG MODULE> Download Username :user Download password :pass Download Server IP :0.0.0.0 Config File Name : (When this is blank, display phones will prompt for ConfigID and
non-display phones will prmpt audibly with Doodle Doodle tone When it is occupied with a filename like 1234.3300ip.txt the phone will check that file for configuration information.)
Config File Key : Download Protocol :1 (0 = ftp, 1 = tftp, 2 = http) Download Mode :0 Download Interval :1 <<END OF FILE>>
You could save this as a text file (such as 3.3300ip.txt) and upgrade the phones firmware by typing in 3 # (to retrieve 3.3300ip.txt) when the phone boots up and requests a Config Id. (Display phones display Config Id, but display-less phones such as the 9600IP-DECT prompt with a series of tones sounding like doodle-doodle.
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
<<VOIP CONFIG FILE>>Version:2.0004
sipsupport@telematrix.net
Page 49
www.telematrix.net
2. Put the 3.3300ip.txt (Autupdate Config Module) on the tftp server (DHCP Option 66 on Guest VLAN AND Voice VLAN must specify the tftp server referenced in Auto Image Server.)
3. Factory Reset on the phone (# at power up, count to three then * # 1 6 8 then cycle power again) (This will reset your phone with a blank config file of Version Number 2.0001) 4. At Config ID Prompt (Doodle Doodle) pres 3 # to download autoupdate image config file (3.3300ip.txt) 5. After phone downloads and reboots you will be challenged for Config ID (doodle doodle) again 6. Enter the original config ID # for the room to restore the original values (This Version Number of config file should be higher than the Version Number 2.0004 now on the phone because of 3.3300ip.txt ) This process assumes that the phones can still reach a single TFTP server from both the
sipsupport@telematrix.net
Page 50
www.telematrix.net
The scope of this document is to provide the basic screenshots necessary to quickly configure the guest phone for basic registration and show the user where to program voicemail retrieval keys and speed dials. Our example 3300IP phone is programmed as extension 1234 Program your connection under the VoIP -> SIP Configuration Screen
Server address of the IP/PBX, extension number/account name, phone number and display name, enable register and enable message waiting indication are all programmed here.
sipsupport@telematrix.net
Page 51
www.telematrix.net
Speed dial and Touchlite Message keys are programmed under Advance -> Memory Key
MWI Number is the field for programming the Red Message Waiting Indicator Touchlite. In this example, it is programmed to dial number (7001) on the IP/PBX for retrieving voicemail messages.
Manual Programming - Programming the 3300IP via the LCD and Submerged Keys There are 2 submerged keys (above the 10 speed dial keys/underneath the faceplate). The left (store) key is used to store speed dials as well as enter the internal menu to check status and program the phone. 1. Speed Dial: To program a speed dial, Press the store key press the digits you want stored press a speed dial key. 2. Internal Menu: To enter the phones internal menu, hold down the left (store) key for three seconds. At that time, you will be prompted to enter the password (default password = 123) then press the other key (right key = flash) to enter the LCD navigation menu. Vol up key navigates up Vol Down key navigates down Right/Flash key is Enter/Select Left/Store key is Escape (back out of that menu option) To determine the IP address assigned to the phone, Navigate to Config -> Network -> WAN -> Status using the keys and process outlined above. Reset to Factory Default To reset the phone to the factory default settings, press # during the startup procedure (At power up you can see a black progress bar). The phone will enter into post mode, then input * # 1 6 8 Then you will see clearing conf on the screen, next you see conf reset. Now you have reset to the default settings. Finally, cycle power (remove and replace WAN power cable) to restart the phone with factory default settings.
sipsupport@telematrix.net
Page 52
www.telematrix.net
sipsupport@telematrix.net
Page 53
www.telematrix.net
sipsupport@telematrix.net
Page 54
www.telematrix.net
sipsupport@telematrix.net
Page 55
www.telematrix.net