Home » Cisco Manuals » Telephony » Cisco ATA188-I2-A » Manual Viewer

Cisco ATA188-I2-A Administration Guide - Page 51

Examples of Upgrading to Stronger Encryption Key, Example 1

Get Cisco ATA188-I2-A PDF manuals and user guides

Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

Chapter 3 Configuring the Cisco ATA for H.323 Configuring the Cisco ATA Using a TFTP Server Syntax examples The cfgfmt.exe syntax affects how the EncryptKeyEx or EncryptKey parameters are used, as shown in the following examples. In these examples, input-text-file is the ata.txt file that you will convert to binary to create the ata configuration file(s) for the Cisco ATA; output-binary-file is that binary ata file, and Secret is the encryption key. • cfgfmt -h323 -tptag.dat input-text-file output-binary-file If input-text-file sets the Cisco ATA EncryptKey parameter to 0, then output-binary-file is not encrypted. If the input-text-file sets EncryptKey to a non-zero value, then output-binary-file is encrypted with that value. • cfgfmt -X -h323 -tptag.dat input-text-file output-binary-file This is an example of how you might perform encryption on a first-time Cisco ATA. The -X (uppercase) option means that any value specified for the Cisco ATA EncryptKeyEx parameter in input-text-file is ignored. However, because Secret is not specified in this example, output-binary-file is not encrypted. Nevertheless, the EncryptKeyEx parameter and its value, if specified in input-file-text, will be included in output-binary-file for possible encryption at a later time. The next time the Cisco ATA fetches the configuration file from the TFTP server, the file will be encrypted with Secret. • cfgfmt -X -xSecret -h323 -tptag.dat input-text-file output-binary-file This is an example of changing the encryption key from one key to another key. The -X (uppercase) option means that any value specified for the Cisco ATA EncryptKeyEx parameter in input-text-file is ignored and the output-binary-file is encrypted with the Secret key. However, the EncryptKeyEx parameter and its value, if specified in input-text-file, will be included in output-binary-file. Examples of Upgrading to Stronger Encryption Key This section contains two examples of how you would upgrade your Cisco ATA configuration to use the stronger encyrption method if the current Cisco ATA firmware version was a version earlier than version 2.16.2. Versions earlier than 2.16.2 do not support the stronger EncryptKeyEx parameter. Example 1 In this example, the Cisco ATA has not yet been deployed, but its firmware version is earlier than 2.16.2. Therefore, the Cisco ATA will upgrade to to firmware version 3.0 to use the EncryptKeyEx parameter as its encryption key. The Cisco ATA in this example has a MAC address of 102030405060. Perform the following steps: Procedure Step 1 Step 2 Create a file called ata102030405060.txt by using the applicable example.txt file provided with the Cisco ATA software. (For example, for H.323, the example.txt file is called h323_example.txt.) Modify the ata102030405060.txt file with desired parameter values. The value of the EncryptKey parameter should be 0. OL-4804-01 Cisco ATA 186 and Cisco ATA 188 Analog Telephone Adaptor Administrator's Guide for H.323 (version 3.0) 3-15

