Product guide

A5000 R5.4 Product Guide SIP terminals Aastra 6700i range
BPS0121AENAA01 Page 45/64
35.17 Deploying 6700i series terminal
There are two methods of deploying 6700i series terminals, recommended by Aastra:
Deployment through manual login:
With TMA not configured
Or with TMA configured (CTRL-I)
Massive deployment
Other deployment methods are available but are not recommended by Aastra.
See the sections below for more information about these different methods.
35.17.1 Automatic deployment through manual login
This deployment method is used when the administrator does not wish to enter the subscriber number
in each terminal. Manual login is then used.
This deployment method consists in logging on manually to A6700i series terminals without having to
enter the specific configuration file @MAC.cfg. The production software release and global data
configuration files downloaded by the A6700i series terminals during this deployment phase are
available in the storage directory deployment_67xxi. This directory is accessible to A6700i series
terminals via the connexio/connexio account, which is the default account of the A6700i series
terminal upon leaving the factory.
The administrator configures the DHCP server in order to communicate the FTP server IP
address to the terminal.
Via an Excel file imported by TMA, the administrator enters the general configuration
parameters and the terminal’s latest software release. It is also possible to choose the FTP
server used. The general configuration parameters differ from one FTP server to the other.
The terminal can then be connected to the working network.
The terminal is initialised and connects to the integrated DHCP server. The integrated
DHCP server then assigns the terminal an IP address. The integrated DHCP server
also provides the A6700i series terminal with the IP address of the integrated FTP
server and the (connexio/connexio) account to which the A6700i series terminal will
connect to download its production software release and deployment global data
configuration file.
After the new production software release and global data configuration file are
downloaded, the terminal screen indicates that the terminal is a general-purpose
terminal (without a subscriber).
The manual login procedure may start after pressing the Ident key, which lights up by
default. The user must then enter the subscription number of the 6700i series terminal
and confirm (by pressing Enter) then the password (0000 by default) and confirm (by
pressing Enter or OK). A hold message appears and the terminal automatically logs
on to its subscription.
The terminal is working; the idle screen is displayed.
Note: when the user enters his subscriber number, Aastra 5000 checks whether the subscription
exists in the LDAP directory. If the subscriber number does not exist, the user is again prompted to
enter his subscriber number.
Automatic configuration allows the Dual Homing and programmable key management functions to be
addressed.
Note: if an SIP MD5 password is used, you have to implement authentication after manual login or
else the terminal login will be rejected.