Cisco MGCP IP Phone, 7940, 7960 Administrator's Manual

Download

Page 1

Corporate Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 526-4100

Cisco MGCP IP Phone Administrator Guide

Release 5.0 and Release 5.1 June 2003

Page 2

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS M ANUAL ARE SUBJECT TO CHA NGE WITHOUT NO TICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSI BILITY FOR THEIR APPLICA TION OF ANY PRODUCT S.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORT H IN THE INFORMATION PACKET T HAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP head er compressi on is an adap tation of a program developed by the Universi ty of C alifornia, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operatin g system. All rights reserved . Copyri ght © 1981 , Rege nts of the Uni versity of Calif ornia.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THE SE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAI M ALL WARRANTIE S, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NO NINFRINGEM ENT OR ARISING FROM A COURS E OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING , WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE S.

Cisco MGCP IP Phone Administrator Guide

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)

Page 3

iii

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

CONTENTS

Overview vii Who Should Use This Guide vii Objectives viii Document Organization viii Related Documentation viii Document Conventions ix Obtaining Documentation ix

Cisco.com x Documentation CD-ROM x Ordering Documentation x Documentation Feedback x

Obtaining Technical Assistance xi

Cisco.com xi Technical Assistance Center xi

Cisco TAC Website xii Cisco TAC Escalation Center xii

Obtaining Additional Publications and Information xii

CHAPTER

1 Product Overview 1-1

What’s New in This Release? 1-1 What Is Media Gateway Cont rol Protocol? 1-1 What Is the Cisco MGCP IP Phone? 1-2

BTXML Support 1-4 Cisco CallManager XML Support 1-4

Supported Features 1-5

Physical Features 1-5 Network Features 1-6 Codec and Protocol Support 1-6 Dialing and Messaging Features 1-7 Supported Protocols 1-7 Character Support 1-8

Page 4

Contents

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

CHAPTER

2 Installing the Cisco MGCP IP Phone 2-1

Safety Notices 2-1 Prerequisites 2-2 Connecting the Cisco MGCP IP Phone 2-2

Connecting to the Network 2-3 Connecting to Power 2-3 Using a Headset 2-4

Using the Cisco MGCP IP Phone with a Catalyst Switch 2-4

CHAPTER

3 Configuring the Cisco MGCP IP Phone 3-1

MGCP Commands 3-2 Using Configuration Files 3-2 Using the MGCP Phone Se ttings Button 3-11

In Release 4.2 or Lat e r 3-11

In Release 4.1 or Ear li er 3-11 Customizing the Cisc o MGCP IP Phone Ring Types 3-12 Viewing the Firm w a re Ve rs io n 3-12 Upgrading the Cisco MGCP I P Phone Firmware 3-13

Upgrading to Release 5.0 and Release 5.1 3-13 Upgrading from Release2.2 or Later Releases to Release4.0 3-14 Upgrading from Release2.1 or Earlier Releases to Release4.0 3-15 Upgrading from Older Releases to the Current Release 3-15 Dual Booting from SCC P or MGCP to Release 4.0 3-16

Performing an Image Upgrade and Remote Reboot 3-16

CHAPTER

4 Using the Cisco MGCP IP Phone 4-1

Using the Handset 4-1 Using the Speakerphone 4-1 Using the Headset 4-1 Adjusting the Handset, Speakerphone, and Headset Volume 4-2 Adjusting the Ringer Volume 4-2 Changing the LCD Contrast 4-2 Muting a Call 4-2

CHAPTER

5 Monitoring and Maintaining the Cisco MGCPIPPhone 5-1

Viewing Status Messages 5-6 Viewing Netw or k S ta tis tics 5-6

Page 5

Contents

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Verifying the Ethernet Statistics 5-7

APPENDIX

A Translated Safety Warnings A-1

Warning Definition A-1 Installation Warning A-2 Product Disposal Warning A-3 Lightning Activity Warning A-4 SELV Circuit Warning A-5 Circuit Breaker (15A) Warning A-6 TN Power Warn in g A-7

NDEX

Page 6

Contents

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Page 7

vii

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

This chapter describes the objectives and organization of the Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Re le ase 5.1 and explains how to find additional information on related products and services. This chapter contains the following sections:

• Overview, page vii

• Who Should Use This Guide, pa ge vii

• Objectives, page viii

• Document Organization, pag e viii

• Related Document ation , page vii i

• Document Conventions, page ix

• Obtaining Documentation, page ix

• Obtaining Technical Assistance, page xi

Overview

The Cisco MGCP IP Phone Re ference Guide provides info rmati on about how to setup, conn ect cable s to, and configure a Cisco MG CP IP phone 794 0 or 7960 (here after ref erred to as a Cisco MGCP IP phone). It also provides informa tion on how to configure settings an d options of the Cisco MGC P IP phone.

Who Should Use This Guide

Network engineers, syste m administ rators, or teleco mmunic ation engine ers shou ld use this g uide to learn the steps required to properly set up the Cisco MGCP IP pho ne on the netwo rk.

The tasks described are considered to be administration-level tasks and are not intended for end-users of the phones. Many of the tasks involve configuring network settings which could affect the phone’s ability to function in th e ne twork and re quir e an u nde rsta nding o f IP n etworki ng and tele pho ny co nce pts.

Page 8

viii

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Objectives

The Cisco MGCP IP Phone Admi nistrator Guide, Rel ease 5.0 and Release 5.1 provides necessary information to get the Cisco MGCP IP phone operati onal in a Voice-over-IP (VoIP) network.

It is not the intent of this administrator guide to provide information on how to implement an MGCP VoIP network. For information on implementing an MGC P VoIP network, refer to the documents listed in the “Related Documentation” section on page viii.

Note Many features available on your Cisco MGCP IP phone ar e deter mined by the c all agent (CA ) in your

network. Some features descri bed here may not be available through yo ur CA. Consul t your CA documentation for more information.

Document Organization

The chapter s in this docume nt ar e as fo llows:

• Chapter 1, “Prod uct Overview”—Gives an introduction to the Cisco MGCP IP phone.

• Chapter 2, “Insta lling the Cisco MG CP IP Ph one”—Provides information needed to install th e

Cisco MGCP IP phone.

• Chapter 3, “Configuring t he Cisco MGCP IP Phone”—Provides configuration information for the

Cisco MGCP IP phone.

• Chapter 4, “Usin g t he Cisco M GCP I P Ph one ”—Tells you how to use the Cisco M GCP I P p hon e.

• Chapter 5, “Monitoring and Maintaining the Cisco MGCP IP Phone”—Lists and describes

debugging commands and other commands that can be used to troubleshoot the phone and network.

• Appendix A, “Translated Safety Warnings”—Contains translated safety warnings for the

Cisco MGCP IP phone.

Related Documentation

The following is a list of related Cisco MGCP VoIP publications. For more information about implementing an MGCP VoIP network refer to the following publications:

• Cisco IP Phone 7960 an d 794 0 Serie s A t a Gl ance

• Regulatory Compliance and Safety Information for the Cisco IP Phone 7960, 7940, and 7910 Series

• Installing the Wall Mount Kit for the Cisco IP Phone

The following is a list of Cisco VoI P publica tions that provide info rmati on about im pleme nting a VoIP network:

• Cisco IOS Voice Library, Release 12.3

• Cisco IOS Voi ce Comm and R eference, Release 12.3

• Cisco IOS IP Configuration Guide, Release 12.3

• Cisco IOS IP Comman d R eference, Volume 1 of 3: Addressing and Services, Release 12.3

• Cisco IOS IP Comman d R efe rence, Volume 2 of 3: Ro uti ng Protocols, Relea se 12.3

• Cisco IOS IP Command Reference, Volume 3 of 3: Multicast, Release 12.3

Page 9

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Document Conventions

Note Be sure to consult your CA document ation for information on features that may be specific to your CA.

Document Conventions

This docume nt u s es the f ol lowing conventions:

• Commands and keywords are in boldface font.

• Arguments for which you supply values are in italic font.

• Elements in sq uare br acket s ([ ]) are optional .

• Alternative keywords are grouped in braces and separated by vertical bars (for example, { x | y | z }).

• Optional alternative keywords are grouped in brackets and separated by vertical bars (for example, [

x | y | z ]).

• Terminal sessions and informati on the system displa ys are in screen fo nt.

• Information you must enter is in boldface screen font.

Notes use the following conventions:

Note Means reader take note. Notes contain helpful suggestio ns or references to material not covered in the

publication.

Cautions use the following conventions:

Caution Means rea der be careful. In this situation, you might do something that could result in equipment

damage or loss of data.

Warn ings use the foll owing conventions:

Obtaining Documentation

Cisco provides several ways to obtain documentation, techn ical assistance , and other tec hnical resources. These sect ion s expla in h ow to obta in te chni cal infor ma tion fr om Ci sco Sy stem s.

Warning

This warning symbol means danger. You are in a situation that could cause bodily injury . Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. (To s ee translations of the warnings that appear in this publication, refer to the Appendix A “Translated Safety Warnings.”

Page 10

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Obtaining Docume ntation

Cisco.com

You can acc ess t he m ost c ur rent C isc o doc um ent ation on the World Wide Web at this URL :

http://www.cisco.com/univercd/home/home.h tm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco web sites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more curre nt than printed do cumentati on. The CD-R OM pack age is av ailable as a single unit or through an an nual su bscript ion.

Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:

http://www.cisco.com/go/subscription

Ordering Documentation

You can find ins truc tio ns for or de ring do cu ment atio n a t t his U RL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco doc umen tation in th ese ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from

the Networking Produ cts Market Pla ce:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number

DOC-CONDOCCD=) through the online Subscription Store:

http://www.cisco.com/go/subscription

• Nonregistered Cisco.co m u ser s can o rd er docum en tati on th rou gh a l oc al ac count r epre sen tative by

calling Cisco Systems Corpo rate Headqu arter s (Califo rnia, U.S.A. ) at 408 526-7208 or, elsewhere in North America, by calli ng 800 55 3-NE TS (6387).

Documentation Feedback

You can submit co mm ents el ec tronic all y on Cisc o.com . On the Cisco Doc ume nta tion h ome pag e, cl ick Feedback at the top of the page.

You can e-ma il your co mmen ts to bug-doc@c isco.c om.

Page 11

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Obtaining Technical Assistance

You can submit yo ur comm ents by mail by using the respon se card beh ind the fr ont cover of your document or by wri ting t o the fo llowing a ddr es s:

Cisco Systems Attn: Customer Docume nt Ordering 170 West Tasman Drive San Jose, CA 95134- 988 3

We appre ciate yo ur co mmen ts.

Obtaining Technical Assistanc e

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite o f in tera ct ive, networked servi ces th at let y ou ac cess Cisc o in for matio n, networking solutions, serv ices, pr ograms, an d resour ces at any time, fr om anywhere in the world.

Cisco.com provides a br oad r ange of fea tur es an d s er vice s to h elp you wi th th ese ta sks:

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and te st so ft war e pa ck ag es

• Order Cisco learning m ateri als and me rcha ndise

• Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisc o TAC w ebsite an d the Cisc o TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We ca tegoriz e Cisco TAC inquiries according to urgency:

• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities,

product installation, or basi c product configuration.

• Priority level 3 (P3)—Your network performance is degraded. Network func tionalit y is notice ably

impaired, but most business operations continue.

• Priority level 2 (P2)—Your production network i s severely degraded, affecting signi ficant aspec ts

of business operations. No workar oun d is available.

Page 12

xii

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Obtaining Additiona l Publications and Information

• Priority leve l 1 (P1)—Your production network is down, and a critical impact to business operations

will occur if se rvic e is n ot r esto red qui ckl y. No workaround i s available.

Cisco TAC Website

You can use the Cisco TA C website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clo ck access to onlin e tools, knowledge ba ses, and soft ware. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registere d user, and you cannot resol ve your tech ni cal issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/en/US/support/index.html

If you have Internet access, we recommend that you open P3 and P4 cases through t he Cisco TAC website so that y ou ca n desc ribe the s ituati on in your own wor ds an d a ttac h a ny nece ssar y files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To o bt ain a d ir ect or y of t oll- free C isco TAC telephone numbers for yo ur co unt ry, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC .shtml

Before calling, please check with your network operations center to determine the l ev el of Cisc o support services to which your company is entitled: for examp le, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product se rial numbe r.

Obtaining Additional Publications and Information

Information about Cisco products, technologies , and network solutions is available from various online and printed sources.

• The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as

ordering and custome r support ser vices. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wid e ran ge of n etworki ng pub l icatio ns. Cisco suggest s the se t itle s for new

and experienced users: Inter network ing Terms and Acronyms Dictionary, Internetworking Technology Hand boo k, In tern etwo rkin g Troubleshooting Guide, and the Inter netw ork ing De sign Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Page 13

xiii

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Obtaining Additional Publications and Information

• Pa cket magazine is the Cisco monthly periodical that provides industry professionals with the latest

information about t he field of net working. You can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html

• iQ Magazine is the Cisco monthly periodical that provides business leaders and decisi on makers

with the latest information about the networkin g industry. You can access iQ Magazine at this URL:

http://business.cisco. com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

• Internet Protocol Journal is a quarte rly journa l published by Cisco Systems for engin eering

professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

• Training—Cisco offers world-class networki ng training, with current offerings in network tra i ning

listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html

Page 14

xiv

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Preface

Obtaining Additiona l Publications and Information

Page 15

CHAPTER

1-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Product Overview

This chapter contains the following information about the Cisco MGCP IP Phone:

• What’s New in This Release?, page 1-1

• What Is Media G ateway Contro l Pro toco l?, pa ge 1-1

• What Is the Cisco MGCP IP Phone?, page 1-2

• Supported Features, page 1-5

What’s New in This Release?

Release 5.0

Cisco has added image authe ntica tion t o IP phone protoc ols, which me ans tha t tampe rin g of the bina ry image is not allowed before the image is downloaded to the phone. Any tampering with the image will cause the phone to fail the authentication process and reject the image. Once you download the Release

