Home » Cisco Manuals » Telephony » Cisco ATA186-I1 » Manual Viewer

Cisco ATA186-I1 Administration Guide - Page 173

Performing a Cross-Protocol Upgrade - sip firmware

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

Page 173 highlights

D A P P E N D I X Performing a Cross-Protocol Upgrade OL-4652-01 This section describes how to perform an upgrade from the SCCP signaling image to either the MGCP, SIP or H.323 signaling images. You can configure the Cisco ATA to automatically download a new signaling image that the Cisco CallManager administrator has stored on the TFTP server. You do this by configuring the parameter upgradecode in your Cisco ATA configuration file. For more information about setting up the configuration file, see the "Creating a Configuration File for a Specific Cisco ATA" section on page 3-11. Syntax of upgradecode Parameter upgradecode:3,0x301,0x0400,0x0200,tftp_server_ip,69,image_id,image_file_name Definitions • The hexadecimal values that precede the tftp_server_ip variable must always be the values shown in the syntax. • tftp_server_ip is the TFTP server that contains the latest signaling image file. • image_id is a unique 32-bit integer that differs with each upgrade. You can determine this 32-bit integer value by using the build date on the image file name and prepending it with "0x". For example, if the image_file_name is ata186-v2-14-020514a.kxz, then the build date is 020508a, and the image_id is 0x020508a). • image_file_name is the signaling upgrade-image file name. The image_file_name format is: ata186-v{M}-{N}-{yymmdd}{a-f}{ext} - - M is the major version number - - N is the minor version number (always two digits) - - yymmdd is a two-digit year, two-digit month, and two-digit day - - a-f is the build letter (- yymmdd and a-f together form the build date of the image) - - ext must be ".kxz" for upgrading from version 2.11 and below, and can be ".zup" for upgrading from version 2.12 and up for the Cisco ATA186, but it must be ".zup" for upgrading the Cisco ATA188. Process Whenever the Cisco CallManager administrator stores a new signaling image (denoted by a change to the image_id) on the TFTP server, the Cisco ATA updates its firmware with the new image_file_name. To contact the TFTP server, the Cisco ATA uses the TFTP server IP address that is contained within the value of the upgradecode parameter. Cisco ATA 186 and Cisco ATA 188 Analog Telephone Adaptor Administrator's Guide for SCCP (version 3.0) D-1