Section	Page
CiscoATA186 and CiscoATA188 Analog Telephone Adaptor Administrator’s Guide for H.323 (version...	1
Contents	3
Preface	11
Overview	11
Audience	11
Organization	12
Conventions	12
Related Documentation	16
Obtaining Documentation	16
World Wide Web	16
Documentation CD-ROM	17
Ordering Documentation	17
Documentation Feedback	17
Obtaining Technical Assistance	17
Cisco.com	18
Technical Assistance Center	18
Cisco TAC Web Site	18
Cisco TAC Escalation Center	19
Cisco Analog Telephone Adaptor Overview	21
H.323 Overview	22
H.323 Terminals	23
H.323 Gateways	23
H.323 Gatekeepers	24
H.323 MCUs	24
H.323 Proxy Server	24
Hardware Overview	25
Software Features	27
Voice Codecs Supported	27
Additional Supported Signaling Protocols	27
Other Supported Protocols	27
CiscoATA H.323 Services	28
Fax Services	29
Supplementary Services	29
Installation and Configuration Overview	29
Installing the CiscoATA	31
Safety Recommendations	31
What the CiscoATA Package Includes	32
What You Need	32
Installation Procedure	33
Power-Down Procedure	35
Configuring the CiscoATA for H.323	37
Default Boot Load Behavior	38
Specifying a Preconfigured VLAN ID or Disabling VLAN IP Encapsulation	39
Steps Needed to Configure the Cisco ATA	41
Basic Configuration Steps in a TFTP Server Environment	41
Basic Configuration Steps in a Non-TFTP Server Environment	43
Configuring the Cisco ATA Using a TFTP Server	44
Setting Up the TFTP Server with CiscoATA Software	44
Configurable Features and Related Parameters	44
Creating Unique and Common CiscoATA Configuration Files	45
Using atapname.exe Tool to Obtain MAC Address	47
Using Encryption With the cfgfmt Tool	48
Examples of Upgrading to Stronger Encryption Key	51
atadefault.cfg Configuration File	53
Configuring the Cisco ATA to Obtain its Configuration File from the TFTP Server	54
Using a DHCP Server	54
Without Using a DHCP Server	56
Voice Configuration Menu	56
Using the Voice Configuration Menu	57
Entering Alphanumeric Values	58
Resetting the CiscoATA to Factory Default Values	59
CiscoATA Web Configuration Page	59
Refreshing or Resetting the CiscoATA	61
Procedure to Refresh the CiscoATA	62
Procedure to Reset the CiscoATA	62
Obtaining CiscoATA Configuration File After Failed Attempt	62
Upgrading the H.323 Signaling Image	62
Basic and Additional H.323 Services	63
Important Basic H.323 Services	63
Required Parameters	63
Setting Up User IDs for the CiscoATA	65
Using the Cisco ATA with an H.323 Gatekeeper	65
Choosing Cisco ATA Registration Mode with an H.323 Gatekeeper	65
Setting Up Gatekeeper Time-To-Live Value	66
Setting Up an Alternate H.323 Gatekeeper	66
Establishing Authentication with Cisco H.323 Gatekeeper	67
Using the Cisco ATA Without an H.323 Gatekeeper	68
Using the Cisco ATA With an H.323 Gateway but Without an H.323 Gatekeeper	68
Using Multiple Cisco ATAs Without an H.323 Gatekeeper	68
Setting the Audio Codecs	69
Additional H.323 Services	69
Configurable Reboot of CiscoATA	70
Configuring Audio Packet Settings	70
Configuring Billable Features	70
Configuring the Call Waiting Permanent Default Setting	71
Configuring the CiscoATA Refresh Interval	71
Configuring Hook Flash Timing	71
Configuring the Mixing of Call Waiting Tone and Audio	71
Configuring Network Ringback Tone	72
Configuring Reverse Audio Cut-Through Behavior	72
Configuring Supplementary Service Behavior and Parameters	72
Debugging Diagnostics	72
Hardware Information Display	72
Network Timing	73
Polarity Settings	73
Progress Tones	73
Selecting DTMF and Hookflash Transmission Methods	73
Selecting H.323 Connection and H.245 Transmission Methods	74
Setting Dial Plans	74
Complete Reference Table of all CiscoATA H.323 Services	74
Parameters and Defaults	77
Configuration Text File Template	78
User Interface (UI) Security Parameter	79
UIPassword	79
Parameters for Configuration Method and Encryption	80
UseTFTP	80
TftpURL	81
CfgInterval	82
EncryptKey	82
EncryptKeyEx	83
Network Configuration Parameters	84
DHCP	84
StaticIp	85
StaticRoute	85
StaticNetMask	86
NTPIP	86
AltNTPIP	87
DNS1IP	87
DNS2IP	88
VLANSetting	88
H.323 Parameters	89
GkOrProxy	89
GkId	90
GkTimeToLive	90
AltGk	90
AltGkTimeOut	91
UID0	92
PWD0	92
UID1	93
PWD1	94
LoginID0	94
LoginID1	95
UseLoginID	95
AutMethod	96
Gateway	96
Audio Configuration Parameters	97
MediaPort	97
RxCodec	98
TxCodec	98
LBRCodec	99
AudioMode	100
NumTxFrames	101
TOS	102
Operational Parameters	102
CallFeatures	103
PaidFeatures	104
CallCmd	105
FeatureTimer	106
FeatureTimer2	107
SigTimer	107
ConnectMode	108
OpFlags	110
TimeZone	112
Telephone Configuration Parameters	113
CallerIdMethod	114
Polarity	115
FXSInputLevel	116
FXSOutputLevel	116
Tone Configuration Parameters	117
Tone Parameter Syntax—Basic Format	117
Tone Parameter Syntax—Extended Formats	119
Extended Format A	119
Extended Format B	120
Recommended Values	124
Specific Tone Parameter Information	124
DialTone	124
BusyTone	125
ReorderTone	125
RingbackTone	126
CallWaitTone	126
AlertTone	127
RingOnOffTime	127
Dial Plan Parameters	128
DialPlan	128
Dial Plan Commands	129
Dial Plan Rules	130
Dial Plan Examples	134
DialPlanEx	136
IPDialPlan	136
Diagnostic Parameters	136
NPrintf	137
SyslogIP	137
SyslogCtrl	138
CFGID—Version Parameter for CiscoATA Configuration File	139
Call Commands	141
Call Command Structure	141
Syntax	142
Context-Identifiers	143
Input Sequence Identifiers	144
Action Identifiers	144
Call Command Example	145
Call Command Behavior	147
Configuring and Debugging Fax Services	153
Using Fax Pass-through Mode	153
Configuring the Cisco ATA for Fax Pass-through mode	154
AudioMode	154
ConnectMode	155
Configuring Cisco IOS Gateways to Enable Fax Pass-through	155
Enable Fax Pass-through Mode	156
Disable Fax Relay Feature	157
Using FAX Mode	158
Configuring the Cisco ATA for Fax Mode	158
Configuring the Cisco ATA for Fax Mode on a Per-Call Basis	159
Configuring the Cisco IOS Gateway for Fax Mode	159
Debugging the Cisco ATA 186/188 Fax Services	159
Common Problems When Using IOS Gateways	159
Using prserv for Diagnosing Fax Problems	161
prserv Overview	161
Analyzing prserv Output for Fax Sessions	162
Using rtpcatch for Diagnosing Fax Problems	164
rtpcatch Overview	164
Example of rtpcatch	166
Analyzing rtpcatch Output for Fax Sessions	168
Using rtpcatch to Analyze Common Causes of Failure	170
rtpcatch Limitations	172
Upgrading the CiscoATA Signaling Image	173
Upgrading the Signaling Image from a TFTP Server	173
Upgrading the Signaling Image Manually	174
Preliminary Steps	175
Running the Executable File	175
Upgrade Requirements	175
Syntax	176
Upgrade Procedure and Verification	176
Confirming a Successful Signaling Image Upgrade	177
Using a Web Browser	177
Using the Voice Configuration Menu	178
Troubleshooting	179
General Troubleshooting Tips	179
Symptoms and Actions	180
Installation and Upgrade Issues	181
Debugging	182
Using System Diagnostics	183
Local Tone Playout Reporting	187
Obtaining Network Status Prior to Getting IP Connectivity	188
Obtaining Network Status After Getting IP Connectivity	189
DHCP Status HTML Page	190
Real-Time Transport Protocol (RTP) Statistics Reporting	190
Frequently Asked Questions	191
Contacting TAC	193
Using H.323 Supplementary Services	195
Changing Call Commands	195
Cancelling a Supplementary Service	195
Common Supplementary Services	195
Caller ID	196
Call-Waiting Caller ID	196
Making a Conference Call in the United States	196
Making a Conference Call in Sweden	197
Call Waiting in the United States	197
Call Waiting in Sweden	197
Calling Line Identification Presentation	197
About Calling Line Identification Restriction	198
Calling Line Identification Restriction in the United States	198
Calling Line Identification Restriction in Sweden	198
Voice Menu Codes	199
CiscoATASpecifications	203
Physical Specifications	203
Electrical Specifications	204
Environmental Specifications	204
Physical Interfaces	204
Ringing Characteristics	205
Software Specifications	205
H.323 Signaling	209
Supported H.323 Messages	209
H.323 Signaling Scenarios	210
H.323 Endpoint-to-Gatekeeper Registration	210
H.323 Endpoint-to-Endpoint Call Setup with a Common Gatekeeper	213
H.323 Call Setup from H.323 Network to Circuit Switched Network	222
Recommended CiscoATATone Parameter Values by Country	243
Glossary	259

Match case Limit results 1 per page

3-15

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

OL-4804-01

Chapter 3

Configuring the Cisco ATA for H.323

Configuring the Cisco ATA Using a TFTP Server

Syntax examples

The cfgfmt.exe syntax affects how the EncryptKeyEx or EncryptKey parameters are used, as shown in

the following examples. In these examples, input-text-file is the ata<

macaddress>.

txt

file that you will

convert to binary to create the ata<

macaddress>

configuration file(s) for the Cisco ATA;

output-binary-file is that binary ata<

macaddress>

file, and

Secret

is the encryption key.

•

cfgfmt -h323

-tptag.dat

input-text-file output-binary-file

If input-text-file sets the Cisco ATA EncryptKey parameter to 0, then output-binary-file is not

encrypted. If the input-text-file sets EncryptKey to a non-zero value, then output-binary-file is

encrypted with that value.

•

cfgfmt -X -h323

-tptag.dat

input-text-file output-binary-file

This is an example of how you might perform encryption on a first-time Cisco ATA.

The -X (uppercase) option means that any value specified for the Cisco ATA EncryptKeyEx

parameter in input-text-file is ignored. However, because

Secret

is not specified in this example,

output-binary-file is not encrypted. Nevertheless, the EncryptKeyEx parameter and its value, if

specified in input-file-text, will be included in output-binary-file for possible encryption at a later

time. The next time the Cisco ATA fetches the configuration file from the TFTP server, the file will

be encrypted with

Secret

•

cfgfmt -X -xSecret -h323

-tptag.dat

input-text-file

output-binary-file

This is an example of changing the encryption key from one key to another key.

The -X (uppercase) option means that any value specified for the Cisco ATA EncryptKeyEx

parameter in input-text-file is ignored and the output-binary-file is encrypted with the

Secret

key.

However, the EncryptKeyEx parameter and its value, if specified in input-text-file, will be included

in output-binary-file.

Examples of Upgrading to Stronger Encryption Key

This section contains two examples of how you would upgrade your Cisco ATA configuration to use the

stronger encyrption method if the current Cisco ATA firmware version was a version earlier than version

2.16.2. Versions earlier than 2.16.2 do not support the stronger EncryptKeyEx parameter.

Example 1

In this example, the Cisco ATA has not yet been deployed, but its firmware version is earlier than 2.16.2.

Therefore, the Cisco ATA will upgrade to to firmware version 3.0 to use the EncryptKeyEx parameter

as its encryption key.

The Cisco ATA in this example has a MAC address of 102030405060.

Perform the following steps:

Procedure

Step 1

Create a file called

ata102030405060.txt

by using the applicable

example.txt

file provided with the

Cisco ATA software. (For example, for H.323, the example.txt file is called h323_example.txt.)

Step 2

Modify the

ata102030405060.txt

file with desired parameter values. The value of the EncryptKey

parameter should be 0.