AudioCodes 420HD - Preparing a Global.cfg Configuration File; Generating MAC-Specific <Private>.Cfg Configuration Files

400HD Series IP Phones
Administrator's Manual 314 Document #: LTRT-11950
D.1.2 Preparing a global.cfg Configuration File
This section shows how to prepare a configuration file containing parameter settings
common to all users in the customer enterprise. You'll name the file global.cfg.
 To prepare a global.cfg configuration file:
1. In the Web interface, change the default settings of parameters unique to your
enterprise customers (e.g., Language).
2. Make sure the phone functions as expected.
3. In the Web interface's 'Configuration file' page (Management > Manual Update
> Configuration file), save the modified configuration parameter settings to a
file. Name the file global.cfg.
D.1.3 Generating MAC-specific <private>.cfg Configuration Files
This section shows how to generate MAC-specific <private>.cfg configuration files that will
contain parameter settings that are unique to each user in a customer enterprise.
To generate MAC-specific <private>.cfg configuration files:
1. Prepare a csv file (see Section C.1.3.1)
2. Prepare a template file (see Section C.1.3.2)
3. Automatically generate MAC-specific <private>.cfg configuration files using
VoIProvision tool (see Section C.1.3.3 on page 316)
D.1.3.1 Preparing a csv File
Export a csv file from your enterprise customer's IP-PBX or another database.
The csv file must list the IP phones in the enterprise, including MAC address, user name,
extension ID, and password of each phone. The csv file contains the tagged records for each
IP phone. When opened as a text file, the csv file looks like this:
[mac],[name],[id],[password]
00908F123456,Jonathan,4071,12345
00908F123457,David,4418,12345
Table D-1: CSV File Description
[mac] [name] [id] [password]
00908F123456 Jonathan 4071
12345
00908F123457 David 4418
12345
Note:
• 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,Eitan).
• There is no restriction on the format of the tags (e.g., [tag] or @tag@).