Section	Page
Cisco ATA 186 and Cisco ATA 188 Analog Telephone Adaptor Administrator’s Guide for SCCP (version 3.0)	1
Contents	3
Preface	11
Overview	11
Audience	11
Organization	11
Conventions	12
Related Documentation	16
Obtaining Documentation	16
Cisco.com	16
Documentation CD-ROM	17
Ordering Documentation	17
Documentation Feedback	17
Obtaining Technical Assistance	18
Cisco.com	18
Technical Assistance Center	18
Cisco TAC Website	18
Cisco TAC Escalation Center	19
Obtaining Additional Publications and Information	19
Cisco Analog Telephone Adaptor Overview	21
Overview of the Skinny Client Control Protocol	22
Hardware Overview	23
Software Features	25
SCCP Version	25
Voice Codecs Supported	25
Additional Supported Signaling Protocols	26
Other Supported Protocols	26
Basic Services	26
Fax Services	27
Pre-call and Mid-call Services	27
Pre-call Services	27
Mid-call Services	28
Installation and Configuration Overview	29
Installing the Cisco ATA	31
Network Requirements	32
Safety Recommendations	32
What the Cisco ATA Package Includes	32
What You Need	33
Installation Procedure	33
Power-Down Procedure	36
Configuring the Cisco ATA for SCCP	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 Cisco CallManager TFTP Server Environment	41
Basic Configuration Steps in a Non-TFTP Server Environment	42
Configuring the Cisco ATA Using a TFTP Server	43
Setting Up the TFTP Server with Cisco ATA Software	43
Configurable Features and Related Parameters	44
Creating a Cisco ATA Default Configuration File	45
Creating a Configuration File for a Specific Cisco ATA	47
Using atapname.exe Tool to Obtain MAC Address	49
Using Encryption With the cfgfmt Tool	49
Examples of Upgrading to Stronger Encryption Key	52
Configuring the Cisco ATA to Obtain its Configuration File from the TFTP Server	54
Using a DHCP Server	54
Without Using a DHCP Server	57
Voice Configuration Menu	58
Using the Voice Configuration Menu	58
Entering Alphanumeric Values	60
Resetting the Cisco ATA to Factory Default Values	60
Cisco ATA Web Configuration Page	61
Resetting the Cisco ATA Using Cisco CallManager	62
Upgrading the SCCP Signaling Image	63
Adding the Cisco ATA to the Cisco CallManager	65
Device Type Information	66
Adding Cisco ATAs Manually	66
Using the Cisco Bulk Administration Tool (BAT)	67
Using Auto-Registration	68
Survivable Remote Site Telephony	69
Using the Cisco IP Telephony Network Locale Option	69
Cisco ATA Configuration Parameter	69
Cisco IP Telephony Locale Installer Installation and Configuration	70
Using the Gratuitous ARP Feature	70
Parameters and Defaults	71
Configuration Text File Template	72
User Interface (UI) Security Parameter	73
UIPassword	73
Parameters for Configuration Method and Encryption	74
UseTFTP	74
TftpURL	74
AlttftpURL	75
EncryptKey	76
EncryptKeyEx	77
Network Configuration Parameters	78
DHCP	78
StaticIp	79
StaticRoute	79
StaticNetMask	80
DNS1IP	80
DNS2IP	81
VLANSetting	81
CA0orCM0 and CA1orCM1	82
EPID0orSID0 and EPID1orSID1	83
LBRCodec	83
MediaPort	84
Domain	85
Audio Configuration Parameters	86
AudioMode	86
NumTxFrames	87
Operational Parameters	87
CallerIdMethod	87
Polarity	89
FXSInputLevel	90
FXSOutputLevel	90
ConnectMode	91
SigTimer	93
OpFlags	94
TOS	95
Tone Configuration Parameters	96
Tone Parameter Syntax-Basic Format	97
Tone Parameter Syntax-Extended Formats	98
Extended Format A	98
Extended Format B	99
Recommended Values	103
Specific Tone Parameter Information	103
DialTone	103
DialTone2	104
BusyTone	104
ReorderTone	105
RingbackTone	105
CallWaitTone	106
AlertTone	106
Diagnostic Parameters	107
NPrintf	107
TraceFlags	108
SyslogIP	108
SyslogCtrl	109
CFGID-Version Parameter for Cisco ATA Configuration File	110
Parameters Not Used in SCCP that Appear on Web Page	110
Configuring and Debugging Fax Services	111
Using Fax Pass-through Mode	111
Configuring the Cisco ATA for Fax Pass-through mode	112
AudioMode	112
ConnectMode	113
Configuring Cisco IOS Gateways to Enable Fax Pass-through	114
Enable Fax Pass-through Mode	114
Disable Fax Relay Feature	116
Using FAX Mode	116
Configuring the Cisco ATA for Fax Mode	116
Configuring the Cisco IOS Gateway for Fax Mode	117
Debugging the Cisco ATA 186/188 Fax Services	117
Common Problems When Using IOS Gateways	117
Using prserv for Diagnosing Fax Problems	119
prserv Overview	119
Analyzing prserv Output for Fax Sessions	120
Using rtpcatch for Diagnosing Fax Problems	122
rtpcatch Overview	122
Example of rtpcatch	124
Analyzing rtpcatch Output for Fax Sessions	126
Using rtpcatch to Analyze Common Causes of Failure	128
rtpcatch Limitations	130
Upgrading the Cisco ATA Signaling Image	131
Upgrading the Signaling Image Via Cisco CallManager	132
Procedure for Upgrading all Cisco ATAs at Once	132
Procedure for Upgrading One Cisco ATA	133
Running the Executable	133
Upgrading the Signaling Image Manually	134
Preliminary Steps	134
Running the Executable File	134
Upgrade Requirements	135
Syntax	135
Upgrade Procedure	136
Confirming a Successful Signaling Image Upgrade	136
Using a Web Browser	137
Using the Voice Configuration Menu	137
Troubleshooting	139
General Troubleshooting Tips	139
Symptoms and Actions	140
Installation and Upgrade Issues	141
Restarting the Cisco CallManager	142
Capturing Debugging Information	143
Using System Diagnostics	144
Local Tone Playout Reporting	148
Obtaining Network Status Prior to Getting IP Connectivity	149
Obtaining Network Status After Getting IP Connectivity	150
DHCP Status HTML Page	151
Real-Time Transport Protocol (RTP) Statistics Reporting	151
The nptcap Tool	152
Frequently Asked Questions	152
Contacting TAC	154
How to Use Pre-call and Mid-call Services	157
Procedures for Using Pre-call Services	157
Access Voicemail	158
Change Your Pre-Call Service Access Code	158
Activate Call-Forward-All	158
Cancel Call-Forward-All	158
Redial	158
Speed Dial	159
Call Pickup	159
Group Call Pickup	159
MeetMe Conference	160
Procedures for Using Mid-call Services	160
Bellcore Style	160
Bellcore Style Call Transfer Procedure	160
Bellcore Style Conference Call Procedure	161
Cisco VG248 Style	161
Cisco VG248 Style Three-way Calling Procedure	161
Cisco VG248 Call Transfer Procedure	161
Cisco VG248 Conference Call Procedure	162
Cisco ATA Style	162
Cisco ATA Style Call Hold/Resume Procedure	162
Cisco ATA Style Call Transfer Procedure	163
Cisco ATA Style Conference Calling Procedure	163
Voice Menu Codes	165
Cisco ATA Specifications	169
Physical Specifications	169
Electrical Specifications	170
Environmental Specifications	170
Physical Interfaces	170
Ringing Characteristics	171
Software Specifications	171
Performing a Cross-Protocol Upgrade	173
Recommended Cisco ATA Tone Parameter Values by Country	175
Glossary	191

