Aastra 6700i Series User manual

INSTALLATION INSTRUCTIONS
INSTALLATION INSTRUCTIONS26/1531-ANF 901 14E1020140122
Aastra 6700i SIP Terminals for
MX-ONE
AmilerAmilerArne Mileramiler

AASTRA 6700ISIP TERMINALS FOR MX-ONE
2 26/1531-ANF 901 14 Uen E10 2014-01-22
Copyright
© Copyright Aastra Technologies Limited, 2014. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the
written permission of the copyright owner.
The contents of this document are subject to revision without notice due
to continued progress in methodology, design and manufacturing.
Aastrashallhavenoliabilityforanyerrorordamageofanykindresulting
from the use of this document.

26/1531-ANF 901 14 Uen E10 2014-01-22 3
GENERAL
1 General
This document is valid for Aastra 6730i, 6731i, 6735i, 6737i, 6739i,
6753i, 6755i and 6757i SIP phones, when installing these telephones in
a MX-ONE environment.
1.1 Scope
This document describes how to install and configure for the Aastra
6700i terminals in a MX-ONE Telephony Server (TSE) environment. For
general installation information that is not unique for a MX-ONE environ-
ment, there is a reference to the Administrator Guide for Aastra Models
6700i and 9000i Series IP SIP Phones.
There is also one platform independent installation guide per telephone
model available on www.aastra.com.
1.2 Glossary
Some expressions in this document follows the expressions used in
MX-ONE, which can differ from the expressions used in the Adminis-
trator Guide for Aastra Models 6700i and 9000i Series IP SIP Phones.
Table 1 Expressions used in MX-ONE and in 6700i documents
MX-ONE
Administrator Guide for Aastra
Models 6700i and 9000i Series IP
SIP Phones
Software server Configuration server
Shortcut keys Programmable keys and Softkeys
TNS (Telephony Name
Selection) Speed dial
MNS (Monitored extensions) BLF (Busy Lamp Field)
Settings key Options key
Key Panel Unit (KPU) and
Display Panel Unit (DPU) Expansion Module

AASTRA 6700ISIP TERMINALS FOR MX-ONE
4 26/1531-ANF 901 14 Uen E10 2014-01-22
1.3 Environmental Requirements
See Administrator Guide for Aastra Models 6700i and 9000i Series IP
SIP Phones.

26/1531-ANF 901 14 Uen E10 2014-01-22 5
CABLING
2 Cabling
See Administrator Guide for Aastra Models 6700i and 9000i Series IP
SIP Phones.

AASTRA 6700ISIP TERMINALS FOR MX-ONE
6 26/1531-ANF 901 14 Uen E10 2014-01-22
3 Power Equipment
These telephones can be powered from any of the following methods:
• 6730i is powered from an AC adapter 5V. No PoE support.
• 6731i, 6735i, 6737i, 6739i, 6753i, 6755i, 6757i are powered using
PoE according to IEEE 802.3af or from an AC/DC adapter 48 V.
• Power over Ethernet power injector, which supplies 48 V power
through the Ethernet cable on pins 4&5 and 7&8. The power
injector is available as an optional accessory.
Table 2 Power classes for the different phone models
*) Maximum one expansion module with PoE. Up to three modules with
AC/AC adapter.
**) Single call established in handset mode, backlight on. No PC
connected.
Explanation of power classes:
• 0 - classification is not implemented.
• 1 - less than 3.84 W.
• 2 - less than 6.49 W.
Device Power Consumption **) Power Class
6730i 2.4 W not applicable
6731i 2.4 W 1
6735i 2.8 W 2 *) from REV:29
6737i 2.9 W 2 *) from REV:30
6739i 4.8 W 0
6753i 3.3 W 0
6755i 4.0 W 0
6757i 4.1 W 0

26/1531-ANF 901 14 Uen E10 2014-01-22 7
EARTHING AND GROUNDING
4 Earthing and Grounding
See Administrator Guide for Aastra Models 6700i and 9000i Series IP
SIP Phones.

