Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept responsibility
for errors or omissions. Updates to this document can be downloaded from
This document is subject to change without notice.
Date Published: June-23-2020
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of
with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our Web site at
Each abbreviation, unless widely used, is spelled out in full when first used.
Version 3.4.3 15 400HD Series IP Phones
400HD Series IP Phones
Related Documentation
Document Name
405HD IP Phone User’s Manual
405HD IP Phone Quick Guide
430HD IP Phone User’s Manual
430HD IP Phone Quick Guide
440HD IP Phone User’s Manual
440HD IP Phone Quick Guide
445HD Generic SIP IP Phone User's Manual
445HD Generic SIP IP Phone Quick Guide
450HD Generic SIP IP Phone User's Manual
450HD Generic SIP IP Phone Quick Guide
C450HD Generic SIP IP Phone User's Manual
C450HD Generic SIP IP Phone Quick Guide
HRS Conference Device User’s Manual
HRS Conference Device Quick Guide
RX50 Conference Phone User's Manual
RX50 Conference Phone Release Notes
400HD Series IP Phone Administrator’s Manual
Device Manager Pro Administrator’s Manual
One Voice Operations Center (OVOC) IOM Manual
OVOC User’s Manual
Document Revision Record
LTRT Description
11973 This is the initial release of the unified product documentation.
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the Documentation
Feedback form on our Web site at https://online.audiocodes.com/documentation-feedback.
Administrator's Manual 16 Document #: LTRT-11975
Administrator's Manual 1. Introduction
1 Introduction
This Administrator’s Manual is intended for network administrators responsible for
configuring AudioCodes’ IP phones in their enterprise telephony networks.
The manual covers AudioCodes’ low-end and high-end phone models:
Low-end phone models: 405HD, 430HD and 440HD
High-end phone models: 445HD, 450HD, C450HD, RX50 conference phone and the
HRS conference device
Note:
•Release Notesversion 3.4.3 documents support only the following high-end phone
•This Administrator’s Manual documents support both theseand the following low-
end phone models:
√ 405HD
√ 430HD
√ 440HD
•When a feature is documented but support is still pending, a note will indicate this.
AudioCodes' IP phones are based on AudioCodes' proprietary High Definition (HD) voice
technology, providing clarity and a rich audio experience in Voice-over-IP (VoIP) calls. The
phones are fully-featured telephones that provide voice communication over an IP network,
allowing you to place and receive phone calls, put calls on hold, transfer calls, make
conference calls, and so on.
For a detailed description on hardware installation and for operating the phone's call features,
see the phone’s User's Manual.
Version 3.4.3 17 400HD Series IP Phones
400HD Series IP Phones
This page is intentionally left blank.
Administrator's Manual 18 Document #: LTRT-11975
Administrator's Manual 2. Configuration Methods
2 Configuration Methods
The phones feature four optional configuration methods:
Configuration file. Text-based file, created using a text editor such as Microsoft's
Notepad. Contains configuration parameters. Loaded to the phone using provisioning
methods TFTP, FTP, HTTP/HTTPS. See Section 2.2 for more information.
Device Manager Pro/Express. See Section 2.3 for more information.
Phone screen. Easy-to-use, menu-driven screen providing basic phone configuration
and status capabilities. See the next section for more information.
2.1 Phone Screen
The Liquid Crystal Display (LCD) phone screen allows configuring phone Settings, Keys and
Administration menus.
2.1.1 Administration Menu
Note:
•The phone is password protected. The default password is 1234. To change the
login password, use the phone's configuration file.
• After entering the password, the access session is applied to all the submenus.
• To change the Administration screen's login password, use the configuration file.
To access the Administration screen:
1. Press the MENU key on the phone and navigate down to Administration.
Note: Alternatively, after pressing the MENU key you can press an item's number to
navigate to the item, for exam ple, in the 445HD, press 5 to navigate to Administration.
2. Press Select; you're prompted for a password.
3. Enter the administration password (Default: 1234) and then press the OK softkey.
2.1.2 Configuring the Web Interface's Port
If the network administrator requires the Web interface for a configuration purpose, they need
to assign it a port number.
To configure the Web interface port:
•Use the table as reference.
Table 2-1: Port Parameters
Parameter Description
system/http_server_port
system/https_server_port
Version 3.4.3 19 400HD Series IP Phones
Assigns a port number to the Web interface.
The HTTP server by default uses port number 80. Range: 0-65535.
Assigns a port number to the Web interface.
The HTTPS server by default uses port number 443. Range: 0-65535.
400HD Series IP Phones
2.1.3 Configuring User Login Credentials
The network administrator can configure the phone user's name and password.
To configure user's name and password:
• Use the table as reference.
Table 2-2: User Name and Password Parameters
Parameter Description
system/web_user_name
system/web_user_password
2.2 Configuration File
This section describes the configuration file and the parameters you can configure in it. The
configuration file can be loaded to the phone using automatic provisioning or from the Device
Manager. The subsections below describe configuration file syntax and linking additional
configuration files to a configuration file.
2.2.1 File Syntax
The configuration file can be created using a standard ASCII, text-based program such as
Notepad. The configuration file is a .cfg file with the file name being the phone's MAC
address: <phone's MAC address>.cfg.
The syntax of the configuration file is as follows:
<parameter name>=<value>
Make sure the configuration file conforms to these guidelines:
No spaces on either side of the equals (=) sign.
Each parameter must be on a new line.
Below is an example of part of a configuration file:
The phone user name. Default: admin.
Applies only to the Web interface.
The encrypted phone password. Default: 1234.
Applies only to the Web interface, and phone screen.
2.2.2 Linking Multiple Files
The Configuration file allows you to include links (URL and/or file name) to other
Configuration files that provide additional parameter settings. This is especially useful in
deployments with multiple phones, where the phones share common configuration but where
each phone has some unique settings. In such a scenario, a phone's Configuration file can
include unique parameter settings as well as links to additional Configuration files with
settings common to all phones.
Linking additional files is achieved by using the include function in the phone's Configuration
file. For example, the below Configuration file provides links to additional Configuration files
(shown in bolded font):
system/type=440HD
Administrator's Manual 20 Document #: LTRT-11975
Administrator's Manual 2. Configuration Methods
include 440HD_<MAC>_voip.cfg
include vlan_conf.cfg
include network_conf.cfg
include provisioning_conf.cfg
In addition, the Configuration file can provide URL paths (FTP, TFTP, HTTP, or HTTPS) to
where the additional files are located, as shown in the example below (shown in bolded font):
system/type=440HD
include http://10.10.10.10/440HD_<MAC>_voip.cfg
include https://remote-pc/vlan_conf.cfg
include tftp://10.10.10.10/440HD_<MAC>_network.cfg
include ftp://remote-pc/provisining_conf.cfg
Note: If no URL is provided in the Configuration file, the files are retrieved according to
the provisioning information (e.g. DHCP Option 160 as well as Option 66/67).
2.2.3 Creating Configuration Files using VoIProvision Utility
When installing AudioCodes' phones, the network administrator typically configures each
installed phone automatically. Using DHCP options or other methods, the phone can be
instructed to download a configuration file. This file is typically unique to each phone, based
on the MAC address. This MAC-specific configuration file is generated with phone specific
configuration parameters; such as, the extension ID, name and authentication password.
Not all of the iPBX and SoftSwitch vendors (and especially the full solution vendors) include
provisioning in their interoperability programs. As an IP phone vendor, AudioCodes is
required to provide a standalone provisioning tool that will enable the provisioning of its
phones in such environments.
AudioCodes provides a tool that assists in the automatic generation of configuration files.
These files can be generated for the initial configuration of the phones and then later
regenerated for subsequent configuration updates as required.
2.2.3.1 Configuration File Format
The detailed format of the phones' configuration files are described in the appendix. The
following is an output example of an automatically generated MAC-specific file:
system/type=440HD
voip/line/0/enabled=1
voip/line/0/id=56832432
voip/line/0/auth_name=3423fdwer2tre
voip/line/0/auth_password=123456
include global.cfg
2.2.3.2 Global Configuration File
In addition to the MAC-specific files, it is recommended to maintain a single global
configuration file, which contains parameters that are common to all phones in the specific
site. The MAC-specific files can call the global file (using the 'include' method) as illustrated
in the above example. For more information, see 'Linking Additional Files using “Include”' in
the Administrator's Manual.
2.2.3.3 VoIProvision Utility Overview
The VoIProvision utility is a generic tool that automatically generates multiple MAC-specific
configuration files (.cfg). The utility generates a separate .cfg file for each phone.
Version 3.4.3 21 400HD Series IP Phones
To execute the utility, the user needs to prepare a csv file and a template file. The csv file
12345
12345
contains the tagged records for each phone and the template file maps these tagged records
to a configuration file format, which can be read by the phone.
2.2.3.4 CSV File
The csv file contains a list of tags and a list of the tag's values. The first line in the file contains
the list of tags (comma-separated) and each of the other lines contains a list of values, where
each line record represents an individual phone.
The csv file is usually exported from the customer's IP-PBX or some other database and
typically contains the list of phones (e.g. MAC, extension ID, user name and password of
each phone).
[mac] [name] [id] [password]
400HD Series IP Phones
Table 2-3: Example of CSV File
00908F123456 Jonathan 4071
00908F123457 David 4418
When opened as a text file, the csv file appears similar to the example below:
The template file defines the format of the generated configuration files, but contains tags
instead of actual values. The VoIProvision utility reads the template file and replaces each
tag with actual values from the csv file.
Example of a template file:
system/type=440HD
voip/line/0/enabled=1
voip/line/0/id=id
voip/line/0/auth_name=name
voip/line/0/auth_password=password
include global.cfg
2.2.3.6 Generated Configuration Files
The generated configuration (.cfg) files use a similar format to the template file; however the
tags are replaced with the actual values that are read by the VoIProvision utility from the csv
file. One of the tags defined in the csv file, should be used as the .cfg file name (in order for
the VoIProvision utility to generate a separate .cfg file for each line record in the csv file).
Typically the tag which defines the MAC address is used as the .cfg file name.
2.2.3.7 Starting the VoIProvision Utility
The VoIProvision utility can run on both the Linux and Windows platforms. The VoIProvision
utility initially parses the csv file to generate the list of tags. The VoIProvision then reads each
line record of values in the csv file and for each line record, does the following:
Parses the line record to create a list of values
Opens the template file
Generates the .cfg file name and create a new .cfg file
Reads the template file, associates the mapped tags with actual values from the csv
The first line of the csv file contains the list of tags (e.g.,
mac,name,id).
The remainder of the csv file contains a line record per .cfg file (e.g.
00908f112233,4071,Ethan).
There is no restriction on the format of the tags (e.g., tag or @tag@).
The template file defines the .cfg file format. During VoIProvision
run-time, the mapped tags in the template file are associated to actual
values that are read from the csv file.
Currently only a single tag can be defined per line record in the
template file.
The .cfg file name should represent the string of one of the predefined
tags in order to generate a separate .cfg file per csv line record
(e.g., mac.cfg).
2.2.4 Using the Encryption Tool
AudioCodes' phones use the Triple Data Encryption Standard (3DES) algorithm for
encryption.
Note: Support pending.
2.2.4.1 Encrypting Configuration Files
The configuration file can be encrypted. For example, you may wish to encrypt the
configuration file when it is sent over an insecure network.
To encrypt the configuration file:
At the command line prompt, specify the following:
encryption_tool.exe –f <filename>.cfg
where <file name>.cfg specifies the name of the Configuration file that you wish to
encrypt.
Once the Configuration file is encrypted, it receives the suffix '.cfx' (e.g. Conf.cfx). This
is the file that you should specify in the 'Configuration URL' and the 'Dynamic
Configuration URL' fields when performing automatic provisioning (see Part II
'Automatic Provisioning').
Version 3.4.3 23 400HD Series IP Phones
400HD Series IP Phones
2.2.4.2 Encrypting Passwords in the Configuration File
Phone passwords used in the configuration process can be encrypted, for example, the
'System' password and the 'SIP Authentication' password.
To encrypt passwords:
1. At the command line prompt, specify the following:
encryption_tool.exe –s <password_string>
where <password_string> specifies the string of the password that you wish to
encrypt.
Once the password is encrypted, a string is generated with the following syntax:
{"<encrypted_string>"}
For example:
{"0qrNRpSJ6aE="}
2. Copy the generated string (including the {“ “}) with the syntax specified above to the
relevant parameter in the Configuration file.
For example, if you encrypted the SIP authentication password, the following is
displayed in the relevant line in the configuration file:
voip/line/0/auth_password={"0qrNRpSJ6aE="}
Note: It's recommended to encrypt the 'System' password using this procedure. If you
choose not to, the 'System' password is by default encrypted using MD5.
Administrator's Manual 24 Document #: LTRT-11975
Administrator's Manual 2. Configuration Methods
2.3 Device Manager
Network administrators can provision an enterprise's phones from the server of the One
Voice Operations Center (OVOC) module, Device Manager.
Note:
• Device Manager and OVOC share the same server location.
• For more information on using Device Manager to provision phones, see the Device
Manager Administrator's Manual.
To configure provisioning phones from the OVOC server:
Use the table as reference.
Table 2-4: OVOC Server Parameters
Parameter Description
ems_server/keep_alive_period
ems_server/provisioning/url
ems_server/user_name
ems_server/user_password
The OVOC server sends a keep alive message at a
configured interval to verify that its link with the network
is operating. If no reply is received, the link is
determined to be down or not working.
Default: 60 minutes
Defines the URL of the OVOC server, for example,
http://10.1.8.23:8081
Defines the username of the administrator who'll use
the OVOC serv er for provisioning, for example, John
Smith.
Defines the password (encrypted) of the network
administrator who'll provision the phones from the
OVOC server, f or example:
{"Y6QYmP53BDkoTvuIFjEBuQ=="}
By default, the phone is ready for out-of-the-box deployment using its automatic provisioning
capabilities.
The phone offers a built-in mechanism for automatically upgrading its software image and
updating its configuration. This method is used to upgrade the phone firmware and update
its configuration, by remotely downloading an updated software image and configuration file.
The automatic update mechanism helps you keep your software image and configuration
up-to-date, by performing routine checks for newer software versions and configuration files,
as well as allowing you to perform manual checks.
The automatic update mechanism is as follows:
Before connecting the phone, verify that the provisioning server is running and that the
firmware and configuration files are located in the correct location.
Connect your phone to the IP network, and then connect the phone to the power
outlet.
During DHCP negotiation, the phone requests for DHCP options 66/67/160 to receive
provisioning information. The DHCP server should respond with Option 160 providing
the provisioning URL or Options 66 and 67 providing the TFTP IP address and
firmware file name respectively.
The phone then checks whether new firmware is available by checking the firmware
file header. If the version is different from the one currently running on the phone, the
phone downloads the complete image and burns it to its flash memory.
If a new firmware is unavailable, the phone then checks whether a new configuration
is available. If a configuration file is available on the server, the phone downloads it
and updates the phone's configuration after verifying that the configuration file is
related to the phone model. When a configuration update is needed, the phone might
reboot.
Note:
•In the DHCP Discover message, the phone publishes its model name in Option
fields 60 and 77 (e.g. 440HD). If the administrator wants to provide different
provisioning information to different phone models, the administrator can set up a
policy in the DHCP server according to the phone model name.
•If the phone is powered off for some reason during the firmware upgrade process,
the phone will be unusable and the recovery process must be performed.
•You can only use firmware files with an .img extension and configuration files with a
.cfg extension.
•An additional auto-provisioning mechanism is supported if the provisioning
environment does not provide all the required information (e.g. DHCP options).
Note: Automatic mass provisioning of phones using DHCP can alternatively be
performed from the OVOC’s Device Manager module. For more information, see the
Device Manager Pro Administrator's Manual.
Version 3.4.3 27 400HD Series IP Phones
400HD Series IP Phones
3.1 Setting up Network for Auto Provisioning
The phone supports dynamic VLAN discovery, dynamic IP addressing (DHCP), and NTP (as
client).
Note: For manual configuration of Network Settings, see Section 4.2.
3.1.1 Provisioning Hunt Order
The phone always attempts to use the first provisioning method listed below (DHCP Option
160). If it cannot use this method, it attempts to use the second method listed below, and so
on, until it reaches a successful provisioning method. This is called the provisioning 'hunt
order'. The 'hunt order' is:
1. DHCP Option 160 (see Section 3.1.2.1)
2. DHCP Options 66-67 (see Section 3.1.2.2)
3. DHCP Options 43 (see Section 3.1.2.5)
4. SIP SUBSCRIBE and NOTIFY Messages (see Section 3.1.2.7)
5. Static and Globally Accessible Domain (see Section 3.1.2.8)
6. Cached Addresses of the Last Provisioning Server Used on Reboots (see Section
3.1.2.9)
7. AudioCodes Redirect server (see Section 3.1.2.10)
3.1.2 Dynamic URL Provisioning
Dynamic Host Configuration Protocol (DHCP) can be used to automatically provision the
phone.
To configure DHCP:
•Use the table as reference.
Table 3-1: DHCP Automatic Provisioning Parameters
Parameter Description
provisioning/method Defines the provisioning method:
Disable - Automatic update is disabled. The phone
attempts to upgrade its firmware and configuration
Dynamic - DHCP Options (Dynamic URL) (default) -
Using DHCP option 160 as well as option 66/67 for
provisioning
Static URL - Using Static URL for provisioning
provisioning/url_option_value
Determines the DHCP option number to be used for
receiving the URL for provisioning.
The default value is 160.
The phone supports DHCP Option 160 for complete URL
as well as Options 66/67 for TFTP usage. Option 160 has
the highest priority and if absent, Options 66/67 are used.
The following syntax is available for DHCP option 160:
and the configuration file name is <MAC address>.cfg.
For example, 001122334455.cfg
tftp://192.168.2.1/different_firmware_name.img -
retrieved firmware file is
Different_Firmware_Name.img and the configuration
file name is <MAC address>.cfg. For example,
001122334455.cfg
http://192.168.2.1/different_firmware_name.img;
<MODEL>_<MAC>_conf.cfg - retrieved firmware file
is different_firmware_name.img and the configuration
file name is <Model type>_<MAC address>_conf.cfg.
For example, 440HD_001122334455_conf.cfg
•https://192.168.2.1/;<MODEL>_<MAC>_conf.cfg - if
the model is 440HD, the retrieved firmware file is
440HD.img and the configuration file name is
440HD_<MAC Address>_conf.cfg.
For example, 440HD_001122334455_conf.cfg
The following syntax is available for DHCP Options
66/67:
Option 66 must be a valid IP address or host name of
a TFTP server only.
Option 67 must be the firmware name.
If Option 67 is absent, the phone requests for the
440HD.img image file. For example:
Option 66: 192.168.2.1 or myTFTPServer
Option 67: 440HD_2.2.2.img
Note:
This parameter is applicable only when method is
configured to Dynamic.
It is recommended to leave the parameter at its
default value to avoid conflict with other DHCP options
settings.
Defines the maximum random number to start the
provisioning process.
This is used for periodic checking of firmware and
configuration files to avoid multiple devices from starting
the upgrade process at the same time. When the device
is meant to start the upgrade, the device randomly
Version 3.4.3 29 400HD Series IP Phones
400HD Series IP Phones
random_provisioning_time and performs the check
Parameter Description
only after the random time.
The valid range is 0-65535. The default value is 120.
provisioning/period/type Defines the period type for automatic provisioning:
every5minutes Minimum definable time. Sets the
interval at every five minutes.
every15minutes Sets the interval at every five
minutes.
hourly - Sets an interval in hours.
daily (default) - Sets an hour in the day.
weekly - Sets a day in the week and an hour in the
day.
powerup Irrespective of what value is defined, the
phone always checks on powerup, but if powerup is
defined, the phone will check only on powerup.
provisioning/period/hourly/hours_interval
The interval in hours for automatically checking for new
firmware and configuration files.
The valid range is 1 to 168. The default is 24.
Note: This parameter is applicable only when type is
configured to hourly.
provisioning/period/daily/time
provisioning/period/weekly/day
provisioning/period/weekly/time
The hour in the day for automatically checking for new
firmware and configuration files.
The format of this value is hh:mm, where hh is hour and
mm is minutes. For example, 00:30.
The default time is 00:00.
Note: This parameter is applicable only when type is
configured to daily.
The day in the week for automatically checking for new
firmware and configuration files.