Cisco Systems ATA 186, ATA 188 manual atamacaddress.txt, Syntax, 3-10

Chapter 3 Configuring the Cisco ATA for MGCP

Configuring the Cisco ATA Using a TFTP Server

Step 4 Use the mgcp_example.txt file again, this time as a template for creating a text file of values that are specific to one Cisco ATA. For example, you might configure the following parameters:

UserID:8530709

GkorProxy:192.168.1.1

Save this file of Cisco ATA-specific parameters as:

ata<macaddress>.txt

where macaddress is the non-dotted hexadecimal version of the MAC address of the Cisco ATA you are configuring. This non-dotted hexadecimal MAC address is labeled on the bottom of most Cisco ATAs next to the word “MAC.” The file name must be exactly 15 characters long. (However, if this filename is supplied by the DHCP server, the name can be as long as 31 characters and can be any name with printable ASCII characters.)

If necessary, you can obtain the non-dotted hexadecimal MAC address by using the atapname.exe command. For information on using the atapname.exe command, see the “Using atapname.exe Tool to Obtain MAC Address” section on page 3-11. That section includes an example of a dotted decimal MAC address and its corresponding non-dotted hexadecimal address.

Note The ata<macaddress>.txt file should contain only those parameters whose values are different from the file of common parameters. Parameter values in the ata<macaddress> configuration file will overwrite any manually configured values (values configured through the web or voice configuration menu) when the Cisco ATA powers up or refreshes.

Step 5 On the top line of the ata<macaddress>.txt file, add an include command to include the name of the common-parameters file, and save the file.

include:common.txt

UserID:8530709

GkorProxy:192.168.1.1

Step 6 Run the cfgfmt.exe tool, which is bundled with the Cisco ATA software, on the ata<macaddress>.txt text file to generate the binary configuration file. If you wish to encrypt the binary file, see the “Using Encryption With the cfgfmt Tool” section on page 3-12.

The syntax of the cfgfmt program follows:

Syntax

cfgfmt [Encryption options] -mgcp -tptag.dat input-text-file output-binary-file

–Encryption options are described in the “Using Encryption With the cfgfmt Tool” section on page 3-12.

–mgcp (for MGCP) is the protocol you are using, which you must specify so that the cfgfmt tool will include only the applicable protocol in the converted output binary file.

–The ptag.dat file, provided with the Cisco ATA software version you are running, is used by cfgfmt.exe to format a text input representation of the parameter/value pairs to its output binary representation. Be sure this file resides in the same directory from which you are running the cfgfmt program.

–input-text-fileis the input text file representation of the Cisco ATA configuration file.

–output-binary-fileis the final output binary file that Cisco ATA uses as the TFTP configuration file.

Cisco ATA 186 and Cisco ATA 188 Analog Telephone Adaptor Administrator’s Guide for MGCP (version 3.0)

3-10 OL-4803-01