AASTRA 6700ISIP TERMINALS FOR MX-ONE
8 26/1531-ANF 901 14 Uen E10 2014-01-22
5 Setting up the Software Server
The software and the configuration files used by the IP phones shall be
stored on a server where the IP phones can fetch them. The server is
called IP Phone SW Server.
Figure 1: Deployment Scenario when telephony domains use different
SW servers
IntheTelephonyServeryou can definemultipletelephonydomains.The
telephony domains are managed through the Manager Telephony
System web interface.
The IP phone configuration files are preferably generated through the
Manager Telephony System (MTS). To enable the files to be generated
through Manager Telephony System, the IP Phone SW Server Configu-
ration Management Application must be installed on the IP Phone SW
Server.Oncegeneratedthe configurationfilescanvieweddirectly onthe
IP Phone SW Server.
The IP phones can use the following protocols to download the software
and configuration file(s): http, https, ftp, tftp. The recommendation is to
use the http protocol and it is described in these installation instructions.
IfMTS for some reason isnot used, stop reading and go to chapter“How
to start a new phone”.
Setting up the software server comprises the following steps:
• Installing the IP Phone SW Server Configuration Management
Application.
Telephony
Server
IP Phone
SW Server
Manager Telephony System
IP Phone
SW Server
Telephony Domain A
Telephony Domain B IP Phone SW Server
Application installed

26/1531-ANF 901 14 Uen E10 2014-01-22 9
SETTING UP THE SOFTWARE SERVER
• Reconfigure Microsoft IIS web server, if it exists.
• Creating a directory structure on the IP Phone SW Server.
• Copy the IP phone application and language files to the IP Phone
SW Server. The configuration files shall not be copied, these are
created by MTS. For information about the files, see section 8.1
Phone software and configuration files on the software server on
page 24.
5.1 Install IP Phone SW Server
Before the installation of the IP Phone SW Server you have to install the
Java Runtime Enviroment. When you run IP Phone SW Server wizard
the Tomcat is also installed.
Note: For more information see the IP Phone SW Server release notes
for additional installation information. See also section 8.1 Phone soft-
ware and configuration files on the software server on page 24 on how
to manage the SW in the IP phone.
5.1.1 System and program requirements
• Java Runtime Enviroment (JRE) version 6 (32- bit) or later.
• Windows 32 bit or 64 bit.
• Tomcat version 7.0.33 (apache-tomcat-7.033-windows x86.zip), is
installed via the wizard.
5.1.2 Prerequisites
• Check if Java Runtime Enviroment version 6 or later, is installed. If
not, installed JRE before you start the IP Phone SW Server wizard.
• If IP Phone Server (version 1.4 or prior) is installed, uninstalled the
the program before you start the wizard.
5.1.3 Install IP Phone SW Server (and Tomcat)
Do as follows:
1. Download and click Setup.exe, . The window
Installer Language is displayed.
2. Select Language from the list.

AASTRA 6700ISIP TERMINALS FOR MX-ONE
10 26/1531-ANF 901 14 Uen E10 2014-01-22
3. Click OK. The window Welcome to the IPPhone SW Server
Setup Wizard is displayed.
4. Click Next. The step Licence Agreement is displayed.
5. Click Agree. The step Tomcat Port Number is displayed.
6. Type the port number in the field, default port is 80.
7. Click Next. The step Tomcat Administrator is displayed.
8. Click Next.
9. The message window, Do you want to continue without config-
uring a Tomcat administrator? is displayed.
10. Click Yes. The step Choose Install Location is displayed.
11. Click Install. When the installation is complete you will get a
message, Installation Complete.
12. Click Next. The step Completing the IPPhone SW Server Setup
Wizard is displayed.
13. Click Finish.
5.2 Co-existence with Microsoft IIS Web Server
If a Windows IIS web server is running on the IP Phone SW Server there
will be a port conflict with the IP Phone SW Server Configuration
Management Application since they are both using port 80. This is typi-
cally the case when CMG or OneBox are installed on the same server.