5.0 image, you cann ot downgrade t o any earlier re leas es. See “Upgrading to Release 5.0 and Release

5.1” section on page 3-13.

Release 5.1

Release 5.1 is the second rel ease of the si gned Cisc o IP phone ima ge. Rele ase 5.1 is compat ible with Release 5.0 an d la ter r ele ases . Re leas e 5 .1 addr esse s use r in terfa ce r es pons iveness and voice clipp i ng issues. See “Upgrading to Release 5.0 and Release 5.1” section on page 3-13.

What Is Media Gateway Control Protocol?

Media Gateway Control Protocol (M GC P) is the Int erne t E nginee ring Task Force (IETFs) standard f or multimedia conferencing over IP . MGCP is an ASCII-based, application-layer control protocol (defined in RFC 2705) that can be used to establish, maintain, and terminate calls between two or more endpoints.

Like other VoIP prot ocol s, M GC P is de signe d to addr ess the f unct ions of si gnal ing and sess ion management within a packet telephony network. Signaling allows call information to be carried across network boundaries. Session management provides the ability to control the attributes of an end-to-end call.

One aspect of MGCP tha t di ffers from othe r VoIP protocols is that MGCP relies on a contr ol server, or call agent (CA) to con trol ca ll progr essio n, t ones to a pply, and call cha rac teris tic s. MGCP endpo i nts carry out instructions fr om the CA, whic h control s how calls procee d.

Page 16

1-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter1 Product Overview

What Is the Cisco MGCP IP Phone?

MGCP provides the capabilities to allow a Control Server to:

• Determine the location of the target endpoint.

• Determine the media capabiliti es of t he tar get en dpoint. Using Session D escriptio n Protocol ( SDP),

MGCP determines the lowest level of common service between the endpoints. Conferences are established using only the media capab ilities that can be s upporte d by all endp oints.

• Determine the availability of the target en dpoint.

• Establish a session between the originating an d targ et endpoin t. If the ca ll can be com pleted, MGCP

establishes a session between the endpoints. MGCP also supports mid-call changes, such as the addition of another en dpo int to the confer ence or th e cha nging of a me dia ch aract eristi c or code c.

Note Conferences can consist of two or more users and can be established using multicast or multiple unicast

sessions. The term conference means an established session (or call) between two or more endpoints. In this document, the terms conference and call are used interchangeably.

MGCP is a client-server protocol. The CA handles all aspects of setting up calls to and from endpoints. CAs or control ser vers p rovide the fea ture ca pabi litie s tha t a part icula r e ndpo int w il l be a ble to use . Endpoints connected to different CAs will likely have a different set of features they can use. Since all of the call co ntrol fe atu re s a re i n t he con trol ser ver, each cont rol server vendor d ecide s wh ic h fe atu re s are most import ant , a nd the refor e differen t c ontr ol server vendor s di ffer in “essential features. ”

What Is the Cisco MGCP IP Phone?

The Cisco MGCP IP Phone provides voice communication over an IP network. It functions much like a traditional ph one, a llowing yo u to pl ac e an d r e ceive tele phone c alls .

The Cisco MGCP IP phon e work s wi th a third- pa rty CA t hat us es M GC P f or cal l c ontr ol a nd Basic Telephony eXtensible Markup Language (BTXML) for control of the phone’s displays an d feat ure k eys. This document d escri bes the ph one f eat ures t hat a re c ontr ol led by the ph one . Re fe r t o y our CA documentation for de scriptio ns of all othe r phone fea tures, di splays, and applicat ions.

Cisco MGCP IP phones are full-featured telephones that can be plugged directly into an IP network and used very much like a standard PBX telephone. The Cisco MGCP IP phone model terminals can attach to the existing in place data network infra structure, via 10BaseT/100BaseT interfaces on an Ethernet switch. When u sed w ith a voice -c apab le E the rn et s wi tc h (one that und er st ands Type of Service [ ToS] bits and can prioritize VoIP traf fic ), the phones eliminat e the need for a trad itional proprie tary telephone set and key system/PBX.

Figure 1-1 illustrates physical features of the Cisco MGCP IP phone:

Page 17

1-3

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 1 Product Overview

What Is the Cisco MGCP IP Phone?

Figure 1-1 Cisco MGCP IP Phone Physical Features

The main compone nts of the Ci sco M GCP IP Phone are de fined in Table 1-1.

Handset

Dialing

pad

Scroll

key

Function

toggles

On-screen mode button

button

Soft keys

LCD

Line or speed-dial

buttons

38007

Footstand adjustment

Volume buttons

Table 1-1 Cisco MGCP IP Phone Features

Feature Description

LCD screen The IP Phone “desktop,” which displays in format ion such as the time, date, your phone

number, caller ID, and line/call status. Refer to your call agent o r service provider documentation for the LCD functionality.

Lin e or speed- dial buttons Provide additional dialing capabilities, such as opening a new line, speed- dialing the number on

the LCD screen, or ending a c all. Refer to your c all a g ent o r se rvic e provider documentation for

line and speed-dial bu tton functionality. Footstand adjustment Adjusts the angle of the phone base. Soft keys Provide additional fu nct ion s f or yo ur phone . Ref er t o yo ur ca ll a ge nt o r ser vic e prov ide r

documentation for so ft keys f unct iona lity. i button Provides additional functions for your pho ne. Refe r to your call age nt or servi ce provider

documentation for i button func tionali ty.

Can provide online help for selected keys or features and network statistics about the active

call. Displays a descriptor of the key pressed dir ec tly after pressing the i button. For example,

pressing the i button, then up or down displays a screen instructing you how to scroll up and

down on the LCD Messages mode button Refer to yo ur ca ll age nt o r ser vice provi der doc ume nta tion for M essag es mode button

functionality. Directory mode button Ref er to yo ur cal l a gent o r ser vi ce provi der d oc ume nta tio n for D ire c tory mo de butt on

functionality. Services mode button Refer to your call agent or service provider documentation for Services mode button

functionality.

Page 18

1-4

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter1 Product Overview

What Is the Cisco MGCP IP Phone?

BTXML Support

Basic Telephony eXtensible Markup La ng uage is s uppo rt ed o n the Ci sco M GCP IP p hon e. B TX ML defines XML element s f or cont rol ling the user i nte rface o f an I P t ele phone . BTXM L desc ribe s wh at information is d ispl ayed on the scr een an d h ow the u ser provid es inpu t usi ng so ft keys and ha rd keys.

For information about crea ting an d using BTXML scripts on the Cisco MGCP IP pho ne, see the Cisc o IP Phone MGCP BTXML Version 2.0 Application Developmen t Guide.

Cisco CallManager XML Support

The Cisco MGCP IP phone supports customer-written Cisco CallManager XM L cards that can be accessed using buttons or softkeys on the phone. The se cards can provi de data such as stock quotes, calendars, and dir ect ory l oo kups. The XML c ards ca n be a ccesse d by the following me thod s:

• From the Services soft key, configured using the services_url pa ramet er.

• By pressing the directory button and selecting External Directory, configured using the

directory_url parame ter.

• The logo_url pa rame ter ena ble s the use r to downloa d a b i t-ma p t o b e use d as t he ph one lo go

(branding).

Refer to Chapter 3, “Configurin g the Cisco M GCP I P Ph one” for informati on about co nfiguring the se parameters.

The Cisco MGCP IP phone supports Cisco CallManger XML up to version 3.0. It does not suppo rt the XML objects added in Cisco CallManager XML ver sion 3.1:

• CiscoIPPhoneIconMenu

• CiscoIPPhoneExecute

• CiscoIPPhoneError

• CiscoIPPhoneResponse

The following exceptions apply to the Cisco MGCP IP phone:

Settings mode button Provides access to phone settings such as contrast and ring type and to network configuration

and status information.

Volume buttons Increase or decrease the volume for the currently active voice receiver: handset, headset, or

speakerphone. The volume keys also control the ringer volume (if onhook), and the contrast of

the LCD. Function toggles To ggle the heads et, mu te, a nd spea ker fun cti ons on a nd off. Scroll key Enables you to m ove among different opti ons disp lay ed on the LCD scr een. Dialing pad Press the dial ing pad buttons t o dia l a phon e num ber. Dialing pa d buttons work exactly li ke

those on your existing telephone. Refer to your call agent or service provider documentation for

any additional dialing pad functions. Handset Lift the handset and press the dialing pad numbers to place a call, answer a call, and operate

other phone fu nc tions.

Table 1-1 Cisco MGCP IP Phone Features

Feature Description

Page 19

1-5

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 1 Product Overview

Supported Features

• External directori es c annot be a ppend ed to the m ain list of di r ectori es u nder t he directory button.

If external directories are provisi oned fo r the Cisco MG CP IP phone , then they can be ac cesse d by pressing the directory button and selecting the External Directory optio n.

• The Cisco MGCP IP phone removes white space when the Cisco CallManager XML cards are

displayed. Multiple spaces are consolidated to a single space.

• Setting x and y coordinates for the Ci scoIPPho ne Im age obje ct is no t sup por ted. T he im ag e always

appears at location 0,0 . Center ing of the image is not supp orted if x and y are set to -1.

• The Cisco MGCP IP phone displays any valid title it receives. This differs from the Cisco

CallManager phones in th at th e Ci sco IPPho neGra phic Men u o bj ect d oes not d ispl ay a title even if it receives one and the CiscoIPPhoneImage ob ject displa ys the previous menu it em or “Services” rather than received titles.

• CallManager phones allow embedde d carriag e return s and line feeds i n menu items. In the

Cisco MGCP IP phone, carriage returns and line feeds are discarded.

• The Cisco MGCP IP phone always displays the full set of directory softkeys. For Cisco CallManager

phones, the softkeys can change depending on what type of object it receives. This is due to support for Cisco CallManager 3.0 .

• A parameter is sent along with the initial request for a Services or Directory URL which

differentiates the Cisco M GCP IP pho ne f rom o ther typ es of ph one s.

For more information a bou t usin g X ML on yo ur Ci sco M GCP IP p hon e, se e t he f ol lowing lin ks or documents:

• Cisco IP Phone Se rv ice fo rum at th e fo llowing U RL:

http://www.hotdispatch.com/cisco-ip-telephony

• Cisco Call Manager Services Developer Kit at the following URL:

http://www.cisco.com/warp/public/570/avvid/voice_ip/cm_xml/cm_xmldown.shtml

• Developing Cisco IP Phone Services by Darrick Deel, Mark Nelson, and Anne Smith, ISBN

1-58705-060-9

Supported Features

The MGCP phone supports th e following feat ures. Dep ending on the featur es that you r CA supports , some of these may not be available on your phone.

Physical Features

• Hearing-aid compatible handset

• Headset compatibility

• Integrated two-port Ethernet switch that allows the telep hone and a computer to share a single

Ethernet jack

• Direct connectio n t o a 10B ase T or 1 00Ba se T Et h erne t (RJ -45 ) n etwor k (ha lf- or f ull -dupl ex

connections are supp orte d)

• Large (4.25 x 3 in.) display with adjustable contrast

Page 20

1-6

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter1 Product Overview

Supported Features

Network Features

• Interoperability with third-party CAs.

• Up to six MGCP connections an d call appe aran ces.

• IP address assignment—Dyna mic Host Configurati on Protoco l (DHCP) client or ma nuall y

configured via a loca l se tup menu

• Network startup using D HCP a nd Trivial File Transfer Protocol (TFTP)

• Domain Name Syste m (D NS) : T he M GCP p hon e uses D NS lo okup s to loc ate i ts com mu nic ation

partners (for example, a TFTP server or a CA. If a CA is unreachable, the MGCP phone queries the DNS server for an alternate CA .)

• Dynamic DNS and TFTP servers: You can configure additional DNS and TFTP servers in the

configuration files. Upo n b ootup , the ph one first goe s to t he d efa ult T F TP ser ver t o downlo ad the configuration files. If a new dynamic TFTP server is specified in the files, the phone requests a new set of files from the s pecified server. If new DNS addresses are specified in the f iles, th e phone uses those addresses for l ookups.

• Telnet support—Allows the user to use telnet to connect directly to the Cisco MGCP IP Phone to

debug and troublesho ot th e p hon e. Se e Chap ter 3, “Configuring the Cisco MGCP IP Phone” for more information on configuratio n parameters.

• Ping support—Allows the user to use ping to see if a Cisco MGCP IP Phone is operational and how

long the response tim e is from the phon e.

• Traceroute support—Allows the user to use traceroute to see the path that a Cisco MGCP IP phone

traverses in the route to its desired destination.

• Remote reset suppo rt—Allows a service provider to reset a phone from a remote site. This feature

provides a key tool for res tart ing the p hone’s registration p roc ess w ith t he provi der’s call ag en t or proxy and for receiving a new or updated configuration or firmware load from a de signated TFTP server.

Codec and Protocol Support

• Basic phone servic e i ncl uding MG CP 0 .1 a nd MGC P 1. 0 head er s

• G.711 u-law codec

• G.711 a-law codec

• G.729a codec

• DTMF out-of-ban d f or G .7 29a c od ec c ompl ian t to RFC 2833

• Local Connection O ptio ns ( LC Os):

–

G.729a codec: supports low-bandwidth access for multitenant deployment

–

Voice activity detection (VAD) support

–

Type o f ser vic e (ToS) bit for Real-Time Transport Protocol ( RTP)

• XML support

• Hypertext Transfer Protocol ( HTT P)—The phone contai ns limited sup port fo r HTTP 1.1. The

phone uses HTTP to retrieve Call Manager XML files.

Page 21

1-7

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 1 Product Overview

Supported Features

Dialing and Messaging Features

• Message Waiting Indication—Lights to indicate that a new voice message is in a subscriber’s

mailbox. If the subscribe r listens to the me ssage but does not save or delete the messa ge, the li ght remains on. If a subscriber listens to the new message or messages, an d saves or deletes them , the light goes off. The message waiting indicator (MWI) is controlled by the voicemail server. The indication will be saved over a phone upgrade or reboot.

• Notified entity: A CA can direct an endpoint to send notify messages to an alternate destination.

