Product guide

A5000 R5.4 Product Guide – SIP terminals – Aastra 6700i range
BPS0121AENAA01 Page 47/64
35.17.3 Automatic DHCP and FTP server configuration
Case 1: deployment on an AX Series gateway – single-site configuration
To facilitate deployment, the configuration of DHCP and FTP servers on AXS gateways is optional.
Once the administrator enters all the parameters, the file aastra.cfg is automatically generated and
made available on the FTP server.
The DHCP server is automatically activated and reroutes the terminals to the FTP server on which the
file aastra.cfg is located.
If the file aastra .cfg is not suitable for the administrator, the administrator may use TMA to create his
own aastra.cfg. In this case, a template file is used to personalise aastra.cfg.
TMA then makes this new file available.
The administrator must create the link between the subscriber number and the terminal. This will be
done by entering in each terminal the subscriber number for which is meant. This operation may be
performed via the terminal’s web interface or directly via the terminal interface, or through manual
login.
Case 2: deployment on an AX Series gateway and A5000 server – multi-site configuration
The same behaviour as for case 1, except that when the terminal connects to the iPbx, the iPbx
reroutes the terminal to the iPbx on which the terminal is declared.
Note:
The following parameters must also be managed:
 iPbx address, backup iPbx address (for dual homing), the keys – parameters managed by the
file @mac.cfg
 Numbering plan – parameters managed by the file aastra.cfg
Automatic configuration of these parameters can be disabled if the administrator wishes to configure
them directly in the configuration files @mac.cfg and aastra.cfg.