26/1531-ANF 901 14 Uen E10 2014-01-22 11
SETTING UP THE SOFTWARE SERVER
The reason that you need to have the Tomcat web server running
instead of just using the IIS web server is that the IP Phone SW Server
ConfigurationManagement Application isdeveloped in Java and IIS can
only host web applications developed in the Microsoft environment.
Perform the following steps to resolve the port conflict.
• Keep IIS running on port 80.
• Reconfigure the IP Phone Configuration Management Application
to run on port 82 instead.
– Edit the jakarta-tomcat-4.1.31\conf\server.xml (where
-4.1.31 is an example) and change the port 80 to 82.
– Restart Tomcat by going to
Control Panel/Administrative Tools/Services
Restart the service Jakarta Tomcat 4.
• Connect MTS to IP Phone SW Server Configuration Management
Application on port 82, using the MTS task IP Phone SW Server.
• Createthe configuration file intheMTStaskIPPhone configuration
File and it will be stores on the IP Phone SW Server, see section
6.1 Create a Configuration File on page 15 for details.
• The .cfg, .st, .txt and .tuz file types must be enabled. Follow the
steps below to enable these file types:
–InIIS Manager, select File Type, select DefaultWEB Site.
– Select Properties and edit HTTP header. Apply the following
settings:
–Associated extension: .cfg,.st, .txt and .tuz (encrypted .cfg
file)
–Content type (MIME): application/octet-stream.
• Redirect IIS web server to Tomcat web server for the IP phone’s
requests like this:

AASTRA 6700ISIP TERMINALS FOR MX-ONE
12 26/1531-ANF 901 14 Uen E10 2014-01-22
– Open C:\WINDOWS\system32\inetsrv\inetmgr.exe, navigate
to Default Web Site.
– Right click on Default Web Site and select New Virtual Direc-
tory. A wizard will start.
– Enter the directory name to where the telephone firmware
shall be stored as Alias, example: aastra67xxi.
– Enter the path to the folder under Tomcat, example:
C:\jakarta-tomcat-4.1.31\webapps\ROOT\aastra67xxi.
– Enable the Read option and finish the wizard.
– You can now access the Tomcat folder with terminal settings
on both port 80 as well as 82, while MTS can update the
configuration file on port 82.
– If subnets or telephony domains are defined for the configura-
tion file in MTS, the path under Tomcat will include the
subnet/telephony domain in its path. Update the IIS virtual
directory link accordingly.

26/1531-ANF 901 14 Uen E10 2014-01-22 13
SETTING UP THE SOFTWARE SERVER
5.3 Start of the Tomcat Web Server
During the installation of IP Phone SW Server Configuration Manage-
ment Application for Windows®, Tomcat will start automatically on port
80.Incase Tomcatisnotup and running, it can be startedmanuallywith
Windows® Services Jakarta Tomcat 4 (see instruction below) or by
restarting the Tomcat web server PC.
If the Tomcat web server starts on another port number than 80, the port
number can be set manually in the file
jakarta-tomcat-4.1.31\conf\server.xml(where-4.1.31isan example).
5.3.1 Verify that the Apache Tomcat server is running
Use the following procedure on the server PC:
1. Go to Control Panel/ Administrative Tools/
Services
Check that the service Jakarta Tomcat 4 has status started. If the
service has not been automatically started, then start it manually.
2. Start a web browser for example Internet Explorer and enter the
address http://localhost. The Apache Tomcat web page
server is shown.
3. Enter the address http://localhost/ipfmsBinary in the
web browser.
The Axis web page is shown.

AASTRA 6700ISIP TERMINALS FOR MX-ONE
14 26/1531-ANF 901 14 Uen E10 2014-01-22
6 ManagetheConfigurationFilesin
Manager Telephony System
MX-ONE Manager Telephony System (MTS) shall be used when
creating or changing the aastra.cfg and the model specific configuration
files.Theinformationregarding parametersisavailableinthe onlinehelp
for MX-ONE Manager Telephony System. The picture below shows an
example of the page in the IP Phone Configuration File task in MTS:
Figure 2: IP Phone Configuration File in Manager Telephony System
Note: MTS requires that the IP Phone SW Server Configuration
ManagementApplication is installed on the IP Phone SW Server,
please see section 5 Setting up the Software Server on page 8