• Call waiting, call transfer, call forward (unconditional, busy, no answer), announcement, music on

hold, and volume control. (Must be sup ported by the CA.)

• Three-way calling using an exter nal multip oint cont rol unit ( MCU). (Must b e supported b y the CA.)

Supported Protocols

The Cisco MGCP IP phone supports the following standard protocols:

• Domain Name S yste m (DNS )—Used in the Internet for tr anslating names of network nodes into

addresses. The MGCP IP Phone uses DNS to resolve the host name s of endpoi nts to IP addresse s.

• Dynamic Host Control Pr otocol (D HCP)—Used to dynamically allocate and assign IP addresses.

DHCP allows you to move network devices from one subnet to another without admi nistrative attention. If using DHCP, you can connect Cisco MGCP IP phones to the network and become operational withou t having to man ua lly a ssign an I P addr ess a nd ad di tiona l ne twor k par amet ers.

The Cisco M GCP IP p hon e co mp lie s wi th th e D HC P sp ec i ficatio n s d oc ume nte d in RF C 2131. By default, Cisco MGCP IP phones are DHCP-enabled.

• Internet Control Message Protocol (ICMP)—A network layer Internet protocol that enables hosts to

send error or con trol mess age s to oth er ho sts. ICMP al so provid es othe r i nfo rmati on rel evant to IP packet processing.

The Cisco MGCP IP phone supports IC MP as it is docume nted in RFC 792.

• Internet Protocol (IP)—A network layer protocol that sends datagram packets between nodes on the

Internet. IP also provides features for addressing, type-of-service (T oS) specification, fragmentation and reassembl y, and security.

The Cisco MGCP IP phone supports IP as it is defined in RFC 791.

• Real-Time Transport Protocol (RTP)—Transports re al -tim e d ata ( such a s voice da ta ) over dat a

networks. RTP also has the ability to obtain Quality of Service (QoS) information. The Cisco MGCP IP p hon e supp orts RTP as a media chan ne l.

• Session Description Protocol (SDP)—An ASCII-based protocol that describes multimedia sessions

and their related sche duling info rmat ion. The Cisco MGCP IP p hon e uses SD P for se ssion desc ripti on.

• Simple Network Time Protocol (SNTP)—Synchronizes co mputer clocks on an IP network. The

Cisco MGCP IP phones use SN TP for the ir d ate a nd time suppo rt .

• Transmission Control Protocol (TCP)—Provides a reliable byte-stream transfer service betwee n two

endpoints on an Intern et . T he Ci sco IP Phone 796 0 su pport s TC P for Telnet and HTTP sessions.

• Triv ial File Transfer Protocol (TFTP)—Allows files to be transferred from one co mputer to an other

over a network. The Cisco MGCP IP phone uses TFTP to download configuration files and software updates.

Page 22

1-8

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter1 Product Overview

Supported Features

• User Datagram Pr ot ocol (U DP )—A simple protocol that exchanges data packets without

acknowledgments or guaranteed delivery. MGCP can use UDP as the underlying transport protocol. If UDP is used, retransmissions are used to ensure reliability.

Character Support

The Cisco MGCP IP p hon e supp orts the IS O 885 9-1 Lati n1 c ha racters. T he f oll owing langua ges a re supported:

French (fr), Spanish (es), Cata lan (ca), Basque (eu) , Portu guese (pt ), Italia n (it), Alba nian (sq) , Rhaeto-Romanic (rm), Dutch (nl) , German (de), Danish (d a), Swedish (sv), Nor wegian (no), Finnish (f i), Faroese (fo), Icelandic (is), Irish (ga), Scottish (gd), English (en), Afrikaans (af) and Swahili (sw).

The following languages ar e not supp orted: Zulu (zu) and other Bantu languages usi ng Latin Ext ended -B letter s, Arabi c in North Afri ca, and

Guarani (gn) missing GEIUY with ~ tilde.

Note The info key text and the Settings menu are in English. These items are built into the phone image and

cannot be ch an ged.

ISO 8859-1 Latin1 chara cters ca n be used in th e following are as:

• Caller ID informa ti on. When a n MGCP me ssage is re ceived wit h IS O 88 59- 1 L at in1 c hara ct er s in

the caller ID strings, those caller ID strings are displayed on the Cisco MGCP phone's LCD screen with the correct ISO 8859-1 Latin1 charac ters.

• Services menu applications written in CMXML. The customer can develop language-specific

applications for a pa rticular region. For example, an ap plication that displayed the current weath er in Sweden using Swedish language characters can be displayed on the Cisco MGCP IP phone. If the customer de velo ps the same applicati on for a Sp anish t ow n, they could tr anslat e the applica tion into Spanish.

• Call control displays (external MGCP XML card deck). The XML deck used for MGCP call control

is downloaded to the p hone, a nd t hose XML c ards ca n be tra nsla ted int o t he l oca l l angua ge.

Note The Info key text and t he t est conta ine d in t he Se ttin gs menu ar e displa yed i n Eng lish .

• Line key labels. Line key la bels are set usin g a n M GC P m essage th at s et s the lab el to t he s tr ing

provided. Strings containing ISO 885 9-1 Lati n1 charact ers are displ ayed pro perly.

• Soft key labels. Soft key labels are set usi n g XML ca r ds. XM L ca rds, inc luding c a ll con trol s car ds

and services applications, can provide soft keys with ISO 8859-1 Latin1 characters.

Page 23

CHAPTER

2-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Installing the Cisco MGCP IP Phone

This chapter contains the following sections:

• Safety Notices, pa ge 2-1

• Prerequisites, page 2-2

• Connecting the Cisco MGCP IP Phone, page 2-2

• Using the Cisco MGCP IP Phone with a Catalyst Switch, page 2-4

Safety Notices

Read the following safety considerations before installing or using the Cisco MGCP IP phone. Translations of the warnings are available in Appendix A, “Translated Safety Warnings.” Additionally, the Re gulatory Compliance and Safety Information for the Cisco IP Phone 7960, 7940, and 7910 Series includes regulator y com pl ian ce infor ma ti on ab out you r p hon e, whi ch you r s ystem a dm ini stra tor can review.

Warning

Read the installation instructions before you connect the system to its power source.

Warning

Ultimate disposal of this product should be handled according to all national laws and regulations.

Warning

Do not work on the system or connect or disconnect cables during periods of lightning activity.

Warning

To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone network-voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some LAN and WAN ports use RJ-45 connectors. Use caution when connecting cables.

Page 24

2-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 2 Installing the Cisco MGCP IP Phone

Prerequisites

The following warnin g app lie s w hen yo u u se a n exte rnal p ower suppl y.

Warning

This product depends on the building installation for short-circuit (over current) protection. Ensure that a fuse or circuit breaker no larger than 120 VAC, 15A U.S. (240 VAC, 10A international) is used on the phase conductors (all current-carrying conductors).

Warning

The device is designed to work with TN power systems.

Caution The Cisco MGCP IP Ph one is inop erab le durin g a power outage if it is n ot support ed by an

uninterruptible power supply (UPS) wh en using e ither a loca l tr an sforme r or inline power on the LA N. This affects your ability to reac h 911.

Prerequisites

For the Cisco MGCP IP pho ne t o successfu l ly o per ate a s an MG CP end point in y our networ k, your network must meet t he fol lowing re qu irem ent s:

• A working IP network is established. For more information about configuring IP, refer to Cisco IOS

IP Configuration Guide, Rele ase 12. 3.

• VoIP is configured on your Cisco routers. For more information about configuring VoIP, refer to the

Cisco IOS Voi ce Configuration G uide, Release 12.3 for th e appropr iate acce ss platfo rm.

• VoIP gateways are configured for MGCP.

• A TFTP server is active and contains the latest Cisco MGCP IP Phone firmware image in its root

directory.

• Your CA is configured and c ommunica ting with th e Cisco MGCP IP Phones.

Connecting the Cisco MGCP IP Phone

The Cisco MGCP IP phone has connections for connecting to the data network, for providing power to the phone, and for connecti ng a headset to the phone. Fi gure 2-1 illustrates the connections on the Cisco MGCP IP phone.

Page 25

2-3

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 2 Installing the Cisco MGCP IP Phone

Connecting the Cisco MGCP IP Phone

Figure 2-1 Cisco MGCP IP Phone Cable Connections

Connecting to the Network

The Cisco MGCP IP p hone ha s two RJ-45 ports that each support 10 /100 Mbps half - or full-dup lex Ethernet conne ctio ns t o exter nal devices—network port (labeled 10 /100 SW) and ac cess port (l abeled 10/100 PC). You can use either Category 3 or 5 cabling for 10 Mpbs connections, but use Category 5 for 100 Mbps connect ions. On bo th t he n etwor k port and acc ess port , use f ull -dupl ex mode to avoid collisions.

Network Port (10/100 SW)

Use the network port to connect the phone to the network. You must use a straight-through cable on this port. The phone can also obtain inline power from the Cisco Catalyst switch over this connection. See the “Connecting to Power” section on page 2-3 for details.

Access Port (10/100 PC)

Use the access port to connect a network device, such as a computer, to the phone. You must use a straight-through cable o n thi s port .

Connecting to Power

The Cisco MGCP IP phone can be powered by the following sources:

• External power source—Optional Cisco AC adaptor and power cord for con necting to a standa rd

wall receptacle.

• WS-X6348-RJ45V 10/100 switching module—Provides inline power to the Cisco MGCP IP phone

when connected to a Ca ta lyst 3500, 4 000 , or 600 0 fa mily 10/10 0BASE-TX sw itchi ng modu le. This module send s power on pin s 1 & 2 an d 3 & 6 .

Handset

port

Headset

port

Cisco IP phone (rear view)

62472

Power

outlet

RS-232 port

(optional power

cable)

AC adapter

(-48VDC)

Access port

(

10/100 PC

)

Network port

(

10/100 SW

)

Page 26

2-4

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 2 Installing the Cisco MGCP IP Phone

Using the Cisco MGCP IP Phone with a Catalyst Switch

• WS-PWR-PANEL—Power patch panel provides power to the Cisco MGCP IP phone which allows

the Cisco MGCP IP pho ne t o be conn ec ted to existing Ca taly st 40 00, 5000 , and 6 000 fami ly 10/100BASE-TX switching modules.

This module sends p ower on p in s 4 , 5, 7, and 8.

• WS-X4148-RJ45V—48 port 10/100 Eth erne t w ith i nli ne p ower modu le for t he C ata lyst 4006 .

• WS-X4095-PEM—VoIP DC Power Entry module for the Catalyst 4006.

• WS-X4608-2PSU and WS-X 460 8—External -48V DC power shelf common equipment for the

Catalyst 4006 with two AC-to-DC PSUs and one empty bay for redundant option and the 110V 15A AC-to48V DC PSU redundant o ption for the power sh elf

• WS-C3524-PWR-XL-EN—Catalyst 3524-PWR XL switch

Note Only the network port (labeled 10/100 SW) supports inline power from the Cisco Catalyst switches.

For redundancy, you can use the Cisco AC adapte r even if you are usi ng inl ine power f rom th e Cisco Catalyst switches. The Cisco MGCP IP phone can share the power load being used from the inline power and external power source. If either the inline power or the externa l power go es down, t h e phone can switch entirely to the other power source.

T o use this redundancy feature you must set the inline power mode to auto on the Cisco Catalyst switch. Next, connect the un-powered Cisco MGCP IP phone to the network. After the phone powers up, connect the external power supply to the phone.

Using a Headset

The Cisco IP Phone 7 960 sup por ts a f our or six -w ire hea dset jack. Sp eci fically, the Cisco MGCP I P phone supports the foll owing Plan tronic s h eadse t m odel s:

• Tristar Monaural

• Encore Monaur al H91

• Encore Binaura l H 101

The Volume and Mute controls will also adjust volume to the earpiece and mute the speech path of the headset. The headset activation key is located on the fr ont of the Cisc o MGCP IP phone.

Note When using a headset, an amplifier is not required. However, a coil cord is required to connect the

headset to the headset port on the back of your Cisco IP Pho ne 7940/7960. For information on ordering compatible headse ts a nd coi l co rds f or the Cisc o IP p hone 79 40/ 79 60, se e http://cisco.getheadsets.com or http://vxicorp.com/cisco.

Using the Cisco MGCP IP Phone with a Catalyst Switch

To function in the IP telephony network, t he Cisco MGCP IP phone must be connected to a networking device, such as a Catalyst switch, to obtain network connectivity.

The Cisco MGCP IP phone has an internal Ethernet switch, which enables it to switch traffic coming from the phone, a cce ss port , a nd the networ k p ort.

Page 27

2-5

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 2 Installing the Cisco MGCP IP Phone

Using the Cisco MGCP IP Phone with a Catalyst Switch

If a computer is connected to the access port, packets traveling to and from the computer and to and from the phone share t he sa me physi cal lin k to the swi tch and the same port on t he sw itch .

This configuration has these implications for the VLAN configuration on the network:

• The current VLANs might be configure d on an IP subnet ba sis, and add itional IP addresse s might

not be available to assign the pho ne t o a por t so tha t i t be long s to the same su bnet as o ther devices (PC) connected to the same port.

• Data traffic present on t he V LAN supp ort ing ph ones mi ght reduc e t he q ua lity of VoIP traffic.

You can resolve these issues by isolating the voice traffic onto a separate VLAN on each of the ports connected to a p hon e. T he swi tch port configure d f or conne c ting a p hone would have separa te VLAN s configured for ca rr ying :

• Voice traffic to and from the Cisco MGCP IP phone (auxiliary VLAN)

• Data traffic to and from the PC connected to the switch through the access port of the Cisco MGCP

IP phone (native VLAN)

Isolating the phones on a separate, auxiliary VLAN increases the quality of the voice traffic and allows a large number of phones to be added to an existing net work whe re there are not enough IP address es.

For more information, refer to the documentation included with the Cisco Catalyst switch or available online at the following URL:

http://www.cisco.com/univercd/home/index.htm

Page 28