Match case Limit results 1 per page

D-1

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

OL-4652-01

APPENDIX

Performing a Cross-Protocol Upgrade

This section describes how to perform an upgrade from the SCCP signaling image to either the MGCP,

SIP or H.323 signaling images.

You can configure the Cisco ATA to automatically download a new signaling image that the

Cisco CallManager administrator has stored on the TFTP server. You do this by configuring the

parameter

upgradecode

in your Cisco ATA configuration file. For more information about setting up the

configuration file, see the

“Creating a Configuration File for a Specific Cisco ATA” section on

page 3-11

Syntax of upgradecode Parameter

upgradecode:3,0x301,0x0400,0x0200,tftp_server_ip,69,image_id,image_fil

_name

Definitions

•

The hexadecimal values that precede the tftp_server_ip variable must always be the values shown

in the syntax.

•

tftp_server_ip

is the TFTP server that contains the latest signaling image file.

•

image_id

is a unique 32-bit integer that differs with each upgrade. You can determine this 32-bit

integer value by using the build date on the image file name and prepending it with "0x". For

example, if the image_file_name is ata186-v2-14-020514a.kxz, then the build date is 020508a, and

the image_id is 0x020508a).

•

image_file_name

is the signaling upgrade-image file name. The image_file_name format is:

ata186-v{M}-{N}-{yymmdd}{a-f}{ext}

–

- M

is the major version number

–

- N

is the minor version number (always two digits)

–

- yymmdd

is a two-digit year, two-digit month, and two-digit day

–

- a-f

is the build letter (

- yymmdd

and

a-f

together form the build date of the image)

–

- ext

must be ".kxz" for upgrading from version 2.11 and below, and can be ".zup" for

upgrading from version 2.12 and up for the Cisco ATA186, but it

must

be ".zup" for upgrading

the Cisco ATA188.

Process

Whenever the Cisco CallManager administrator stores a new signaling image (denoted by a change to

the image_id) on the TFTP server, the Cisco ATA updates its firmware with the new image_file_name.

To contact the TFTP server, the Cisco ATA uses the TFTP server IP address that is contained within the

value of the

upgradecode

parameter.