26/1531-ANF 901 14 Uen E10 2014-01-22 15
MANAGE THE CONFIGURATION FILES IN MANAGER TELEPHONY SYSTEM
6.1 Create a Configuration File
The procedure to create a new configuration file is:
• Log in to MX-ONE Manager Telephony System.
•GotoTelephony > IP Phone > Configuration file. Press Add
new to open the new configuration file.
Make sure that Aastra 67xxi family is selected and enter the data
into the configuration file which is automatically stored under the
correct directory in the IP Phone Software Server when pressing
Apply.
• To force the telephones to fetch the new configuration file there are
a number of cases:
– If the telephones are not started yet: connect the power and
the telephones will fetch the new configuration file.
– If the telephones are already registered to the PBX, select the
Unregistration option to force the telephones to fetch the
new configuration file.
– The telephones will after less than 24 hours automatically
fetch the new configuration file and if necessary download a
new firmware.
– Restart the telephones manually.
6.2 Changing an Existing Configuration File
The existing configuration file can be updated using the MX-ONE
Manager Telephony System.
The following procedure shall be used when the configuration file shall
be changed:
1. Log in to MX-ONE Manager Telephony System and select:
Telephony > IP Phone > Configuration file
2. Takeabackupcopyoftheexistingconfigurationfilebypressingthe
backup icon.
3. Use the Change icon to view the configuration file. When the adap-
tation of the file is completed, it is automatically stored under the
aastra67xxi directory in the IP Phone Software Server.
4. For the telephones that are already registered to the PBX, select
the Unregistration option to force the telephones to fetch the new

AASTRA 6700ISIP TERMINALS FOR MX-ONE
16 26/1531-ANF 901 14 Uen E10 2014-01-22
configurationfile.Forthenotregisteredtelephones,seesection6.1
Create a Configuration File on page 15.
6.3 Scratch Pad when Creating the Configura-
tion file
If a new parameter has to be added into the aastra.cfg file but there is no
support for this new parameter in Manager Telephone System, the
scratch pad can be used. Another usage is if MTS creates a parameter
value, but another value is requested.
It is a free text window where the new parameter or parameter value can
be entered. The parameters are added at the end of the aastra.cfg file.
If a parameter exists twice in the configuration file, the telephone uses
the value at the end of the file.
The scratch pad is found at the bottom of the page:
Telephony > IP Phone > Configuration File > General Setting
6.4 Connect Existing Configuration File to
Manager Telephony System
In a system where MX-ONE Manager Telephony System has not previ-
ously been used when working with an IP phone configuration file, the
existingconfigurationfilecanbeconnectedtotheMTS instead of having
to be recreated. Follow the steps below to connect a configuration file to
MX-ONE Manager Telephony System.
1. Log on to MX-ONE Manager Telephony System.
2. Go to Telephony > IP Phone > SW Server where you register the
IP Phone SW Server.
3. Go to Telephony > IP Phone > Connect Configuration File.
4. Select the IP Phone SW Server and search for existing files. Click
on the Connect icon next to the configuration file to connect to.
5. Go to the Configuration File task. Select the connected configu-
ration file and use the Change icon to change the file, if needed.
When the adaptation of the file is completed, it is automatically
storedunderthecorrectdirectoryintheIPPhoneSoftwareServer.
6. For the phones that are already registered to the PBX, select the
Unregistration option to force the phones to fetch the new config-
uration file.

26/1531-ANF 901 14 Uen E10 2014-01-22 17
MANAGE THE CONFIGURATION FILES IN MANAGER TELEPHONY SYSTEM
6.5 Retrieve the Back-up Copy
If any problem is discovered when a new configuration file has been
loaded into the phones and there is a need to go back to the previous
version, the following procedure shall be used:
1. Log on to MX-ONE Manager Telephony System.
2. Go to Telephony > IP Phone > Configuration File.
3. Use the back-up retrieve icon.
4. For the phones that are already registered to the PBX, select the
Unregistration option to force the phones to fetch the new
configuration file. For phones that are not registered, 6.1 Create a
Configuration File on page 15.