2-6

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 2 Installing the Cisco MGCP IP Phone

Using the Cisco MGCP IP Phone with a Catalyst Switch

Page 29

CHAPTER

3-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Configuring the Cisco MGCP IP Phone

This chapter d escrib es supp orted fe atu re s on the Ci sco MG CP p hon e an d i nfor ma tio n abo ut how to configure some features . Consult your call age nt (CA) doc ument ation fo r additio nal configurat ion information.

This chapter includes the following sections:

• MGCP Commands, page 3-2

• Using Configuration Files, page 3-2

• Using the MGCP Pho ne Set tings B ut ton, page 3-11

• Customizing the Ci sco M GCP I P Ph one R ing Types, page 3-12

• View ing the Firmware Version, page 3-12

• Upgrading the Cisco MGCP IP Phone Fir mware, page 3-13

• Performing an Imag e Upgrad e and R emote Reboot, pa ge 3-16

The Cisco MGCP IP phone can be con figured using the fol lowing methods:

• The CA configures t h e pho ne thr ough M GCP c om mand s .

• The MGCP phone co mmu ni cat es with a Dy nam ic H ost C onfigurat ion Pr otoc ol ( D HCP) se r ver to

obtain configuration informa tion at star tup.

• You configure some set tings by using teln et to connec t to your Cisc o MGCP IP phone an d ente r

commands in a term ina l wi nd ow. You can also connec t an ASCI I t ermi n al to your p hone’s console port to enter the same commands.

• Configuration files on the TFTP server that specify settings are downloaded by your phone at

startup.

• You configure some fe atures using the setti ngs button on your MGCP pho ne.

Note This document d oes not desc ribe con figurat ion of the Ci sco MG CP IP pho ne us ing th e CA b ec ause

configuration procedures depend on the CA capabilities and vary by ve ndor.

Page 30

3-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

MGCP Commands

The Cisco MGCP IP p hon e supp orts the MG CP com mand s shown in Table 3-1:

Using Configuration Files

You can use the f ollowing t wo con figuration files to spe cif y s ettings fo r y our Cisco M GCP IP pho ne :

• MGCDefault.cnf—The default configuration file. Use this file to configure the call agent address,

time, and other global parameters.

• MGCmacaddress.cnf—The use r configurati on file. The MAC address specifies the har dware

address of the Cisco MGCP IP phone and is not configurable . Use this file to specify t he phone prompt, phone password, an d time zo ne (for example , if a CA covers an area w ith mult iple time zones). You can also spec ify a differen t se t o f eXten si ble Mar kup L angua ge ( X ML) ca rd s fo r t he phone. For example, you may want to contr ol which X ML servi ces are available on each ph one; managers may have different features on their phon es than em ployees do. You can also specify whether you wan t a spec ific p hone to u se a differen t i mag e ver sio n.

Note The values in the user configuration file take precedence because that file is process ed last.

Values in this file override what is in the default configuration file .

If you use configura tion files, the OS7 9XX .TXT file no l ong er c on trols th e ima ge u sed by t he p hone . The OS79XX.TXT file controls the image only if you change protocols (SIP to MGCP , or MGCP to SIP). Image version and upgradi ng is done throug h the im age_versi on configurat ion para meter in the configuration files.

Upon startup, the phone attempts to download both files. If neither file exists, a TFTP timeout occurs after approximatel y 9 se cond s pe r file. If t he files exist, they are parse d and pro cessed.

Note Both files can use the same values or contain empty values. If the files have empty values, the

Cisco MGCP IP phon e boo ts usi n g th e de fault values for som e of the para meter s.

Table 3-1 MGCP Commands

Command Description Direction

Notification Request Specifies events that generate notifications to the CA. CA to phone Create Connection Creates an RTP connection. CA to phone Modify Connection Modifies an ex isting RTP connection. CA to phone Delete Connection Deletes an endpoint RTP connection. CA to phone Audit Endpoint Queries endpoint status. CA to phone Audit Connection Queries connection status. CA to phone Restart in Progress Notifies the CA of the endpoint’s service state change. Phone to CA Endpoint Configuration Specifies encoding for aud io signals. CA to phone Notification Indicates event occurrences. Phone to CA

Page 31

3-3

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

These configuration files are not require d; however, it takes longer (approximately 20 secon ds) for the Cisco MGCP IP phone to boot because it is waiting for the timeout on the TFTP server.

Table 3-2 shows the default MGCP IP Phone configuration file parameters in alphabetical order. All

parameters are opti onal ; t he p hon e boo ts w it h th e de fault o r exis ti ng fl as h co nfigura tion. O nly image_version is required to upgrade to a new image.

Table 3-2 Default MGCP Configuration File Parameters

Parameter Description

date_format The format to use for dates. Valid values are:

• M/D/Y—Mon th/ day/ye ar

• D/M/Y—Day/ month/year

• Y/M/D—Year/month/day

• Y/D/M—Year/day/month

• Y-M-D—Year-month- day

• YY-M-D—4-digit year-month-da y

The default is M/D/Y.

directory_url URL of the external directory s erver . This URL is ac cessed when the Directory

key is pressed and the External Directory option is selected. For example, use directory_url : “http://10.10.10 .10 /Cisco S ervi ces/D ire ctor y.asp”.

dst_auto_adjust Whether or not daylight saving time (DST) is automati cally adju sted on the

phones. Va lid values are 0 (di sable au tomat ic DST ad justme nt) or 1 (enabl e automatic DST adjustment). The default is 1.

dst_offset Offset from the phon e’s time when DST is in effect. When DST is over, the

specified offset is no longer applied to the phone’s time. Valid values are hour/minute, -h our/ minute , +hour /mi nute , ho ur, -hour, and +hour.

dst_start_day Day of t he m onth on w hich D ST b egins.

Valid values are 1 throug h 31 for the da ys of the month or 0 wh en spec ifying relative DST to specify that this field be ignored and that the value in the dst_start_day_of_ week para meter be use d instead.

dst_start_day_ of_we ek Day of the we ek on whi ch DST b egins.

Valid values ar e Su nday o r Sun , Mon da y or Mon, Tuesday or Tue, Wednesday or Wed, Thursday or Thu, Friday or Fri, Saturday or Sat, or Sunday or Sun or 1 through 7 with 1 being Sunday and 7 being Saturday. When specifying the name of the day , the v alue is not case -sensiti v e. In the United States, the def ault v alue is Sunday.

dst_start_month Month in which DST starts. Valid values are January, February, March, April,

May, June, July, August, Septem ber, October, November, and December or 1 through 12 with January being 1 and December being 12. When specifying the name of a month, the value is n ot case-sens itive. In the United States, the de fault value is April.

dst_start_time Time of day on which DST begins. Valid va lues are hour/minute (02/00) or hour

(02:00). In the United States, the default value is 02:00.

Page 32

3-4

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

dst_start_week_of_month Week of month in which DST begins.

Valid values are 1 through 6 and 8 with 1 being the first week and each number thereafter being subsequent weeks and 8 specifying the last week in the month regardless of which we ek the last week is. In the United States, the def ault v alue is 1.

dst_stop_day Day of the mont h on w hich D ST end s.

Valid values are 1 throug h 31 for the da ys of the month or 0 wh en spec ifying relative DST to specify that this field be ignored and that the value in the dst_stop_day_of_w ee k p aram eter be us ed inste ad.

dst_stop_day_of_w eek Day of the we ek on whi ch DST end s .

Valid values ar e Su nday o r Sun , Mon da y or Mon, Tuesday or Tue, Wednesday or Wed, Thursday or Thu, Friday or Fri, Saturday or Sat, or Sunday or Sun or 1 through 7, with 1 being Sunday and 7 being Sat urday. When specifying the name of the day , the v alue is n ot case-sensiti v e. In the Uni ted States, the d efault value is Su n da y.

dst_stop_month Month in which DST ends. Valid values are January, February, March, April,

May, June, July, August, Septem ber, October, November, and December or 1 through 12 with January being 1 and December being 12. When specifying the name of a month, the v alue is not case-sensiti ve. In the United States, the def ault value is October.

dst_stop_time Time of day on which DST ends. Valid valu es ar e ho ur/m in ute (0 2/00) or hour

(02:00). In the United States, the default value is 02:00.

dst_stop_week_of_month Week of month in which DST ends.

dtmf_avt_payload Payload type for A VT packets. Possible range is 96 to 127. If the value specified

exceeds 127, the phone will default to 101.

dtmf_outofband Whether to generate the out-of-band signaling (for tone detection on the IP side

of a gateway) and if so, wh en. The C is co M GCP I P ph one s uppo rts out-of-bound signaling via the AVT tone method. Valid values are:

• none—Do not gener ate DTM F digits out- of-ba nd.

• avt—If requested by the remote side, generate DTMF digits out-of-band

(and disable in- band DTM F si gnal ing ); ot herw ise , do not g ene rate DTM F digits out-of-band.

• avt_always—Always generate D TMF digi ts out-of-ba nd. This opt ion

disables in -band DTMF signaling.

The default is avt.

Table 3-2 Default MGCP Configuration File Parameters (continued)

Parameter Description

Page 33

3-5

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

dyn_dns_addr_1 You can sp ec ify the I P addr es s of a n ew dynam ic DNS. I f a new DNS i s

specified, it is used f or an y f urther DN S reques ts after the pho ne uses the init ial DNS address when it boots. The DNS addresses are used in the follo wing order:

1. dyn_ dns_ad dr_1 (if pre sent)

2. dyn_ dns_ add_2 ( if p re sen t)

3. DNS Server 1

4. DNS Server 2

5. DNS Server 3

6. DNS Server 4

7. DNS Server 5

The dynamic DNS address is not store d in Flash memo ry. Only dotted IP addresses are accept ed. This value can be clea red by remov ing it from the config

file or changing its value to a null value “” or “UNPROVISIONED”. dyn_dns_addr_2 You ca n spec ify a sec ond dyna mic D NS se rver to b e use d for D NS req ue sts. dyn_tftp_addr You can specify the IP address of a new dynamic TFTP server. After initially

querying the default TFTP server, the phone will re-request the default and

MAC-specific configuration files from th e new TFTP se rver. The dynamic

TFTP server is not stored in Flash m emory. Only dotted IP addresses are

accepted. This value can be cleared by removing it from the config file or

changing its value to a null value “” or “UNPROVISIONED”. http_proxy_addr The IP address of the HTTP proxy server. You can use either a dotted IP address

or a DNS name (a record only). http_proxy_port The port num ber of the HT TP proxy port . The default is 80. image_version Firmware version that the Cisco MGCP IP phone should run. Enter the name of

the image version (as it is released by Cisco). Do not enter the extension. You

cannot change the image version by changing the file name because the version

is also built into the f ile header. Trying to change th e image vers ion by changin g

the file name will cause the f irmware to f ail when it compare s the versio n in the

header against the file name. language This is an optional param eter for future use. English is the only value that is

currently supported. logo_url Location of the company logo file. This logo appears on the phone display. The

background space allocated for the image is 90 x 56 pixels. Images that are

larger than this will automatically be scaled down to 90 x 56 pixels. The

recommended file size for the image is 5 to 15k. For example, use log o_url:

“http://10.10 .10 .10/co mpanylo go.bmp ”.

Note This parameter supports Windows 256 color bitmap forma t only.

CMXML PhoneImage obje cts are not supp orted for this parame ter. Using anything other th an a Windows bitmap (.bm p) file ca n ca use

unpredictable resul ts. mgcp_gw_controller IP address of CA. mgcp_input_port Port on which the phone liste ns. The defau lt is 24 27.

Table 3-2 Default MGCP Configuration File Parameters (continued)

Parameter Description

Page 34

3-6

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

mgcp_output_por t Port on which the the phone tra nsmits. The default is 2427 . nat_enable Use 0 to disable NAT and 1 to enable NAT. Default is 0. If NAT is enabled, the

Session Description Protoc ol (SDP ) messa ge uses the nat _addr ess a nd an RTP port between the star t_media _port and the end_me dia_po rt range in the C and M fields. All RTP traffic is sourced from the port advertised in the SDP.

nat_address The WAN IP address of the NAT or firewall server. You can use either a dotted

IP address or a DN S n am e (a reco rd only ). phone_password Password to be used for console or telnet access. The default password is cisco. phone_prompt Prompt to be displayed when using telnet or console access. The default phone

prompt is “MGCP Phone.” services_url URL of the services BTXML files. This URL is accessed when the Services

button is pressed. For example, use services_url:

“http://10.10.10.10/CiscoServices/Services.asp” sntp_mode Mode in which the phone will listen for the SNTP server. Valid values are

unicast, multicast, anycast, or directedbroadcast. See sntp_server IP address of the SNTP server from which the phone will obtain time data. If

the SNTP server is set to 0 or not set, the MGCP software defaults the SNTP

server address to t he a ddress of the C A.

See Table 3-3 for more i nfor ma tio n. telnet_level Enables Telnet for the phone.

Valid values are:

• 0 — Te lnet is disabled

• 1 — Telnet is enabled, no privilege d commands

• 2 — Telnet is enabled and privileged commands can be execute d

The default value is 0. tftp_cfg_dir Path to the TFTP subdirectory in which phone-specific configuration files are

stored.

Note Exists only in the MGCDefault.cnf file.

time_format_24hr Whether a 12 or 24-hour time format is displayed by default on the phones’ user

interface. Valid values are:

• 0—Th e 12- hou r for mat is di spla yed by defau lt but c an be ch ang ed t o a

24-hour format via the phon e’s user interface.

• 1—Th e 24- hou r for mat is di spla yed by defau lt but c an be ch ang ed t o a

12-hour format via the phon e’s user interface.

• 2-The 12-hour fo rm at is di spla yed an d c anno t be c han ged t o a 24 -ho ur

format via the phone's user interface.

• 3—Th e 24- hou r forma t i s displ ayed a nd can not be cha nged t o a 1 2-h our

format via the pho ne’s user interface.

The default value is 1.

Table 3-2 Default MGCP Configuration File Parameters (continued)

Parameter Description

