Specifications

3-14
Cisco ATA 186 and Cisco ATA 188 Analog Telephone Adaptor Administrator’s Guide for SCCP (version 3.0)
OL-4652-01
Chapter 3 Configuring the Cisco ATA for SCCP
Configuring the Cisco ATA Using a TFTP Server
Note Because the factory-fresh ATA cannot accept encrypted configuration files, the first unencrypted file, if
intercepted, can easily be read. (You would still have to know the data structure format in order to
decode the binary information from the unencrypted file.) Therefore, the new encryption key in the
unencrypted file can be compromised.
Note For security reasons, Cisco recommends that you set the UIPassword parameter (if desired) in the
configuration file and not by using one of the manual configuration methods.
This section contains the following topics:
• Configuration Files that the cfgfmt Tool Creates, page 3-14
• cfgfmt Tool Syntax and Examples, page 3-15
Configuration Files that the cfgfmt Tool Creates
The number of output binary configuration files that the Cisco ATA produces is dependent on two
factors:
• Which encryption key parameter is used—EncryptKey or EncryptKeyEx
• The total size of the binary output
Table 3-6 shows the names of the binary files that can be generated. One, two or four files can be
generated.
Note <macaddress> in Table 3-6 is the MAC address of the Cisco ATA .
Note If you are creating an atadefault configuration file, the generated binary file name will be
atadefault.cfg.x if you encrypt the text file with the EncryptKeyEx parameter; the binary file name will
be atadefault.cfg if you do not use the EncryptKeyEx parameter to encrypt the text file.
Ta b l e 3-6 Configuration Files that the Cisco ATA May Gen erate
Total Binary Output Size Less
Than or Equal to 2,000 Bytes
Total Binary Output Size
Greater Than 2,000 Bytes
Value of
EncryptKeyEx
Parameter
0 ata<macaddress> ata<macaddress>
ata<macaddress>.ex
Non-zero ata<macaddress>
ata<macaddress>.x
ata<macaddress>
ata<macaddress>.ex
ata<macaddress>.x
ata<macaddress>.xex