AASTRA 6700ISIP TERMINALS FOR MX-ONE
18 26/1531-ANF 901 14 Uen E10 2014-01-22
7 How to Start a New Phone
The phone is delivered with default settings for an IP network. These
settings must be adapted to the local network using phone configuration
files.
If Manager Telephony Server (MTS) is used and chapter 5.1 Install IP
PhoneSWServer on page 9 has beenfollowed, the phone configuration
files are generated and stored on the Software Web Server.
If MTS is not used, a software server must be set up supporting any of
theprotocolsHTTP or HTTPS to hostthephonefirmware,language files
and configuration files. The firmware files can be downloaded from
Service Support Plaza. There are phone configuration template files
adapted for MX-ONE stored under: etc/opt/eri_sn/aastraSIPPhone.
All firmware files are described in section 8.1 Phone software and config-
uration files on the software server on page 24.
When the phone is powered up, it will look for software (firmware) and
configuration files on the software server according to its configuration
server settings, see section11.8 Setting the IP Address and Download
Protocol of the Software Server on page 34.

26/1531-ANF 901 14 Uen E10 2014-01-22 19
HOW TO START ANEW PHONE
7.1 Boot flow chart
:Configuration of:
-IP address, mask W
-DNS servers
-Time server
-Time zone ofst
-Software server URI (opt 66,43)
Power up
LLDP To get Voice VLAN
DHCP
?
SW-server configured?
Manually
configuration
N
Y
Connect to
SW-server Recommended protocols:
http or https
Reboot Get
security.tuz This file contains the encrypted site
key. Use the anacrypt tool to create
security.tuz and encrypt the config
files.
?
File exists?
Get
aastra.tuz
Get model
specific.tuz
Get
aastra.cfg
Get model
MD5 check sum
?
Get auxiliary
files
Done
Download
fw, reboot
Language files,
Certificates
Different firmware?
firmware
Check
No
Get
MAC.cfg
specific.cfg
No
Get
MAC.tuz
802.1x To get access to the LAN

AASTRA 6700ISIP TERMINALS FOR MX-ONE
20 26/1531-ANF 901 14 Uen E10 2014-01-22
7.2 Connecting the Phone to a Network
To be able to connect the phone to a network, the following parameters
must be configured:
•The phone's IP address, subnet mask, and default gateway.
When using DHCP, these parameters are configured automati-
cally.
•The IP address of the software server. This address is config-
ured automatically using DHCP, or manually from the phone. If
DHCP is used for providing this parameter, the DHCP server must
be configured before the phones can connect to the network. For
information on how to configure the DHCP server for providing the
phone with the IP address to the software server, see 18.1 Data
from DHCP on page 71.
•The IP address of the SIP proxy / SIP registrar. This address is
configured using the configuration file or manually from the phone.
For information on how to configure the phone with the IP address
of the SIP proxy / registrar see 11.9 Setting the IP Address of the
SIP proxy / registrar on page 35
7.3 Log on / Log off
To get log on / log off working, the configuration file shall be created in
MTS and if this is not possible it shall be based on the aastra.cfg
template which is stored in MX-ONE under /etc/opt/eri_sn/aastraSIP-
phones.
There are a number of options when register the telephone to MX-ONE:
•Soft key / Programmable key. The user can log on by pressing
the log on key and enter the extension number and PIN code (if
used). This is the recommended method.
•Procedure: *11*PIN*extension number#. The user can log on by
enteringthisprocedure.This method can be usefulina home office
scenario.
•MAC configuration file, <mac>.cfg. This option can be useful for
telephones where log on/off are not wanted, for example in recep-
tion area or in elevators.
The extension number and the PIN code (if used) are defined in the
MAC configuration file. The telephone will always be logged on.
The user cannot log off the telephone. This can be useful for tele-
phones in the reception area or in elevators. For settings in this file,
see 8.1 Phone software and configuration files on the software
server on page 24.