Page 35

3-7

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

Table 3-3 lists the actions that take place when a valid IP address is specified in the sntp_server

parameter.

Table 3-4 shows the abbreviations for the time_zone parameter.

time_zone Time zone in which the phone is located. Vali d values are the time zo ne

abbreviations shown in Table 3-4. These ab breviat ions ar e case sensit ive and must be in all capital letters.

tos_media Type of Service (ToS) level for the media stream being used. Valid values are:

• 0 (IP_ROUTINE)

• 1 (IP_PRIORITY)

• 2 (IP_IMMEDIATE)

• 3 (IP_FLASH)

• 4 (IP_OVERIDE)

• 5 (IP_CRITIC)

The default is 5.

use_mac_name Specifies whether to use the IP add ress or M AC address in the end poi nt na me.

By default, the IP address is used. Valid values are:

• 0—IP addre ss

• 1—MAC address

xml_card_dir Specifies the dire ctory to use fo r retri e ving th e XML car ds f ile. The bas e for the

directory is the base TFTP server directory. This field is limited to 64 characters.

xml_card_file The file name of the XML card s. This field is limited to 20 characters.

Table 3-2 Default MGCP Configuration File Parameters (continued)

Parameter Description

Table 3-3 Actions Based on sntp_mode When the sntp_server Parameter is Set to an IP Address

sntp_server = 192.168.1.9

sntp_mode= unicast

sntp_mode= multicast

sntp_mode= anycast

sntp_mode= directedbroa dcast

Sends

SNTP req ues t to th e SNTP server.

Nothing. When in multicast mode,

SNTP requests are not sent.

SNTP request to the SNTP server.

SNTP packet to the SNTP server.

After the first SNTP response is received, the phone switches to multicast mode.

Receives

SNTP response from the SNTP server and ignores responses from other SNTP servers.

SNTP data via the SNTP/NTP multicast address from the local network broadcast address.

SNTP response from the SNTP server and ignore s responses from other SNTP servers.

SNTP data from the SNTP/NTP multicast address and the loca l network broadcast address and ignores responses from other SNTP servers.

Page 36

3-8

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

Table 3-4 Time Zone Abbreviations

Abbreviation GMT Offset Cities Time Zone Names

IDL GMT-12:00 Eniwetok IDL (Interna tiona l Date Line ),

IDLW (Internationa l Da te L ine West) NT GMT-11:00 Midway BT (Bering Time), NT (Nome Time) AHST GMT-10:00 Hawaii AHST (Alaska -H awaii St a nda rd Time),

HST (Hawaiian Standard Time),

CAT (Central Alaska Time) IMT GMT-0 9:30 Isle Marquises Isle Marquises YST GMT-0 9: 00 Yukon YST (Yukon Sta ndard Time) PST GMT-08:00 Los Angeles PST (Pacific Standard Time), MST GMT-0 7:00 Phoenix MST (Mountain Standar d Time),

PDT (Pacific Daylight Time) CST GMT-06:00 Dallas, Mexico City CST (Central Standard Time),

MDT (Mountain D ayl ight Time), Chic ago EST GMT-05:00 New York EST (Eastern Standard Time),

CDT (Central Daylight Time), NYC AST GMT-04:00 La Paz AST (Atlantic St an dard Time),

EDT (Eastern Da ylight Time) NST GMT-03:30 Newfoundland NST (Newfoundland Standard Time) BST GMT-03:00 Buenos Aires BST (Brazil Standard Time),

ADT ( Atlantic Daylight Time),

GST (Greenland Sta ndard Time) AT GMT-02:00 Mid-Atlantic AT (Azores Time) WAT GMT-01:00 Azores WAT ( West Africa Time) GMT GMT 00:00 London GMT ( Gree nwi ch M e an Time),

WET (We ste rn Europea n Time),

UT (Universal Time) CET GMT+01:00 Paris CET (Central European Time),

MET (Middle Eu rope a n Time),

BST (British Summer Time),

MEWT( Middle Europ ean Winter Time),

SWT (Swedish Winter Time),

FWT (French Winter Time) EET G MT +0 2:0 0 Athens, Rome EET (Eastern E uro pe an Time),

USSR-zone1,

MEST (Middle Eur ope an Su mm er Time),

FST (French Summer Time) BT GMT+03:00 Baghdad, Moscow BT (Bagh dad Time), U SSR-zo ne2 IT GMT+03:30 Tehran IT (Iran Time) ZP4 GMT+04:00 Abu Dha bi USSR-zone3, ZP4 (GMT Plu s 4 Hour s) AFG GMT+04:30 Kabul Afghanistan ZP5 GMT+05:00 Islamaba d USSR-zone4, ZP5 ( GMT Plu s 5 Hour s)

Page 37

3-9

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

Example 3-1 Sample MGCP Default Configuration File

# Any or All of these options can be configured # in the user config file (MGC<MAC ADDR>.cnf). # The user config file options override any options # specified here in the Default Config File. # :sample user config file name: MGC003E362FE92.cnf

# image_version - specifies which image version should # be on the phone. This is used to upgrade from an # MGCP image to a different MGCP image. The OS79XX.TXT # file is only used to switch protocols (ie. SIP to MGCP). image_version: P0M3-04-2-00

# tftp_cfg_dir - specifies the directory to use for the # retrieving the MGC<MAC ADDR>.cnf file. The base # for the directory is the base TFTP Server directory. # tftp_cfg_dir is limited to 64 characters. tftp_cfg_dir : ""

# phone_password - specifies the password used to telnet # to the phone. phone_password is limited to 32 characters. # phone_prompt - specifies the prompt the phone will display # when logged in from the console or telnet session. # phone_prompt is limited to 16 characters. phone_password : "password" phone_prompt : "MGCP Phone"

# sntp_mode - specifies the mode the SNTP server uses # (unicast, multicast, anycast, directedbroadcast)

IST G MT+0 5:30 Bombay, Delhi IST (Indian Standar d Time) ZP6 GMT+06:00 Colombo USSR-zone5, ZP6 (GMT Plus 6 H ours) SUM GMT+06:30 North Sumatra NST (North Sumatra Time) WAST GMT+07:00 Bangkok, Hanoi SST (South Sumatra Time), USSR-z one6,

WAST (West Australian Standard Time)

HST GMT+08:00 Bei ji ng, H ong Kong CCT (China Coast Time),

HST (HongKong Standard Time), USSR-zone7, WADT (West Australia n Dayl igh t Time)

JST GMT +09:00 Tokyo, Seoul JST (Japan Standard Time/Tokyo),

KST (Korean Standard Time), USSR-zone8

CAST GMT+09:30 Darwin SAST (South Australian St andard Time) ,

CAST (Central Australian Standard Time)

EAST GMT+10:00 Brisbane, Guam GST (Guam Standard Time),U SSR-zon e9,

EAST (East Australi an Standa rd Time)

EADT GMT+11:00 Solomon Islands USSR-zone10,

EADT (East Australian Daylight Time)

NZST GMT+12:00 Auckland NZT (New Zealand Time/Auc klan d),

NZST (New Zealand Standard Time), IDLE (International Date Line East)

Table 3-4 Time Zone Abbreviations

Abbreviation GMT Offset Cities Time Zone Names

Page 38

3-10

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Using Configuration Files

# sntp_server - specifies the address of the SNTP server sntp_mode : Unicast sntp_server : "1.2.3.4"

# The following parameters setup time zone and # daylight savings settings. # Supported time zones are : # EST, AST, NST, BST, AT, WAT, GMT, HST, YST time_zone : EST dst_offset : 1 dst_start_month : "April" dst_start_day : 0 dst_start_day_of_week : "Sun" dst_start_week_of_month : 1 dst_start_time : 2 dst_stop_month : "Oct" dst_stop_day : 0 dst_stop_day_of_week : "Sun" dst_stop_week_of_month : 8 dst_stop_time : 2 dst_auto_adjust : 1

# Date and Time format displays # time_format_24hr (1 - yes, 0 - 12 hours format) # date_format (M/D/Y, D/M/Y, Y/M/D, Y/D/M) time_format_24hr : 1 date_format : M/D/Y

# Language - specifies which language to use for # internal strings [english (default), swedish] language: “english”

# MGCP Call Agent Information # mgcp_gw_controller - address of call agent # mgcp_input_port - port the phone listens on # mgcp_output_port - port the call agent listens on # mgcp_keepalive - specifies if the RSIP keepalive should # be used to keep NAT bindings open to the Call Agent. # values are [0 - off (default), 1 - on] # mgcp_keepalive_timer - specifies the time interval to # use for the mgcp keepalive timer if turned on. # values are in seconds [10 to 600, 30 is default]. mgcp_gw_controller : 1.2.3.4 mgcp_input_port : 2427 mgcp_output_port : 2727 mgcp_keepalive: 1 mgcp_keepalive_timer: 30

# xml_card_dir - specifies the directory to use for the # retrieving the xml cards file. The base # for the directory is the base TFTP Server directory. # xml_card_dir is limited to 64 characters. # xml_card_file - specifies the file name of the XML Cards # file. xml_card_file is limited to 20 characters. xml_card_dir : "" xml_card_file : "CARD.XML"

# tos_media - specifies the value to be used for the tos bits. # valid range is 0-7. tos_media: 7

#use_mac_name - specifies whether to use the IP address # or MAC Address in the endpoint name. The default is # to use the IP address. Valid values are :

Page 39

3-11

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Using the MGCP Phone Settings Button

# [ 0 - IP Address (default) 1 - Mac Address ] use_mac_name: 1

services_url: "http://www.company.com/phone/services.asp" directory_url: "http://www.company.com/phone/companydirectory.asp" logo_url: “http://www.company.com/phone/logo.bmp”

Using the MGCP Phone Settings Button

You can configure several featur es using t he se tti ngs button on your M GCP phon e. So me of t h ese features may differ dep endi ng on t he vend or CA y ou ar e usi n g. To begin you have to unlock the configuration mode.

There are two methods for un locking the configuration mode: one method for phones that have Release

4.2 and later a nd one m e thod fo r p hon es t ha t have Rele as e 4.1 a nd ear lie r.

In Release 4.2 or Later

In Cisco Release 4.2, there is an “Unlock Config” item in the phone settings menu. When you select Unlock Config, the user is prompted to enter a phone password using the alphanumberic entry func tion of the keypad. The phone password is set using the phone_password configuration parameter. When the correct password i s e ntere d, the configu ratio n is unl o cked a nd the settin gs c an be cha nged.

The Unlock Config it em in the me nu chan ges to L ock Conf i g and th e co nf igurati on remains l ocke d until it is unlocked. When the Settings menu is exited, the phone will automatically relock the configuration.

In Release 4.1 or Earlier

To configure the MGCP features on phones with earlier releases, perform the following tasks:

Step 1 Unlock the phone by pressing **#. The lock icon changes to show that the phone is unlocked. If you do

not unlock the p hone, yo u ca nnot cha nge t h e pho ne set tings.

Step 2 Press the settings button and use the arrow keys to scroll down to Network Configuration. Choose

Select.

Step 3 You can use this menu to configure the following items:

• IP address

• Subnet mask

• Default router

• DNS

• TFTP server addr ess

Note You must disable DHCP before you can configure these items. If you do not, the phone does not

allow you to over ride the values. To disable DHCP, in the Network Config u ratio n screen , scr oll down to DHCP Enabled and select No.

Step 4 To configure additional items, return to the main settings menu, then scroll to MGCP configuration and

choose select. This allows you to configure the following items:

Page 40

3-12

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Customizing the Cisco MGCP IP Phone Ring Types

• CA IP address

• Phone input port

• Phone output port

Note Your call agent or ser vice provider might offer additional phone features and capabilities not described

in this chapter. Refer to the documentation from your call agent or service provider for instructions on using those features.

Customizing the Cisco MGCP IP Phone Ring Types

The Cisco MGCP IP p hon e ships w ith t wo ri ng t ypes: C hirp 1 and Ch irp2. B y d efault , you r r ing type options will be those two choices. However, using the RINGLIST.DAT file, you can customize the ring types that are available to the Cisco MGCP IP phone users .

Step 1 Create a pulse code modulation (PCM) file of the desired ring types and store the PCM files in the root

directory of your TFTP server. PCM files must contain no header information and must comply with the following format gui del ine s:

• 8000 Hz sampling rate

• 8 bits per sample

• u-law compression

Step 2 Using an ASCII editor, open the RINGLIST.DAT file and for each of the ring types you are adding,

specify the name as you want it to appear on the Ring Type menu; press Tab; and then specify the filename of the ring type. For example, the format of a pointer in your RINGLIST.DAT file should appear similar to the following:

Ring Type 1ringer1.pcm

Step 3 After defining pointers for each of the ring types you are adding, save your modifications and close the

RINGLIST.DAT file.

Viewing the Firmware Version

To view the firmware version, complete the following steps:

Step 1 Press the Settings key. The Settings menu appears. Step 2 Highlight Status. Step 3 Press the Select soft key. The Setting Status menu appear s. Step 4 Highlight Firmware Versions.

Page 41

3-13

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Upgrading the Cisco MGCP IP Phone Firmware

Step 5 Press the Select soft key. The Firmware Versions pane l a ppear s.

The following information is displayed on this panel:

• Application Load ID—Current software image on the phon e.

• Boot Load ID—Bootstrap loader image version that is manufactured on the phone. This image name

does not change.

Step 6 To exit the Firmware Versions panel, press the Exit soft key.

Upgrading the Cisco MGCP IP Phone Firmware

You can use one of two methods to upg rade the firmware on yo ur Cisco MGCP IP pho nes. You can upgrade the firmware on one phone at a time using the phone-specific configuration, or you can upgrade the firmware on a system of phones using the defaul t configurat ion file.

Before You Begin

• To u pgr ad e the firmwar e on j ust o ne ph one at a tim e, y ou upg ra de t he i m age_ versi on in t h e

phone-specific configuration file. To upgrade the firmware on a system of phones, spe cify the image_version in the default configuration file and do not define the image_version in the phone-specific configuration files.

• Ensure that the latest version of the Cisc o MGCP IP phon e firmware has bee n copied fr om

Cisco.com to the root direct ory of your TFT P server.

See the upgrade scenarios in Table 3-5 to det erm in e how to upg rad e.

Upgrading to Release 5.0 and Release 5.1

When you upgrade to R ele as e 5.0 or Release 5.1, you will down lo ad a ZI P ar ch ive instead of a file as in earlier release s. Cont ai ned i n t he a rc hive are th e unsig ned ( .b in) an d sig ned ( .sb n) bina ry i mage s. Specific information for each release is as follows:

Table 3-5 Upgrade Scenarios

Image Name Use Section

P0M3-05-0-00 and P0M 3-0 5-1-0 0 Up grading to Release 5.0 an d Release 5.1, page 3-13 P0M3-03-03-0 -00, P 0M3-0 3-1-00 , and

P0M3-03-2-00, P0M 30100, P0M30200, P0M30201, P0M3Zxxx , P0M302 02, P0M30203, P0M3-03- y-x x, a nd P0M3-04-4-00

Upgrading from Older Releases to the Current Release, page 3-1 5

P0M3-xx-y-zz Dual Booting from SCCP or M G CP to Rel ease 4.0,

page 3-16

Page 42

3-14

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Upgrading the Cisco MGCP IP Ph one Firmware

Release 5.0

Cisco has added image authentication to IP phone protocols, which means that tampering with the binary image before the image is downloaded to the phone is not allowed. Any tampering with the image will cause the phone to fail the authentication process and reject the image. Once you download the Release

5.0 image, y ou ca nn ot d owngrad e t o any ea r lie r re l ease s.

Release 5.1

Release 5.1 is the second rel ease of the si gned Cisc o IP phone ima ge. Rele ase 5.1 is compat ible with Release 5.0 and la ter releas es. Release 5.1 addr esses the u ser interfa ce respon siv eness an d voice clipping issues.

Procedure

Step 1 Unzip the ZIP archive to extract the binary images and any notes or readme text files. Read these text

files for any special directions regarding the images.

Step 2 Copy the new images P0M3-xx-y-zz.sbn (sign ed binary) an d P0M3-x x-y-zz. bin (unsi gned

binary)—where xx is the release majo r version, y is the release min or version, and zz is the maintenance number—from Ci sco. co m t o the root dire ct ory of th e TFT P server.

Step 3 Using a text editor, open the configuration file and upda te the ima ge version speci fied in the

image_version v ariabl e. The v ersion name i n the image_v ersion v ariab le should matc h the ver sion name (without the .sbn extension) of the latest firmware that you downloaded (for exam ple, P0M3 -xx-y-zz).

Step 4 Reset each phone.

The phone contacts the TFTP server and requests its configuration files. The phone compares the image defined in the f ile to the im age that it has stor ed in Flash memory. If the phone determines that the imag e defined in the file differs from the image in Flash memory, it downloads the image defined in the configuration file (which is stored i n the root dir ectory on the TFTP server). Once th e new image has been downloaded, the ph one pro gra ms t hat ima ge i n to Fla sh m e mory an d the n rebo ot s.

Note If you do not define the image_version parameter in the default configuration file, only phones that have

an updated phone-specific configuration file with the new image version and that have been restarted use the latest firmware image. All other phones use the older v ersion until their conf iguration f iles hav e been updated with the new image version.

Upgrading from Release 2.2 or Later Releases to Release 4.0

Step 1 Copy the Release 4.0 image P0M3-xx -y-zz.bin, wher e xx is the release major version, y is the release

minor version, and zz is the main tena nc e nu mbe r, from Cisc o.co m to t he r oo t di rec tory of the TF TP server.

Step 2 Using a text editor, open the configuration file and upda te the ima ge version speci fied in the

image_version v ariabl e. The v ersion name i n the image_v ersion v ariab le should matc h the ver sion name (without the .bin extension) of the latest firmware that you downloaded (for example, P0M3-xx-y-zz).

Step 3 Reset each phone.

Page 43

3-15

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Upgrading the Cisco MGCP IP Phone Firmware

Note If you do not define the image_version parameter in the default configuration file, only phones that have

Upgrading from Release 2.1 or Earlier Releases to Release 4.0

Step 1 Copy the P0M30202.bi n i mage f rom C isco. c om t o th e roo t dir ect ory of t he TFT P se rver. Step 2 If you are dual booting from a Cisco IP phone ru nning the Ski nny Client Control Protocol (SCC P) or

MGCP protocol, open the OS79XX.TXT file with a text editor and change the file to include P0M30202.

Step 3 Open the phone configuration file with a text editor and edit the image_version variable to read

P0M30202.

Step 4 Reset each phone.

Step 5 Copy the Release 4.0 image P0M3-xx -y-zz.bin, wher e xx is the release major version, y is the release

minor version, and zz is the main tena nc e nu mbe r, from Cisc o.co m to t he roo t di rec tory of the TF TP server.

Step 6 Using a text editor, open the configuration file and upda te the ima ge version speci fied in the

image_version variable. The version name in image_version variable should match the version name (without the .bin extension) of the latest firmware that you downloaded (for example, P0M3-xx-y-zz).

Step 7 Reset each phone.

Upgrading from Older Releases to the Current Release

Step 1 Copy the P0M3-xx-y-zz image from Cisco.com to the root directory of the TFTP server. Step 2 Using a text editor, open the configuration file and upda te the ima ge version speci fied in the

image_version variable. The version name in image_version variable should match the version name (without the .bin extension) of the latest firmware that you downloaded.

Step 3 Open the phone configuration file with a text editor and edit the image_version variable to read

P0M3-xx-y-zz.

Page 44

3-16

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Performing an Image Up grade and Remote Reboot

Step 4 Reset each phone.

Dual Booting from SCCP or MGCP to Release 4.0

Step 1 If you are dual booting from a Ci sco IP ph one run ni ng the SCCP prot ocol , open th e OS79X X.T XT file

with a text editor and change the file to include P0S30202.

Step 2 If you are dual booting from a Cisco IP phone running the SIP protocol, open the OS79XX.TXT file with

a text editor and change t he file to include P0M3-04 -2-00 .

Step 3 Copy the Release 4.2 image P0M3-xx-y-z z.b in, wher e xx is the re lease major versio n, y is the rele ase

minor version, and zz is t he m ain tena nce nu mb er, from Cisc o.c om to t he roo t di r ectory of the TFTP server.

Using a text editor, open the configuration file and upda te the image version specified in the image_version variable. The version name in image_version variable should match the version name (without the .bin extension) of the latest firmware that you downloaded (for example, P0M3-xx-y-zz).

Step 4 Reset each phone.

Performing an Image Upgrade and Remote Re boot

With Release 4.0 and late r rele as es of t he C i sco MG CP I P ph one, yo u c an p er fo rm a n im ag e upg rade and remote reboot usi ng Noti fy me ssa ges a nd t he sy nc info .xm l file.

Note To p er fo rm an i mage upg rade and re mo te r eboot , a n MGCP ca ll age nt a nd a T FTP ser ver m ust exi st i n

the phone network.

To u pgr ad e the firmware ima ge and perf orm a re mote r eboot , c omp lete th e f oll owing step s:

Step 1 Using an ASCII editor, open the MGCPDefault.cnf file located in the root directory of your TFTP server

and change the image_version parameter to the name of the latest image.

Step 2 Using an ASCII editor, open the syncinfo.xml file located in the root directory of your TFTP server and

specify values for the image version and sync parameter as follows:

Where:

• image_version is the image version of the phone. The asterisk (*) can be used as a wildcard

character.

• sync_number is the synchronization level of the phone. The default synchronization level for the

phone is 1. A valid value is a character string of up to 32 chara cters.

Step 3 Send an RQNT message to the phone. In the RQNT message, ensure that the signal line is equal to

X-check-sync.

Page 45

3-17

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 3 Configuring the Cisco MGCP IP Phone

Performing an Image Upgrade and Remote Reboot

The following is a sample RQNT message:

RQNT 9713 d001 @ 003094c25d40 MGCP 0.1 X: 100 S: X-check-sync

After the remote reboot process is initiated on the phone via the NOTIFY message, the following actions take place:

1. If the phon e i s curr e ntly in a n idl e s ta te, th e pho ne wa its 20 se co nds an d th en c ont ac ts t he T FTP

server for the syncinfo.xml file. If the phone is not in an idle state, the phone waits until it is in an idle state for 20 seconds and then contacts the TFTP server for the syncinfo.xml file.

2. The phone reads the syncinfo.xml file and performs the following as appropriate: a. Determines whether the current image is specified. If so, the phone proceeds to Step c. If not,

the phone proceed s to St ep b.

b. Determi nes whether there is a wildcar d entry (*) in the image v ersion parameter . If so, the p hone

proceeds to Step c. If not, the phone proceeds to Step d.

c. Determines if the synchronization value is different than what is stored on the phone. If so, the

phone proceeds to Step e. If not, the phon e proc eeds to Step d.

d. The phone does nothing. e. The phone reboots.

The phone the performs a normal reboot process, sees the new image, and upgrades to t he new image with a synchronization value of what is specified in the syncinfo.xml file.

The phone contacts the TFTP server and requests its configuration files. The phone compares the image defined in the f ile to the im age that it has stor ed in Flash memory. If the phone determines that the imag e defined in the file differs from the image in Flash memory, it downloads the image defined in the configuration file (which is stored i n the root dir ectory on the TFTP server). Once th e new image has been downloaded, the ph one pro grams t hat ima ge in to Fla sh m emor y an d the n rebo ots.

Page 46

3-18

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter3 Configuring the Cisco MGCP IP Phone

Performing an Image Up grade and Remote Reboot

Page 47

CHAPTER

4-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Using the Cisco MGCP IP Phone

This chapter descr ibes basic Cisco MGCP IP phone functions. Your call agent or ser vice provide r might offer additional phone features an d capabilities n ot described in this chapter. Refer to the documentation from your call agent or ser vice provid er for inst ructi ons on usin g those feat ures.

This chapter includes the following sections:

• Using the H an dse t, pag e 4-1

• Using the Speakerphone, page 4-1

• Using the Headset, page 4-1

• Adjusting the Handset, Speaker phone, an d Headse t Volume, page 4-2

• Adjusting the Ring er Vo l ume, pa ge 4 -2

• Changing the LCD Contrast, page 4-2

• Muting a Call, page 4-2

Using the Handset

To place and answer calls with the handset, simply lift the handset. To change from handset to speakerphone, press SPEAKER and ha ng up the ha ndset .

Using the Speakerphone

T o place and answer calls using the speakerphone, press SP EAKER. You can use the speakerphone with all Cisco MGCP IP phone features. To change from speakerphone to handset, li ft the handse t.

Using the Headset

To pl ace and a nswe r ca lls u si ng the hea dse t, plug th e app roved head set i nto t he ba ck of the p hon e b ase and press HEADSET.

You can use t he h ea dset wi th all C isco MGCP IP Phonefeatures . The volu me a nd mut e co nt rols al so adjust volume to the ear piece and mute the speech path of the headset. The headset activation key is located on the front of the phone.

Page 48

4-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter4 Using the Cisco MGCP IP Phone

Adjusting the Handset, Speakerphone, and Headset Volume

The Cisco MGCP IP Phonesupports a four- or six-wire headset jack (Plantronics H series compatible is required). For information on the exact models supported, see the Cisco MGCP IP phone information on http://cisco.getheadsets.com.

Adjusting the Handset, Speakerph one, and Heads et Volume

To a dju st the volume on the han dse t, sp eaker pho ne, or he ad set:

Step 1 T o increase or decrease the volume of your handset, headset, or speakerphone, select the item and make

it active. Pres s the Up or Down volu m e button . The volume buttons adjust the volume for the cu rrently active voice receiver.

Adjusting the Ringer Volume

To change the volume used by the ringer:

Step 1 Press the volume key to he ar a sa mp le ri ng . Step 2 While the ring plays, press the Up or Down volume key to adjust the volume to the desired level.

Changing the LCD Contrast

To improve the readability of the LCD, change the amount of contrast:

Step 1 Press the settings butto n . Step 2 Select Contrast from the Settings menu. Step 3 Press the volume keys to set the desired intensity of the display. Step 4 Press the BACK key to accept your changes.

Muting a Call

While on a call, you can mute the ha ndset, he adset, or spe akerpho ne, preventing the party yo u are speaking to from h eari n g wha t y ou or som e one e lse in th e ro om is sayi ng.

• To mute a call, press MUTE.

• To disen gage mute , pres s MUTE again.

Page 49

CHAPTER

5-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Monitoring and Maintaining the Cisco MGCP IP Phone

You can use Telnet to view information about your Cisco MGCP IP phone , to monitor the network, and to maintain the ph one s in yo ur ne twork .

Note Only two Telnet sessions can be op en a t a ny tim e, a nd t he Ci sco M GCP IP ph one ca nnot or igin ate a

Telnet session to another address.

The available commands are as follows:

Command Purpose

MGCP Phone> clear {arp | malloc | tcp-stats | ethernet | ip}

Clears the following depending on keywords used:

• arp—Clears the Address Resolution Protocol (ARP) cache.

• malloc—Clears the memory allocation table.

• tcp-stats—Clears the TCP statistics.

• ethernet—Clears the network statistics.

• ip—Clears the IP statistics.

Page 50

5-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Maintaining the Cisco MGCP IP Phone

MGCP Phone> debug {arp | console-stall | strlib | malloc | malloctable | sk-platform | flash | dsp

arp-broadcast | xml-events | xml-deck | xml-vars | xml-post}

Shows detailed MGCP debug command output when used with the following keywords:

• arp—Shows debug output for the ARP cache.

• console-stall—Shows debug command output for the

console-stall driver output mode.

• strlib—Shows debug command output for the st ring lib rary.

• malloc—Shows debug command output for memo ry

allocation.

• malloc-table—Enables the population of the memory

allocation table. The table can b e viewed with the show malloc-table command.

• sk-platform—Shows debug command output f or the

platform.

• flash—Shows debug command output for the Flash memory.

• dsp—Sh ows debug command output for DSP accesses.

• vcm—Shows debug command output for the voice chann el

manager (VCM), i ncl uding ton es, r in ging , and volum e.

• dtmf—Sh ows debug command output for dual -tone

multifrequency (DTMF) relay.

• task-socket—Shows socket task debug comma nd outp ut.

• mgcpio—Shows debug command output for MGC P

input/output.

• mgcp_parse—Shows detailed MGCP debug command

output; displays each MGCP message gettin g par sed or built.

• dns—Shows the DNS command-line interface (CLI)

configuration; allows you to clear the cache and set servers).

• config—Shows output for the config system option.

• sntp—Shows debug command output for Simp le Networ k

Time Protocol (SNTP)

• sntp-packet—Displays full SNTP packet data.

• arp-broadcast—Shows ARP broadcast messages.

• http—Sh ows HTTP requests and respo nses.

• xml-events—Shows XML event s that are posted to the XM L

application chain.

• xml-deck—Shows XML requests for XM L card s and de cks.

• xml-vars—Shows XML content variables.

• xml-post—Shows XML post strings.

Note Do not use the debug all command, because it can cause

the phone to become inoperable. This command is for use only by Cisco TAC personnel.

Command Purpose

Page 51

5-3

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Ma int ai ning the Cisco MGCP IP Phone

MGCP Phone> dns value

Manipulates the D N S s yst em. Th e va l ue a rgument has the following keywords:

• -p—Prints out the DNS cache table.

• -c—Clears out the DNS cache table.

• -s ipaddress—Sets the primary DNS.

• -b ip address—Sets the first backup server.

MGCP Phone> erase protflash

Erases the pro toco l a rea of Fla sh m emor y. Forces the phone to reset its IP stack and request its config files again. This command can only be used if the telnet_level parameter is set to allow privileged commands to be executed.

MGCP Phone> exit

Exits the Telnet or console session.

MGCP Phone> ping ipaddress number packetsize timeout

Sends a n Internet Control Message Protocol (ICMP) ping to a network address. You can use a dotted IP add ress o r a n alphanumeric add re ss . Th e numb er value specifies how many pings to send; the default value is 5. The packetsize argument defines the size of the packet; you can send any size packet up to 1480 bytes and the defaul t p acket si ze is 1 00. T he timeout val u e is measured in seconds and identif ies ho w long to wait before the request times out; the default is 2.

MGCP Phone> reset

Resets the phone. This co mman d can be used onl y if the telnet_level parameter is set to allow privileged commands to be executed.

Command Purpose

Page 52

5-4

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Maintaining the Cisco MGCP IP Phone

MGCP Phone> show {arp | debug | strpool | memorymap | dump | malloctable | stacks | status

| abort_vector | flash | timers | dspstate | rtp | tcp | lists | network | config | mgcp_lists | dialplan | timers | ethernet | ip}

Shows information about the Cisco MGCP IP phone. The following keywords are used:

• arp—Displays contents of the ARP cache.

• debug—Shows which debug command m odes a r e ac tivated.

• strpool—Shows the string library pool of strings.

• memorymap—Shows memory mapping table , includi ng

free, used, and wasted blocks.

• dump—Displays a dump of the memor y contents.

• malloctable—Shows the memory allocation table.

• stacks—Shows tasks and buffer lists.

• status—Shows the current phone status, inc luding errors.

• abort_vector—Shows the address of the last recorded abort

vector.

• flash—Shows Flash memory information.

• timers—Shows a list of timers, including the expiratio n time

and other data about each.

• dspstat e —Shows the digital signal processor (DSP) status,

including whether the DSP is re ady, the audio mode, if keepalive pending is turn ed on, an d the ri nger stat e.

• rtp—Shows packet statistics for the RTP streams.

• tcp—Shows the status of TCP p orts, incl uding the state

(listen or closed) and the por t numb er.

• network—Shows network informat ion, such a s phone

platform, DHCP server, phone IP address and subn et mask, default gateway, address of the TFTP server, phone MAC address, domain name, and phone name.

• config—Shows the current Flash memory configuration,

including network inform ation , phone lab el and password, SNTP server address, daylight saving time (DST) hinformation, time and date format, CA address, and MGCP input and output port numbers .

• mgcp_lists—Shows the filter list and duplicate message list

lengths .

• dialplan—Shows the phone dia l pla n.

• timers—Shows the current status of the platform timers.

• ethernet—Shows the netwo rk statistics in the Network

Statistics menu.

• ip—Shows the IP statistics.

Command Purpose

Page 53

5-5

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Ma int ai ning the Cisco MGCP IP Phone

MGCP Phone> test {open | close | key | onhook | offhook | show | hide}

Accesses the remote call test interface, allowing you to control the phone from a remote site. To use this feature, enter the test open command. T o pre ven t use of this f eature, enter the test close command. This comm and ca n be used only if the teln et_level parameter is set to allow privileged commands to be executed.

The following commands ar e available:

• test key: When a test session i s op en, you c an sim ul ate key

presses using the test key k1 k2 k3...k13 command, where k1 through k13 represent the following key names:

–

voldn—Vo lu me down

–

volup—Vo lu me up

–

headset—Headset

–

spkr—Speaker

–

mute—Mute

–

info—Info

–

msgs—Messages

–

serv—Services

–

dir—Directories

–

set—Settings

–

navup—Navigate up

–

navdn—Navigate down

The keys 0 through 9, #, and * ma y be entered in continuous strings to better express t ypi cal dial ing stri ngs. A t ypic al command would be test ky 23234.

• test onhook: Simulates a hands et onhook event.

• test offhook: Simulates a handse t offhook event.

• test show: Show test feedback.

• test hide: Hide test feedback.

MGCP Phone> traceroute ip-address [ttl]

Initiates a traceroute session from the console or from a Telnet session. T raceroute shows th e route that IP datagrams follow f rom the MGCP IP phone to the specified IP address. Use the following two arguments:

• ip-address: The dotted IP ad dress or alp hanum eric addre ss

(host name) of the host to which you ar e sending the traceroute.

• ttl: The time-to -live value, or the number of ro uters (hop s)

through which the datag ram can pass. The def ault v alue is 30.

Command Purpose

Page 54

5-6

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Maintaining the Cisco MGCP IP Phone

Viewing Status Messages

To v iew status me ssage s tha t yo u can use to dia gnose ne twork pr oble ms, com ple te th e following steps:

Step 1 Press the Settings key. The Settings menu appears. Step 2 Highlight Status. Step 3 Press the Select soft key. The Setting Status menu appear s. Step 4 Highlight Status Messages. Step 5 Press the Select soft key. The Status M essages panel a ppears. Step 6 To exit the Status Messages panel, press the Exit soft key.

Viewing Network Statistics

T o vie w statistical information about the phone and network performance, complete the following steps:

Step 1 Press the Settings key. The Settings menu appears. Step 2 Highlight Status. Step 3 Press the Select soft key. The Setting Status menu appear s. Step 4 Highlight Network Statistics. Step 5 Press the Select soft key. The Network Statistics panel appears.

The following information is displayed on this panel:

• Rcv—Number o f packet s re ceived by th e p hon e, n ot thr oug h t h e swit c h.

• Xmit—Number of packets sent by the phone , not thro ugh the switch .

• REr—Number o f pa cket s rece ived by the p hon e t ha t c onta in ed err ors .

• BCast—Number of broadcast packets received by the phone.

• Phone State Mes sage—TCP messages indicating the state of the p hone. Possible message s are:

MGCP Phone> tty {echo {on | off} | mon | timeout value | kill session | msg}

Controls the Telnet system. The echo keyword controls local echo. The mon keyword sends all debug com mand output to both the console and Telnet sessions. The timeout value keyword sets t he telnet session timeout period based on the value. The value range is 0 through 65535. The kill session keyword tears down the Telnet session specified by the session argument. The msg keyword allows you to send a message to another terminal logged into the phone; for example, you can send a message telling everyone else that is logged in to log off.

MGCP Phone> undebug {arp | console-stall | strlib | malloc | malloctable | sk-platform | flash |

dsp | vcm | dtmf | task-socket | mgcpio | mgcp_parse | dns | config | sntp sntp-packet}

Turns off debugging.

Command Purpose

Page 55

5-7

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Ma int ai ning the Cisco MGCP IP Phone

–

Phone Initialized—TCP connection ha s not g one d own since t he pho ne was p owered on.

–

Phone Closed TCP—TCP co nnec tion was closed by the phone.

–

TCP Timeout—TCP connection was closed because of a retry timeout.

–

Error Code—Error messages i ndic ating un usual rea son s the TCP co nne ctio n was close d.

• Elapsed Time—Length of t ime (i n days, h ours, minu t es, and se conds) si nce the l ast power cycle.

• Port 0 Full, 100—Indicates that the network is in a linked state and has autonegotiated a full-duplex

100-Mbps connec tion.

• Port 0 Half, 100—Indicates that the network is in a linked state and has autonegotiated a half-duplex

100-Mbps connec tion.

• Port 0 Full, 10—Indicates that the network is in a linked state and has autonegotiated a full-duplex

10-Mbps connection.

• Port 0 Half, 10—Indicates that the network is in a link e d state an d has au tonegotiated a half-duplex

10-Mbps connection.

• Port 1 Full, 100—Indicates that the network is in a linked state and has autonegotiated a full-duplex

100-Mbps connec tion.

• Port 1 Half, 100—Indicates that the network is in a linked state and has autonegotiated a half-duplex

100-Mbps connec tion.

• Port 1 Full, 10—Indicates that the network is in a linked state and has autonegotiated a full-duplex

10-Mbps connection.

• Port 1 Half, 10—Indicates that the network is in a link e d state an d has au tonegotiated a half-duplex

10-Mbps connection.

• ethernet—Indicates the ???

Step 6 To exit the Network Statistics panel, press the Exit soft key.

Note To re set the values disp layed on Networ k Statist ics panel, power off and power on the phone.

Verifying the Ethernet Statistics

Use the show ethernet command to verify the ethernet statistics. The following is sample output:

MGCP Phone> show ethernet Ethernet Mib:

-------------------------------------------------- ResErr 00000154, RcvCnt 00137436, RcvErr 00000000, DrpCnt 00001421 BrdCst 00122041, TooLng 00000363, TxCnt 00012322, TxQCnt 00000000 TxQue 00000000, TxQMax 00000000, TxXCol 00000000, TxFram 00012322

Overflow Counters... UDP 00000000, ICMP 00000000, NonIP 00000000, TCP 00000000 CDP 00000000, Unknown 00000000, Arp 00000000

Use the show ip command to verify the IP statistics. The following is sample output:

MGCP Phone> show ip IP Statistics:

---------------------------------------------------

Page 56

5-8

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter 5 Monitoring and Maintaining the Cisco MGCP IP Phone

Received 01426183, RxDrops 00002181 RxFrags 00000000, RxFragDrops 00000000, RxReassembled 00000000 Transmitted 00011996, TxDrops 00000010, TxFragments 00000000

Use 'clear ip' to clear data

Page 57

APPENDIX

A-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Translated Safety Warnings

These sections contain translations of the warnings used in the “Safety Notices” section on page 2-1.

Warning Definition

Warning

Waarschuwing

Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico’s en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen.

Varoitus

Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisi sta onnettomuuksien ehkäisykeinoista.

Attention

Ce symbole d’avertissement indique un danger. Vous vous trouvez dans une situation pouvant entraîner des blessures. Avant d’accéder à cet équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures courantes de prévention des accidents.

Warnung

Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt.

Page 58

A-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

Installation Warning

Avvertenza

Questo simbolo di avvertenza indica un pericolo. Si è in una situazione che può causare infortuni. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti.

Advarsel

Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du være oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker.

Aviso

Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos fisicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes.

¡Advertencia!

Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes.

Varning!

Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador.

Warning

Read the installation instructions before you connect the system to its power source.

Waarschuwing

Raadpleeg de installatie-aanwijzingen voordat u het systeem met de voeding verbindt.

Varoitus

Lue asennusohjeet ennen järjestelmän yhdistämi stä virtalähteeseen.

Attention

Avant de brancher le système sur la source d'alimentation, consulter les directives d'installation.

Warnung

Lesen Sie die Installationsanweisungen, bevor Sie das System an die Stromquelle anschließen.

Avvertenza

Consultare le istruzioni di installazione prima di collegare il sistema all’alimentatore.

Advarsel

Les installasjonsinstruksjonene før systemet kobles til strømkilden.

Page 59

A-3

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

Product Disp osal Warning

Product Disposal Warning

Aviso

Leia as instruções de instalação antes de ligar o sistema à sua fonte de energia.

¡Advertencia!

Ver las instrucciones de instalación antes de conectar el sistema a la red de alimentación.

Varning!

Läs installationsanvisni ngarna innan du kopplar systemet till dess strömförsörjningsenhet.

Warning

Ultimate disposal of this product should be handled according to all national laws and regulations.

Waarschuwing

Dit produkt dient volgens alle landelijke wetten en voorschriften te worden afgedankt.

Varoitus

Tämän tuotteen lopullisesta hävittämisestä tulee huolehtia kaikkia valtakunnallisia lakeja ja säänn öksiä noudattaen.

Attention

La mise au rebut définitive de ce produit doit être effectuée conformément à toutes les lois et réglementations en vigueur.

Warnung

Dieses Produkt muß den geltenden Gesetzen und Vorschriften entsprechend entsorgt werden.

Avvertenza

L'eliminazione finale di questo prodotto deve essere eseguita osservando le normative italiane vigenti in materia.

Advarsel

Endelig disponering av dette produktet må skje i henhold til nasjonale lover og forskrifter.

Aviso

A descartagem final deste produto deverá ser efectuada de acordo com os regulamentos e a legislação nacional.

¡Advertencia!

El desecho final de este producto debe realizarse según todas las leyes y regulaciones nacionales.

Varning!

Slutlig kassering av denna produkt bör skötas i enlighet med landets alla lagar och föreskrifter.

Page 60

A-4

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

Lightning Activity Warning

Warning

Do not work on the system or connect or disconnect cables during periods of lightning activity.

Waarschuwing

Tijdens onweer dat gepaard gaat met bliksem, dient u niet aan het systeem te werken of kabels aan te sluiten of te ontkoppelen.

Varoitus

Älä ty öskentele järjestelmän parissa äläkä yhdis tä tai irrota kaapeleit a ukkosilmalla.

Attention

Ne pas travailler sur le système ni brancher ou débrancher les câbles pendant un orage.

Warnung

Arbeiten Sie nicht am System und schließen Sie keine Kabel an bzw. trennen Sie keine ab, wenn es gewittert.

Avvertenza

Non lavorare sul sistema o collegare oppure scollegare i cavi durante un temporale con fulmini.

Advarsel

Utfør aldri arbeid på systemet, eller koble kabler til eller fra systemet når det tordner eller lyner.

Aviso

Não trabalhe no sistema ou ligue e desligue cabos durante períodos de mau tempo (trovoada).

¡Advertencia!

No operar el sistema ni conectar o desconectar cables durante el transcurso de descargas eléctricas en la atmósfera.

Varning!

Vid åska skall du aldrig utföra arbete på systemet eller ansluta eller koppla loss kablar.

Page 61

A-5

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

SELV Circuit Warning

Warning

To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables.

Waarschuwing

Om elektrische schokken te vermijden, mogen veiligheidscircuits met extra lage spanning (genaamd SELV = Safety Extra-Low Voltage) niet met telefoonnetwerkspanning (TNV) circuits verbonden worden. LAN (Lokaal netwerk) poorten bevatten SELV circuits en WA N (Regionaal netwerk) poorten bevatten TNV circuits. Sommige LAN en W AN poorten gebruiken allebei RJ-45 connectors. Ga voorzichtig te werk wanneer u kabels verbindt.

Varoitus

Jotta vältyt sähköiskulta, älä kytke pienjännitteisiä SELV-suojapiirejä puhelinverkkojännitettä (TNV) käyttäviin virtapiireihin. LAN-portit sisältävät SELV-piirejä ja WAN-portit puhelinverkkojännitettä käyttäviä piirejä. Osa sekä LAN- että WAN-porteista käyttää RJ-45-liitti miä. Ole varovainen kytkiessäsi kaapeleita.

Attention

Pour éviter une électrocution, ne raccordez pas les circuits de sécurité basse tension (Safety Extra-Low Voltage ou SEL V) à des circuits de tension de réseau téléphonique (Telephone Network Voltage ou TNV). Les ports du réseau local (LAN) contiennent des circuits SELV et les ports du réseau longue distance (WAN) sont munis de circuits TNV. Certains ports LAN et WAN utilisent des connecteurs RJ-45. Raccordez les câbles en prenant toutes les précautions nécessaires.

Warnung

Zur Vermeidung von Elektroschock die Sicherheits-Kleinspannungs-Stromkreise (SELV-Kreise) nicht an Fernsprechnetzspannungs-Stromkreise (TNV-Kreise) anschließen. LAN-Por ts enthalten SELV -Kreise, und W AN-Ports enthalten TNV -Kreise. Einige LAN- und WAN-Ports verwenden auch RJ-45-Steckverbinder. Vorsicht beim Anschließen von Kabeln.

Avvertenza

Per evitare scosse elettriche, non collegare circuiti di sicurezza a tensione molto bassa (SELV) ai circuiti a tensione di rete telefonica (TNV). Le porte LAN contengono circuiti SELV e l e porte WAN contengono circuiti TNV. Alcune porte LAN e WAN fanno uso di connettori RJ-45. Fare attenzione quando si collegano cavi.

Advarsel

Unngå å koble lavspenningskretser (SELV) til kretser for telenettspenning (TNV), slik at du unngår elektrisk støt. LAN-utganger inneholder SELV-kretser og WAN-utganger inneholder TNV-kretser. Det finnes både LAN-utganger og WAN-utganger som bruker RJ-45-kontakter. Vær forsiktig når du kobler kabler.

Page 62

A-6

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

Circuit Breaker (15A) Warning

Aviso

Para evitar choques eléctricos, não conecte os circuitos de segurança de baixa tensão (SELV) aos circuitos de tensão de rede telefónica (TNV). As portas LAN contêm circuitos SELV e as portas WAN contêm circuitos TNV. Algumas portas LAN e WAN usam conectores RJ-45. Tenha o devido cuidado ao conectar os cabos.

¡Advertencia!

Para evitar la sacudida eléctrica, no conectar circuitos de seguridad de voltaje muy bajo (safety extra-low voltage = SELV) con circuitos de voltaje de red telefónica (telephone network voltage = TNV). Los puertos de redes de área local (local area network = LAN) contienen circuitos SELV, y los puertos de redes de área extendida (wide area network = WAN) contienen circuitos TNV. En algunos casos, tanto los puertos LAN como los WA N usan conectores RJ-45. Proceda con precaución al conectar los cables.

Varning!

För att undvi ka elektris ka stötar, koppla inte säkerhetskretsar med extra låg spänning (SELV-kretsar) till kretsar med telefonnätspänning (TNV-kretsar). LAN-portar innehåller SELV-kretsar och WAN-portar innehåller TNV-kretsar. Vissa LAN- och WAN-portar är försedda med RJ-45-kontakter. Iaktta försiktighet vid anslutning av kablar.

Warning

This product relies on the building’s installation for short-circuit (overcurrent) protection. Ensure that a fuse or circuit breaker no larger than 120 VAC, 15A U.S. (240 VAC, 10A international) is used on the phase conductors (all current-carrying conductors).

Waarschuwing

Dit produkt is afhankelijk van de installatie van het gebouw voor kortsluit(overstroom)beveiliging. Controleer of er een zekering of stroomverbreker van niet meer dan 120 Volt wisselstroom, 15 A voor de V.S. (240 Volt wisselstroom, 10 A internationaal ) gebruikt wordt op de fasegeleiders (alle geleiders die stroom voeren).

Varoitus

Tämä tuote on riippuvainen rakennukseen asennetusta oikosulkusuojauksesta (ylivirtasuojauksesta). Varmista, että vaihevirtajohtimissa (kaikissa virroitetuissa johtimiss a) käytetää n Yhdysv alloissa alle 120 voltin, 15 ampeerin ja monissa muissa maissa 240 volti n, 10 ampeerin sulaketta tai suojakytkintä.

Attention

Pour ce qui est de la protection contre les courts-circuits (surtension), ce produit dépend de l'installation électrique du local. Vérifier qu'un fusible ou qu'un disjoncteur de 120 V alt., 15 A U.S. maximum (240 V alt., 10 A international) est utilisé sur les conducteurs de phase (conducteurs de charge).

Page 63

A-7

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

TN Power Warning

Warnung

Dieses Produkt ist darauf angewiesen, daß im Gebäude ein Kurzschluß- bzw. Überstromschutz installiert ist. Stellen Sie sicher, daß eine Sicherung oder ein Unterbrecher von nicht mehr als 240 V Wechselstrom, 10 A ( bzw. in den USA 120 V Wechselstrom, 15 A) an den Phasenleitern (allen stromführenden Leitern) verwendet wird.

Avvertenza

Questo prodotto dipende dall’installazione dell’edificio per quanto riguarda la protezione contro cortocircuiti (sovracorrente). Verificare che un fusibile o interruttore automatico, non superiore a 120 VCA, 15 A U.S. (240 VCA, 10 A internazionale) sia stato usato nei fili di fase (tutti i conduttori portatori di corrente).

Advarsel

Dette produktet er avhengig av bygningens installasjoner av kortslutningsbeskyttelse (overstrøm). Kontroller at det brukes en sikring eller strømbryter som ikke er større enn 120 VAC, 15 A (USA) (240 VAC, 10 A internasjonalt) på faselederne (alle strømførende l edere).

Aviso

Este produto depende das instalações existentes para protecção contra curto-circuito (sobrecarga). Assegure-se de que um fusível ou disjuntor não superior a 240 VAC, 10A é utilizado nos condutores de fase (todos os condutores de transporte de corrente).

¡Advertencia!

Este equipo utiliza el sistema de protección contra cortocircuitos (o sobrecorrientes) deló propio edificio. Asegurarse de que se utiliza un fusible o interruptor automático de no más de 240 voltios en corriente alterna (VAC), 10 amperios del estándar internacional (120 VAC, 15 amperios del estándar USA) en los hilos de fase (todos aquéllos portadores de corriente).

Varning!

Denna produkt är beroende av i byggnaden installerat kortslutningsskydd (överströmsskydd). Kontrollera att säkring eller överspänningsskydd används på fasledarna (samtliga strömförande ledare) ¥ för int ernationellt bruk max. 240 V växelström, 10 A (iþUSA m ax. 120 V växels tröm, 15 A) .

Warning

The device is designed to work with TN power systems.

Waarschuwing

Het apparaat is ontworpen om te functioneren met TN energiesystemen.

Varoitus

Koje on suunniteltu toimimaan TN-sähkövoimajärjestelmien yhteydessä.

Attention

Ce dispositif a été conçu pour fonctionner avec des systèmes d'alimentation TN.

Warnung

Das Gerät ist für di e Verwendung mit TN-Stromsystemen ausgelegt.

Page 64

A-8

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

Chapter A Translated Safety Warnings

TN Power Warning

Avvertenza

Il dispositivo è stato progettato per l’uso con sistemi di alimentazione TN.

Advarsel

Utstyret er utfomet til bruk med TN-strømsystemer.

Aviso

O dispositivo foi criado para operar com sistemas de corrente TN.

¡Advertencia!

El equipo está diseñado para trabajar con sistemas de alimentación tipo TN.

Varning!

Enheten är konstruerad för användning tillsammans med elkraftssystem av TN-typ.

Page 65

IN-1

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

INDEX

Numerics

10/100 PC port 2-3 10/100 SW port 2-3

abbreviations, time zone 3-8 accessing 3-12, 5-6 access port 2-3 Audit Connection com mand 3-2 Audit Endpoint comma nd 3-2

book objectives viii buttons 1-3, 1-4, 3-11

call forward 1-7 call transfer 1-7 call waiting 1-7 character su ppo rt 1-8 conventions, docum ent ix Create Connect ion comm and 3-2

debug command 5-2 default configurat ion f ile 3-2, 3-9 Delete Connection command 3-2 dialing pad 1-4

DNS description 1-7 documentation convent ions ix Domain Name S ystem ( D NS) 1-6, 1-7 DTMF 1-6 DTMF payload 3-4 Dynamic Host Configur ati on Pro toc ol ( DHCP) 1-7, 3-1,

3-11

Endpoint Configuratio n command 3-2

features 1-2 firmware

updating

3-13

firmware version, view ing 3-12 footstand, adjusting 1-3 function toggles 1-4

G.711 a-law codec 1-6 G.711 u-law co dec 1-6 G.729a codec 1-6

handset 1-4 headset 2-4, 4-1, 4-2

Page 66

Index

IN-2

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

ICMP, description 1-7 image_version configuration parameter 3-2 image upgrade 3-16 image version 3-5 Internet Control Message Protocol (ICMP) 1-7 Internet Protocol (IP) 1-7 IP description 1-7 ISO 8859-1 Latin1 char acte rs 1-8

language support 1-8 LCD screen 1-3, 4-2 Local Connection O ptio ns ( LC Os) 1-6

MAC address 3-2 messages, status 5-6 Message Waiting Indi cat ion 1-7 MGCDefault.cnf file 3-2 MGCmacaddress.cnf file 3-2 MGCP commands 3-2 Modify Connection command 3-2 mute 4-2

network

connections

2-3

port 2-3

statistics 5-6 network address translation (NAT 3-6 network connections, a cce ss port 2-3 Notification command 3-2 Notification Request command 3-2

notify messag es 1-7

OS79XX.TXT file 3-2

parameters

dtmf_avt_paylo ad

3-4

image_version 3-5 SIP telnet_enable 3-6 tos_media 3-7

phone

connections

2-3

features, physical 1-2 interfaces 1-2 prerequisite s 2-2

supported protocols 1-7, 1-8 port 2-3 power source, Cisco Catalyst switches 2-3 power source, external 2-3 prerequisite s 2-2 protocols 1-7, 1-8

TFTP 1-7

Real-Time Transport Protocol (RTP) 1-7 remote reboot 3-16 resetting

network statistics

5-7

Restart in Progress command 3-2 RFC 1-6, 1-7 RTP 1-7

Page 67

Index

IN-3

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1

saftey warnings 2-1 scroll key 1-4 SDP, description 1-7 Session Description Pro toco l (SD P) 1-7 show command 5-4 Simple Network Time Protocol (SNTP) 1-7 SNTP, description 1-7 specifying 3-5

DTMF payload 3-4

image version 3-5 specifying, TOS media 3-7 statistics, network 5-6 status information

accessing

5-6

status information, accessing 3-12, 5-6

TCP, description 1-7 telnet_enable para mete r 3-6 Telnet sessions 5-1 TFTP, description 1-7 TFTP server, t ime out 3-2, 3-3 three-way calling 1-7 time zone abbreviations 3-8 TOS media

specifying

3-7

traceroute command 5-5 translated safety warnings A-1 Transmission Control Proto col (TCP) 1-7 Trivial File Transfer Protocol (TFTP) 1-7 troubleshooting 5-1 tty command 5-6 type of service (ToS) bit 1-6

UDP, description 1-8 updating

firmware

3-13

upgrade 3-16 upgrade scenarios 3-13

release 5.0 and 5.1 3-14

release 5.0 an d release 5.1 3-13 user configuration fil e 3-2 User Datagram Pr otoc ol (UD P) 1-8

viewing firmware v ers ion 3-12 voice activity detection (VAD) 1-6 volume, adjusting 4-2

what’s new in this release

release 5.0

1-1

release 5.1 1-1

XML 1-6, 3-2

Page 68

Index

IN-4

Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1