Cisco CallManager Administration Guide

Release 3.0(9)

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
Customer Order Number: DOC-7810450= Text Part Number: OL-1047-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. 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 RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT 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 header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE 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 DAMAGES. AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Discover All That’s Possible, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Voice LAN, Wavelength Router, WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other brands, names, or 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. (0101R) Cisco CallManager Administration Guide Copyright © 2001, Cisco Systems, Inc. All rights reserved.

C O N T E N T S

Preface xxi Purpose xxi Audience xxii Organization xxii Related Documentation xxv Conventions xxvi Obtaining Documentation xxvii World Wide Web xxvii Documentation CD-ROM xxviii Ordering Documentation xxviii Documentation Feedback xxviii Obtaining Technical Assistance xxix Cisco.com xxix Technical Assistance Center xxx Contacting TAC by Using the Cisco TAC Website xxx Contacting TAC by Telephone xxx
1

PART

System Description
1

CHAPTER

Introduction 1-1 Understanding Distributed Call Processing 2-1 Clusters 2-1

CHAPTER

2

Cisco CallManager Administration Guide OL-1047-01

iii

Contents

Configuring a Distributed System 2-3
3

CHAPTER

Understanding Redundancy 3-1 Groups and Clusters 3-1 Components of a Group 3-2 Combining Redundancy with Distributed Call Processing 3-3 Configuring Call Processing Redundancy 3-5

CHAPTER

4

Understanding Auto-Registration 4-1 Enabling Auto-Registration 4-2 Disabling Auto-Registration 4-6 Reusing Auto-Registration Numbers 4-7

CHAPTER

5

Understanding Call Admission Control 5-1 Locations 5-2 Gatekeepers 5-3

CHAPTER

6

Understanding Route Plans 6-1 Route Plan Overview 6-1 Understanding Route Pattern Wildcards and Special Characters 6-7 Understanding Closest-Match Routing 6-11 Understanding Discard Digits Instructions 6-12 Understanding Route Patterns 6-24 Understanding the External Route Plan Wizard 6-25 Generated Route Filters 6-26 Generated Route Groups 6-27 Generated Route Lists 6-27

Cisco CallManager Administration Guide

iv

OL-1047-01

Contents

Generated Route Patterns 6-29
7

CHAPTER

Understanding Device Support 7-1 Using DHCP and TFTP 7-1 Understanding DHCP and TFTP 7-2 Accessing the TFTP Server 7-3 Understanding How Devices Identify the TFTP Server 7-4 Understanding Device Loads 7-6 Updating Device Loads 7-7 Updating a Load on a Cisco IP Phone 7-8 Updating the Load on a Cisco Gateway 7-9 Verifying the Load on Cisco IP Phones 7-9 Adding Devices to Cisco CallManager 7-10

CHAPTER

8

Understanding Cisco WebAttendant 8-1 Cisco WebAttendant Configuration Checklist 8-2 Configuring Cisco CallManager for Cisco WebAttendant 8-3 Cisco WebAttendant Users 8-4 Setting Up Cisco IP Phones for Use with Cisco WebAttendant 8-4 Understanding Pilot Points and Hunt Groups 8-6 Understanding the Cisco Telephony Call Dispatcher 8-9 Client Installation and Configuration 8-10 Cisco WebAttendant Client Requirements 8-10 Client Installation 8-11 Client Configuration 8-11 Sharing Default Directory Database Information 8-11 Cisco WebAttendant Redundancy 8-13

Cisco CallManager Administration Guide OL-1047-01

v

Contents

Tips and Troubleshooting 8-14 Viewing Cisco WebAttendant Performance Monitors 8-14 Troubleshooting 8-16
9

CHAPTER

Understanding the LDAP Directory 9-1 Cisco CallManager Directory 9-1 Using the Embedded Directory 9-2 Scenario 1: Using the Embedded Directory 9-3 Using the Embedded Directory 9-3 Managing User Entries in the Embedded Directory 9-4 Scenario 2: Using the Embedded Directory on a Pilot System 9-4 Managing Users in the Pilot System 9-5

CHAPTER

10

Understanding Service Parameters 10-1 Cisco CallManager Service Parameters 10-2 Cisco TFTP Service Parameters 10-20 Cisco Messaging Interface Service Parameters 10-22 Cisco IP Voice Media Streaming Service Parameters 10-28 Cisco Database Layer Service Parameters 10-29 Cisco Telephony Call Dispatcher Service Parameters 10-30

PART

2

System Configuration
11

CHAPTER

Server

11-1

Adding a Server 11-2 Updating a Server 11-3 Deleting a Server 11-4

Cisco CallManager Administration Guide

vi

OL-1047-01

Contents

CHAPTER

12

Configuring Cisco CallManager 12-1 Adding a Cisco CallManager 12-1 Updating a Cisco CallManager 12-5 Deleting a Cisco CallManager 12-6

CHAPTER

13

Configuring Cisco CallManager Groups 13-1 Adding a Cisco CallManager Group 13-2 Updating a Cisco CallManager Group 13-4 Copying a Cisco CallManager Group 13-5 Deleting a Cisco CallManager Group 13-6

CHAPTER

14

Configuring Date/Time Groups 14-1 Adding a Date/Time Group 14-2 Updating a Date/Time Group 14-3 Deleting a Date/Time Group 14-4

CHAPTER

15

Setting Device Defaults 15-1 Updating Device Defaults 15-2

CHAPTER

16

Configuring Regions 16-1 Understanding Regions 16-1 Adding a Region 16-3 Updating a Region 16-4 Deleting a Region 16-5

CHAPTER

17

Configuring Device Pools 17-1 Adding a Device Pool 17-1

Cisco CallManager Administration Guide OL-1047-01

vii

Contents

Updating a Device Pool 17-3 Deleting a Device Pool 17-4
18

CHAPTER

Understanding Enterprise Parameters 18-1 Updating Enterprise Parameters 18-4

CHAPTER

19

Configuring Locations 19-1 Understanding Locations 19-2 Locations and Regions 19-3 Bandwidth Calculations 19-4 Adding a Location 19-5 Updating a Location 19-7 Deleting a Location 19-7

CHAPTER

20

Starting and Stopping Cisco CallManager 20-1 Using the Control Center 20-2 Using Windows Services 20-3 Using the Cisco CallManager Reset Button 20-4

PART

3

Route Configuration
21

CHAPTER

Configuring Partitions 21-1 Adding a Partition 21-1 Deleting a Partition 21-2

CHAPTER

22

Configuring Calling Search Spaces 22-1 Adding a Calling Search Space 22-1 Updating a Calling Search Space 22-3

Cisco CallManager Administration Guide

viii

OL-1047-01

Contents

Copying a Calling Search Space 22-3 Deleting a Calling Search Space 22-4
23

CHAPTER

Configuring Route Filters 23-1 Understanding Route Filter Tags 23-2 Adding a Route Filter 23-5 Updating a Route Filter 23-7 Copying a Route Filter 23-7 Adding Route Filter Clauses 23-9 Removing Route Filter Clauses 23-10 Deleting a Route Filter 23-11

CHAPTER

24

Configuring Route Groups 24-1 Understanding Route Groups 24-2 Adding a Route Group 24-2 Adding Devices to a Route Group 24-3 Removing Devices from a Route Group 24-5 Updating a Route Group 24-6 Deleting a Route Group 24-7

CHAPTER

25

Configuring Route Lists 25-1 Understanding Calling Party Transform Settings 25-2 Understanding Called Party Transform Settings 25-4 Adding a Route List 25-6 Adding Route Groups to a Route List 25-8 Removing Route Groups from a Route List 25-10 Changing the Order of Route Groups in a Route List 25-11

Cisco CallManager Administration Guide OL-1047-01

ix

Contents

Deleting a Route List 25-12
26

CHAPTER

Configuring Route Patterns 26-1 Adding a Route Pattern 26-1 Updating a Route Pattern 26-4 Copying a Route Pattern 26-5 Deleting a Route Pattern 26-6

CHAPTER

27

Configuring Translation Patterns 27-1 Understanding Translation Patterns 27-1 Adding a Translation Pattern 27-2 Updating a Translation Pattern 27-4 Copying a Translation Pattern 27-5 Deleting a Translation Pattern 27-6

CHAPTER

28

Using the External Route Plan Wizard 28-1 Creating an External Route Plan 28-2 Setting the Routing Options 28-2 Providing Tenant Information 28-4 Entering Location Information 28-5 Selecting Gateways 28-6 Providing Gateway Information 28-8 Generating the External Route Plan 28-9 Confirming the External Route Plan 28-10 Finishing the External Route Plan 28-11 Deleting an External Route Plan 28-11

Cisco CallManager Administration Guide

x

OL-1047-01

Contents

CHAPTER

29

Using Route Plan Report 29-1 Viewing All Route Plan Records 29-2 Viewing Route Plan Reports in a File 29-3

PART

4

Service Configuration
30

CHAPTER

Cisco Messaging Interface 30-1 Most Commonly Changed CMI Service Parameters 30-2 Adding Cisco Messaging Interface Service on the Cisco CallManager 30-5 Deleting Cisco Messaging Interface Service From a Server 30-6 Configuring Cisco Messaging Interface Service Parameters 30-8 Configuring Cisco Messaging Interface Trace Parameters 30-10

CHAPTER

31

Configuring Cisco TFTP 31-1 Inserting Cisco TFTP Service on a Server 31-2 Deleting Cisco TFTP Service From a Server 31-4 Configuring Cisco TFTP Command Line Parameters 31-5 Deleting Cisco TFTP Command Line Parameters 31-7 Configuring Cisco TFTP Trace Parameters 31-9

CHAPTER

32

Configuring Cisco WebAttendants 32-1 Configuring Pilot Points 32-2 Adding a Pilot Point 32-2 Viewing, Updating, or Deleting a Pilot Point 32-4 Configuring Hunt Groups 32-5 Adding Hunt Group Members 32-5 Viewing, Updating, or Deleting Hunt Group Members 32-9

Cisco CallManager Administration Guide OL-1047-01

xi

Contents

Configuring Cisco WebAttendant Users 32-10 Adding a Cisco WebAttendant User 32-10 Viewing, Updating, and Deleting Cisco WebAttendant Users 32-11 Installing the Cisco WebAttendant Client 32-13 Configuring Cisco WebAttendant Client Settings 32-14 Cisco WebAttendant Server Configuration 32-18 Setting Up the wauser Shared Directory for Cisco WebAttendant 32-19 Starting the Telephony Call Dispatcher 32-20
33

CHAPTER

Configuring Conference Bridges 33-1 Understanding Conference Devices 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc 33-3 Using an Ad-Hoc Conference Bridge 33-4 Using a Meet-Me Conference Bridge 33-5 Adding a Software Conference Device 33-6 Adding a Hardware Conference Device 33-8 Updating a Conference Device 33-10 Deleting a Conference Device 33-11 Updating Conference Bridge Parameters 33-12 Adding a Meet-Me Number Pattern 33-14 Updating a Meet-Me Number Pattern 33-15 Deleting a Meet-Me Number Pattern 33-17

CHAPTER

34

Configuring Media Termination Point 34-1 Planning Your MTP Configuration 34-3 Avoiding Call Failure/User Alert 34-4 Adding a Media Termination Point 34-5

Cisco CallManager Administration Guide

xii

OL-1047-01

Contents Updating a Media Termination Point 34-7 Deleting a Media Termination Point 34-8 35 CHAPTER Configuring Service Parameters 35-1 Service Parameter Restart Conditions 35-2 Adding a New Service on a Server 35-3 Deleting a Service From a Server 35-4 Adding a New Service Parameter 35-5 Updating a Service Parameter 35-7 Deleting a Service Parameter 35-9 CHAPTER 36 Configuring Trace 36-1 Understanding Trace Configuration 36-2 Trace Levels 36-2 Time 36-3 User Mask 36-3 Event Level 36-6 Components 36-7 Recommended Trace Settings 36-9 Adding a New Service and Trace Configuration 36-10 Updating a Trace Configuration 36-12 Deleting a Trace Configuration 36-13 Deleting a Service 36-14 37 CHAPTER Configuring Transcoder 37-1 Configuring a Transcoder 37-3 Updating a Transcoder 37-4 Cisco CallManager Administration Guide OL-1047-01 xiii .

Contents Copying a Transcoder 37-5 Deleting a Transcoder 37-6 38 CHAPTER Starting and Stopping Services Using the Control Center Starting and Stopping Services on a Single Server 38-2 Selecting Services to Start and Stop for All Servers 38-3 38-1 PART 5 Feature Configuration 39 CHAPTER Configuring Call Park 39-1 Adding a Call Park Number 39-2 Updating a Call Park Number 39-3 Deleting a Call Park Number 39-4 40 CHAPTER Configuring Call Pickup 40-1 Configuring Call Pickup 40-2 Adding a Call Pickup Group Number 40-2 Updating a Call Pickup Group Number 40-3 Deleting a Call Pickup Group Number 40-4 Assigning Directory Numbers to a Call Pickup Group 40-5 41 CHAPTER Configuring Cisco IP Phone Services 41-1 Understanding Cisco IP Phone Services 41-2 Adding a Cisco IP Phone Service 41-3 Adding a Cisco IP Phone Service Parameter 41-5 Updating a Cisco IP Phone Service 41-6 Deleting a Cisco IP Phone Service 41-7 Updating a Cisco IP Phone Service Parameter 41-8 Cisco CallManager Administration Guide xiv OL-1047-01 .

Contents Deleting a Cisco IP Phone Service Parameter 41-9 6 PART Configuring Devices in Cisco CallManager 42 CHAPTER Configuring CTI Route Points 42-1 Adding a CTI Route Point 42-2 Modifying a CTI Route Point 42-3 Deleting a CTI Route Point 42-4 Finding and Listing CTI Route Points 42-5 Resetting a CTI Route Point 42-6 CHAPTER 43 Configuring Cisco uOne Voice Messaging 43-1 Cisco uOne Port Wizard 43-3 Adding a New Cisco uOne Server and Ports 43-3 Adding Ports to an Existing Cisco uOne Server 43-6 Deleting Ports from an Existing Cisco uOne Server 43-7 Configuring Cisco CallManager Service Parameters for Cisco uOne 43-8 Setting up the MWI Device 43-11 Adding Cisco uOne Ports 43-12 Deleting a Cisco uOne Port 43-16 Resetting a Cisco uOne Port 43-17 Updating a Cisco uOne Port 43-18 Copying an Existing Cisco uOne Port 43-19 CHAPTER 44 Configuring a Gatekeeper 44-1 Adding a Gatekeeper 44-1 Deleting the Gatekeeper 44-6 Cisco CallManager Administration Guide OL-1047-01 xv .

323 Devices 45-6 Adding Gateways to Cisco CallManager 45-7 Adding an Analog Gateway 45-7 Adding Digital Gateways 45-9 Adding an MGCP Gateway 45-21 Adding an H.Contents Resetting or Restarting the Gatekeeper 44-6 Modifying the Gatekeeper 44-7 45 CHAPTER Configuring Gateways 45-1 Understanding Supported Gateways 45-2 Understanding Cisco Access Gateways 45-3 Cisco Access Analog Gateways 45-3 Cisco Access Digital Trunk Gateways 45-4 Understanding Catalyst 6000 Gateways 45-4 Catalyst 6000 Family Analog Line Card 45-4 Catalyst 6000 Family T1/E1 Line Cards 45-5 Catalyst 6000 Family DSP Services Card 45-5 Cisco VG200 Gateway 45-6 Understanding Other H.323 Gateway 45-23 Configuring Gateway Ports in Cisco CallManager 45-27 Configuring Ports on Analog Gateways 45-27 Configuring POTS Ports 45-27 Configuring Loop Start Ports 45-31 Configuring Ports on a Cisco MGCP Gateway 45-35 Configuring FXS Ports on a Cisco MGCP Gateway 45-35 Configuring FXO Ports on Cisco MGCP Gateways 45-38 Configuring Ground Start on an MGCP Gateway 45-38 Cisco CallManager Administration Guide xvi OL-1047-01 .

Contents Configuring Loop Start on MGCP Gateways 45-40 Modifying Gateways 45-41 Deleting Gateways 45-42 Resetting Gateways 45-42 Updating Gateways 45-43 Finding Specific Gateways 45-44 Searching by Device Name 45-44 Searching by Description 45-45 Searching by Directory Number 45-46 46 CHAPTER Configuring Cisco IP Phones in Cisco CallManager 46-1 Understanding Cisco IP Phones 46-2 Cisco IP Phone 7900 Family 46-2 Cisco IP Phone 7960 46-3 Cisco IP Phone 7940 46-3 Cisco IP Phone 7910 46-4 Cisco IP Phone 12 SP+ 46-4 Cisco IP Phone 30 VIP 46-4 CTI Ports 46-5 H.323 Clients 46-5 Configuring Cisco IP Phones 46-5 Displaying the MAC Address of a Phone 46-6 Adding a Phone 46-7 Deleting a Phone 46-11 Resetting a Phone 46-12 Updating a Phone 46-13 Copying an Existing Phone 46-14 Cisco CallManager Administration Guide OL-1047-01 xvii .

Contents Finding a Phone 46-15 Tips for Finding a Phone 46-16 Configuring Phone Features 46-16 Configuring Call Waiting 46-17 Configuring Call Forward 46-17 Configuring Call Park 46-17 Configuring Call Pickup 46-18 Configuring Directory Numbers 46-18 Adding a Directory Number 46-19 Deleting a Directory Number 46-23 Updating a Directory Number 46-24 Shared Line Appearances 46-25 47 CHAPTER Configuring Phone Button Templates 47-1 Understanding Default Phone Button Templates 47-1 Default Cisco IP Phone 7960 Template 47-2 Default Cisco IP Phone 7940 Templates 47-3 Default Cisco IP Phone 7910 Templates 47-3 Default Cisco IP Phone 30 SP+ Template 47-3 Default Cisco IP Phone 30 VIP Template 47-4 Default Cisco IP Phone 12-Series Template 47-4 Adding Phone Button Templates 47-5 Guidelines for Creating Custom Templates 47-7 Modifying Phone Button Templates 47-9 Renaming a Phone Button Template 47-10 Deleting a Phone Button Template 47-11 Updating a Phone Button Template 47-12 Cisco CallManager Administration Guide xviii OL-1047-01 .

Contents PART 7 User Configuration 48 CHAPTER Adding a New User 48-1 How Cisco JTAPI uses the Directory 48-2 Using the Embedded Directory 48-2 Adding a User 48-2 Assigning Devices to a User 48-3 CHAPTER 49 Searching the Global Directory 49-1 Using Basic User Search 49-1 Using Advanced User Search 49-3 PART 8 Appendices A APPENDIX Cisco TAPI Service Provider Installation and Configuration A-1 Installing the Cisco TAPI Service Provider A-1 Activating the Cisco TAPI Service Provider A-3 Configuring the Cisco TAPI Service Provider A-4 Uninstalling the Cisco TAPI Service Provider A-9 Installing the Wave Driver A-10 Uninstalling the Wave Driver A-12 Verifying the Cisco TAPI Service Provider Installation A-14 Setting up Client-Server Configuration A-16 APPENDIX B Cisco JTAPI Installation and Configuration B-1 Installing the Cisco JTAPI Software B-2 Verifying the Installation B-4 Cisco CallManager Administration Guide OL-1047-01 xix .

xml File Format C-2 PCM File Requirements for Custom Ring Types C-3 INDEX Cisco CallManager Administration Guide xx OL-1047-01 .Contents Configuring Cisco JTAPI Tracing B-4 Trace Levels B-5 Debug Levels B-7 Log Destination B-8 Cisco CallManager B-11 Other JTAPI Preferences Settings B-12 JTAPI Preferences on non-Microsoft environments B-13 Administering User Information for JTAPI and TAPI Applications B-14 C APPENDIX Creating Custom Cisco IP Phone Rings C-1 Creating a Custom Phone Ring C-2 RingList.

audience. page xxvii Obtaining Technical Assistance. page xxvi Obtaining Documentation. page xxii Related Documentation. Cisco CallManager Administration Guide OL-1047-01 xxi . page xxv Conventions. page xxi Audience. and provides information on how to obtain related documentation. page xxii Organization. page xxix Purpose The Cisco CallManager Administration Guide provides instructions for administering the Cisco CallManager system. It also provides references for commands and conceptual information to assist you in using Cisco CallManager. The preface covers these topics: • • • • • • • Purpose. and conventions of this guide. This guide includes descriptions of procedural tasks you complete using Cisco CallManager.Preface This preface describes the purpose. organization.

which describe general topics related to the configuration and operation of Cisco CallManager: • • • • • • • • • • Chapter 1. “Understanding Cisco WebAttendant” Chapter 9.Preface Audience Audience The Cisco CallManager Administration Guide is written for network administrators responsible for managing the Cisco CallManager system. Organization This guide is organized as shown in the following table: Part Part 1 Description “System Description” Contains the following chapters. This guide requires knowledge of telephony and IP networking technology. “Understanding Auto-Registration” Chapter 5. “Understanding Service Parameters” Cisco CallManager Administration Guide xxii OL-1047-01 . “Understanding Route Plans” Chapter 7. “Introduction” Chapter 2. “Understanding Distributed Call Processing” Chapter 3. “Understanding Call Admission Control” Chapter 6. “Understanding the LDAP Directory” Chapter 10. “Understanding Redundancy” Chapter 4. “Understanding Device Support” Chapter 8.

“Server” Chapter 12. “Configuring Calling Search Spaces” Chapter 23.Preface Organization Part Part 2 Description “System Configuration” Contains the following chapters. which explain how to configure route plans in Cisco CallManager: • • • • • • • • • Chapter 21. “Configuring Route Filters” Chapter 24. “Configuring Device Pools” Chapter 18. “Configuring Translation Patterns” Chapter 28. “Configuring Date/Time Groups” Chapter 15. “Configuring Cisco CallManager Groups” Chapter 14. “Configuring Route Lists” Chapter 26. which explain how to configure the system parameters used by Cisco CallManager: • • • • • • • • • • Chapter 11. “Starting and Stopping Cisco CallManager” Part 3 “Route Configuration” Contains the following chapters. “Configuring Locations” Chapter 20. “Using Route Plan Report” Cisco CallManager Administration Guide OL-1047-01 xxiii . “Setting Device Defaults” Chapter 16. “Configuring Route Patterns” Chapter 27. “Configuring Partitions” Chapter 22. “Configuring Cisco CallManager” Chapter 13. “Configuring Regions” Chapter 17. “Configuring Route Groups” Chapter 25. “Understanding Enterprise Parameters” Chapter 19. “Using the External Route Plan Wizard” Chapter 29.

“Configuring Cisco uOne Voice Messaging” Chapter 44. which explain how to configure user features: • • Chapter 39. “Configuring Call Pickup” Part 6 “Configuring Devices in Cisco CallManager” Contains the following chapters. “Cisco Messaging Interface” Chapter 31. “Configuring Cisco IP Phones in Cisco CallManager” Chapter 47. “Configuring CTI Route Points” Chapter 43. which explain how to configure devices in Cisco CallManager: • • • • • • Chapter 42. “Starting and Stopping Services Using the Control Center” Part 5 “Feature Configuration” Contains the following chapters. “Configuring Gateways” Chapter 46.Preface Organization Part Part 4 Description “Service Configuration” Contains the following chapters. “Configuring Service Parameters” Chapter 36. “Configuring Cisco TFTP” Chapter 32. “Configuring a Gatekeeper” Chapter 45. “Configuring Conference Bridges” Chapter 34. “Configuring Call Park” Chapter 40. which explain how to configure services used in conjunction with Cisco CallManager: • • • • • • • • • Chapter 30. “Configuring Transcoder” Chapter 38. “Configuring Media Termination Point” Chapter 35. “Configuring Trace” Chapter 37. “Configuring Cisco WebAttendants” Chapter 33. “Configuring Phone Button Templates” Cisco CallManager Administration Guide xxiv OL-1047-01 .

0 Cisco CallManager v3.Preface Related Documentation Part Part 7 Description “User Configuration” Contains the following chapters. “Cisco TAPI Service Provider Installation and Configuration” Appendix B. “Cisco JTAPI Installation and Configuration” Appendix C. which explain how to configure user and directory information: • • Chapter 48. “Adding a New User” Chapter 49. “Searching the Global Directory” Part 8 “Appendices” Contains the following chapters. which include additional information related to Cisco CallManager and IP telephony: • • • Appendix A. “Creating Custom Cisco IP Phone Rings” Related Documentation Refer to the following documents for further information about related Cisco IP Telephony applications and products: • • • • • • Installing Cisco CallManager on the Cisco Media Convergence Server Release Notes for Cisco CallManager Release 3.0 Remote Serviceability Users Guide Hardware Configuration Guide for the Cisco Voice Gateway 200 Software Configuration Guide for the Cisco Voice Gateway 200 Cisco IP Phone 7900 Family Administration Guide Cisco CallManager Administration Guide OL-1047-01 xxv .

Cisco CallManager Administration Guide xxvi OL-1047-01 . This pointer highlights an important line of text in an example. the key combination ^D in a screen display means hold down the Control key while you press the D key. Elements in square brackets are optional. < > Notes use the following conventions: Note Means reader take note. ^ The symbol ^ represents the key labeled Control—for example. such as passwords. Alternative keywords are grouped in braces and separated by vertical bars. Arguments for which you supply values are in italics. Information you must enter is in boldface screen screen boldface screen font. are in angle brackets. Do not use quotation marks around the string or the string will include the quotation marks.Preface Conventions Conventions This document uses the following conventions: Convention boldface font italic font [ ] {x|y|z} [x|y|z] string Description Commands and keywords are in boldface. A nonquoted set of characters. Nonprinting characters. Notes contain helpful suggestions or references to material not covered in the publication. Optional alternative keywords are grouped in brackets and separated by vertical bars. font Terminal sessions and information the system displays are in screen font. font italic screen font Arguments for which you supply values are in italic screen font.

Cautions use the following conventions: Caution Means reader be careful. In this situation. Cisco CallManager Administration Guide OL-1047-01 xxvii . you must be aware of the hazards involved with electrical circuitry and familiar with standard practices for preventing accidents. You can save time by performing the action described in the paragraph. Tips use the following conventions: Tips Means the information contains useful tips. You are in a situation that could cause bodily injury. you might do something that could result in equipment damage or loss of data.Preface Obtaining Documentation Timesavers use the following conventions: Timesaver Means the described action saves time. Warnings use the following conventions: Warning This warning symbol means danger. Obtaining Documentation The following sections provide sources for obtaining documentation from Cisco Systems. Before you work on any equipment.

com/cgi-bin/order/order_root. USA) at 408 526-7208 or.com http://www-europe.cisco.pl • Registered Cisco.cisco. Cisco CallManager Administration Guide xxviii OL-1047-01 .com Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package. The CD-ROM package is available as a single unit or through an annual subscription.com http://www-china.Preface Obtaining Documentation World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: • • • http://www.cisco.cisco. which ships with your product.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California.com users can order the Documentation CD-ROM through the online Subscription Store: http://www. Ordering Documentation Cisco documentation is available in the following ways: • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace: http://www. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. in North America. by calling 800 553-NETS(6387).com/go/subscription • Nonregistered Cisco.cisco.

and certification programs are also available. This highly integrated Internet application is a powerful. you can find information about Cisco and our networking solutions. or write to the following address: Attn Document Resource Connection Cisco Systems.com registered users. and order Cisco learning materials and merchandise. you can resolve technical issues with online technical support. Valuable online skill assessment.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity.com. To submit your comments by mail. open access to Cisco information and resources at anytime. networked services that provides immediate. 170 West Tasman Drive San Jose.com. Inc. and programs. click Submit to send it to Cisco. and sample configurations from online tools. In addition. For Cisco. After you complete the form.com Cisco. CA 95134-9883 We appreciate your comments. troubleshooting tips. You can e-mail your comments to bug-doc@cisco. Cisco. Click Feedback in the toolbar and select Documentation. download and test software packages. additional troubleshooting tools are available from the TAC website. services. use the response card behind the front cover of your document.com as a starting point for all technical assistance. from anywhere in the world. Through Cisco. Obtaining Technical Assistance Cisco provides Cisco. Cisco.Preface Obtaining Technical Assistance Documentation Feedback If you are reading Cisco product documentation on the World Wide Web. Customers and partners can obtain documentation. you can submit technical comments electronically. training. easy-to-use tool for doing business with Cisco. Cisco CallManager Administration Guide OL-1047-01 xxix .com is the foundation of a suite of interactive.

com Technical Assistance Center The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract. Network functionality is noticeably impaired.cisco. P4—You need information or assistance on Cisco product capabilities. To register for Cisco.com/register/ If you cannot resolve your technical issue by using the TAC online resources.com/tac P3 and P4 level problems are defined as follows: • • P3—Your network performance is degraded.com/tac/caseopen Cisco CallManager Administration Guide xxx OL-1047-01 . and view benefits specific to their relationships with Cisco. go to the following website: http://www.com to obtain additional personalized information and services. In each of the above cases.com.cisco. use the Cisco TAC website to quickly find answers to your questions.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www. but most business operations continue.cisco. Registered users can order products. To access Cisco. Contacting TAC by Using the Cisco TAC Website If you have a priority level 3 (P3) or priority level 4 (P4) problem. check on the status of an order.cisco.Preface Obtaining Technical Assistance Customers and partners can self-register on Cisco.com. go to the following website: http://www. or basic product configuration. access technical support. Cisco. product installation. contact TAC by going to the TAC website: http://www.

No workaround is available. contact TAC by telephone and immediately open a case. causing a critical impact to business operations if service is not restored quickly. No workaround is available.com/warp/public/687/Directory/DirTAC. To obtain a directory of toll-free numbers for your country. affecting significant aspects of your business operations. go to the following website: http://www. Cisco CallManager Administration Guide OL-1047-01 xxxi . P2—Your production network is severely degraded.cisco.Preface Obtaining Technical Assistance Contacting TAC by Telephone If you have a priority level 1(P1) or priority level 2 (P2) problem.shtml P1 and P2 level problems are defined as follows: • • P1—Your production network is down.

Preface Obtaining Technical Assistance Cisco CallManager Administration Guide xxxii OL-1047-01 .

“Understanding Service Parameters” . “Introduction” • Chapter 2. “Understanding Cisco WebAttendant” • Chapter 9. “Understanding Auto-Registration” • Chapter 5.P A R T 1 System Description The following chapters describe general topics related to the configuration and operation of Cisco CallManager: • Chapter 1. “Understanding Route Plans” • Chapter 7. “Understanding the LDAP Directory” • Chapter 10. “Understanding Distributed Call Processing” • Chapter 3. “Understanding Call Admission Control” • Chapter 6. “Understanding Redundancy” • Chapter 4. “Understanding Device Support” • Chapter 8.

.

Additional data. part of Cisco AVVID (Architecture for Voice. This architecture improves system availability and scalability. Because Cisco CallManager is a software application. speed dial. Voice-over-IP (VoIP) gateways. Because this suite of voice applications exists. conference. transfer. services. and interactive multimedia response systems interact through Cisco CallManager's open telephony application programming interface (API). and applications across an IP network provides a distributed. The Cisco CallManager system extends enterprise telephony features and functions to packet telephony network devices such as IP phones. Distribution of Cisco CallManager and all Cisco IP Phones. last-number redial. enhancing its capabilities in production environments only requires upgrading software on the server platform. thereby avoiding expensive hardware upgrade costs. virtual telephony network. and other features extend to IP phones and gateways. Supplementary and enhanced services such as hold.C H A P T E R 1 Introduction Cisco CallManager is the software-based call-processing component of the Cisco IP Telephony solution. there is no need for special-purpose voice processing hardware. and multimedia applications. multimedia conferencing. collaborative contact centers. multiple line appearances. Call Cisco CallManager Administration Guide OL-1047-01 1-1 . The Cisco Media Convergence Server serves as the high-availability server platform for Cisco CallManager call processing. forward. media processing devices. voice. gateways. Video and Integrated Data). Key Features and Benefits The Cisco CallManager system includes a suite of integrated voice applications that perform voice conferencing and manual attendant console functions. and applications. automatic route selection. and video services such as unified messaging.

Triple server redundancy improves overall system availability. distributed. Finally. distributed Cisco CallManagers. Cisco IP Contact Center. The benefits include readily available.0 include toll restriction by user group. and availability of the enterprise IP telephony solution. and applications. By interlinking multiple clusters. Further enhancements in Cisco CallManager Release 3. enhancing the scalability and accessibility of the servers to phones.000 users on each cluster. the Cisco IP Phone 7960. This interface also provides access to HTML-based online help for users and administrators. Cisco CallManager comes preinstalled on the Cisco Media Convergence Server.0 Cisco CallManager Release 3. and system serviceability enhancements. Cisco CallManager Administration Guide 1-2 OL-1047-01 . gateways.0 provides capability for up to 10. These applications extend the Cisco CallManager system’s capability and expand the applications space within Cisco AVVID. the system capacity increases to tens of thousands of users for each multisite system. Release 3. and automatically diverts calls to alternate Public Switched Telephone Network (PSTN) routes when WAN bandwidth is not available. and Cisco SoftPhone interact with the Cisco CallManager through telephony APIs. A web-browsable interface to the configuration database provides the capability for remote device and system configuration. software-only voice and multimedia applications such as the Cisco Low-End Interactive Voice Response system.Chapter 1 Introduction admission control ensures that voice Quality of Service (QoS) is maintained across constricted WAN link. New for Cisco CallManager Release 3. Cisco Automated Attendant. database configuration changes without system restart. Multiple Cisco CallManager servers are clustered and managed as a single entity.0 significantly enhances the scalability. Clustering aggregates the power of multiple. Alterations to the Cisco CallManager Administration user interface reduce the administrative burden when managing a large network of devices and users. distributability. Users benefit from the new call pickup-group feature as well as from the support of the first of a new generation of Cisco IP phones. next-generation applications that can interact with e-business applications.

if the network connection is broken). Periodically. During normal operation. the various Cisco CallManagers in the cluster can continue to operate from their local backup copies of the database. the backup copies of the database are updated automatically from the publisher. Use the following procedure to configure a distributed call processing system: • Configuring a Distributed System.C H A P T E R 2 Understanding Distributed Call Processing Cisco CallManager (release 3. With this feature. When you install the Cisco CallManager software on a server. When the publisher database is restored. Cisco CallManager Administration Guide OL-1047-01 2-1 . normal operation resumes. The other servers in the cluster are all subscribers to the publisher database. If the publisher database becomes unavailable for any reason (for example. You also specify which server is the publisher database for the cluster. Figure 2-1 illustrates a simple cluster containing three Cisco CallManagers. you specify which servers and which Cisco CallManagers belong to the same cluster. page 2-3 Clusters A cluster is a set of Cisco CallManagers that share the same database. all of the Cisco CallManagers in the cluster read data from and write data to the publisher database. but they also maintain their own backup copies of the publisher database.0 and later) provides the capability for distributed call processing. you can distribute the call processing load of your system across multiple Cisco CallManagers in a cluster.

Chapter 2 Clusters Understanding Distributed Call Processing Figure 2-1 Example of a Cluster with Three Cisco CallManagers Server (Database Publisher) Cisco CallManager Publisher database Server (Database Subscriber) Cisco CallManager Server (Database Subscriber) Cisco CallManager IP Network Subscriber database Subscriber database 34031 Cisco CallManager Administration Guide 2-2 OL-1047-01 .

For example. control of the device pools and devices registered with the primary Cisco CallManager transfers to the next Cisco CallManager in the group list. first backup for DP3. assume a simplified system consisting of three Cisco CallManagers in a cluster. Figure 2-2 shows one possible way to configure the Cisco CallManager groups and device pools to distribute the call processing load for this system. you configure Cisco CallManager groups and device pools. CCM1 serves as the primary Cisco CallManager for the devices in DP1 and DP2. Cisco CallManager groups and device pools are logical groupings that may or may not relate to the physical locations of the Cisco CallManagers and devices on your network. CCM2 serves as the primary Cisco CallManager for the devices in DP3 and DP4. and second backup for the devices in DP4. and group G4 is assigned to device pool DP4. and then assign the devices to the device pools in a way that achieves the type of distribution you want.Chapter 2 Understanding Distributed Call Processing Configuring a Distributed System Configuring a Distributed System After installing the Cisco CallManagers that form a cluster. and second backup for the devices in DP1 and DP4. Cisco CallManager group G1 is assigned to device pool DP1. and second backup for the devices in DP4. group G3 is assigned to device pool DP3. Cisco CallManager Administration Guide • • • OL-1047-01 2-3 . This section describes some general steps and guidelines for configuring a distributed call processing system. first backup for DP1. Group G4 is configured as the default group for devices that auto-register. • Four Cisco CallManager groups are configured. you create a distributed system by distributing the devices (such as phones and gateways) among the various Cisco CallManagers in a cluster. If the primary Cisco CallManager in a group fails. CCM3 is the first backup Cisco CallManager for the devices in DP2 and DP3. You can use Cisco CallManager groups to establish redundancy (backup call processors) for the primary Cisco CallManager in the group. To distribute the devices. During normal operation. all device pools and devices that use a particular Cisco CallManager group are controlled by the first (primary) Cisco CallManager in the group. A Cisco CallManager group is an ordered list of up to three Cisco CallManager servers. group G2 is assigned to device pool DP2. with 300 existing Cisco IP Phones and provisions to auto-register new phones as they are added later. you must configure the publisher database to allow these Cisco CallManagers to work as a distributed system. In general.

Chapter 2 Configuring a Distributed System Understanding Distributed Call Processing Figure 2-2 Example of Cisco CallManager Groups and Device Pools DP1 G1 Cisco CallManager Group CCM1 Primary CCM2 First Backup CCM3 Second Backup Device pool (100 phones) DP2 G2 Cisco CallManager Group CCM1 Primary CCM3 First Backup CCM2 Second Backup Device pool (100 phones) DP3 G3 Cisco CallManager Group CCM2 Primary CCM1 First Backup CCM3 Second Backup Device pool (100 phones) DP4 G4 Default Cisco CallManager Group CCM2 Primary CCM3 First Backup CCM1 Second Backup Cisco CallManager Administration Guide 2-4 OL-1047-01 47069 Device pool (Auto-registered phones) .

Chapter 2 Understanding Distributed Call Processing Configuring a Distributed System The following procedure describes general steps for configuring Cisco CallManager groups and device pools. Procedure Step 1 In Cisco CallManager Administration. If desired. enter the partition name and external phone number mask for the phones that auto-register. b. a. auto-registration is enabled on CCM2. Enter the starting and ending directory numbers for the new phones that auto-register with the selected Cisco CallManager. d. and CCM3. For details. In the example shown in Figure 2-2. Enabling auto-registration carries a security risk in that “rogue” phones can automatically register to the Cisco CallManager. see the “Updating a Cisco CallManager” section on page 12-5 and the “Understanding Auto-Registration” section on page 4-1. but similar steps apply to other devices such as gateways. select a Cisco CallManager server. Before You Begin Install the Cisco Media Convergence Servers and Cisco CallManager software to form a cluster of Cisco CallManagers. and enable its auto-registration option. select System > Cisco CallManager. The example shown in Figure 2-2 focuses on the Cisco IP Phones. For details. This will allow new phones to auto-register with that Cisco CallManager as they are added to the system. Click Update to save the changes. CCM2. This enables auto-registration for the selected Cisco CallManager. refer to the installation instructions that shipped with your Cisco CallManager. Cisco CallManager Administration Guide OL-1047-01 2-5 . The example cluster in Figure 2-2 consists of Cisco CallManagers CCM1. Uncheck the “Auto-registration Disabled on this Cisco CallManager” option. c. Caution Auto-registration is disabled by default. Restrict your use of auto-registration to brief periods when bulk phone adds are required.

refer to the “Configuring Device Pools” section on page 17-1 and the “Understanding Redundancy” section on page 3-1. G2. and the Default Cisco CallManager group is assigned to it. However. Cisco CallManager group G1 is assigned to DP1. There can be only one default Cisco CallManager group for auto-registration for the entire cluster.Chapter 2 Configuring a Distributed System Understanding Distributed Call Processing Step 2 In Cisco CallManager Administration. four groups—G1. G2 is assigned to DP2. Step 3 In Cisco CallManager Administration. However. G3 is assigned to DP3. • • A Cisco CallManager group is a prioritized list of up to three Cisco CallManagers. • In the example shown in Figure 2-2. Configure the other device pools and assign the Cisco CallManager groups to the appropriate device pools to achieve the desired load balancing and redundancy. This is the default device pool for devices that auto-register with Cisco CallManager. A device pool named Default is configured automatically when you install Cisco CallManager. see the “Configuring Cisco CallManager Groups” section on page 13-1. and G4—are configured. select System > Cisco CallManager Group to configure groups. select System > Device Pool to configure the device pools for the system. you can update this group to assign a particular Cisco CallManager to it. a. device pool DP4 is configured as the default device pool for auto-registered devices. you can update this device pool to change its settings. For details. and G4 is the default Cisco CallManager auto-registration group. For details. Cisco CallManager Administration Guide 2-6 OL-1047-01 . A Cisco CallManager group named Default is configured automatically when you install the Cisco CallManager software. b. G3. This is the default group for devices that auto-register with Cisco CallManager. or you can select a different device pool as the default for auto-registered devices. and G4 is assigned to DP4. In the example shown in Figure 2-2. or you can select a different group as the default group for auto-registration.

Note After a phone auto-registers with a particular Cisco CallManager.Chapter 2 Understanding Distributed Call Processing Configuring a Distributed System Step 4 In Cisco CallManager Administration. device pool. you can update its configuration and assign it to a different device pool (and a different Cisco CallManager group). page 3-1 Configuring Cisco CallManager Groups. it acquires the device defaults that apply to its device type on that Cisco CallManager. you can reconfigure any device and assign it to a different device pool to achieve better load balancing for your system. As new phones are connected to the system. page 15-1 Cisco CallManager Administration Guide OL-1047-01 2-7 . restart all devices affected by those changes. When a device auto-registers with a particular Cisco CallManager. page 13-1 Configuring Device Pools. select System > Device Defaults to select the default device load. Step 6 After making your configuration changes and saving them in the database. and template for each type of device. Similarly. Step 5 In Cisco CallManager Administration. they auto-register with the default device pool until all the auto-registration directory numbers are consumed (see Step 1). select Device > Phone to configure the Cisco IP Phones and assign them to the appropriate device pools. Related Topics • • • • Understanding Redundancy. Refer to the “Setting Device Defaults” section on page 15-1 for more information. page 17-1 Setting Device Defaults.

Chapter 2 Configuring a Distributed System Understanding Distributed Call Processing Cisco CallManager Administration Guide 2-8 OL-1047-01 .

C H A P T E R 3 Understanding Redundancy Cisco CallManager (release 3. page 3-5 Groups and Clusters Groups and clusters are logical collections of Cisco CallManagers and their associated devices. you can designate backup Cisco CallManagers to handle call processing for a disabled Cisco CallManager. Cisco CallManager Administration Guide OL-1047-01 3-1 . For more information on clusters.0 and later) provides several forms of redundancy: • • Database redundancy—The Cisco CallManagers in a cluster maintain backup copies of their shared database. Call processing redundancy—Using Cisco CallManager groups. The following procedure describes how to configure call processing redundancy using Cisco CallManager groups: • Configuring Call Processing Redundancy. refer to the installation and configuration instructions that shipped with your Cisco CallManager. You specify which servers and which Cisco CallManagers belong to the same cluster and specify the publisher database location when you install and configure the Cisco CallManager software. Groups and clusters are not necessarily related to the physical locations of any of their members. See the “Clusters” section on page 2-1. A cluster is a set of Cisco CallManagers that share a common database.

If you specify a second standby Cisco CallManager for the group. Components of a Group A Cisco CallManager group is a prioritized list of up to three Cisco CallManagers. the primary Cisco CallManager in a group controls call processing for all the registered devices (such as phones and gateways) associated with a group. You can combine the groups and device pools in various ways to achieve the desired level of redundancy. For example.Chapter 3 Groups and Clusters Understanding Redundancy A group is a list of Cisco CallManagers that is assigned to one or more device pools to provide redundant call processing. You use Cisco CallManager Administration to define the groups. Cisco CallManager Administration Guide 3-2 OL-1047-01 . Each device belongs to one device pool. it takes control of the devices if both the primary and the first standby Cisco CallManagers fail. and to assign a Cisco CallManager group to each device pool. If the primary Cisco CallManager fails for any reason. You associate devices to a Cisco CallManager group by using device pools. The order that the Cisco CallManagers are listed in a group determines the failover order. Figure 3-1 shows a simple system with three redundant Cisco CallManagers controlling 800 devices. and each device pool is associated with one Cisco CallManager group. Under normal operation. and it may contain one or two standby Cisco CallManagers. the first standby Cisco CallManager takes control of the devices that were registered with the primary Cisco CallManager. specify which Cisco CallManagers belong to each group. Each group must contain a primary Cisco CallManager.

Combining Redundancy with Distributed Call Processing The configuration in Figure 3-1 provides call processing redundancy. CCM1. control of all 800 devices transfers to CCM2. you would want to distribute the devices in a way that prevents a single Cisco CallManager from becoming overloaded if one of the other Cisco CallManagers in the group fails.Chapter 3 Understanding Redundancy Groups and Clusters Figure 3-1 Example of a Cisco CallManager Group DP1 Device pool (400 devices) G1 Cisco CallManager Group CCM1 Primary CCM2 First Backup CCM3 Second Backup In Figure 3-1. If CCM2 also fails. Figure 3-2 shows one possible way to configure the Cisco CallManager groups and device pools to achieve both distributed call processing and redundancy for a system of three Cisco CallManagers and 800 devices. In most cases. Cisco CallManager group G1 is assigned to two device pools. then control of all 800 devices transfers to CCM3. as the primary Cisco CallManager in group G1. If CCM1 fails. DP1 and DP2. controls all 800 devices in DP1 and DP2 under normal operation. Cisco CallManager Administration Guide OL-1047-01 47070 DP2 Device pool (400 devices) 3-3 . but it does not distribute the call processing load very well among the three Cisco CallManagers in the example.

Chapter 3 Groups and Clusters Understanding Redundancy Figure 3-2 Example of Redundancy Combined with Distributed Call Processing G1 Cisco CallManager Group DP1 Device pool (100 devices) CCM1 Primary CCM2 First Backup CCM3 Second Backup G2 Cisco CallManager Group DP2 Device pool (300 devices) CCM1 Primary CCM3 First Backup CCM2 Second Backup G3 Cisco CallManager Group DP3 Device pool (100 devices) CCM2 Primary CCM1 First Backup CCM3 Second Backup G4 Default Cisco CallManager Group DP4 Device pool (300 devices) CCM2 Primary CCM3 First Backup CCM1 Second Backup Cisco CallManager Administration Guide 3-4 OL-1047-01 47071 .

Cisco CallManager Administration Guide OL-1047-01 3-5 . you might want to update these configurations to change the settings for some of the parameters such as auto-registration. select System > Cisco CallManager and update the configuration for the Cisco CallManagers in a cluster. For details. G1 and G2. For more information on distributed call processing. If CCM2 fails. Similarly. the 100 devices in device pool DP1 transfer to CCM2. and the 300 devices in DP2 transfer to CCM3. A cluster is a set of Cisco CallManagers that share the same database. Configuring Call Processing Redundancy This section describes the general steps for configuring Cisco CallManager groups to provide call processing redundancy and distributed call processing as illustrated by the example in Figure 3-2. When you install the Cisco CallManager software. all devices transfer to CCM3. the Cisco CallManager groups are configured and assigned to device pools so that Cisco CallManager CCM1 is the primary controller in two groups. If CCM1 fails. the cluster consists of Cisco CallManagers CCM1. see the “Understanding Distributed Call Processing” section on page 2-1. CCM2 is the primary controller of groups G3 and G4. Procedure Step 1 In Cisco CallManager Administration. refer to the installation instructions that shipped with your Cisco CallManager. In Figure 3-2. and CCM3. the database contains an initial configuration for each of the Cisco CallManagers in the cluster. and the 300 devices in DP4 transfer to CCM3. the 100 devices in DP3 transfer to CCM1. Before You Begin Install the Cisco Media Convergence Servers and Cisco CallManager software to form a cluster of Cisco CallManagers.Chapter 3 Understanding Redundancy Configuring Call Processing Redundancy In Figure 3-2. For details. However. If CCM1 and CCM2 both fail. CCM2. see the “Updating a Cisco CallManager” section on page 12-5.

Cisco CallManager Administration Guide 3-6 OL-1047-01 . select System > Device Pool to configure device pools for your system. and devices that auto-register with Cisco CallManager are normally assigned to this Default group. unless you specify a different default device pool through the Device Defaults (see the “Setting Device Defaults” section on page 15-1). DP2 is assigned to G2. In this example. page 2-1. b. device pools. and so forth. Step 4 In Cisco CallManager Administration. see the “Configuring Device Pools” section on page 17-1. The Default group is configured automatically when you install the Cisco CallManager software. For details. see: • Understanding Distributed Call Processing. you might want to update its configuration to set the parameters such as region and to assign this pool to the appropriate Cisco Call Manager group.Chapter 3 Configuring Call Processing Redundancy Understanding Redundancy Step 2 In Cisco CallManager Administration. and Cisco CallManagers among the groups is critical for maintaining the desired level of redundancy and load balancing in your system. select System > Cisco CallManager Group to configure Cisco CallManager groups for the cluster. The way you distribute devices. a. select the desired options under Device to configure the devices on your network and to assign them to the appropriate device pools. see the “Configuring Cisco CallManager Groups” section on page 13-1. restart the devices affected by those changes. However. For more information on distributed call processing. Step 5 Related Topics Cisco CallManager groups provide both call processing redundancy and distributed call processing. you might want to change the configuration of the Default group or specify one of the other groups as the default group for auto-registration. Step 3 In Cisco CallManager Administration. The Default device pool is configured automatically when you install Cisco CallManager. For details. device pool DP1 is assigned to group G1. Configure the other device pools and assign them to the appropriate Cisco CallManager groups. Cisco CallManager normally assigns the Default device pool to devices that auto-register with it. After making your configuration changes and saving them in the database. However.

Auto-registration is disabled by default to prevent unauthorized connections to your network. If all of the auto-registration directory numbers are consumed. Cisco CallManager Administration Guide OL-1047-01 4-1 .C H A P T E R 4 Understanding Auto-Registration Use auto-registration if you want Cisco CallManager to assign directory numbers automatically to new devices when you plug these devices into your network. Once a directory number is assigned to an auto-registered device. Caution Auto-registration is disabled by default. As new devices are connected to the network. page 4-7 When you enable auto-registration. Enabling auto-registration carries a security risk in that “rogue” phones can automatically register to the Cisco CallManager. no additional devices can auto-register with Cisco CallManager. page 4-2 Disabling Auto-Registration. you specify a range of directory numbers for Cisco CallManager to assign to new devices connected to your network. you can move the device to a new location and its directory number remains the same. Use the following procedures to enable or disable auto-registration and to reuse the auto-registration directory numbers: • • • Enabling Auto-Registration. Cisco CallManager assigns the next available directory number in the specified range. Auto-registration should only be enabled for brief periods when bulk phone adds are required. page 4-6 Reusing Auto-Registration Numbers.

you can update its configuration and assign it to a different device pool and a different Cisco CallManager (see the “Configuring Device Pools” section on page 17-1). Related Topics • • • Enabling Auto-Registration. Select System > Cisco CallManager. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. page 4-2 Disabling Auto-Registration.Chapter 4 Enabling Auto-Registration Understanding Auto-Registration Note New devices auto-register with the primary Cisco CallManager in the Auto-Registration Cisco CallManager Group (see the “Configuring Cisco CallManager Groups” section on page 13-1). From the list of Cisco CallManagers. page 4-7 Enabling Auto-Registration This section describes how to enable auto-registration for devices. Cisco CallManager Administration Guide 4-2 OL-1047-01 . page 4-6 Reusing Auto-Registration Numbers. After a device has auto-registered. select the Cisco CallManager where you want to enable auto-registration. That Cisco CallManager automatically assigns each auto-registered device to a default device pool based on the device type (see the “Setting Device Defaults” section on page 15-1).

If you set the starting and ending directory numbers to the same value. auto-registration is automatically enabled.Chapter 4 Understanding Auto-Registration Enabling Auto-Registration Step 4 Enter the following information in the section for Auto-registration Information. auto-registration is disabled. select None. If you specify a range of directory numbers in the Starting Directory Number and Ending Directory Number fields. Partition Select the partition to which auto-registered directory numbers belong. Field Name Starting Directory Number Description Enter the first directory number to use for auto-registration of devices. auto-registration is automatically enabled. Ending Directory Number Enter the last directory number to use for auto-registration of devices. auto-registration is disabled. If you set the starting and ending directory numbers to the same value. The partition field is reset when auto-registration is disabled. If you specify a range of directory numbers in the Starting Directory Number and Ending Directory Number fields. You must select a valid range for auto-registration before you can select a partition and external phone number mask. If you are not using partitions. Cisco CallManager Administration Guide OL-1047-01 4-3 .

Step 5 Click Update to save any changes in the database. • • Uncheck the auto-registration Disabled option to enable auto-registration for this Cisco CallManager. Enter the literal digits that you want to appear in the caller ID information. For example. Check the Auto-registration Disabled option to disable auto-registration for this Cisco CallManager. Cisco CallManager sets the starting and ending directory numbers to the same value. You can disable auto-registration by setting the Starting Directory Number and Ending Directory Number to the same value. The mask can contain up to 50 characters. If starting and ending directory numbers are currently specified when you disable auto-registration by checking this option. The partition and external phone mask information fields are also reset when auto-registration is disabled. you must configure the directory numbers manually whenever you add new devices to your network. Cisco CallManager Administration Guide 4-4 OL-1047-01 . and use Xs to represent the directory number of the auto-registered device. When Disabled on this Cisco CallManager auto-registration is disabled. then that literal number is the caller ID displayed for an external call from any auto-registered device. Auto-registration is disabled by default to prevent Auto-registration unauthorized connections to the network. an external call from extension 1234 displays a caller ID number of 9728131234 if the Use External Phone Number Mask option is checked on the route pattern used to make the external call.Chapter 4 Enabling Auto-Registration Understanding Auto-Registration Field Name External Phone Number Mask Description Specify the mask used to format caller ID information for external (outbound) calls made from the auto-registered devices. if you specify a mask of 972813XXXX. If you specify a mask of all literal digits such as 9728135000 to represent a main attendant number.

Select System > Cisco CallManager Group. From the list of device pools. Click Update to save the device pool changes in the database. select the calling search space to assign to the devices in this device pool that auto-register with Cisco CallManager. There can be only one primary Cisco CallManager for auto-registration. the name of this group is Default. but you can designate other Cisco Call Managers as backups for purposes of auto-registration. See the “Understanding Redundancy” section on page 3-1. From the list of Cisco CallManager groups. From the drop-down list box for Cisco CallManager Group. From the drop-down list box for Calling Search Space for Auto-Registration.) This is the default Cisco CallManager group for devices that auto-register.Chapter 4 Understanding Auto-Registration Enabling Auto-Registration Step 6 Repeat Steps 3 through 5 for each Cisco CallManager where you want to enable auto-registration. Repeat Step 11 through Step 14 for each device pool listed in the Device Defaults. select the Cisco CallManager group you configured for auto-registration in Step 8. If you made any changes to the group configuration. page 4-1 Disabling Auto-Registration. The calling search space specifies the route partitions used by the devices in the pool. Cisco CallManager assigns each auto-registered device to a default device pool based on the device type. Make sure the Selected list for this group contains the Cisco CallManagers you configured for auto-registration in Step 3. This step assigns the default device pool to the default Cisco CallManager group for auto-registration. (In most systems. page 4-7 Cisco CallManager Administration Guide OL-1047-01 4-5 . click Update to save the changes in the database. Select System > Device Pool. Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15 Related Topics • • • Understanding Auto-Registration. select the group that is enabled for auto-registration. page 4-6 Reusing Auto-Registration Numbers. select one of the default device pools assigned in the Device Defaults (see the “Setting Device Defaults” section on page 15-1).

From the Cisco CallManager list. select the Cisco CallManager where you want to disable auto-registration. auto-registration is disabled). Related Topics • • • Understanding Auto-Registration. Select System > Cisco CallManager. page 4-2 Reusing Auto-Registration Numbers. page 4-7 Cisco CallManager Administration Guide 4-6 OL-1047-01 .Chapter 4 Disabling Auto-Registration Understanding Auto-Registration Disabling Auto-Registration This section describes how to disable auto-registration for devices. Repeat Steps 3 through 5 for each Cisco CallManager where you want to disable auto-registration. Note You can also disable auto-registration by setting the Starting Directory Number and Ending Directory Number to the same value. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Click the Auto-registration Disabled option to disable auto-registration for this Cisco CallManager (when this box is checked. page 4-1 Enabling Auto-Registration. Step 5 Step 6 Click Update to save the changes in the database.

When a device attempts to auto-register. Cisco CallManager Administration Guide OL-1047-01 4-7 . Select the Cisco CallManager where you want to reset auto-registration. or if you delete that device from the database. Cisco CallManager assigns the next available (unused) auto-registration directory number to that device. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Select System > Cisco CallManager. Caution Step 6 Step 7 Step 8 New devices cannot auto-register while auto-registration is disabled. Write down the current settings for Starting Directory Number and Ending Directory Number. It begins the search with the next directory number in sequence after the last one assigned. Set the Starting Directory Number and Ending Directory Number to their previous values (or to new values if desired). Click Update. Click Update. If you manually change the directory number of an auto-registered device.Chapter 4 Understanding Auto-Registration Reusing Auto-Registration Numbers Reusing Auto-Registration Numbers When you connect a new device to the network. You can use the following procedure to reset the range of auto-registration directory numbers and force Cisco CallManager to search from the starting number in the range. If it reaches the ending directory number in the range. Cisco CallManager searches the range of auto-registration numbers you specified and tries to find the next available directory number to assign to the device. Cisco CallManager continues to search from the starting directory number in the range. Cisco CallManager can reuse the auto-registration directory number of that device. Click Auto-registration Disabled on this Cisco CallManager.

page 4-6 Cisco CallManager Administration Guide 4-8 OL-1047-01 . page 4-1 Enabling Auto-Registration. page 4-2 Disabling Auto-Registration.Chapter 4 Reusing Auto-Registration Numbers Understanding Auto-Registration Related Topics • • • Understanding Auto-Registration.

Call admission control regulates voice quality by limiting the number of calls that can be active on a particular link at the same time. page 5-2 Gatekeepers. For example.C H A P T E R 5 Understanding Call Admission Control Use call admission control to maintain a desired level of voice quality over a WAN link. Call admission control does not guarantee a particular level of audio quality on the link. There are two types of call admission control that you can use with Cisco CallManager: • • Locations. page 5-3 Cisco CallManager Administration Guide OL-1047-01 5-1 . you can use call admission control to regulate the voice quality on a T1 line connecting your main campus and a remote site. but it does allow you to regulate the amount of bandwidth consumed by active calls on the link. Voice quality can begin to degrade when there are too many active calls on a link and the amount of bandwidth is oversubscribed.

Figure 5-1 Call Admission Control Using Locations in a Centralized System Hub location Cisco CallManager IP WAN link IP WAN link Remote location A Remote location B Cisco CallManager Administration Guide 5-2 OL-1047-01 38538 . provides call admission control for centralized call processing systems. refer to the “Configuring Locations” section on page 19-1 and to the Cisco IP Telephony Network Design Guide. For more information. A centralized system uses a single Cisco CallManager to control all the locations. Figure 5-1 illustrates call admission control using locations. available in Cisco CallManager.Chapter 5 Locations Understanding Call Admission Control Locations The Locations feature.

Figure 5-2 Call Admission Control Using H. Refer to the Cisco IP Telephony Network Design Guide for more information about deployment of gatekeeper-based call admission control. also known as a Multimedia Conference Manager (MCM).323 Gatekeeper Technology in a Distributed System Main campus Cisco CallManager (or cluster) Gatekeeper IP WAN link Cisco CallManager (or cluster) IP WAN link Cisco CallManager (or cluster) Remote site A Remote site B Cisco CallManager Administration Guide OL-1047-01 38539 5-3 . Figure 5-2 illustrates call admission control using gatekeeper technology.Chapter 5 Understanding Call Admission Control Gatekeepers Gatekeepers An H. provides call admission control in a distributed system with a separate Cisco CallManager or Cisco CallManager cluster at each site.323 gatekeeper. Only one gatekeeper can be registered per Cisco CallManager cluster.

Chapter 5 Gatekeepers Understanding Call Admission Control Cisco CallManager Administration Guide 5-4 OL-1047-01 .

and route groups provide flexibility in network design. page 6-1 Understanding Route Pattern Wildcards and Special Characters. (Use route patterns to include and exclude digit patterns.) Route lists control the selection order of the route groups. page 6-11 Understanding Discard Digits Instructions. route lists.C H A P T E R 6 Understanding Route Plans The Route Plan drop-down list on the menu bar allows you to configure Cisco CallManager route plans using route patterns. page 6-7 Understanding Closest-Match Routing. route lists. This section contains descriptions of the following route plan concepts: • • • • • Route Plan Overview. page 6-12 Understanding the External Route Plan Wizard. route filters. route filters. page 6-25 Route Plan Overview The Cisco CallManager uses the route plan to route both internal calls and external (Public Switched Telephone Network [PSTN]) calls. and route groups. Use route filters primarily to include digit patterns. Route groups set the selection order of the gateway devices. Route patterns. Cisco CallManager Administration Guide OL-1047-01 6-1 . Route patterns work in conjunction with route filters to direct calls to specific devices and to include or exclude specific digit patterns.

or to route lists and route groups. at least one route group must be configured. a private branch exchange (PBX). and SUBSCRIBER (1234) tags. or a gateway on another Cisco CallManager system. A tag applies a name to a portion of the dialed digits. the North American Numbering Plan (NANP) number 972-555-1234 contains the LOCAL-AREA-CODE (972). One or more route lists can point to one or more route groups.323-compliant gateways also use route patterns. When you assign a directory number to a Cisco IP Phone. For example. you are assigning it a route pattern (the directory number is the route pattern). Cisco CallManager Administration Guide 6-2 OL-1047-01 . Route lists determine the order of preference for route group usage. Route groups determine the order of preference for gateway and port usage. you must reset the gateway for the new or updated information to be recognized. in Figure 6-1 Cisco Access Digital Gateway 1 is designated as the first-choice for routing outgoing calls to the PSTN. Cisco MGCP gateways. Bermuda. For example. Route filters permit or restrict access to routing patterns. The adjacent system can be a central office (CO). Route patterns represent all valid digit strings. A route pattern can be assigned directly to a Cisco Access Gateway. Route groups allow overflows from busy or failed devices to alternate devices. Note After adding or changing route pattern information. Canada. Cisco Access Analog Trunk Gateways. If a route list is configured.Chapter 6 Route Plan Overview Understanding Route Plans Route patterns can be assigned to gateways. or it can be assigned to a route list for more flexibility. OFFICE-CODE (555). Note The NANP is the numbering plan for the PSTN in the United States and its territories. and H. Cisco gateways can route ranges of numbers with complex restrictions and manipulate directory numbers before the Cisco CallManager passes them on to an adjacent system. and many Caribbean nations. Cisco Access Digital Trunk Gateways. Tags are the core component of route filters. It includes any number that can be dialed and is recognized in North America.

and that route list is associated with a single route group. If all ports on the first-choice gateway are busy or out of service. In this example. it cannot place calls to the PSTN or to a PBX. To assign a route pattern to an individual port on a gateway. Cisco CallManager Administration Guide OL-1047-01 6-3 .Chapter 6 Understanding Route Plans Route Plan Overview Tips If a gateway does not have a route pattern. the call is routed to the second-choice gateway. Figure 6-1 shows the effects of using route patterns with Cisco Access Digital Gateways. you must assign a route list and a route group to that port. the route pattern is assigned to a route list. The route group supports a list of devices that are selected based on availability.

perform digit manipulation and route to the route list. Second-choice First-choice Cisco Access Digital Gateway 1 Cisco Access Digital Gateway 2 Route to PSTN.Chapter 6 Route Plan Overview Understanding Route Plans Figure 6-1 Route Plan Summary Diagram for Cisco Access Digital Gateways User dials number Route pattern If the route pattern matches. Cisco CallManager Administration Guide 6-4 OL-1047-01 32370 PSTN . Route list Associate the route list with a single route group Route group Route to Cisco Access Digital Gateway devices in order of preference.

if ports 1 through 8 on the first-choice gateway are busy or out of service.Chapter 6 Understanding Route Plans Route Plan Overview Figure 6-2 shows the effects of using route patterns with Cisco Access Analog Gateways. If all routes in route group 1 are unavailable. If no ports on any gateway in either route group are available. the call is routed to an all trunks busy tone. In this example. and that route list is associated with two route groups. if ports 5 through 8 on the first-choice gateway are busy or out of service. For route group 1. Each route group supports a list of devices that are selected based on availability. calls are routed to ports 1 through 8 on the second-choice gateway. Route group 2 is associated with ports 5 through 8 on gateway 2 and all ports on gateway 3. the route pattern is assigned to a route list. calls are routed to route group 2. calls are routed to ports 1 through 4 on the second-choice gateway. Route group 1 is also associated with ports 1 through 4 on gateway 2. which route all calls to interexchange carrier 1 (IXC 1). Cisco CallManager Administration Guide OL-1047-01 6-5 . For route group 2. Route group 1 is associated with ports 1 through 8 on gateway 1.

IXC 1 IXC 2 IXC 3 Related Procedures • • • • Adding a Route Filter. perform digit manipulation and route to the route list. Second-choice gateway 3 ports 1 to 8 Route group 1 Route Group 2 First-choice gateway 1 ports 1 to 8 Second-choice gateway 2 ports 1 to 4 First-choice gateway 2 ports 5 to 8 Cisco Access Analog Gateway 1 Cisco Access Analog Gateway 2 Cisco Access Analog Gateway 2 Route to an IXC. Second choice Route to Cisco Access Analog Gateway devices based on gateway and port number. page 23-5 Adding a Route Group. page 26-1 Adding a Route List. Route list First choice Associate the route list with a single route group. page 25-6 Cisco CallManager Administration Guide 6-6 32371 OL-1047-01 .Chapter 6 Route Plan Overview Understanding Route Plans Figure 6-2 Route Plan Summary Diagram for Cisco Access Analog Gateways User dials number Route pattern If the route pattern matches. page 24-2 Adding a Route Pattern.

• • • • • 0 1411 19725551234 101028819725551234 01133123456789 X The X wildcard matches any single digit in the range 0 through 9. Only one @ wildcard is allowed in each route pattern. ! The exclamation point (!) The route pattern 91! routes or wildcard matches one or more blocks all numbers in the range digits in the range 0 through 9. Table 6-1 Wildcards and Special Characters Character @ Description The at symbol (@) wildcard matches all NANP numbers. The route pattern 9XXX routes or blocks all numbers in the range 9000 through 9999.Chapter 6 Understanding Route Plans Understanding Route Pattern Wildcards and Special Characters Understanding Route Pattern Wildcards and Special Characters Route pattern wildcards and special characters allow a single route pattern to match a range of numbers (addresses). These wildcards and special characters are also used to build instructions that enable the Cisco CallManager to manipulate a number before sending it to an adjacent system. 910 through 91999999999999999999999. The following route patterns are examples of NANP numbers encompassed by the @ wildcard. Cisco CallManager Administration Guide OL-1047-01 6-7 . Examples The route pattern 9. Table 6-1 describes the wildcards and special characters supported by Cisco CallManager.@ routes or blocks all numbers recognized by the NANP.

- ^ Cisco CallManager Administration Guide 6-8 OL-1047-01 . Only one ^ character is allowed in each route pattern. to negate a range of values. The hyphen (-) character is The route pattern 813510[0-5] used. The route pattern 91X+ routes or blocks all numbers in the range 9100 through 91999999999999999999999. routes or blocks all numbers in to denote a range of values. all numbers in the range 8135100 through 8135105. the range 8135100 through 8135105.Chapter 6 Understanding Route Pattern Wildcards and Special Characters Understanding Route Plans Table 6-1 Wildcards and Special Characters (continued) Character ? Description The question mark (?) wildcard matches zero or more occurrences of the preceding digit or wildcard value. with the square brackets. The circumflex (^) character is used. + [] The square bracket ([ ]) The route pattern characters are used to enclose a 813510[012345] routes or blocks range of values. It must be the first first character following the opening bracket ([). The route pattern 813510[^1-5] routes or blocks all numbers in the range 8135106 through 8135109. Examples The route pattern 91X? routes or blocks all numbers in the range 91 through 91999999999999999999999. with the square brackets. The plus sign (+) wildcard matches one or more occurrences of the preceding digit or wildcard value.

) character is used as a delimiter to separate the Cisco CallManager access code from the directory number. The route pattern *411 can be configured to provide access to the internal operator for directory assistance. Only one . # The octothorpe (#) character is The route pattern 901181910555# generally used to identify the routes or blocks an international number dialed from within the end of the dialing sequence.@ identifies the initial 9 as the Cisco CallManager access code in an NANP call. * The asterisk (*) character is available as an extra digit for special dialed numbers. digit in the sequence. This special character can be used. Description The dot (. character is allowed in each route pattern. NANP. Table 6-2 lists Cisco CallManager Administration fields that require route patterns and shows the valid entries for each field. with the discard digits instructions. The # character after the The # character must be the last last 5 identifies this as the last character in the pattern. Examples The route pattern 9. Table 6-2 Field Entries Field Call Park Number/Range Calling Party Transform Mask Called Party Transform Mask Valid entries [^0123456789-]X*# 0123456789X*# 0123456789X*# Cisco CallManager Administration Guide OL-1047-01 6-9 . to strip off the Cisco CallManager access code before sending the number to an adjacent system.Chapter 6 Understanding Route Plans Understanding Route Pattern Wildcards and Special Characters Table 6-1 Wildcards and Special Characters (continued) Character .

Chapter 6 Understanding Route Pattern Wildcards and Special Characters Understanding Route Plans Table 6-2 Field Entries (continued) Field Caller ID DN (Gateways) Directory Number External Phone Number Mask Forward All Forward Busy Forward No Answer Meet-Me Conference number Prefix Digits Prefix DN (Gateways) Route Filter tag values Route Pattern Translation Pattern Valid entries 0123456789X*# [^0123456789-]+?!X*#+ 0123456789X*# 0123456789*# 0123456789*# 0123456789*# [^0123456789-]+?!X*#+ 0123456789*# 0123456789*# [^0123456789-]X*# [^0123456789-]+?!X*#+.@ Directory Number (Call Pickup Group) 0 1 2 3 4 5 6 7 8 9 Cisco CallManager Administration Guide 6-10 OL-1047-01 .@ [^0123456789-]+?!X*#+.

the Cisco CallManager arbitrarily chooses one. The following paragraphs explain why such exact matches are an unusual occurrence. Using the preceding example. The route pattern 89XX matches 8912 plus 99 other addresses. Cisco CallManager Administration Guide OL-1047-01 6-11 . Even though both of these route patterns seem to equally match the address. In this example.XXXXXXX. Since the number 2578912 more closely matches [2-9]XXXXXX than it does XXXXXXX. and the route pattern 8XXX matches 8912 plus 999 other addresses. For instance. If the user dials 8913. and 8XXX.Chapter 6 Understanding Route Plans Understanding Closest-Match Routing Understanding Closest-Match Routing Closest-match routing is the process of routing a call using the route pattern that most closely matches the dialed number.@ route pattern provides the closest match for routing.@ route pattern actually provides the closest match. the call routes differently. the number 8912 matches all of the following route patterns: 8912. the 9. When the Cisco CallManager encounters a a dialed number that matches multiple route patterns. 89XX. Using the @ wildcard character in a route pattern requires additional consideration. the 9. the Cisco CallManager delivers the call to the device assigned the routing pattern 89XX. The number 92578912 matches both of the following route patterns: 9. and one of those route patterns is [2-9]XXXXXX. it uses closest-match routing to determine which route pattern matches the number most closely and directs the call using that route pattern. this address matches only the routing patterns 89XX and 8XXX. Since 89XX matches a narrower range of addresses than 8XXX. The @ wildcard character encompasses many different route patterns. the route pattern 8912 matches exactly one address.) If two configured route patterns match exactly the same number of addresses in a partition. It is possible to configure several route patterns that match a single number. When two configured route patterns match exactly the same number of addresses in different partitions.@ and 9. (Cisco CallManager chooses the route pattern from the partition that appears first in the calling search space. Cisco CallManager chooses the route pattern based on order in which the partitions are listed in the calling search space.

@ Dialed digit string: 919728135000 or 99728135000 After applying DDI: 98135000 long distance direct dialing code long distance operator assisted dialing code IXC access code area code local area code 11/10D->7D This DDI removes: • • • • • This DDI creates a 7-digit local number from an 11.@ Dialed digit string: 910102889728135000 After applying DDI: 99728135000 IXC access code 10-10-Dialing Trailing-# This DDI removes: • • Route pattern: 9. Table 6-3 lists DDIs and describes the effects of applying each DDI to a dialed number. but that access code is not expected by the PSTN switch.Chapter 6 Understanding Discard Digits Instructions Understanding Route Plans Understanding Discard Digits Instructions A discard digits instruction (DDI) removes a portion of the dialed digit string before passing the number on to the adjacent system.@ Dialed digit string: 9101028801181910555# IXC access code end-of-dialing character After applying DDI: for international calls 901181910555 Route pattern: 9. Portions of the digit string must be removed.or 10-digit dialed number. for example. Table 6-3 Discard Digits Instructions DDI 10-10-Dialing Effect This DDI removes: • Example Route pattern: 9. when an external access code is needed to route the call to the PSTN. Cisco CallManager Administration Guide 6-12 OL-1047-01 .

Chapter 6 Understanding Route Plans Understanding Discard Digits Instructions Table 6-3 Discard Digits Instructions (continued) DDI Effect • • • • • • Example Route pattern: 9.or 10-digit dialed number 11D->10D This DDI removes: • • • Route pattern: 9.@ Dialed digit string: 919728135000 After applying DDI: 99728135000 Route pattern: 9.@ Dialed digit string: 919728135000 or 99728135000 After applying DDI: 98135000 11/10D->7D Trailing-# This DDI removes: long distance direct dialing code long distance operator assisted dialing code IXC access code area code local area code end-of-dialing character for international calls This DDI creates a 7-digit local number from an 11.@ Dialed digit string: 919728135000 After applying DDI: 99728135000 long distance direct dialing code long distance operator assisted dialing code IXC access code long distance direct dialing code long distance operator assisted dialing code end-of-dialing character for international calls IXC access code 11D->10D Trailing-# This DDI removes: • • • • Cisco CallManager Administration Guide OL-1047-01 6-13 .

@ Intl TollBypass Trailing-# This DDI removes: • international access code Dialed digit string: 901181910555# • international direct After applying DDI: dialing code 9910555 • country code • • • IXC access code international operator assisted dialing code end-of-dialing character Dialed digit string: 919728135000 After applying DDI: 919728135000 NoDigits This DDI removes no digits. Route pattern: 9.Chapter 6 Understanding Discard Digits Instructions Understanding Route Plans Table 6-3 Discard Digits Instructions (continued) DDI Intl TollBypass Effect This DDI removes: • Example Route pattern: 9.@ end-of-dialing character Dialed digit string: 901181910555# for international calls After applying DDI: 901181910555 Cisco CallManager Administration Guide 6-14 OL-1047-01 .@ international access code Dialed digit string: 901181910555 • international direct After applying DDI: dialing code 9910555 • country code • • IXC access code international operator assisted dialing code Route pattern: 9.@ Trailing-# This DDI removes: • Route pattern: 9.

9@ prior to the NANP portion of Dialed digit string: the route pattern.Chapter 6 Understanding Route Plans Understanding Discard Digits Instructions Table 6-3 Discard Digits Instructions (continued) DDI PreAt Effect Example This DDI removes all digits Route pattern: 8.9@ prior to the NANP portion of Dialed digit string: the route pattern. including: 899728135000 • Cisco CallManager After applying DDI: external access code 9728135000 • PBX external access code This DDI removes all digits Route pattern: 8.9@ prior to the NANP portion of Dialed digit string: the route pattern. including: 8910102889728135000 • Cisco CallManager After applying DDI: external access code 9728135000 • • PBX external access code IXC access code Cisco CallManager Administration Guide OL-1047-01 6-15 . including: 8901181910555# • Cisco CallManager After applying DDI: external access code 01181910555 • PBX external access code • PreAt Trailing-# end-of-dialing character for international calls PreAt 10-10-Dialing This DDI removes all digits Route pattern: 8.

Chapter 6 Understanding Discard Digits Instructions Understanding Route Plans Table 6-3 Discard Digits Instructions (continued) DDI PreAt 10-10-Dialing Trailing-# Effect Example This DDI removes all digits Route pattern: 8.9@ prior to the NANP portion of Dialed digit string: the route pattern. including: 89101028801181910555# • Cisco CallManager After applying DDI: external access code 01181910555 • PBX external access code • • IXC access code end-of-dialing character for international calls PreAt 11/10D->7D This DDI removes all digits Route pattern: 8.9@ prior to the NANP portion of Dialed digit string: the route pattern.or 10-digit dialed number. Cisco CallManager Administration Guide 6-16 OL-1047-01 . including: 8919728135000 or 899728135000 • Cisco CallManager external access code After applying DDI: • • • • • • PBX external access code long distance direct dialing code long distance operator assisted dialing code IXC access code area code local area code 8135000 This DDI creates a 7-digit local number from an 11.

Chapter 6 Understanding Route Plans Understanding Discard Digits Instructions Table 6-3 Discard Digits Instructions (continued) DDI PreAt 11/10D->7D Trailing-# Effect Example This DDI removes all digits Route pattern: 8. Cisco CallManager Administration Guide OL-1047-01 6-17 .9@ prior to the NANP portion of Dialed digit string: the route pattern.or 10-digit dialed number. including: 8919728135000 or 899728135000 • Cisco CallManager external access code After applying DDI: 8135000 • PBX external access code • • • • • • long distance direct dialing code long distance operator assisted dialing code IXC access code area code local area code end-of-dialing character for international calls This DDI creates a 7-digit local number from an 11.

9@ prior to the NANP portion of Dialed digit string: the route pattern. including: 8919728135000 • Cisco CallManager After applying DDI: external access code 9728135000 • PBX external access code • • • long distance direct dialing code long distance operator assisted dialing code IXC access code PreAt 11D->10D Trailing-# This DDI removes all digits Route pattern: 8.Chapter 6 Understanding Discard Digits Instructions Understanding Route Plans Table 6-3 Discard Digits Instructions (continued) DDI PreAt 11D->10D Effect Example This DDI removes all digits Route pattern: 8.9@ prior to the NANP portion of Dialed digit string: the route pattern. including: 8919728135000 • Cisco CallManager After applying DDI: external access code 9728135000 • PBX external access code • • • • long distance direct dialing code long distance operator assisted dialing code IXC access code end-of-dialing character for international calls Cisco CallManager Administration Guide 6-18 OL-1047-01 .

including: 8901181910555 • Cisco CallManager After applying DDI: external access code 910555 • PBX external access code • • • • • international access code international direct dialing code country code IXC access code international operator assisted dialing code PreAt Intl TollBypass This DDI removes all digits Route pattern: 8.9@ Trailing-# prior to the NANP portion of Dialed digit string: the route pattern. including: 8901181910555# • Cisco CallManager After applying DDI: external access code 910555 • • • • • • • PBX external access code international access code international direct dialing code country code IXC access code international operator assisted dialing code end-of-dialing character Cisco CallManager Administration Guide OL-1047-01 6-19 .Chapter 6 Understanding Route Plans Understanding Discard Digits Instructions Table 6-3 Discard Digits Instructions (continued) DDI Effect Example PreAt Intl TollBypass This DDI removes all digits Route pattern: 8.9@ prior to the NANP portion of Dialed digit string: the route pattern.

9@ Dialed digit string: 89101028801181910555# Cisco CallManager external access code IXC access code PreDot 10-10-Dialing This DDI removes: • • PreDot 10-10-Dialing This DDI removes: Trailing-# • Cisco CallManager external access code • After applying DDI: 901181910555 • end-of-dialing character for international calls IXC access code Cisco CallManager Administration Guide 6-20 OL-1047-01 .9@ Dialed digit string: 899728135000 After applying DDI: 99728135000 Cisco CallManager external access code PreDot Trailing-# This DDI removes: • • Route pattern: 8.9@ Dialed digit string: 8901181910555# Cisco CallManager external access code end-of-dialing character After applying DDI: 901181910555 for international calls Route pattern: 8.Chapter 6 Understanding Discard Digits Instructions Understanding Route Plans Table 6-3 Discard Digits Instructions (continued) DDI PreDot Effect This DDI removes: • Example Route pattern: 8.9@ Dialed digit string: 8910102889728135000 After applying DDI: 99728135000 Route pattern: 8.

Cisco CallManager Administration Guide OL-1047-01 6-21 .9@ Dialed digit string: 8919728135000 or 899728135000 After applying DDI: 98135000 Cisco CallManager external access code long distance direct dialing code long distance operator assisted dialing code IXC access code area code local area code This DDI creates a 7-digit local number from an 11. PreDot 11/10D->7D Trailing-# This DDI removes: • • • • • • • Route pattern: 8.Chapter 6 Understanding Route Plans Understanding Discard Digits Instructions Table 6-3 Discard Digits Instructions (continued) DDI PreDot 11/10D->7D Effect This DDI removes: • • • • • • Example Route pattern: 8.9@ Dialed digit string: 8919728135000 or 899728135000 After applying DDI: 98135000 Cisco CallManager external access code long distance direct dialing code long distance operator assisted dialing code IXC access code area code local area code end-of-dialing character for international calls This DDI creates a 7-digit local number from an 11.or 10-digit dialed number.or 10-digit dialed number.

9@ Dialed digit string: 8919728135000 After applying DDI: 99728135000 Cisco CallManager external access code long distance direct dialing code long distance operator assisted dialing code IXC access code end-of-dialing character for international calls Cisco CallManager Administration Guide 6-22 OL-1047-01 .Chapter 6 Understanding Discard Digits Instructions Understanding Route Plans Table 6-3 Discard Digits Instructions (continued) DDI PreDot 11D->10D Effect This DDI removes: • • • • Example Route pattern: 8.9@ Dialed digit string: 8919728135000 After applying DDI: 99728135000 Cisco CallManager external access code long distance direct dialing code long distance operator assisted dialing code IXC access code PreDot 11D->10D Trailing-# This DDI removes: • • • • • Route pattern: 8.

Chapter 6 Understanding Route Plans Understanding Discard Digits Instructions Table 6-3 Discard Digits Instructions (continued) DDI Effect • • Example Route pattern: 8.9@ Dialed digit string: 8901181910555# PreDot Intl TollBypass This DDI removes: Trailing-# • Cisco CallManager external access code • international access code After applying DDI: 9910555 • international direct dialing code • • • • country code IXC access code international operator assisted dialing code end-of-dialing character Cisco CallManager Administration Guide OL-1047-01 6-23 .9@ Dialed digit string: 8901181910555 PreDot Intl TollBypass This DDI removes: Cisco CallManager external access code international access code After applying DDI: 9910555 • international direct dialing code • • • country code IXC access code international operator assisted dialing code Route pattern: 8.

the Cisco CallManager directs any calls to 8912 to the assigned device. Resetting the gateway may result in a dropped call.Chapter 6 Understanding Route Patterns Understanding Route Plans Understanding Route Patterns Cisco CallManager uses route patterns to route or block both internal and external calls. the Discard Digits field can specify any of the PreAt discard digits instructions (DDIs). Related Topics The following list contains additional information related to this section: • • • Route Plan Overview. When @ is used in a routing pattern. A directory number is a type of specific route pattern that is applied to a Cisco IP Phone. The simplest route pattern is just a set of one or more digits. the octothorpe (#) is automatically recognized as an end-of-dialing character for international calls. When assigned to a Cisco Access gateway or a route list. page 6-11 Cisco CallManager Administration Guide 6-24 OL-1047-01 . or it doesn’t belong to a route group. For example. If called party transformations are configured. Gateways can route ranges of numbers and manipulate directory numbers before the Cisco CallManager passes them onto an adjacent system such as a central office (CO) or private branch exchange (PBX). page 6-7 Understanding Closest-Match Routing. Tips You must reset gateways in order for new or updated routing information to be recognized. it cannot route/block any calls. page 6-1 Understanding Route Pattern Wildcards and Special Characters. you must include the # in the routing pattern to be able to use the # character to signal the end-of-dialing. the number 8912 is a route pattern. Considerations for Using Route Patterns • • If the route pattern contains an at symbol (@). Caution If a gateway has no route pattern associated with it. the Cisco CallManager manipulates the dialed address before passing the call to the route list or gateway. For routing patterns that don't use @. Gateways and Cisco IP Phones can also use more complex route patterns that can contain wildcards.

page 26-4 Copying a Route Pattern. partitioned route plan for the North American Numbering Plan (NANP) area using information provided by the administrator through a series of prompts. page 6-26 Generated Route Groups. page 6-27 Generated Route Lists. page 26-6 Understanding the External Route Plan Wizard The external route plan wizard generates a single tenant. page 6-29 Cisco CallManager Administration Guide OL-1047-01 6-25 . The route plan generated by the external route plan wizard includes the following elements: • • • • • • • • route filters route groups route lists route patterns partitions calling search spaces calling party digit translations and transformations access code manipulation The following topics describe the basic concepts used when you generate route plans with the external route plan wizard: • • • • Generated Route Filters. page 26-5 Deleting a Route Pattern. page 6-27 Generated Route Patterns. page 26-1 Updating a Route Pattern. multi-location.Chapter 6 Understanding Route Plans Understanding the External Route Plan Wizard • • • • Adding a Route Pattern.

@ where (SERVICE == 911) Local calls with metro Name: CiscoDallasLocalRF (7.@ where (AREA-CODE DOES_NOT_EXIST)(LOCAL-AREA-CODE DOES_NOT_EXIST) Name: CiscoTollByPassToDallasRF Content: 9. The examples shown in this table use specific route filter names and actual access and area codes for better readability. and appends the suffix RF to each route filter for easy identification.@ where (LOCAL-AREA-CODE == 972) OR (LOCAL-AREA-CODE == 214) Local calls with 7-digit dialing Name: CiscoDallasLocal7DCallRF Content: 9. Table 6-4 Route lists and associated route filters Route list type 911 calls Route filter name and content examples Name: CiscoDallas911RF Content: 9.@ where (AREA-CODE EXISTS) Name: CiscoDallasIntlRF Content: 9.@ where (AREA-CODE == 972) OR (AREA-CODE == 214) Long distance calls International calls Name: CiscoDallasLongDistanceRF Content: 9. The external route plan wizard associates each route list with a particular route filter.and 10-digit) dialing Content: 9.@ where (LOCAL-AREA-CODE == 972) OR (LOCAL-AREA-CODE == 214) Local calls with 10-digit Name: CiscoDallasLocal10DCallRF dialing Content: 9.Chapter 6 Understanding the External Route Plan Wizard Understanding Route Plans Generated Route Filters A generated route filter permits or restricts access through a route list using route patterns.@ where (INTERNATIONAL-ACCESS EXISTS) Toll bypass calls Cisco CallManager Administration Guide 6-26 OL-1047-01 . It names route filters using the TenantLocationCalltype convention. Table 6-4 shows the seven types of route lists that use route filters.

Chapter 6 Understanding Route Plans Understanding the External Route Plan Wizard Generated Route Groups A generated route group sets the order of preference for gateway and port usage. if there are three MGCP trunk gateways at the Cisco Dallas location. The external route plan wizard names route filters using the TenantLocationGatewaytypeNumber convention for easy identification.323 trunk MS: MGCP station MT: MGCP trunk The external route plan wizard identifies route groups associated with multiple gateways of the same type by attaching a number suffix to all route groups. The external route plan wizard creates between five and seven route lists for each location depending on Cisco CallManager Administration Guide OL-1047-01 6-27 . Note All gateways belonging to a location are shared resources for that location. If needed. The gateway type is abbreviated as shown in the following list: • • • • • AA: analog access DA: digital access HT: H. It does not support using partial resources for generated external route plans. The only order imposed is that route groups associated with the local gateways are listed before the route groups associated with remote gateways. If a route list includes more than one route group and more than one gateway (with one gateway for each route group). CiscoDallasMT2. For example. Generated Route Lists A generated route list sets the order of preference for route group usage and defines the route filters applied to those route groups. the external route plan wizard names the associated route groups CiscoDallasMT1. and CiscoDallasMT3. the order in which the external route plan wizard lists the route groups is arbitrary. change the order manually after the route plan is generated. The wizard uses all ports on the gateways. The external route plan wizard assigns one gateway to each generated route group.

Chapter 6 Understanding the External Route Plan Wizard Understanding Route Plans the types of local dialing choices available. Cisco CallManager Administration Guide 6-28 OL-1047-01 . you cannot also choose 7-digit or metro dialing route lists. The external route plan wizard names route lists using the TenantLocationCalltype convention. the total number of route lists depends on the local dialing scheme and the number of locations served by the route plan. The example shown in this table use specific route list names for better readability. Table 6-5 Route list types Route list type 911 calls Example route list name and usage Name: CiscoDallas911RL Use: This route list type is used for 911 emergency calls.or 10-digit dialing route lists. Therefore. and appends the suffix RL to each route list for easy identification. This route list type generates one route list for 10-digit dialing. If you chose to generate a route plan using a 10-digit dialing route list. Table 6-5 shows the eight types of route lists. Enterprise calls Name: CiscoDallasEnterpriseRL Use: This route list type is used for route plans that include Cisco CallManager to adjacent PBX calls. If the route plan does not include routing to an adjacent PBX. Local calls with 10-digit Name: CiscoDallasLocal10DCallRL dialing Use: This route list type is used for route plans that use 10-digit dialing. This route list type generates two route lists: one for 7-digit dialing and another for 10-digit dialing. you cannot also choose 7. Local calls with metro dialing Name: CiscoDallasLocalRL Use: This route list type is used for route plans that encompass both 7. the wizard does not generate this route list type.and 10-digit dialing areas. If you chose to generate a route plan using metro route lists.

Chapter 6 Understanding Route Plans Understanding the External Route Plan Wizard Table 6-5 Route list types Route list type Local calls with 7-digit dialing Example route list name and usage Name: CiscoDallasLocal7DCallRL Use: This route list type is used for route plans that use 7-digit dialing. This route list type generates one route list for 7-digit dialing. and prefix digits for the associated route list. and get routed out the local gateway as local calls. Cisco CallManager Administration Guide OL-1047-01 6-29 . digit discard instructions. International calls Name: CiscoDallasIntlRL Use: This route list type is used for international toll calls. and a partition with each route pattern. Name: CiscoTollByPassToDallasRL Use: This route list type is used for intracluster calls that originate from a remote location. If you chose to generate a route plan using a 7-digit dialing route list. The external route plan wizard only generates route patterns that require an access code prefix. a route filter.9@. The external route plan wizard associates a route list.@. The typical route pattern for routing a call to the PSTN has the prefix construction 9. called party transform mask. The typical route pattern for routing a call to the PBX has the prefix construction 9. The route pattern provides the appropriate calling party transform mask. you cannot also choose 10-digit or metro dialing route lists. Toll bypass calls Long distance calls Name: CiscoDallasLongDistanceRL Use: This route list type is used for long distance toll calls. Generated Route Patterns A generated route pattern directs calls to specific devices and either includes or excludes specific dialed-digit strings.

Chapter 6 Understanding the External Route Plan Wizard Understanding Route Plans The wizard bases route patterns for calls to an adjacent PBX on the access code and the range of directory numbers served by that PBX.1XXX for enterprise calls. if the access code used to direct calls to the adjacent PBX is 9 and the range of directory numbers served by that PBX is 1000 through 1999. For example. then the external route plan wizard generates the route pattern 9. Cisco CallManager Administration Guide 6-30 OL-1047-01 .

page 7-6 Adding Devices to Cisco CallManager. allowing you to configure voice to ensure proper call routing. Devices also require access to a TFTP server that contains device loads and device configuration name files (. Related Topics • • • Understanding DHCP and TFTP.C H A P T E R 7 Understanding Device Support Cisco CallManager controls Cisco voice devices (such as IP telephones and gateways).cnf files provide parameters for connecting to Cisco CallManager. page 7-10 Using DHCP and TFTP Cisco telephony devices require IP addresses that are assigned manually or by using Dynamic Host Configuration Protocol (DHCP). page 7-1 Understanding Device Loads. The .cnf file format). page 7-2 Accessing the TFTP Server. These sections provide general information about how Cisco CallManager interacts with voice devices in your network: • • • Using DHCP and TFTP. page 7-3 Understanding How Devices Identify the TFTP Server. page 7-4 Cisco CallManager Administration Guide OL-1047-01 7-1 .

you will need to configure the IP address through the Cisco IOS command-line interface on the Cisco Catalyst 6000.cnf file also contains phone button URL information.Chapter 7 Using DHCP and TFTP Understanding Device Support Understanding DHCP and TFTP DHCP automatically assigns IP addresses to devices whenever you plug them in. the phone accesses a . Requesting the Configuration File The TFTP server has configuration files (. Gateways and other devices do not have default configuration files and they do not auto-register.cnf file format) for devices that define parameters for connecting to Cisco CallManager. you need to disable DHCP on the phone and manually assign it an IP address. For example. • • • Cisco IP Phones are DHCP-enabled by default. you must assign it an IP address. If you are not using DHCP. If DHCP is not enabled on a device. If DHCP is not enabled. If a phone has been manually added into the Cisco CallManager database. Cisco CallManager Administration Guide 7-2 OL-1047-01 . All devices except phones must be manually added to the Cisco CallManager configuration database. For Cisco Catalyst 6000 8 Port Voice T1/E1 and Services Modules. the statically configured IP address is used. DHCP is always enabled for Cisco Analog Access and Cisco Digital Access gateways.cnf) from the TFTP server. you can connect multiple Cisco IP Phones anywhere on the IP network and DHCP automatically assigns IP addresses to them. If not. the phones access a default configuration file (sepdefault. the . you must configure the TFTP server locally on the device and then it will go to the TFTP server directly. If the device has a statically defined IP address. the DHCP server also directs the device to a TFTP Server.cnf file corresponding to its device name. Obtaining an IP Address If the device is using DHCP to obtain an IP address. in addition to assigning an IP address. the Network Management Processor (NMP) on the Catalyst 6000 may or may not have DHCP enabled. For Cisco IP Phone 7960 and 7940 models. If auto-registration is enabled in Cisco CallManager. the device queries the DHCP server to obtain one. Accessing the TFTP Server If DHCP is enabled on the phone.

Chapter 7 Understanding Device Support Using DHCP and TFTP Contacting Cisco CallManager The configuration file for a device specifies a list of Cisco CallManagers to contact. • Gateways and phones can query CiscoCM1. depending on the device type: • Gateways and phones can use DHCP custom option 150. it is informed of its device load ID. in priority order. • Gateways and phones can use DHCP option 066. Cisco CallManager identifies the device. If DHCP is enabled on the phone. Accessing the TFTP Server You can enable the IP phones and gateways to discover the TFTP server IP address in one or more of the following ways. If the device is a phone that was not manually added to the database and auto-registration is enabled in Cisco CallManager. the device next attempts to make a TCP connection to the highest priority Cisco CallManager on the list. Cisco CallManager Administration Guide OL-1047-01 7-3 . The TFTP server IP address is configured as the option value. When a device connects to a Cisco CallManager. • Phones can be configured with the IP address of the TFTP server. The Domain Name Server (DNS) must be able to resolve this name to the IP address of the TFTP server. Either the DNS Host Name or IP address of the TFTP server may be configured as the option value. If the device load ID differs from the load ID that is currently executing on the device. If the device was manually added to the database. the device requests the load associated with the new load ID from the TFTP server and resets itself. the phone attempts to auto-register itself in the Cisco CallManager database. an alternate TFTP server IP address can still be configured locally on the phone that will override the TFTP address obtained through DHCP. This is the method Cisco recommends. After obtaining the configuration file from the TFTP server.

The phone or gateway always tries to resolve the DNS name CiscoCM1. It is not necessary to name the TFTP server CiscoCM1. The TFTP server address is saved in non-volatile memory. the TFTP server can co-exist with a Cisco CallManager on the same server. The order of precedence is based on the method used to specify the TFTP server (method 1 in the following list has the highest precedence): 1. If one of the above methods was available at least once. The phone or Catalyst 6000 gateway uses a locally configured TFTP server address. For small systems. If this name is resolved.Chapter 7 Using DHCP and TFTP Understanding Device Support • • Gateways and phones also accept the DHCP Optional Server Name (sname) parameter. page 7-2 Understanding How Devices Identify the TFTP Server. The phone or gateway queries the DNS name CiscoCM1 and it is resolved. The phone or gateway can use the value of Next-Server in the boot processes (siaddr). but you must enter a DNS CName record to associate CiscoCM1 with the address or name of the TFTP server. then it overrides all information sent by the DHCP server. This address overrides any TFTP address sent by the DHCP server. 2. the address saved in memory will be used. but is not currently available. The TFTP server must subscribe to the Cisco CallManager Publisher (master database). Cisco CallManager Administration Guide 7-4 OL-1047-01 . page 7-4 Understanding How Devices Identify the TFTP Server Phones and gateways have an order of precedence that they use for selecting the address of the TFTP server if they receive conflicting or confusing information from the DHCP server. Related Topics • • Understanding DHCP and TFTP.

5. Option 066 is normally used to replace the sname (server name) field when option overloading occurs. However. then the device prefers the IP address over the name given by the 066 option. This name field can contain a DNS name or a dotted decimal IP address. this field is typically referred to as the address of the TFTP server. Related Topics • • Understanding DHCP and TFTP. Some servers allow access to the Next-Server parameter only when IP addresses are statically assigned. then order of preference is dependent on the order that they appear in the option list. This DHCP configuration parameter is the DNS name of a TFTP server. which is the name of the boot server. Use this option. page 7-3 Cisco CallManager Administration Guide OL-1047-01 7-5 . The phone or gateway uses the value of Next-Server in the boot processes. a dotted decimal IP address should not be used. If they are sent together.Chapter 7 Understanding Device Support Using DHCP and TFTP 3. This information is returned in the siaddr (server IP address) field of the DHCP header. The phone or gateway uses the Optional Server Name parameter. The phone or gateway uses the site-specific option 150. option 066 and option 150 are mutually exclusive. if available. When configuring BOOTP servers. 4. because some DHCP servers will place their own IP address in this field when it is not configured. This DHCP configuration parameter has traditionally been used as the address of the TFTP server. The device chooses the last item in the option list. To reiterate. The 066 option should not be used with the 150 option. page 7-2 Accessing the TFTP Server. 6. Currently only a DNS name can be configured in this parameter. The phone or gateway uses the 066 option. if both a dotted decimal IP address and a 150 option are sent. This option resolves the issue that some servers do not allow the Next-Server configuration parameter.

and conference bridge loads.. New loads you receive between releases must be copied to this location for the system to access them. Cisco CallManager Administration Guide 7-6 OL-1047-01 . Table 7-1 Device Load Descriptions Device Cisco IP Phone models 12S. D501A022. the latest loads are automatically provided. See Table 7-1 for a description of the loads for each device type... Cisco IP Phone 7960.. Loads are files that contain updated firmware for devices.. such as phones or gateways.. for example. A001P022. Not applicable.. for example. and 30VIP Description Loads for these devices begin with P002. 7910 Cisco Analog Access gateways Cisco Digital Access gateways Cisco Voice Gateway 200 Loads for these devices begin with P003. P002K202.. for example.. D003C202. you can also receive a load between releases that can contain patches or other information important to the devices that use loads.Cisco\TFTPPath subdirectory as *.... Loads for these devices begin with A001.Chapter 7 Understanding Device Loads Understanding Device Support Understanding Device Loads There are four types of loads: phone loads. the latest loads are stored in this location.. Loads are stored in the .bin files.bin. However. for example... P001K202. MTP loads. for example. 12SP. 12SP+. P003AM30.. Cisco IP Phone model 30SP+ Loads for these devices begin with P001. During installation or upgrade. During installation or upgrade. gateway loads. for example.. 7940. Loads for these devices begin with D003.

Related Topics • • • Updating a Load on a Cisco IP Phone. page 7-8 Updating the Load on a Cisco Gateway.Chapter 7 Understanding Device Support Understanding Device Loads Table 7-1 Device Load Descriptions (continued) Device Cisco Catalyst 6000 8 Port T1/E1 and Services Module Description Loads for these devices vary depending on how the device is being used: • • • Conference Bridge loads begin with C001. page 7-7 Verifying the Load on Cisco IP Phones. Updating Device Loads. All other devices of that type use the old load until you update the system-wide defaults for that device with the new load. Transcoder loads begin with M001. Digital Gateway loads begin with D004. page 7-9 Updating Device Loads You can apply a new load to a single device before applying it as a system-wide default. page 7-9 Updating Device Defaults. however. Cisco Catalyst 6000 24 Port FXS Analog Interface Module Related Topics • • Loads for these devices begin with A002. that only the device you have updated with the new load will use that load. Remember. page 15-2 Cisco CallManager Administration Guide OL-1047-01 7-7 . This is useful for testing purposes.

Use uppercase for letters. The Find and List Phones page displays. The Phone Configuration window appears. a phone might use load P002K202. Step 6 Enter the appropriate load in the Load Information field.Chapter 7 Understanding Device Loads Understanding Device Support Updating a Load on a Cisco IP Phone Follow these instructions to update a load on a particular Cisco IP phone. page 15-2 Cisco CallManager Administration Guide 7-8 OL-1047-01 . Click Device Name. Related Topics • • • Updating a Phone. For the change to take effect. The information is saved in Cisco CallManager Administration. page 46-13 Verifying the Load on Cisco IP Phones. Step 3 Step 4 Step 5 Enter search criteria to locate a specific phone. you must reset the phone. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Only the phone you updated with the new load uses that load. A list of discovered devices appears. page 7-9 Updating Device Defaults. Step 7 Click Update. Select Devices > Phone. For example.

Enter search criteria to locate a specific gateway. page 15-2 Configuring Gateways. The gateway configuration page displays. Follow these procedures to verify the load on the different phone types. page 45-1 Verifying the Load on Cisco IP Phones You can verify the load locally on the Cisco IP phones. Click Update. enter the appropriate load. Click Device Name. Cisco CallManager Administration Guide OL-1047-01 7-9 . you must reset the gateway. you must update the device defaults for that type of gateway. Step 6 Step 7 In the Load Information field. A list of discovered gateways appears. follow these steps to verify the load version. For the change to take effect. The information is saved in Cisco CallManager Administration. To update all gateways of a specific type with a new load. Cisco IP Phone 7960/7940 Using the Cisco IP Phone 7960/7940.Chapter 7 Understanding Device Support Understanding Device Loads Updating the Load on a Cisco Gateway Follow these steps to update a load on a particular Cisco gateway. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Select Device > Gateway. Only the gateway you updated with the new load uses that load. Related Topics • • Updating Device Defaults.

Adding Devices to Cisco CallManager Before you can use devices. page 47-5 Adding Cisco uOne Ports. Scroll to Firmware Versions. The Application Load ID indicates the current firmware version. page 46-7 Adding Phone Button Templates. Scroll to select Status. page 45-7 Cisco CallManager Administration Guide 7-10 OL-1047-01 . Refer to these sections for assistance in adding telephony devices to the Cisco CallManager’s configuration database: • • • • Adding a Phone. Press the Select soft key. Related Topics • Updating a Load on a Cisco IP Phone. if you configured the phone with load P002K202. The display shows the letter and the last three digits of the phone load in use. such as gateways and IP phones in your IP telephony network.Chapter 7 Adding Devices to Cisco CallManager Understanding Device Support Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Press settings. Press Select. you must add them to the Cisco CallManager configuration database. page 43-12 Adding Gateways to Cisco CallManager. For example. page 7-8 Cisco IP Phone Models 12 SP+ and 30 VIP On the phone whose load has been changed.02. press *. the display would read k2. .

page 8-14 Cisco CallManager Administration Guide OL-1047-01 8-1 . monitoring line status. page 8-10 Cisco WebAttendant Redundancy. This section covers the following topics: • • • • • Cisco WebAttendant Configuration Checklist. Administrative tasks such as adding users. The Cisco WebAttendant client provides a graphical user interface for controlling a Cisco IP Phone as an attendant console. The Cisco Telephony Call Dispatcher (TCD) service running on the Cisco CallManager communicates with Cisco WebAttendant clients for call routing and control. The Cisco WebAttendant client. and directing calls. Multiple clients can connect to a single Cisco CallManager.C H A P T E R 8 Understanding Cisco WebAttendant Cisco WebAttendant client-server application enables you to set up Cisco IP Phones as attendant consoles. A receptionist or administrative assistant can use Cisco WebAttendant to handle calls for a department or company or an individual can use it. page 8-13 Tips and Troubleshooting. and starting and stopping the TCD service are performed using Cisco CallManager Administration. page 8-2 Configuring Cisco CallManager for Cisco WebAttendant. installs on a PC that has IP connectivity to the Cisco CallManager system. a plug-in application. page 8-3 Client Installation and Configuration. The client works in conjunction with a Cisco IP Phone that is registered to a Cisco CallManager (one client for each phone that will be used as an attendant console). including speed dial buttons and quick directory access for looking up phone numbers. configuring pilot points and hunt groups for call routing. and services client database requests. monitors and reports line state.

page 32-5 Understanding Pilot Points and Hunt Groups. page 8-4 Configuring Pilot Points. Set up pilot points and hunt groups. page 8-9 On Each Cisco CallManager in the Cluster Step 5 Setting Up the wauser Shared Create a wauser shared directory with read/write access for Cisco WebAttendant Directory for Cisco WebAttendant. “Sharing Default Directory Database Information” section on page 8-11 Cisco CallManager Administration Guide 8-2 OL-1047-01 . Make sure that each Cisco WebAttendant user’s Cisco IP Phone is set up correctly for use with Cisco WebAttendant. You must perform this step to ensure Cisco WebAttendant clients can display directory information. page 32-19 users. page 32-10 Setting Up Cisco IP Phones for Use with Cisco WebAttendant. Task Cisco CallManager Administration Step 1 Step 2 Related Procedures and Topics Adding a Cisco WebAttendant User. Starting the Telephony Call Dispatcher.Chapter 8 Cisco WebAttendant Configuration Checklist Understanding Cisco WebAttendant Cisco WebAttendant Configuration Checklist The following table provides an overview of the steps you will need to complete to set up Cisco WebAttendants. page 32-2 Configuring Hunt Groups. page 32-20 Understanding the Cisco Telephony Call Dispatcher. Step 3 Step 4 Make sure the Telephony Call Dispatcher service is running on all Cisco CallManagers in the cluster. page 8-6 Add Cisco WebAttendant users.

Chapter 8 Understanding Cisco WebAttendant Configuring Cisco CallManager for Cisco WebAttendant Task Cisco WebAttendant Client PCs Step 6 Related Procedures and Topics Installing the Cisco WebAttendant Client. page 8-9 Cisco CallManager Administration Guide OL-1047-01 8-3 . • • • • Cisco WebAttendant Users. page 8-6 Understanding the Cisco Telephony Call Dispatcher. page 8-10 Install and configure the Cisco WebAttendant client on each Cisco WebAttendant user’s PC. page 32-1 Cisco WebAttendant Redundancy. page 8-13 Tips and Troubleshooting. Related Topics • • • Configuring Cisco WebAttendants. page 32-13 Configuring Cisco WebAttendant Client Settings. page 8-4 Setting Up Cisco IP Phones for Use with Cisco WebAttendant. page 32-14 Cisco WebAttendant Client Requirements. page 8-14 Configuring Cisco CallManager for Cisco WebAttendant The topics in this section provide an overview of the Cisco CallManager server components that must be configured within Cisco CallManager Administration to set up Cisco WebAttendants. page 8-4 Understanding Pilot Points and Hunt Groups.

they must first be added as a Cisco WebAttendant user and assigned a password. Note Cisco WebAttendant user IDs and passwords are not the same as Directory users and passwords entered in the User area of Cisco CallManager. The Cisco WebAttendant user and password database is completely separate from the Cisco CallManager Directory user database. Cisco WebAttendant client. The Cisco WebAttendant User Configuration pages also enable administrators to delete Cisco WebAttendant users or to modify user IDs and password information. page 32-10 Setting Up Cisco IP Phones for Use with Cisco WebAttendant Cisco WebAttendant works in conjunction with a Cisco IP Phone. The MAC address that is defined in the Settings dialog box of the Cisco WebAttendant application links the Cisco CallManager. and the Cisco IP Phone. This means that the IP Address or Host Name field in the Cisco Telephony Call Dispatcher Settings section of the client Settings dialog box should be the address of the Cisco CallManager server to which the Cisco IP Phone is normally registered. Configure the Cisco WebAttendant client to connect to the same Cisco CallManager server as its associated Cisco IP Phone. Cisco CallManager Administration Guide 8-4 OL-1047-01 . Cisco WebAttendant users are special user accounts that are created in the Cisco WebAttendant User Configuration page in Cisco CallManager Administration.Chapter 8 Configuring Cisco CallManager for Cisco WebAttendant Understanding Cisco WebAttendant Cisco WebAttendant Users Before a user can log in to a Cisco WebAttendant client to answer and direct calls. Related Topics • Adding a Cisco WebAttendant User.

Cisco IP Phone 12-Series model. or Cisco IP Phone 30VIP. ensure each phone is set up according to these guideline and that each phone is registered with its own Cisco WebAttendant client. Ensure the Cisco IP Phone has buttons for Hold and Transfer for Cisco WebAttendant to work properly. page 46-5 Cisco CallManager Administration Guide OL-1047-01 8-5 . up to eight. If a headset will be used. • • • • • Related Topics • • • Configuring Cisco WebAttendant Client Settings. If a Cisco WebAttendant user will be logging in to Cisco WebAttendant at more than one phone. Disable call waiting and call forwarding for lines and directory numbers on Cisco IP Phones used as Cisco WebAttendant consoles. Ensure the Cisco IP Phone is added as a device in Cisco CallManager before it is used with Cisco WebAttendant.Chapter 8 Understanding Cisco WebAttendant Configuring Cisco CallManager for Cisco WebAttendant Cisco IP Phones used with Cisco WebAttendant must meet the following guidelines: • • • Use Cisco WebAttendan with any Cisco IP Phone 7960/7940 models. Configure a maximum of eight lines for use with Cisco WebAttendant. The number of Smart Lines (SLs) available on Cisco WebAttendant is the same as the number of lines configured on the phone button template for the Cisco IP Phone. page 32-14 Understanding Default Phone Button Templates. ensure the phone has a headset button (Cisco IP Phone 7960/740 models) or an Answer/Release button assigned on the phone’s button template (older Cisco IP Phone models). Directory numbers assigned to a Cisco IP Phone that is used with Cisco WebAttendant must not appear on any other device in the system. page 47-1 Configuring Cisco IP Phones. Do not use a shared line appearance on any phone that will be used with Cisco WebAttendant.

Ensure the pilot point number is unique throughout the system (it cannot be a shared line appearance). TCD checks whether the line is available (not busy) and if it is. If the user is logged in and online. and the line is available. Cisco CallManager Administration Guide 8-6 OL-1047-01 . TCD goes through the members in the hunt group in order until it finds the first available destination for routing the call. If a user and a line number are specified. Specify a hunt group member as a directory number (device member) or as a Cisco WebAttendant user plus a line number (user member): • • If a directory number is specified. routes the call. TCD routes the call. TCD checks whether the user is logged in to a Cisco WebAttendant and online before checking whether the line is available. the Telephony Call Dispatcher uses the hunt group list for that pilot point to determine the call destination. A hunt group comprises a list of destinations that determine the call redirection order. • When a call comes in to a pilot point. • A pilot point is a virtual directory number for which the Telephony Call Dispatcher receives and directs calls based on a list of hunt group members. The advantage of specifying a user and line number instead of a directory number is that the Cisco WebAttendant user can be logged in and online at any Cisco IP Phone controlled by Cisco WebAttendant software in the cluster and receive calls.Chapter 8 Configuring Cisco CallManager for Cisco WebAttendant Understanding Cisco WebAttendant Understanding Pilot Points and Hunt Groups The Cisco Telephony Call Dispatcher must establish pilot points and hunt groups for call routing.

1025. For example. To handle overflow conditions. Caution Disable call waiting and call forwarding for lines and directory numbers on Cisco IP Phones used with Cisco WebAttendant consoles. which is the final member of the hunt group Cisco CallManager Administration Guide OL-1047-01 8-7 . Otherwise. Example Assume a pilot point named Support exists at directory number 4000. Make sure that “Always Route Member” is enabled for this voice mail number if TCD can perceive its line state.Chapter 8 Understanding Cisco WebAttendant Configuring Cisco CallManager for Cisco WebAttendant Caution When creating pilot point and hunt groups. 5060. listed in the hunt group in that order A voice mail number. be sure to consider overflow conditions. The hunt group for the Support pilot point contains the following members: • • • Support Admin. this voice mail number will not receive more than one call at a time. if you have a single pilot point called Support. all three directory numbers could be busy when a fourth call comes in. no additional directory numbers exist to which the call can be routed. with three directory numbers. Line 2 (Support Admin is the Cisco WebAttendant login for the administrative assistant for Support) Three directory numbers for support staff. configure one or more hunt groups that route calls to multiple Cisco WebAttendants with the final directory number being voice mail. and 1026. Line 1 and Support Admin. 1024. Do not use shared line appearances for any phone used with Cisco WebAttendant. In that case.

the Telephony Call Dispatcher (TCD) associated with that pilot point checks the members in the hunt group in order. directory number 4000. Because 4000 is a pilot point. 3. TCD routes the call to the first available directory number. directory number 1024 is busy. A call is received and directed to the Support Pilot Point.Chapter 8 Configuring Cisco CallManager for Cisco WebAttendant Understanding Cisco WebAttendant Figure 8-1 shows this example configuration. 1. and directory number 1026 is available. page 32-2 Configuring Hunt Groups. page 32-5 Cisco CallManager Administration Guide 8-8 47073 OL-1047-01 . beginning with Support Admin. which is 1026. directory number 1025 is busy. TCD determines that the Support Admin user is not online. the TCD never checks the 5060 number. Related Topics • • Configuring Pilot Points. Because 1026 is available. 2. Figure 8-1 Pilot Point and Hunt Group Example Support Pilot Point 4000 Hunt Group members for Support Pilot Point Support Admin: Line 1 Support Admin: Line 2 1024 1025 1026 5060 9201 9202 9203 9204 Cisco WebAttendant phone 5060 Voice mail Support staff directory numbers 1024 1025 1026 Support Admin logged in to Cisco WebAttendant The following example describes a simple call routing scenario for the configuration shown in Figure 8-1. Line 1.

available. not all TCDs are required to have a route point. a Cisco CallManager service. on-hook. and the IP phones used with Cisco WebAttendant clients. answering calls. Restart TCD to correct the problem. Note When you add a new Cisco WebAttendant user or modify user ID and password information for an existing user. This is required for Cisco WebAttendant redundancy to work properly. and disconnecting calls) Call dispatching from pilot point directory numbers to the appropriate destination based on hunt groups Line status (unknown. provides communication among Cisco CallManager servers. TCD handles Cisco WebAttendant client requests for • • • • Call control (making calls. putting calls on and taking calls off hold.Chapter 8 Understanding Cisco WebAttendant Configuring Cisco CallManager for Cisco WebAttendant Understanding the Cisco Telephony Call Dispatcher The Cisco Telephony Call Dispatcher (TCD). Cisco WebAttendant clients. Note If you are using Cisco WebAttendant in a cluster environment. or off-hook) User directory information (TCD caches and periodically updates directory information for fast lookup by the Cisco WebAttendant client) TCD also provides the mechanism for automated recovery for Cisco WebAttendant if a Cisco CallManager fails. Cisco CallManager Administration Guide OL-1047-01 8-9 . it will take approximately 6 minutes before the changes will take effect and the user can log in to Cisco WebAttendant. ensure all Cisco CallManagers within a cluster have the TCD service installed and running. all Cisco WebAttendant clients connected to that TCD do not work. If TCD stops running. redirecting calls. however. Note No automated recovery for a TCD failure exists.

Network connectivity to the Cisco CallManager Cisco CallManager Administration Guide 8-10 OL-1047-01 .0 (Service Pack 3 or greater) workstation or server Microsoft Internet Explorer 4. page 8-11 Cisco WebAttendant Client Requirements The following list gives Cisco WebAttendant PC client requirements: • • • • Operating system—Microsoft Windows 98. page 8-11 Client Configuration. Windows 2000. Access it through the Microsoft Internet Explorer browser (version 4. The Cisco WebAttendant provides a web-based GUI for using a Cisco IP Phone as an attendant console. or Windows NT 4.0 or later web browser with Active X enabled Display adapter color palette setting — minimum of 256 colors. page 32-20 Client Installation and Configuration The Cisco WebAttendant client is a plug-in application that is installed on a PC that has IP connectivity to the Cisco CallManager server. page 8-13 Starting the Telephony Call Dispatcher. The Cisco WebAttendant client application registers with and receives call dispatching services from the Telephony Call Dispatcher (TCD) services on the Cisco CallManager. select 16-bit color or greater for optimal display. The rest of this section discusses the following topics: • • • Cisco WebAttendant Client Requirements. page 8-10 Client Installation.0 or later).Chapter 8 Client Installation and Configuration Understanding Cisco WebAttendant Related Topics • • Cisco WebAttendant Redundancy. Multiple Cisco WebAttendant clients can simultaneously be registered with a Cisco CallManager to use these services.

Related Topics • • Configuring Cisco WebAttendant Client Settings.Chapter 8 Understanding Cisco WebAttendant Sharing Default Directory Database Information Client Installation Access and install the Cisco WebAttendant client from the Cisco CallManager Application Plug-In Installation page. page 8-11 Sharing Default Directory Database Information The Cisco WebAttendant client displays user and line information in the Directory section of its user interface. Related Topics • Installing the Cisco WebAttendant Client. open Cisco CallManager Administration and choose Application > Install Plugins. page 32-14 Sharing Default Directory Database Information. page 32-13 Client Configuration Configure each Cisco WebAttendant client to meet the following criteria: • • • Provide the Cisco WebAttendant user and password Connect to the correct Cisco CallManager TCD server and directory database Associate the MAC address of the Cisco IP Phone being used with the Cisco WebAttendant client with the Cisco CallManager server Note Ensure the Cisco WebAttendant client TCD IP Address or Host Name setting points to the Cisco CallManager server where its associated Cisco IP Phone is normally registered. Cisco CallManager Administration Guide OL-1047-01 8-11 . The Cisco TCD Database Path field in the Cisco WebAttendant client Settings dialog box controls where the Cisco WebAttendant client looks for its directory information. To locate the client plug-in.

Cisco recommends this setting.) You must then point the Cisco WebAttendant client to this file by entering the path to the file in the Cisco TCD Database Path field in the client Settings dialog box. Ensure this is done on all Cisco CallManagers in the cluster. For more information on how to do this. the client will use that setting until you change it. the Cisco CallManager administrator must rename the C:\Program Files\Cisco\Users folder to “wausers” and set network security and share permissions so that all Cisco WebAttendant users have read and write access. Choosing to do this makes any database changes made through Cisco CallManager not automatically available to the Cisco WebAttendant client: • You must manually copy a new version of the database file to the new location when you need to update Cisco WebAttendant client users with database changes.mdb to a different location. Specifying a Location for the TCD Database Path As an alternative to using the default setting (leaving the field blank). so that the client uses the default database from the TCD associated with the Cisco WebAttendant client. Default Setting for TCD Database Path The default setting leaves this field blank. the client uses cached directory information from the Cisco CallManager Directory user database. Cisco CallManager Administration Guide 8-12 OL-1047-01 . you must restart the client for the change to take effect. You can also set up the client to point to an alternate database. refer to the “Setting Up the wauser Shared Directory for Cisco WebAttendant” section on page 32-19. if you manually specify a TCD Database Path in the Settings dialog for the client. copy the file on the Cisco CallManager server named C:\Program Files\Cisco\Users\UsersDB1.Chapter 8 Sharing Default Directory Database Information Understanding Cisco WebAttendant By default. (This could be a file in a different shared directory on the network or a file on the Cisco WebAttendant user’s PC. • If you change the TCD Database Path setting for a Cisco WebAttendant client. This ensures that the client directory information automatically updates within 24 hours as changes are made to the Cisco CallManager directory database. Also. To ensure that this default setting works properly.mdb or C:\Program Files\Cisco\UsersDB2.

page 32-14 Cisco WebAttendant Redundancy The TCD service provides the mechanism for Cisco WebAttendant redundancy. its TCD will resume servicing its route points and Cisco WebAttendant clients. • When the Cisco CallManager comes back up. Cisco CallManager Administration Guide OL-1047-01 8-13 . the following events occur: • Another TCD service running on a Cisco CallManager within the cluster takes over servicing of the route points associated with the failed Cisco CallManager. If only TCD fails (and Cisco CallManager is still running). Restart TCD to correct the problem. ensure all Cisco CallManagers in the cluster have TCD installed and running. If a Cisco CallManager fails. Note For Cisco WebAttendant redundancy to work correctly. page 32-19 Configuring Cisco WebAttendant Client Settings.Chapter 8 Understanding Cisco WebAttendant Cisco WebAttendant Redundancy Related Topics • • Setting Up the wauser Shared Directory for Cisco WebAttendant. Note No automated recovery for a TCD failure exists. all Cisco WebAttendant clients connected to that TCD stop working. You do not need to have route points configured for TCD services running on backup (standby) Cisco CallManagers in the cluster. The Cisco WebAttendant clients that were attached to the failed TCD service attempt to locate and connect to the TCD service on the Cisco CallManager server where their associated Cisco IP Phone registered after failover.

Figure 8-2 shows a sample performance report for Cisco WebAttendant and TCD. page 8-16 Viewing Cisco WebAttendant Performance Monitors The ScmLineLinkState performance monitor for Cisco WebAttendant provides a quick way to check whether Cisco WebAttendant is functioning correctly: • • If the ScmLineLinkState counter is 11. If this digit is 0. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Log in to the Cisco CallManager server. Cisco CallManager Administration Guide 8-14 OL-1047-01 . perform the following procedure. TCD is functioning normally. and choose Cisco WebAttendant from the Object drop-down list box. Choose System Monitor. Click Add. a problem probably exists with Cisco CallManager. Click the View report data icon. The leftmost digit of ScmLineLinkState indicates whether TCD is connected to and registered with the Cisco CallManager CTI. The rightmost digit of ScmLineLinkState indicates whether TCD can perceive line state information through Cisco CallManager. enable All Counters. • To view ScmLineLinkState and other performance monitoring information for Cisco WebAttendant and TCD. Click the + (Add counter) icon. page 8-14 Troubleshooting. Choose Start > Programs > Administrative Tools > Performance.Chapter 8 Tips and Troubleshooting Understanding Cisco WebAttendant Tips and Troubleshooting This section provides information about the following topics: • • Viewing Cisco WebAttendant Performance Monitors. If this digit is 0. a problem may exist with the CTI or the directory.

Chapter 8 Understanding Cisco WebAttendant Tips and Troubleshooting Figure 8-2 Sample Performance Counter Report for Cisco WebAttendant The following list gives other performance monitoring information provided for Cisco WebAttendant: • • • • • • • Heartbeat—Number of seconds TCD has been running StartTime—Platform-based start time for this TCD TotalActiveCalls—Total number of active calls for this TCD TotalActiveLines—Total number of active lines for this TCD TotalCalls—Total of all calls handled by this TCD TotalClients — Number of Cisco WebAttendant clients associated with this TCD TotalCtiRoutePoints—Number of pilot points (route points) for this TCD Cisco CallManager Administration Guide OL-1047-01 8-15 .

Chapter 8 Tips and Troubleshooting Understanding Cisco WebAttendant • • • • TotalOnlineClients—Number of Cisco WebAttendant clients currently logged in and online TotalRedirectedCalls—Total number of calls redirected by pilot points (route points) for this TCD TotalRegisteredClients—Number of Cisco WebAttendant clients registered with this TCD Version—TCD version Troubleshooting This section addresses questions you may have or situations you may encounter when administering Cisco WebAttendant. the voice mail number will not receive more than one call at a time. Cisco CallManager Administration Guide 8-16 OL-1047-01 . Ensure the final member of a hunt group a number for voice mail. enable the “Always Route Calls” option for the number. Always choose “None” as the partition for a pilot point. Make sure that phones and pilot points are set up correctly for use with Cisco WebAttendant: • • • • Do not enable call waiting or call forwarding for any phone used as a Cisco WebAttendant console. auto attendant. Avoid these common configuration mistakes. See the “Setting Up the wauser Shared Directory for Cisco WebAttendant” section on page 32-19 for instructions. The Cisco WebAttendant user and client PC must have read/write access to the wauser shared directory on the Cisco CallManager. simultaneous calls. If TCD can perceive the line state of the voice mail number. Otherwise. or other device that can handle multiple. The final member of a hunt group must be able to handle overflow conditions. Do not use shared line appearance for any lines on any phones that are used with Cisco WebAttendant. Do not place pilot points in a partition.

The Cisco WebAttendant user and client PC must have read/write access to the wauser shared directory on the Cisco CallManager. No directory information exists for a Cisco WebAttendant client. Cisco WebAttendant users and passwords configured in the Cisco WebAttendant User Configuration area in Cisco CallManager Administration are not the same as directory users and passwords entered in the User area of Cisco CallManager. Make sure that Cisco CallManager and TCD are both running.Chapter 8 Understanding Cisco WebAttendant Tips and Troubleshooting A user cannot log in to Cisco WebAttendant client. If you have modified the Shared As properties for the wausers folder. The Cisco WebAttendant user and password database is completely separate from the Cisco CallManager directory user database. Check to make sure that the Cisco Webattendant client setting for the TCD Database Path is correct and that no network security or access problems exist for the directory shared as wausers or network issues that prevent connection. have the Cisco WebAttendant users log out of the Cisco WebAttendant client. Check ScmLineLinkState to see whether Cisco CallManager and TCD are functioning normally. Check to see that the user has been added in the Cisco WebAttendant User Configuration area of Cisco CallManager Administration and that the correct user name and password are specified in the client Settings dialog box. Directory information is available. Make sure that Cisco CallManager and TCD are both running. Refer to “Viewing Cisco WebAttendant Performance Monitors” section on page 8-14. This can occur due to a problem during Cisco CallManager installation (CTI Framework user not created). No Cisco WebAttendant users can log in to Cisco WebAttendant. log out of Windows. but no user can log in to Cisco WebAttendant. See the “Setting Up the wauser Shared Directory for Cisco WebAttendant” section on page 32-19 for instructions. no line state information is available. then log back in to Windows to make sure that the new sharing and permission settings are in effect. Contact the TAC if you receive this error message. Cisco CallManager Administration Guide OL-1047-01 8-17 .

Chapter 8 Tips and Troubleshooting Understanding Cisco WebAttendant Cisco WebAttendant user cannot see line state for a phone that is connected to a gateway. Cisco CallManager Administration Guide 8-18 OL-1047-01 . A phone that connects to a gateway and gets its connection to the Cisco CallManager through the gateway is considered outside the system. TCD can only monitor the status of internal devices and phone lines.

Cisco CallManager Administration Guide OL-1047-01 9-1 . If you are not responsible for LDAP administration. while authorization identifies the telephony resources a user is permitted to use. Authentication establishes a user’s right to access the system. In this section. This chapter is written for the administrator of the LDAP directory.0. you can skip this chapter. The following sections describe how Cisco CallManager works with the embedded directory. page 9-1 Using the Embedded Directory. such as a specific telephone extension. the term “embedded directory” is used to refer to the directory product that is provided with Cisco CallManager Release 3. This chapter includes the following topics: • • Cisco CallManager Directory.C H A P T E R 9 Understanding the LDAP Directory This chapter provides background information and deployment guidelines for using Cisco CallManager with the embedded Lightweight Directory Access Protocol (LDAP) directory. page 9-2 Cisco CallManager Directory Cisco CallManager uses an LDAP directory to store authentication and authorization information about telephony application users.

This chapter describes using the embedded directory in two different situations: • • Scenario 1: Using the Embedded Directory. page 9-4 Cisco CallManager Administration Guide 9-2 OL-1047-01 44521 Cisco AVVID embedded LDAP Directory . Figure 9-1 Using the Cisco CallManager Embedded Directory Configuration (devices & extensions) Cisco CallManager Configuration (application & user profile) Cisco CallManager embedded database CallManager Administration After the LDAP directory configuration is complete. The application server downloads these files to run workflow applications when you use the Administration client to start a specific application.Chapter 9 Using the Embedded Directory Understanding the LDAP Directory Using the Embedded Directory Figure 9-1 illustrates how the embedded directory works with the other components of Cisco CallManager. This design allows you to start workflow applications from anywhere in the network. you can upload completed workflow application files to it. page 9-3 Scenario 2: Using the Embedded Directory on a Pilot System. and to run them on application servers throughout the enterprise network.

Figure 9-2 Using the Embedded Directory Startup. but plans to add a large number of employees in the coming months.Chapter 9 Understanding the LDAP Directory Using the Embedded Directory Scenario 1: Using the Embedded Directory This section describes a scenario in which a small business.com Embedded Directory In this scenario. page 9-3 Managing User Entries in the Embedded Directory. 44522 Cisco CallManager Administration Guide OL-1047-01 9-3 .This scenario illustrates the following issues: • • Using the Embedded Directory. implements Cisco CallManager using only the embedded directory. Startup.com is a fast-growing Internet business that currently has only 20 employees. as shown in Figure 9-2. page 9-4 Using the Embedded Directory Startup. the Cisco CallManager administrator does not need to know anything about the LDAP directory.com. It is implementing Cisco CallManager with the embedded directory.

see Part 7 of the Cisco CallManager Administration Guide. using the embedded directory for testing a deployment of 100 phones with Cisco CallManager and the workflow framework. the administrator creates an LDIF file for adding each pilot user to the embedded directory.Chapter 9 Using the Embedded Directory Understanding the LDAP Directory Managing User Entries in the Embedded Directory The system administrator uses the Cisco CallManager Administrator User pages to manage user information and telephony resources. Figure 9-3 Using the Embedded Directory for a Pilot System Pilot server Cisco CallManager Embedded Directory In this scenario. For more information. as shown in the following example: Cisco CallManager Administration Guide 9-4 44525 OL-1047-01 . Scenario 2: Using the Embedded Directory on a Pilot System Acme Communications is implementing Cisco CallManager on a pilot system.

o=acme. ou=CCN. ou=CCN. o=acme. This page allows the administrator to enter or change only that information required to manage telephony resources for specific users.com changeType: add cn: John Smith givenName: John sn: Smith mail: jsmith userPassword: jsmith objectclass: top objectclass: inetOrgPerson objectclass: ciscoocUser ciscoatUserProfile: cn=jsmith-profile.Chapter 9 Understanding the LDAP Directory Using the Embedded Directory Example 9-1 LDIF File for Adding Users to Acme Communication’s Pilot System dn: cn=jsmith-CCNProfile.com changeType: add cn: jsmith-profile objectclass: top objectclass: ciscoocUserProfile ciscoatProfileOwner: John Smith ciscoatAppProfile: cn=jsmith-CCNProfile. the Cisco CallManager administrator can also add or modify users for testing purposes with the Cisco CallManager Administrator User configuration page. ou=CCN. ou=CCN. ou=CCN. o=acme.com dn: cn=John Smith. Cisco CallManager Administration Guide OL-1047-01 9-5 . o=acme. o=acme.com changeType: add cn: jsmith-CCNProfile objectclass: top objectclass: ciscoCCNocAppProfile ciscoatProfileOwner: John Smith ciscoCCNatAllDevices: false ciscoCCNatControlDevices: SEP0010EB001801 ciscoCCNatControlDevices: SEP0010EB001B01 ciscoCCNatControlDevices: SEP0010EB003CF0 ciscoCCNatControlDevices: SEP0010EB003EA3 ciscoCCNatControlDevices: SEP0010EB003EC4 dn: cn=jsmith-profile.com Managing Users in the Pilot System During the pilot phase.

Chapter 9 Using the Embedded Directory Understanding the LDAP Directory Cisco CallManager Administration Guide 9-6 OL-1047-01 .

page 10-31 Cisco CallManager Administration Guide OL-1047-01 10-1 .0 and later) allow you to configure several different services on selected servers. page 10-2 Cisco TFTP Service Parameters. and delete service parameters for those services. With the Service Parameters application. page 10-29 Cisco Telephony Call Dispatcher Parameters. page 10-28 Cisco Database Layer Service Parameters. Refer to the “Service Parameter Restart Conditions” section on page 35-2 for information on when a Cisco CallManager restart is required for certain parameters. page 10-22 Cisco IP Voice Media Streaming Service Parameters. page 10-21 Cisco Messaging Interface Service Parameters. Some changes to service parameters may cause system failure.C H A P T E R 10 Understanding Service Parameters The Service Parameters configuration pages for Cisco CallManager (release 3. you can insert. Related Topics • • • • • • Cisco CallManager Service Parameters. modify. Caution You will never need to add or delete service parameters unless directed to do so by the Cisco Technical Assistance Center (TAC).

Specifies the mixer type to be used for AdHoc conferences. Valid values are T or F. Note If you must modify trace parameters. Table 10-1 Cisco CallManager Service Parameters ParamName AbleToEstablishMF Values Default: T Description Used for certification testing. Some changes to service parameters may cause system failure. when a user presses the Conference button on the phone. If the mixer type is set to Unicast Bridge.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Cisco CallManager Service Parameters Caution You will never need to add or delete service parameters unless directed by the Cisco Technical Assistance Center (TAC). AdHocConferenceMixerType Default: 2 Cisco CallManager Administration Guide 10-2 OL-1047-01 . Refer to the “Configuring Trace” section on page 36-1 for more information. Table 10-1 provides service parameters configured for Cisco CallManager. Cisco recommends that you do not change the default value. the conference supplementary service allocates a Unicast Bridge resource to handle the conference. Cisco strongly recommends doing so from the Trace Configuration page. This setting sends the SABME at startup instead of waiting for the distance end to do it.

Default: F Determines whether call diagnostic records are generated. and is then forwarded to the next voicemail port. but not any additional lines. the Cisco CallManager call forward feature does not skip the busy or unregistered voicemail port. When AdvancedCallForwardHopFlag = true: When selecting the next voicemail port. Cisco CallManager Administration Guide OL-1047-01 10-3 . instead. Valid value is any numeric value. CallAcceptTimer CallDiagnosticsEnabled Default: 10 Specifies the maximum time an application has to accept a call offered at a CTI port or route point. is rejected. Determines whether to automatically select the call on hold when the phone goes offhook if that call was the last signal sent to the phone. AnalogAccessUse729 AutoSelectHeldCallFlag Default: F Default: F Not supported for Cisco CallManager Release 3.0. AlwaysUsePrimeLine Default: F T = When phone goes offhook. the call is extended to the busy or unregistered voicemail port.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName AdvancedCallForwardHopFlag Values Default: F Description When AdvancedCallForwardHopFlag = false: When selecting the next voicemail port. Example: If a call comes in on a user’s second line. or the speaker button is pressed. going offhook makes only the first line active. Valid values are F = not generated T = generated CallParkReversionTimeout Default: 60 Designates the number of seconds to wait before reverting a parked party to the user who parked the call. the Cisco CallManager call forward feature skips the busy or unregistered voicemail port. in addition to going offhook to answer the call. The user must select the second line. the first line becomes active. the call is extended to the available voicemail port so that the voicemail ports are selected more efficiently.

CdrEnabled Default: F Determines whether Call Detail Records (CDRs) are generated. Integrated Data) system On the phone Has Call Waiting enabled Does not have Forward enabled CcmPriorityClass Default: 0 CcmPriorityClass = 0: Cisco CallManager process runs in normal priority class. Designates the number of seconds that a caller hear s ringback (alerting tone) if the person the caller is calling is in one of these states: • • • • Internal to the Cisco AVVID (Architecture for Voice. Valid values are T = CDRs are generated F = CDRs are not generated CdrLogCallsWithZeroDuration Flag Default: F ClearCallsWhenDatalinkGoes Down Default: T Enables logging of CDR records for calls that never connected or that lasted less than 1second. CcmPriorityClass = 2: Cisco CallManager process runs in high priority class.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName CallWaitingEnable CallWaitingTimeout Values Default: T Default: 180 Description Enables or disables call waiting for the entire system. Valid values are 0 = Do not clear calls when datalink goes down 1 = Clear calls when datalink goes down Cisco CallManager Administration Guide 10-4 OL-1047-01 . Determines whether calls to the phones terminate if the D-channel (datalink) terminates. CcmPriorityClass = 1: Cisco CallManager process switches between normal and high priority class every second. Video.

If no call forward busy is configured. the calls are not suspended. Cisco strongly recommends you do not change the default value. CtiApplicationHeartBeatTime CTINewCallAcceptTimeout Default: 30 Specifies the interval at which CTI sends heartbeat polls to applications. Cisco CallManager Administration Guide OL-1047-01 10-5 . redirect. Cisco CallManager forwards the call to the call forward busy number configured for the CTI port or CTI route point. Default: 4 (seconds) Specifies timeout interval. so that callers hear only silence. Timer ensures that. or disconnect). the Cisco CallManager waits for a configurable time for the application to handle the call (as in accept.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName ConnectDisconnectTimer Values Default: 7 Description Used for debugging purposes only. if the CTI application controlling the CTI ports/route points does not handle the call. Valid value is any numeric value. If the application does not respond within the set time. Parameter designates the maximum time allowed for a response from a connect or disconnect request. for calls made into CTI ports and CTI route points. answer. caller receives a fast busy tone. After the Cisco CallManager notifies the application (using JTAPI/TAPI) of an incoming call at a CTI port or CTI route point.

Timer designates the maximum time allowed for a response from a digit analysis requests. Files\Cisc o\DialPlan Default: 6 Used for debugging purposes only. Default: 300000 Denotes the time between two change of port status messages. This timer services the following specific CTI requests: • • • • • • • • • LINE_CALL_INITIATE_REQUEST CALL_ACCEPT_REQUEST CALL_ANSWER_REQUEST CALL_BLIND_TRANSFER_REQUEST CALL_DISCONNECT_REQUEST CALL_HOLD_REQUEST CALL_RETRIEVE_REQUEST CALL_SETUP_CONFERENCE_REQUEST CALL_SETUP_TRANSFER_REQUEST DbNoActivityTimeout Default: 30 Denotes the time to wait before closing the file after no database requests received. Timer ensures responses to CTI requests are generated for situations where network or remote Cisco CallManager node problems prevent the normal processing of the CTI requests. DeviceStatusPollInterval_msec DialPlanPath Notifies the digit analysis component where to Default: c:\Program find national dial plan files. Valid value is any numeric value.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName CTIRequestTimeout Values Default: 5 (seconds) Description Specifies timeout interval. Do not modify the default value. Valid value is any numeric value. DigitAnalysisTimer Cisco CallManager Administration Guide 10-6 OL-1047-01 . Cisco strongly recommends that you do not change the default value.

Default: 25 Designates the number of seconds between gateway status messages.225 call. Valid value is any numeric value. ForwardNoAnswerTimeout GatekeeperControlRegistration Type Default: F GatekeeperRefresh GatewayKeepAliveTimeout GatewayPollTimeout Default: 60 Designates the number of seconds between seconds gatekeeper refresh messages. Cisco strongly recommends that you do not change this parameter unless you have a complete understanding of RAS registration. or call connecting.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName DisplayIEDeliveryFlag Values Default: F Description Enables the delivery of the display IE in SETUP and CONNECT messages for the calling and called party name delivery service when set to T. Designates whether silence plays. Default: 0 Determines. the digital gateway does not play silence after receiving the Alert message. When this flag is set. Default: 10 Designates the number of seconds to wait for a response from a GatewayOpenReq. DtSilenceFlag Default: F EnableSNMP ForwardMaximumHopCount Default: T Default: 12 Designates maximum number of attempts to extend a forwarded call. whether processing the open logical channel (when audio is transmitted) on the call proceeding. Valid value is (Value >=1) Denotes H. Valid value is (Value >=1) Default: 12 Designates the number of seconds to wait before forwarding on No Answer Condition. H225ConnectTime Cisco CallManager Administration Guide OL-1047-01 10-7 .323 Gatekeeper Control Registration Type. Enables the collection of SNMP data from the Cisco CallManager.323/H. call alerting. on an outgoing H. This may enable a full duplex path before the Connect message is received on ISDN calls.

Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName HoldType Values Default: F Description Designates originator new hold type. This parameter interoperates with Nortel PBX when the PBX is configured to use the DMS100 protocol. and CONNECT messages. CALL PROCEEDING. media applications. The new hold type allows the user to press the line button on which the held call is stored to retrieve it. Cisco strongly recommends that this parameter never be changed. Used by anyone who configures streaming. ALERTING. Applies only to the DMS100 protocol for the digital access gateway in the Channel Identification IE of the SETUP. phones. Controls class of service of IP traffic and signals between Cisco CallManager to Cisco CallManager. etc. InterfaceIdentifierPresentFlag Default: F IpPrecedence Default: 0x000000 B0 Default: 3 IpTosCm2Cm Note The following list shows that the valid value for IpTosCm2Cm is between 0 and 7 and is represented as follows: 0 = routine 1 = priority 2 = immediate 3 = flash 4 = flashOver 5 = critical 6 = internet 7 = network Cisco CallManager Administration Guide 10-8 OL-1047-01 . Original Hold Type requires the user to press the hold button to retrieve a call from hold.

LineStateUpdateEnabled Default: T LowPriorityQueueThrottling Flag Default: F Cisco CallManager Administration Guide OL-1047-01 10-9 .Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName IpTosCm2Dvce Values Default: 3 Description Controls class of service of IP traffic and signals between Cisco CallManager to device. Designates whether when low-priority TCP queue gets too large. Controls class of service of IP traffic and signals between Cisco CallManager to Cisco CallManager. Determines whether Line State Server (used by Cisco WebAttendant) can track the active/inactive states of each line/directory number. Note The following list shows the valid value for IpTosCm2Dvce is between 0 and 7 and is represented as follows: 0 = routine 1 = priority 2 = immediate 3 = flash 4 = flashOver 5 = critical 6 = internet 7 = network L2RetriesN200 Default: 3 Designates the number of retries before declaring the datalink down. Valid value is any numeric value. the system starts throwing away new call attempts.

Default: 30 Designates that all the responses sent by Media Gateway are kept in memory for a certain time. MGCPConnectTime Default: 30 Designates that all the responses sent by Media seconds Gateway are kept in memory for a certain time. make it so all ports with an attendant number assigned to them are not usable for the life of the current call. MaxAdHocConference Default: 4 Max: 32 Cisco CallManager Administration Guide 10-10 OL-1047-01 . Compare whether the calling party number matches one of the associated analog access ports on an outbound analog access gateway call. otherwise. Valid value is any numeric value. If so. MGCPTimeout MatchingCgpnWithAttendant Flag Default: 5 seconds Default: F Designates the number of seconds to wait before Cisco CallManager retries its request. select that port. Default for this duration is set to 30 seconds. Specifies the maximum number of participants per port that can be added to a Unicast ad-hoc conference. This forces selection of another analog access device if another analog access gateway was configured in RoutePoint/RouteGroup. Use this value to adjust call response time. You should not change this value. MGCPRespTimeout Note You should not change this value. Default for this duration is set to 30 seconds by default. If another analog access gateway was not configured. the user hears a fast busy signal.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName LowPriorityQueueThrottling MaxCount Values Default: 1000 Description Designates the maximum number of outstanding low-priority stimulus messages in the queue before new call attempts are discarded.

MaxErrorsToReport Default: 1 MaxMeetMeConferenceUnicast MaxNumberOfReceivedIFrames BeforeAcking Default: 10 Specifies the maximum number of participants per port that can join a Unicast Meet-Me conference. Cisco CallManager allows a maximum number of CTI connections. calls can overwhelm the system to the point where no calls can complete. each CTI application (or instance of the application) has a single CTI connection to the Cisco CallManager. This limit on the number of CTI connections is independent of the number of CTI devices that the application can control. Max: 32 Default: 0 Specifies number of receive 5 I-Frames received before responding with a receiver ready (RR) for an acknowledgement (ACK). Typically. Valid value is any numeric value. Valid value is any numeric value. Decreasing the LowPriorityQueueThrottlingMaxCount provides faster dial tone but also increases the chances for calls being rejected. for example. Specifies the number of errors to report per data link establishment. Cisco CallManager Administration Guide OL-1047-01 10-11 . Set these values to restore usability if the system becomes overwhelmed. Under a heavy load.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName MaxCTI Connections Values Default: 400 Description Designates the maximum number of CTI connections. Valid value is any numeric value. each Softphone instance has a single CTI connection to the Cisco CallManager. MaxNumberOfStationsIniting Default: 50 Designates the maximum number of stations that can try to initialize without completing all database requests.

then phone registrations could slow the Cisco CallManager’s real time response. Note If the performance value is set too high. the total time for a large group of phones to register will be slow.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName MaxStationsInitPerSecond Values Description Default: 10 Parameter is an integer with a value usually between 5 and 15. MediaExchangeInterfaceCaps Timeout MediaExchangeTimeout MessageWaitingOffDN Default: 8 Specifies the time for a device to send capabilities for a media connection. Valid value is any numeric value. If set too low. Valid value is any numeric value. Specifies the directory to which calls from a voicemail system are directed to disable or turn off the message waiting light for the specified calling party. This parameter throttles the number of phones allowed to concurrently register with Cisco CallManager without being queued. Specifies the directory number to which calls from a voicemail system are directed to enable or turn on a message waiting light for the specified calling party. Specifies the time for a media connection to be made. Default: 5 MessageWaitingOnDN Cisco CallManager Administration Guide 10-12 OL-1047-01 .

Enough Bandwidth Default: 7 Specifies the maximum number of outstanding I-Frames that are not acknowledged. • OutOfBandwidthText Designates the text to be displayed when the call Default: cannot be placed because not enough bandwidth Not exists. never set this parameter below 20. the Numbering Plan Information is also set to UNKNOWN.323 calls and ISDN calls has the following characteristics: • • If set to 0: disabled If set to 1: a check determines what the ISDN Type of Number on the called party information element is. Default: 20 Specifies the preferred time set for delivering packets. never set this parameter below 20. To avoid adding latency. and the Type of Number is set to UNKNOWN. If set to 2: The Numbering Plan Information is set to a PRIVATE PLAN. Valid value is any numeric value. Cisco strongly recommends using the default setting for this parameter. This control that is available for H. To avoid adding latency. OutStandingIFramesK OverlapReceivingForPriFlag PreferredG711Millisecond PacketSize PreferredG723Millisecond PacketSize PreferredG729Millisecond PacketSize Default: F Default: 20 Specifies the preferred time set for delivering packets.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName NumberingPlanInfo Values Default: 1 Description Gives some control over the ISDN Numbering Plan Information field on the Called Party Number. Default: 30 Specifies the preferred time set for delivering packets. To avoid adding latency. Cisco CallManager Administration Guide OL-1047-01 10-13 . If the Type of Number is set to UNKNOWN. never set value for this parameter below 20.

SdlTraceDataSize SdlTraceFilePath Specifies the absolute path where SDL trace files Default: c:\Program are located. When the flag is set to True. Parameter tells SDL trace processing how many bytes of raw data to dump from each signal that it traces. so that SDL traces are collected by default. SdlTraceFlag Cisco CallManager Administration Guide 10-14 OL-1047-01 . are re-ordered when a call is placed using the associated route list. 0 Default: 100 Used in the SDL layer.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName RASMulticastFlag Values Default: F Description Allows multicast registration of RAS. It is set to true by default. and are associated with a route list. RedirectingNumIEDeliveryFlag Default: F ReorderRouteList Default: F SdlListeningPort SdlMaxUnHandledExceptions Default: 8002 Default: 5 SdlTraceDataFlags Default: Provides a bit mask used for enabling tracing of 0x0000011 SDL non-application-specific components or for modifying the behavior of SDL tracing. Caution: Do not set this parameter unless you want all RAS devices to register to Cisco CallManager. Specifies the maximum number of Cisco CallManager exceptions before Cisco CallManager stops running. Applies to the SETUP message only on all protocols for the digital access gateway. File\Cisco\ Trace\SDL \ Default: T Indicates whether SDL traces should be turned on or off. You should not change this value. the SETUP message includes RedirectingNumberIE to indicate the first redirecting number and the redirecting reason of the call when Call Forward happens. Specifies when set to true that devices that have the same selection order in a route group.

931 and H. Determines whether silence suppression is disabled for all devices on gateways. sending these status enquiries does not disrupt call connection. Cisco recommends you do not change the default value. Default: T Determines whether system statistics are generated. StripPoundCalledPartyFlag Default: T Cisco CallManager Administration Guide OL-1047-01 10-15 . Provides an application-specified bit mask used for the application tracing and signal tracing. Valid value is any numeric value. If the device is within range.323 devices to check for out-of-range status. the call terminates. Determines whether silence suppression is disabled for all devices on a system-wide basis. Use any numeric value starting at 30. Valid values are F = not generated T = generated StatisticsEnabled StatusEnqPollFlag Default: F Sends status enquiries to H. Default: 30 Designates the number of seconds between keepalive messages sent to Cisco IP Phones (stations). Used for certification testing. Cisco recommends you do not use the 0 value. Enables the stripping of # sign digits from the called party IE. SdlTraceTotalNumFiles SdlTraceTypeFlags SilenceSuppressionSystemWide SilenceSuppressionWith Gateways StableIn4Flag Station2ndKeepaliveInterval StationKeepaliveInterval Default: 60 Designates the Keepalive Interval for backup server.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName SdlTraceMaxLines Values Default: 10000 Default: 100 Default: 0x00004B 05 Default: T Default: T Default: F Description Specifies the maximum number of lines in each file before starting the next file. Specifies the maximum number of files before restarting file count and overwriting old files. of the inbound and outbound Q. If the device is determined to be out of range.225 SETUP message.

no re-routing to the next device in the route list is attempted and the call is released with the associated cause. no re-routing to the next device in the route list is attempted and the call is released with the associated cause. that if a call being routed through a route list detects the associated “cause” during the release of the call. Determines whether out of channels responses will be sent to event processing. all other values are in 1/8 second ticks. that if a call being routed through a route list detects the associated “cause” during the release of the call. Designates Layer 2 Keepalive interval. This is the only timer value that is in 1/40-second ticks. Designates Layer 2 Retransmission time. Specifies when set to true. StopRoutingOnUnallocatedNumber Flag Default: F StopRoutingOnUserBusyFlag Default: F SuppressOutOfChansEvents Default: T TimerSendProgress_msec Default: 3000 Default: 2000 Default: 1000 TimerT1Frame_msec TimerT200_msec TimerT203_msec Default: 10000 Cisco CallManager Administration Guide 10-16 OL-1047-01 . Sometimes the other end does not get back fast enough with the Alert.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName StopRoutingOnOutOfBandwidthFla g Values Default: F Description Specifies when set to true. Valid value is any numeric value in 1/8 second ticks. Specifies when set to true. Cisco strongly recommends that you do not change the default value. Progress. or Connect while in Call_initiated state. Valid value is any numeric value in 1/8 second ticks. Used for debugging purposes only. no re-routing to the next device in the route list is attempted and the call is released with the associated cause. Valid value is any numeric value in 1/40-second ticks. that if a call being routed through a route list detects the associated “cause” during the release of the call.

Valid value is any numeric value in 1/8-second ticks. Network-(Call Received) ALERTING Received. Valid value is any numeric value in 1/8-second ticks. Network-(Release Request) RELEASE sent. Network-(Disconnect Indication) DISCONNECT without progress ind sent. Specifies interdigit timeout for User-(Overlap Receiving) SETUP ACK sent. Network-(Call Present) SETUP sent. Specifies User/Network-(Any stable State) Datalink lost. Specifies Network-(Null) SUSPEND ACK sent. Valid value is any numeric value in 1/8-second ticks. Valid value is any numeric value in 1/8-second ticks. Specifies Network-(Disconnect Indication) DISCONNECT with progress ind sent. Valid value is any numeric value in 1/8-second ticks. Network-(Overlap Receiving) SETUP ACK received. Specifies User-(Disconnect Request) DISCONNECT sent. Valid value is any numeric value in 1/8-second ticks.Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName TimerT301_msec Values Default: 180000 Description Specifies User-(Call Delivered) ALERTING Received. Valid value is any numeric value in 1/8-second ticks. Network-(Overlap Sending) SETUP ACK sent. Specifies User-(Release Request) RELEASE sent. Valid value is any numeric value in 1/8-second ticks. Specifies User-(Overlap Sending) SETUP ACK received. TimerT302_msec Default: 10000 TimerT303_msec Default: 4000 Default: 20000 TimerT304_msec TimerT305_msec Default: 30000 TimerT306_msec Default: 30000 Default: 180000 Default: 4000 Default: 90000 TimerT307_msec TimerT308_msec TimerT309_msec Cisco CallManager Administration Guide OL-1047-01 10-17 . Valid value is any numeric value in 1/8-second ticks. Specifies User-(Call Initiated) SETUP sent.

Valid value is any numeric value in 1/8-second ticks. Network-(Incoming Call Proceed) CALL PROCEED received. TimerT313_msec Default: 4000 Default: 120000 Default: 300000 Default: 30000 Default: 4000 Default: 10000 TimerT316_msec TimerT317_msec TimerT321_msec TimerT322_msec TimerTStatusEnqPoll_msec TimeToDelayBeforeSendingAn Ack_msec Default: 0 ToneOnCallForward ToneOnHoldTime Default: T Default: 10 Specifies the number of seconds to play some type of tone when a call is on hold (minimum of 5 Min: 5 seconds). Valid value is any numeric value in 25-millisecond ticks. 0 = send immediately. Valid value is any numeric value in 1/8-second ticks. Specifies User-(Connect Request) CONNECT sent. Max: 99999 Cisco CallManager Administration Guide 10-18 OL-1047-01 . Valid value is any numeric value in 1/8 second ticks. Specifies (Any state) STATUS ENQUIRY sent. Specifies (Any state) D-Channel failure.323 phone is still attached. Valid value is any numeric value in 1/8-second ticks. Designates flag to set tone on call forward on or off.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName TimerT310_msec Values Default: 10000 Description Specifies User-(Outgoing Call Proceed) CALL PROCEED received. Specifies the time to wait to send a receiver ready (RR) acknowledgement on a given non poll I-Frame. Valid value is any numeric value in 1/8-second ticks. Valid value is any numeric value in 1/8-second ticks. Specifies (Restart Request) RESTART sent. Valid value is any numeric value in 1/8-second ticks. Specifies (Any state) Timer initially used to send a StatusEnq to check whether Symbol H.

Chapter 10 Understanding Service Parameters Cisco CallManager Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName TosBitPosition Values Default: 3 Description Allows setting a bit between bit 0 and bit 4 along with IPTOS settings to make it compatible with Cisco DIFF-SERV (Differentiated Service). ToSendH225UserInfoMsg Default: F TypeOfCalledNumberForH225Devic Default: 0 es Denotes the type of number (TON) for H225 devices. Valid value is any numeric value representing a general number for your system (if you wish to provide caller ID functionality to called parties). The default value is 0. Cisco strongly recommends using the default setting because this flag can now be configured using Cisco CallManager Administration. and the second line is 14 characters. Specifies the text to be displayed to called parties who have caller ID capability. UnknownCallerId Designates the directory number to be displayed. Refer to the “Configuring Trace” section on page 36-1 for descriptive and configuration information on all trace parameters. A value of 2 denotes a national number. Valid value is any valid telephone number. Specifies whether Cisco CallManager sends H225 user information message. and 3. an international number. When ToSendH225UserInfoMsg = false Cisco CallManager does not send out the H225UserInformation message. The first line is 20 characters. Use a character setup that can be broken into two lines. When ToSendH225UserInfoMsg = true Cisco CallManager sends out the H225UserInformation message. Default: T Relates to the Unknown CallerId field. which denotes the value sent by call control. UnknownCallerIdFlag UnknownCallerIdText Default: Unknown Cisco CallManager Administration Guide OL-1047-01 10-19 . A value of 1 indicates an unknown number. each of which has the specified number of characters per line.

Specifies the number that is dialed when the “message” button on the phone is pressed. Related Topics • Configuring Service Parameters. Note Set VoiceMailMaximumHopCo unt to the number of voicemail ports in the system. VoiceMail VoiceMailMaximumHopCount Default: F Default: 12 Used together with AdvancedCallForwardHopFlag.Chapter 10 Cisco CallManager Service Parameters Understanding Service Parameters Table 10-1 Cisco CallManager Service Parameters (continued) ParamName UserUserIEStatus Values Default: F Description Designates whether the user-to-user information element (UUIE) is passed in the system. Enabling UUIE status allows ISDN PRI messages to include them on outbound PRI calls. allows the Cisco CallManager to select the next available voicemail port by skipping the busy or unregistered voicemail ports. page 35-1 Cisco CallManager Administration Guide 10-20 OL-1047-01 .

When set to True. Cisco CallManager uses default local IP address.0. PhoneTcpPort ServerIpTrack Cisco CallManager Administration Guide OL-1047-01 10-21 . Not used under normal circumstances. FileLocation String that represents the primary path for building Default: c:\Program Fil and serving files. Not used under normal circumstances. Cisco strongly recommends doing so from the Trace Configuration page. Do not change this parameter.0. Table 10-2 provides service parameters configured for Cisco TFTP. es\Cisco\TFTP path Default: 2000 Default: T Not used under normal circumstances. Not used under normal circumstances.1 Default: T Default: 3000 Default: 2001 Default: T Description Not used under normal circumstances. Note If you must modify trace parameters. Flag that enables configuration file deletion to ensure deleted devices do not still get configuration files. Refer to the “Configuring Trace” section on page 36-1 for more information.Chapter 10 Understanding Service Parameters Cisco TFTP Service Parameters Cisco TFTP Service Parameters Caution Never add or delete service parameters unless directed to do so by the Cisco Technical Assistance Center (TAC). Table 10-2 Cisco TFTP Service Parameters ParamName AnalogTcpPort CallManagerIp CallManagerIpTrack ChangeUDPPort DigitalTcpPort FileDelete Values Default: 2002 Default: 127. Some changes to service parameters may cause system failure. Do not change this parameter.

Note If you must modify trace parameters. Ciscostrongly recommends doing so from the Trace Configuration page. Refer to the “Configuring Trace” section on page 36-1 for more information. page 36-1 Understanding Trace Configuration.1 Description String that represents the IP address of the TFTP server if ServerIpTrack is false. Configuring Service Parameters. Table 10-3 provides service parameters configured for Cisco Messaging Interface (CMI). Refer to the “Configuring Trace” section on page 36-1 for descriptive and configuration information on all trace parameters. Some changes to service parameters may cause system failure.Chapter 10 Cisco Messaging Interface Service Parameters Understanding Service Parameters Table 10-2 Cisco TFTP Service Parameters (continued) ParamName TFTPIp Values Default: 127. page 31-1 Configuring Trace. page 36-2 Table 36-4 provides the trace parameters for Event Type. page 36-9 Cisco Messaging Interface Service Parameters Caution Do not add or delete service parameters unless directed to do so by the Cisco Technical Assistance Center (TAC). page 35-1 Configuring Cisco TFTP. UseDb Default: T Related Topics • • • • • Do not change this parameter. Cisco CallManager Administration Guide 10-22 OL-1047-01 .0. User Mask.0. and Date and Time.

BaudRate Recommended default: 9600 This parameter defines the EIA/TIA-232 connection that Cisco CallManager uses to connect to the voicemail system.. Cisco CallManager Administration Guide OL-1047-01 10-23 . You can use either the name of a Cisco CallManager or its IP address.Chapter 10 Understanding Service Parameters Cisco Messaging Interface Service Parameters Table 10-3 Cisco Messaging Interface (CMI) Service Parameters ParamName BackupCallManagerName Values Description This parameter defines the names of the Cisco CallManagers that are going to be used for the CMI backup. but the one shown here will frequently be correct. Note Many voicemail systems can be configured to use different baud rates. You can use either the name of a Cisco CallManager or its IP address. if existing on a local machine. Default: 7 This parameter defines the names of the Cisco CallManagers that are going to be used for the primary CMI. DataBits This parameter defines the EIA/TIA-232 connection that Cisco CallManager uses to connect to the voicemail system. CallManagerName If the default is left blank. CMI will choose the Cisco CallMan ager.

RouteFilter. If a legacy voicemail system has mailbox numbers that are no longer than the DNs on the system. and VoiceMailPartition. will default to empty strings. use this parameter to strip the most-significant digits. The remaining parameters. Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. KeepAliveDn None Cisco CallManager Administration Guide 10-24 OL-1047-01 . By programming that DN into the KeepAliveDn parameter. In this case.Chapter 10 Cisco Messaging Interface Service Parameters Understanding Service Parameters Table 10-3 Cisco Messaging Interface (CMI) Service Parameters (continued) ParamName DialingPlan Values Description CMI requires this parameter as one of four to register an intercept for the voicemail system with which CMI is going to work. InputDnSignificantDigits Default: 10 This parameter accommodates the differences between voicemailbox numbers and directory numbers (DNs). you will ensure that the invalid DN message is returned to the voicemail system when needed. For this string parameter for most voicemail systems. The numeric value of this parameter indicates how many digits should be used. DialingPlan. some Octel systems periodically send an invalid DN specifically for the purpose of verifying that the attached Cisco CallManager is functioning properly. you can turn off ValidateDns if you know the DN that the Octel system will use as a keepalive one. However. a value of F is acceptable.

OutputDnFormat Default: %010s Because this parameter is used to format the DNs sent to the voicemail system. most numbers passed to the voicemail system are formatted using this parameter. Default: Even This parameter defines the EIA/TIA-232 connection that CMI uses to connect to the voicemail system. Cisco CallManager Administration Guide OL-1047-01 10-25 . most numbers passed to the voicemail system are formatted using this parameter. or Space. Mark and Space rarely get used. OutputExternalFormat Parity Note Possible parity settings include None. Even. Odd. Mark.Chapter 10 Understanding Service Parameters Cisco Messaging Interface Service Parameters Table 10-3 Cisco Messaging Interface (CMI) Service Parameters (continued) ParamName MwiSearchSpace Values Description This parameter designates the search space to use when determining the device to be affected by the MWI lamp. Default: %010s Because this parameter is also used to format the DNs sent to the voicemail system. Settings are usually Even and None. Using just the first character of the parity name also works.

DialingPlan.Chapter 10 Cisco Messaging Interface Service Parameters Understanding Service Parameters Table 10-3 Cisco Messaging Interface (CMI) Service Parameters (continued) ParamName RouteFilter Values Description CMI requires this parameter as one of four to register an intercept for the voicemail system with which CMI is going to work. RouteFilter. Cisco CallManager Administration Guide 10-26 OL-1047-01 . and VoiceMailPartition. Note Small systems without a complex dialing plan usually only need the VoiceMailDn parameter. The remaining parameters. Note Use the SerialPort name that is the same name that you see in Device Manager under NT. will default to empty strings. SerialPort Default: COM1 This parameter defines the EIA/TIA-232 connection that CMI uses to connect to the voicemail system.

CMI sends a keepalive message to the Cisco CallManager at the rate (in seconds) this parameter specifies. During normal operations when CMI is attached to a Cisco CallManager.Chapter 10 Understanding Service Parameters Cisco Messaging Interface Service Parameters Table 10-3 Cisco Messaging Interface (CMI) Service Parameters (continued) ParamName SsapiKeepAliveInterval Values Default: 30 Description This numeric parameter specifies keepalive message interval. StopBits Default: 1 This parameter defines the EIA/TIA-232 connection that CMI uses to connect to the voicemail system. you may choose to skip this validation process by setting the ValidateDns parameter default to F. Note Do not change his parameter from the default value unless directed to do so by the Cisco Technical Assistance Center (TAC). CMI sends an invalid DN message is sent to the voicemailbox. ValidateDns Default: T Note On a system with a lot of traffic to and from the voicemail system. it normally validates the associated DN against the NumPlan table in an attempt to verify that the DN matches an existing DN known to Cisco CallManager. When CMI receives incoming lamp commands from the voicemail system. Cisco CallManager Administration Guide OL-1047-01 10-27 . If the DN is not found in NumPlan.

page 30-2 Configuring Trace. CMI requires this parameter as one of four to register an intercept for the voicemail system with which CMI is going to work.Chapter 10 Cisco IP Voice Media Streaming Service Parameters Understanding Service Parameters Table 10-3 Cisco Messaging Interface (CMI) Service Parameters (continued) ParamName Values Description Refer to the “Configuring Trace” section on page 36-1 for descriptive and configuration information on all trace parameters. Related Topics • • • • • • Configuring Service Parameters. page 36-9 Cisco IP Voice Media Streaming Service Parameters Caution Do not add or delete service parameters unless directed to do so by the Cisco Technical Assistance Center (TAC). Table 10-4 provides service parameters configured for Cisco IP Voice Media Streaming. page 35-1 Cisco Messaging Interface. VoiceMailDn VoiceMailPartition This parameter represents the voicemail access number. page 30-1 Most Commonly Changed CMI Service Parameters. Cisco CallManager Administration Guide 10-28 OL-1047-01 . User Mask. The voicemail DN resides in this partition. and Date and Time. Some changes to service parameters may cause system failure. page 36-2 Table 36-4 provides the trace parameters for Event Type. page 36-1 Understanding Trace Configuration.

page 36-1 Cisco Database Layer Service Parameters Caution Do not add or delete service parameters unless directed to do so by the Cisco Technical Assistance Center (TAC). page 34-3 Avoiding Call Failure/User Alert. Specifies time (number of seconds) for orphaned calls or conferences to stay up when a Cisco CallManager goes down. ChangeUDPPort MTP:OrphanStreamTimeout Default: 3000 Default: 300 MTP:RunFlag Default: F Refer to the “Configuring Trace” section on page 36-1 for descriptive and configuration information on all trace parameters. This flag (when set) enables MTP. page 34-4 Configuring Trace. Cisco CallManager Administration Guide OL-1047-01 10-29 .Chapter 10 Understanding Service Parameters Cisco Database Layer Service Parameters Table 10-4 Cisco IP Voice Media Streaming Service Parameters ParamName CFB:OrphanStreamTimeout Values Default: 300 Description Specifies time (number of seconds) for orphaned CFB calls to stay up when a Cisco CallManager goes down. Related Topics • • • • • Configuring Service Parameters. Some changes to service parameters may cause system failure. Table 10-5 provides service parameter configured for the Database Layer. page 34-1 Planning Your MTP Configuration. page 35-1 Configuring Media Termination Point. Do not change this parameter.

page 35-1 Most Commonly Changed CMI Service Parameters. Cisco CallManager Administration Guide 10-30 OL-1047-01 . Refer to the “Configuring Trace” section on page 36-1 for descriptive and configuration information on all trace parameters. Related Topics • • • • • Configuring Service Parameters. If the CDR tables get too full (the number of records reaches this maximum number). Table 10-6 provides service parameters configured for Cisco Telephony Call Dispatcher. page 36-1 Configuring Cisco CallManager. Some changes to service parameters may cause system failure. the oldest records are deleted and a message is sent to the Event log. page 13-1 Cisco Telephony Call Dispatcher Service Parameters Caution Do not add or delete service parameters unless directed to do so by the Cisco Technical Assistance Center (TAC). page 12-1 Configuring Cisco CallManager Groups. This check occurs once a day. page 30-2 Configuring Trace.Chapter 10 Cisco Telephony Call Dispatcher Service Parameters Understanding Service Parameters Table 10-5 Cisco Database Layer Service Parameter ParamName MaxCdrRecords Values Description Specifies the maximum number of CDR records to keep.

page 35-1 Configuring Cisco CallManager. Related Topics • • Configuring Service Parameters. page 12-1 Cisco CallManager Administration Guide OL-1047-01 10-31 .Chapter 10 Understanding Service Parameters Cisco Telephony Call Dispatcher Service Parameters Table 10-6 Cisco Telephony Call Dispatcher Parameters ParamName CCN Line State Port Values Default: 3223 Description Designates the port number of the TCP/IP port in Cisco CallManager that is used by the line state server to register and receive line and device information. Default: 3221 Designates the TCP port where WA clients register with TcdSrv for Line and Device state information. TCDServ Listen Port Default: 4321 Refer to the “Configuring Trace” section on page 36-1 for descriptive and configuration information on all trace parameters. Designates the TCP port where WA clients register with TcdSrv for Call Control. LSS Access Password LSS Listen Port Default: private Designates the default password used at registration to authenticate line state server.

Chapter 10 Cisco Telephony Call Dispatcher Service Parameters Understanding Service Parameters Cisco CallManager Administration Guide 10-32 OL-1047-01 .

“Configuring Device Pools” • Chapter 18. “Configuring Locations” • Chapter 20. “Configuring Date/Time Groups” • Chapter 15. “Configuring Cisco CallManager” • Chapter 13. “Server” • Chapter 12. “Configuring Cisco CallManager Groups” • Chapter 14. “Setting Device Defaults” • Chapter 16. “Configuring Regions” • Chapter 17.P A R T 2 System Configuration The following chapters explain how to configure the system parameters used by Cisco CallManager: • Chapter 11. “Starting and Stopping Cisco CallManager” . “Understanding Enterprise Parameters” • Chapter 19.

.

If your network uses Domain Name System (DNS) services. page 11-3 Deleting a Server. or delete a server address in the Cisco CallManager database: • • • Adding a Server.C H A P T E R 11 Server Use server configuration to specify the address of the server where Cisco CallManager is installed. page 11-4 Cisco CallManager Administration Guide OL-1047-01 11-1 . Note You must update the DNS server with the appropriate Cisco CallManager name and address information before using that information to configure the Cisco CallManager server. you must specify the Internet Protocol (IP) address of the server. Use the following procedures to add. you can specify the DNS name of the server. page 11-2 Updating a Server. update. If your network does not use DNS services.

you can omit the MAC address. Cisco recommends that you enter the MAC address so that other devices on the network can always identify the server. If you do not plan to relocate the server. Select System > Server. Step 4 Optionally you can enter the Media Access Control (MAC) address of the Network Interface Card (NIC) in the Cisco CallManager server. If you plan to move the server periodically to different locations on the network. If your network uses DNS services. Step 5 Cisco CallManager Administration Guide 11-2 OL-1047-01 . you can configure other properties of the Cisco CallManager installed on that server. Note You must update the DNS server with the appropriate Cisco CallManager name and address information before using that information here. you can enter the DNS name of the Cisco CallManager server. Otherwise. you must enter the full IP address of the server. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Click Insert to save the server information in the database. Changes to the server configuration do not take effect until you restart Cisco CallManager.Chapter 11 Adding a Server Server Adding a Server This section describes how to add a server address to the Cisco CallManager database. After adding a server. The MAC address is the permanent hardware address of the NIC. Note Server information is configured automatically in the database when you install the Cisco CallManager software.

Changes to the server configuration do not take effect until you restart Cisco CallManager. Click Update to save the changes in the database. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Select System > Server. select the server you want to update. From the server list. page 12-1 Starting and Stopping Cisco CallManager. page 20-1 Cisco CallManager Administration Guide OL-1047-01 11-3 . page 20-1 Updating a Server This section describes how to update server information in the Cisco CallManager database. Make the desired changes in the fields you want to update. you can click Cancel to reset all fields to their original value.Chapter 11 Server Updating a Server Related Topics • • Adding a Cisco CallManager. Before saving the changes. Related Topics • Starting and Stopping Cisco CallManager.

Cisco CallManager displays an error message. See the “Deleting a Cisco CallManager” section on page 12-6. page 20-1 Cisco CallManager Administration Guide 11-4 OL-1047-01 . Select System > Region. select the server you want to delete. In the server list. Delete the Cisco CallManager assigned to the server you want to delete. Click Delete. If the server is not in use. you must perform either or both of the following tasks: • • Update the Cisco CallManager in question and assign it to a different server. See the “Updating a Cisco CallManager” section on page 12-5. Changes to the server configuration do not take effect until you restart Cisco CallManager. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Before You Begin You cannot delete a server that has a specific Cisco CallManager running on it. If you try to delete a server that is in use.Chapter 11 Deleting a Server Server Deleting a Server This section describes how to delete a server from the Cisco CallManager database. If it is in use. it is deleted. an error message is displayed. Before deleting a server that is currently in use. Related Topics • Starting and Stopping Cisco CallManager.

page 12-6 Adding a Cisco CallManager This section describes how to add a new Cisco CallManager to the database. See the “Updating a Cisco CallManager” section on page 12-5. A cluster is a set of Cisco CallManagers that share the same database. Use the following procedures to add. update. page 12-5 Deleting a Cisco CallManager. page 12-1 Updating a Cisco CallManager. After installing the software. Cisco CallManager Administration Guide OL-1047-01 12-1 .C H A P T E R 12 Configuring Cisco CallManager Use Cisco CallManager configuration to specify the ports and other properties for each Cisco CallManager installed in the same cluster. or delete a Cisco CallManager configuration: • • • Adding a Cisco CallManager. but you might want to update the configuration information for an existing Cisco CallManager. you normally do not have to add a new Cisco CallManager configuration to the database. Note Information about Cisco CallManager is configured automatically in the database when you install the Cisco CallManager software.

Note Each Cisco CallManager server address can be assigned only once (that is. enter the name you want to assign to this Cisco CallManager. enter a brief text description for this Cisco CallManager. that address disappears from the list. click Copy. There are two ways to add a Cisco CallManager: • If there is an existing Cisco CallManager with settings that are similar to the one you want to add. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. continue with Step 4. select the IP address or DNS name of the server where this Cisco CallManager is installed. See “Adding a Partition”. See the “Adding a Server” section on page 11-2. perform the following tasks: • • Configure the address of the server where this Cisco CallManager is installed. Select System > Cisco CallManager. Cisco CallManager Administration Guide 12-2 OL-1047-01 . select the existing Cisco CallManager to display its settings. then continue with the Step 4 and modify the settings as needed. To add a Cisco CallManager without copying an existing one. Step 5 Step 6 In the Cisco CallManager Name field. there can be only one Cisco CallManager per server).Chapter 12 Adding a Cisco CallManager Configuring Cisco CallManager Before You Begin Before adding a new Cisco CallManager to the database. After you assign a server address to a particular Cisco CallManager. • Step 4 From the Cisco CallManager Server drop-down list box. In the Description field. If you want to specify a partition for directory numbers used in auto-registration with this Cisco CallManager. configure that partition.

You must select a range for auto-registration before you can select a partition and external phone number mask. If you specify a valid range of directory numbers in the Starting Directory Number and Ending Directory Number fields. then that literal number (9728135000) is the caller ID displayed for an external call from any auto-registered device. such as 9728135000 to represent a main attendant number. and use Xs to represent the directory number of the auto-registered device. Cisco CallManager Administration Guide OL-1047-01 12-3 . If you specify a mask of all literal digits. Field Name Starting Directory Number Ending Directory Number Description Enter the first directory number to use for auto-registration of devices. External Phone Number Mask Specify the mask used to format caller ID information for external (outbound) calls made from the auto-registered devices. If you set the starting and ending directory numbers to the same value. For example. Refer to the “Understanding Auto-Registration” section on page 4-1 for more information.Chapter 12 Configuring Cisco CallManager Adding a Cisco CallManager Step 7 Enter the following auto-registration information. Enter the last directory number to use for auto-registration of devices. auto-registration is disabled. Partition Select the partition to which auto-registered directory numbers belong. select None. If you are not using partitions. an external call from extension 1234 displays a caller ID number of 9728131234 if the Use External Phone Number Mask option is checked on the route pattern used to make the external call. The mask can contain up to 50 characters. Enter the literal digits that you want to appear in the caller ID information. auto-registration is automatically enabled. if you specify a mask of 972813XXXX.

Step 8 Enter the following port numbers. All port entries must be unique. Field Name Ethernet Phone Port Description Cisco CallManager uses this TCP port to communicate with the Cisco IP Phones on the network. Digital Port Cisco CallManager Administration Guide 12-4 OL-1047-01 . you must configure the directory numbers manually whenever you add new devices to your network. Cisco CallManager uses this TCP port to communicate with Cisco Access Digital Gateways (such as the DT-24+ or DE-30+) on the network. The range of valid port numbers is 1024 to 49151.Chapter 12 Adding a Cisco CallManager Configuring Cisco CallManager Field Name Auto-registration Disabled on this Cisco CallManager Description Auto-registration is disabled by default to prevent unauthorized connections to the network. Check the Auto-registration Disabled option to disable auto-registration for this Cisco CallManager. The partition and external phone mask information fields are reset when Auto-registration is disabled. When auto-registration is disabled. • • Uncheck the Auto-registration Disabled option to enable auto-registration for this Cisco CallManager. Accept the default port of 2001 unless this port is already in use on your system. All port entries must be unique. Accept the default port of 2000 unless this port is already in use on your system. Setting the Starting Directory Number and Ending Directory Number to the same value also disables auto-registration. The range of valid port numbers is 1024 to 49151. If starting and ending directory numbers are currently specified when you disable auto-registration by checking this option. Cisco CallManager sets the starting and ending directory numbers to the same value.

page 13-2 Updating a Cisco CallManager This section describes how to update a Cisco CallManager configuration. Accept the default port of 2002 unless this port is already in use on your system. All port entries must be unique. Select System > Cisco CallManager. Cisco CallManager uses this TCP port to listen for messages from its associated MGCP gateway. Cisco CallManager uses this TCP port to exchange keep-alive messages with its associated MGCP gateway. Accept the default port of 2427 unless this port is already in use on your system. page 4-1 Adding a Cisco CallManager Group. All port entries must be unique. The range of valid port numbers is 1024 to 49151. MGCP Listen Port MGCP Keep-alive Port Step 9 Click Insert to save the Cisco CallManager configuration in the database. Cisco CallManager Administration Guide OL-1047-01 12-5 .Chapter 12 Configuring Cisco CallManager Updating a Cisco CallManager Field Name Analog Port Description Cisco CallManager uses this TCP port to communicate with Cisco Access Analog Gateways (such as the WS-6624 FXS) on the network. All port entries must be unique. Related Topics • • Understanding Auto-Registration. The range of valid port numbers is 1024 to 49151. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Accept the default port of 2428 unless this port is already in use on your system. The range of valid port numbers is 1024 to 49151.

you can click Cancel to reset all fields to their original value. Before You Begin You cannot delete a Cisco CallManager from the database if it is running. Step 5 Click Update to save the changes in the database. Changes to the settings for auto-registration partition. and TCP ports do not take effect until you restart Cisco CallManager. external phone number mask. you must perform either or both of the following tasks: Cisco CallManager Administration Guide 12-6 OL-1047-01 . If you try to delete a Cisco CallManager that is in use. select the Cisco CallManager you want to update. page 12-1 Deleting a Cisco CallManager. Before deleting a Cisco CallManager that is currently in use. Related Topics • • Adding a Cisco CallManager. Before saving the changes.Chapter 12 Deleting a Cisco CallManager Configuring Cisco CallManager Step 3 Step 4 From the Cisco CallManager list. For other methods of resetting Cisco CallManager. Caution The Reset button resets Cisco CallManager and can temporarily interrupt call processing. an error message displays. Refer to the “Adding a Cisco CallManager” section on page 12-1 for information about configuration settings. Make the desired changes in the fields you want to update. See the “Starting and Stopping Cisco CallManager” section on page 20-1. page 12-6 Deleting a Cisco CallManager This section describes how to delete a Cisco CallManager configuration from the database. see the “Starting and Stopping Cisco CallManager” section on page 20-1.

Select System > Cisco CallManager. select the Cisco CallManager you want to delete. Delete the Cisco CallManager group that contains the Cisco CallManager you want to delete. See the “Deleting a Cisco CallManager” section on page 12-6. • Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. From the Cisco CallManager list. Related Topics • Adding a Cisco CallManager. page 12-1 Cisco CallManager Administration Guide OL-1047-01 12-7 . Click Delete. click either OK to delete or Cancel to cancel the delete operation.Chapter 12 Configuring Cisco CallManager Deleting a Cisco CallManager • Update the Cisco CallManager group so that it no longer contains the Cisco CallManager you want to delete. When asked to confirm the delete operation. See the “Updating a Cisco CallManager Group” section on page 13-4.

Chapter 12 Deleting a Cisco CallManager Configuring Cisco CallManager Cisco CallManager Administration Guide 12-8 OL-1047-01 .

Call processing load balancing—This feature enables you to distribute the control of devices across multiple Cisco CallManagers. Refer to the “Understanding Distributed Call Processing” section on page 2-1. and the other members of the group are used as secondary (backup) Cisco CallManagers.C H A P T E R 13 Configuring Cisco CallManager Groups A Cisco CallManager group is a prioritized list of up to three Cisco CallManagers. Cisco CallManager Administration Guide OL-1047-01 13-1 . When a device registers. Refer to the “Understanding Redundancy” section on page 3-1. The first Cisco CallManager in the list is the primary Cisco CallManager for that group. Cisco CallManager groups provide two important features for your system: • Redundancy—This feature enables you to designate a primary and backup Cisco CallManagers for each group. and so on. it attempts to connect to the primary (first) Cisco CallManager in the group assigned to its device pool. the device tries to connect to the next Cisco CallManager listed in the group. One Cisco CallManager group is assigned to each device pool. If the primary Cisco CallManager is not available. • For most systems you will want to assign a single Cisco CallManager to multiple groups to achieve better load distribution and redundancy.

you must configure the Cisco CallManagers that you want to assign as members of that group. Before You Begin Before configuring a Cisco CallManager group. Select System > Cisco CallManager Group. update. page 13-2 Updating a Cisco CallManager Group. Cisco CallManager Administration Guide 13-2 OL-1047-01 . Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. page 13-5 Deleting a Cisco CallManager Group. Leave this box unchecked if you do not want devices to auto-register with this Cisco CallManager group. or delete a Cisco CallManager group: • • • • Adding a Cisco CallManager Group. Refer to the “Adding a Cisco CallManager” section on page 12-1 for more information. Click the Auto-registration Cisco CallManager Group check box if you want this Cisco CallManager group to be the default Cisco CallManager group when auto-registration is enabled. page 13-6 Adding a Cisco CallManager Group This section describes how to configure a new Cisco CallManager group. You can also create a new Cisco CallManager group by copying an existing one. Refer to “Copying a Cisco CallManager Group” section on page 13-5 for more information. Enter the name of the new group in the Cisco CallManager Group field. page 13-4 Copying a Cisco CallManager Group.Chapter 13 Adding a Cisco CallManager Group Configuring Cisco CallManager Groups Use the following procedures to add.

page 3-1 Adding a Device Pool. The first entry in the list is the primary Cisco CallManager for the group.Chapter 13 Configuring Cisco CallManager Groups Adding a Cisco CallManager Group Note There can be one default auto-registration group per cluster. Related Topics • • • Understanding Distributed Call Processing. Step 5 In the Cisco CallManager selection area. The Selected list can contain up to three Cisco CallManagers. Cisco CallManagers in the Selected list become members of the group when you click Insert. When you select a different Cisco CallManager group as the default group for auto-registration and apply the change. page 17-1 Cisco CallManager Administration Guide OL-1047-01 13-3 . and Cisco CallManagers in the Available list are left out of the group. • Use the left and right arrows to move Cisco CallManager groups from the Available list to the Selected list. See the “Understanding Redundancy” section on page 3-1. the previously selected default auto-registration group for the cluster is automatically deselected. select the Cisco CallManager names and use the arrows to arrange the lists the way you want them. Step 6 Click Insert to save the Cisco CallManager group in the database. page 2-1 Understanding Redundancy. The order of the Cisco CallManagers in the Selected list determines their priority. and the other entries are successive backups. • Use the up and down arrows to arrange the groups in the Selected list in the order that you want.

select the group you want to update. If the currently selected group is the default group for auto-registration. From the Cisco CallManager group list. When you do so. Make the desired changes in the fields you want to update. you can click Cancel to reset all fields to their original value. you can not deselect it by un-checking the Auto-registration Cisco CallManager check box. Before saving the changes. You must restart the devices that use the updated Cisco CallManager group to apply the changes. To restart all the devices that use this Cisco CallManager group. Step 5 Click Update to save the changes in the database. the currently selected default auto-registration group will be automatically deselected. click Restart Devices. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration.Chapter 13 Updating a Cisco CallManager Group Configuring Cisco CallManager Groups Updating a Cisco CallManager Group This section describes how to update an existing Cisco CallManager group. Tips The Restart Devices button restarts all devices in the device pool that uses this Cisco CallManager group. Note To make a group the default Auto-registration Cisco CallManager group. Select System > Cisco CallManager Group. You must first select a different default auto-registration group. check in the Auto-registration Cisco CallManager check box. Refer to the “Adding a Cisco CallManager Group” section on page 13-2 for information about configuration settings. Cisco CallManager Administration Guide 13-4 OL-1047-01 . This button is for your convenience in restarting devices.

Click Insert to apply the changes and add the new Cisco CallManager group to the database. Enter the name of the new group in the Cisco CallManager Group field.Chapter 13 Configuring Cisco CallManager Groups Copying a Cisco CallManager Group Caution Restarting devices can cause them to drop calls. Refer to the “Adding a Cisco CallManager Group” section on page 13-2 for information about configuration settings. You must change the name of the group. Select the name of the group you want to copy from the list on the left side of the page. Click Copy. page 13-6 Copying a Cisco CallManager Group Use the following procedure to add a new Cisco CallManager group by copying settings from an existing group. page 13-2 Deleting a Cisco CallManager Group. Make the desired changes. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Open Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 13-5 . Related Topics • • Adding a Cisco CallManager Group. Select System > Cisco CallManager Group.

Click Delete. page 13-4 Deleting a Cisco CallManager Group. When asked to confirm the delete operation. you must perform some or all of the following tasks: • Assign a different Cisco CallManager group to the device pools that are currently using this Cisco CallManager group. page 13-6 Deleting a Cisco CallManager Group This section describes how to delete a Cisco CallManager group from the database. If you try to delete a Cisco CallManager group that is in use. click either OK to delete or Cancel to cancel the delete operation. Cisco CallManager Administration Guide 13-6 OL-1047-01 . See the “Updating a Device Pool” section on page 17-3. Before You Begin You cannot delete a Cisco CallManager group if it is assigned to any device pools or if it is the current Auto-registration CallManager Group for the cluster.Chapter 13 Deleting a Cisco CallManager Group Configuring Cisco CallManager Groups Related Topics • • • Adding a Cisco CallManager Group. Create or select a different Cisco CallManager group to be the Auto-registration CallManager group. • Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Before deleting a Cisco CallManager group that is currently in use. an error message displays. Select System > Cisco CallManager Group. page 13-2 Updating a Cisco CallManager Group. select the group you want to delete. From the Cisco CallManager group list.

page 13-4 Cisco CallManager Administration Guide OL-1047-01 13-7 . page 13-2 Updating a Cisco CallManager Group.Chapter 13 Configuring Cisco CallManager Groups Deleting a Cisco CallManager Group Related Topics • • Adding a Cisco CallManager Group.

Chapter 13 Deleting a Cisco CallManager Group Configuring Cisco CallManager Groups Cisco CallManager Administration Guide 13-8 OL-1047-01 .

C H A P T E R

14

Configuring Date/Time Groups
Use Date/Time Groups to define time zones for the various devices connected to Cisco CallManager. Each device is a member of only one device pool, and each device pool is assigned only one Date/Time Group. A default Date/Time Group called CMLocal is configured automatically when you install Cisco CallManager. CMLocal is synchronized to the active date and time of the operating system on the server where Cisco CallManager is installed. After installing Cisco CallManager, you can change the settings for CMLocal as desired. Normally, server date/time should be adjusted to the local time zone date and time.

Note

CMLocal resets to the operating system date and time whenever you restart Cisco CallManager or upgrade the Cisco CallManager software to a new release. Do not change the name of CMLocal.

Tips

For a worldwide distribution of Cisco IP Phones, create one named Date/Time Group for each of the 24 time zones. Use the following procedures to add, update, or delete Date/Time Groups:
• • •

Adding a Date/Time Group, page 14-2 Updating a Date/Time Group, page 14-3 Deleting a Date/Time Group, page 14-4

Cisco CallManager Administration Guide OL-1047-01

14-1

Chapter 14 Adding a Date/Time Group

Configuring Date/Time Groups

Adding a Date/Time Group
This section describes how to add a new Date/Time Group to the Cisco CallManager database.
Procedure
Step 1 Step 2 Step 3

Open Cisco CallManager Administration. Select System > Date/Time Group. There are two ways to add a new Date/Time group:

If there is an existing Date/Time Group with settings that are similar to the new group you want to create, select the existing group to display its settings, click Copy, then continue with the Step 4 and modify the settings as needed. To create a new Date/Time Group without copying an existing one, continue with Step 4.

• Step 4 Step 5

In the Date/Time Group Name field, enter the name you want to assign to the new Date/Time Group. From the Time Zone drop-down list box, select the time zone for the group you are adding. The option “local time zone of CallManager” copies the time zone information from the operating system of the server where Cisco CallManager is installed. Select the separator character to use between the date fields from the drop-down list box. From the Date Format drop-down list box, select the date format. This selection sets the format for the date displayed on the Cisco IP Phones. From the Time Format drop-down list box, select 12-hour or 24-hour time. Click Insert to save the new Date/Time Group in the database.

Step 6 Step 7 Step 8 Step 9

Related Topics

After adding a new Date/Time Group to the database, you can assign it to a device pool to configure the date and time information for that device pool. For more information, see:

Adding a Device Pool, page 17-1

Cisco CallManager Administration Guide

14-2

OL-1047-01

Chapter 14

Configuring Date/Time Groups Updating a Date/Time Group

Updating a Date/Time Group
This section describes how to update a Date/Time Group.
Procedure
Step 1 Step 2 Step 3 Step 4

Open Cisco CallManager Administration. Select System > Date/Time Group. From the Date/Time Group list, select the Date/Time Group you want to update. Make the desired changes in the fields you want to update. Refer to the “Adding a Date/Time Group” section on page 14-2 for more information about configuration settings. Before saving the changes, you can click Cancel to reset all fields to their original value. Click Update to save the changes in the database.

Step 5

Tips

The Restart Devices button restarts all devices in the selected Date/Time Group. This button is only for your convenience in restarting devices. You do not have to use it when making changes to a Date/Time Group.

Caution

Restarting devices can cause them to drop calls.

Related Topics
• •

Adding a Date/Time Group, page 14-2 Deleting a Date/Time Group, page 14-4

Cisco CallManager Administration Guide OL-1047-01

14-3

Chapter 14 Deleting a Date/Time Group

Configuring Date/Time Groups

Deleting a Date/Time Group
This section describes how to delete a Date/Time Group from the Cisco CallManager database.
Before You Begin

You cannot delete a Date/Time Group that is used by any device pool. If you try to delete a Date/Time Group that is in use, Cisco CallManager displays an error message. Before deleting a Date/Time Group that is currently in use, you must perform either or both of the following tasks:

Assign a different Date/Time Group to any device pools that are using the Date/Time Group you want to delete. See the “Updating a Device Pool” section on page 17-3. Delete the device pools that are using the Date/Time Group you want to delete. See the “Deleting a Device Pool” section on page 17-4.

Procedure
Step 1 Step 2 Step 3 Step 4 Step 5

Open Cisco CallManager Administration. Select System > Date/Time Group. From the Date/Time Group list, select the Date/Time Group you want to delete. Click Delete. When asked to confirm the delete operation, click either OK to delete or Cancel to cancel the delete operation.

Related Topics
• •

Adding a Date/Time Group, page 14-2 Updating a Date/Time Group, page 14-3

Cisco CallManager Administration Guide

14-4

OL-1047-01

C H A P T E R

15

Setting Device Defaults
Use device defaults to set the system-wide default characteristics of each type of device that registers with a Cisco CallManager. The system-wide device defaults for a device type apply to all devices of that type within a Cisco CallManager cluster. Default settings for devices include:
• • •

Device loads Device pools Phone button templates

When a device registers with a Cisco CallManager, it acquires the system-wide device default settings for its device type. After a device registers, you can update its configuration individually to change the device settings. Device defaults are set automatically when you install Cisco CallManager. You cannot create new device defaults or delete existing ones, but you can change the default settings by using the following procedure:

Updating Device Defaults, page 15-2

Cisco CallManager Administration Guide OL-1047-01

15-1

Chapter 15 Updating Device Defaults

Setting Device Defaults

Updating Device Defaults
This section describes how to modify the device defaults in the Cisco CallManager configuration database.
Before You Begin

Before updating the device defaults, perform any of the following tasks that apply to your system:

Add new firmware files for the devices to the TFTP server. For each available firmware load, there is a .bin file in the \Program Files\Cisco\TFTPPath\ folder on the Cisco CallManager server. For example, for the firmware load P002A030, there is a file named P002A030.bin in the Program Files\Cisco\TFTPPath\folder.

• •

Configure new device pools. See the “Adding a Device Pool” section on page 17-1. If the device is a phone, configure new phone templates. See the “Adding Phone Button Templates” section on page 47-5.

Procedure
Step 1 Step 2 Step 3 Step 4

Open Cisco CallManager Administration. Select System > Device Defaults. From the Cisco CallManager list, select the type of device whose device defaults you want to update. Make the desired changes in the fields you want to update. Before saving the changes, you can click Cancel to reset all fields to their original value.

Cisco CallManager Administration Guide

15-2

OL-1047-01

Chapter 15

Setting Device Defaults Updating Device Defaults

The fields you can update are listed in the following table. Field Name Load Information Description This field specifies the ID number of the firmware load used with a particular type of hardware device. If you install an upgrade or patch load, you must update the load information for each type of device that uses the new load. This field specifies the device pool associated with each type of device. The device pool defines common characteristics for all devices in the pool. This field specifies the phone button template used by each type of Cisco IP Phone. The template defines which keys on the phone perform which functions.

Device Pool

Phone Template

Step 5 Step 6

Click Update to save the changes in the Cisco CallManager configuration database. Click the Reset icon to the left of the device name to reset all the devices of that type and load the new defaults on all Cisco CallManagers in the cluster. If you choose not to reset all devices of that type, only new devices added after you change the device defaults will receive the latest defaults.

Related Topics
• •

Understanding Device Support, page 7-1 Understanding Device Loads, page 7-6

Cisco CallManager Administration Guide OL-1047-01

15-3

Chapter 15 Updating Device Defaults

Setting Device Defaults

Cisco CallManager Administration Guide

15-4

OL-1047-01

C H A P T E R

16

Configuring Regions
Use regions to specify the type of compression and amount of bandwidth used per call. You can select the compression and bandwidth used for calls within a region and between two regions. Use the following procedures to add, update, or delete regions:
• • •

Adding a Region, page 16-3 Updating a Region, page 16-4 Deleting a Region, page 16-5

Understanding Regions
The compression types available in Cisco CallManager are G.711, G.723, and G.729. The default compression type for all calls through Cisco CallManager is G.711. To specify a different compression type, you must use regions. The bandwidth used per call depends on the compression type as well as factors such as data packet size and overhead (packet header size), as indicated in Table 16-1.

Cisco CallManager Administration Guide OL-1047-01

16-1

Chapter 16 Understanding Regions

Configuring Regions

Table 16-1 Bandwidth Used Per Call by Each Type of Compression

Type of Compression G.711 G.723 G.729

Bandwidth Used for Data Packets Only (Fixed Regardless of Packet Size) 64 kbps 6 kbps 8 kbps

Bandwidth Used Per Call (Including IP Headers) with 30 ms Data Packets 80 kbps 22 kbps 24 kbps

Bandwidth Used Per Call (Including IP Headers) with 20 ms Data Packets 88 kbps Not applicable 32 kbps

Figure 16-1 illustrates the use of regions to specify compression type and bandwidth.
Figure 16-1 Example of Regions

Internal: G.711 Each call uses about 80 kbps

G.723 Compression Each call uses about 22 kbps

Internal: G.723 Each call uses about 22 kbps

Region A
on si es pr es om l us ps C l b ca 2 k 23 .7 ch t 2 G Ea bou a G .7 11 Ea Co m ab ch pr ou c es t 8 all si o 0 us kb es n ps

Region B

Region C

Internal: G.723 Each call uses about 22 kbps
34036

Cisco CallManager Administration Guide

16-2

OL-1047-01

Chapter 16

Configuring Regions Adding a Region

The following matrix shows the compression type that will be used for calls within and between Regions A, B, and C for the example configuration shown in Figure 16-1. Region A Region A Region B Region C G.711 G.723 G.723 Region B G.723 G.723 G.711 Region C G.723 G.711 G.723

Adding a Region
This section describes how to add a new region to the Cisco CallManager database.
Procedure
Step 1 Step 2 Step 3 Step 4

Open Cisco CallManager Administration. Select System > Region. In the Region Name box, enter the name you want to assign to the new region and click Insert. Using the drop-down list boxes, select the type of compression to use for calls within the new region and between the new region and existing regions. By selecting the compression type, you are also specifying the amount of bandwidth used per call. See Table 16-1 for details. Before saving the changes, you can click Cancel to reset all fields to their original value.

Step 5

Click Update to save the new region in the database. After adding a new region to the database, you can use it to configure device pools.

Cisco CallManager Administration Guide OL-1047-01

16-3

Chapter 16 Updating a Region

Configuring Regions

Related Topics
• •

Adding a Device Pool, page 17-1 Understanding Regions, page 16-1

Updating a Region
This section describes how to update the configuration for a region.
Procedure
Step 1 Step 2 Step 3 Step 4 Step 5

Open Cisco CallManager Administration. Select System > Region. From the region list, select the region you want to update. Make the desired changes in the fields you want to update. Before saving the changes, you can click Cancel to reset all fields to their original value. Click Update to save the changes in the database.

Related Topics
• • •

Understanding Regions, page 16-1 Adding a Region, page 16-3 Deleting a Region, page 16-5

Cisco CallManager Administration Guide

16-4

OL-1047-01

Before You Begin You cannot delete a region that is being used by any device pools. page 16-3 Updating a Region. you must perform either or both of the following tasks: • • Update the device pools to use a different region. select the region you want to delete. page 16-1 Adding a Region. See the “Deleting a Device Pool” section on page 17-4. Cisco CallManager displays an error message.Chapter 16 Configuring Regions Deleting a Region Deleting a Region This section describes how to delete a region from the Cisco CallManager database. Related Topics • • • Understanding Regions. Select System > Region. page 16-4 Cisco CallManager Administration Guide OL-1047-01 16-5 . See the “Updating a Device Pool” section on page 17-3. Before deleting a region that is currently in use. If you try to delete a region that is in use. Delete the device pools that are using the region you want to delete. Click Delete. From the region list. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration.

Chapter 16 Deleting a Region Configuring Regions Cisco CallManager Administration Guide 16-6 OL-1047-01 .

page 17-3 Deleting a Device Pool. or delete a device pool: • • • Adding a Device Pool. Cisco CallManager Administration Guide OL-1047-01 17-1 . page 17-4 Adding a Device Pool This section describes how to add a new device pool to the Cisco CallManager database. The device characteristics you can specify for a device pool are: • • • • Region Date/time group Cisco CallManager group Calling search space for auto-registration Use the following procedures to add. page 17-1 Updating a Device Pool. update.C H A P T E R 17 Configuring Device Pools Use device pools to define sets of common characteristics for devices.

Date/time group (required). See the “Adding a Cisco CallManager Group” section on page 13-2. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. select the date/time group to assign to devices in this device pool. continue with Step 4. select the Cisco CallManager group to assign to devices in this device pool.Chapter 17 Adding a Device Pool Configuring Device Pools Before You Begin Before configuring a device pool. In the Region drop-down list box. Calling search space for auto-registration (optional). enter the name of the new device pool you are creating. Regions specify the type of compression used. • Step 4 Step 5 Step 6 In the Device Pool Name field. In the Cisco CallManager Group drop-down list box. See the “Adding a Date/Time Group” section on page 14-2. then continue with Step 4 to modify settings as needed. The Cisco CallManager group specifies the primary and backup Cisco CallManagers for the group. Select System > Device Pool. Cisco CallManager group (required). To create a device pool without copying an existing one. There are two ways to add a new device pool: • If there is an existing device pool with settings that are similar to the new device pool you want to configure. Step 7 Cisco CallManager Administration Guide 17-2 OL-1047-01 . select the existing device pool to display its settings. select the region to assign to devices in this device pool. click Copy. you must configure the following items if you want to select them for the device pool: • • • • Region (required). See the “Adding a Calling Search Space” section on page 22-1. The date/time group specifies the time zone and the display formats for date and time. See the “Adding a Region” section on page 16-3. In the Date/Time Group drop-down list box.

CTI route points. click Restart Devices. Cisco CallManager Administration Guide OL-1047-01 17-3 . media termination points. Select System > Device Pool. This button is for your convenience in restarting devices. click the device pool you want to update. select the calling search space to assign to devices in this device pool that auto-register with Cisco CallManager. Click Insert to save the device pool information in the database. you can use it to configure devices such as Cisco IP Phones. transcoders. conference bridges. Related Topics • Setting Device Defaults. gateways. you can click Cancel to reset all fields to their original value. You must restart the devices to apply the changes. In the device pool list. and so on. Cisco uOne ports. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Click Update to save the changes in the database. page 15-1 Updating a Device Pool This section describes how to modify the configuration of an existing device pool. The calling search space specifies which partitions devices can search when attempting to complete a call.Chapter 17 Configuring Device Pools Updating a Device Pool Step 8 In the drop-down list box for Calling Search Space for Auto-Registration. To restart all the devices in the selected device pool. Refer to the “Adding a Device Pool” section on page 17-1 for information about configuration settings Before saving the changes. Make the desired changes in the fields you want to update. Step 5 Step 6 Tips The Restart Devices button restarts all devices in the selected device pool. Step 9 After adding a new device pool to the database.

See the “Deleting a Phone” section on page 46-11. click the device pool you want to delete. you must perform either or both of the following tasks: • • Update the devices to assign them to a different device pool. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Deleting a Device Pool This section describes how to delete a device pool from the Cisco CallManager database.Chapter 17 Deleting a Device Pool Configuring Device Pools Caution Restarting devices can cause them to drop calls. See the “Updating a Phone” section on page 46-13. Before You Begin You cannot delete a device pool that has been assigned to any devices or one that is used for Device Defaults configuration. When asked to confirm the delete operation. If you try to delete a device pool that is in use. click either OK to delete or Cancel to cancel the delete operation. an error message is displayed. Select System > Device Pool. Click Delete. Before deleting a device pool that is currently in use. Delete the devices assigned to the device pool you want to delete. In the device pool list. Cisco CallManager Administration Guide 17-4 OL-1047-01 .

) When you install a new Cisco CallManager.C H A P T E R 18 Understanding Enterprise Parameters Enterprise parameters provide default settings that apply to all devices and services in the same cluster. (A cluster is a set of Cisco CallManagers that share the same database. For more information on device defaults. and Media Termination Points Lightweight Directory Access Protocol (LDAP) parameters URLs for web-based applications such as directory services for the Cisco IP Phone 7960 System Version MessageDirectoryNumber You cannot add or delete enterprise parameters. gateways. page 18-4 Cisco CallManager Administration Guide OL-1047-01 18-1 . but you can use the following procedure to update existing enterprise parameters: • Updating Enterprise Parameters. Enterprise parameters include the following default settings: • • • • • Firmware loads for devices such as phones. see the “Setting Device Defaults” section on page 15-1. it uses the enterprise parameters to set the initial values of its device defaults.

The password of the directory manager. The type of the LDAP directory. The directory number of the directory manager. The RN attribute used to create new Do not change this parameter setting unless instructed to do so entries in the user portion of the LDAP directory.Chapter 18 Understanding Enterprise Parameters Table 18-1 describes the enterprise parameters and lists allowed values for each. Cisco CallManager Administration Guide 18-2 OL-1047-01 . Table 18-1 Enterprise Parameters Enterprise Parameter FirmwareLoad Description The firmware loads used as Device Defaults when a new Cisco CallManager is added to a cluster. Do not change this parameter setting unless instructed to do so by Cisco TAC. setting unless instructed to do so by Cisco TAC. setting unless instructed to do so by Cisco TAC. Allowed Values Do not change the firmware load settings unless instructed to do so by Cisco Technical Assistance Center (TAC). DC Directory or Netscape LDAP: Directory Type LDAP: Extension Base LDAP: Manager DN LDAP: Manager Password The location of the list of extensions Do not change this parameter in the LDAP directory tree. The LDAP attribute used to authenticate users who log into their user speed dial and call forwarding pages. Any valid directory number that is not assigned to another use. A mapping of attribute names used in the enterprise directory. by Cisco TAC. LDAP: Attribute Mappings LDAP: Cisco Base LDAP: Device Base LDAP: Directory RN Attribute LDAP: User ID The location of Cisco information in Do not change this parameter the LDAP directory. setting unless instructed to do so by Cisco TAC. The location of devices in the LDAP Do not change this parameter directory tree.

This parameter should never be changed. directory. The URL used for the information (i) button on the Cisco IP Phone 7960. This parameter is the same as the installation version number. The URL of the LDAP directory. The object class hierarchy of the User Object Class. If the installation is to an enterprise directory. LDAP://DAL-CCM1:8404). LDAP: User Base LDAP: User Object Class LDAP: User Object Class Hierarchy MessageDirectoryNumber The location of the user subtree in the LDAP directory tree. Note that the port number will always be 8404 for DC Directory installations.Chapter 18 Understanding Enterprise Parameters Table 18-1 Enterprise Parameters (continued) Enterprise Parameter LDAP: Profile Base LDAP: URL Description Allowed Values The location of the profile subtree in Do not change this parameter the LDAP directory tree. The Cisco CallManager system version. Do not change this parameter setting unless instructed to do so by Cisco TAC. The URL used for the directories key on the Cisco IP Phone 7960. Do not change this parameter setting unless instructed to do so by Cisco TAC. Default voice messaging directory number used by the Cisco Messaging Interface (CMI). this subtree can be anywhere. setting unless instructed to do so by Cisco TAC. The name of the object class used to Do not change this parameter setting unless instructed to do so create new users in the LDAP by Cisco TAC. Any valid directory number that is not assigned to another use. A URL in standard format (for example. Do not change this setting unless you moved the enterprise directory to a new location or changed ports. Do not change this parameter setting unless instructed to do so by Cisco TAC System Version URL Directories URL Information Cisco CallManager Administration Guide OL-1047-01 18-3 .

Chapter 18 Updating Enterprise Parameters Understanding Enterprise Parameters Table 18-1 Enterprise Parameters (continued) Enterprise Parameter URL Messages Description Allowed Values The URL used for the messages key Do not change this parameter on the Cisco IP Phone 7960. If you make an error. click Update to save the changes in the database. Select System > Enterprise Parameters. select the enterprise parameter you want to update. page 2-1 Updating Enterprise Parameters This section describes how to update or modify the enterprise parameters. Do not change this parameter setting unless instructed to do so by Cisco TAC URL Services Related Topics • Clusters. When you are done making changes to the enterprise parameters. retype the entry before saving the changes. See Table 18-1 for allowed values. From the Parameters list. Enter the new value for the selected parameter. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. setting unless instructed to do so by Cisco TAC The URL used for the services key on the Cisco IP Phone 7960. Cisco CallManager Administration Guide 18-4 OL-1047-01 .

Call admission control enables you to regulate voice quality by limiting the amount of bandwidth available for calls over links between the locations. Figure 19-1 illustrates the hub-and-spoke topology and its use with Cisco CallManager admission control. see the “Understanding Call Admission Control” section on page 5-1. Cisco CallManager requires that you arrange the locations in a hub-and-spoke topology (also know as a star topology). Cisco CallManager Administration Guide OL-1047-01 19-1 . an unlimited number of calls can be active on that link at the same time.C H A P T E R 19 Configuring Locations Use locations to implement call admission control in a centralized call processing system. The spokes are remote locations that contain other devices (such as phones and gateways) on the same network. The hub is the location of the primary Cisco CallManager that controls call processing on the network. This can cause the voice quality of each call to degrade as the link becomes oversubscribed. Note If you do not use call admission control to limit the voice bandwidth on an IP WAN link. For more information.

page 19-7 Deleting a Location. You can also specify how much bandwidth to allocate for calls between each spoke location and the hub. page 19-2 Adding a Location. The main location. However. you can use the locations feature to decrease the amount of available bandwidth and thereby decrease the number of active calls on the link. Cisco CallManager uses a hub-and-spoke topology for locations. Cisco CallManager Administration Guide 19-2 OL-1047-01 47072 . and call admission control does not apply. As more active calls are placed over the WAN link. the audio quality of each call can begin to degrade. the available bandwidth is considered to be unlimited. To avoid this audio quality degradation. calls between locations travel over a WAN link that has limited available bandwidth. Using Cisco CallManager Administration. is the location of the primary Cisco CallManager controlling the network. or hub.Chapter 19 Understanding Locations Configuring Locations Figure 19-1 Example of Hub-and-Spoke Topology for Locations Central site IP IP WAN V IP Branch 1 V IP Branch 2 V IP V V IP Branch 3 IP Branch n The following sections explain locations in more detail: • • • • Understanding Locations. page 19-7 Understanding Locations For calls between devices on the same LAN. you can define the spoke locations and assign devices to those locations. page 19-5 Updating a Location.

the calling party receives a reorder tone and a text message on the phone’s display. For more information. the link to the Austin location could support one G.711 calls at 80 kbps each. depending on how you define them. Thus. You must assign each device on the network to both a region (by means of a device pool) and a location. Any additional calls that try to exceed the bandwidth limit are rejected. Regions define the type of compression (G.723 or G. As illustrated in Figure 19-2.711 call and one G. and locations define the amount of available bandwidth for the link. or one G. assume that the locations in Figure 19-1 are configured as follows: Location Hub Austin Dallas Bandwidth to Hub (kbps) Unlimited 100 200 For calculation purposes.723. see the “Configuring Regions” section on page 16-1. or G.Chapter 19 Configuring Locations Understanding Locations For example.723 (or G.729) call.723 or G. four G.729) used on the link. the regions and locations can overlap and intersect in various ways. assume that calls using G.729 calls at 24 kbps each.729 compression consume 24 kbps.711. Locations and Regions Locations work in conjunction with regions to define the characteristics of a network link. Cisco CallManager continues to admit new calls to a link until the available bandwidth for that link drops to zero. Cisco CallManager Administration Guide OL-1047-01 19-3 .711 compression consume 80 kbps of bandwidth and calls using G. G.

Cisco CallManager also assumes that calls using G. Note Actual bandwidth consumption per call will vary. depending on factors such as data packet size.323 Gateway PSTN 34030 Bandwidth Calculations In performing bandwidth calculations for purposes of admission control.711 protocol consume 80 kbps. Cisco CallManager uses the values of 24 kbps and 80 kbps to simplify the bandwidth calculations for purposes of call admission control only.729 protocol consume 24 kbps of bandwidth and calls using G.723 or G. Cisco CallManager Administration Guide 19-4 OL-1047-01 .323 Gateway Cisco Voicemail Region A Region B Cisco CallManager (Primary) San Francisco (Hub location) Cisco CallManager (Backup) Cisco CallManager (Backup) Region C Austin (Spoke location) Dallas (Spoke location) H.Chapter 19 Understanding Locations Configuring Locations Figure 19-2 Interaction Between Locations and Regions San Francisco (Hub location) PSTN H. Cisco CallManager assumes that all calls are full-duplex connections.

At that point. the user can still retrieve the held call even though it exceeds the available bandwidth limit. For example. Calls placed simultaneously on the same link can exceed the available bandwidth limit because their bandwidth is not subtracted from the available limit until the calls complete. see • Adding a Cisco CallManager. If new calls consume all the available bandwidth while the original call is on hold. Before You Begin Before configuring a location. an emergency 911 call can be blocked if you route it to a link that has no more available bandwidth. page 12-1 Cisco CallManager Administration Guide OL-1047-01 19-5 . the bandwidth from that call becomes available again. The following situations are exceptions to the bandwidth rules outlined in the preceding paragraph. when a user places a call on hold. • Caution In the United States and Canada. any additional calls fail and the calling party receives reorder tone.Chapter 19 Configuring Locations Adding a Location Cisco CallManager allows calls to complete over a link until the available bandwidth for that link drops to zero. always route 911 calls to the local Public Switched Telephone Network (PSTN) through a local VoIP gateway. the bandwidth from that call is temporarily available for use on another call. If a feature temporarily stops call streaming. In these cases. additional calls can complete even though the available bandwidth has dropped to zero: • • Calls made through a Media Termination Point (MTP) can complete even if they exceed the available bandwidth limit. For each location on your network. you must configure the primary Cisco CallManager that controls the location. Adding a Location This section describes how to add a new location to the Cisco CallManager database. For details.

you can use it to configure a Cisco IP Phone. enter the name of the new location you are creating. In the Location Name field. Step 4 Step 5 Note To improve voice quality. page 45-1 Configuring Cisco IP Phones in Cisco CallManager. page 46-1 Cisco CallManager Administration Guide 19-6 OL-1047-01 . click Copy. Select System > Location. If you want to use a copy of the existing location to configure the new one. an H. lower the bandwidth setting so that fewer active calls are allowed on the link to this location. page 16-1 After adding a new location to the database.Chapter 19 Adding a Location Configuring Locations Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. In the bandwidth field. If you enter a value of zero. this allocates infinite bandwidth and allows an unlimited number of calls on the link. If there is an existing location with settings that are similar to the new location you want to configure. or other devices: • • Configuring Gateways.711 call uses 80 kbps of bandwidth and each G. The hub is the location of the primary Cisco CallManager that controls call processing for your network. Related Topics • • Understanding Call Admission Control. Step 6 Click Insert to save the location information in the database. For purposes of these bandwidth calculations only.323 gateway. select the existing location to display its settings.723 or G. page 5-1 Configuring Regions. assume that each G. enter the maximum amount of voice bandwidth (in kbps) available for all calls on the link between this location and the hub.729 call uses 24 kbps.

Cisco CallManager displays an error message. Before deleting a location that is currently in use. and it can cause the voice quality to degrade.Chapter 19 Configuring Locations Updating a Location Updating a Location This section describes how to modify the configuration of a location. This allows an unlimited number of calls on those links. Click Update to save the changes in the database. Note Deleting a location is equivalent to setting the bandwidth to zero for the links connected to that location. Make the desired changes in the fields you want to update. Before You Begin You cannot delete a location that has any devices assigned to it. Select System > Location. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Deleting a Location This section describes how to delete a location from the Cisco CallManager database. Cisco CallManager Administration Guide OL-1047-01 19-7 . From the location list. you can click Cancel to reset all fields to their original value. If you try to delete a location that is in use. Before saving the changes. Delete the devices assigned to the location you want to delete. select the location you want to update. you must perform either or both of the following tasks: • • Update the devices to assign them to a different location.

select the location you want to delete. Click Delete. Select System > Location. click either OK to delete or Cancel to cancel the delete operation. When asked to confirm the delete operation.Chapter 19 Deleting a Location Configuring Locations Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. From the location list. Cisco CallManager Administration Guide 19-8 OL-1047-01 .

There are three methods for starting and stopping a Cisco CallManager server: • • • Using the Control Center in Cisco CallManager Administration. calls in progress from an IP phone to an MGCP gateway will also stay up. and any other type of calls will be dropped. See the “Using Windows Services” section on page 20-3. Using the Reset button in Cisco CallManager Administration.C H A P T E R 20 Starting and Stopping Cisco CallManager This chapter describes how to start and stop the Cisco CallManager server. calls from an IP phone to another IP phone will stay up. See the “Understanding Redundancy” section on page 3-1. When a Cisco CallManager is stopped. Table 20-1 lists the system parameters that require you to restart Cisco CallManager after changing their settings. refer to the “Starting and Stopping Services Using the Control Center” section on page 38-1. For information about starting and stopping other Cisco CallManager services. Cisco CallManager Administration Guide OL-1047-01 20-1 . See the “Using the Cisco CallManager Reset Button” section on page 20-4. See the “Using the Control Center” section on page 20-2. Using the Windows Control Panel for Services. Caution Stopping Cisco CallManager also stops call processing for all devices controlled by that Cisco CallManager.

select the Cisco CallManager server you want to stop or start. In the Service Status field.Chapter 20 Using the Control Center Starting and Stopping Cisco CallManager Table 20-1 Parameter Settings that Require Restarting Cisco CallManager System Parameter IP address of the Cisco CallManager server Partition for auto-registration External phone number mask for auto-registration TCP port settings for the Cisco CallManager server Path to this Parameter in Cisco CallManager Administration System > Server System > Cisco CallManager System > Cisco CallManager System > Cisco CallManager Tips In general. and restart Cisco CallManager only once after completing the changes. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. From the server list. Using the Control Center This section describes how to use the Control Center in Cisco CallManager Administration to start or stop Cisco CallManager. a square symbol indicates that the service is stopped and a triangle indicates that the service is running. it is better to make as many configuration changes as possible at one time. Cisco CallManager Administration Guide 20-2 OL-1047-01 . Select Service > Control Center. Click Start or Stop for the Cisco CallManager service you want to start or stop.

open the Windows Control Panel for Services. Caution Make sure you are accessing the correct Cisco CallManager server before attempting to start or stop Cisco CallManager. depending on the action you want to perform. Procedure Step 1 On the server that contains the Cisco CallManager you want to start or stop. Click Start or Stop. Step 2 Step 3 Cisco CallManager Administration Guide OL-1047-01 20-3 .Chapter 20 Starting and Stopping Cisco CallManager Using Windows Services Using Windows Services This section describes how to use the Windows Control Panel to start or stop Cisco CallManager. Select the Cisco CallManager service you want to start or stop.

Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Cisco CallManager Administration Guide 20-4 OL-1047-01 . click Reset. Click the button only once to perform a complete reset.Chapter 20 Using the Cisco CallManager Reset Button Starting and Stopping Cisco CallManager Using the Cisco CallManager Reset Button This section describes how to use the Reset button to stop and start Cisco CallManager. select on the one you want to reset. After selecting the appropriate Cisco CallManager. Select System > Cisco CallManager. Note Clicking the Reset button stops Cisco CallManager momentarily and then starts it again. From the list of Cisco CallManagers. and give Cisco CallManager sufficient time to restart.

“Using the External Route Plan Wizard” • Chapter 29. “Configuring Translation Patterns” • Chapter 28. “Configuring Route Groups” • Chapter 25. “Configuring Calling Search Spaces” • Chapter 23. “Configuring Route Filters” • Chapter 24. “Configuring Route Lists” • Chapter 26. “Configuring Partitions” • Chapter 22. “Configuring Route Patterns” • Chapter 27. “Using Route Plan Report” .P A R T 3 Route Configuration The following chapters include information about configuring route plans in Cisco CallManager: • Chapter 21.

.

and can contain any combination of spaces. page 21-1 Deleting a Partition.). page 21-2 Adding a Partition The following procedure describes how to add a partition. Enter a name in the Partition Name field. and call type. hyphens (-). location. Each partition name must be unique to the route plan. Use the following procedures to add or delete route partitions: • • Adding a Partition. Select Route Plan > Partition in the menu bar. and underscore characters (_). Cisco CallManager Administration Guide OL-1047-01 21-1 . periods (. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration.C H A P T E R 21 Configuring Partitions A partition is a list of route patterns. Partitions facilitate call routing by dividing the route plan into logical subsets based on organization. The name can consist of up to 50 alphanumeric characters.

click New and repeat Steps 3 through 5. The description can consist of up to 50 alphanumeric characters. For example. and underscore characters (_). the partition name is automatically entered in this field. and the message “Status: Insert completed” is displayed. periods (. The new partition name is added to the partition list on the left side of the page. The CompanynameLocationCalltype format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a partition. Click Insert to add the new partition. and can contain any combination of spaces. CiscoDallasMetroPT identifies a partition for toll free inter-LATA (Local Access and Transport Area) calls from the Cisco office in Dallas. hyphens (-). Select Route Plan > Partition in the menu bar. To add more partitions. If you do not enter a description. Step 4 Step 5 Step 6 Related Topics • Deleting a Partition. Enter a description in the Description field. Select a name in the partition list on the left side of the page.Chapter 21 Deleting a Partition Configuring Partitions Timesaver Use concise and descriptive names for your partitions. Click Delete to remove the partition. Cisco CallManager Administration Guide 21-2 OL-1047-01 . Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration.). page 21-2 Deleting a Partition The following procedure describes how to delete a partition.

Deleted partitions cannot be recovered. Repeat Steps 3 through 7 to delete other partitions. or click Cancel to cancel the action. Step 5 Step 6 Step 7 Related Topics • Adding a Partition. it must be rebuilt. If you click OK. A dialog box appears warning you that deleting this partition cannot be undone.Chapter 21 Configuring Partitions Deleting a Partition Caution Check carefully to ensure that you are deleting the correct partition before initiating this action. Click OK to delete the partition. If a partition is accidentally deleted. the partition is deleted and the message “Status: Ready” is displayed. page 21-1 Cisco CallManager Administration Guide OL-1047-01 21-3 .

Chapter 21 Deleting a Partition Configuring Partitions Cisco CallManager Administration Guide 21-4 OL-1047-01 .

page 22-3 Copying a Calling Search Space. Calling search spaces determine which partitions calling devices search when attempting to complete a call. hyphens (-). The name can consist of up to 50 alphanumeric characters. Cisco CallManager Administration Guide OL-1047-01 22-1 . update. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. page 22-3 Deleting a Calling Search Space. or delete a calling search space: • • • • Adding a Calling Search Space.C H A P T E R 22 Configuring Calling Search Spaces A calling search space is an ordered list of route partitions. Select Route Plan > Calling Search Space in the menu bar. Enter a name in the Calling Search Space Name field. page 22-4 Adding a Calling Search Space The following procedure describes how to add a calling search space. copy.). Each calling search space name must be unique to the route plan. Use the following procedures to add. page 22-1 Updating a Calling Search Space. periods (. and can contain any combination of spaces. and underscore characters (_).

page 22-3 Copying a Calling Search Space. If you do not enter a description. Enter a description in the Description field. Select partitions in the Available Partitions list box and add them to the Selected Partitions list box by clicking the arrow buttons between the two list boxes. page 22-3 Deleting a Calling Search Space. Step 4 Step 5 Step 6 Step 7 Step 8 Related Topics • • • Updating a Calling Search Space. the calling search space name is automatically entered in this field. Click Insert to add the new calling search space. periods (. Move the partition up or down in the list by clicking the arrows on the right side of the list box. page 22-4 Cisco CallManager Administration Guide 22-2 OL-1047-01 .Chapter 22 Adding a Calling Search Space Configuring Calling Search Spaces Timesaver Use concise and descriptive names for your calling search spaces. hyphens (-). and can contain any combination of spaces. The CompanynameLocationCalltype format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a calling search space. The description can consist of up to 50 alphanumeric characters. To add more calling search spaces. and underscore characters (_). click New and repeat Steps 3 through 7. The new calling search space name is added to the calling search space list on the left side of the page.). and the message “Status: Insert completed” is displayed. To move a partition. For example. select a partition name in the Selected Partitions list box. CiscoDallasMetroCS identifies a calling search space for toll free inter-LATA (Local Access and Transport Area) calls from the Cisco office in Dallas.

or reorder partitions in the Partitions list boxes by using the appropriate arrow buttons. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Click Copy. page 22-3 Deleting a Calling Search Space. Select Route Plan > Calling Search Space in the menu bar. Select a name in the calling search space list on the left side of the page. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. Add. page 22-4 Copying a Calling Search Space The following procedure describes how to copy a calling search space. Select Route Plan > Calling Search Space in the menu bar.Chapter 22 Configuring Calling Search Spaces Updating a Calling Search Space Updating a Calling Search Space The following procedure describes how to update a calling search space. Click Update. Related Topics • • • Adding a Calling Search Space. Select a name in the calling search space list on the left side of the page. Repeat Steps 3 through 5 to update other calling search spaces. page 22-1 Copying a Calling Search Space. remove. Cisco CallManager Administration Guide OL-1047-01 22-3 .

Each calling search space name must be unique to the route plan. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. page 22-4 Deleting a Calling Search Space The following procedure describes how to delete a calling search space.). and underscore characters (_). Cisco CallManager Administration Guide 22-4 OL-1047-01 . hyphens (-). periods (. periods (. Modify the description in the Description field. Step 6 Step 7 Step 8 Step 9 Related Topics • • • Adding a Calling Search Space. page 22-3 Deleting a Calling Search Space.Chapter 22 Deleting a Calling Search Space Configuring Calling Search Spaces Step 5 Modify the name in the Calling Search Space Name field. and underscore characters (_). Select a name in the calling search space list on the left side of the page. Click Insert to add the calling search space. repeat Steps 3 through 8. Note You cannot delete calling search spaces that are being used by devices or translation patterns. remove. To copy another calling search space. Select Route Plan > Calling Search Space in the menu bar. Add. and can contain any combination of spaces. hyphens (-). and the message “Status: Insert completed” is displayed. page 22-1 Updating a Calling Search Space. The description can consist of up to 50 alphanumeric characters. The new calling search space name is added to the calling search space list on the left side of the page. The name can consist of up to 50 alphanumeric characters. and can contain any combination of spaces.). or reorder partitions in the Partitions list boxes by using the appropriate arrow buttons.

page 22-3 Copying a Calling Search Space. Deleted calling search spaces cannot be recovered. it must be rebuilt. Step 5 Related Topics • • • Adding a Calling Search Space. Repeat Steps 3 and 4 to delete other calling search spaces. Caution Check carefully to ensure that you are deleting the correct calling search space before initiating this action. If a calling search space is accidentally deleted. page 22-3 Cisco CallManager Administration Guide OL-1047-01 22-5 . page 22-1 Updating a Calling Search Space.Chapter 22 Configuring Calling Search Spaces Deleting a Calling Search Space Step 4 Click Delete to remove the calling search space. The calling search space is deleted and the message “Status: Delete completed” is displayed.

Chapter 22 Deleting a Calling Search Space Configuring Calling Search Spaces Cisco CallManager Administration Guide 22-6 OL-1047-01 .

Route filters allow you to determine which route patterns your users can dial. whether your users can manually select a long distance carrier (by dialing 101 plus a carrier access code). page 23-7 Adding Route Filter Clauses. page 23-7 Copying a Route Filter. Route filters can only be used with North American Numbering Plan (NANP) route patterns. or delete a route filter: • • • • • • Adding a Route Filter. and then add the route filter to the route pattern. that is. along with route patterns. use dialed-digit strings to determine how a call is handled. update.C H A P T E R 23 Configuring Route Filters Route filters. Tips Always add and define the route filter first. page 23-11 Cisco CallManager Administration Guide OL-1047-01 23-1 . page 23-5 Updating a Route Filter. copy. page 23-9 Removing Route Filter Clauses. for example. route patterns that use an at symbol (@) wildcard. Use the following procedures to add. page 23-10 Deleting a Route Filter.

two-. *. For example. The two-digit access code used for international dialing. the description “The three-digit area code in the form [2-9]XX” means you can enter the actual digits 200 through 999. The one-. Therefore. and SUBSCRIBER (1234) route filter tags. [2-9] represents any single digit in the range 2 through 9. This code is 01 for calls originating in the U. In this notation.S. Route filter tags require operators. #. A single character used to identify the end of the dialed-digit string. ^. ]. The descriptions in Table 23-1 use the notations [2-9] and XXXX to represent actual digits. [. COUNTRY CODE END-OF-DIALING INTERNATIONAL-ACCESS Cisco CallManager Administration Guide 23-2 OL-1047-01 . The values for route filter tag fields can contain the wildcard characters X. the NANP number 972-555-1234 comprises LOCAL-AREA-CODE (972). or any mixture of actual digits and wildcards that results in a pattern with that range. Table 23-1 Route Filter Tags Tag AREA-CODE Description The three-digit area code in the form [2-9]XX. and the numbers 0 through 9.Chapter 23 Understanding Route Filter Tags Configuring Route Filters Understanding Route Filter Tags The tag is the core component of a route filter. This entry identifies the area code for long distance calls. or three-digit code used to specify the destination country for international calls. A tag applies a name to a subset of the dialed-digit string. and can require additional values to decide which calls are filtered. -. and X represents any single digit in the range 0 through 9. OFFICE-CODE (555). The # character is used as the end-of-dialing signal for international numbers dialed within the NANP. or all wildcards.

The one-digit code identifying a direct dialed long distance call. This code is 1 for NANP calls. The one-digit code identifying an operator-assisted international call. This entry identifies the local area code for 10-digit local calls. INTERNATIONAL-OPERATOR LOCAL-AREA-CODE LOCAL-DIRECT-DIAL LOCAL-OPERATOR LONG-DISTANCE-DIRECT-DIAL LONG-DISTANCE-OPERATOR NATIONAL-NUMBER OFFICE-CODE SATELLITE-SERVICE SERVICE Cisco CallManager Administration Guide OL-1047-01 23-3 . This code is 0 for NANP calls. The one-digit code identifying a direct dialed local call. and 411 for information. The nation-specific part of the digit string for an international call. This code is 0 for operator-assisted calls. The one-digit code that provides access to satellite connections for international calls.Chapter 23 Configuring Route Filters Understanding Route Filter Tags Table 23-1 Route Filter Tags (continued) Tag INTERNATIONAL-DIRECT-DIAL Description The one-digit code identifying a direct dialed international call.or two-digit code identifying an operator-assisted long distance call within the NANP.S. or 00 for direct operator access. The first three digits of a seven-digit directory number in the form [2-9]XX. 611 for repair service.S. A three-digit code such as 911 for emergency. This code is 1 for NANP calls. The three-digit local area code in the form [2-9]XX. This code is 1 for calls originating in the U. The one. This code is 0 for calls originating in the U. The one-digit code identifying an operator-assisted local call.

Filter calls when the dialed-digit string associated with this tag is found. TRANSIT-NETWORK-ESCAPE The three-digit value that precedes the long distance carrier identifier. The operator == matches the actual dialed-digits with the specified value or pattern. Do not include the four-digit carrier identification code in the TRANSIT-NETWORK-ESCAPE value. Table 23-2 Route Filter Operators Operator NOT-SELECTED EXISTS Description Do not filter calls based on the dialed-digit string associated with this tag. The value for this field is 101. Refer to TRANSIT-NETWORK for more information.Chapter 23 Understanding Route Filter Tags Configuring Route Filters Table 23-1 Route Filter Tags (continued) Tag SUBSCRIBER TRANSIT-NETWORK Description The last four digits of a seven-digit directory number in the form XXXX. The operators EXISTS and DOES-NOT-EXIST simply check for the existence of that part of the dialed-digit string. The four-digit value that identifies a long distance carrier. Do not include the leading 101 carrier access code prefix in the TRANSIT-NETWORK value. and sometimes the contents. Refer to TRANSIT-NETWORK-ESCAPE for more information. Table 23-2 describes the operators that can be used with route filter tags. of the dialed-digit string associated with that tag. Route filter tag operators determine if a call is filtered based on the existence. Cisco CallManager Administration Guide 23-4 OL-1047-01 .

selects all dialed-digit strings with the carrier access code 1010288. Caution Do not enter route filter tag values for tags using the operators EXISTS. the operator ==. Select Route Plan > Route Filter in the menu bar. DOES-NOT-EXIST. selects all dialed-digit strings that do not include an area code. the operator ==. or NOT-SELECTED. selects all dialed-digit strings that include the 515 area code. Cisco CallManager Administration Guide OL-1047-01 23-5 . Examples Example 1: A route filter that uses AREA-CODE and the operator DOES-NOT-EXIST. and the entry 515. and the entry 5[2-9]X. along with TRANSIT-NETWORK-ESCAPE. Adding a Route Filter The following procedure describes how to add a route filter. the operator ==. Example 2: A route filter that uses AREA-CODE. Example 3: A route filter that uses AREA-CODE. and the entry 101. and the entry 0288. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Select North American Numbering Plan in the Dial Plan drop-down list box. selects all dialed-digit strings that include area codes in the range of 520 through 599. Example 4: A route filter that uses TRANSIT-NETWORK. Filter calls when the dialed-digit string associated with this tag matches the specified value.Chapter 23 Configuring Route Filters Adding a Route Filter Table 23-2 Route Filter Operators (continued) Operator DOES-NOT-EXIST == Description Filter calls when the dialed-digit string associated with this tag is not found. the operator ==.

Step 8 Related Topics • • • • Understanding Route Filter Tags. where appropriate. Click Continue.Chapter 23 Adding a Route Filter Configuring Route Filters Step 4 Enter a name in the Route Filter Name field. For example. page 23-2 Route Plan Overview. Step 5 Step 6 Note For help with entering data for route filter tags and operators. Each route filter name must be unique to the route plan. Step 7 Click Insert to add the filter.). Select the route filter tags and operators and enter data. click New and repeat Steps 3 through 7. periods (. refer to the “Understanding Route Filter Tags” section on page 23-2. The CompanynameLocationCalltype format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a route filter. page 6-7 Updating a Route Filter. The name can consist of up to 50 alphanumeric characters. page 23-7 Cisco CallManager Administration Guide 23-6 OL-1047-01 . hyphens (-). The new route filter name is added to the route filter list on the left side of the page and the message “Status: Insert completed” is displayed. and can contain any combination of spaces. page 6-1 Understanding Route Pattern Wildcards and Special Characters. and underscore characters (_). CiscoDallasMetro identifies a route filter for toll free inter-LATA (Local Access and Transport Area) calls from the Cisco office in Dallas. To add more route filters. Timesaver Use concise and descriptive names for your route filters. to create a clause for this route filter.

page 23-2 Route Plan Overview. Procedure Step 1 Step 2 Open Cisco CallManager Administration. update the appropriate operators and values and click Update. Select Route Plan > Route Filter in the menu bar.Chapter 23 Configuring Route Filters Updating a Route Filter Updating a Route Filter The following procedure describes how to update a route filter. When the Route Filter Configuration page displays the tags for the route filter. Repeat Steps 4 and 5 to update other route filters. page 23-7 Copying a Route Filter The following procedure describes how to copy a route filter. page 23-5 Copying a Route Filter. page 6-1 Understanding Route Pattern Wildcards and Special Characters. Select a name from the route filter list on the left side of the page. Repeat Step 5 to update other route filter tags. Select North American Numbering Plan in the Dial Plan drop-down list box. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. Select Route Plan > Route Filter in the menu bar. Related Topics • • • • • Understanding Route Filter Tags. page 6-7 Adding a Route Filter. Cisco CallManager Administration Guide OL-1047-01 23-7 .

Chapter 23 Copying a Route Filter Configuring Route Filters Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Select North American Numbering Plan in the Dial Plan drop-down list box. Modify operators. Select a name from the route filter list on the left side of the page. Click Copy. and add or remove clauses as appropriate to customize the new route filter. enter a new route filter name. The Route Filter Configuration page displays the new route filter with a Copy Of.. Enter the name for this route filter in the Route Filter Name field. name in the Route Filter Name field. To build another route filter that is similar to the current route filter.. add or change values. page 23-9 Removing Route Filter Clauses. Step 9 Related Topics • • • • • Understanding Route Filter Tags. page 6-1 Understanding Route Pattern Wildcards and Special Characters. page 6-7 Adding Route Filter Clauses. click Copy. page 23-10 Cisco CallManager Administration Guide 23-8 OL-1047-01 . The new route filter name is added to the route filter list on the left side of the page and the message “Status: Insert completed” is displayed. and repeat Steps 7 and 8. page 23-2 Route Plan Overview. Click Insert to add the filter.

) Step 8 To add more clauses to the same filter. You can add route filter clauses either when initially adding a new route filter or when updating an existing route filter. Select North American Numbering Plan in the Dial Plan drop-down list box. Select Route Plan > Route Filter in the menu bar. Select the route filter tags and operators and enter data. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. to create an additional clause for this route filter. Cisco CallManager Administration Guide OL-1047-01 23-9 . Select a name from the route filter list on the left side of the page. The new clause is added to the route filter and the message “Status: Insert completed” is displayed. All the operator fields for this new clause are set to NOT-SELECTED. Click Add Clause to display a new route filter clause data entry page. refer to the “Understanding Route Filter Tags” section on page 23-2. Note The new clause is displayed below the existing clauses on the page.Chapter 23 Configuring Route Filters Adding Route Filter Clauses Adding Route Filter Clauses Adding route filter clauses allows you to expand upon an existing route filter by incorporating additional operators and entries for existing tags using a logical OR. repeat Steps 4 through 7. To add clauses to another route filter. Step 7 Click Insert to add the clause. where appropriate. This procedure describes adding a route filter clause to an existing route filter. (You might need to scroll down to view the new information. Note For help with entering data for route filter tags and operators. click Add Clause and repeat Steps 6 and 7.

page 23-10 Removing Route Filter Clauses You can remove route filter clauses either when setting up a new route filter or when updating an existing route filter. Click OK to remove the clause. and must be rebuilt. This procedure describes removing a route filter clause from an existing route filter. Select a name from the route filter list on the left side of the page. the clause is removed from the route filter and the message “Status: Ready” is displayed. Caution Each Remove Clause button is linked to the clause immediately below the button. page 23-2 Route Plan Overview.Chapter 23 Removing Route Filter Clauses Configuring Route Filters Related Topics • • • • Understanding Route Filter Tags. Select Route Plan > Route Filter in the menu bar. Step 6 Cisco CallManager Administration Guide 23-10 OL-1047-01 . Select North American Numbering Plan in the Dial Plan drop-down list box. page 6-1 Understanding Route Pattern Wildcards and Special Characters. A dialog box appears warning you that removing this route filter clause cannot be undone. or click Cancel to cancel the action. If you click OK. Scroll down to the top of the clause you want to remove and click Remove Clause. If a clause is accidentally removed it cannot be recovered. page 6-7 Removing Route Filter Clauses. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Check carefully to ensure that you are removing the correct clause before initiating this action.

scroll to the appropriate clause. A dialog box appears warning you that deleting this route filter cannot be undone. page 6-7 Deleting a Route Filter. Caution Check carefully to ensure that you are deleting the correct route filter before initiating this action. page 6-1 Understanding Route Pattern Wildcards and Special Characters. To remove clauses from another route filter. Related Topics • • • • Understanding Route Filter Tags. Note You cannot delete route filters that are being used in route patterns or translation patterns. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Select North American Numbering Plan in the Dial Plan drop-down list box. Click Delete. page 23-2 Route Plan Overview. Cisco CallManager Administration Guide OL-1047-01 23-11 .Chapter 23 Configuring Route Filters Deleting a Route Filter Step 7 To remove more clauses from the same filter. repeat Steps 4 through 6. Select a name from the route filter list on the left side of the page. it must be rebuilt. Select Route Plan > Route Filter in the menu bar. Deleted route filters cannot be recovered. click Remove Clause for that clause and repeat Step 6. If a route filter is accidentally deleted. page 23-11 Deleting a Route Filter The following procedure describes how to delete a route filter.

Chapter 23 Deleting a Route Filter Configuring Route Filters Step 6 Step 7 Click OK to delete the route filter. page 23-9 Removing Route Filter Clauses. the route filter is deleted and the message “Status: Ready” is displayed. page 23-2 Route Plan Overview. Related Topics • • • • • Understanding Route Filter Tags. page 6-7 Adding Route Filter Clauses. page 23-10 Cisco CallManager Administration Guide 23-12 OL-1047-01 . or click Cancel to cancel the action. If you click OK. Repeat Steps 4 through 6 to delete other route filters. page 6-1 Understanding Route Pattern Wildcards and Special Characters.

if you use two long distance carriers. and “Understanding Route Groups” section on page 24-2 for more detailed route group information. Refer to the “Route Plan Overview” section on page 6-1. For example. page 24-6 Deleting a Route Group. Calls only route to the more expensive carrier if the first trunk is unavailable. you could add a route group so that long distance calls to the less expensive carrier are given priority.C H A P T E R 24 Configuring Route Groups A route group allows you to designate the order in which gateways are selected. page 24-2 Adding Devices to a Route Group. Use the following procedures to add or delete a route group or to add devices to or remove devices from a route group: • • • • • Adding a Route Group. It allows you to prioritize a list of gateways and ports for outgoing trunk selection. page 24-3 Removing Devices from a Route Group. page 24-5 Updating a Route Group. page 24-7 Cisco CallManager Administration Guide OL-1047-01 24-1 .

however. periods (. CiscoDallasAA1 identifies a Cisco Access Analog route group for the Cisco office in Dallas. if device X with ports 4. can be used in other route groups. Each route group name must be unique to the route plan. 5 are selected in route group 1. Timesaver Use concise and descriptive names for your route groups. The name can consist of up to 50 alphanumeric characters.port combination can only be included in one route group. For example. Step 4 Cisco CallManager Administration Guide 24-2 OL-1047-01 . Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. hyphens (-). or all ports or selected ports combination. Route groups are optional. then the same device and ports cannot be selected in any other route group. can only belong to one route group and can only be listed once within that route group. Select Route Plan > Route Group in the menu bar. Adding a Route Group The following procedure describes how to add a route group. The gateway-and. Click Continue. the route group is not needed. For example. If a gateway is assigned to a route pattern (all ports used). Enter a name in the Route Group Name field. Other unused ports. and underscore characters (_). and can contain any combination of spaces. The CompanynameLocationGroup format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a route group. then the gateway will not be listed as gateways to be included in route groups.).Chapter 24 Understanding Route Groups Configuring Route Groups Understanding Route Groups Each gateway. If a proposed route group only contains one gateway or one gateway-and-port combination and that route group is not to be included in a route list.

Chapter 24 Configuring Route Groups Adding Devices to a Route Group Step 5 Step 6 Select the device you want to add to the group from the Device Name drop-down list box. page 25-8 Adding Devices to a Route Group You can add devices to a new route group or to an existing route group. Click New and repeat Steps 3 through 8 to add more route groups. Click Insert to add this route group with one device. Step 7 Step 8 Step 9 Related Topics • • • • • • • Route Plan Overview. The following procedure describes adding a device to an existing route group. select All (default value). (Cisco Access Analog and Cisco MGCP Analog gateways allow you to select individual ports. page 24-5 Deleting a Route Group. Select the order in which you want to access this port or device in the Order drop-down list box.) Otherwise. Cisco CallManager Administration Guide OL-1047-01 24-3 . page 24-2 Adding Devices to a Route Group. page 6-1 Understanding Route Groups. Before You Begin You must define one or more gateway devices before performing this procedure. page 24-3 Removing Devices from a Route Group. page 24-7 Adding a Route List. Procedure Step 1 Open Cisco CallManager Administration. Click Add Device and repeat Steps 4 through 8 to add more devices to this route group. select the port in the Port drop-down list box. If this device supports individually configurable ports. page 25-6 Adding Route Groups to a Route List.

page 6-1 Understanding Route Groups. select the port in the Port drop-down list box.) Otherwise. Select a name from the route group list on the left side of the page. Select the order in which the new device is to be accessed in this route group in the Order drop-down list box. select All (default value). Select the order in the Order drop-down list box. page 25-6 Cisco CallManager Administration Guide 24-4 OL-1047-01 . page 24-2 Removing Devices from a Route Group. Click Update to update the device order for this route group. Click Add Device. Click Insert to add this gateway and selected ports to the route group. If this device supports individually configurable ports. Click Add Device and repeat Steps 5 through 9 to add more devices to this route group. page 24-6 Deleting a Route Group. (Cisco Access Analog and Cisco MGCP Analog gateways allow you to select individual ports. page 24-2 Adding a Route Group. page 24-7 Adding a Route List. page 24-5 Updating a Route Group. Select the device you want to add to the group from the Device Name drop-down list box.Chapter 24 Adding Devices to a Route Group Configuring Route Groups Step 2 Step 3 Step 4 Step 5 Step 6 Select Route Plan > Route Group in the menu bar. Step 7 Step 8 Step 9 Step 10 Step 11 Related Topics • • • • • • • Route Plan Overview.

or click Cancel to cancel the action. page 24-2 Adding a Route Group. Under the Route Group Members subheading. Select a name in the route group list on the left side of the page and repeat Steps 4 through 6 to remove devices from another route group. Select a name from the route group list on the left side of the page. Select Route Plan > Route Group in the menu bar. select the check box or boxes to the left of the devices to be deleted. A dialog box appears warning you that removing devices from a route group cannot be undone. If you click OK. the devices are removed from the route group. page 24-2 Adding Devices to a Route Group. The following procedure describes removing a device from an existing route group. page 24-6 Deleting a Route Group. Click OK to remove the devices. page 24-3 Updating a Route Group. page 25-6 Cisco CallManager Administration Guide OL-1047-01 24-5 . Related Topics • • • • • • • Route Plan Overview. page 24-7 Adding a Route List. Click Remove Device.Chapter 24 Configuring Route Groups Removing Devices from a Route Group Removing Devices from a Route Group You can remove devices from a new route group or from an existing route group. page 6-1 Understanding Route Groups. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Open Cisco CallManager Administration.

page 24-3 Deleting a Route Group. Select the route group you want to update from the list on the left side of the page. page 24-2 Adding a Route Group. Make the desired changes to the route group and click Update. Related Topics • • • • • • Route Plan Overview. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. page 24-7 Adding a Route List. page 24-2 Adding Devices to a Route Group. page 6-1 Understanding Route Groups. Select Route Plan > Route Group in the menu bar. Before You Begin The route group to be updated must already be configured before performing this procedure. page 25-6 Cisco CallManager Administration Guide 24-6 OL-1047-01 .Chapter 24 Updating a Route Group Configuring Route Groups Updating a Route Group The following procedure describes how to update a route group. Your changes should appear and the Status field should say Update completed.

The gateways that belonged to the deleted route group can now be selected by other route groups or route patterns. Click Delete. Select Route Plan > Route Group in the menu bar. You must remove the route group from all route lists to which it belongs before deleting the route group. page 6-1 Understanding Route Groups. Select a name in the route group list on the left side of the page and repeat Steps 4 and 5 to remove another route group. If you click OK. page 24-3 Updating a Route Group. Note You cannot delete a route group that is referenced by one or more route lists. provided that all ports were available with the gateways.Chapter 24 Configuring Route Groups Deleting a Route Group Deleting a Route Group The following procedure describes how to delete a route group. page 24-2 Adding Devices to a Route Group. page 25-6 Cisco CallManager Administration Guide OL-1047-01 24-7 . page 24-6 Adding a Route List. the route group is removed from the route group list. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. page 24-2 Adding a Route Group. Click OK to delete the group. A dialog box appears warning you that deleting route groups cannot be undone. or click Cancel to cancel the action. Select a name from the route group list on the left side of the page. Step 6 Related Topics • • • • • • Route Plan Overview.

Chapter 24 Deleting a Route Group Configuring Route Groups Cisco CallManager Administration Guide 24-8 OL-1047-01 .

page 25-8 Removing Route Groups from a Route List. route groups) that route calls that match the defined route pattern. the Cisco CallManager finds the first available device based on the order of the route group(s) defined in a route list. Some devices. A route list is a collection of resources (gateways. available. There should be at least one route group in each route list. Some. Within each route group. such as digital access. page 25-12 Cisco CallManager Administration Guide OL-1047-01 25-1 .C H A P T E R 25 Configuring Route Lists Route lists are made up of route groups which consist of a list of resources (gateways). page 25-10 Changing the Order of Route Groups in a Route List. Each route list can contain the same route groups that have already been selected by other route lists. The order controls the progress of the search for available trunk devices for outgoing calls. such as a gateway. Once a call is determined by the Cisco CallManager to be routed througha defined route list. Use the following procedures to add or remove route lists or to add. only allow you to select all ports. there should be at least one device. page 25-11 Deleting a Route List. remove or change the order of route groups in a route list: • • • • • Adding a Route List. or all. ports can be selected as resources in each route group based on device type. page 25-6 Adding Route Groups to a Route List. A route list associates a set of route groups with a route pattern and determines the order in which those route groups are accessed.

the CLID is passed to each private branch exchange (PBX). The calling party transformsettings assigned to the route groups in a route list override any calling party transform settings assigned to a route pattern associated with that route list. and values used to specify calling party transform for a route group. Table 25-1 describes the fields. The CLID is also delivered to the calling party when the call completes. The calling party’s number is used for Calling Line Identification (CLID).Chapter 25 Understanding Calling Party Transform Settings Configuring Route Lists Understanding Calling Party Transform Settings Calling party transform settings allow you to manipulate the appearance of the calling party’s number for outgoing calls. The calling party transform settings used in route lists are assigned to the individual route groups comprising the list. Cisco CallManager Administration Guide 25-2 OL-1047-01 . and inter-exchange carrier (IXC) as the call progresses. central office (CO). During an outgoing call. options. rather than the route list as a whole.

The options for this field are Default. page 6-7 Cisco CallManager Administration Guide OL-1047-01 25-3 . calls that are routed through this group are not associated with a CLID. Off: This setting indicates that the calling party’s external phone number is not used for CLID. On: This setting indicates that the calling party’s full. Off. Valid values for this field are the numbers 0 through 9. external number is used for CLID. page 6-1 Understanding Route Pattern Wildcards and Special Characters. If it is blank and the preceding field is set to Off. • • Calling Party Transform Mask This field specifies the calling party transform mask for all calls routed through this route group. Related Topics • • Route Plan Overview. • Default: This setting indicates that the calling party external phone number and calling party transform masks are not governed by the route group. no calling party number is available for CLID. If no transform mask is entered for this route group. external phone number is used for CLID on outgoing calls. If a calling party external phone number mask or transform mask is selected for the route pattern. and the wildcard character X. and On. calls that are routed through this route group will use those masks. This field can also be left blank.Chapter 25 Configuring Route Lists Understanding Calling Party Transform Settings Table 25-1 Calling Party Transform Settings Field Name Use Calling Party’s External Phone Number Mask Description This field determines whether or not the full. The calling party transform mask can contain up to 50 digits.

Cisco CallManager Administration Guide 25-4 OL-1047-01 . and suppressing carrier access codes for equal access calls. Examples of manipulating called numbers include appending or removing prefix digits (outgoing calls). The called party transform settings assigned to the route groups in a route list override any called party transform settings assigned to a route pattern associated with that route list. and values used to specify called party transform for a route group. for outgoing calls. Table 25-2 describes the fields. or called party’s number.Chapter 25 Understanding Called Party Transform Settings Configuring Route Lists Understanding Called Party Transform Settings Called party transform settings allow you to manipulate the dialed digits. appending area codes to calls dialed as seven-digit numbers. appending area codes and office codes to interoffice calls dialed as four. The called party transform settings used in route lists are assigned to the individual route groups comprising the list. rather than the route list as a whole.or five-digit extensions. options.

this field cannot be modified. change this field to North American Numbering Plan. Cisco CallManager Administration Guide OL-1047-01 25-5 . Refer to the “Understanding Discard Digits Instructions” section on page 6-12 for more information. If it is not already selected. in a system where users must dial 9 to make a call to the Public Switched Telephone Network (PSTN).Chapter 25 Configuring Route Lists Understanding Called Party Transform Settings Table 25-2 Called Party Transform Settings Field Name Dial Plan Description This field determines which dialing plan is used. Discard Digits This field contains a list of discard patterns that control the discard digit instructions. For example. Note The Dial Plan field only appears when inserting a route group in a route list. the PreDot discard pattern causes the 9 to be stripped from the dialed digit string. Once the route group is inserted.

page 6-7 Understanding Discard Digits Instructions. This field can also be left blank. and the wildcard character X. Valid values for this field are the numbers 0 through 9. Valid values for this field are the numbers 0 through 9 and blank. Related Topics • • • Route Plan Overview. Procedure Step 1 Step 2 Open Cisco CallManager Administration.Chapter 25 Adding a Route List Configuring Route Lists Table 25-2 Called Party Transform Settings (continued) Field Name Called Party Transform Mask Description This field specifies the called party transform mask for all calls routed through this route group. The calling party transform mask can contain up to 50 digits. page 6-1 Understanding Route Pattern Wildcards and Special Characters. Select Route Plan > Route List in the menu bar. If this field is blank. page 6-12 Adding a Route List The following procedure describes how to add a route list. Cisco CallManager Administration Guide 25-6 OL-1047-01 . Prefix Digits (Outgoing Calls) can contain up to 50 digits. no transformation takes place—the dialed digits are sent exactly as dialed. Prefix Digits (Outgoing Calls) This field contains a prefix digit or a set of Prefix Digits (Outgoing Calls) that are appended to the called party number on all calls routed through this route group.

CiscoDallasMetro identifies a route list for toll free inter-LATA (Local Access and Transport Area) calls from the Cisco office in Dallas. Click Add Route Group and perform Steps 5 through 9 of the “Adding Route Groups to a Route List” section on page 25-8 to add a route group to this list. hyphens (-).Chapter 25 Configuring Route Lists Adding a Route List Step 3 Enter a name in the Route List Name field. and can contain any combination of spaces. page 25-8 Changing the Order of Route Groups in a Route List. page 25-11 Removing Route Groups from a Route List. periods (. Click New and repeat Steps 3 through 5 to add another route list. Click Insert to add this route list. page 25-12 Cisco CallManager Administration Guide OL-1047-01 25-7 . Each route list name must be unique to the route plan. page 6-1 Understanding Route Groups. Step 4 Step 5 Step 6 Related Topics • • • • • • Route Plan Overview. page 25-10 Deleting a Route List. Type a description for the route list in the Description field and click Update. Timesaver Use concise and descriptive names for your route lists. The CompanynameLocationCalltype format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a route list. and underscore characters (_). The name can consist of up to 50 alphanumeric characters.). For example. page 24-2 Adding Route Groups to a Route List.

If you need to manipulate the calling party’s number on calls routed through this route group.Chapter 25 Adding Route Groups to a Route List Configuring Route Lists Adding Route Groups to a Route List You can add route groups to a new route list or an existing route list. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Open Cisco CallManager Administration. Select Route Plan > Route List in the menu bar. Note For more information on called party transform. set up the called party transform in the appropriate fields. Select a name from the route lists on the left side of the page. Note For more information on calling party transform. Step 9 Click Insert to add the route group. Click Add. page 25-4. set up the calling party transform in the appropriate fields. Step 8 If you need to manipulate the dialed digits on calls routed through this route group. Before You Begin You must build one or more route groups and add a route list before performing this procedure. see Understanding Calling Party Transform Settings. Select a route group to add to the list from the Select Route Group drop-down list box. Cisco CallManager Administration Guide 25-8 OL-1047-01 . page 25-2. see Understanding Called Party Transform Settings. The following procedure describes adding a route group to an existing route list. Click Add Route Group. The new route group name is added to the route list on the left side of the page and the message “Status: Insert completed” is displayed.

page 25-10 Deleting a Route List. page 25-12 Cisco CallManager Administration Guide OL-1047-01 25-9 . page 25-6 Changing the Order of Route Groups in a Route List. page 25-2 Understanding Called Party Transform Settings. page 6-1 Understanding Calling Party Transform Settings. page 25-11 Removing Route Groups from a Route List. page 25-4 Adding a Route List.Chapter 25 Configuring Route Lists Adding Route Groups to a Route List Step 10 Click Add Route Group to the current Route List and repeat Steps 5 through 9 to add more route groups to this list. Click Add new Route List and perform Steps 3 through 5 of the “Adding a Route List” section on page 25-6 to add another route list. Related Topics • • • • • • • Route Plan Overview.

Select Route Plan > Route List in the menu bar. If you click OK. page 6-1 Adding a Route List. press the Shift key and click on Multiple Route Groups. Step 8 Related Topics • • • • • Route Plan Overview. The following procedure describes removing a route group from an existing route list. page 25-6 Adding Route Groups to a Route List. Select a route group name from the Selected Route Groups list and repeat Steps 5 through 7 to remove another route group from this route list. Click OK to remove the route group. Step 5 Step 6 Step 7 Click Remove Route Group. Note To select multiple route groups from the list. page 25-12 Cisco CallManager Administration Guide 25-10 OL-1047-01 . page 25-11 Deleting a Route List. when the page refreshes. or click Cancel to cancel the action. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. A dialog box appears warning you that removing route groups from a route list cannot be undone.Chapter 25 Removing Route Groups from a Route List Configuring Route Lists Removing Route Groups from a Route List You can remove route groups from a new route list or from an existing route list. the route group is removed from the route list and the message “Status: Ready” is displayed. Select one or more route group names from the Selected Route Groups list. Select a name from the route lists on the left side of the page. page 25-8 Changing the Order of Route Groups in a Route List.

page 25-10 Deleting a Route List. page 25-6 Adding Route Groups to a Route List. Select a route group name from the Selected Route Groups list. Related Topics • • • • • Route Plan Overview. The following procedure allows you to change the access order of route groups. Select a name from the route lists on the left side of the page. page 25-8 Removing Route Groups from a Route List. Select Route Plan > Route List in the menu bar. Select a route group name from the Selected Route Groups list and repeat Steps 4 and 5 to move another route group in the route list.Chapter 25 Configuring Route Lists Changing the Order of Route Groups in a Route List Changing the Order of Route Groups in a Route List Route groups are accessed in the order in which they appear in the route list. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. page 6-1 Adding a Route List. Click the up or down arrows on the right side of the list box to move the route group up or down in the list. page 25-12 Cisco CallManager Administration Guide OL-1047-01 25-11 .

Step 7 Warning If you delete a route list that is associated with a route pattern in the Route Pattern Configuration page. The following procedure describes how to delete a route list. Click Delete. A dialog box appears warning you that removing a route list cannot be undone. page 25-11 Removing Route Groups from a Route List. page 25-6 Adding Route Groups to a Route List. Related Topics • • • • • Route Plan Overview. the route list is removed and the message “Status: Ready” is displayed. or click Cancel to cancel the action.Chapter 25 Deleting a Route List Configuring Route Lists Deleting a Route List Route lists are associated with both route groups and route patterns. Select Route Plan > Route List in the menu bar. however neither route groups nor route patterns are deleted when the route list is deleted. page 25-8 Changing the Order of Route Groups in a Route List. page 25-10 Cisco CallManager Administration Guide 25-12 OL-1047-01 . This means that any calls that match the route patterns will not be routed until you select another route list/gateway to be associated with that route pattern. when the page refreshes. Click OK to remove the route list. page 6-1 Adding a Route List. If you click OK. Select a name from the route lists on the left side of the page. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. Repeat Steps 3 through 6 to remove another route list. the route pattern will not have a route list associated with it.

or delete a route pattern: • • • • Adding a Route Pattern. They work in conjunction with route filters and route lists to direct calls to specific devices and to include.C H A P T E R 26 Configuring Route Patterns A route pattern is a string of digits (an address) and a set of associated digit manipulations that can be assigned to a route list or a gateway. page 26-4 Copying a Route Pattern. page 26-6 Adding a Route Pattern This section describes how to add a route pattern. Use the following procedures to add. or modify specific digit patterns. Route patterns provide flexibility in network design. update. Before You Begin The following Cisco CallManager applications must be configured first in order to select them: • • Gateway Route List Cisco CallManager Administration Guide OL-1047-01 26-1 . page 26-1 Updating a Route Pattern. exclude. copy. Refer to the “Understanding Route Patterns” section on page 6-24 for more detailed route pattern information. page 26-5 Deleting a Route Pattern.

Selecting a route filter restricts certain number patterns. Route filters are optional. or None if you don’t want to assign a partition. Step 5 Step 6 Step 7 Cisco CallManager Administration Guide 26-2 OL-1047-01 . Step 4 Select a partition from the Partition drop-down list box. Check the route pattern. Timesaver Assigning 8XXX to a gateway routes all directory numbers 8000 to 8999 out the gateway. and numbering plan combination. Similarly. Select the gateway or route list for which you are adding a route pattern from the Gateway/Route List drop-down list box. using the selected partition. Refer to the “Understanding Route Pattern Wildcards and Special Characters” section on page 6-7 for more information about wildcards. Refer to the “Configuring Partitions” section on page 21-1 for more information on how to use partitions. Select Route Plan > Route Pattern. call pickup number. route filter. translation pattern. 82XX routes directory numbers 8200 to 8299. including numbers and wildcards (do not use spaces) in the Route Pattern field. Select a numbering plan from the Numbering Plan drop-down list box.@ for typical local access. must be unique. 9. Enter the route pattern.Chapter 26 Adding a Route Pattern Configuring Route Patterns • • Partition Route Filter Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Note The directory route pattern. or 8XXX for a typical private network numbering plan. for example. or Meet Me number if you receive an error indicating duplicate entries. directory number. select a route filter from the Route Filter drop-down list box. call park number. If your route pattern includes the @ wildcard.

Refer to the “Understanding Discard Digits Instructions” section on page 6-12 for more information. #. that gateway will not be included in this drop-down list box. Step 9 Step 10 Step 11 Note The calling party transformation settings assigned to the route groups in a route list override any calling party transformation settings assigned to a route pattern associated with that route list. or that has an assigned DN. Step 13 Step 14 Cisco CallManager Administration Guide OL-1047-01 26-3 . all the ports are being used to route/block this route pattern. Valid entries include the digits 0 through 9. If this field is blank and the preceding field is not checked. No ports can be used in order to include the gateway. Step 12 Select the discard digits instructions you want associated with this route pattern from the Discard Digits drop-down list box. Select “Route this pattern” or “Block this pattern” in the Route Option fields. When a gateway is selected in the drop-down list box. Valid entries include the digits 0 through 9. The dialed digits are sent exactly as dialed. Refer to the “Understanding Calling Party Transform Settings” section on page 25-2 for more information. Check the boxes for Provide Outside Dial Tone and Urgent Priority accordingly. and blank. You must also configure an External Mask on all phone devices. Valid entries include the digits 0 through 9. no calling party transformation takes place. and blank. *. Step 8 The Route Option designation indicates whether you want this route pattern used for routing calls (such as 9.@ or 8[2-9]XX) or for blocking calls. and blank.Chapter 26 Configuring Route Patterns Adding a Route Pattern Note If there is at least one port of the defined gateway included in a route group. the wildcard character X. the wildcard character X. Enter prefix digits in the Prefix Digits (Outgoing Calls) field. Enter a transformation mask value in the Calling Party Transform Mask field. external phone number used for CLID on outgoing calls. Refer to the “Understanding Called Party Transform Settings” section on page 25-4 for more information. Check the box for Use Calling Party’s External Phone Number Mask if you want the full. Enter a transformation mask value in the Called Party Transform Mask field. no transformation takes place. If the field is blank.

Procedure Step 1 Step 2 Open Cisco CallManager Administration. This link takes you to the MGCP Member Configuration page for reference so you can see the route group(s) included in that route list. The route pattern appears in the list on the left side of the page. page 6-7 Understanding Closest-Match Routing.Chapter 26 Updating a Route Pattern Configuring Route Patterns Note The appended prefix digit does not affect which directory numbers route to the assigned device. Note Once you click Insert and the page refreshes. Step 16 Click New and repeat Steps 1 through 15 to add more route patterns. page 23-5 Updating a Route Pattern. page 26-5 Deleting a Route Pattern. page 6-1 Understanding Route Pattern Wildcards and Special Characters. Related Topics • • • • • • • Route Plan Overview. page 6-11 Adding a Route Filter. Cisco CallManager Administration Guide 26-4 OL-1047-01 . Step 15 Click Insert. Click Route Plan > Route Pattern. page 26-4 Copying a Route Pattern. page 26-6 Updating a Route Pattern This section describes how to update a route pattern. an (Edit) link appears on the page next to the Gateway/Route List field.

Procedure Step 1 Step 2 Open Cisco CallManager Administration. or Meet Me number if you receive an error indicating duplicate entries. Repeat Steps 3 and 4 to update more route patterns. page 23-5 Adding a Route Pattern. page 6-1 Understanding Route Pattern Wildcards and Special Characters. Step 4 Step 5 Make the desired changes to the route pattern and click Update. page 6-7 Understanding Closest-Match Routing. The page displays the updated route pattern. using the selected partition. route filter. call pickup number. page 26-6 Copying a Route Pattern This section describes how to copy a route pattern.Chapter 26 Configuring Route Patterns Copying a Route Pattern Step 3 Select the route pattern you want to update from the Route Pattern list on the left side of the page. page 26-5 Deleting a Route Pattern. Click Route Plan > Route Pattern. Cisco CallManager Administration Guide OL-1047-01 26-5 . and numbering plan combination. Note The directory route pattern. page 26-1 Copying a Route Pattern. Check the route pattern. must be unique. page 6-11 Adding a Route Filter. translation pattern. directory number. Related Topics • • • • • • • Route Plan Overview. call park number.

. Cisco CallManager Administration Guide 26-6 OL-1047-01 . page 23-5 Adding a Route Pattern. Select the route pattern you want to delete from the Route Pattern list on the left side of the page. Click Delete. Related Topics • • • • • • • Route Plan Overview. A message displays stating that you are about to delete the selected route pattern and that this action cannot be undone. click Copy.Chapter 26 Deleting a Route Pattern Configuring Route Patterns Step 3 Step 4 Step 5 Step 6 Step 7 Select the route pattern you want to copy from the Route Pattern list on the left side of the page. The new route pattern appears in the route pattern list on the left side of the page. page 26-6 Deleting a Route Pattern This section describes how to delete a route pattern. page 26-4 Deleting a Route Pattern. page 6-11 Adding a Route Filter. page 26-1 Updating a Route Pattern. enter a new route pattern name. Click Route Plan > Route Pattern.. page 6-7 Understanding Closest-Match Routing. To build another route pattern that is similar to the current route pattern. Make appropriate changes to customize the new route pattern and click Insert. and repeat Steps 3 through 6. Click Copy. page 6-1 Understanding Route Pattern Wildcards and Special Characters. Replace the name for this route pattern in the Route Pattern field. The page displays the route pattern with a Copy of. name in the Route Pattern field. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration.

Repeat Steps 3 through 5 to delete more route patterns. page 26-4 Copying a Route Pattern. Related Topics • • • • • • • Route Plan Overview. page 6-7 Understanding Closest-Match Routing. page 26-5 Cisco CallManager Administration Guide OL-1047-01 26-7 . or Cancel to cancel the deletion. page 26-1 Updating a Route Pattern. page 23-5 Adding a Route Pattern. page 6-1 Understanding Route Pattern Wildcards and Special Characters.Chapter 26 Configuring Route Patterns Deleting a Route Pattern Step 5 Step 6 Click OK to continue. page 6-11 Adding a Route Filter.

Chapter 26 Deleting a Route Pattern Configuring Route Patterns Cisco CallManager Administration Guide 26-8 OL-1047-01 .

the dialed number is not the number that is used by the system. page 27-6 Understanding Translation Patterns Digit manipulation and translation patterns are used frequently in cross-geographical distributed systems where. In other cases. and translation patterns can be applied to accommodate the unique office codes at each location. for instance. Use the following procedures to add. page 27-2 Updating a Translation Pattern. update. page 27-5 Deleting a Translation Pattern. Refer to the “Understanding Translation Patterns” section on page 27-1 for more detailed translation pattern information. the dialed number is not a number that is recognized by the Public Switched Telephone Network (PSTN).C H A P T E R 27 Configuring Translation Patterns The Cisco CallManager uses translation patterns to manipulate dialed digits before routing a call. a uniform dialing plan can be created. page 27-4 Copying a Translation Pattern. copy. In some cases. the office codes are not the same at all locations. In these situations. or delete a translation pattern: • • • • Adding a Translation Pattern. Cisco CallManager Administration Guide OL-1047-01 27-1 .

page 6-7 Understanding Closest-Match Routing. page 6-11 Understanding Discard Digits Instructions. Select Route Plan > Translation Pattern.Chapter 27 Adding a Translation Pattern Configuring Translation Patterns Note Translation patterns provide a level of routing indirection for other applications also. The previous explanation is just the most common application Related Topics • • • • Route Plan Overview. or 8XXX for a typical private network numbering plan. Cisco CallManager Administration Guide 27-2 OL-1047-01 . 9. Before You Begin Configure the following Cisco CallManager applications before adding a translation pattern: • • • Partition Route Filter Calling Search Space Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. page 6-1 Understanding Route Pattern Wildcards and Special Characters. For example.@ for typical local access. Enter the translation pattern. including numbers and wildcards (do not use spaces) in the Translation Pattern field. page 6-12 Adding a Translation Pattern This section describes how to add a translation pattern.

Check the boxes for Provide Outside Dial Tone. must be unique. If your translation pattern includes the @ wildcard. Select a numbering plan from the Numbering Plan drop-down list box. Select None if you don’t want to assign a partition. Select the discard digits instructions you want associated with this translation pattern from the Discard Digits drop-down list box. Urgent Priority is selected by default.@ or 8[2-9}XX) or for blocking calls. Select “Route this pattern” or “Block this pattern” in the Route Option fields. Step 7 Step 8 Step 9 Note All translation patterns are set with urgent priority and cannot be changed. or Meet Me number if you receive an error indicating duplicate entries. Cisco CallManager Administration Guide Step 12 OL-1047-01 27-3 . Check the route pattern. Refer to the “Understanding Route Pattern Wildcards and Special Characters” section on page 6-7. directory number. and blank. using the selected partition. Step 4 Step 5 Step 6 Select a partition from the Partition drop-down list box. select a route filter from the Route Filter drop-down list box. call park number. Valid entries include the digits 0 through 9. translation pattern.Chapter 27 Configuring Translation Patterns Adding a Translation Pattern Note The directory route pattern. The Route Option designation indicates whether you want this translation pattern used for routing calls (such as 9. Enter a transformation mask value in the Calling Party Transform Mask field. call pickup number. Step 10 Step 11 Check the box for Use Calling Party’s External Phone Number Mask if you want the full. route filter. and numbering plan combination. and the “Configuring Route Filters” section on page 23-1 for more information. See the “Understanding Calling Party Transform Settings” section on page 25-2 for more detailed information. the wildcard character X. Route filters are optional. Select the calling search space for which you are adding a translation pattern from the Calling Search Space drop-down list box. Selecting a route filter restricts certain number patterns. This is an optional selection. no calling party transformation takes place. external phone number used for calling line ID (CLID) on outgoing calls. If this field is blank and the preceding field is not checked.

#. Click New and repeat Steps 1 through 15 to add more translation patterns. If the field is blank. The page displays the updated translation pattern. *. Select the translation pattern you want to update from the Translation Pattern list on the left side of the page. Refer to the “Understanding Called Party Transform Settings” section on page 25-4 for more detailed information. page 27-4 Copying a Translation Pattern. Enter prefix digits in the Prefix Digits (Outgoing Calls) field. Valid entries include the digits 0 through 9. Click Route Plan > Translation Pattern. The translation pattern appears in the list on the left side of the page. and blank. Step 14 Note The appended prefix digit does not affect which directory numbers route to the assigned device. page 27-5 Deleting a Translation Pattern. Cisco CallManager Administration Guide 27-4 OL-1047-01 . Valid entries include the digits 0 through 9. The dialed digits are sent exactly as dialed. no transformation takes place. Step 15 Step 16 Click Insert. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration.Chapter 27 Updating a Translation Pattern Configuring Translation Patterns Step 13 Enter a transformation mask value in the Called Party Transform Mask field. Make the desired changes to the translation pattern and click Update. the wildcard character X. page 27-6 Updating a Translation Pattern This section describes how to update a translation pattern. Related Topics • • • Updating a Translation Pattern. and blank.

Chapter 27 Configuring Translation Patterns Copying a Translation Pattern Note The directory route pattern. The new translation pattern appears in the translation pattern list on the left side of the page.. directory number. Cisco CallManager Administration Guide OL-1047-01 27-5 . page 27-2 Copying a Translation Pattern.. call pickup number. Replace the name for this translation pattern in the Translation Pattern field. translation pattern. route filter. page 27-6 Copying a Translation Pattern This section describes how to copy a translation pattern. must be unique. Click Copy. Related Topics • • • Adding a Translation Pattern. Click Route Plan > Translation Pattern. using the selected partition. page 27-5 Deleting a Translation Pattern. name in the Translation Pattern field. Step 5 Repeat Steps 3 and 4 to update more translation patterns. The page displays the translation pattern with a Copy of. or Meet Me number if you receive an error indicating duplicate entries. and numbering plan combination. Make appropriate changes to customize the new translation pattern and click Insert. Check the route pattern. call park number. Select the translation pattern you want to copy from the Translation Pattern list on the left side of the page. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration.

Cisco CallManager Administration Guide 27-6 OL-1047-01 . page 27-4 Deleting a Translation Pattern. enter a new translation pattern name. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration.Chapter 27 Deleting a Translation Pattern Configuring Translation Patterns Step 7 To build another translation pattern that is similar to the current translation pattern. page 27-2 Updating a Translation Pattern. Related Topics • • • • • Route Plan Overview. page 27-6 Deleting a Translation Pattern This section describes how to delete a translation pattern. page 6-1 Understanding Translation Patterns. Click Delete. or Cancel to cancel the deletion. Click Route Plan > Translation Pattern. and repeat Steps 3 through 6. Click OK to continue. click Copy. A message displays stating that you are about to delete the selected translation pattern and that this action cannot be undone. Repeat Steps 3 through 5 to delete more translation patterns. page 27-1 Adding a Translation Pattern. Select the translation pattern you want to delete from the Translation Pattern list on the left side of the page.

Chapter 27 Configuring Translation Patterns Deleting a Translation Pattern Related Topics • • • Adding a Translation Pattern. page 27-2 Updating a Translation Pattern. page 27-4 Copying a Translation Pattern. page 27-5 Cisco CallManager Administration Guide OL-1047-01 27-7 .

Chapter 27 Deleting a Translation Pattern Configuring Translation Patterns Cisco CallManager Administration Guide 27-8 OL-1047-01 .

page 28-4 Entering Location Information. page 28-6 Providing Gateway Information. to Private Branch Exchanges (PBXs). page 28-9 Confirming the External Route Plan. page 28-10 Finishing the External Route Plan. Refer to the “Understanding the External Route Plan Wizard” section on page 6-25 for more detailed information about how the wizard generates the external route plan. page 28-8 Generating the External Route Plan. page 28-11 Deleting an External Route Plan. page 28-2 Providing Tenant Information. page 28-2 Setting the Routing Options.C H A P T E R 28 Using the External Route Plan Wizard The external route plan wizard is a tool that allows Cisco CallManager administrators to quickly configure external routing to the Public Switched Telephone Network (PSTN). page 28-5 Selecting Gateways. Use the following procedures to set up a route plan with the external route plan wizard: • • • • • • • • • • Creating an External Route Plan. page 28-11 Cisco CallManager Administration Guide OL-1047-01 28-1 . or to other Cisco CallManager systems.

Chapter 28 Creating an External Route Plan

Using the External Route Plan Wizard

Creating an External Route Plan
The following procedure describes how to begin to create an external route plan.
Before You Begin

All gateways must be defined before using the external route plan wizard. Select Device > Gateway or Device > MGCP in the menu bar to set up new gateways.
Procedure
Step 1 Step 2 Step 3

Open Cisco CallManager Administration. Select Route Plan > External Route Plan Wizard in the menu bar. Click Next on the External Route Plan Wizard introduction page to create an external route plan.

Related Topics
• • • • • • • • •

Setting the Routing Options, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Generating the External Route Plan, page 28-9 Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Setting the Routing Options
The following procedure describes how to set routing options for the external route plan.

Cisco CallManager Administration Guide

28-2

OL-1047-01

Chapter 28

Using the External Route Plan Wizard Setting the Routing Options

Procedure
Step 1

Check the boxes for Local call fallback, Toll bypass fallback, Long distance fallback, International call fallback, and Equal access suppression as appropriate.

Note

If you choose local call fallback, toll bypass fallback, long distance fallback, or international call fallback, the external route plan wizard includes route groups with remote gateways in the associated route lists.

Step 2

Enter the access code for calls that are routed to remote or local gateways in the “Access code for toll bypass and fallback calls” field. Use only numeric values. (Many systems use 9 for external calls.)

Note

The access code entered in this field applies to the entire dial plan. Only one access code is allowed per dial plan.

Step 3

Enter the access code for callas between the Cisco CallManager and the adjacent PBX “Access code for extensions served by a connected PBX” field. (Many systems use 8 for calls to adjacent PBX systems.) Click Next.

Step 4

Related Topics
• • • • • • • • •

Creating an External Route Plan, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Generating the External Route Plan, page 28-9 Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11
Cisco CallManager Administration Guide

OL-1047-01

28-3

Chapter 28 Providing Tenant Information

Using the External Route Plan Wizard

Providing Tenant Information
The following procedure describes how to add tenant information for the external route plan.
Procedure
Step 1

Enter the tenant name in the Tenant Name field. (This is generally the name of the organization for which the route plan is being built.)

Note

We recommend that you use a short tenant name because it is incorporated in the calling search space and partition names.

Step 2

Enter the number of geographical locations associated with the organization in the “Number of physical locations in the entire system” field. This field should reflect the all Cisco CallManagers in the system that use unique area codes. The default number of locations is two. Click Next.

Step 3

Related Topics
• • • • • • • • •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Generating the External Route Plan, page 28-9 Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Cisco CallManager Administration Guide

28-4

OL-1047-01

Chapter 28

Using the External Route Plan Wizard Entering Location Information

Entering Location Information
The Location Entry page provides information for the number of locations specified on the Tenant Information page. The following procedure describes how to add location information for the external route plan.
Procedure
Step 1

Enter the name of the location in the Location Name field if it is different from the one shown. Each location name must be unique for the tenant to which it applies. Enter the local area codes available at this location in the Local Area Code(s) field. (Local area codes are all area codes in the calling area that are not considered to be long distance calls.) If your area includes more than one local (toll free) area code, use commas to separate the area codes in the list. Place the primary local area code first, followed by the secondary, and tertiary local area codes.

Step 2

Note

The primary local area code is used to set prefix digits on local route patterns. If the primary area code is not listed in the correct order, it adversely affects route filter generation.

Step 3 Step 4

Enter the 7- or 10-digit number that is the main number for the organization at this location. Specify the number of digits required for local calls at this location. The route plan wizard uses this information to determine how many route lists to create for this location. If you select 10-digit or 7-digit dialing, the wizard creates one route list for this location. If you select Metro dialing, the wizard creates two route lists for the location.

Step 5

Repeat Steps 1 through 4 to add location information for other locations.

Related Topics
• •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2
Cisco CallManager Administration Guide

OL-1047-01

28-5

Chapter 28 Selecting Gateways

Using the External Route Plan Wizard

• • • • • • •

Providing Tenant Information, page 28-4 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Generating the External Route Plan, page 28-9 Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Selecting Gateways
The following procedure describes how to select gateways for the external route plan.

Caution

Do not select gateways that are used by existing route groups or route patterns. The wizard uses all ports on the selected gateway. If you select a gateway that is used by existing route groups or route patterns, the external route plan wizard will overwrite the previously configured ports.
Procedure

Step 1 Step 2 Step 3

Check the boxes for all the gateways associated with this route plan in all locations. Click Select All if you want to include all the gateways defined in the system. Click Select None if you have selected several gateways and want to deselect all of your selections.

Note

You must select at least one gateway before continuing with this procedure.

Cisco CallManager Administration Guide

28-6

OL-1047-01

Chapter 28

Using the External Route Plan Wizard Selecting Gateways

Step 4

Click Next.

Related Topics
• • • • • • • •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Providing Gateway Information, page 28-8 Generating the External Route Plan, page 28-9 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Cisco CallManager Administration Guide OL-1047-01

28-7

Chapter 28 Providing Gateway Information

Using the External Route Plan Wizard

Providing Gateway Information
The following procedure describes how to add gateway information for the gateways in the external route plan.
Procedure
Step 1 Step 2 Step 3 Step 4 Step 5

Select the gateway location in the “Location of the gateway” drop-down list box. Select the type of connection for this gateway in the “Type of carrier to which the gateway is connected” drop-down list box. Specify the calling number that will be sent to the adjacent switch when a call is routed through this gateway. Check the Discard dialed access code... check box if this gateway is connected to a PBX that does not require the Cisco CallManager access code. Enter the range of directory numbers or extension numbers associated with the adjacent PBX. Use commas to separate multiple entries. Use X wildcard characters to specify ranges of digits. For example, if the PBX serves extensions numbered 8000 through 8999 and 9000 through 9999, enter 8XXX,9XXX to create route patterns for the identified directory number ranges.

Note

If you provide directory number ranges, the wizard generates one route list for each unique range (route pattern) you enter. If you provide an access code for the directory number ranges and do not check the Discard dialed access code... check box, the wizard generates one route list for each unique range (route pattern) you enter, and precedes each route list with the access code and a dot (.).

Step 6 Step 7

Click Next. Repeat Steps 1 through 6 to add gateway information for the additional gateways.

Related Topics
• •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2

Cisco CallManager Administration Guide

28-8

OL-1047-01

Chapter 28

Using the External Route Plan Wizard Generating the External Route Plan

• • • • • • •

Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Generating the External Route Plan, page 28-9 Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Generating the External Route Plan
Click Next to generate the external route plan.
Note

The wizard can take several minutes to generate the external route plan, depending on the complexity of the route plan and the system load. Please do not start additional processes that would further load the system during this time. Click Cancel to prevent the external route plan wizard from generating this route plan.

Note

If you click Cancel, all data associated with the current route plan is discarded. This action cannot be undone. The information must be re-entered.
Related Topics
• • • • • •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8

Cisco CallManager Administration Guide OL-1047-01

28-9

Chapter 28 Confirming the External Route Plan

Using the External Route Plan Wizard

• • •

Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Confirming the External Route Plan
The following procedure describes how to confirm an external route plan.
Procedure
Step 1 Step 2

Check the external route plan wizard status report to ensure that the route plan contains the proper elements. Click Next to complete the external route plan.

Note

We strongly recommend that you print the status report for future reference.

If you determine that the external route plan is incorrect based on the information shown in the status report, proceed to the final page of the external route plan wizard. The final page allows you to delete the entire route plan, if needed.

Related Topics
• • • • • • • •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Finishing the External Route Plan, page 28-11 Deleting an External Route Plan, page 28-11

Cisco CallManager Administration Guide

28-10

OL-1047-01

Chapter 28

Using the External Route Plan Wizard Finishing the External Route Plan

Finishing the External Route Plan
Click Finish to complete the external route plan if the information shown on the external route plan wizard status report is correct. Click Delete External Route Plan to remove all data generated by the external route plan wizard if the information shown on the status report is incorrect.

Warning

Clicking “Delete External Route Plan” deletes all data that has been generated by the external route plan wizard. This action cannot be undone. All external route plan information must be re-entered. Related Topics
• • • • • • • •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Confirming the External Route Plan, page 28-10 Deleting an External Route Plan, page 28-11

Deleting an External Route Plan
The following procedure describes how to delete an external route plan. If any element generated by the external route plan wizard is being used in the system (for example, if Cisco IP Phones belong to a generated partition), the delete function will fail. If generated elements are used, the system components that are using those elements must be moved to non-generated elements before using the delete function.

Cisco CallManager Administration Guide OL-1047-01

28-11

Chapter 28 Deleting an External Route Plan

Using the External Route Plan Wizard

Warning

This procedure deletes all data that has been generated by the external route plan wizard. This action cannot be undone. All external route plan information must be re-entered. Procedure

Step 1 Step 2 Step 3

Open Cisco CallManager Administration. Select Route Plan > External Route Plan Wizard in the menu bar. Click Delete External Route Plan to remove all data generated by the external route plan wizard.

Related Topics
• • • • • • • • •

Creating an External Route Plan, page 28-2 Setting the Routing Options, page 28-2 Providing Tenant Information, page 28-4 Entering Location Information, page 28-5 Selecting Gateways, page 28-6 Providing Gateway Information, page 28-8 Generating the External Route Plan, page 28-9 Confirming the External Route Plan, page 28-10 Finishing the External Route Plan, page 28-11

Cisco CallManager Administration Guide

28-12

OL-1047-01

C H A P T E R

29

Using Route Plan Report
The route plan report is a listing of all call park numbers, call pickup numbers, conference numbers, route patterns and translation patterns in the system. The route plan report allows you to view either a partial or full list, and to go directly to the associated configuration pages, by selecting a route pattern, partition, route group, route list, call park number, call pickup number, conference number, or gateway. In addition, the route plan report allows you to save report data into a .csv file that you can import into other applications. The .csv file contains more detailed information than the web pages, including directory numbers (DN) for phones, route patterns, and translation patterns. The Cisco CallManager uses the route plan to route both internal calls and external (Public Switched Telephone Network [PSTN]) calls. For more detailed information on the route plan, see the “Understanding Route Plans” section on page 6-1. Use the following procedures to view all route plan records:
• •

Viewing All Route Plan Records, page 29-2 Viewing Route Plan Reports in a File, page 29-3

Cisco CallManager Administration Guide OL-1047-01

29-1

The Route Detail column shows a route list (with route group and associated gateway. page 29-1 Viewing Route Plan Reports in a File. the corresponding call type. If there are more than 50 items. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Note The route plan report shows the Pattern/Directory.Chapter 29 Viewing All Route Plan Records Using Route Plan Report Viewing All Route Plan Records This section describes how to view all Route Plan Records. Related Topics • • • Understanding Route Plans. Step 3 Click All to view the entire report (viewing this option can take a long time to load on large systems). the Route Plan Report screen shows the first 50. or click Next 50 or Previous 50 to navigate through the report 50 items at a time. page 6-1 Using Route Plan Report. and ports used information). and partition. Select Route Plan > Route Plan Report. or gateway information. page 29-3 Cisco CallManager Administration Guide 29-2 OL-1047-01 .

Procedure Step 1 Step 2 Open Cisco CallManager Administration. page 6-1 Using Route Plan Report. or import it into another application.csv file you just saved and double-click on its icon to view it. Locate the .csv file. Another window appears allowing you to save this file to a location of your choice. A dialog box appears. page 29-2 Cisco CallManager Administration Guide OL-1047-01 29-3 . Step 3 Click View In File.Chapter 29 Using Route Plan Report Viewing Route Plan Reports in a File Viewing Route Plan Reports in a File This section contains information on how to view route plan reports in a . Step 5 Step 6 Select the location in which to save the file and click Save. If there are more than 50 items. Step 4 Click Save File in the dialog box. you can either save the file. the Route Plan Report screen shows the first 50. but the extension the file name must have a . From this dialog box.csv extension. The file should now be saved to the location you designated. Select Route Plan > Route Plan Report. Note You may also save the file as a different file name. Related Topics • • • Understanding Route Plans. page 29-1 Viewing All Route Plan Records.

Chapter 29 Viewing Route Plan Reports in a File Using Route Plan Report Cisco CallManager Administration Guide 29-4 OL-1047-01 .

“Cisco Messaging Interface” • Chapter 31. “Configuring Cisco TFTP” • Chapter 32. “Configuring Cisco WebAttendants” • Chapter 33. “Configuring Media Termination Point” • Chapter 35. “Configuring Conference Bridges” • Chapter 34. “Starting and Stopping Services Using the Control Center” .P A R T 4 Service Configuration The following chapters include information on configuring services used in conjunction with Cisco CallManager: • Chapter 30. “Configuring Transcoder” • Chapter 38. “Configuring Trace” • Chapter 37. “Configuring Service Parameters” • Chapter 36.

.

A Cisco Analog Access Station Gateway or Cisco VG200 Gateway must be installed and configured. The voice mail system must use analog ports for connecting voice lines. The voice mail system must meet the following requirements: • • • • • The voice mail system must have a simplified message desk interface (SMDI) accessible with a null-modem RS-232 cable (and an available serial port). See the “Configuring Route Patterns” section on page 26-1 for more information. The SMDI-compliant voice mail system is connected to Cisco CallManager in two ways: • • Using a standard serial connection to the Cisco CallManager Using POTS line connections to a Cisco Analog Station gateway Note CMI should only reside on a single Cisco CallManager within a cluster. The Cisco CallManager server must have an available serial port for the SMDI connection. Gateways are configured in a route pattern.C H A P T E R 30 Cisco Messaging Interface The Cisco Messaging Interface allows you to use an external voice mail system with the Cisco CallManager 3. You cannot have two CMI applications connected to the same voice mail system running at the same time.0. Cisco CallManager Administration Guide OL-1047-01 30-1 .

the local machine is assumed to be the Cisco CallManager. page 30-8 Configuring Cisco Messaging Interface Trace Parameters.Chapter 30 Most Commonly Changed CMI Service Parameters Cisco Messaging Interface Related Topics • • • • • Most Commonly Changed CMI Service Parameters. page 30-2 Adding Cisco Messaging Interface Service on the Cisco CallManager. but the one shown here will frequently be correct. Default value: 9600 Note Many voice mail systems can be configured to use different baud rates. You can use either the name of a Cisco CallManager or its IP address. Cisco CallManager Administration Guide 30-2 OL-1047-01 . CallManagerName This parameter specifies the name of the Cisco CallManager server that will be used for the CMI primary. This parameter defines that connection. If this field is not specified. Caution Do not add or delete service parameters unless directed by the Cisco Technical Assistance Center (TAC). Table 30-1 Most Commonly Changed Service Parameter Fields Parameter Fields BaudRate Value/Description CMI connects to the voice mail system via an RS-232 connection. You can also leave this field blank. page 30-10 Most Commonly Changed CMI Service Parameters Table 30-1 lists and describes CMI service parameter fields that are most commonly changed. page 30-6 Configuring Cisco Messaging Interface Service Parameters. page 30-5 Deleting Cisco Messaging Interface Service From a Server.

CMI connects to the voice mail system via an RS-232 connection. If a legacy voice mail system has mailbox numbers that are longer than the DNs on the system. The numeric value of this parameter indicates how many digits should be used. Recommended default value: 10 Parity CMI connects to the voice mail system via an RS-232 connection. Cisco CallManager Administration Guide OL-1047-01 30-3 . Recommended default value: 7 DataBits InputDNSignificantDigits This parameter is designed to accommodate the differences between voice mail mailbox numbers and directory numbers (DNs). This parameter defines one of the values used to configure that connection. Just using the first character of the parity name also works. This field is case insensitive. Default value: Even Note The parity settings can be None. This parameter defines one of the values used to configure that connection. Mark. Even. Settings are usually Even or None. You can use either the name of a Cisco CallManager or its IP address. with Mark and Space rarely being used. Note There is no provision for stripping digits other than leading ones. this parameter can be used to strip the most significant digits. or Space. Odd.Chapter 30 Cisco Messaging Interface Most Commonly Changed CMI Service Parameters Table 30-1 Most Commonly Changed Service Parameter Fields (continued) Parameter Fields BackUpCallManager Value/Description This parameter specifies the name of the Cisco CallManager that will be used for the CMI backup.

This parameter defines one of the values used to configure that connection.Chapter 30 Most Commonly Changed CMI Service Parameters Cisco Messaging Interface Table 30-1 Most Commonly Changed Service Parameter Fields (continued) Parameter Fields SerialPort Value/Description CMI connects to the voice mail system via an RS-232 connection. This parameter defines one of the values used to configure that connection. where dallas01 and dallas02 are partition names. StopBits CMI connects to the voice mail system via an RS-232 connection. page 30-10 Cisco CallManager Administration Guide 30-4 OL-1047-01 . as defined in a route pattern. Recommended default value: 1 The voice mail access number. The partition in which the voice mail directory number resides Related Topics • • • • VoiceMailDN VoiceMailPartition Configuring Service Parameters. page 30-8 Configuring Cisco Messaging Interface Trace Parameters. page 35-1 Cisco Messaging Interface Service Parameters. page 10-22 Configuring Cisco Messaging Interface Service Parameters. Default value: COM1 Note The SerialPort name should be the same name that you see in Device Manager under NT. MwiSearchSpace The search space to use when determining the device to be affected by the MWI lamp. Type a colon-separated list of partition names for the value of this parameter. For example: dallas01:dallas02.

Cisco CallManager Administration Guide OL-1047-01 30-5 . Next. Refer to the “Server” section on page 11-1 for more information. • • Servers must be configured The Cisco CallManager must have Cisco Messaging Interface loaded whenever the Cisco CallManager is installed or upgraded. Click Service > Cisco Messaging Interface.Chapter 30 Cisco Messaging Interface Adding Cisco Messaging Interface Service on the Cisco CallManager Adding Cisco Messaging Interface Service on the Cisco CallManager This section describes how to add Cisco Messaging Interface service on the Cisco CallManager. go to Service > Service Parameters and select the appropriate server. The Value field should be the voice mail access number. displaying the server you selected. To enable the MWI button on your phone for it to access the voice mailbox. Before You Begin Be sure that the following requirements are met before proceeding with the any series of steps. Note To configure the Cisco CallManager. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Select the new server on which you want to add the Cisco Messaging Interface from the drop-down list box. click Cisco CallManager in the Configured Services list. and what the extension and mailbox length are on the voice mail. and select VoiceMail. you must know the voice mail access number and partition. The page refreshes. The Cisco CallManager service parameters MessageWaitingOffDN and MessageWaitingOnDN parameters do not apply to configuring Cisco Messaging Interface.

page 30-6 Configuring Cisco Messaging Interface Service Parameters. page 30-10 Deleting Cisco Messaging Interface Service From a Server This section describes how to delete Cisco Messaging Interface service from a server. page 30-8 Configuring Cisco Messaging Interface Trace Parameters. The page refreshes again. The Cisco CallManager must have Cisco Messaging Interface loaded whenever the Cisco CallManager is installed or upgraded. Refer to the “Server” section on page 11-1for more information. • • Servers must be configured. Related Topics • • • Deleting Cisco Messaging Interface Service From a Server. Before You Begin Be sure that the following requirements are met before proceeding with the any series of steps. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Cisco CallManager Administration Guide 30-6 OL-1047-01 .Chapter 30 Deleting Cisco Messaging Interface Service From a Server Cisco Messaging Interface Note The servers listed on the left side of the page are already configured with Cisco Messaging Interface service. Step 4 Click Insert. and the server is now configured with Cisco Messaging Interface service. Click Service > Cisco Messaging Interface.

page 30-8 Most Commonly Changed CMI Service Parameters. or Cancel to cancel the deletion. Click OK to continue. page 30-10 Cisco CallManager Administration Guide OL-1047-01 30-7 . Step 4 Step 5 Click Delete Service. the server should no longer appear in the list on the left side of the page. Note The servers listed on the left side of the page are already configured with Cisco Messaging Interface service. page 30-2 Configuring Cisco Messaging Interface Trace Parameters. A message displays stating that you are about to permanently delete service from this server.Chapter 30 Cisco Messaging Interface Deleting Cisco Messaging Interface Service From a Server Step 3 Select the server from which you want to delete the Cisco Messaging Interface service from the list on the left side of the page. page 30-5 Configuring Cisco Messaging Interface Service Parameters. Related Topics • • • • Adding Cisco Messaging Interface Service on the Cisco CallManager. If you chose Delete Service. The page refreshes displaying the server you selected.

Caution Do not add or delete service parameters unless directed by the Cisco Technical Assistance Center (TAC).Chapter 30 Configuring Cisco Messaging Interface Service Parameters Cisco Messaging Interface Configuring Cisco Messaging Interface Service Parameters This section describes how to configure Cisco Messaging Interface service parameters. Read the “Understanding Service Parameters” section on page 10-1 for more information on service parameters. Select the server on which you want to configure Cisco Messaging Interface service parameters from the list of servers on the left side of the page. Before You Begin Be sure that the following requirements are met before proceeding with any series of steps. displaying the server you selected. The page refreshes. • • • Servers must be configured. Click Service > Cisco Messaging Interface. Refer to the “Server” section on page 11-1. Use the operating system service manager or task manager to restart Cisco Messaging Interface if you need an instant update. Cisco CallManager Administration Guide 30-8 OL-1047-01 . Caution Cisco Messaging Interface can take up to five minutes to detect and load new parameters. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. The Cisco CallManager must have Cisco Messaging Interface loaded whenever the Cisco CallManager is installed or upgraded.

A message displays stating that you are about to permanently delete any previous settings and replace them with the default settings. page 30-10 Cisco CallManager Administration Guide OL-1047-01 30-9 . highlight the parameter in the Configured Service Parameters list. make changes using the Type and Value fields. Do not add or delete services parameters unless directed by the Cisco TAC. or Cancel to keep the current settings. page 35-1 Cisco Messaging Interface Service Parameters. Click OK to continue. We recommend you do not make any changes to service parameters unless you fully understand the feature that you are changing. or unless the changes are specified by the Cisco Technical Assistance Center (TAC). page 30-2 Configuring Service Parameters. page 10-22 Configuring Cisco Messaging Interface Trace Parameters. Refer to the “Understanding Service Parameters” section on page 10-1 for more information. then click Update. Caution Some changes to service parameters may cause system failure. Repeat Steps 2 through 5 for each service parameter you want to configure. Step 6 Note To restore Cisco CallManager default service parameter settings. Step 5 To make changes to an existing service parameter.Chapter 30 Cisco Messaging Interface Configuring Cisco Messaging Interface Service Parameters Note The servers listed on the left side of the page are already configured with Cisco Messaging Interface service. Step 4 Click Command Line Parameters if it is not already selected. Related Topics • • • • Most Commonly Changed CMI Service Parameters. click Default.

Caution Do not add or delete trace parameters unless directed by the Cisco Technical Assistance Center (TAC). and it should be enabled whenever Cisco Messaging Interface operations are in question. Cisco CallManager Administration Guide 30-10 OL-1047-01 . the Cisco Messaging Interface creates a trace file and logs its actions. This section provides detailed descriptions of trace levels and settings. Refer to the “Server” section on page 11-1.Chapter 30 Configuring Cisco Messaging Interface Trace Parameters Cisco Messaging Interface Configuring Cisco Messaging Interface Trace Parameters This section describes how to configure Cisco Messaging Interface trace parameters. Note If Trace is enabled. Click Service > Cisco Messaging Interface. • • • Servers must be configured The Cisco CallManager must have Cisco Messaging Interface loaded whenever the Cisco CallManager is installed or upgraded. Before You Begin The following prerequisites must be met before proceeding with the steps. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Refer to the “Configuring Trace” section on page 36-1 to configure trace parameters for this service. This trace file can be helpful when debugging Cisco Messaging Interface operations.

Click Trace On to enable trace. The page refreshes. Step 4 Step 5 Step 6 Click Trace. When you have completed your trace parameter selections.Chapter 30 Cisco Messaging Interface Configuring Cisco Messaging Interface Trace Parameters Step 3 Select the server on which you want to configure trace parameters. Click Show Time if you want a time associated with the mask. Select the type of trace event alarms you want from the Event drop-down menu. leave all User Mask boxes enabled. Click Show Date if you want a date associated with the trace level. click Update. If Trace On is not selected. For Cisco Messaging Interface. Select the level of trace you want from the Level drop-down menu. Note If you’d rather use the Cisco CallManager default settings. For CMI. Step 9 Step 10 Check the box for each trace component you want enabled. The user mask automatically appears in the Mask field. Note The servers listed on the left side of the page are already configured with Cisco Messaging Interface service. Step 7 Step 8 Note The level of trace event you want is determined by what you select from the drop-down menu. from the list of servers on the left side of the page. it is disabled and you will not be able to modify any trace properties. page 36-1 Cisco CallManager Administration Guide OL-1047-01 30-11 . Related Topics • Configuring Trace. set the trace level to either ERROR or DETAILED. click SetDefault.

Chapter 30 Configuring Cisco Messaging Interface Trace Parameters Cisco Messaging Interface Cisco CallManager Administration Guide 30-12 OL-1047-01 .

For more detailed TFTP information. TFTP is a simplified version of the FTP protocol.C H A P T E R 31 Configuring Cisco TFTP Cisco Trivial File Transfer Protocol (TFTP) is a Windows NT service that builds and serves files consistent with the TFTP protocol. refer to the following sections: • • Understanding DHCP and TFTP. The . page 7-4 Cisco CallManager Administration Guide OL-1047-01 31-1 .cnf file from the TFTP server. A configuration file is a list of Cisco CallManagers to which devices (telephones and gateways) make connections. If the Cisco CallManager’s name is received. The device requests a . a default gateway. If neither an IP address or name is received. and configuration (. the component queries a Dynamic Host Configuration Protocol (DHCP) server for its network configuration information.cnf file contains a list of Cisco CallManagers and the TCP port through which the device connects to those Cisco CallManagers. The DHCP server responds with an IP address for the device. runner files. When a device boots. a Domain Name System (DNS) server address. Cisco TFTP serves embedded component executable.cnf) files. the device resolves the name using DNS and a Cisco CallManager connection is opened. the default server name is used. a subnet mask. page 7-2 Understanding How Devices Identify the TFTP Server. and a TFTP server name or address.

• Servers must be configured Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. (Servers listed on the left side of the page have already been configured with TFTP service. Inserting Cisco TFTP Service on a Server This section describes how to insert Cisco TFTP service on a server. page 31-7 Configuring Cisco TFTP Trace Parameters. configure and delete Command Line Parameters.Chapter 31 Inserting Cisco TFTP Service on a Server Configuring Cisco TFTP Use the following procedures to insert and delete TFTP service from a server. page 31-5 Deleting Cisco TFTP Command Line Parameters. Note Service(s) are automatically inserted during the installation process. showing the server you selected.) The page refreshes. Before You Begin The following prerequisite must be met before proceeding with the steps. Cisco CallManager Administration Guide 31-2 OL-1047-01 . See the “Server” section on page 11-1. page 31-9 Note Under normal circumstances. default values are preferable. Click Service > Cisco TFTP. Select a server on which to insert Cisco TFTP service from the drop-down list box and click Insert. and to configure and delete TFTP Trace Parameters: • • • • • Inserting Cisco TFTP Service on a Server. page 31-4 Configuring Cisco TFTP Command Line Parameters. page 31-2 Deleting Cisco TFTP Service From a Server.

page 7-4 Configuring Cisco CallManager Groups. page 31-5 Deleting Cisco TFTP Command Line Parameters. Note You only need to configure Cisco TFTP service on one server in a network. then click Insert. page 13-1 Deleting Cisco TFTP Service From a Server. Tips Click New if you want to insert Cisco TFTP on another server. page 31-4 Configuring Cisco TFTP Command Line Parameters. page 31-1 Understanding DHCP and TFTP. page 31-7 Configuring Cisco TFTP Trace Parameters. page 31-9 Adding a Cisco CallManager Group. unless you want to share TFTP load. page 13-2 Cisco CallManager Administration Guide OL-1047-01 31-3 . This takes you back to the first Cisco TFTP Configuration page. You are now ready to configure either Command Line Parameters or Trace. page 7-2 Understanding How Devices Identify the TFTP Server.Chapter 31 Configuring Cisco TFTP Inserting Cisco TFTP Service on a Server Step 4 Select either Command Line Parameters or Trace. Related Topics • • • • • • • • • Configuring Cisco TFTP.

page 31-2 Configuring Cisco TFTP Command Line Parameters. • • Servers must be configured Cisco TFTP service must be configured Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. page 7-4 Configuring Cisco CallManager Groups. page 31-1 Understanding DHCP and TFTP. Before You Begin The following prerequisite must be met before proceeding with the steps. page 31-5 Deleting Cisco TFTP Command Line Parameters. A message displays stating that you are about to permanently delete this service. and that the action can not be undone. Click Service > Cisco TFTP. Click Delete Service. page 7-2 Understanding How Devices Identify the TFTP Server. page 13-1 Inserting Cisco TFTP Service on a Server.) The page refreshes showing the information for the server you selected.Chapter 31 Deleting Cisco TFTP Service From a Server Configuring Cisco TFTP Deleting Cisco TFTP Service From a Server This section describes how to delete Cisco TFTP service from a server. Select the server from which you want to delete Cisco TFTP service from the list of servers on the left side of the page. Step 4 Step 5 Related Topics • • • • • • • Configuring Cisco TFTP. page 31-7 Cisco CallManager Administration Guide 31-4 OL-1047-01 . Click OK. See the “Server” section on page 11-1. If you wish to continue this deletion. otherwise click Cancel. (Servers listed on the left side of the page have already been configured with Cisco TFTP service.

page 31-9 Adding a Cisco CallManager Group. • • • Servers must be configured Cisco TFTP service must be configured Before configuring any Cisco TFTP service parameters. If you choose a server from the drop-down list box.Chapter 31 Configuring Cisco TFTP Configuring Cisco TFTP Command Line Parameters • • Configuring Cisco TFTP Trace Parameters. Select the server on which you want to configure command line parameters from either the drop-down list box. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. read the “Understanding Service Parameters” section on page 10-1. you must first add Cisco TFTP service to the server before configuring any command line parameters. page 13-2 Configuring Cisco TFTP Command Line Parameters This section describes how to configure Cisco TFTP command line parameters. See the “Server” section on page 11-1. Note The list of servers on the left side of the page are already configured with TFTP service. Cisco CallManager Administration Guide OL-1047-01 31-5 . The page refreshes. Step 4 Click Command Line Parameters if it is not already selected. Click Service > Cisco TFTP. Refer to the “Cisco TFTP Service Parameters” section on page 10-20 for service parameters specific to Cisco TFTP. Before You Begin The following prerequisite must be met before proceeding with the steps. or the list of servers on the left side of the page.

click Default. Repeat Steps 1 through 8 to add additional service parameters. Related Topics • • • Configuring Cisco TFTP. Enter the type of the parameter in the Type field. Click Update. Step 5 Step 6 Note The drop-down list box contains parameter types that have already been configured. Click OK if you wish to continue. Step 7 Step 8 Step 9 Enter a value for the parameter in the Value field. Refer to the “Understanding Service Parameters” section on page 10-1 for more information. A message displays stating that you are about to permanently delete any previous settings and replace them with the default settings. The page refreshes and your new service parameter appears in the Configured Service Parameters list at the bottom of the page. page 7-2 Understanding How Devices Identify the TFTP Server. Note If you would rather use the Cisco CallManager default service parameters. page 31-1 Understanding DHCP and TFTP. You will probably never need to add parameters unless directed by the Cisco TAC.Chapter 31 Configuring Cisco TFTP Command Line Parameters Configuring Cisco TFTP Caution Some changes to service parameters may cause system failure. We recommend you do not make any changes to service parameters unless you fully understand the feature that you are changing. page 7-4 Cisco CallManager Administration Guide 31-6 OL-1047-01 . or choose a type from the drop-down list box. Enter the name of the parameter you want to configure on this server in the Param field. or Cancel to keep the current settings. or unless the changes are specified by the Cisco Technical Assistance Center (TAC).

page 31-7 Configuring Cisco TFTP Trace Parameters. • • • • Servers must be configured Cisco TFTP service must be configured Command line parameters must be configured Before deleting any Cisco TFTP service parameters. Before You Begin The following prerequisite must be met before proceeding with the steps. page 13-1 Inserting Cisco TFTP Service on a Server. Click Service > Cisco TFTP. page 13-2 Deleting Cisco TFTP Command Line Parameters This section describes how to delete Cisco TFTP command line parameters. read the “Understanding Service Parameters” section on page 10-1. Refer to the “Cisco TFTP Service Parameters” section on page 10-20 for service parameters specific to Cisco TFTP. Select the server from which you want to delete command line parameters from the list of servers on the left side of the page. page 31-2 Deleting Cisco TFTP Service From a Server. page 31-9 Adding a Cisco CallManager Group. See the “Server” section on page 11-1. Caution You will never need to delete parameters unless directed by the Cisco Technical Assistance Center (TAC).Chapter 31 Configuring Cisco TFTP Deleting Cisco TFTP Command Line Parameters • • • • • • Configuring Cisco CallManager Groups. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 31-7 . page 31-4 Deleting Cisco TFTP Command Line Parameters.

The parameter you deleted should no longer appear in the list of configured service parameters. Highlight the service parameter you want to delete from the list of configured service parameters at the bottom of the page. page 31-2 Deleting Cisco TFTP Service From a Server. page 13-2 Cisco CallManager Administration Guide 31-8 OL-1047-01 . Click OK if you wish to delete the parameter. A message displays stating that you are about to permanently delete this parameter. Related Topics • • • • • • • • Configuring Cisco TFTP. page 31-4 Configuring Cisco TFTP Command Line Parameters. and that this action cannot be undone. Click Delete. page 7-2 Understanding How Devices Identify the TFTP Server. page 31-5 Configuring Cisco TFTP Trace Parameters.Chapter 31 Deleting Cisco TFTP Command Line Parameters Configuring Cisco TFTP Step 4 Step 5 Step 6 Step 7 Step 8 Click Insert. page 31-1 Understanding DHCP and TFTP. The page refreshes. or Cancel to cancel the deletion. Click Command Line Parameters if it is not already selected. page 31-9 Adding a Cisco CallManager Group. page 7-4 Inserting Cisco TFTP Service on a Server.

The page refreshes.Chapter 31 Configuring Cisco TFTP Configuring Cisco TFTP Trace Parameters Configuring Cisco TFTP Trace Parameters This section describes how to configure Cisco TFTP trace parameters. or deselect Trace On. Select the server on which you want to configure trace parameters from either the drop-down list box. • • • Servers must be configured Cisco TFTP service must be configured Read the “Configuring Trace” section on page 36-1 before configuring trace parameters. For more detailed trace information refer to the “Configuring Trace” section on page 36-1. If Trace On is not selected. You can access Trace via the Service menu in the Cisco CallManager Administration application. Caution We recommend that you configure all trace parameters from the Trace configuration pages. Click Trace. However. Cisco does not recommend deleting any parameters without the assistance of the Cisco Technical Assistance Center (TAC). Click Service > Cisco TFTP. Before You Begin The following prerequisite must be met before proceeding with the steps. If you want to delete the trace. you can either click the Delete button. it is disabled and you will not be able to modify any trace properties. This section provides detailed descriptions of trace levels and settings. See the “Server” section on page 11-1. Select Trace On to enable trace. Step 4 Step 5 Cisco CallManager Administration Guide OL-1047-01 31-9 . Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. or the list of servers on the left side of the page.

page 7-2 Understanding How Devices Identify the TFTP Server. DEBUG is used for lab purposes and traces every event on the system. Select the type of trace event alarms you want from the Event drop-down list box. page 31-1 Understanding DHCP and TFTP. Related Topics • • • • • • • • Configuring Cisco TFTP. When you have completed your trace parameter selections. page 31-7 Adding a Cisco CallManager Group. For instance. page 13-2 Cisco CallManager Administration Guide 31-10 OL-1047-01 . Select the level of trace you want from the Level drop-down list box.Chapter 31 Configuring Cisco TFTP Trace Parameters Configuring Cisco TFTP Step 6 Check each User Mask check box you want enabled. Step 9 Step 10 Check the box of each trace component you want enabled. Step 7 Step 8 Note The level of trace event you want is determined by what you select from the drop-down list box. page 31-2 Deleting Cisco TFTP Service From a Server. page 31-4 Configuring Cisco TFTP Command Line Parameters. page 7-4 Inserting Cisco TFTP Service on a Server. page 31-5 Deleting Cisco TFTP Command Line Parameters. Click the Show Time check box if you want a time associated with the trace. while CRITICAL only traces critical alarms. Note If you’d rather use the default settings. The user mask automatically appears in the Mask field. click Update. Click the Show Date check box if you want a date associated with the trace level. click SetDefault.

page 32-14 Setting Up the wauser Shared Directory for Cisco WebAttendant. page 32-19 Starting the Telephony Call Dispatcher. page 32-13 Configuring Cisco WebAttendant Client Settings. page 8-1 Cisco CallManager Administration Guide OL-1047-01 32-1 . enables you to set up Cisco IP Phones as attendant consoles. monitoring phone status. This section describes the following configuration procedures for Cisco WebAttendants: • • • • • • Configuring Pilot Points. a client-server application. and directing calls. or an individual can use it with a Cisco IP Phone. page 32-2 Configuring Hunt Groups. A receptionist or administrative assistant can use the Cisco WebAttendant client to handle calls. The Cisco WebAttendant client provides a graphical user interface for controlling a Cisco IP Phone for use as an attendant console and includes speed dial buttons and quick directory access for looking up phone numbers. page 32-5 Installing the Cisco WebAttendant Client.C H A P T E R 32 Configuring Cisco WebAttendants Cisco WebAttendant. page 32-20 Related Topics • Understanding Cisco WebAttendant.

Enter the appropriate settings as described in Table 32-1. Cisco CallManager Administration Guide 32-2 OL-1047-01 . page 32-1 Understanding Pilot Points and Hunt Groups. Related Topics • • • • Adding a Pilot Point. The order in which the members of the hunt group are listed determines the call redirection order. the Pilot Point Configuration page refreshes to display the name of the new pilot point in the list on the left. Click Insert. Once the pilot point is created. page 32-2 Viewing. page 8-6 Adding a Pilot Point Procedure Perform the following steps to add a new pilot point. page 32-4 Configuring Cisco WebAttendants. Updating. or Deleting a Pilot Point. Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. The new pilot point and its settings display. Choose Service > Cisco WebAttendant. Now that the pilot point is created. The first available (not busy) member in a hunt group receives the call. you must configure a hunt group to specify how the calls that come in to the pilot point are redirected.Chapter 32 Configuring Pilot Points Configuring Cisco WebAttendants Configuring Pilot Points Ensure pilot points and hunt groups are configured before the Cisco Telephony Call Dispatcher can route calls to Cisco WebAttendant A Cisco WebAttendant pilot point serves as a virtual directory number that receives and redirects calls to the members of its associated hunt group.

or Deleting a Pilot Point. Updating. page 32-4 Configuring Hunt Groups. Ensure directory-based hunt group members associated with a Cisco WebAttendant pilot point are in a partition that is visible to the calling search space for the pilot point number. page 8-6 Cisco CallManager Administration Guide OL-1047-01 32-3 . Choose a calling search space from the drop-down list. Take call processing and device load balancing into account when selecting the Primary Cisco CallManager. do not use partitions. Partition Calling Search Space Choose None from the drop-down Cisco WebAttendant pilot points list box. Related Topics • • • Viewing. Ensure this number is unique throughout the system (that is.Chapter 32 Configuring Cisco WebAttendants Configuring Pilot Points Table 32-1 Pilot Point Configuration Settings Field Device Information Description Usage Notes Pilot Name Primary Cisco CallManager Specifies descriptive name for the Enter up to 50 characters. it cannot be a shared line appearance). The calling search space determines which partitions the pilot point searches when attempting to route a call. page 32-5 Understanding Pilot Points and Hunt Groups. Specifies name or IP address of the Cisco CallManager whose Telephony Call Dispatcher (TCD) service will be used to service this pilot point. pilot point. Pilot Number (DirN) Designates directory number for this pilot point.

Step 3 Step 4 Step 5 Click the name of the pilot point you wish to modify or delete. The page refreshes to display information for the selected pilot point. page 8-6 Cisco CallManager Administration Guide 32-4 OL-1047-01 . and the list on the left side of the page shows all currently configured pilot points. update. page 32-5 Understanding Pilot Points and Hunt Groups. Choose Service > Cisco WebAttendant. After you delete a pilot point. Note You do not have to restart TCD or Cisco CallManager after deleting a pilot point for the deletion to take effect. or Deleting a Pilot Point Perform the following steps to view. Related Topics • • • Adding a Pilot Point. page 32-2 Configuring Hunt Groups. Make the desired changes. or delete pilot points. Refer to Table 32-1 for a description of pilot point configuration settings. The Pilot Point Configuration page displays. Updating.Chapter 32 Configuring Pilot Points Configuring Cisco WebAttendants Viewing. Procedure Step 1 Step 2 Open Cisco CallManager Administration. TCD will stop directing calls to any hunt group members associated with that pilot point within approximately 10 minutes. Click Update to modify the pilot point or click Delete to remove the pilot point.

page 32-9 Understanding Pilot Points and Hunt Groups. The Pilot Hunt Group Members list initially displays the text <<not configured>>. Click New. A hunt group provides a list of destinations (either directory numbers or Cisco WebAttendant user /line number references) that are used to determine the call redirection order for calls received by the pilot point. or Deleting Hunt Group Members. you must configure a hunt group to specify how the calls that come in to the pilot point number are redirected. Choose the pilot point for which you want to add hunt group members. Step 4 Step 5 Cisco CallManager Administration Guide OL-1047-01 32-5 . page 32-5 Viewing. A list of available pilot points appears on the left side of the Pilot Point Configuration page. The Pilot Point Configuration page displays.Chapter 32 Configuring Cisco WebAttendants Configuring Hunt Groups Configuring Hunt Groups Once you have created a pilot point. Choose Service > Cisco WebAttendant. Updating. This section covers the following procedures: • • • Adding Hunt Group Members. page 8-6 Adding Hunt Group Members Procedure Perform the following steps to add a list of hunt group members to a new pilot point: Step 1 Step 2 Step 3 Open Cisco CallManager Administration. The first available (not busy) member of the hunt group receives the call. Click the link to Hunt Group Configuration in the upper right corner of the Pilot Point Configuration page to add hunt group members to this pilot point.

Step 7 Enter the appropriate configuration settings for the new hunt group member as described in Table 32-2. TCD first checks whether the Cisco WebAttendant user is logged in to a Cisco WebAttendant client and online before attempting to route the call. If you specify a Cisco WebAttendant user and line number. • If the hunt group member is a directory number. • • If you specify a directory number. fill in only the Cisco WebAttendant User Name and Line Number fields in the User Member Information section. Line 1 (user and line number example) Cisco CallManager Administration Guide 32-6 OL-1047-01 . It is not the same as a User ID that is added through the Cisco CallManager User area of Cisco CallManager Administration.Chapter 32 Configuring Hunt Groups Configuring Cisco WebAttendants Step 6 Decide whether the hunt group member you want to add will be a directory number (device member) or a user and line number (user member). Refer to “Adding a Cisco WebAttendant User” section on page 32-10 for more information. As you make selections. The advantage to specifying a user and line number is that the user can be logged in to any Cisco IP Phone controlled by Cisco WebAttendant software in the cluster and still receive calls. for example: #1 Call directory number 35201 (directory number example) #2 Direct Call to Mary Brown. TCD always attempts to route the call to that number. The Hunt Group Member list displays either the device directory number or the Cisco WebAttendant user name and line number. You cannot specify a partition or a directory number if the hunt group member is a Cisco WebAttendant user. You cannot specify a user name or a line number if the hunt group member is a directory number. fill in only the Partition and Directory Number fields in the Device Member Information section. • Note The User Name you specify is a Cisco WebAttendant User ID. The optional Always Route Member check box also applies only to directory numbers. If the hunt group member is a user and line number. the Hunt Group Member list box reflects the information you choose.

Telephony Call Dispatcher (TCD) always routes the call to this hunt group member. • If the directory number is not in a Note partition. whether it is busy or not. simultaneous calls. choose None. such as voicemail devices. Ensure directory number-based hunt group members are in a partition that can be seen from the calling search space of the associated pilot point. you must choose a partition. • Usage Notes You can only choose a partition for a directory-number-based hunt group member. If a partition is specified. The TCD does not check whether the line is available before routing the call. Directory Number Designates directory number of the hunt group member device. and the directory number is not in that partition. Always Route Member If this box is checked (enabled).Chapter 32 Configuring Cisco WebAttendants Configuring Hunt Groups Table 32-2 Hunt Group Configuration Settings Field Partition Description Designates route partition to which this directory number belongs. You cannot enter a user name or line number if a directory number is specified in this field. Cisco CallManager Administration Guide OL-1047-01 32-7 . You can enable this option for devices that can handle multiple. an error dialog box displays. Device Member Information (These fields only apply to directory number-based hunt group members) If the directory number for this hunt group member is in a partition. Specify Always Route Member only for directory-number-based hunt group members. You cannot choose a partition for a user and line number-based hunt group member.

Note Be sure to consider overflow conditions when assigning hunt group members. Provides drop-down list of line numbers to choose. If TCD can see the line state of a voicemail number. enable the “Always Route Calls” option for that number. When you define a user and line number pair as a hunt group member.Chapter 32 Configuring Hunt Groups Configuring Cisco WebAttendants Table 32-2 Hunt Group Configuration Settings (continued) Field User Name Description Usage Notes User Member Information (these fields apply only to user and line number hunt group members) Designates name of the Choose a user name from the Cisco WebAttendant user to choose as drop-down list. you can handle overflow conditions by having one or more hunt groups that route calls to multiple Cisco WebAttendants with the final directory number being voicemail. Otherwise. If the user is not online. Line Number Step 8 Repeat Steps 6 through 8 to add more hunt group members to this pilot point. Cisco CallManager Administration Guide 32-8 OL-1047-01 . For example. You can change the order of the members in the hunt group by selecting the member you want to reorder from the list and using the up and down arrows to move that member to a new position in the list. Only user names that a hunt group member. TCD automatically goes to the next member of the hunt group. the voicemail number will not receive more than one call at a time. were added using Cisco WebAttendant User Configuration appear in this list. the Telephony Call Dispatcher first checks whether that user is logged in to Cisco WebAttendant and online.

modify the settings as needed. page 32-9 Understanding Pilot Points and Hunt Groups. • • To update settings for a hunt group member. modify. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Refer to Table 32-2 for a description of hunt group configuration settings.Chapter 32 Configuring Cisco WebAttendants Configuring Hunt Groups Step 9 Click Update to save the hunt group member information. The Pilot Point Configuration page displays. or Deleting Hunt Group Members. Updating. select the name of the member you wish to move and use the arrow buttons to move it to a new position in the list. click Update to save the changes. To change the order of the hunt group members. or delete members of a hunt group. and the list on the left side of the page displays all currently configured pilot points. Updating. or Deleting Hunt Group Members Perform the following procedure to view. select that member’s name in the list. The hunt group members are added to the pilot point. then. or delete members. Related Topics • • Viewing. page 8-6 Viewing. Choose Service > Cisco WebAttendant. Step 5 Make any desired changes. The Hunt Group Configuration group page displays. update. Step 3 Click the Hunt Group Configuration link at the top of the page. The Hunt Group Configuration page updates to display information for the chosen pilot point. Cisco CallManager Administration Guide OL-1047-01 32-9 . Step 4 Click the name of the pilot point associated with the hunt group for which you want to view.

Related Topics • • Adding Hunt Group Members. page 8-6 Configuring Cisco WebAttendant Users This section covers the following procedures: • • Adding a Cisco WebAttendant User. Note Cisco WebAttendant user IDs and passwords are not the same as Directory users and passwords entered in the User area of Cisco CallManager. Cisco CallManager Administration Guide 32-10 OL-1047-01 . The Cisco WebAttendant user and password database is completely separate from the Cisco CallManager Directory user database. and Deleting Cisco WebAttendant Users. page 32-10 Viewing. page 32-11 Adding a Cisco WebAttendant User Users cannot log in to a Cisco WebAttendant client before they are added in Cisco WebAttendant User Configuration.Chapter 32 Configuring Cisco WebAttendant Users Configuring Cisco WebAttendants • • Step 6 To delete a hunt group member. page 32-5 Understanding Pilot Points and Hunt Groups. Click Update to save the changes before leaving the Hunt Group Member Configuration screen. Updating. highlight that member’s name in the list and click Delete. You can press Cancel at any time to restore any settings you changed before clicking Update.

Repeat Steps 4 and 5 to add additional users. Cisco WebAttendant ignores this setting. Step 5 Step 6 Click Insert to add the new user. page 8-1 Cisco CallManager Administration Guide OL-1047-01 32-11 . Table 32-3 Cisco WebAttendant User Configuration Settings Field User ID Password Confirm Station Type Action/Description Enter the login name for the new Cisco WebAttendant user. The Cisco WebAttendant User Configuration page refreshes. and Deleting Cisco WebAttendant Users. Choose Service > Cisco WebAttendant. Click the Cisco WebAttendant User Configuration link in the upper right corner of the page. Not used. page 32-11 Understanding Cisco WebAttendant. Enter the appropriate configuration settings as described in Table 32-3. Updating.Chapter 32 Configuring Cisco WebAttendants Configuring Cisco WebAttendant Users Procedure Perform the following procedure to add a Cisco WebAttendant user. Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Re-enter the same password. and the new User ID displays in the list on the left side of the page. Related Topics • • Viewing. Enter a password of up to 50 alphanumeric characters. If specified. Enter up to 50 alphanumeric characters.

Refer to Table 32-3 for a description of Cisco WebAttendant user configuration settings. Choose Service > Cisco WebAttendant. click Delete to remove the user. Step 4 Step 5 Step 6 Click the name of the user you wish to modify or delete. or delete Cisco WebAttendant users. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. update.Chapter 32 Configuring Cisco WebAttendant Users Configuring Cisco WebAttendants Viewing. The Cisco WebAttendant User Configuration page displays with a list of current users on the left side of the page. right corner of the page. and Deleting Cisco WebAttendant Users Perform the following procedure to view. page 32-10 Understanding Cisco WebAttendant. Related Topics • • Adding a Cisco WebAttendant User. Click Update to save the changes. Click the Cisco WebAttendant User Configuration link in the upper. Make the desired changes. page 8-1 Cisco CallManager Administration Guide 32-12 OL-1047-01 . or click Cancel to exit the screen without making any changes. Updating.

Password — Enter the Cisco WebAttendant password for user ID just specified. hexadecimal number located on a label on the underside of the Cisco IP Phone. Log in to the PC on which you want to install the Cisco WebAttendant client. Step 11 Click Next. Choose Application > Install Plugins. Cisco CallManager Administration Guide OL-1047-01 32-13 . The Cisco WebAttendant installation wizard runs. Procedure Step 1 Ensure you have added the Cisco WebAttendant user and the phone you wish to associate with Cisco WebAttendant to the Cisco CallManager database (refer to the “Adding a Cisco WebAttendant User” section on page 32-10). Click Next to install the Cisco WebAttendant client to the default location or use the Browse button to specify a new location and then click Next. Choose a Program Folder and click Next. Open Internet Explorer (version 4. The MAC address comprises a 12-character. browse to Cisco CallManager Administration. Enter the following information on the Customer Information screen: • • Login ID — Enter the Cisco WebAttendant user ID for the attendant. click Yes to accept the License Agreement. then.0 or greater). and log in to Cisco CallManager Administration. Click the icon for the Cisco WebAttendant client. Write down the MAC address of the phone that is to be associated with the Cisco WebAttendant client you are installing. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Click Next at the initial screen.Chapter 32 Configuring Cisco WebAttendants Installing the Cisco WebAttendant Client Installing the Cisco WebAttendant Client Perform the following steps to install the Cisco WebAttendant Client on a user’s PC.

After the installation program finishes installing files. you can configure or update any client settings that you did not configure during the installation process. MAC ID — Enter MAC address of the Cisco IP Phone that will be used with Cisco WebAttendant (see Step 2 for a description of the MAC address). the Cisco WebAttendant client operates with the specified settings until they are changed. You must use uppercase letters when entering the MAC address. choose whether you want to restart the computer now or later. page 8-1 Configuring Cisco WebAttendant Client Settings After the Cisco WebAttendant client is installed. Once the application is installed. click Finish. to view current settings. page 32-14 Adding a Cisco WebAttendant User. Once it is configured. or to update the client configuration. Refer to “Configuring Cisco WebAttendant Client Settings” section on page 32-14 for more information. Cisco CallManager Administration Guide 32-14 OL-1047-01 .Chapter 32 Configuring Cisco WebAttendant Client Settings Configuring Cisco WebAttendants Step 12 Enter the following information: • IP Address — Enter IP address or host name of the primary Cisco CallManager for TCD (usually the Cisco CallManager with which the Cisco WebAttendant phone is registered). Use the procedure in this section to configure settings that were not specified during installation. Restart the computer. • Step 13 Step 14 Step 15 Click Next. Related Topics • • • Configuring Cisco WebAttendant Client Settings. page 32-10 Understanding Cisco WebAttendant. then. you must configure it before a user can log into Cisco WebAttendant.

Click OK. Step 2 Step 3 Step 4 Note If the Cisco WebAttendant client does not display directory information. page 8-1 Setting Up the wauser Shared Directory for Cisco WebAttendant.Chapter 32 Configuring Cisco WebAttendants Configuring Cisco WebAttendant Client Settings Procedure Step 1 On the PC where the Cisco WebAttendant is installed. check whether the wauser shared directory is configured correctly and that the Cisco WebAttendant user and client PC have read/write access to the wauser shared directory. Click Settings. Related Topics • • • Installing the Cisco WebAttendant Client. Enter the appropriate configuration settings. as described in Table 32-4. page 32-19 Cisco CallManager Administration Guide OL-1047-01 32-15 . then. The settings for Cisco WebAttendant client have been configured and can now be used for call distribution activities. See the “Setting Up the wauser Shared Directory for Cisco WebAttendant” section on page 32-19 for instructions. page 32-13 Understanding Cisco WebAttendant. click Yes to allow the ActiveX controls to launch Cisco WebAttendant. choose Start > Programs > Cisco CallManager > Cisco WebAttendant.

if you manually specify a TCD Database Path in the Settings dialog for the client.mdb or C:\Program Files\Cisco\UsersDB2. The MAC address comprises a 12-character number on a label on the underside of the Cisco IP Phone. This is the recommended default setting. You must use uppercase letters. You must enter SEP. Also. Cisco CallManager Administration Guide 32-16 OL-1047-01 . you must restart the client for the change to take effect.Chapter 32 Configuring Cisco WebAttendant Client Settings Configuring Cisco WebAttendants Table 32-4 Cisco WebAttendant User Configuration Settings Field MAC Address Action Enter SEP plus the media access control (MAC) address for the Cisco IP Phone you want to use in conjunction with Cisco WebAttendant. any database changes made through Cisco CallManager are not automatically made available to the Cisco WebAttendant client. If you change the TCD Database Path setting for a Cisco WebAttendant client. As an alternative to using the default setting (leaving the field blank). Refer to the “Setting Up the wauser Shared Directory for Cisco WebAttendant” section on page 32-19 for additional steps required to ensure that this setting works correctly. SEP0010EB001234. You must manually copy a new version of the database file to the new location when you need to update Cisco WebAttendant clients with database changes. copy the file on the Cisco CallManager server named C:\Program Files\Cisco\Users\UsersDB1. eliminating any dashes. If you choose to do this. Cisco TCD Database Leave this setting blank if you want to use the default Path database from the TCD associated with this Cisco IP Phone.mdb to a different location (such as a file in a different shared directory on the network or a file on the Cisco WebAttendant user’s PC) and enter the path to the file in this field. the client uses that path until you change it. for example. then the MAC address.

Cisco Telephony Call Dispatcher (TCD) Settings IP Port WebAttendant User ID Note The Cisco WebAttendant User ID is not the same as a Cisco CallManager User ID entered in the User area of Cisco CallManager Administration. Note The Cisco WebAttendant password is not the same as a Cisco CallManager password entered in the User area of Cisco CallManager Administration. Refer to the “Adding a Cisco WebAttendant User” section on page 32-10 for more information. Designates User ID for this Cisco WebAttendant user as specified in the Cisco WebAttendant User Configuration page Cisco CallManager Administration.Chapter 32 Configuring Cisco WebAttendants Configuring Cisco WebAttendant Client Settings Table 32-4 Cisco WebAttendant User Configuration Settings (continued) Field IP Address or Host Name Action Enter the IP address or host name of the TCD server. This entry designates the Cisco CallManager to which the Cisco IP Phone specified by MAC address field is normally registered. Refer to the “Adding a Cisco WebAttendant User” section on page 32-10 for more information. The default value is 4321. WebAttendant Password Specifies password for this Cisco WebAttendant user as specified in the Cisco WebAttendant User Configuration page in Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 32-17 . Do not modify this value.

IP Port Related Topics • • • Installing the Cisco WebAttendant Client. Line State Server Settings IP Address or Host Name Enter the IP address or host name of the line state server. Connected To Designates view-only field that displays the IP address of the Line State Server to which this Cisco WebAttendant client is currently connected. Designates line state server IP port number. page 32-19 Understanding Cisco WebAttendant.Chapter 32 Configuring Cisco WebAttendant Client Settings Configuring Cisco WebAttendants Table 32-4 Cisco WebAttendant User Configuration Settings (continued) Field Connected To Action Designates view-only field that displays the IP address of the Cisco CallManager to which this Cisco WebAttendant client is currently connected. This entry usually designates the same as the Cisco CallManager to which the Cisco IP Phone specified by the MAC address field is registered. Do not change this setting unless advised to do so by the Cisco Technical Assistance Center. page 8-1 Cisco CallManager Administration Guide 32-18 OL-1047-01 . page 32-13 Setting Up the wauser Shared Directory for Cisco WebAttendant. The default value is 3224.

Doing so may cause system failure. page 10-1 Understanding Trace Configuration. page 8-1 Cisco CallManager Administration Guide OL-1047-01 32-19 . LSS Listen Port—This TCP port designates where Cisco WebAttendant clients register with TCD for line and device state information.Chapter 32 Configuring Cisco WebAttendants Cisco WebAttendant Server Configuration Cisco WebAttendant Server Configuration The Cisco WebAttendant Server Configuration page lists service parameters and enables you to configure trace parameters for the Telephony Call Dispatcher (TCD). The default value is 4321. The following service parameters are specific to TCD: Caution Do not change any of the listed service parameters without permission of a Cisco Technical Assistance Center engineer. page 36-2 Understanding Cisco WebAttendant. TCDServ Listen Port—This TCP port designates where Cisco WebAttendant clients register with TCD for call control. The default value is 3221. The default value is 3223. • • • Related Topics • • • Understanding Service Parameters. LSS Access Password—This default password used at registration authenticates the line state server. • CCN Line State Port—This designates the TCP/IP port number in Cisco Call Manager that is used by the line state server to register and receive line and device information.

Note If you are running Cisco CallManager in a cluster environment. Change the default share name from “Users” to “wausers.mdb. Step 1 Step 2 Log in to the Cisco CallManager server.” The share name is not case-sensitive. Ensure security and share permissions are set so that all Cisco WebAttendant client users have read and write access for this folder on the Cisco CallManager server. Perform this procedure on every Cisco CallManager in the cluster. Cisco CallManager Administration Guide 32-20 OL-1047-01 . Step 7 Step 8 Click OK to apply the changes and close the Properties dialog. Click the Sharing tab. perform this procedure on every Cisco CallManager in the cluster.Chapter 32 Setting Up the wauser Shared Directory for Cisco WebAttendant Configuring Cisco WebAttendants Setting Up the wauser Shared Directory for Cisco WebAttendant You must perform the following procedure to ensure that the Cisco WebAttendant client can display the directory information from the Cisco CallManager directory database. The share name must be “wausers” for this to work properly. Step 3 Step 4 Step 5 Step 6 Right-click on the Users folder and choose Properties. Click Shared As.mdb and UsersDB2. Use Windows Explorer to browse to the following folder: C:\Program Files\Cisco\Users The Cisco WebAttendant client must have read/write access to the following two files in this directory to build its user directory information: UsersDB1.

Chapter 32 Configuring Cisco WebAttendants Starting the Telephony Call Dispatcher Note To ensure that the changes made to the Shared As properties are visible to Cisco WebAttendant clients. Coose a Cisco CallManager server from the server list on the left side of the page. Cisco CallManager automatically makes directory database information available to Cisco WebAttendant clients and updates the information every 24 hours with the latest changes. page 8-1 Starting the Telephony Call Dispatcher The Telephony Call Dispatcher (TCD) service starts up automatically when Cisco CallManager is started. you must wait approximately 6 minutes for the changes to take effect. Procedure Step 1 Step 2 Choose Service > Control Center. The page refreshes. have the Cisco WebAttendant users exit the client and log out of Windows and then log back in. Related Topics • • Sharing Default Directory Database Information. The following procedure describes how to verify that the TCD service is running and how to start TCD if it is stopped. Note If you add new Cisco WebAttendant users or modify the user information or password for an existing user. Cisco CallManager Administration Guide OL-1047-01 32-21 . The Service Name column lists all services that are configured on this server. page 8-11 Understanding Cisco WebAttendant.

click the Start button in the Service Control column. • • If an arrow icon displays. Step 4 If the TCD service is not running. the TCD service is running If a square icon displays. page 8-1 Cisco CallManager Administration Guide 32-22 OL-1047-01 . page 8-6 Understanding Cisco WebAttendant. the TCD service is stopped.Chapter 32 Starting the Telephony Call Dispatcher Configuring Cisco WebAttendants Step 3 Look at the Service Status column for the Cisco Telephony Call Dispatcher. Related Topics • • Understanding Pilot Points and Hunt Groups.

page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc. page 33-15 Deleting a Meet-Me Number Pattern.0 and later) is an application designed to allow both Ad-Hoc and Meet-Me voice conferencing. page 33-3 Using an Ad-Hoc Conference Bridge. multi-party conferences. page 33-6 Adding a Hardware Conference Device.C H A P T E R 33 Configuring Conference Bridges Conference Bridge for Cisco CallManager (release 3. page 33-11 Updating Conference Bridge Parameters. Each conference bridge is capable of hosting several simultaneous. page 33-8 Updating a Conference Device. page 33-17 Cisco CallManager Administration Guide OL-1047-01 33-1 . page 33-12 Adding a Meet-Me Number Pattern. page 33-10 Deleting a Conference Device. Related Topics • • • • • • • • • • • • Understanding Conference Devices. Note The hardware model type for Conference Bridge contains a specific Media Access Control (MAC) address and device pool information. page 33-4 Using a Meet-Me Conference Bridge. page 33-14 Updating a Meet-Me Number Pattern. page 33-5 Adding a Software Conference Device.

Chapter 33 Understanding Conference Devices

Configuring Conference Bridges

Understanding Conference Devices
For conferencing, you must determine the total number of concurrent users (or audio streams) required at any given time. Then you create and configure a device to support the calculated number of streams. These audio streams can be used for one large conference, or several small conferences. For example, a conference device that was created with 20 streams would provide for one conference of 20 participants, or five conferences with four participants each (or any other combination that adds up to 20 total participants). The total number of conferences supported by each conference device is calculated by taking the total number of streams (for example, 20) and dividing by three. Therefore, in the example, you can have twenty divided by three (20/3) or six conferences supported by the conference device.

Caution

Although conference devices can be installed on the same PC as the Cisco CallManager, we strongly recommend against this. If conference devices are installed on the same PC as the Cisco CallManager, it can adversely affect the performance on the Cisco CallManager.

Note

Conference devices configured only for software support G.711 codecs, however, configuring for hardware provides transcoding for G.711, G.729 and G.723 codecs.
Related Topics
• • • • • • • •

Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using an Ad-Hoc Conference Bridge, page 33-4 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8 Updating a Conference Device, page 33-10 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12

Cisco CallManager Administration Guide

33-2

OL-1047-01

Chapter 33

Configuring Conference Bridges Two Types of Conferences: Meet-Me and Ad-Hoc

• • •

Adding a Meet-Me Number Pattern, page 33-14 Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Two Types of Conferences: Meet-Me and Ad-Hoc
Cisco CallManager supports both Meet-Me conferences and Ad-Hoc conferences. Meet-Me conferences allow users to dial into a conference. Ad-Hoc conferences allow the conference controller to let only certain participants into the conference. Meet-Me conferences require that a range of directory numbers be allocated for their exclusive use. When a Meet-Me conference is set up, the conference controller selects a directory number and advertises it to members of the group. The users call the directory number to join the conference. Anyone who calls the directory number while the conference is active, joins the conference. (This is true provided that the maximum number of participants specified for that conference type has not been exceeded, and sufficient streams are available on the conference device.) Ad-Hoc conferences are controlled by the conference controller. The conference controller individually calls and adds each participant to the conference. Any number of parties can be added to the conference up to the maximum number of participants specified for Ad-Hoc conferences, and provided that sufficient streams are available on the conference device.
Related Topics
• • • • • • • •

Understanding Conference Devices, page 33-2 Using an Ad-Hoc Conference Bridge, page 33-4 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8 Updating a Conference Device, page 33-10 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12

Cisco CallManager Administration Guide OL-1047-01

33-3

Chapter 33 Two Types of Conferences: Meet-Me and Ad-Hoc

Configuring Conference Bridges

• • •

Adding a Meet-Me Number Pattern, page 33-14 Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Using an Ad-Hoc Conference Bridge
When you initiate an Ad-Hoc conference, you are considered the conference controller. In an Ad-Hoc conference, only a conference controller can add participants to a conference. If other participants attempt to conference, the Cisco CallManager ignores the signals. When the conference controller initiates a conference call, the Cisco CallManager places the current call on hold, flashes the conference lamp, and provides dial tone to the user. At the dial tone, the conference controller dials the next conference participant and when the user answers, presses Conference again to complete the conference. The Cisco CallManager then connects the conference controller, the first participant, and the new conference participant to a conference bridge. Each participant’s Cisco IP Phone display reflects the connection to the conference. Participants can leave a conference by simply hanging up and terminating the conference call. A conference continues even if the conference controller hangs up, although the remaining conference participants cannot add new participants to the conference.
Related Topics
• • • • • • • • •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8 Updating a Conference Device, page 33-10 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12 Adding a Meet-Me Number Pattern, page 33-14

Cisco CallManager Administration Guide

33-4

OL-1047-01

Chapter 33

Configuring Conference Bridges Two Types of Conferences: Meet-Me and Ad-Hoc

• •

Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Using a Meet-Me Conference Bridge
When you initiate a Meet-Me conference by pressing Meet-Me on the phone, you are considered the conference controller. The conference controller provides the directory number for the conference to all attendees, who can then dial that directory number to join the conference. If other participants in a Meet-Me conference press Meet-Me, the Cisco CallManager ignores the signals. The conference controller selects a directory number from the range specified for the conference device. The Cisco CallManager Administrator should provide the conference directory number range to users so they can access the feature. When you, the conference controller, initiate a conference call by pressing Meet-Me, the Cisco CallManager provides dial tone to you. At the dial tone, you can dial the conference directory number to create the conference. The Cisco CallManager then connects you to the conference. Participants can join the conference by dialing the specified directory number. You hear a tone each time a participant joins the conference. Participants can leave a conference by hanging up the conference call. A conference continues even if you, the conference controller, hangs up.
Related Topics
• • • • • • • • •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using an Ad-Hoc Conference Bridge, page 33-4 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8 Updating a Conference Device, page 33-10 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12 Adding a Meet-Me Number Pattern, page 33-14

Cisco CallManager Administration Guide OL-1047-01

33-5

Chapter 33 Adding a Software Conference Device

Configuring Conference Bridges

• •

Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Adding a Software Conference Device
This section describes how to add a software conference device. For Conference Bridge hardware configuration see the “Adding a Hardware Conference Device” section on page 33-8.

Note

The service must be installed in order to perform this procedure.

Before You Begin

The following prerequisites must be met before proceeding with the steps:
• •

Servers must be configure. See the “Server” section on page 11-1. Device pools must be configured. See the “Configuring Device Pools” section on page 17-1.

Procedure
Step 1 Step 2 Step 3 Step 4

Open Cisco CallManager Administration. Click Service > Conference Bridge. Select Software in the Model Type field. Enter a name for the conference device, up to 15 alphanumeric characters, in the Device Name field.

Note

If the specified device name is longer than 15 characters, the device will not be able to successfully register with the Cisco CallManager.

Step 5

Enter any description for the conference device in the Device Description field.

Cisco CallManager Administration Guide

33-6

OL-1047-01

Chapter 33

Configuring Conference Bridges Adding a Software Conference Device

Step 6

Select a device pool from the drop-down list box in the Device Pool field, to which you want this conference device assigned. You can choose one of the available device pools, or you can select the default device pool. Select a server from the drop-down list box in the Server Name field. Enter the maximum number of streams you want to allow on this device, or keep the default number, in the Full Duplex Streaming Endpoint Count field. Enter the maximum number of seconds you want to allow calls or conferences to stay connected in the event of a Cisco CallManager failure, or keep the default number, in the Orphan Stream Time Out field.

Step 7 Step 8 Step 9

Note

When a Cisco CallManager goes down, the calls to the conferences that were on that Cisco CallManager are called orphans. The orphaned calls or conferences will stay up for the length of time you have allocated for Orphan Stream Time Out.

Step 10

Select True or False in the Run Flag field. True determines when you want a run flag.

Note

The Run Flag provides a way to disable functionality without removing devices.

Step 11

Click Insert. The page refreshes and a message displays stating that the Conference Bridge device must be reset in order for the changes to take effect. Click OK. The page refreshes again, showing information, including the status, for the device you just added. Each device is listed on the left side of the page.

Step 12

Click Reset Device and follow the instructions in the Reset Device dialog box.

Related Topics
• • •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using an Ad-Hoc Conference Bridge, page 33-4

Cisco CallManager Administration Guide OL-1047-01

33-7

Chapter 33 Adding a Hardware Conference Device

Configuring Conference Bridges

• • • • • • • •

Using a Meet-Me Conference Bridge, page 33-5 Adding a Hardware Conference Device, page 33-8 Updating a Conference Device, page 33-10 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12 Adding a Meet-Me Number Pattern, page 33-14 Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Adding a Hardware Conference Device
This section describes how to add a hardware conference device. For Conference Bridge software configuration, see the “Adding a Software Conference Device” section on page 33-6.

Note

The service must be installed in order to perform this procedure.

Before You Begin

The following prerequisites must be met before proceeding with the steps:
• •

Servers must be configured. See the “Server” section on page 11-1. Device pools must be configured. See the “Configuring Device Pools” section on page 17-1.

Procedure
Step 1 Step 2 Step 3 Step 4

Open Cisco CallManager Administration. Click Service > Conference Bridge. Select Hardware in the Model Type field. Enter the device MAC address (must be at least 12 characters) in the MAC address field.

Cisco CallManager Administration Guide

33-8

OL-1047-01

Chapter 33

Configuring Conference Bridges Adding a Hardware Conference Device

The Device Description field is automatically generated from the MAC address you provide.
Step 5 Step 6 Step 7 Step 8 Step 9

Enter any special load information into the Special Load Information field, or leave blank to use default. Select a device pool from the drop-down list box or choose Default, in the Device Pool field. Click Insert. A message displays stating that the Conference Bridge device must be reset in order for the changes to take effect. Click OK. The page refreshes and displays the conference device you just added. The device should appear in the list on the left side of the page. Click Reset Device and follow the instructions in the Reset Device dialog box.

Related Topics
• • • • • • • • • • •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using an Ad-Hoc Conference Bridge, page 33-4 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Updating a Conference Device, page 33-10 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12 Adding a Meet-Me Number Pattern, page 33-14 Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Cisco CallManager Administration Guide OL-1047-01

33-9

Chapter 33 Updating a Conference Device

Configuring Conference Bridges

Updating a Conference Device
This section describes how to update a Conference Device.
Note

The service must be installed in order to perform this procedure.

Before You Begin

The following prerequisites must be met before proceeding with the steps:
• • •

Servers must be configured. See the “Server” section on page 11-1. Device pools must be configured. See the “Configuring Device Pools” section on page 17-1. Conference device must be configured. See the “Understanding Conference Devices” section on page 33-2.

Procedure
Step 1 Step 2 Step 3 Step 4

Open Cisco CallManager Administration. Click Service > Conference Bridge. Select the Conference Bridge device you want to update from the list on the left side of the page. The page refreshes showing the device you want to update. Make the desired changes to the device. When you have completed your changes, click Update. A message displays stating that the Conference Bridge device must be reset in order for the changes to take effect. Click OK. The page refreshes showing the updated device information. Click Reset Device and follow the instructions in the Reset Device dialog box. Repeat steps 1 through 6 to update other conference devices.

Step 5 Step 6 Step 7

Related Topics
• •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3

Cisco CallManager Administration Guide

33-10

OL-1047-01

Chapter 33

Configuring Conference Bridges Deleting a Conference Device

• • • • • • • • •

Using an Ad-Hoc Conference Bridge, page 33-4 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8 Deleting a Conference Device, page 33-11 Updating Conference Bridge Parameters, page 33-12 Adding a Meet-Me Number Pattern, page 33-14 Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Deleting a Conference Device
This section describes how to delete a Conference Device.
Note

The service must be installed in order to perform this procedure.

Before You Begin

The following prerequisites must be met before proceeding with the steps:
• • •

Servers must be configured. See the “Server” section on page 11-1. Device pools must be configured. See the “Configuring Device Pools” section on page 17-1. Conference device must be configured. See the “Configuring Conference Bridges” section on page 33-1.

Procedure
Step 1 Step 2 Step 3

Open Cisco CallManager Administration. Click Service > Conference Bridge. Select the device you want to delete from the list on the left side of the page. The page refreshes, showing the device you selected.

Cisco CallManager Administration Guide OL-1047-01

33-11

Chapter 33 Updating Conference Bridge Parameters

Configuring Conference Bridges

Step 4 Step 5

Click Delete. A message displays stating that you are about to permanently delete the device, and that this action cannot be undone. If you wish to continue with the deletion, click OK, otherwise click Cancel. The page refreshes again, and the conference device you deleted is removed from the list of devices, and all active calls are terminated.

Related Topics
• • • • • • • • • • •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using an Ad-Hoc Conference Bridge, page 33-4 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8 Updating a Conference Device, page 33-10 Updating Conference Bridge Parameters, page 33-12 Adding a Meet-Me Number Pattern, page 33-14 Updating a Meet-Me Number Pattern, page 33-15 Deleting a Meet-Me Number Pattern, page 33-17

Updating Conference Bridge Parameters
This section describes how to update Conference Bridge Parameters.
Before You Begin

The following prerequisites must be met before proceeding with the steps:
• • •

Servers must be configured. See the “Server” section on page 11-1. Device pools must be configured. See the “Configuring Device Pools” section on page 17-1. Cisco CallManager must be configured. See the “Configuring Cisco CallManager” section on page 12-1.

Cisco CallManager Administration Guide

33-12

OL-1047-01

Chapter 33

Configuring Conference Bridges Updating Conference Bridge Parameters

Procedure
Step 1 Step 2 Step 3

Open Cisco CallManager Administration. Click Service > Conference Bridge. Click Conference Bridge Parameters from either the top right-hand corner or the bottom right-hand corner of the page. The page refreshes and the Conference Bridge Parameters page appears.

Step 4 Step 5

Select a device pool from the drop-down list box or choose Default. The Cisco CallManagers in this device pool appear in the box to the left of the page. Highlight the Cisco CallManager on which you want to update the conference parameters. The maximum number of users configured for both an Ad-Hoc conference and a Meet-Me conference using Unicast appear in the fields to the right of the page. Change the maximum number of users accordingly and click Update.

Step 6

Note

You must reset each Conference Bridge device after making updates for the changes to take effect. To do this, click Conference Bridge Configuration and select the Conference Bridge device you want to reset. Next, click Reset Device and follow the instructions in the Reset Device dialog box. Changes will only take place when there are no active calls. When you click Restart, the changes are made immediately, and active calls are terminated.

Related Topics
• • • • • •

Understanding Conference Devices, page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc, page 33-3 Using an Ad-Hoc Conference Bridge, page 33-4 Using a Meet-Me Conference Bridge, page 33-5 Adding a Software Conference Device, page 33-6 Adding a Hardware Conference Device, page 33-8

Cisco CallManager Administration Guide OL-1047-01

33-13

See the “Server” section on page 11-1. Click Meet-Me Number/Pattern Configuration. Before You Begin The following prerequisites must be met before proceeding with the steps: • • Servers must be configured.Chapter 33 Adding a Meet-Me Number Pattern Configuring Conference Bridges • • • • • Updating a Conference Device. Click Insert. See the “Configuring Device Pools” section on page 17-1. Step 4 Step 5 Step 6 Enter a Meet-Me Numbers/pattern in the Pattern field. page 33-10 Deleting a Conference Device. from either the top right-hand corner or the bottom right-hand corner of the page. The page refreshes and the Meet-Me Number/Pattern Configuration page appears. page 33-11 Adding a Meet-Me Number Pattern. Cisco CallManager Administration Guide 33-14 OL-1047-01 . Select a partition from the scroll menu in the Route Partition field. Device pools must be configured. page 33-15 Deleting a Meet-Me Number Pattern. page 33-17 Adding a Meet-Me Number Pattern This section describes how to add a Meet-Me Number Pattern. Click Service > Conference Bridge. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. The page refreshes and the new Meet-Me Numbers pattern appears in the list on the left side of the page. See the “Configuring Partitions” section on page 21-1 for more information. page 33-14 Updating a Meet-Me Number Pattern.

See the “Server” section on page 11-1. page 33-11 Updating Conference Bridge Parameters. Meet-Me Number/Pattern must be configured. Click Service > Conference Bridge. page 33-17 Configuring Partitions. Cisco CallManager Administration Guide OL-1047-01 33-15 . Device pools must be configured. page 33-15 Deleting a Meet-Me Number Pattern. page 33-3 Using an Ad-Hoc Conference Bridge. page 33-6 Adding a Hardware Conference Device. page 21-1 Updating a Meet-Me Number Pattern This section describes how to update a Meet-Me Number Pattern. See the “Configuring Device Pools” section on page 17-1. page 33-10 Deleting a Conference Device.Chapter 33 Configuring Conference Bridges Updating a Meet-Me Number Pattern Related Topics • • • • • • • • • • • • Understanding Conference Devices. Procedure Step 1 Step 2 Open Cisco CallManager Administration. page 33-4 Using a Meet-Me Conference Bridge. Before You Begin The following prerequisites must be met before proceeding with the steps: • • • Servers must be configured. page 33-12 Updating a Meet-Me Number Pattern. page 33-5 Adding a Software Conference Device. page 33-8 Updating a Conference Device. See the “Adding a Meet-Me Number Pattern” section on page 33-14. page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc.

The page refreshes again and the pattern you chose appears in the pattern field. Related Topics • • • • • • • • • • • • Understanding Conference Devices. page 21-1 Cisco CallManager Administration Guide 33-16 OL-1047-01 . Step 4 Highlight the Meet-Me Numbers pattern you want to update from the list on the left side of the page.Chapter 33 Updating a Meet-Me Number Pattern Configuring Conference Bridges Step 3 Click Meet-Me Number/Pattern Configuration. Step 5 Select a new route partition from the scroll list and click Update. page 33-12 Adding a Meet-Me Number Pattern. The page refreshes and the pattern is updated with the new route partition information. page 33-6 Adding a Hardware Conference Device. from either the top right-hand corner or the bottom right-hand corner of the page. page 33-17 Configuring Partitions. page 33-3 Using an Ad-Hoc Conference Bridge. page 33-10 Deleting a Conference Device. page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc. The page refreshes and the Meet-Me Number/Pattern Configuration page appears. page 33-4 Using a Meet-Me Conference Bridge. page 33-5 Adding a Software Conference Device. Note You can change the number or pattern as needed (example. changing 5000 to 500X). page 33-14 Deleting a Meet-Me Number Pattern. page 33-8 Updating a Conference Device. page 33-11 Updating Conference Bridge Parameters.

page 33-2 Two Types of Conferences: Meet-Me and Ad-Hoc. page 33-3 Using an Ad-Hoc Conference Bridge. or Cancel to cancel the deletion. Related Topics • • • • • • • Understanding Conference Devices. Before You Begin The following prerequisites must be met before proceeding with the steps: • • • Servers must be configured Device pools must be configured Meet-Me Number/Pattern must be configured Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Click Service > Conference Bridge. page 33-4 Using a Meet-Me Conference Bridge. page 33-5 Adding a Software Conference Device. A message displays stating that you are about to permanently delete this pattern and that this action cannot be undone. Click OK to continue. Click Delete. page 33-10 Cisco CallManager Administration Guide OL-1047-01 33-17 . from either the top right-hand corner or the bottom right-hand corner of the page. page 33-8 Updating a Conference Device. Step 4 Step 5 Step 6 Highlight the Meet-Me Number/Pattern you want to delete from the list on the left side of the page. Click Meet-Me Number/Pattern Configuration. page 33-6 Adding a Hardware Conference Device. The page refreshes again. The page refreshes and the Meet-Me Number/Pattern Configuration page appears.Chapter 33 Configuring Conference Bridges Deleting a Meet-Me Number Pattern Deleting a Meet-Me Number Pattern This section describes how to delete a Meet-Me Number Pattern.

page 33-11 Updating Conference Bridge Parameters. page 33-12 Adding a Meet-Me Number Pattern.Chapter 33 Deleting a Meet-Me Number Pattern Configuring Conference Bridges • • • • Deleting a Conference Device. page 33-14 Updating a Meet-Me Number Pattern. page 33-15 Cisco CallManager Administration Guide 33-18 OL-1047-01 .

323 gateways may require that calls use an MTP in order to enable supplementary call services. in priority order. An MTP always registers with its primary (or publisher) Cisco CallManager if that Cisco CallManager is available. See the “Configuring Transcoder” section on page 37-1 for more information. Each MTP can register with only one Cisco CallManager at a time.C H A P T E R 34 Configuring Media Termination Point A Media Termination Point (MTP) is invoked on behalf of H. This list is called a Device Pool. and Cisco CallManager Administration Guide OL-1047-01 34-1 . Note Transcoders also provide the capabilities of an MTP in addition to their transcoding functions. the MTP attempts to register with the next available Cisco CallManager in the list. If the primary Cisco CallManager fails. H. Under Windows2000. In some cases. Cisco gateways do not. The first Cisco CallManager in the list is its primary Cisco CallManager. at the same time. Each MTP is given a list of Cisco CallManagers. and informs the Cisco CallManager about how many MTP resources it supports. the application runs as a service and is called “Cisco Ip Voice Media Streaming App”. The MTP registers with its specified primary Cisco CallManager. MTP is a Cisco software application that installs on a server during the software installation process. but normally.323 endpoints involved in a call in order to enable supplementary call services. During installation. to which it should attempt to register. You cannot have both Transcoders and MTPs registered with the same Cisco CallManager. the component is called the “IpVoiceMediaStreamer” and is common to both the MTP and Conference Bridge applications.

When more than one MTP is registered with a given Cisco CallManager. the call is connected without using an MTP resource. each of which may be registered to one Cisco CallManager. such as call hold.323 endpoint. that are otherwise not available when a call is routed to an H. MTP resource use is invisible to both the users of the system. page 34-7 Deleting a Media Termination Point. page 34-8 Cisco CallManager Administration Guide 34-2 OL-1047-01 . depending on how you have your system configured. and supplementary services are not available on that call. call park. Multiple MTPs may be registered with the same Cisco CallManager. Related Topics: • • • • • • Planning Your MTP Configuration. That MTP resource is inserted into the call on behalf of the endpoint. The Cisco CallManager controls MTP resources. and conferencing. The system may have multiple MTPs. page 34-3 Avoiding Call Failure/User Alert. Note Supplementary services are features. page 34-5 Updating a Media Termination Point. For example. MTP application server 1 is configured for 48 MTP resources. When the Cisco CallManager determines that a call endpoint requires an MTP. call transfer.Chapter 34 Configuring Media Termination Point re-registers with the primary Cisco CallManager as soon as it becomes available after a failure. page 37-1 Adding a Media Termination Point. page 34-4 Configuring Transcoder. The MTPs may also be distributed across a networked system as desired. that Cisco CallManager controls the set of resources for each of the MTPs. it allocates an MTP resource from the MTP that has the most resources available. If an MTP resource is not available when it is needed. The MTP application server 2 is configured for 24 resources. If both MTPs register with the same Cisco CallManager. that Cisco CallManager maintains both sets of resources for a total of 72 registered MTP resources. and the endpoint on whose behalf it was inserted. and is currently not in use.

however. and various other factors. the speed of the processor. Consider the following formula to determine the approximate number of MTP applications needed for your system. while a 10 MB NIC card cannot. depending on the speed of the network and the network interface card (NIC) card. network loading. approximately 24 MTP resources can be provided. a 100 MB Network/NIC card can support 48 MTP resources. the exact number of MTP resources available depends on the amount of resources being consumed by other applications on that PC. more than one MTP resource might be consumed by a given call.323 endpoint requires an MTP. however. For a 10 MB Network/NIC card. assuming that your server can handle 48 MTP resources (you can substitute 48 for the correct number of MTP resources supported by your system): A plus B divided by 48 = number of MTP applications needed (A + B / 48 = # of MTP apps) where: A represents the maximum number of simultaneous calls to H. thus depending on the originating and terminating device type. to provide more MTP resources. you can install additional MTP applications on networked Windows NT servers.Chapter 34 Configuring Media Termination Point Planning Your MTP Configuration Planning Your MTP Configuration Consider the following information when planning your MTP configuration: • Only one MTP application can be installed per server. it consumes one MTP resource. The MTP resources assigned to the call are released when the call is terminated.323 endpoints that require an MTP B represents the maximum number of simultaneous calls between Cisco CallManager clusters If a remainder exists. A single MTP provides a default of 48 MTP (user configurable) resources. Cisco CallManager Administration Guide OL-1047-01 34-3 . add another MTP application. • If one H. For example.

page 34-4 Configuring Transcoder. page 34-7 Deleting a Media Termination Point. The Performance Monitor counter. all calls connected to the MTP go down at that time. Refer to the MTP system requirements are the same as Cisco CallManager system requirements. increments for each H.323 call that has been connected without an MTP resource when one was required. page 34-5 Updating a Media Termination Point. you are prompted to reset MTP before any changes can take effect. This does not result in disconnection of any calls connected to MTP resources. as soon as the MTP has no active calls. When you configure the MTP. • Related Topics: • • • • • • Configuring Media Termination Point. Media TermPoints Out of Resources. If the MTP application is installed on the same PC as the Cisco CallManager.Chapter 34 Avoiding Call Failure/User Alert Configuring Media Termination Point • Use Performance Monitor to monitor the usage of MTP resources. Cisco CallManager Administration Guide 34-4 OL-1047-01 . page 34-1 Avoiding Call Failure/User Alert. • Note When you make updates to the MTP and you choose Restart. the changes take effect. page 34-8 Avoiding Call Failure/User Alert Avoid the following conditions to prevent call failure or user alert: • Although the MTP application can be installed on the same PC as the Cisco CallManager. This number can assist you in determining how many MTP resources are required for your callers. If you choose Reset. it can adversely affect the performance of the Cisco CallManager. we strongly recommend against this. page 37-1 Adding a Media Termination Point. and whether you have adequate coverage.

Note Add only one Media Termination Point (MTP) device for each MTP application. page 34-3 Configuring Transcoder. See the “Server” section on page 11-1. Device pools must be configured.Chapter 34 Configuring Media Termination Point Adding a Media Termination Point Related Topics: • • • • • • Configuring Media Termination Point. Cisco CallManager Administration Guide OL-1047-01 34-5 . up to 15 alphanumeric characters. Click Service> Media Termination Point. See the “Server” section on page 11-1. page 34-5 Updating a Media Termination Point. Before You Begin The following prerequisites must be met before proceeding with the steps: • • Servers must be configured. page 34-8 Adding a Media Termination Point This section describes how to add a Media Termination Point (MTP). Enter any description for the MTP in the Device Description field. Enter a name for the MTP. in the Device Name field. page 34-1 Planning Your MTP Configuration. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. page 34-7 Deleting a Media Termination Point. page 37-1 Adding a Media Termination Point. Note The service must be installed in order to perform this procedure.

page 34-3 Avoiding Call Failure/User Alert. from the drop-down list box. A message displays stating that the MTP device must be reset before the changes take effect. Step 9 Step 10 Step 11 Step 12 Select True or False in the Run Flag field.) Click Insert. The device pool specifies the list of Cisco CallManagers for this MTP. Click Reset Device and follow the instructions in the Reset Device dialog box. the calls to conferences that were on that Cisco CallManager are called orphans. page 34-8 Configuring a Transcoder.Chapter 34 Adding a Media Termination Point Configuring Media Termination Point Step 5 Step 6 Step 7 Step 8 Select a device pool from the drop-down menu in the Device Pool field. The page refreshes showing the specific information for the device you just created. Related Topics • • • • • • • Configuring Media Termination Point. page 34-4 Configuring Transcoder. The orphaned calls or conferences will stay up as long as the length of time you allocated for Orphan Stream Time Out. page 34-1 Planning Your MTP Configuration. or keep the default number. page 37-1 Updating a Media Termination Point. Enter an endpoint count or keep the default number in the Full Duplex Streaming Endpoint Count field. Click OK. Select the server on which the MTP will run in the Server Name field. page 37-3 Cisco CallManager Administration Guide 34-6 OL-1047-01 . (The Run Flag provides a way to disable functionality without removing devices. Note When a Cisco CallManager goes down. Enter the maximum number of seconds you want to allow conference calls to stay connected in the Orphan Stream Time Out field. The device should now appear in the list on the left side of the page. page 34-7 Deleting a Media Termination Point.

Note The service must be installed in order to perform this procedure. all calls connected to the MTP go down at that time. Click OK. Step 7 Repeat Steps 1-6 to update other MTPs.Chapter 34 Configuring Media Termination Point Updating a Media Termination Point Updating a Media Termination Point This section describes how to update a Media Termination Point (MTP). Note When you make updates to the MTP and you choose Restart. The page refreshes. The page refreshes. Before You Begin The following prerequisites must be met before proceeding with the steps: • • • Servers must be configured Device pools must be configured Media Termination Points must be configured Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. Select the MTP you want to update from the device list on the left side of the page. A message displays stating that the MTP device must be reset before the changes will take effect. Reset will wait until all calls are completed. Cisco CallManager Administration Guide OL-1047-01 34-7 . showing the device you selected. showing the updated MTP. Make the desired changes to the MTP and click Update. Click Reset Device and follow the instructions in the Reset Device dialog box. Click Service> Media Termination Point.

page 34-4 Configuring Transcoder. or Cancel to cancel the deletion. Select the MTP you want to delete from the device list on the left side of the page. Cisco CallManager Administration Guide 34-8 OL-1047-01 . Click OK to continue. Before You Begin The following prerequisites must be met before proceeding with the steps: • • • Servers must be configured Device pools must be configured Media Termination Points must be configured Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration Click Service> Media Termination Point. page 34-8 Deleting a Media Termination Point This section describes how to delete a Media Termination Point (MTP). page 37-1 Adding a Media Termination Point.Chapter 34 Deleting a Media Termination Point Configuring Media Termination Point Related Topics • • • • • • Configuring Media Termination Point. page 34-5 Deleting a Media Termination Point. A message displays verifying your delete request. showing the device you selected. There is no undo for this action. The page refreshes. page 34-1 Planning Your MTP Configuration. Click Delete. page 34-3 Avoiding Call Failure/User Alert. Note The service must be installed in order to perform this procedure.

page 34-5 Updating a Media Termination Point. page 37-1 Adding a Media Termination Point.Chapter 34 Configuring Media Termination Point Deleting a Media Termination Point The page refreshes again and the MTP you deleted should no longer appear in the device list. page 34-7 Cisco CallManager Administration Guide OL-1047-01 34-9 . Related Topics • • • • • • Configuring Media Termination Point. page 34-1 Planning Your MTP Configuration. page 34-4 Configuring Transcoder. Step 6 Repeat Steps 1-5 to delete another MTP. All active calls/streams are terminated. page 34-3 Avoiding Call Failure/User Alert.

Chapter 34 Deleting a Media Termination Point Configuring Media Termination Point Cisco CallManager Administration Guide 34-10 OL-1047-01 .

it may not physically exist. Read the “Understanding Service Parameters” section on page 10-1 for more detailed service parameter information. as well as insert. Note The previous statements only apply to the Cisco CallManager database. Refer to the “Service Parameter Restart Conditions” section on page 35-2 for information on when a restart of Cisco CallManager is required for certain parameters.0 and later) allows you to configure different services on selected servers.C H A P T E R 35 Configuring Service Parameters Service Parameters for Cisco CallManager (release 3. The Service Parameters application also provides the following lists: • • Configured servers in the system All configured services on a selected server Caution Some changes to service parameters may cause system failure. Services must be installed in the database for them to work. You can insert and delete services on a selected server. For example. It will only be installed if you chose Media Streaming Off during installation. Cisco CallManager Administration Guide OL-1047-01 35-1 . modify. if you add a conference bridge to the database. and delete the service parameters for those services. or unless the Cisco Technical Assistance Center (TAC) specifies the changes. Cisco recommends that you do not make any changes to service parameters unless you fully understand the feature that you are changing.

page 35-3 Deleting a Service From a Server. page 35-9 Service Parameter Restart Conditions If you modify any of the following service parameters. you must restart the Cisco CallManager before the modifications take effect: • • • • • • • • • • Digital Port Ethernet Phone Port Analog Port MGCP Listen Port MGCP Keep-alive Port MessageWaitingOffDN MessageWaitingOnDN StatisticsEnabled MaxDaResponseTimeoutErrorCount MaxTotalNumberOfRegisteredCallingEntities Note These restart conditions apply starting with release 3.0(7) of the Cisco CallManager. page 35-7 Deleting a Service Parameter. page 35-2 Adding a New Service on a Server. page 10-1 Service Parameter Restart Conditions.Chapter 35 Service Parameter Restart Conditions Configuring Service Parameters Related Topics • • • • • • • Understanding Service Parameters. Cisco CallManager Administration Guide 35-2 OL-1047-01 . page 35-5 Updating a Service Parameter. page 35-4 Adding a New Service Parameter.

The page refreshes. page 35-3 Deleting a Service From a Server. Click New. A status message prompts you to wait. The system loads the service type you selected after the service type is inserted. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. page 35-7 Deleting a Service Parameter. page 35-4 Adding a New Service Parameter. From the Service Type drop-down menu. Step 4 Step 5 Step 6 Cisco CallManager Administration Guide OL-1047-01 35-3 . page 10-1 Adding a New Service on a Server. choose a service type to configure on this server. The page refreshes to the server you selected. Click Insert to configure the service type. Choose a configured server from the list of configured servers on the left side of the page. page 35-1 Understanding Service Parameters. page 35-5 Updating a Service Parameter. The page refreshes again. Choose Service > Service Parameters. showing the services already configured on that server.Chapter 35 Configuring Service Parameters Adding a New Service on a Server Related Topics • • • • • • • Configuring Service Parameters. page 35-9 Adding a New Service on a Server This section describes how to add a new service on a server. Before You Begin Ensure the following prerequisite is met before proceeding with the steps: • Servers must be configured.

showing the services already configured on that server. Service must be present. page 35-7 Deleting a Service Parameter. page 35-9 Deleting a Service From a Server This section describes how to delete service from a server. • • Servers must be configured. From the list of configured servers on the left side of the page. Step 4 Cisco CallManager Administration Guide 35-4 OL-1047-01 . page 35-4 Adding a New Service Parameter.Chapter 35 Deleting a Service From a Server Configuring Service Parameters Related Topics • • • • • • • Configuring Service Parameters. page 35-5 Updating a Service Parameter. The page refreshes to the server you selected. Before You Begin Ensure the following prerequisites are met before proceeding with the steps. Choose Service > Service Parameters. Choose the configured service you want to delete. page 35-1 Understanding Service Parameters. See the “Server” section on page 11-1. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. choose the configured server from which you want to delete a service. The page refreshes again. page 35-2 Deleting a Service From a Server. The drop-down list box under Configured Services lists the configured services. page 10-1 Service Parameter Restart Conditions.

page 35-9 Adding a New Service Parameter This section describes how to add a new service parameter. • • Servers must be configured. Cisco recommends that you do not make any changes to service parameters unless you fully understand the feature that you are changing or unless the Cisco Technical Assistance Center (TAC) specifies the changes. Related Topics • • • • • • • Configuring Service Parameters. See the “Server” section on page 11-1. Service must be configured. Click OK to continue or Cancel to cancel the deletion. page 35-5 Updating a Service Parameter. The service type no longer appears in the drop-down list. Refer to the “Understanding Service Parameters” section on page 10-1 for more information about service parameters. A message displays stating that you are about to permanently delete this service and that the action cannot be undone.Chapter 35 Configuring Service Parameters Adding a New Service Parameter Step 5 Step 6 Click Delete Service. Before You Begin Ensure the following prerequisites are met before proceeding with the steps. page 10-1 Service Parameter Restart Conditions. page 35-2 Adding a New Service on a Server. Cisco CallManager Administration Guide OL-1047-01 35-5 . Caution Some changes to service parameters may cause system failure. page 35-1 Understanding Service Parameters. page 35-3 Adding a New Service Parameter. page 35-7 Deleting a Service Parameter.

page 10-1 Service Parameter Restart Conditions. A status message prompts you to wait. The page refreshes again. page 35-1 Understanding Service Parameters. Enter the parameter type in the Type field. page 35-4 Updating a Service Parameter. and the status message displays results. Choose a configured server from the list of configured servers on the left side of the page. page 35-3 Deleting a Service From a Server.Chapter 35 Adding a New Service Parameter Configuring Service Parameters Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Open Cisco CallManager Administration. Click OK if you wish to use the default settings or Cancel to cancel the operation. Enter the service parameter name you want to add in the Param field. The page refreshes to the list of configured services. click Default. page 35-2 Adding a New Service on a Server. Note If you want to use default settings. page 35-7 Deleting a Service Parameter. Choose Service > Service Parameters. page 35-9 Cisco CallManager Administration Guide 35-6 OL-1047-01 . The service parameter you added appears in the list of configured service parameters. Click Update. Enter a value in the Value field. A message displays stating that you are about to permanently delete all the previous settings and replace them with the default settings. Related Topics • • • • • • • Configuring Service Parameters. The page refreshes. Choose the service to which you want to add a new parameter.

Choose Service > Service Parameters. Type. The page refreshes again. make the desired changes to the parameter. Cisco recommends that you do not make any changes to service parameters unless you fully understand the feature that you are changing. Choose the service to which you want to update a parameter. Note Refer to the “Understanding Service Parameters” section on page 10-1 for more information before updating service parameters. and Value fields.Chapter 35 Configuring Service Parameters Updating a Service Parameter Updating a Service Parameter This section describes how to update a service parameter. Before You Begin Ensure the following prerequisites are met before proceeding with the steps. Choose the parameter you want to update from the list of configured service parameters. or unless the Cisco Technical Assistance Center (TAC) specifies the changes. See the “Server” section on page 11-1 for more information. Caution Some changes to service parameters may cause system failure. Cisco CallManager Administration Guide OL-1047-01 35-7 . The page refreshes to the list of configured services. Service must be configured. • • Servers must be configured. Choose a configured server from the list of configured servers on the left side of the page. Step 6 Using the Param. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Refer to the “Understanding Service Parameters” section on page 10-1 for more information about service parameters.

You cannot change default value types. A status message prompts you to wait. click Default. page 35-4 Adding a New Service Parameter. page 35-2 Adding a New Service on a Server. page 35-5 Deleting a Service Parameter. Step 7 Click Update.Chapter 35 Updating a Service Parameter Configuring Service Parameters Note You can change a service parameter type only if it is added. A message displays stating that you are about to permanently delete all the previous settings and replace them with the default settings. and the status message displays results. page 10-1 Service Parameter Restart Conditions. page 35-3 Deleting a Service From a Server. page 35-9 Cisco CallManager Administration Guide 35-8 OL-1047-01 . Related Topics • • • • • • • Configuring Service Parameters. page 35-1 Understanding Service Parameters. The Cisco CallManager updates the service parameter with your changes. Note If you want to use default settings. Click OK if you want to use the default settings or Cancel to cancel the operation. The page refreshes.

From the Configured Services list.Chapter 35 Configuring Service Parameters Deleting a Service Parameter Deleting a Service Parameter This section describes how to delete a service parameter. See the “Server” section on page 11-1 and the “Understanding Service Parameters” section on page 10-1 for more information. The deleted service parameter no longer appears in the list of configured service parameters. Choose a configured server from the list of configured servers on the left side of the page. Service must be configured. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Open Cisco CallManager Administration. Before You Begin Ensure the following prerequisites are met before proceeding with the steps. Cisco CallManager Administration Guide OL-1047-01 35-9 . and the status message displays results. Caution Some changes to service parameters may cause system failure. choose the service type from which you want to delete a service parameter. Cisco recommends that you do not make any changes to service parameters unless you fully understand the feature that you are changing or unless the Cisco Technical Assistance Center (TAC) specifies the changes. A message displays stating that you are about to permanently delete this parameter and that this action cannot be undone. Refer to the “Understanding Service Parameters” section on page 10-1 for more information about service parameters. Click Delete. The page refreshes again. A status message prompts you to wait. Click OK to continue or Cancel to cancel the deletion. The page refreshes. Choose the service parameter you want to delete. • • Servers must be configured. Choose Service > Service Parameters. The page refreshes to the list of configured services.

page 35-5 Updating a Service Parameter. page 35-4 Adding a New Service Parameter. Related Topics • • • • • • Configuring Service Parameters.Chapter 35 Deleting a Service Parameter Configuring Service Parameters Note If you want to use default settings. A message displays stating that you are about to permanently delete all the previous settings and replace them with the default settings. page 10-1 Adding a New Service on a Server. page 35-7 Cisco CallManager Administration Guide 35-10 OL-1047-01 . page 35-3 Deleting a Service From a Server. page 35-1 Understanding Service Parameters. click Default. Click OK if you want to use the default settings or Cancel to cancel the operation.

and Date and Time. page 36-14 Deleting a Service. page 36-11 Updating a Trace Configuration. User Mask. page 36-2 Table 36-4 provides the trace parameters for Event Type. You can configure trace options for each of the following system services: • • • • • • Cisco CallManager Cisco Database Layer Monitor Cisco IP Voice Media Streaming Application Cisco Messaging Interface (CMI) Cisco Telephony Call Dispatcher (TCD) Cisco Trivial File Transfer Protocol (TFTP) The following sections provide details about configuring trace settings: • • • • • • Understanding Trace Configuration. page 36-13 Deleting a Trace Configuration. page 36-15 Cisco CallManager Administration Guide OL-1047-01 36-1 .C H A P T E R 36 Configuring Trace Use trace configuration to specify the type and level of trace information reported by Cisco CallManager and its associated services. page 36-9 Adding a New Service and Trace Configuration.

a more detailed level includes all the same information as the lower level plus some additional information. Traces all Special conditions plus subsystem state transitions that occur during normal operation. page 36-7 The hexadecimal number in the Trace Mask field changes as you change the settings of trace level. Traces all State Transition conditions plus media events that occur during normal operation. Too little trace information will prevent you from debugging the system.Chapter 36 Understanding Trace Configuration Configuring Trace Understanding Trace Configuration Traces provide information that can be used for system performance monitoring. but too much trace information can overload the system and degrade performance. You can set the following parameters in Cisco CallManager Administration to control the type and amount of trace information generated: • • • • • Trace Levels. Cisco CallManager Administration Guide 36-2 OL-1047-01 . page 36-3 Event Level. time. Selecting the proper level and amount of trace information for your needs is important. Traces all Error conditions plus process and device initialization messages. and user mask. date. Because the levels are cumulative. Table 36-1 Trace Levels Level Error Special State Transition Significant Description Traces alarm conditions and events. Trace Levels Table 36-1 lists the available trace levels used by the Cisco CallManager service. and the Detailed level provides the most. and debugging. The Error level provides the least amount of trace information. troubleshooting. page 36-6 Components. page 36-3 User Mask. page 36-2 Time.

Cisco recommends that you enable the Show Time option for all traces. The function of each mask bit depends on the service you are tracing. as indicated in Table 36-2. Detailed Traces all Arbitrary conditions plus detailed debugging information. As you click on the bits to turn them on and off. User Mask The user mask. Not all services use this trace level. Cisco CallManager Administration Guide OL-1047-01 36-3 . Note Do not use this trace level with the Cisco CallManager service or the Cisco IP Voice Media Streaming Application service during normal operation. a series of flags or bits. Note Do not use this trace level with the Cisco CallManager service or the Cisco IP Voice Media Streaming Application service during normal operation. Traces all Entry/Exit conditions plus low-level debugging information. Time You can enable the Show Time option to record the time of each trace event. enables and disables specific types of trace information. the hexadecimal value in the Mask field changes.Chapter 36 Configuring Trace Understanding Trace Configuration Table 36-1 Trace Levels (continued) Level Entry/Exit Arbitrary Description Traces all Significant conditions plus entry and exit points of routines.

Digital gateway information. and 4) Detailed debugging information. Conference bridge information. H. Primary Rate Interface (PRI) information. Cisco CallManager Administration Guide 36-4 OL-1047-01 . Note Do not set this flag during normal system operation. 11 12 13 14-15 Subsystem information not covered by one of the other user mask bits. Skinny Station protocol information. Media Termination Point (MTP) information.Chapter 36 Understanding Trace Configuration Configuring Trace Table 36-2 User Mask Bits Service Cisco CallManager Mask Bits 0 1 2 3 4 5 6 7 8 9 10 Type of Trace Enabled by This Bit Protocol Layer 1 information. Protocol Layer 2 information. Gateway traces (used in conjunction with bits 2. 3. Message translation information for ISDN messages. Analog gateway information. MGCP gateway information. Not used.225 and gatekeeper information.

Not used. Not used.Chapter 36 Configuring Trace Understanding Trace Configuration Table 36-2 User Mask Bits (continued) Service Cisco Database Layer Monitor Mask Bits 0 1 2 Type of Trace Enabled by This Bit Detailed database information such as SQL statements. Conference bridge device information. Not used. you must stop and restart all applications that use this DLL before tracing will begin. After enabling this bit. Device driver information. High-level WinSock information. Detailed information about the business rules. Service and database manager information. Media Termination Point (MTP) device information. Not used.dll relating to any application programs that access the database. MTP and conference bridge device recovery information. Information about DBL. you must stop and restart all applications that use this DLL before tracing will begin. Application initialization information.dll relating to the web administration pages and Visual Basic applications. Low-level WinSock information. Information about database change notification messages. Information about DBLX. 3 4-7 8 9 10-15 Cisco IP Voice Media Streaming Application 0 1 2 3 4 5 6 7 8 9 10-15 Cisco Messaging Interface (CMI) 0-15 Cisco CallManager Administration Guide OL-1047-01 36-5 . Not used. Message information from Skinny Station protocol. Tracing this information from web administration requires that you enable the debug settings on IISAdmin service and the web service from the IIS Management console. Information about all code in the database. After enabling this bit.

including events that occur during normal system operation. The following list gives available event levels: • • • • • • • • Debug Information Notice Warning Error Critical Alert Emergency The Emergency event level traces only the most severe Error events. Cisco CallManager Administration Guide 36-6 OL-1047-01 . For traces during normal system use. 0 = System 1 = Build files 2 = Server files 1-15 Not used. Event Level The Event level applies only to Error traces. The Debug event level provides trace information on all types of events. and it specifies what types of Error events are traced.Chapter 36 Understanding Trace Configuration Configuring Trace Table 36-2 User Mask Bits (continued) Service Cisco Trivial File Transfer Protocol (TFTP) Mask Bits 0 Type of Trace Enabled by This Bit All TFTP event information. The event levels between Emergency and Debug provide increasingly greater amounts of trace information. and it provides the least amount of trace information. choose an event level between Error (minimum) and Debug (maximum).

Chapter 36 Configuring Trace Understanding Trace Configuration Components The trace log components let you specify where the trace information is collected or stored. Warning Do not modify the trace parameters in any way unless directed to do so by Cisco Technical Assistance Center (TAC). Output Debug String TraceOutputDebugStri T ng Note Do not enable this option unless instructed to do so by Cisco Technical Assistance Center (TAC). This option is for Cisco Development use only. File Enable this option to store trace information in a file. or letting a single trace file grow too large. You can also set the following file parameters: Cisco CallManager Administration Guide OL-1047-01 36-7 . Table 36-3 describes the trace log components. Table 36-3 Trace Log Components Component EventLog Parameter TraceEvent Default Value T Description Enable this option to send trace information to the Windows 2000 EventLog. Caution Creating a large number of trace files. can severely degrade the performance of your system.

and the remaining trace data is written to the next file in the sequence. To do this. you can set up trace files to store a full week of data. Cisco CallManager Administration Guide 36-8 OL-1047-01 . with one day of data in each file. TraceNumFiles 250 This parameter specifies the total number of trace files for a given service. For example. TraceFileNumLines 10000 TraceFileNumMinutes 1440 Note When the trace data exceeds either the maximum number of lines or the maximum number of minutes for one file. and number of lines to a large value such as 10000. This parameter specifies the maximum number of lines of data stored in each trace file. A sequence number automatically appended to the file name indicates which file it is.txt of the trace file. This parameter specifies the maximum number of minutes of data stored in each trace file. you can set the number of files to 7. When the last file in the sequence is full. Cisco CallManager closes that file.Chapter 36 Understanding Trace Configuration Configuring Trace Table 36-3 Trace Log Components (continued) Component Parameter TraceFile Default Value Description c:\Program Each service requires a unique trace file Files\Cisco\Trace\ name. Note Cisco recommends that you leave the file names set to their default values. as the fully qualified path name CCM\ccm. the trace data begins writing over the first file again. the number of minutes to 1440 (one day).

Chapter 36 Configuring Trace Understanding Trace Configuration Table 36-3 Trace Log Components (continued) Component System Log Parameter TraceSyslog Default Value T Description Enable this option to send trace information to the Cisco Syslog Collector. only alarm (Error) traces are sent to the Cisco Syslog Collector. System Server designates the name of the Cisco Syslog Collector. and Date and Time Cisco CallManager Administration Guide OL-1047-01 36-9 . TraceSyslogDebug F TraceSyslogServer Note Do not change this field unless instructed to do so by Cisco Technical Assistance Center (TAC). Table 36-4 provides the trace parameters for Event Type. User Mask. Debug Enabling causes all trace data to be sent to the Cisco Syslog Collector. If you do not enable this option.

During normal system operation. so that system resources are not overloaded by the trace data. start with a small amount of tracing. Recommended Trace Settings In general. and Notice. To configure this minimum level of alarm tracing. The Show Date option records the date of each trace event. enables and disables specific types of trace information. Note The TraceOn parameter determines whether trace is enabled. set the trace parameters as follows for each service on each Cisco CallManager in the cluster: Cisco CallManager Administration Guide 36-10 OL-1047-01 . Information. a series of flags or bits. and Date and Time Parameter TraceEventLevel Default Value 469762048 Description The event type applies only to traces at the Error level and specifies what types of the following error events are traced: Debug. If the initial traces are not sufficient for your purposes. Table 36-4 Trace Parameters for Event Type. The user mask.Chapter 36 Recommended Trace Settings Configuring Trace Warning Do not modify any trace parameters unless directed to do so by Cisco Technical Assistance Center (TAC). TraceMask 4144124 TraceShowTime T The Show Time option records the time of each trace event. User Mask. Alarm tracing is the minimum level of tracing for a fully operational system. trace alarm conditions and respond to them as quickly as possible. If system performance begins to degrade during tracing. you can gradually increase the level of tracing until you get the desired data. The default value is T. decrease the trace level until the performance returns to normal.

Cisco CallManager Administration Guide OL-1047-01 36-11 . Enable the Show Time check box. This section describes how to add a new service and trace configuration to the Cisco CallManager database. If you then install a Cisco CallManager with the same name specified in the new trace configuration. that trace configuration becomes the default for the specified service on the specified Cisco CallManager.Chapter 36 Configuring Trace Adding a New Service and Trace Configuration • • • • • • Enable the Trace On check box. Normally. as described in Table 36-2. You can also add a new service and trace configuration before installing an additional (subscriber) Cisco CallManager in a cluster. Set the level type to Error. Enable the EventLog check box. you do not have to use this procedure because each service receives a default trace configuration when you install the Cisco CallManager software. Set the event level to Error. Enable the appropriate user mask bits for each service. Adding a New Service and Trace Configuration Warning Cisco recommends that you do not use this procedure unless specifically directed to do so by the Cisco Technical Assistance Center (TAC). You can then modify this default trace configuration by following the procedure described in the “Updating a Trace Configuration” section on page 36-13.

For details. Cisco recommends that you enable the Show Time option. If desired. then. see the “Components” section on page 36-7. choose the server whose trace parameters you want to configure. Note You can only add services that are not already configured for this Cisco CallManager server. For details. For details. From the list of IP addresses or DNS names at the left of the screen. Choose the desired event level. enable the Show Time and Show Date options to record the time and date of each event. Note The Configured Services list contains all the services that are configured for this server. see the “Event Level” section on page 36-6. choose the service for which you want to add a trace configuration. click Insert. Set the appropriate user mask bits for the service. see the “Trace Levels” section on page 36-2.Chapter 36 Adding a New Service and Trace Configuration Configuring Trace Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Cisco CallManager Administration Guide 36-12 OL-1047-01 . Step 4 Step 5 Click New to create a trace configuration for a new service. Set the desired trace log components. Choose the desired trace level. Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Click Trace On to enable trace. see the “User Mask” section on page 36-3. From the Service Type drop-down list box. Choose Service > Trace. For details.

Chapter 36 Configuring Trace Updating a Trace Configuration Step 12 If you want to reset all trace parameters to their previous values. click SetDefault. From the list of IP addresses or DNS names at the left of the screen. Before saving the changes. you can click Cancel to reset all fields to their previous value or click SetDefault to reset all fields to their default value. When you are finished setting the trace parameters. Make the desired changes in the fields you want to update. From the list of Configured Services. choose the service whose trace configuration you want to update. If you want to reset all trace parameters to their initial default values. Choose Service > Trace. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Step 6 Cisco CallManager Administration Guide OL-1047-01 36-13 . click Update to save the changes in the database. click Cancel. choose the server whose trace configuration you want to update. Step 13 Updating a Trace Configuration This section describes how to update an existing trace configuration for a service. Click Update to save the changes in the database.

click either OK to delete or Cancel to cancel the delete operation. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Step 6 Cisco CallManager Administration Guide 36-14 OL-1047-01 . From the list of IP addresses at the left of the screen.Chapter 36 Deleting a Trace Configuration Configuring Trace Deleting a Trace Configuration Warning Cisco recommends that you do not use this procedure unless specifically directed to do so by the Cisco Technical Assistance Center (TAC). Choose Service > Trace. From the list of Configured Services. Caution Turning off all trace services also disables Simple Network Management Protocol (SNMP). When asked to confirm the delete operation. click Delete Service. Click Delete to delete the trace configuration for this service. This section describes how to delete a trace configuration. choose the service whose trace configuration you want to delete. choose the IP address of the Cisco CallManager server whose trace configuration you want to delete. If you want to delete all trace services for the chosen Cisco CallManager.

A message displays stating that you are about to permanently delete this service and that the action cannot be undone. choose the IP address of the Cisco CallManager server from which you want to delete a service. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration.Chapter 36 Configuring Trace Deleting a Service Deleting a Service Warning Cisco recommends that you do not use this procedure unless specifically directed to do so by the Cisco Technical Assistance Center (TAC). This section describes how to delete a service from the Cisco CallManager database. Choose Service > Trace. From the list of IP addresses at the left of the screen. Cisco CallManager Administration Guide OL-1047-01 36-15 . Click OK if you want to continue the deletion or Cancel to cancel the operation. Choose the service you wish to delete from the Configured Services list. Click Delete Service.

Chapter 36 Deleting a Service Configuring Trace Cisco CallManager Administration Guide 36-16 OL-1047-01 .

if required. it could take an output stream from a G.729 codec. The same hardware can support Conference Bridges. A transcoder requires specific hardware in order to run. The Cisco CallManager invokes a transcoder on behalf of endpoint devices when the two devices are using different codecs. You cannot have both transcoders and MTPs registered with the same Cisco CallManager at the same time. or PRI interfaces. The transcoder registers with its specified primary Cisco CallManager. In addition. and G. Transcoders for this Cisco CallManager release transcode between G. the transcoder converts the data streams between the two disparate codecs in order to enable communications between them. G.C H A P T E R 37 Configuring Transcoder A transcoder is a device that takes the output stream of one codec and transcodes (converts) it from one compression type to another compression type.323 endpoints when required. for calls to H. a transcoder provides MTP capabilities. and enabling supplementary services. and would normally not be able to communicate. and informs that Cisco CallManager how many transcoder resources are supported. transcoders. When configured as a transcoder. each of which is capable of transcoding data streams between disparate codecs.323 endpoints. Note MTPs are capable of enabling supplementary services for H. Cisco CallManager Administration Guide OL-1047-01 37-1 . When inserted into a call. For example.711 codec and transcode (convert) it in real time to a G.323 endpoints. but they cannot transcode data streams.711. and may be used to enable supplementary services for H. this hardware provides a designated number of streaming mechanisms.723.729 input stream accepted by a G.729 codecs.

The Cisco CallManager also uses transcoder resources as MTPs to enable supplementary services for H. and inserts it into the call. depending on how your system is configured. that Cisco CallManager maintains both sets of resources for a total of 32 registered transcoder resources. When the Cisco CallManager determines that the two endpoints of a call are using disparate codecs and cannot communicate directly. Each transcoder can register with only one Cisco CallManager at a time. or each of them may be registered to a different Cisco CallManager as desired. In this capacity.323 endpoints when required. after a failure. it inserts a transcoder into the call to transcode the datastreams between them. and the endpoint on whose behalf it was inserted. If a transcoder resource is not available when it is needed. Transcoder 2 is also configured for 16 transcoder resources. Transcoder resources are always allocated from the registered transcoder that has the most available resources. that Cisco CallManager controls the set of resources for each of the transcoders. it attempts to register with the next available Cisco CallManager in the list. when more than one transcoder is registered with a given Cisco CallManager. The first Cisco CallManager in the list is the primary (or publisher) Cisco CallManager. The transcoder always registers with its primary Cisco CallManager and. Multiple transcoders may be registered with the same Cisco CallManager.Chapter 37 Configuring Transcoder Each transcoder attempts to register with a given a list of Cisco CallManagers that are arranged in priority order. when the Cisco CallManager determines that an endpoint in a call requires an MTP. it re-registers with the primary Cisco CallManager. Cisco CallManager Administration Guide 37-2 OL-1047-01 . where it acts like a normal MTP. it allocates a transcoder resource. The transcoders may be distributed across a networked system as desired. For example. each of which is registered to the same Cisco CallManager. and supplementary services are not available on that call. If both transcoders register with the same Cisco CallManager. the call is connected without using a transcoder resource. If the primary Cisco CallManager fails. The transcoder is not visible to either the user or the endpoints involved in a call. transcoder 1 is configured for 16 transcoder resources. however. The system may have multiple transcoders. The transcoder is invisible to both the users of the system.

page 37-4 Copying a Transcoder. The transcoder should now appear in the list on the left side of the page. click View Details for more detailed information on the selected device pool. including the status. Click Insert. The page refreshes showing specific information. Cisco CallManager Administration Guide OL-1047-01 37-3 . page 34-1 Configuring Conference Bridges. for the transcoder you just configured. or leave blank to use default. page 37-6 Configuring a Transcoder This section describes how to configure a Transcoder. Enter any special load information into the Special Load Information field. Enter a MAC address (must be at least 12 characters) in the MAC Address field. page 33-1 Configuring a Transcoder. Once you’ve chosen the device pool.Chapter 37 Configuring Transcoder Configuring a Transcoder Related Topics • • • • • • Configuring Media Termination Point. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Click Service > Transcoder. The Description field is automatically generated from the MAC address you provide. Step 4 Step 5 Step 6 Step 7 Select a device pool from the drop-down list box or choose Default in the Device Pool field. page 37-3 Updating a Transcoder. page 37-5 Deleting a Transcoder.

page 34-1 Configuring Conference Bridges. page 37-1 Configuring Media Termination Point. page 37-4 Copying a Transcoder. page 33-1 Updating a Transcoder. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. page 37-6 Updating a Transcoder This section describes how to update a transcoder. Click Service > Transcoder. showing the updated transcoder. page 33-1 Configuring a Transcoder. The page refreshes displaying the transcoder you selected. Select the transcoder you want to update from the list on the left side of the page. Click OK. A message displays stating that the transcoder must be reset before the changes will take effect. The page refreshes again. page 34-1 Configuring Conference Bridges. Related Topics • • • • Configuring Transcoder.Chapter 37 Updating a Transcoder Configuring Transcoder Related Topics • • • • • • Configuring Transcoder. Step 6 Click Reset and follow the instructions in the Reset Device dialog box. Make the desired changes to the transcoder and click Update. page 37-5 Deleting a Transcoder. page 37-3 Cisco CallManager Administration Guide 37-4 OL-1047-01 . page 37-1 Configuring Media Termination Point.

name in the Current Transcoder field. page 37-6 Copying a Transcoder This section describes how to copy a transcoder. click Copy. page 37-5 Deleting a Transcoder. The page refreshes displaying the transcoder you selected. Related Topics • • • • • • Configuring Transcoder. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Click Copy.. Click Service > Transcoder. and repeat steps 1 through 5. Select the transcoder you want to copy from the list on the left side of the page. page 37-3 Updating a Transcoder. Step 6 To build another transcoder that is similar to the current transcoder.. page 34-1 Configuring Conference Bridges. page 37-1 Configuring Media Termination Point. The page refreshes again and displays the transcoder with a Copy of. page 37-4 Deleting a Transcoder. The screen refreshes and the new transcoder appears in the transcoder list on the left side of the page. Make appropriate changes to customize the new transcoder and click Insert. page 37-6 Cisco CallManager Administration Guide OL-1047-01 37-5 . page 33-1 Configuring a Transcoder.Chapter 37 Configuring Transcoder Copying a Transcoder • • Copying a Transcoder.

displaying the transcoder you selected. Click Service > Transcoder. Related Topics • • • • • • Configuring Transcoder. When the page is refreshed. the transcoder you deleted should no longer appear in the transcoder list. page 37-5 Cisco CallManager Administration Guide 37-6 OL-1047-01 . page 37-3 Updating a Transcoder. Click OK if you want to continue or Cancel to cancel the deletion.Chapter 37 Deleting a Transcoder Configuring Transcoder Deleting a Transcoder This section describes how to delete a transcoder. Select the transcoder you want to delete from the list on the left side of the page. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. The page refreshes. Click Delete. page 37-1 Configuring Media Termination Point. page 33-1 Configuring a Transcoder. page 34-1 Configuring Conference Bridges. A message displays stating that you are about to permanently delete this transcoder and that this action cannot be undone. page 37-4 Copying a Transcoder.

calls in progress from an IP phone to an MGCP gateway will also stay up. An All Servers option is provided so that you can view service status or start and stop selected services for all Cisco CallManagers in a cluster. Starting and stopping a Cisco CallManager causes all Cisco IP Phones and gateways currently registered to that Cisco CallManager to fail over to their secondary Cisco CallManager.C H A P T E R 38 Starting and Stopping Services Using the Control Center Control Center for the Cisco CallManager (release 3. such as Conference Bridge and Cisco Messaging Interface. Devices and phones will only need to restart if they can not register with another Cisco CallManager. Cisco CallManager Administration Guide OL-1047-01 38-1 . Starting and stopping Cisco CallManager also causes all other installed applications that are homed to that Cisco CallManager. and any other type of calls will be dropped. calls from an IP phone to another IP phone will stay up. You can view service status or start and stop any of the configured services for a particular Cisco CallManager server. When a Cisco CallManager is stopped. Note Stopping Cisco CallManager also stops call processing for all devices controlled by that Cisco CallManager. to start or stop as well.0 and later) is the web page used for viewing status and starting and stopping the Cisco CallManager and other services.

Procedure Note In order for this procedure to work on all servers in a network. The page updates to display Service Status and Service Control buttons for all services that are configured on the selected server. and the User ID must also have Administration privileges on all servers. page 38-3 Starting and Stopping Services on a Single Server Use the following procedure to view service status or start and stop services on a particular Cisco CallManager server. Click Service > Control Center. The User ID and password you use to log in must be identical on all servers. Cisco CallManager Administration Guide 38-2 OL-1047-01 . Arrow—Running. Question mark—Unknown status. click the Start or Stop button next to the service you want to start or stop. Repeat Steps 1 through 4 to start or stop services on other servers. Select a server from the server list on the left side of the page. Step 4 Step 5 In the Service Control column.Chapter 38 Starting and Stopping Services on a Single Server Starting and Stopping Services Using the Control Center Related Topics • • Starting and Stopping Services on a Single Server. you must be logged in with Administration privileges. Step 1 Step 2 Step 3 Open Cisco CallManager Administration. The Service Status icons have the following meaning: • • • Square—Stopped. page 38-2 Selecting Services to Start and Stop for All Servers.

To select a particular services or group of services. Question mark—Unknown status. then click Refresh the List. The User ID and password you use to log in must be identical on all servers. click Select All and Refresh the List. check only the services you want to display. Arrow—Running. The page refreshes and displays a list of all Cisco CallManagers in the cluster. or view status: • • To select all services. The page updates to display Service Status and Service Control buttons for the selected services for each Cisco CallManager in the list. Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 38-3 . and the User ID must also have Administration privileges on all servers. page 38-1 Selecting Services to Start and Stop for All Servers Use the following procedure to select services you want to start or stop from a list of all Cisco CallManagers in a cluster. Procedure Note In order for this procedure to work on all servers in a network. you must be logged in with Administration privileges. Click Service > Control Center. stop. Step 4 Select the services for which you want to start. The Service Status icons have the following meaning: • • • Square—Stopped.Chapter 38 Starting and Stopping Services Using the Control Center Selecting Services to Start and Stop for All Servers Related Topics • • Selecting Services to Start and Stop for All Servers. Select All Servers from the server list on the left side of the page (it is the first item in the list). page 38-3 Starting and Stopping Services Using the Control Center.

page 38-1 Cisco CallManager Administration Guide 38-4 OL-1047-01 . page 38-2 Starting and Stopping Services Using the Control Center. Related Topics • • Starting and Stopping Services on a Single Server.Chapter 38 Selecting Services to Start and Stop for All Servers Starting and Stopping Services Using the Control Center Step 5 Click the Start or Stop button next to the services you wish to start or stop for each server in the list.

P A R T 5 Feature Configuration The following chapters include information on configuring user features: • Chapter 39. “Configuring Call Pickup” • Chapter 41. “Configuring Cisco IP Phone Services” . “Configuring Call Park” • Chapter 40.

.

C H A P T E R 39 Configuring Call Park Call park allows you to place a call on hold so that it can be retrieved from another phone in the system. You can park only one call at each call park extension number. update. you can park the call to a call park extension such as 1234. For example. Use the following procedures to add. page 39-4 Cisco CallManager Administration Guide OL-1047-01 39-1 . You can define either a single directory number or a range of directory numbers for use as call park extension numbers. Someone on another phone in your system can then dial 1234 to retrieve the call. page 39-3 Deleting a Call Park Number. page 39-2 Updating a Call Park Number. if you are on an active call at your phone. or delete a call park extension: • • • Adding a Call Park Number.

Cisco CallManager Administration Guide 39-2 OL-1047-01 . Note You can create a maximum of 100 call park numbers with one call park range definition. Enter the call park extension number. Note Each Cisco CallManager in a cluster requires its own unique call park numbers. enter 5555 to define a single call park extension number of 5555. You can enter literal digits or the wildcard character X. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Step 5 Using the drop-down list box. select the desired route partition from the drop-down list box. For example. Note The combination of call park extension number and route partition must be unique within the Cisco CallManager cluster.Chapter 39 Adding a Call Park Number Configuring Call Park Adding a Call Park Number This section describes how to add a single call park extension number or range of extension numbers. or enter 55XX to define a range of call park extension numbers from 5500 to 5599. Step 4 If you want to use a route partition to restrict access to the call park numbers. select the Cisco CallManager to which these call park numbers apply. If you do not want to restrict access to the call park numbers. select None for the route partition. Select Feature > Call Park.

Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Make the desired changes in the fields you want to update. you can click Cancel to reset all fields to their original values. page 39-1 Adding a Cisco CallManager. page 39-3 Deleting a Call Park Number. Select the call park number or range of numbers you want to update from the call park list. Step 5 Click Update to save the changes in the database. page 2-1 Configuring Call Park. Note Before saving the changes. page 39-4 Updating a Call Park Number This section describes how to update a call park extension number or range of numbers. Cisco CallManager Administration Guide OL-1047-01 39-3 .Chapter 39 Configuring Call Park Updating a Call Park Number Step 6 Click Insert to save the new call park numbers in the database. page 12-1 Updating a Call Park Number. Related Topics • • • • • Clusters. The call park number you added should appear in the list on the left side of the page. Select Feature > Call Park.

Select Feature > Call Park. Related Topics • • • Configuring Call Park. Select the call park number or range of numbers you want to delete from the call park list. page 39-1 Adding a Call Park Number. Click Delete. page 39-4 Deleting a Call Park Number This section describes how to delete call park numbers from the Cisco CallManager database. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration.Chapter 39 Deleting a Call Park Number Configuring Call Park Related Topics • • • Configuring Call Park. page 39-1 Adding a Call Park Number. page 39-2 Deleting a Call Park Number. page 39-2 Updating a Call Park Number. page 39-3 Cisco CallManager Administration Guide 39-4 OL-1047-01 .

• The procedures are the same for configuring both of these features. you can redirect the call to your phone by using the call pickup feature.C H A P T E R 40 Configuring Call Pickup Call pickup allows you to answer a call that comes in on a directory number other than your own. When you hear an incoming call ringing on another phone. Group Call Pickup allows users to pick up incoming calls within their own group or in other groups. Users must dial the appropriate call pickup group number when using this feature. and they are described in: • Configuring Call Pickup. page 40-2 Cisco CallManager Administration Guide OL-1047-01 40-1 . The appropriate call pickup group number is dialed automatically when a user activates this feature. There are two types of call pickup available on Cisco IP Phones: • Call Pickup allows users to pick up incoming calls within their own group.

page 47-9. see the “Adding a Call Pickup Group Number” section on page 40-2. Select Feature > Call Pickup. Add a Call Pickup or Group Call Pickup button to the phone templates where needed. page 40-1 Adding a Call Pickup Group Number. For details. page 40-5 Adding a Call Pickup Group Number This section describes how to add a call pickup group number to the Cisco CallManager database. For details. page 40-4 Assigning Directory Numbers to a Call Pickup Group. see the “Assigning Directory Numbers to a Call Pickup Group” section on page 40-5. page 40-2 Updating a Call Pickup Group Number. see the Modifying Phone Button Templates.Chapter 40 Configuring Call Pickup Configuring Call Pickup Configuring Call Pickup This section describes the general steps for configuring the call pickup feature. Step 3 Related Topics • • • • • Configuring Call Pickup. For details. Procedure Step 1 Step 2 Create a call pickup group number. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Assign the desired directory numbers to a call pickup group by using the call pickup group number you created in Step 1. page 40-3 Deleting a Call Pickup Group Number. Cisco CallManager Administration Guide 40-2 OL-1047-01 . Subsequent sections of this chapter describe the steps in more detail. Enter the directory number for the call pickup group you want to add.

page 40-3 Deleting a Call Pickup Group Number. Note The combination of call pickup group number and route partition must be unique within the Cisco CallManager cluster. Select the call pickup group number you want to update. page 40-1 Updating a Call Pickup Group Number. select None for the route partition. Before saving the changes. Click Update to save the changes in the database. page 2-1 Configuring Call Pickup. If you do not want to restrict access to the call pickup group. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. page 40-4 Assigning Directory Numbers to a Call Pickup Group. select the desired route partition from the drop-down list box.Chapter 40 Configuring Call Pickup Configuring Call Pickup Step 4 If you want to use a route partition to restrict access to the call pickup group. Related Topics • • • • • Clusters. Step 5 Click Insert to save the new call pickup group number in the database. Cisco CallManager Administration Guide OL-1047-01 40-3 . Select Feature > Call Pickup. page 40-5 Updating a Call Pickup Group Number This section describes how to update a call pickup group number. you can click Cancel to reset all fields to their original value. Make the desired changes in the fields you want to update.

For details. Caution When you delete a call pickup group number. page 40-1 Adding a Call Pickup Group Number. you disable the Call Pickup feature for all directory numbers assigned to that group. page 40-2 Cisco CallManager Administration Guide 40-4 OL-1047-01 . see the “Assigning Directory Numbers to a Call Pickup Group” section on page 40-5. Related Topics • • • • Configuring Call Pickup. you must reassign each of them to a new call pickup group. page 40-5 Deleting a Call Pickup Group Number This section describes how to delete a call pickup group number from the Cisco CallManager database. The call pickup group is now removed from the list on the left side of the page. page 40-4 Assigning Directory Numbers to a Call Pickup Group. page 40-2 Deleting a Call Pickup Group Number. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Select Feature > Call Pickup. it is automatically updated for all directory numbers assigned to that call pickup group. To enable Call Pickup again for those directory numbers. Click Delete. Select the call pickup group number you want to delete.Chapter 40 Configuring Call Pickup Configuring Call Pickup When you update a call pickup group number. page 40-1 Adding a Call Pickup Group Number. Related Topics • • Configuring Call Pickup.

Select the desired directory number to display the configuration information for the phone where that number appears. Select the line where the desired directory number appears. Only directory numbers assigned to a call pickup group can use the Call Pickup feature. page 40-2 Cisco CallManager Administration Guide OL-1047-01 40-5 . Before You Begin Before you can assign a directory number to a call pickup group. Repeat Step 2 through Step 6 for each directory number you want to assign to the call pickup group. page 40-5 Assigning Directory Numbers to a Call Pickup Group This section describes how to assign directory numbers to a call pickup group. page 40-2 Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Open Cisco CallManager Administration. Use the search capability to find a directory number that you want to assign to a call pickup group. you must create a number for that group as described in: • Adding a Call Pickup Group Number. Select Device > Phone. page 40-1 Adding a Call Pickup Group Number. page 40-3 Assigning Directory Numbers to a Call Pickup Group. Select the desired call pickup group number from the Call Pickup Group drop-down list box. Related Topics • • Configuring Call Pickup.Chapter 40 Configuring Call Pickup Configuring Call Pickup • • Updating a Call Pickup Group Number.

Chapter 40 Configuring Call Pickup Configuring Call Pickup • • Updating a Call Pickup Group Number. page 40-3 Deleting a Call Pickup Group Number. page 40-4 Cisco CallManager Administration Guide 40-6 OL-1047-01 .

Once the list of services is configured. page 41-5 Updating a Cisco IP Phone Service. page 41-3 Adding a Cisco IP Phone Service Parameter. page 41-7 Cisco CallManager Administration Guide OL-1047-01 41-1 . page 41-2 Adding a Cisco IP Phone Service. Cisco CallManager (Release 3. Note Currently. page 41-6 Deleting a Cisco IP Phone Service. users can log on to the Cisco CallManager user preferences pages and subscribe to these services for their Cisco IP Phones. This section covers the following topics: • • • • • Understanding Cisco IP Phone Services.C H A P T E R 41 Configuring Cisco IP Phone Services The Cisco IP Phone Services Configuration area of Cisco CallManager Administration is where system administrators define and maintain the list of Cisco IP Phone Services to which users can subscribe at their site. Cisco IP Phone services are XML applications that enable interactive content with text and graphics to be displayed on Cisco IP Phones. You can also create customized Cisco IP Phone applications for your site. only Cisco IP Phone 7960 and 7940 model phones support Cisco IP Phone services.0(5) or later) provides sample Cisco IP Phone services applications.

or user IDs. and news quotes. zip codes.Chapter 41 Understanding Cisco IP Phone Services Configuring Cisco IP Phone Services • • Updating a Cisco IP Phone Service Parameter. page 41-8 Deleting a Cisco IP Phone Service Parameter. which help end users browsing the system A list of parameters that are appended to the URL when it is sent to the server These are used to personalize a service for an individual user. When a service is selected from the menu. Examples of parameters include stock ticker symbols.” When the user presses this button. city names. page 41-9 Understanding Cisco IP Phone Services Cisco IP Phone Services are XML applications that enable interactive content with text and graphics to be displayed on Cisco IP Phones. stock quotes. the phone uses its HTTP client to load a specific URL that contains a menu of services to which the user has subscribed for their phone. users can log on to the Cisco CallManager user preferences pages and subscribe to services. which then updates the phone's display. The following information is configured for each service: • • • URL of the server that provides the content Service name and description.) Cisco CallManager Administration Guide 41-2 OL-1047-01 . After the system administrator configures the services. such as Microsoft's Internet Information Service (IIS). Only services configured through Cisco CallManager Administration are available for user subscription. users can • • • • Customize the name of the service as it is displayed on their services list Enter any service parameters available for the selected phone service Review the description of each phone service parameter Subscribe to that service on their phone (Subscriptions are made on a per-device basis. From the user preferences pages. and a server provides the content. the URL is requested via HTTP. The user then selects a service from the listing. Typical services that might be supplied to a phone include weather information. The Cisco IP Phone model 7960 and 7940 telephones have a button labeled “services. Cisco IP Phone Services are deployed using the HTTP protocol from standard web servers.

such as the TFTP server or directory database publisher server. Select Features > Cisco IP Phone Services. Click New. Description of the content provided by the service. This precaution eliminates the possibility of errors in a Cisco IP Phone Service application having an impact on Cisco CallManager performance or interrupting call processing services. a custom URL is built and stored in the database for this subscription. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Enter configuration settings for the new service. Cisco CallManager Administration Guide OL-1047-01 41-3 . Adding a Cisco IP Phone Service Perform the following steps to add a Cisco IP Phone Service.Chapter 41 Configuring Cisco IP Phone Services Adding a Cisco IP Phone Service When the user clicks the Subscribe button. Caution Do not put Cisco IP Phone services on any Cisco CallManager server at your site or any server associated with Cisco CallManager. Table 41-1 Cisco IP Phone Service Configuration Settings Field Service Name Service Description Description Name of the service as it will display on the menu of available services on the user preferences pages. The service then appears on the device’s services list. as described in Table 41-1.

Refer to the “Adding a Cisco IP Phone Service Parameter” section on page 41-5.asp Where <Server> is a fully qualified domain name or an IP address. This server must be independent of the servers in your Cisco CallManager cluster.Chapter 41 Adding a Cisco IP Phone Service Configuring Cisco IP Phone Services Table 41-1 Cisco IP Phone Service Configuration Settings (continued) Field Service URL Description URL to the server where the Cisco IP Phone Services application is located. Step 5 Click Update to add the service. Related Topics • • • Deleting a Cisco IP Phone Service. page 41-7 Updating a Cisco IP Phone Service. For the services to be available. you can add and configure parameters for the service. For example: http://<Server>/ccmuser/sample/sample. Do not specify a Cisco CallManager server or any server associated with Cisco CallManager (such as a TFTP server or directory database publisher server). Once the service is added to the list. page 41-5 Cisco CallManager Administration Guide 41-4 OL-1047-01 . page 41-6 Adding a Cisco IP Phone Service Parameter. the phones in the Cisco CallManager cluster must have network connectivity to the server.

Descriptive parameter name to display to the user on the user preferences page. Refer to the documentation for the individual Cisco IP Phone service for specific information about whether the service uses parameters and how those parameters should be configured. Parameter definitions are optional. Check the Parameter is Required box if the user must enter data for this parameter before the subscription can be saved. Before you can configure parameters.Chapter 41 Configuring Cisco IP Phone Services Adding a Cisco IP Phone Service Parameter Adding a Cisco IP Phone Service Parameter Use the following procedure to add and configure Cisco IP Phone service parameters. Table 41-2 Cisco IP Phone Service Parameter Configuration Settings Field Parameter Name Parameter Display Name Default Value Description The exact query string parameter to use when building the subscription URL. Select Features > Cisco IP Phone Services. the phone service must already have been added. Click the New button to the right of the Service Parameter Information list box to open the Cisco IP Phone Service Parameter Configuration dialog. Default value for the parameter. Select the service to which you wish to add parameters from the list of Cisco IP Phone services on the left side of the page. The text entered here will be available to the user while they are subscribing to the service. The parameter description should provide information or examples to help users input the correct value for the parameter. Configure the phone service parameter settings as described in Table 41-2. This value will display to the user when a service is being subscribed to for the first time. Parameter is Required Parameter Description Cisco CallManager Administration Guide OL-1047-01 41-5 . Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Log in to Cisco CallManager Administration.

be sure to click Update Subscriptions to update all currently subscribed users with the changes. or change the Parameter Name of a phone service parameter for a phone service to which users are already subscribed. users must re-subscribe to the service to rebuild the URL correctly. Cisco CallManager Administration Guide 41-6 OL-1047-01 . remove a Cisco IP Phone service parameter. Repeat Steps 4 through 6 to add additional parameters. Note If you change the service URL. Select the Cisco IP Phone Service you wish to update from the list of Cisco IP Phone services on the left side of the page.Chapter 41 Updating a Cisco IP Phone Service Configuring Cisco IP Phone Services Step 6 Step 7 Step 8 Click Insert to add the new parameter. Updating a Cisco IP Phone Service Perform the following steps to update a Cisco IP Phone service (for example. “Updating a Cisco IP Phone Service Parameter” section on page 41-8. Click Insert and Close to add the last parameter. If you do not do so. and “Deleting a Cisco IP Phone Service Parameter” section on page 41-9 for more information. Click Features > IP Phone Services. Make the desired changes to the configuration settings. to change the service URL or other information). Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Refer to Table 41-1 for information about configuration settings. Add. if needed. Refer to the “Adding a Cisco IP Phone Service” section on page 41-3. or delete parameters as needed. update.

user subscriptions. or changed the Parameter Name for a phone service parameter. Note When you delete a Cisco IP Phone subscription. Select Features > Cisco IP Phone Services. Select the name of the Cisco IP Phone service you wish to delete from the list of Cisco IP Phone services on the left side of the page.Chapter 41 Configuring Cisco IP Phone Services Deleting a Cisco IP Phone Service Step 6 Update the Cisco IP Phone Services Configuration pages to apply the changes: • Click Update Subscriptions to rebuild all user subscriptions if the service was modified after subscriptions existed. Procedure Step 1 Step 2 Step 3 Step 4 Log in to Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 41-7 . all service information. removed a phone service parameter. Click Update if the service is new and you do not need to rebuild user subscriptions. You must update subscriptions if you have changed the service URL. page 41-7 Deleting a Cisco IP Phone Service Perform the following steps to update a Cisco IP Phone service. • Related Topics • • Adding a Cisco IP Phone Service. Click Delete. page 41-3 Deleting a Cisco IP Phone Service. and user subscription data are removed from the database.

page 41-6 Adding a Cisco IP Phone Service. users must re-subscribe to the service to rebuild the URL correctly. be sure to click Update Subscriptions to update all currently subscribed users with the changes. Click Update to apply the changes.Chapter 41 Updating a Cisco IP Phone Service Parameter Configuring Cisco IP Phone Services Related Topics • • Updating a Cisco IP Phone Service. or click Update and Close to apply the changes and close the dialog. Click Edit. Cisco CallManager Administration Guide 41-8 OL-1047-01 . Make the desired changes to the parameter settings. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Log in to Cisco CallManager Administration. Note If you remove a Cisco IP Phone service parameter or change the Parameter Name of a phone service parameter for a phone service to which users are already subscribed. Refer to Table 41-2 for information about service parameter configuration settings. Select the phone service you wish to update from the list of Cisco IP Phone services on the left side of the page. Click on the name of the parameter you wish to update in the Parameters list box under Service Parameter Information. If you do not do so. page 41-3 Updating a Cisco IP Phone Service Parameter Perform the following steps to update a service parameter for a specific Cisco IP Phone service. Select Features > Cisco IP Phone Services.

Click Features > Cisco IP Phone Services. Cisco CallManager Administration Guide OL-1047-01 41-9 . Click Update if the service is new and you do not need to rebuild user subscriptions. users must re-subscribe to the service to rebuild the URL correctly. Select the phone service whose parameters you wish to delete from the list of Cisco IP Phone services on the left side of the page. You must update subscriptions if you changed the service URL. Click Delete. removed a phone service parameter. page 41-6 Deleting a Cisco IP Phone Service Parameter. Note If you remove a phone service parameter or modify the Parameter Name of a phone service parameter for a phone service to which users are already subscribed.Chapter 41 Configuring Cisco IP Phone Services Deleting a Cisco IP Phone Service Parameter Step 8 Update the Cisco IP Phone Services Configuration page to apply the changes: • Click Update Subscriptions to rebuild all user subscriptions if the service was modified after subscriptions existed. you must click Update Subscriptions to update all currently subscribed users with the changes. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Click on the name of the parameter you wish to delete in the Parameters list box under Service Parameter Information. page 41-9 Deleting a Cisco IP Phone Service Parameter Perform the following steps to delete a Cisco IP Phone service. or changed the Parameter Name for a phone service parameter. • Related Topics • • Updating a Cisco IP Phone Service. If you do not do so.

Click Update if the service is new and you do not need to rebuild user subscriptions. or changed the Parameter Name for a phone service parameter. page 41-5 Cisco CallManager Administration Guide 41-10 OL-1047-01 . • Related Topics • • Updating a Cisco IP Phone Service Parameter. Update the Cisco IP Phone Services Configuration page to apply the changes: • Click Update Subscriptions to rebuild all user subscriptions if the service was modified after subscriptions existed. removed a phone service parameter.Chapter 41 Deleting a Cisco IP Phone Service Parameter Configuring Cisco IP Phone Services Step 6 Step 7 Click OK to confirm the deletion. You must update subscriptions if you changed the service URL. page 41-8 Adding a Cisco IP Phone Service Parameter.

P A R T 6 Configuring Devices in Cisco CallManager The following chapters include information on configuring devices in Cisco CallManager: • Chapter 42. “Configuring Gateways” • Chapter 46. “Configuring Phone Button Templates” . “Configuring a Gatekeeper” • Chapter 45. “Configuring Cisco IP Phones in Cisco CallManager” • Chapter 47. “Configuring Cisco uOne Voice Messaging” • Chapter 44. “Configuring CTI Route Points” • Chapter 43.

.

Cisco IP Auto Attendant. page 42-4 Finding and Listing CTI Route Points. For first-party call control. and Cisco IP Interactive Voice Response System. Applications that use CTI route points and CTI ports include Cisco SoftPhone. refer to the documentation and online help included with these applications. page 42-6 Cisco CallManager Administration Guide OL-1047-01 42-1 . This section describes the following basic procedures: • • • • • Adding a CTI Route Point. you must add a CTI port for each active voice line.C H A P T E R 42 Configuring CTI Route Points A Cisco Telephony Integration (CTI) route point is a virtual device that can receive multiple simultaneous calls for application-controlled redirection. page 42-2 Modifying a CTI Route Point. page 42-5 Resetting a CTI Route Point. For detailed instructions on how to configure CTI route points and CTI ports associated with these applications. page 42-3 Deleting a CTI Route Point.

connections. dash. including alphanumeric. Region. and Calling Search Space for auto-registration. Specifies the collection of route partitions searched to determine how a collected (originating) number should be routed. Description Device Pool Descriptive name for the CTI route point. dot. Select the name of a Device Pool from the drop-down list box. Select a calling search space from the drop-down list box. Table 42-1 CTI Route Point Configuration Settings Field Device Name Description Unique identifier for this device. Date/Time Group. Specifies the collection of properties for this device including CallManager Group. Select Device > CTI Route Point.Chapter 42 Adding a CTI Route Point Configuring CTI Route Points Adding a CTI Route Point Perform the following procedure to add a CTI route point. as defined in Table 42-1. Location Specifies the remote location Select the name of a location from accessed using restricted bandwidth the drop-down list box. Click the Add a New CTI Route Point link. Usage Notes • • This field is required. Enter the appropriate settings. Enter from 1 to 15 characters. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. Calling Search Space Cisco CallManager Administration Guide 42-2 OL-1047-01 . or underscores.

Cisco CallManager Administration Guide OL-1047-01 42-3 . For instructions on how to add and configure lines (directory numbers). Click Find. and the list on the left side of the page displays an icon that you can click to begin adding lines to the route point. The page refreshes to show the current settings for the selected CTI route point. Step 6 Make the desired changes to the configuration settings. Select Device > CTI Route Point. page 42-6 Modifying a CTI Route Point Perform the following steps to modify a CTI route point: Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. page 42-5 Resetting a CTI Route Point. The Find/List CTI Route Points page displays. Specify the search criteria needed to locate the CTI route point you want to delete.Chapter 42 Configuring CTI Route Points Modifying a CTI Route Point Step 5 Click Insert to add the new CTI route point. The page updates to display a list of CTI route points that match the specified search criteria. The page refreshes to display the information entered for the new CTI route point. Click on the name of the CTI route point whose settings you want to modify. page 42-3 Deleting a CTI Route Point. page 42-4 Finding and Listing CTI Route Points. refer to the “Adding a Directory Number” section on page 46-19 Related Topics • • • • Modifying a CTI Route Point. Refer to Table 42-1 on page 42-2 for detailed descriptions of CTI route point configuration settings.

page 42-3 Cisco CallManager Administration Guide 42-4 OL-1047-01 . page 42-4 Finding and Listing CTI Route Points. page 42-5 Resetting a CTI Route Point. page 42-2 Modifying a CTI Route Point. Click Find. Specify the search criteria needed to locate the CTI route point you want to delete. A confirmation dialog displays.Chapter 42 Deleting a CTI Route Point Configuring CTI Route Points Step 7 Click Update to apply the changes. You can also click on the name of the CTI route point you want to delete from the list to display its current settings and then click Delete. Related Topics • • Adding a CTI Route Point. The Find/List CTI Route Points page displays. The page refreshes to display the new settings. The page refreshes to display a list of the CTI route points that match the specified search criteria. page 42-2 Deleting a CTI Route Point. Click the Delete icon for the CTI route point in the list that you want to delete. Select Device > CTI Route Point. page 42-6 Deleting a CTI Route Point Perform the following procedure to delete a CTI route point: Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Open Cisco CallManager Administration. Step 6 Click OK to permanently delete the CTI route point. Related Topics • • • • Adding a CTI Route Point.

click Next. click Find without entering any search text. Select Device > CTI Route Point. page 42-3 Deleting a CTI Route Point. To list all items. Related Topics • • • • • Adding a CTI Route Point. Step 5 To view the next set of CTI route points. The total number of CTI route points and pages are also listed on this page. Step 3 Step 4 Select the search criteria to use. The Find and List Route Points page displays. The first 20 CTI route points that match the search criteria are listed. page 42-5 Resetting a CTI Route Point. Procedure Step 1 Step 2 Open Cisco CallManager. or use "Device Name is not empty" as the search criteria. page 42-2 Modifying a CTI Route Point.Chapter 42 Configuring CTI Route Points Finding and Listing CTI Route Points • • Finding and Listing CTI Route Points. Click Find. page 42-4 Resetting a CTI Route Point. page 42-1 Cisco CallManager Administration Guide OL-1047-01 42-5 . page 42-6 Configuring CTI Route Points. page 42-6 Finding and Listing CTI Route Points Perform the following procedure to find and list CTI route points.

Step 6 Click one of the following: • • • Restart Device—Restarts a device without shutting it down. The Reset Device dialog is displayed. The Find and List CTI Route Points page displays. Related Topics • • • • Adding a CTI Route Point. page 42-4 Finding and Listing CTI Route Points.Chapter 42 Resetting a CTI Route Point Configuring CTI Route Points Resetting a CTI Route Point Perform the following procedure to reset a CTI route point: Procedure Step 1 Step 2 Open Cisco CallManager. Step 5 Click the Reset icon for the CTI route point you want to reset. Close—Closes the Reset Device dialog without performing any action. Click Find. page 42-3 Deleting a CTI Route Point. page 42-5 Cisco CallManager Administration Guide 42-6 OL-1047-01 . Reset Device—Shuts down a device and brings it back up. The CTI route points that match the search criteria are listed. Step 3 Step 4 Select the search criteria to use. Select Device > CTI Route Point. page 42-2 Modifying a CTI Route Point.

This section describes the procedures required for adding and configuring Cisco uOne ports in Cisco CallManager. Configure values for Cisco CallManager service parameters associated with Cisco uOne. All users and their directory numbers must be entered in Cisco CallManager Administration to retrieve messages from a Cisco uOne voice mail device. Set Forward Busy and Forward No Answer for Cisco IP Phones that will be accessing voice mail. available as part of Cisco IP Telephony Solutions. Configure a message waiting indicator (MWI) device. provides voice messaging capability for users when they are unavailable to answer calls. • • • Cisco CallManager Administration Guide OL-1047-01 43-1 . To connect Cisco uOne to Cisco CallManager.C H A P T E R 43 Configuring Cisco uOne Voice Messaging The optional Cisco Unified Open Network Exchange (uOne) software. you need to: • Add Cisco uOne ports to Cisco CallManager.

“Configuring Call Forward” section on page 46-17 Installation and configuration documentation supplied with Cisco uOne. “Setting up the MWI Device” section on page 43-11 Installation and configuration documentation supplied with Cisco uOne. page 43-19 Cisco CallManager Administration Guide 43-2 OL-1047-01 . refer to the installation and configuration documentation that shipped with the software. Step 3 Configure the MWI device. page 43-16 Resetting a Cisco uOne Port. Service Parameters for Cisco uOne” section on page 43-8 Installation and configuration documentation supplied with Cisco uOne. page 43-3 Adding Cisco uOne Ports. Add a Cisco uOne server and ports to the Cisco CallManager database. For more information about configuring Cisco CallManager with Cisco uOne.Chapter 43 Configuring Cisco uOne Voice Messaging The following table provides an overview of the steps required to configure Cisco CallManager with Cisco uOne voice messaging: Procedure Step 1 Step 2 Reference “Cisco uOne Port Wizard” section on page 43-3. page 43-18 Copying an Existing Cisco uOne Port. Step 4 Set up Call Forward No Answer and Call Forward Busy on all Cisco IP Phones that will be used with Cisco uOne. Configure CallManager service parameter “Configuring Cisco CallManager values. page 43-17 Updating a Cisco uOne Port. page 43-12 Deleting a Cisco uOne Port. Related Topics • • • • • • Cisco uOne Port Wizard.

The Cisco uOne Server page displays. Before You Begin The uOne wizard requires a range of consecutive directory numbers for the uOne ports.ini uOne configuration file (the default is CiscoUM). the uOne wizard prompts you enter the name of the Cisco uOne Server to add (see Step 6). Enter the name of the Cisco uOne device. the Cisco uOne Server page displays. This name must match the CMDeviceName value in the SS. page 43-6 Deleting Ports from an Existing Cisco uOne Server. Otherwise. page 43-7 Adding a New Cisco uOne Server and Ports Perform the following steps to use the Cisco uOne Port wizard to add a new Cisco uOne server and ports to the Cisco CallManager database. Step 4 Step 5 Step 6 Cisco CallManager Administration Guide OL-1047-01 43-3 . Click on the Use the Cisco uOne Wizard link in upper right corner of the page.Chapter 43 Configuring Cisco uOne Voice Messaging Cisco uOne Port Wizard Cisco uOne Port Wizard The Cisco uOne Port wizard is a tool that allows Cisco CallManager administrators to quickly add and delete ports associated with a Cisco uOne server to the Cisco CallManager database. page 43-3 Adding Ports to an Existing Cisco uOne Server. The following procedures are described in this section: • • • Adding a New Cisco uOne Server and Ports. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Select Device > Cisco uOne Port. Make sure the voice mail pilot number and subsequent numbers are available. Select Create a new Cisco uOne server and add ports to it. Click Next. If there are no existing Cisco uOne ports.

The wizard will apply these configuration settings to all of the new ports. Collection of partitions that are searched for numbers called from this directory number. Select the number of ports to add from the list. because the wizard automatically appends this when adding the ports. The Cisco uOne Ports page is displayed. Select the default value of None. Click Next. Enter the appropriate configuration settings. Table 43-1 uOne Port Wizard Device Information Settings Field Device Information Description Clarifies the purpose of device. Usage Notes Description Device Pool Calling Search Space Location Remote location accessed using restricted bandwidth connections. Cisco CallManager Administration Guide 43-4 OL-1047-01 . The Cisco uOne Device Information page is displayed. The Cisco uOne Pilot Number page displays. Step 7 Step 8 Step 9 Step 10 Click Next.Chapter 43 Cisco uOne Port Wizard Configuring Cisco uOne Voice Messaging You do not need to add the "-VI<port_number>" suffix. Step 11 Step 12 Click Next. as described in Table 43-1. Enter the pilot number configuration settings as described in Table 43-2. Select the default value of Default Pool.

you must select a Calling Search Space that includes the selected Route Partition. Usage Notes A pilot number is required. Select None if partitions are not used. This number must be the same as the Cisco Voice Mail pilot directory number configured in the Cisco uOne DialMap. you must select a Calling Search Space that includes the selected Route Partition. Route Partition Route partition to which this set of directory numbers belong.Chapter 43 Configuring Cisco uOne Voice Messaging Cisco uOne Port Wizard Table 43-2 uOne Port Wizard Pilot Number Configuration Settings Field Pilot Number Description The number people call to access the Cisco uOne server. The operator number is the number to which the last port is forwarded. Enter an operator number (optional). A summary screen that lists the settings you configured in the previous screens displays. If a Route Partition is selected.ini file. The Cisco uOne wizard automatically assigns the correct values for the Forward Busy and Forward No Answer fields for each port. If a Route Partition is selected. Select a partition from the drop-down list. instead of getting a busy signal if all ports are in use. Step 13 Step 14 Click Next. Cisco CallManager Administration Guide OL-1047-01 43-5 . The Cisco uOne Operator Number page is displayed. Step 15 Click Next. Each new port receives the next available directory number. Calling Search Space Collection of partitions that are searched for numbers called from this directory number. Supplying an attendant's number here gives the caller another chance to reach the party they were calling. A caller is directed to this number if all ports on the Cisco uOne Server are busy.

Select the name of an existing Cisco uOne server (pilot number) from the list and click Next. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. click Finish to add the new ports. Select Add Ports to an Existing Cisco uOne Server. which lists the number of ports that are currently configured. The Cisco uOne Server page displays. Related Topics • • Adding Ports to an Existing Cisco uOne Server. Select Device > Cisco uOne Port. The voice mail pilot number is the number people call to access the Cisco uOne server. If the information shown is not correct.Chapter 43 Cisco uOne Port Wizard Configuring Cisco uOne Voice Messaging Step 16 If this information is correct.ini files. page 43-6 Deleting Ports from an Existing Cisco uOne Server.ini file. Before You Begin The uOne wizard requires a range of consecutive directory numbers for the uOne ports. Click Next. click the Back button to edit the information. Refer to the Cisco uOne documentation for information about the Cisco uOne . Make sure the voice mail pilot number and subsequent numbers are available. This number is the Cisco Voice mail pilot directory number configured in the Cisco uOne DialMap. or Cancel to quit without adding any ports. Click on the Use the Cisco uOne Wizard link in the upper right corner of the page. page 43-7 Adding Ports to an Existing Cisco uOne Server Perform the following steps to use the Cisco uOne Port wizard to add ports to an existing Cisco uOne server. Cisco CallManager Administration Guide 43-6 OL-1047-01 . The Cisco uOne Ports page is displayed. The Cisco uOne Server page displays.

Step 8 Step 9 Click Next. If needed. Procedure Step 1 Step 2 Step 3 Step 4 Open Cisco CallManager Administration. The Cisco uOne Server page displays. If this information is correct. A summary page is displayed that shows the configuration information for the Cisco uOne server to which you added the ports. Select Delete ports from an existing Cisco uOne server and click Next. Select Device > uOne Port. If the information shown is not correct. page 43-7 Deleting Ports from an Existing Cisco uOne Server Perform the following steps to use the Cisco uOne Port wizard to delete ports from an existing Cisco uOne server. then click Next. add. The Cisco uOne wizard automatically assigns consecutive directory numbers following the last port.Chapter 43 Configuring Cisco uOne Voice Messaging Cisco uOne Port Wizard Step 7 Select the number of ports to add from the list and click Next. change. click the Back button to edit the information or click Cancel to quit without adding any ports. Select the Use the Cisco uOne Wizard link in the upper right corner of the page. The Cisco uOne Server page displays. and uses the same Route Partition and Calling Search Space settings as the Cisco uOne voice mail pilot directory number. Cisco CallManager Administration Guide OL-1047-01 43-7 . click Finish to add the new ports. or remove the Operator Number for this Cisco uOne server and ports. page 43-3 Deleting Ports from an Existing Cisco uOne Server. Step 10 Related Topics • • Adding a New Cisco uOne Server and Ports. The Ready to Add Ports summary screen displays the new settings.

Note For Cisco IP Phone 12 SP+ and 30 VIP models. click Finish to delete the selected ports. and Forward No Answer numbers so that they are consecutive. A summary page is displayed that shows the updated settings for the Cisco uOne server from which you deleted the ports. Cisco CallManager Administration Guide 43-8 OL-1047-01 . The Cisco uOne Ports page is displayed. If the information shown is not correct. which lists the number of ports that are currently configured. click the Back button to edit the information. The Cisco uOne wizard automatically updates the port numbers. the phone button template for the user’s phone must have a button configured for Message Waiting for this feature to be available. Related Topics • • Adding a New Cisco uOne Server and Ports. directory numbers. page 43-6 Configuring Cisco CallManager Service Parameters for Cisco uOne The following Cisco CallManager service parameters must be set up when configuring Cisco CallManager to work with Cisco uOne: • MessageWaitingOnDN and MessageWaitingOffDN—Cisco uOne uses the MWI On and MWI Off directory numbers specified by these two service parameters to turn the Message Waiting Indicator (MWI) on a user's phone on or off. Step 7 If this information is correct. page 43-3 Adding Ports to an Existing Cisco uOne Server. Step 6 Select the number of ports to delete from the list and click Next. Forward Busy. or Cancel to quit without deleting any ports.Chapter 43 Configuring Cisco CallManager Service Parameters for Cisco uOne Configuring Cisco uOne Voice Messaging Step 5 Select the name of an existing Cisco uOne server (pilot number) from the list and click Next.

ForwardNoAnswerTimeout—Specifies the number of seconds to wait before forwarding on a No Answer condition. Note You must set the MWI On/Off service parameters for each Cisco CallManager in the cluster. you must first stop the Cisco uLite process in Cisco uOne. Select Service > Service Parameters. refer to the installation and configuration documentation supplied with Cisco uOne.Chapter 43 Configuring Cisco uOne Voice Messaging Configuring Cisco CallManager Service Parameters for Cisco uOne • VoiceMail—Voice mail pilot number (the number users dial to call in to the voice mail system). This value is the number to be dialed to turn off the message waiting indicator as configured in Cisco CallManager. Select MessageWaitingOffDN from the Configured Service Parameters list. Before You Begin Before changing the values of the MWI On/Off service parameters. Cisco CallManager Administration Guide OL-1047-01 43-9 . In the Value field. Step 7 Click Update.ini file. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. Select Cisco CallManager from the Configured Services list. Select the appropriate IP address or name of the Cisco CallManager server from the list on the left side of the page. ForwardMaximumHopCount—Specifies the maximum number of attempts to extend a forwarded call. Note For more information about Cisco uOne . Refer to the installation and configuration documentation shipped with Cisco uOne for more information. enter the device number from the CMMWIOffNumber value as shown in the Cisco uOne SSMWI. • • Use the following procedure to configure the MWI On/Off directory numbers.ini files. Setting this parameter enables you to configure a single button on users’ phones for automatically dialing the voice mail pilot number.

The recommended value is 24. The ForwardNoAnswerTimeout parameter specifies the number of seconds to wait before forwarding on a No Answer condition.ini file. Enter a numeric value in the Value field.ini file. This value is the number to be dialed to turn on the message waiting indicator device as configured in Cisco CallManager. In the Value field. page 43-11 Cisco CallManager Administration Guide 43-10 OL-1047-01 . Step 10 Step 11 Step 12 Step 13 Click Update. Click Update. Select ForwardNoAnswerTimeout from the Configured Service Parameters list box. In the Value field. This is the directory number that users call to access voice mail. Click Update. This number must be the same as the Cisco uOne voice mail pilot directory number configured in the Cisco uOne DialMap. Setting this parameter enables you to configure a single button (for example. The ForwardMaximumHopCount parameter specifies the number of attempts to extended a forwarded call. Repeat this procedure for each Cisco CallManager server in the cluster. Click Update. Enter a numeric value.Chapter 43 Configuring Cisco CallManager Service Parameters for Cisco uOne Configuring Cisco uOne Voice Messaging Step 8 Step 9 Select MessageWaitingOnDN from the Configured Service Parameters list. The recommended value is 15. enter the device number from the CMMWIOnNumber value as shown in the Cisco uOne SSMWI. Select VoiceMail from the Configured Service Parameters list. enter the Cisco uOne Voice Mail pilot number. the messages button on a Cisco IP Phone 79xx) on users’ phones for automatically dialing the voice mail pilot number. Select ForwardMaximumHopCount from the Configured Service Parameters list. Step 14 Step 15 Step 16 Step 17 Step 18 Step 19 Related Topics: • Setting up the MWI Device.

they must be defined here also. refer to the Installation and Configuration documentation supplied with Cisco uOne. Select the default value of None. If partitions are being used. enter the name of the Cisco MWI uOne port device. Note For more information about Cisco uOne .ini file (for example. Step 4 Enter the device configuration settings as follows: Field Name Description Device Pool Location Partition Calling Search Space Value Optional descriptive text about the device. If partitions and calling search spaces are used. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 43-11 .ini files. This name must match the CMDeviceName value in the SSMWI.Chapter 43 Configuring Cisco uOne Voice Messaging Setting up the MWI Device Setting up the MWI Device Use the following procedure to create and configure the MWI device for use with Cisco uOne. Select Device > Cisco uOne Port. CiscoMWI-VI1). Select the default value of Default Pool. the calling search space specified here must include the partitions of the DNs on all phones whose lamps you wish to light (the partition defined for a phone's DN must be in a calling search space that the MWI device uses). In the Cisco uOne Port Name field.

Step 5 Click Insert to add this device to the system. the Forward Busy and Forward No Answer fields are not used. Cisco CallManager Administration Guide 43-12 OL-1047-01 . Forward All Forward Busy Forward No Answer Note The directory number for the MWI device is used for turning on the message indicator only. Leave blank.Chapter 43 Adding Cisco uOne Ports Configuring Cisco uOne Voice Messaging Field Name Directory Number Value Enter the Cisco MWI device directory number. Since it is not used by the uOne Messaging System or Cisco CallManager for receiving calls. Related Topics: • Configuring Cisco CallManager Service Parameters for Cisco uOne. Leave blank. This should be a number that is not used within the Cisco uOne messaging system or within the Cisco CallManager auto-registration range. All users and their directory numbers must be entered in Cisco CallManager Administration to retrieve messages from a Cisco uOne voice mail device. you must add Cisco uOne ports to Cisco CallManager. page 43-8 Adding Cisco uOne Ports To connect Cisco uOne to Cisco CallManager. Leave blank.

The Cisco uOne Port Configuration page displays. you must define 24 devices. Must add a device for each port on Cisco uOne. Step 3 Enter the appropriate settings as described in Table 43-3.Chapter 43 Configuring Cisco uOne Voice Messaging Adding Cisco uOne Ports Tips You can also use the Cisco uOne wizard to add a new Cisco uOne server and ports or to add multiple ports to an existing server rather than the procedure described here. Note If you are adding multiple ports. Use this procedure add individual Cisco uOne ports (for example. An Operator Number can be specified for the Forward Busy and Forward No Answer values for the last uOne port. to update the Operator Number). Procedure Step 1 Step 2 Open Cisco CallManager Administration. Table 43-3 uOne Configuration Settings Field Device Information Description Identifies the Cisco uOne port. Select Device > Cisco uOne Port. The naming convention for the ports should be CiscoUM-VI<consecutive number for each port>. • Cisco CallManager Administration Guide OL-1047-01 43-13 . If there are 24 ports. Follow these instructions to add individual Cisco uOne ports to the Cisco CallManager database. Refer to the “Cisco uOne Port Wizard” section on page 43-3 for more information. such as CiscoUM-VI1 or CiscoUM-VI2. Usage Notes • Cisco uOne Port Name Must match the information in the uOne . use the Cisco uOne wizard.ini files.

Usage Notes Location Directory Number Information Directory Number • • • Indicates the number associated with this uOne port Values can include a maximum of 50 numeric characters Unique in combination with the Partition field.Chapter 43 Adding Cisco uOne Ports Configuring Cisco uOne Voice Messaging Table 43-3 uOne Configuration Settings (continued) Field Description Device Pool Calling Search Space Description Clarifies the purpose of the device. you must select a Calling Search Space that includes the selected Route Partition. Select None if partitions are not used. Cisco CallManager Administration Guide 43-14 OL-1047-01 . Collection of partitions that are searched for numbers called from this device. Select a partition from the drop-down list. If a Route Partition is selected. Indicates a phone number that can be dialed. If a Route Partition is selected. Select the default value of Default Pool from the list. Partition Indicates the route partition to which the directory number belongs. Select the default value of None from the list. Calling Search Space Collection of partitions that are searched for numbers called from this directory number. you must select a Calling Search Space that includes the selected Route Partition. Call Forwarding Information Forward All This field should be left blank.

if it is the last calls are forwarded if this port is port. page 43-17 Updating a Cisco uOne Port. page 43-18 Copying an Existing Cisco uOne Port. page 43-3 Deleting a Cisco uOne Port. if it is the last not answer the call (for example. the next sequential uOne port number). Forward No Answer Voice mail directory number where This should be the next sequential calls are forwarded if this port does Cisco uOne port or. The Forward Busy and Forward No Answer fields should have the same value. busy (for example. an operator number. The Forward Busy and Forward No Answer fields should have the same value. page 43-16 Resetting a Cisco uOne Port. Related Topics • • • • • Cisco uOne Port Wizard. page 43-19 Cisco CallManager Administration Guide OL-1047-01 43-15 . next sequential port).Chapter 43 Configuring Cisco uOne Voice Messaging Adding Cisco uOne Ports Table 43-3 uOne Configuration Settings (continued) Field Forward Busy Description Usage Notes Voice mail directory number where This should be the next sequential Cisco uOne port or. an operator number. the port. Step 4 Click Insert to add the new Cisco uOne port device.

Select Devices > Cisco uOne Port. page 43-18 Copying an Existing Cisco uOne Port. page 43-12 Resetting a Cisco uOne Port. page 43-17 Updating a Cisco uOne Port.Chapter 43 Deleting a Cisco uOne Port Configuring Cisco uOne Voice Messaging Deleting a Cisco uOne Port Follow these procedures to delete a single Cisco uOne port from Cisco CallManager. page 43-19 Cisco CallManager Administration Guide 43-16 OL-1047-01 . Related Topics • • • • • Cisco uOne Port Wizard. Refer to the “Cisco uOne Port Wizard” section on page 43-3 for more information. Step 3 Select the Cisco uOne port you want to delete. page 43-3 Adding Cisco uOne Ports. Tips You can also use the Cisco uOne wizard to delete ports from an existing server instead of using the procedure described here. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Step 4 Click Delete. and the Cisco uOne Ports page updates to display the changes. The Cisco uOne port configuration page displays with a list of the defined Cisco uOne ports. The Cisco uOne port is deleted. you must make sure that no Cisco uOne ports refer to the deleted directory number in their Forward Busy and Forward No Answer fields. Note When you delete a uOne port (and its associated directory number).

page 43-12 Deleting a Cisco uOne Port. page 43-16 Updating a Cisco uOne Port. Close—Close the Reset Device dialog without making any changes. Select Devices > Cisco uOne Port. The Cisco uOne port configuration page displays with a list of the defined Cisco uOne ports. page 43-19 Cisco CallManager Administration Guide OL-1047-01 43-17 . The Reset Device dialog box displays. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Step 3 Step 4 Step 5 Select the Cisco uOne port you want to reset. page 43-3 Adding Cisco uOne Ports. Click Reset. page 43-18 Copying an Existing Cisco uOne Port. Related Topics • • • • • Cisco uOne Port Wizard. Step 6 Select one of the following: • • • Restart Device—Restart a device without shutting it down Reset Device—Shut down a device and bring it back up.Chapter 43 Configuring Cisco uOne Voice Messaging Resetting a Cisco uOne Port Resetting a Cisco uOne Port Follow these procedures to reset a Cisco uOne port from Cisco CallManager. Click OK.

to make minor changes such as updating the Operator Number). Refer to Table 43-3 on page 43-13 for a detailed description of the configuration settings for Cisco uOne ports. Step 3 Step 4 Step 5 Select the Cisco uOne port you want to update. Related Topics • • • • Cisco uOne Port Wizard.Chapter 43 Updating a Cisco uOne Port Configuring Cisco uOne Voice Messaging Updating a Cisco uOne Port Follow these procedures to update a Cisco uOne port (for example. Select Devices > Cisco uOne Port. page 43-3 Adding Cisco uOne Ports. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Enter the desired changes. page 43-12 Deleting a Cisco uOne Port. The Cisco uOne port configuration page displays with a list of the defined Cisco uOne ports. Click Update. page 43-16 Copying an Existing Cisco uOne Port. page 43-19 Cisco CallManager Administration Guide 43-18 OL-1047-01 .

Follow these steps to copy a Cisco uOne port’s settings. Related Topics • • • Cisco uOne Port Wizard. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Step 3 Step 4 Step 5 Select the Cisco uOne port you want to copy. Step 6 Click Insert. you can add one and then copy its basic settings to apply to another Cisco uOne port.Chapter 43 Configuring Cisco uOne Voice Messaging Copying an Existing Cisco uOne Port Copying an Existing Cisco uOne Port If you want to add several similar Cisco uOne ports to the Cisco CallManager database. page 43-3 Adding Cisco uOne Ports. page 43-16 Cisco CallManager Administration Guide OL-1047-01 43-19 . The Cisco uOne port configuration page displays with a list of the defined Cisco uOne ports. Tips It is much easier to use the Cisco uOne wizard to add a new Cisco uOne server and ports or to add multiple ports to an existing server instead of the procedure described here. Refer to the “Cisco uOne Port Wizard” section on page 43-3 for more information. You must change the Cisco uOne Port Name and Directory Number fields. You should also update the Forward Busy and Forward No Answer fields. page 43-12 Deleting a Cisco uOne Port. Make the required changes. Click Copy. Refer to Table 43-3 on page 43-13 for a detailed description of the configuration settings for Cisco uOne ports. Select Devices > Cisco uOne Port.

page 43-18 Cisco CallManager Administration Guide 43-20 OL-1047-01 .Chapter 43 Copying an Existing Cisco uOne Port Configuring Cisco uOne Voice Messaging • • Resetting a Cisco uOne Port. page 43-17 Updating a Cisco uOne Port.

page 5-3 Adding a Gatekeeper. page 44-6 Resetting or Restarting the Gatekeeper. Related Topics The following topics contain additional information related to gatekeepers: • • • • • • Understanding Call Admission Control.C H A P T E R 44 Configuring a Gatekeeper A gatekeeper (also known as a Cisco Multimedia Conference Manager. Cisco CallManager Administration Guide OL-1047-01 44-1 . Select Device > Gatekeeper. Only one gatekeeper device can be configured per Cisco CallManager cluster. page 5-1 Gatekeepers. page 44-7 Adding a Gatekeeper Perform the following procedure to add a gatekeeper device. or MCM) is a device that supports the H.225 RAS message set used for call admission control. page 44-6 Modifying the Gatekeeper. page 44-1 Deleting the Gatekeeper. Procedure Step 1 Step 2 Open Cisco CallManager Administration. bandwidth allocation. and dial pattern resolution.

Do not change this value unless instructed to by a Cisco TAC engineer. An RRQ is a request sent by a Cisco CallManager to the gatekeeper to register and then subsequently to maintain a connection with the gatekeeper. Descriptive name for the gatekeeper. Cisco CallManager Administration Guide 44-2 OL-1047-01 . The default value is 60 seconds. as defined in Table 44-1. registered per Cisco CallManager cluster. Enter a time in seconds. The request may be confirmed (RCF) or denied (RRJ). The default value is 300 seconds. A keepalive RRQ must be sent to the gatekeeper before the RRQ Time to Live expires. The amount of time that the gatekeeper will consider a registration request (RRQ) valid. Description Registration Request Time to Live Registration Retry Timer The amount of time Cisco CallManager waits before retrying gatekeeper registration after a failed registration attempt. Enter a time in seconds. Table 44-1 Gatekeeper Configuration Settings Field Gatekeeper Name Description Usage Notes The IP address or DNS name of the Only one gatekeeper can be gatekeeper.Chapter 44 Adding a Gatekeeper Configuring a Gatekeeper Step 3 Enter the appropriate settings. Do not change this value unless instructed to by a Cisco TAC engineer.

calling search space. Microsoft NetMeeting devices).Chapter 44 Configuring a Gatekeeper Adding a Gatekeeper Table 44-1 Gatekeeper Configuration Settings (continued) Field Terminal Type Description Determines the type for all of the devices controlled by this gatekeeper. and Calling Search Space. This device has all the characteristics of a normal device such as region. • Device Pool Specifies the collection of properties for this device including CallManager Group. in the configuration settings below. Date/Time Group. Allow Anonymous Calls By default. This eliminates the need for a Cisco CallManager to have an H. Select Gateway if all gatekeeper-controlled devices are gateways (including intercluster trunks). This field is normally set to Gateway for normal gatekeeper call admission control. This setting enables or disables the ability to send and receive intercluster calls to and from devices that are not explicitly configured in the database for each remote Cisco CallManager controlled by this gatekeeper.323 clients (for example. you must also fill location. Allow Anonymous Calls is disabled. Select Terminal if all gatekeeper-controlled devices are H. and so on. Cisco CallManager Administration Guide OL-1047-01 44-3 .225 device (intercluster trunk) explicitly configured for every remote CallManager that may be called over the IP WAN. When you enable Allow Anonymous Calls. • Usage Notes All gatekeeper-controlled devices must be of the same type. Region. This only applies to intercluster calls. you are essentially creating a device (similar to an intercluster trunk) that can send and receive calls to or from any remote Cisco CallManager controlled by this gatekeeper. Select either Terminal or Gateway from the drop-down list box. Select the name of a Device Pool from the drop-down list box. When you enable Allow Anonymous Calls and fill in the remainder of the fields below.

number of the calling device.Chapter 44 Adding a Gatekeeper Configuring a Gatekeeper Table 44-1 Gatekeeper Configuration Settings (continued) Field Calling Search Space Description Specifies the collection of Route Partitions searched to determine how a collected (originating) number should be routed. in North America: • 555XXXX = variable Caller ID. Usage Notes Allow Anonymous Calls Device Location Caller ID DN For example. where X is equal to an extension number. Use when you want the Corporate number to be sent instead of the exact extension from which the call is placed. Specifies the remote location accessed using restricted bandwidth connections. from 0 to 24 digits. The Central Office (CO) appends the number with the area code if you do not specify it. The CO appends the number with the area code if you do not specify it. • Calling Party Selection Any outbound call on a gateway can The following options specify send directory number information. 5555000 = Fixed Caller ID. Last Redirect Number—send the directory number of the last device to redirect the call. • First Redirect Number—send the directory number of the redirecting device. which directory number is sent: This field determines which • Originator—send the directory directory number is sent. • Cisco CallManager Administration Guide 44-4 OL-1047-01 . The pattern you want to use for Caller ID.

323 devices that do not support the H. Prefix DN Specifies the prefix digits that are The Cisco CallManager adds prefix appended to the called party number digits after first truncating the on incoming calls.323 clients only and those H. An MTP is also required if you need a transcoder.323 does not support (such as hold and transfer). Sig Digits Represents the number of final digits retained on inbound calls. Select Restricted if you do not want the CO to send caller ID. Media Termination Point Required Determines whether or not a Media Termination Point (MTP) is used to implement features that H.Chapter 44 Configuring a Gatekeeper Adding a Gatekeeper Table 44-1 Gatekeeper Configuration Settings (continued) Field Presentation Bit Description Determines whether the CO transmits or blocks caller ID.323 device. If enabled. Significant digits are counted from the right (last digit) of the number called. Used for H. from 0 to 32. number in accordance with the Num Digits setting. If disabled. Cisco CallManager Administration Guide OL-1047-01 44-5 . It is used for the processing of incoming calls and indicates the number of digits starting from the last digit of the called number used to route calls coming into the H. See Prefix DN and Sig Digits. A trunk with significant digits enabled truncates all but the final few digits of the address provided an inbound call. Enable or disable this box depending on whether you want to collect significant digits. Usage Notes Select Allowed if you want the CO to send caller ID. Num Digits This field is used if you enable Sig Digits. the Cisco CallManager does not truncate the inbound number. you also need to choose the number of significant digits to collect (see Num Digits). Specifies the number of significant digits to collect.245 empty capabilities set.

Related Topics • “Gatekeepers” section on page 5-3 Resetting or Restarting the Gatekeeper Perform the following procedure to reset or restart the gatekeeper. The page refreshes to show the configuration information for the gatekeeper. Procedure Step 1 Open Cisco CallManager Administration.Chapter 44 Deleting the Gatekeeper Configuring a Gatekeeper Step 4 Click Insert to add the new gatekeeper. Related Topics • “Gatekeepers” section on page 5-3 Deleting the Gatekeeper Perform the following steps to delete the gatekeeper. Click OK to permanently delete the gatekeeper. Step 4 Step 5 Click the Delete button. Click on the name of the gatekeeper from the list on the left side of the screen. Select Device > Gatekeeper. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. A confirmation dialog box displays. Cisco CallManager Administration Guide 44-6 OL-1047-01 . The page is updated and the name of the new gatekeeper is displayed in the list on the left.

The page refreshes to display the new settings. Click Update to apply the changes. • Related Topics • “Gatekeepers” section on page 5-3 Modifying the Gatekeeper Perform the following steps to modify gatekeeper settings: Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. The page refreshes to show the configuration settings for the gatekeeper. Step 4 Step 5 Click Reset Gatekeeper. Click on the name of the gatekeeper from the list on the left side of the screen. The Reset Device dialog displays. The page refreshes to show the configuration information for the gatekeeper. Click on the name of the gatekeeper in the list on the left side of the screen. The Cisco CallManager cluster will unregister (URQ) and then re-register (RRQ) with the gatekeeper. Step 4 Step 5 Make the desired changes to the configuration settings. then reset the internal gatekeeper device. Close—Close the Reset Device dialog without performing any action. Related Topics • “Gatekeepers” section on page 5-3 Cisco CallManager Administration Guide OL-1047-01 44-7 . Select Device > Gatekeeper.Chapter 44 Configuring a Gatekeeper Modifying the Gatekeeper Step 2 Step 3 Select Device > Gatekeeper. Click one of the following: • Restart or Reset —Shut down.

Chapter 44 Modifying the Gatekeeper Configuring a Gatekeeper Cisco CallManager Administration Guide 44-8 OL-1047-01 .

AS-8) Communication Protocol Skinny Gateway Protocol Device Protocol Analog Port Types Foreign Exchange Station (FXS) (loop start) Foreign Exchange Office (FXO) (loop start) PRI E1 PRI T1 Foreign Exchange Station (FXS) Cisco Access Analog Trunk Gateway (AT-2.C H A P T E R 45 Configuring Gateways Cisco IP telephony gateways enable Cisco CallManager to communicate with non-IP telecommunications devices. Cisco CallManager supports several types of gateways as described in Table 45-1. AT-4. AT-8) Skinny Gateway Protocol Analog Cisco Access Digital Trunk Gateway DE-30+ Cisco Access Digital Trunk Gateway DT-24+ Skinny Gateway Protocol Skinny Gateway Protocol Digital PRI E1 Digital PRI T1 Analog Cisco Catalyst 6000 24 Port FXS Skinny Gateway Protocol Analog Interface Module Cisco Catalyst 6000 8 Port E1/T1 and Services Module Skinny Gateway Protocol Digital E1/T1 PRI PRI E1/T1 Cisco CallManager Administration Guide OL-1047-01 45-1 . AS-4. Table 45-1 Gateway Model Overview Gateway Model Cisco Access Analog Station Gateway (AS-2.

page 45-44 Understanding Supported Gateways Cisco CallManager supports several types of Cisco and third-party IP telephony gateways.225.323 Gateways.323 Devices. page 45-7 Configuring Gateway Ports in Cisco CallManager. including Cisco VG200 and Cisco IOS-based gateways H. page 45-41 Finding Specific Gateways. page 45-3 Understanding Catalyst 6000 Gateways.323 gateway with T1-CAS ports All H. page 45-27 Modifying Gateways.Chapter 45 Understanding Supported Gateways Configuring Gateways Table 45-1 Gateway Model Overview (continued) Gateway Model Cisco Voice Gateway 200 (VG200) Communication Protocol Device Protocol Port Types Foreign Exchange Office (FXO) Foreign Exchange Station (FXS) Depends on model Analog Media Gateway Control Protocol (MGCP). Inter-cluster Trunk These sections provide information about working with and configuring Cisco gateways with Cisco CallManager • • • • • Understanding Supported Gateways.323 H. works as an H. These sections provide an overview of these supported gateways: • • • • Understanding Cisco Access Gateways. page 45-2 Adding Gateways to Cisco CallManager. page 45-4 Cisco VG200 Gateway. page 45-6 Cisco CallManager Administration Guide 45-2 OL-1047-01 . page 45-6 Understanding Other H.

and AT-8 models accommodate two. page 45-41 Finding Specific Gateways. page 45-7 Configuring Ports on Analog Gateways. four. Related Topics • • • • • Adding an Analog Gateway. The AS-2. four. AT-4. Station gateways provide Foreign Exchange Station (FXS) ports. and voice mail systems. Access Analog Trunk Gateways Analog trunk gateways let you connect the Cisco CallManager to standard public switched telephone network (PSTN) central office (CO) or PBX trunks. The signalling type is loop start. Trunk gateways provide Foreign Exchange Office (FXO) ports. The following Cisco Access gateways are available: • • Cisco Access Analog Gateways—Trunk and station analog gateways Cisco Access Digital Trunk Gateways—Digital trunk gateways Cisco Access Analog Gateways There are two categories of Cisco Access Analog gateways: trunk gateways and station gateways. Cisco Access Analog Station Gateways Station gateways let you connect the Cisco CallManager to Plain Old Telephone Service (POTS) analog telephones.Chapter 45 Configuring Gateways Understanding Supported Gateways Understanding Cisco Access Gateways Cisco Access gateways make it possible for the Cisco CallManager to communicate with non-IP telecommunications devices. page 45-44 Understanding Device Loads. fax machines. AS-4. and AS-8 models accommodate two. The AT-2. interactive voice response (IVR) systems. page 45-27 Modifying Gateways. respectively. and eight Voice over IP (VoIP) gateway channels. and eight VoIP gateway channels. page 7-6 Cisco CallManager Administration Guide OL-1047-01 45-3 .

page 7-6 Understanding Catalyst 6000 Gateways Several telephony modules are available for the Cisco Catalyst 6000 Family. page 45-41 Finding Specific Gateways. The DE-30+ supports ISDN PRI at an E1 rate. page 45-44 Understanding Device Loads. These modules act as telephony gateways enabling you to implement IP telephony in your network using existing Cisco Catalyst 6000 Family devices. The DT-24+ supports ISDN PRI at a T1 rate. Related Topics • • • • Adding Digital Gateways. page 45-9 Modifying Gateways. Catalyst 6000 Family Analog Line Card The Catalyst 6000 Family Analog Line Cards include the following: • Cisco Catalyst 6000 24 Port FXS Analog Interface Module Cisco CallManager Administration Guide 45-4 OL-1047-01 . Access Digital Trunk DE-30+ E1 Gateway The DE-30+ (E1) gateway connects VoIP networks to a PBX or the PSTN.Chapter 45 Understanding Supported Gateways Configuring Gateways Cisco Access Digital Trunk Gateways A Cisco Access Digital Trunk Gateway allows you to connect a Cisco CallManager system to the PSTN or to a PBX. These models of Cisco Access Digital Trunk gateways are available: Cisco Access Digital Trunk DT-24+ Gateway and Cisco Access Digital Trunk DE-30+ (E1) Gateway. The Catalyst 6000 gateways are line cards you can install in any Catalyst 6000 or 6500 series switch. Access Digital Trunk DT-24+ T1 Gateway The DT-24+ gateway connects VoIP networks to a PBX or the PSTN.

Related Topics • Understanding Device Loads. page 45-41 Finding Specific Gateways. page 7-6 Cisco CallManager Administration Guide OL-1047-01 45-5 .Chapter 45 Configuring Gateways Understanding Supported Gateways Related Topics • • • • • Adding an Analog Gateway. However. When used in these configurations. page 45-41 Finding Specific Gateways. the DSP Services Card is configured with a different firmware load. page 45-7 Configuring Ports on Analog Gateways. this card does not act as a gateway and is not described in detail in this chapter. page 45-44 Understanding Device Loads. page 45-27 Modifying Gateways. page 7-6 Catalyst 6000 Family T1/E1 Line Cards The Cisco Catalyst 6000 Family T1 Line Card provides eight ports allowing T1 PRI ISDN ports on connections to the PSTN or a PBX. page 7-6 Catalyst 6000 Family DSP Services Card The Catalyst 6000 Family DSP Services Card is the same hardware as the Catalyst 6000 Family T1/E1 Line Cards. page 45-7 Configuring Ports on Analog Gateways. page 45-44 Understanding Device Loads. The Cisco Catalyst 6000 Family E1 Line Card provides eight ports allowing E1 PRI ISDN ports on connections to the PSTN or a PBX. Related Topics • • • • • Adding an Analog Gateway. This special configuration enables the card to function as a conference bridge or transcoder. page 45-27 Modifying Gateways.

The Cisco VG200 gateway provides a 10/100BaseT Ethernet port for connection to the data network. You can add third-party H.323 (such as the Cisco 2600 series. page 45-44 Understanding Other H.323 gateways used to interlink Cisco CallManagers in different clusters are configured as inter-cluster trunks. H.323 communications standards and enable video conferencing over LANs and other packet-switched networks.323 Devices H. Related Topics • • • • Adding an MGCP Gateway. 3600 series. and it supports H.323 on digital (T1) ports.323 devices comply with the H. page 45-23 Finding Specific Gateways.Chapter 45 Understanding Supported Gateways Configuring Gateways Cisco VG200 Gateway The Cisco VG200 gateway allows you to connect standard POTS devices to the Cisco IP Telephony Solution.323 Gateway. page 45-41 Finding Specific Gateways. page 45-35 Modifying Gateways. page 45-21 Configuring Ports on a Cisco MGCP Gateway. Related Topics • • • Adding an H. page 45-44 “Configuring a Gatekeeper” section on page 44-1 Cisco CallManager Administration Guide 45-6 OL-1047-01 . or 5300 series gateways). The following telephony connections are available: • • • 1 to 4 Foreign Exchange Office (FXO) ports for connecting to a central office or PBX 1 to 4 Foreign Exchange Station (FXS) ports for connecting to POTS telephony devices 1 to 2 T1 digital ports for connecting to the PSTN The Cisco VG200 gateway supports MGCP on FXO and FXS analog ports.323 devices or other Cisco devices that support H.

page 45-9 Adding an MGCP Gateway. you must first add each gateway to the Cisco CallManager system. The Add a New Device screen appears.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Adding Gateways to Cisco CallManager To enable Cisco CallManager to manage IP telephony gateways in your network. Step 4 Select an analog gateway from the Gateway type drop-down list box. AS-4.323 Gateway. Select Device > Add a New Device. page 45-7 Adding Digital Gateways. and AS-8 Gateways Cisco AT-2. AS-4. AT-4. and AT-8 Gateways Cisco Catalyst 6000 24 Port FXS Gateway Procedure Step 1 Step 2 Open Cisco CallManager Administration. Supported analog gateways include the following: • • • Cisco AS-2. and AS-8 Gateways Cisco AT-2. and AT-8 Gateways Cisco Catalyst 6000 24 Port FXS Gateway Cisco CallManager Administration Guide OL-1047-01 45-7 . The Add a New Gateway screen appears. Refer to these sections for detailed procedures: • • • • Adding an Analog Gateway. AT-4. page 45-23 Adding an Analog Gateway Use the following procedure to add these Cisco analog gateways to Cisco CallManager: • • • Cisco AS-2. page 45-21 Adding an H. Step 3 Select Gateway from the Device type drop-down list box.

The country in which the gateway is Select the country in which the located. Load Information Country Code Values entered here override the default values for this gateway. Date/Time Group. Specifies the collection of properties for this device including CallManager Group. Clarifies the purpose of the device. Region.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways When you select a Gateway type. Usage Notes Value must be 12 hexadecimal characters. Step 5 Click Next. Click Insert. and Calling Search Space for auto-registration of devices. as described in Table 45-2. The Gateway Configuration screen appears. the appropriate Device Protocol for the selected gateway (in this case. Step 6 Step 7 Enter the appropriate settings. Specifies the collection of Route Partitions searched to determine how a collected (originating) number should be routed. Specifies the custom software for gateway. Specifies the remote location accessed using restricted bandwidth connections. gateway is located from the drop-down list box. Table 45-2 Access Analog Gateway Configuration Settings Field MAC Address Description Device Pool Description Identifies hardware-based devices. Location Calling Search Space Cisco CallManager Administration Guide 45-8 OL-1047-01 . Analog Access) is automatically selected.

The Add a New Device screen appears. page 45-3 Catalyst 6000 Family Analog Line Card. Select a digital gateway from the Gateway Type drop-down list box. • BOTTOM_UP selects ports in ascending order. page 7-7 Adding Digital Gateways You can add a Cisco digital gateway to Cisco CallManager. Cisco CallManager Administration Guide OL-1047-01 45-9 . page 45-27 Updating Device Loads. choose • TOP_DOWN selects ports in descending order. Step 3 Step 4 Select Gateway from the Device type drop-down list box. page 45-4 Configuring Ports on Analog Gateways. Select Device > Add a New Device. Usage Notes Valid entries are TOP_DOWN or BOTTOM_UP. port 8.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-2 Access Analog Gateway Configuration Settings (continued) Field Port Selection Order Description Specifies the order in which ports are selected. If you're not sure which port order to use. Follow these steps to add a digital PRI gateway. Procedure Step 1 Step 2 Open Cisco CallManager Administration. from port 8 to port 1. from port 1 to TOP_DOWN. Related Topics • • • • Cisco Access Analog Gateways.

Table 45-3 Access Digital PRI Gateway Configuration Settings Field MAC Address Description Device Pool Description Identifies hardware-based telephones and device name. Click Insert. the appropriate Device Protocol for the selected Gateway type (in this case. Digital Access PRI) is automatically selected. Specifies the collection of properties for this device including CallManager Group. Step 6 Step 7 Enter the appropriate settings as described in Table 45-3. and Calling Search Space for auto registration of devices. Date/Time Group. Clarifies the purpose of the device. Step 5 Click Next. The Gateway Configuration screen appears. Region. Usage Notes Value must be 12 hexadecimal characters. Remote location accessed using restricted bandwidth connections. Calling Search Space Location Load Information Values entered here override the default values for this gateway. Cisco CallManager Administration Guide 45-10 OL-1047-01 . Specifies the custom software for gateway.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Digital Access PRI gateways include: • • • • Cisco DT-24+ Gateway Cisco DE-30+ Gateway Cisco Catalyst 6000 E1 VoIP Gateway Cisco Catalyst 6000 T1 VoIP Gateway When you select a Gateway type. Specifies the collection of Route Partitions searched to determine how a collected (originating) number should be routed.

each of which can be used as a clock reference by other ports on the same blade. • • • Cisco CallManager Administration Guide OL-1047-01 45-11 . • -15dB • -22. Select Internal or Network. If you're not sure which port order to use. Choose from the following: • • PCM Type A-law: Use for Europe and the rest of the world µ-law: Use for North America and Japan Internal—When clocking is derived from the card and is then distributed at the span Network—When the Cisco Access Digital Trunk Gateway receives its clocking from the network Span 1 to Span 8—When the Cisco Access Digital Trunk Gateway receives clocking from another port on the same Cisco Catalyst 6000 blade. Valid entries are TOP_DOWN (last to first) or BOTTOM_UP (first to last).Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field TX-Level CSU Description Usage Notes Specifies the transmit level based on Select one of the alternative settings to attenuate the line. or from last to first. the distance between the gateway and the nearest repeater. The default • -7. choose TOP_DOWN.5dB is full power (0dB).5dB Channel Selection Order Specifies the order in which ports are enabled from first (lowest number port) to last (highest number port). Specifies the digital encoding format. Clock Reference Specifies from where the master clock is derived. Cisco Catalyst 6000 blades have eight ports on the same hardware card.

5555000 = Fixed Caller ID. this option is User for Central Office connections. For example. For example. from 0 to 24 digits. The CO appends the number with the area code if you do not specify it. Network should be chosen for this device. The two ends of the PRI connection should use opposite settings. Usage Notes Caller ID DN The pattern you want to use for Caller ID. Typically. The CO appends the number with the area code if you do not specify it. • Cisco CallManager Administration Guide 45-12 OL-1047-01 . Use when you want the Corporate number to be sent instead of the exact extension from which the call is placed. in North America: • 555XXXX = variable Caller ID. if you are connected to a PBX and the PBX uses User as its protocol side.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Protocol Side Description Setting used for Cisco Access Digital gateways depending on whether gateway is connected to a Central Office/Network device or to a User device. where X is equal to an extension number.

This setting only applies to the DMS100 protocol for digital access gateways in the Channel Identification information element (IE) of the SETUP. Any outbound call on a gateway can send directory number • Originator—Send the directory information. • First Redirect Number—Send the directory number of the redirecting device. CALL PROCEEDING. • • Slotmap—B-channel usage is always a slotmap format Use Number When 1B—Channel usage is a channel map for one B-channel but is a slotmap if more than one B-channel Interface Identifier Present The purpose of this parameter is to interoperate with a Nortel PBX when the PBX is configured to use the DMS100 protocol. and CONNECT messages. number of the calling device.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Calling Party Selection Description Usage Notes Determines which directory number The following options specify which directory number is sent: is sent. Valid the PBX provider. is present. When this box is checked. values range from 0 to 255. This value should be obtained from Applies to DMS100 protocol only. • Channel IE Type Indicates whether channel selection Select one of the following from the is presented as a channel map or a drop-down list box: slot map. it indicates that an Interface Identifier ALERTING. • Number—B-channel usage is always a channel map format. Interface Identifier Value Cisco CallManager Administration Guide OL-1047-01 45-13 . Last Redirect Number—Send the directory number of the last device to redirect the call. The default for this setting is disabled.

Controls the rate at which the spans are brought in service when Inhibit Restarts at PRI Initialization is disabled. set the first five cards to 0. Redirecting Number IE Delivery When this box is checked (enabled). This setting applies to the SETUP message only on all protocols for digital access gateways. This field is used if you enable Sig Digits. By default. See Prefix DN and Sig Digits. Significant digits are counted from the right (last digit) of the number called.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Description Usage Notes Display IE Delivery When this box is checked. It is used for the processing of incoming calls and indicates the number of digits starting from the last digit of the called number used to route calls coming into the PRI span. For example. this setting is disabled. Delay for first restart (1/8 sec ticks) Use this option when many PRI spans are enabled on a system and Inhibit Restarts at PRI Initialization is disabled. Cisco CallManager Administration Guide 45-14 OL-1047-01 . Specifies the number of significant digits to collect. from 0 to 32. (Wait two seconds before bringing them in service. it enables By default. when a PRI RESTART is sent. delivery of the display information element (IE) in SETUP and CONNECT messages for the calling and called party name delivery service.) Delay between restarts (1/8 sec ticks) Num Digits Determines the length of time between restarts if Inhibit Restarts is disabled. the Redirecting Number IE is included in the SETUP message to indicate the first redirecting number and the redirecting reason of the call when Call Forward happens. and set the next five cards to 16. Display IE Delivery is disabled.

You can also change this setting when connecting • Unknown—The dialing plan is unknown. Usage Notes Enable or disable this box depending on whether you want to collect significant digits. The Cisco CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting. dialing patterns. Presentation Bit Determines whether the central Select Allowed if you want the Central office transmits or blocks caller ID. We Cisco CallManager sets the directory recommend that you do not change number type. Office to send caller ID. If disabled. Cisco CallManager Administration Guide OL-1047-01 45-15 . Cisco CallManager sets the called • CallManager—The directory number (DN) type. the default value unless you have • International—Use when you are advanced experience with dialing dialing outside the dialing plan for plans.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Sig Digits Description Represents the number of final digits a PRI span should retain on inbound calls. Prefix DN Specifies the prefix digits that are appended to the digits this trunk receives on incoming calls. If enabled. such as NANP or the your country. European dialing plan. to PBXs using routing as a non-national type number. you also need to choose the number of significant digits to collect. A trunk with significant digits enabled truncates all but the final few digits of the address provided an inbound call. the Cisco CallManager does not truncate the inbound number. Called party IE number type unknown The format for the type of number in Use the following definition for each of the variables: called party directory numbers. Select Restricted if you do not want the Central Office to send caller ID. You may need to change the default in Europe • National—Use when you are dialing because Cisco CallManager does within the dialing plan for your not recognize European national country.

Private—Use when you are dialing within a 'private' network. International—Use when you are dialing outside the dialing plan for your country. Cisco CallManager Administration Guide 45-16 OL-1047-01 . such as NANP or the European dialing plan. ISDN—Use when you are dialing outside the dialing plan for your country. National Standard—Use when you are dialing within the dialing plan for your country. such as NANP or the European dialing plan. You can also change this setting when connecting to PBXs using routing as a non-national type number. You can also change this setting when connecting to PBXs using routing as a non-national type number. Unknown—The dialing plan is unknown. The format for the numbering plan in called party directory numbers. National—Use when you are dialing within the dialing plan for your country. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. • • • Called Numbering Plan Use the following definition for each of the variables: CallManager—The Cisco CallManager sets the Numbering Plan in the directory number. We recommend that you do not change the default value unless you have advanced experience with dialing plans. • CallManager—The Cisco CallManager sets the directory number type. Cisco CallManager sets the called DN numbering plan.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Calling party IE number type unknown Description Usage Notes The format for the type of number in Use the following definition for each of the variables: calling party directory numbers. Cisco CallManager sets the calling directory number (DN) type. We recommend you do not change the default value unless you have advanced experience with dialing plans. Unknown—The dialing plan is unknown.

Private—Use when you are dialing within a 'private' network. Determine the switch to which you are connecting and the preferred protocol. also Japanese local exchange. as follows: • • • • Calling Numbering The format for the numbering plan Plan in calling party directory numbers. National Standard—Use when you are dialing within the dialing plan for your country. PRI Protocol Type The communications protocol for the span: • • • • • • 4E —AT&T InterExchange carrier 5E8 Custom—Cisco IP Phone 5E9 and NI2—AT&T family local exchange switch or carrier Australian —European ISDN DMS—MCI family local exchange switch or carrier ETSI SC—European local exchange carrier on T1. Euro—European ISDN Nortel Meridian—5E8 Custom Lucent Definity—4ESS or 5E8 Madge (Teleos) box—5E8 Teleos Intecom PBX—5E8 Intecom Alternatively. ISDN—Use when you are dialing outside the dialing plan for your country. You can also change this setting when connecting to PBXs using routing as a non-national type number. such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. We recommend that you do not change the default value unless you have advanced experience with dialing plans. Unknown—The dialing plan is unknown. Cisco CallManager sets the calling DN numbering plan. select the protocol based on the carrier: • • • MCI—DMS-250 Sprint—DMS-250 or DMS-100 AT&T—4ESS • Cisco CallManager Administration Guide OL-1047-01 45-17 .Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Description Usage Notes Use the following definition for each of the variables: CallManager—The Cisco CallManager sets the Numbering Plan in the directory number.

The choices are (for T1) • • Framing SF—superframe consisting of 12 frames ESF—extended superframe consisting of 24 frames. The FDL is a maintenance • AT&T PUB 54016 channel that allows remote troubleshooting of link-layer • none problems. consisting of 16 frames) FDL Channel Only relevant on T1 spans. Substitution). Usage Notes Enable or disable. E1 is always ESF (Extended Superframe. they are assumed to be in service. Choices are: Determines what kind. Enable to view the B-channel status in the debug window. When the D-Channel successfully connects with another PRI's D-Channel it sends restarts when this option is disabled. from 0 to 32. Cisco CallManager Administration Guide 45-18 OL-1047-01 . In this example.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Inhibit restarts at PRI initialization Description A RESTART is a message that confirms the status of the ports on a PRI span. and remote monitoring of performance statistics of the link.401 span. 8889725551234 is dialed. this could be AMI (Alternate electrically codes binary 1's and 0's Mark Inversion) or B8ZS (Bipolar 8-Zeros on the wire (line coding selection). Enable status poll Number of digits to The number of digits to strip on strip outbound calls. and the number of digits to strip is 3. For example. Zero Suppression Determines how the T1 or E1 span For a T1. facility data link is supported by the • ANSI T. 888 is stripped from the outbound number. For an E1. this could be AMI or HDB3 Determines the multiframe format of the span. If RESTARTs are not sent. if any.

Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Yellow Alarm Description Determines how a remote alarm indication is coded on a T1 span. Adjusts the gain of audio entering or leaving the span. A yellow alarm indicates that the other end of the link has lost frame synchronization on the signal being transmitted by this end. allows 64kbps clear channel bearer capability per B-channel). Usage Notes Choices include F-bit (out of band signaling. following port application types: AnalogCOTrunk—Minus3db DigitalToAnalogCO—NoDbPadding AnalogTieTrunk—NoDbPadding DigitalToDigitalCO—NoDbPadding ISDNStation—NoDbPadding ISDN_DigitalTieTrunk—NoDbPadding ISDNTrunk—NoDbPadding OnPremisePOTSLine—Plus3db OffPremisePOTSLine—NoDbPadding SatelliteAnalogTieTrunk—NoDbPadding SatelliteDigitalTieTrunk—NoDbPadding AnalogTollTrunk—Plus3db Cisco CallManager Administration Guide OL-1047-01 45-19 . Trunk Level Audio Signal Adjustment into IP Network Specifies the gain or loss applied to Select the gain or loss you want applied to the received audio signal relative to the received audio signal relative to the the port application type. or bit-2 (in band signaling. robs bit 2 of every channel).

and each subsequent card should be installed in the next available slot position. Only appears on a DT-24 Gateway. move the original cards to the right-most slots before adding the new card. always add cards from right to left when viewing the gateway from the back. A slot position refers to the peripheral component interconnect (PCI) card slot into which the digital signal processor (DSP) card is plugged.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-3 Access Digital PRI Gateway Configuration Settings (continued) Field Description Usage Notes Audio Signal Specifies the gain or loss applied to Select the gain or loss you want applied to Adjustment from IP the transmitted audio signal relative the transmitted audio signal relative to the Network to the port application type. following port application types: • • • • • • • • • • • • AnalogCOTrunk—Minus6db DigitalToAnalogCO—Minus3db AnalogTieTrunk—NoDbPadding DigitalToDigitalCO—NoDbPadding ISDNStation—NoDbPadding ISDN_DigitalTieTrunk—NoDbPadding ISDNTrunk—NoDbPadding OnPremisePOTSLine—Plus3db OffPremisePOTSLine—Minus3db SatelliteAnalogTieTrunk—Minus3db SatelliteDigitalTieTrunk—Minus3db AnalogTollTrunk—NoDbPadding Card Location Select the slot position from the drop-down list box. moving from right to left. The first (oldest) card should be in the right-most slot. Cisco CallManager Administration Guide 45-20 OL-1047-01 . When adding a new card to the digital access. If you have existing cards that were not installed in the right-most positions.

page 7-7 Adding an MGCP Gateway To use an MGCP gateway. page 45-5 Updating Device Loads. The Add a New Gateway screen appears. For procedures and commands required to perform this configuration. from the Gateway Type drop-down list box. such as the Cisco VG200. as described in Table 45-4. Procedure Step 1 Step 2 Open Cisco CallManager Administration.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Related Topics • • • Cisco Access Digital Trunk Gateways. refer to the configuration documentation supplied with the gateway. you must use the FXO or FXS analog ports. “Not Required for MGCP” is selected. the appropriate Device Protocol for the selected Gateway type. you must configure the gateway using the Cisco IOS command line interface (CLI). Step 4 Select an MGCP gateway. In this case. Before You Begin Before using adding an MGCP gateway to Cisco CallManager. The Add Device screen appears. Step 3 Select Gateway from the Device type drop-down list box. Cisco CallManager Administration Guide OL-1047-01 45-21 . Step 5 Step 6 Click Next. page 45-4 Catalyst 6000 Family T1/E1 Line Cards. Enter the appropriate settings. Slot 0 is not used on the Cisco VG200 gateway. Select Device > Add a New Device. When you select a Gateway type.

Otherwise use this field (in this case. The screen automatically updates to add options for configuring the type of installed Voice Interface Cards (VIC) in Sub-Unit. NM-1V — Has one Voice Interface Card (VIC) in SubUnit 0. • • Step 7 Click Insert. . Cisco CallManager Administration Guide 45-22 OL-1047-01 . the host name as defined on the If the hostname is configured on the Cisco MGCP gateway. if the hostname is configured on the gateway to resolve to vg200-1 (the IP domain Use the Domain Name Service name is not configured) you would (DNS) host name if it is configured only need to enter the hostname in to resolve correctly. which can be VIC-2FXO (two FXO ports). VIC-2FXS (two FXS ports).com. NM-2V — Can have two VICs. . Description Module in Slot 0 Module in Slot 1 Module in Slot 2 Module in Slot 3 . Step 8 Click Update. one in SubUnit 0 and one in SubUnit 1. Clarifies the purpose of the device. gateway as vg200-1 and the IP You must use the same value here domain name is configured on the that is used to configure the gateway as cisco.com in this command line.cisco. Usage Notes For example. None — No network modules installed. you would Cisco MGCP gateway at the IOS enter vg200-1. vg200-1). field. or None. (and so on) Installed Voice Interface Cards For each available slot on the selected MGCP gateway.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-4 MGCP Configuration Settings Field MGCP Domain Name Description Uniquely identifies the Cisco MGCP gateway. select the type of network module installed: • The correct number of slots are displayed for each model of MGCP gateway.

The Add Device screen appears.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager The screen automatically updates to add options for configuring endpoint information for the type of VICs configured in the previous screen.225 (default) Inter-cluster Trunk — An inter-cluster trunk is a virtual H. The Add a New Gateway screen appears.323 Gateway from the Gateway Type drop-down list box. Step 4 Step 5 Select H. Cisco CallManager Administration Guide OL-1047-01 45-23 . Step 3 Select Gateway from the Device type drop-down list box. Two device protocols are available: • • H.323 Gateway Follow these instructions to add an H. page 45-6 Configuring Ports on a Cisco MGCP Gateway. see the “Configuring Ports on a Cisco MGCP Gateway” section on page 45-35. Click Insert. Select Device > Add a New Device.323 gateway to Cisco CallManager. Step 9 To configure ports on an MGCP gateway. Enter the appropriate settings as described in Table 45-5. page 45-35 Adding an H. Select a device protocol from the Device Protocol drop-down list box. Step 6 Step 7 Step 8 Click Next.323 gateway that is used to interlink Cisco CallManagers in different clusters. Related Topics • • Cisco VG200 Gateway. Procedure Step 1 Step 2 Open Cisco CallManager Administration.

and Calling Search Space for auto-registration of devices. Date/Time Group. where X is equal to an extension number. Region. from 0 to 24 digits. • Cisco CallManager Administration Guide 45-24 OL-1047-01 . The CO appends the number with the area code if you do not specify it. Use when you want the Corporate number to be sent instead of the exact extension from which the call is placed. Specifies the remote location accessed using restricted bandwidth connections. Specifies the collection of properties for this device including CallManager Group.323 Gateway Configuration Settings Field Device Name Description Specifies unique name used by Cisco CallManager to identify the device. Specifies the collection of Route Partitions searched to determine how a collected (originating) number should be routed. Clarifies the purpose of the device. 5555000 = Fixed Caller ID. in North America: • 555XXXX = variable Caller ID. The CO appends the number with the area code if you do not specify it. The pattern you want to use for Caller ID.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-5 H. Usage Notes Description Device Pool Calling Search Space Location Caller ID DN For example.

If the H. It controls access to the LAN for connections between H. Central Office to send caller ID. select None. Select Restricted if you do not want the Central Office to send caller ID. • Presentation Bit Determines whether the central Select Allowed if you want the office transmits or blocks caller ID. • • Gatekeeper Name If your device is not gatekeeper controlled.323 gatekeeper. A gatekeeper is an H. Last Redirect Number—send the directory number of the last device to redirect the call.323 entity on the LAN that supports the H. The Domain Name Service (DNS) name or IP address of the H. select the name of the Gatekeeper from the drop-down list. bandwidth allocation. Display IE Delivery is delivery of the display IE in SETUP disabled.225 RAS message set used for admission control. and CONNECT messages for the calling and called party name delivery service.323 Gateway Configuration Settings (continued) Field Calling Party Selection Description Usage Notes Any outbound call on a gateway can The following options specify send directory number information. which directory number is sent: This field determines which • Originator—send the directory directory number is sent. number of the calling device. Use only for H.Chapter 45 Configuring Gateways Adding Gateways to Cisco CallManager Table 45-5 H. Cisco CallManager Administration Guide OL-1047-01 45-25 . • First Redirect Number—send the directory number of the redirecting device.323-compliant devices such as terminals and gateways. and dial pattern resolution. Display IE Delivery When this box is checked.323-compliant gateways. it enables By default.225 device will be controlled by a remote Gatekeeper. All other devices do not use this box.

Num Digits Sig Digits Represents the number of final digits retained on inbound calls.323 clients only and those H. Usage Notes Used for H. you also need to choose the number of significant digits to collect (see Num Digits). Enable or disable this box depending on whether you want to collect significant digits.245 Empty Capabilities Set message.Chapter 45 Adding Gateways to Cisco CallManager Configuring Gateways Table 45-5 H. This field is used if you enable Sig Digits.323 devices that do not support the H.323 Devices. the Cisco CallManager does not truncate the inbound number.323 device. page 45-6 Cisco CallManager Administration Guide 45-26 OL-1047-01 . If enabled. If disabled. number in accordance with the Num Digits setting.323 does not support (such as hold and transfer). See Prefix DN and Sig Digits. A trunk with significant digits enabled truncates all but the final few digits of the address provided an inbound call. Significant digits are counted from the right (last digit) of the number called. Specifies the number of significant digits to collect. It is used for the processing of incoming calls and indicates the number of digits starting from the last digit of the called number used to route calls coming into the H. Prefix DN Specifies the prefix digits that are The Cisco CallManager adds prefix appended to the called party number digits after first truncating the on incoming calls.323 Gateway Configuration Settings (continued) Field Media Termination Point Required Description Determines whether or not a Media Termination Point is used to implement features that H. from 0 to 32. Related Topics • Understanding Other H.

The Find and List Gateways screen appears. Select Device > Gateway. Follow these procedures to configure ports on these analog gateways: • • • Cisco AS-2. See “Adding an Analog Gateway” section on page 45-7 for instructions. page 45-35 Configuring Ports on Analog Gateways You can configure ports on the analog devices added to Cisco CallManager. and AS-8 Gateways Cisco AT-2. Cisco CallManager Administration Guide OL-1047-01 45-27 . Step 3 Enter the appropriate search criteria to locate the analog gateway to which you want to add ports and click Find. AS-4. AS-4. Procedure Step 1 Step 2 Open Cisco CallManager Administration. page 45-27 Configuring Ports on a Cisco MGCP Gateway. AT-4. and AS-8 Gateways Cisco Catalyst 6000 24 Port FXS Gateway Before You Begin You must add a Cisco analog gateway before configuring ports.Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Configuring Gateway Ports in Cisco CallManager After adding gateways to Cisco CallManager refer to these sections to configure the ports on the analog gateways in your network: • • Configuring Ports on Analog Gateways. and AT-8 Gateways Cisco Catalyst 6000 24 Port FXS Gateway Configuring POTS Ports Use this procedure to configure POTS ports on these devices: • • Cisco Access Analog AS-2.

To add all available ports. Step 11 Add directory numbers to the new ports. The screen updates to display the Gateway Configuration screen with information for the selected analog access gateway. click Advanced. Step 5 Step 6 Click Add a New Port at the top of the list of ports on the left side of the page to display a dialog for adding ports. or a range of ports by setting values for the Port Number and End Port Number fields. Step 7 Select whether you want to add and configure all available ports. Cisco CallManager Administration Guide 45-28 OL-1047-01 . For each new POTS port. click the Add DN link to open the Configure a Directory Number page. specify the same number in the Port Number and End Port Number fields. the screen refreshes and displays the POTS ports in the list on the left-hand side of the screen. To the right of each new port is link (Add DN) to the Configure a Directory Number page in Cisco CallManager Administration. Step 8 Step 9 Step 10 To modify additional settings. Enter the appropriate settings. The screen updates to add configuration options for Port Number and End Port Number. Refer to the section “Adding a Directory Number” section on page 46-19 and Table 46-2 on page 46-20 for information about directory number configuration settings. a single port. as described in Table 45-6. Click Insert and Close to apply the changes and close the window. Select POTS as the port type. you must select All Ports for both the Port Number and End Port number fields. Once you have inserted and configured the POTS ports. • • To create a single port.Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Step 4 Select the name of the analog access gateway from the list of gateways that matched the search criteria.

AnalogCOTrunk—Minus3db DigitalToAnalogCO—NoDbPadding AnalogTieTrunk—NoDbPadding DigitalToDigitalCO—NoDbPadding ISDNStation—NoDbPadding ISDN_DigitalTieTrunk—NoDbPadding ISDNTrunk—NoDbPadding OnPremisePOTSLine—Plus3db OffPremisePOTSLine—NoDbPadding SatelliteAnalogTieTrunk—NoDbPadding SatelliteDigitalTieTrunk—NoDbPadding AnalogTollTrunk—Plus3db Cisco CallManager Administration Guide OL-1047-01 45-29 . Specifies the gain or loss applied Select the gain or loss you want applied to the received audio signal relative to the following to the received audio signal port application types: relative to the port application type.Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Table 45-6 POTS Port Configuration Settings Field Port Direction Description The direction of calls passing through this port: • • • Usage Notes Inbound—Use for incoming calls only Outbound—Use for outgoing calls Bothways—Inbound and outbound calls (default) Port Level Audio Signal Adjustment into IP Network Adjusts the gain of audio entering or leaving the span.

This field is used for the processing of Specifies the number of significant digits to collect. The default is 1500 ms. We recommend always using default values for this timer. number used to route calls coming into the Significant digits are counted from the right (last digit) of the PRI span. unsure. • AnalogCOTrunk—Minus6db • • • • • • • • • • • DigitalToAnalogCO—Minus3db AnalogTieTrunk—NoDbPadding DigitalToDigitalCO—NoDbPadding ISDNStation—NoDbPadding ISDN_DigitalTieTrunk—NoDbPadding ISDNTrunk—NoDbPadding OnPremisePOTSLine—Plus3db OffPremisePOTSLine—Minus3db SatelliteAnalogTieTrunk—Minus3db SatelliteDigitalTieTrunk—Minus3db AnalogTollTrunk—NoDbPadding Prefix DN Specifies the prefix digits that The Cisco CallManager adds prefix digits are appended to the digits this after truncating the number in accordance trunk receives on incoming calls. See Prefix DN.Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Table 45-6 POTS Port Configuration Settings (continued) Field Description Usage Notes Audio Signal Specifies the gain or loss applied Select the gain or loss you want applied to the transmitted audio signal relative to the Adjustment from IP to the transmitted audio signal following port application types: Network relative to the port application type. with the Num Digits setting. Num Digits Expected Digits Call Restart Timer (1000-5000 ms) Cisco CallManager Administration Guide 45-30 OL-1047-01 . This field is rarely used. Number of digits expected on the Leave zero as the default value if you are inbound side of the trunk. from incoming calls and indicates the number of digits starting from the last digit of the called 0 to 32. number called.

Timer (100 -1000 ms) Onhook Validation Timer (100 -1000 ms) Hookflash Timer (100 . Offhook Validation The default is 100 ms. Cisco CallManager Administration Guide OL-1047-01 45-31 . page 45-4 Adding an Analog Gateway. AT-4.Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Table 45-6 POTS Port Configuration Settings (continued) Field Description Usage Notes We recommend always using default values for this timer. The default is 1000 ms.1500 ms) The default is 250 ms. Procedure Step 1 Step 2 Open Cisco CallManager Administration. See “Adding an Analog Gateway” section on page 45-7 for instructions. The Find and List Gateways screen appears. We recommend always using default values for this timer. page 45-7 Adding a Directory Number. We recommend always using default values for this timer. page 45-3 Catalyst 6000 Family Analog Line Card. page 46-19 Configuring Loop Start Ports Use this procedure to configure loop start ports on these devices: • Cisco AT-2. Select Device > Gateway. Related Topics • • • • Cisco Access Analog Gateways. and AT-8 Gateways Before You Begin You must add a Cisco analog gateway before configuring ports.

To add all available ports. Use for outgoing calls Both Ways. Inbound and outbound calls Cisco CallManager Administration Guide 45-32 OL-1047-01 . Select Loop Start as the port type. Use for incoming calls only Outbound. Step 5 Step 6 Click Add a New Port at the top of the list on the left side of the page to display a dialog for adding ports. Select the name of the analog access gateway from the list of gateways that matched the search criteria. Enter the appropriate settings as described in Table 45-7. or a range of ports by setting values for the Port Number and End Port Number fields. Table 45-7 Access Analog Loop Start Port Configuration Settings Field Port Direction Description The direction of calls passing through this port: • • • Usage Notes Inbound. • • To create a single port. you must select All Ports for both the Port Number and End Port number fields. The screen updates to display the Gateway Configuration screen with information for the selected analog access gateway.Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Step 3 Step 4 Enter the appropriate search criteria to locate the analog gateway to which you want to add loop start ports and click Find. The screen updates to add Port Number and End Port Number configuration options Step 7 Select whether you want to add and configure all available ports. Step 8 Step 9 Step 10 To modify additional settings. click Advanced. specify the same number in the Port Number and End Port Number fields. a single port. Click Insert and Close to add the ports and close the window.

Specifies the gain or loss applied to the received audio signal relative to the port application type.Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Table 45-7 Access Analog Loop Start Port Configuration Settings (continued) Field Trunk Level Audio Signal Adjustment into IP Network Description Adjusts the gain of audio entering or leaving the span. Usage Notes Select the gain or loss you want applied to the received audio signal relative to the following port application types: • • • • • • • • • • • • AnalogCOTrunk—Minus3db DigitalToAnalogCO—NoDbPadding AnalogTieTrunk—NoDbPadding DigitalToDigitalCO—NoDbPadding ISDNStation—NoDbPadding ISDN_DigitalTieTrunk—NoDbPadding ISDNTrunk—NoDbPadding OnPremisePOTSLine—Plus3db OffPremisePOTSLine—NoDbPadding SatelliteAnalogTieTrunk—NoDbPadding SatelliteDigitalTieTrunk—NoDbPadding AnalogTollTrunk—Plus3db Cisco CallManager Administration Guide OL-1047-01 45-33 .

The default is 500 ms. • AnalogCOTrunk—Minus6db • • • • • • • • • • • DigitalToAnalogCO—Minus3db AnalogTieTrunk—NoDbPadding DigitalToDigitalCO—NoDbPadding ISDNStation—NoDbPadding ISDN_DigitalTieTrunk—NoDbPadding ISDNTrunk—NoDbPadding OnPremisePOTSLine—Plus3db OffPremisePOTSLine—Minus3db SatelliteAnalogTieTrunk—Minus3db SatelliteDigitalTieTrunk—Minus3db AnalogTollTrunk—NoDbPadding Allowed Select if you want the Central Office to send caller ID Restricted Select if you do not want the Central Office to send caller ID Caller ID Enable Determines whether the Central Office transmits or blocks caller ID. For example. Delay Before Dialing Timer (100-5000 ms) Release Guard Timer (100-5000 ms) The default is 2000 ms. zero or a directory you want incoming calls routed. Type the number to which you want incoming The directory number to which calls routed. We recommend always using default values for this timer. • • Attendant DN For Loop_Start port type only. Cisco CallManager Administration Guide 45-34 OL-1047-01 .Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Table 45-7 Access Analog Loop Start Port Configuration Settings (continued) Field Description Usage Notes Select the gain or loss you want applied to the Audio Signal Specifies the gain or loss Adjustment from IP applied to the transmitted audio transmitted audio signal relative to the following port application types: Network signal relative to the port application type. number for an attendant. We recommend always using default values for this timer.

page 45-7 Configuring Ports on a Cisco MGCP Gateway Refer to these sections to configure ports on the VG200 FXS or FXO: • • Configuring FXS Ports on a Cisco MGCP Gateway. Cisco CallManager Administration Guide OL-1047-01 45-35 . Incoming Ring Halt The default is 4500 ms. page 45-35 Configuring FXO Ports on Cisco MGCP Gateways. Use this procedure to configure FXS ports on the Cisco VG200 gateway. We recommend always using default values for this timer. page 45-4 Adding an Analog Gateway. Related Topics • • • Cisco Access Analog Gateways. Timer (1000-8000 ms) Incoming Ring Validation Timer (100-2000 ms) The default is 400 ms. page 45-38 Configuring FXS Ports on a Cisco MGCP Gateway Foreign Exchange Station (FXS) ports can be used to connect to any POTS device. See the “Adding an MGCP Gateway” section on page 45-21 for instructions.Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Table 45-7 Access Analog Loop Start Port Configuration Settings (continued) Field Description Usage Notes We recommend always using default values for this timer. page 45-3 Catalyst 6000 Family Analog Line Card. Before You Begin You must add a Cisco VG200 gateway before configuring ports.

click the endpoint identifiers of the FXS port you want to configure. Calling Search Space Identifies the collection of route partitions searched to determine how a dialed number is routed. Step 5 Click the Add DN link for the port to add a directory numbers to the new POTS port. Usage Notes Description Device Pool This field is only used for Region selection. Identifies the Region selection for this device. Select Port Type > POTS. To the right of the new port is an Add DN link. Cisco CallManager Administration Guide 45-36 OL-1047-01 . Click Insert. Table 45-8 POTS on MGCP Gateway Configuration Settings Field MGCP Member Information Description Describes the purpose of the device.Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Procedure Step 1 Step 2 Step 3 Step 4 From the MGCP Configuration screen. the screen refreshes and displays the POTS port in the list on the left-hand side of the screen. Refer to the section “Adding a Directory Number” section on page 46-19 and Table 46-2 on page 46-20 for information about directory number configuration settings. The list of Cisco CallManagers this port connects to is configured through IOS commands on the gateway. Enter the appropriate settings as described in Table 45-8. Once you have inserted a POTS port.

Usage Notes The Cisco CallManager adds prefix digits after first truncating the number in accordance with the Num Digits setting. Specifies the number of significant digits to collect. See Prefix DN. This field is used for the processing of incoming calls and indicates the number of digits starting from the last digit of the called number used to route calls coming into the PRI span. This field is rarely used. from 0 to 32. page 45-21 “Adding a Directory Number” section on page 46-19 Cisco CallManager Administration Guide OL-1047-01 45-37 .Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Table 45-8 POTS on MGCP Gateway Configuration Settings (continued) Field Port Information Description Specifies the prefix digits that are appended to the digits received on incoming calls. Prefix DN Num Digits Expected Digits Number of digits expected on the inbound side of the trunk. Related Topics • • • Cisco VG200 Gateway. Significant digits are counted from the right (last digit) of the number called. Leave zero as the default value if you are unsure. page 45-6 Adding an MGCP Gateway.

page 45-40 Cisco CallManager assumes all loop start trunks lack positive disconnect supervision. Select Ground Start as the Port Type on the MGCP Member Configuration screen. See the section “Adding an MGCP Gateway” section on page 45-21 for instructions. page 45-38 Configuring Loop Start on MGCP Gateways. Before You Begin You must add an MGCP gateway before configuring ports. Enter the appropriate settings as described in Table 45-9. Procedure Step 1 Step 2 Step 3 From the MGCP Configuration screen. Configuring Ground Start on an MGCP Gateway Use this procedure to configure FXO ports for ground start on an MGCP gateway. Configure trunks with positive disconnect supervision as ground start so that active calls can be maintained during a Cisco CallManager server fail-over. Note The physical characteristics of a Cisco VG200 gateway port are configured under Cisco VG200 configuration. Cisco CallManager Administration Guide 45-38 OL-1047-01 . click the endpoint identifiers of the FXO port you want to configure. The following two subsections describe how to configure FXO ports for ground start and loop start: • • Configuring Ground Start on an MGCP Gateway.Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Configuring FXO Ports on Cisco MGCP Gateways Foreign Exchange Office (FXO) ports can be used for connecting to a central office or PBX.

Inbound and outbound calls Attendant DN The directory number to which you Type the number to which you want want incoming calls routed. The direction of calls passing through this port: • • • Location Port Information Port Direction Inbound. Cisco CallManager Administration Guide OL-1047-01 45-39 . Calling Search Space Specifies the collection of route partitions searched to determine how a dialed number should be routed. Usage Notes Description Device Pool This field is only used for Region selection.Chapter 45 Configuring Gateways Configuring Gateway Ports in Cisco CallManager Table 45-9 Ground Start on MGCP Gateway Configuration Settings Field MGCP Member Information Description Clarifies the purpose of device. Identifies the Region selection for this device. For example. The list of Cisco CallManagers this device connects to is configured through IOS commands on the gateway. Use for outgoing calls Both Ways. incoming calls routed. Specifies the remote location accessed using restricted bandwidth connections. Use for incoming calls only Outbound. zero or a directory number for an attendant.

page 45-21 Configuring Loop Start on MGCP Gateways Use this procedure to configure FXO ports for loop start on MGCP gateways. Calling Search Space Specifies the collection of route partitions searched to determine how a number should be routed. Enter the appropriate settings as described in Table 45-10. Before You Begin You must add an MGCP gateway before configuring ports. Usage Notes Description Device Pool This field is only used for Region selection. See the section “Adding an MGCP Gateway” section on page 45-21 for instructions.Chapter 45 Configuring Gateway Ports in Cisco CallManager Configuring Gateways Related Topics • • Cisco VG200 Gateway. The list of Cisco CallManagers this gateway connects to is configured through IOS commands on the gateway. page 45-6 Adding an MGCP Gateway. click the endpoint identifiers of the FXO port you want to configure. Select Loop Start as the Port Type on the MGCP Member Configuration screen. Procedure Step 1 Step 2 Step 3 From the MGCP Configuration screen. Table 45-10 Loop Start on MGCP Gateway Configuration Settings Field MGCP Member Information Description Clarifies the purpose of the device. Cisco CallManager Administration Guide 45-40 OL-1047-01 . Identifies the Region selection for this device.

Outbound. number for an attendant. page 45-6 Adding an MGCP Gateway. zero or a directory want incoming calls routed. page 45-42 Updating Gateways. Use for outgoing calls. Inbound and outbound calls.Chapter 45 Configuring Gateways Modifying Gateways Table 45-10 Loop Start on MGCP Gateway Configuration Settings (continued) Field Port Information Description The direction of calls passing through this port: • • • Usage Notes Port Direction Inbound. Use for incoming calls only. including: • • • Deleting Gateways. you perform several tasks identically regardless of the gateway type. page 45-42 Resetting Gateways. Both Ways. page 45-43 Cisco CallManager Administration Guide OL-1047-01 45-41 . Related Topics • • Cisco VG200 Gateway. page 45-21 Modifying Gateways Using Cisco CallManager. Attendant DN The directory number to which you For example.

Step 3 Enter search criteria to locate a specific gateway. The Find and List Gateways screen appears. Step 4 Click the Delete icon next to the gateway you want to delete. A message appears verifying that you want to delete the gateway. A list of discovered devices appears. page 45-44 Resetting Gateways Complete the following steps to reset a gateway using Cisco CallManager. A list of discovered devices appears.Chapter 45 Modifying Gateways Configuring Gateways Deleting Gateways Complete the following steps to delete a gateway from Cisco CallManager. Related Topics • • Adding Gateways to Cisco CallManager. page 45-7 Finding Specific Gateways. Step 3 Enter search criteria to locate a specific gateway. Select Devices > Gateway. Step 5 Click OK. The Find and List Gateway screen appears. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Cisco CallManager Administration Guide 45-42 OL-1047-01 . Procedure Step 1 Step 2 Open Cisco CallManager Administration. Select Device > Gateway.

Step 3 Enter search criteria to locate a specific gateway. Step 5 Click one of the following: • • Restart Device—Restart a device without shutting it down. page 45-44 Updating Gateways Complete the following steps to update a gateway from Cisco CallManager. Step 4 Select Device Name. Related Topics • • Adding Gateways to Cisco CallManager. page 45-44 Cisco CallManager Administration Guide OL-1047-01 45-43 . Related Topics • Finding Specific Gateways. A list of discovered device appears. Click Update. Procedure Step 1 Step 2 Open Cisco CallManager Select Device > Gateway. The Reset Device window appears. page 45-7 Finding Specific Gateways. The Gateway Configuration window appears. Reset Device—Shuts down a device and bring it back up. Step 5 Step 6 Step 7 Enter desired changes. The Find and List Gateways screen appears. Reset the gateway to put the changes into effect.Chapter 45 Configuring Gateways Modifying Gateways Step 4 Click the Reset button next to the gateway you want to reset.

page 45-46 Searching by Device Name Use this option if you know the device name of a specific gateway or if you want to get a listing of all gateways registered with Cisco CallManager. Step 3 Select Device Name from the drop-down list box. Cisco CallManager enables you to locate specific gateways based on specific criteria. Use these sections to • • • Searching by Device Name. Cisco CallManager Administration Guide 45-44 OL-1047-01 . Procedure Step 1 Step 2 Open Cisco CallManager Administration. Select Device > Gateway. then chose one of the following: • • • • • • begins with contains ends with is exactly is not empty is empty Step 4 Specify the appropriate search text. page 45-44 Searching by Description.Chapter 45 Finding Specific Gateways Configuring Gateways Finding Specific Gateways Because you might have hundreds of gateways in your network. page 45-45 Searching by Directory Number. if applicable. The Find and List Gateways screen appears.

page 45-45 Searching by Directory Number. Step 3 Select Description from the drop-down list box.Chapter 45 Configuring Gateways Finding Specific Gateways Step 5 Click Find. Select Device > Gateway. page 45-46 Searching by Description Use this option if you know any of the key words used in the Description field of a specific gateway registered with Cisco CallManager. then chose one of the following: • • • • begins with contains ends with is exactly Cisco CallManager Administration Guide OL-1047-01 45-45 . The Find and List Gateways screen appears. A list of discovered devices appears displaying: • • • • • • Device icon Device name Description Device pool Delete Reset Related Topics • • Searching by Description. Procedure Step 1 Step 2 Open Cisco CallManager Administration.

A list of discovered devices appears displaying: • • • • • • Device icon Device name Description Device pool Delete Reset Related Topics • • Searching by Device Name. Select Device > Gateway. if applicable.Chapter 45 Finding Specific Gateways Configuring Gateways • • Step 4 Step 5 is not empty is empty Specify the appropriate search text. page 45-44 Searching by Directory Number. The Find and List Gateways screen appears. then chose one of the following: • • begins with contains Cisco CallManager Administration Guide 45-46 OL-1047-01 . Procedure Step 1 Step 2 Open Cisco CallManager Administration. Click Find. page 45-46 Searching by Directory Number Use this option to locate gateways assigned to a specific extension or range of extensions and registered with Cisco CallManager. Step 3 Select Directory Number from the drop-down list box.

page 45-45 Cisco CallManager Administration Guide OL-1047-01 45-47 . Click Find. page 45-44 Searching by Description.Chapter 45 Configuring Gateways Finding Specific Gateways • • • • Step 4 Step 5 ends with is exactly is not empty is empty Specify the appropriate search text. A list of discovered devices appears displaying: • • • • • Device icon Device name Description Delete Reset Related Topics • • Searching by Device Name. if applicable.

Chapter 45 Finding Specific Gateways Configuring Gateways Cisco CallManager Administration Guide 45-48 OL-1047-01 .

323 Clients CTI Ports Note Devices such as analog phones or fax machines must be connected to a gateway (for example. it can be accessed by opening Cisco CallManager administration and selecting Application > BAT. modify.C H A P T E R 46 Configuring Cisco IP Phones in Cisco CallManager Cisco IP Phones are full-featured telephones that can be plugged directly into your IP network. If you are administering a large number of phones at your site. If BAT is already installed on your Cisco CallManager system. and delete operations for Cisco IP Phones instead of manually adding and configuring each phone using Cisco CallManager Administration. you can use the Bulk Administration Tool (BAT) to perform batch add. a Cisco VG200 gateway). Cisco CallManager Administration Guide OL-1047-01 46-1 . BAT is a plug-in application for Cisco CallManager. Cisco CallManager supports the following Cisco IP Phones: • • • Cisco IP Phone 7900 Family Cisco IP Phone 30 VIP Cisco IP Phone 12 SP+ The following devices are also configured through the Cisco CallManager Administration phone configuration pages: • • H.

page 46-18 Configuring Phone Button Templates. page 46-25 Understanding Cisco IP Phones The following topics describe the types of phones and other devices that can be configured through the Device > Phone area of Cisco CallManager Administration: • • • • • Cisco IP Phone 7900 Family Cisco IP Phone 30 VIP Cisco IP Phone 12 SP+ CTI Ports H. Related Topics The following topics provide information about working with and configuring Cisco IP phones in Cisco CallManager: • • • • • • • Understanding Cisco IP Phones. which include the following models: • • Cisco IP Phone 7960 Cisco IP Phone 7940 Cisco CallManager Administration Guide 46-2 OL-1047-01 . page 47-1 Shared Line Appearances. page 46-16 Configuring Directory Numbers.323 Clients Cisco IP Phone 7900 Family Cisco CallManager supports the Cisco IP Phone 7900 family of phones.Chapter 46 Understanding Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager Refer to the Bulk Administration Tool Guide for Cisco CallManager for detailed instructions on configuring BAT to perform batch operations on Cisco IP phones. page 46-15 Configuring Phone Features. page 46-2 Configuring Cisco IP Phones. page 46-5 Finding a Phone.

services.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Understanding Cisco IP Phones • Cisco IP Phone 7910 Cisco CallManager does not directly control all features on these phones through phone button templates. and directories Four soft keys for displaying additional call detail and functionality A large LCD display that shows call detail and soft key functions An internal two-way speakerphone and microphone mute Cisco CallManager Administration Guide OL-1047-01 46-3 . Cisco IP Phone 7960 The Cisco IP Phone model 7960 is a full-featured. These include: • • • • • • An information (i) button Two programmable buttons (these can be configured as two lines or one line and one speed dial) Four on-screen mode buttons for accessing voice mail messages and adjusting phone settings. six-line business set that supports the following features: • • • • • • An information (i) button Six programmable line or speed dial buttons Four fixed buttons for accessing voice mail messages and adjusting phone settings. services. Refer to the Cisco IP Phone 7900 Family Administration Guide and the Getting Started publications for individual Cisco IP Phone 7900 Family models for detailed information. and directories Four soft keys for displaying additional call detail and functionality A large LCD display that shows call detail and soft key functions An internal two-way speakerphone and microphone mute Cisco IP Phone 7940 The Cisco IP Phone model 7940 is a two-line business set with features similar to the Cisco IP Phone model 7960.

Redial. Speed Dial. Conference. date and time An internal two-way speakerphone and microphone mute Cisco IP Phone 12 SP+ The Cisco IP Phone model 12 SP+ offers many of the same features as PBX or plain old telephone service (POTS) telephones. and Settings Six programmable feature buttons that can be configured through phone button templates in Cisco CallManager Available features include Call Park.Chapter 46 Understanding Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager Cisco IP Phone 7910 The Cisco IP Phone 7910 is a single-line. Call Pickup. call status. Transfer. Hold. • • A two-line LCD display (24 characters per line) that indicates the directory number. This IP phone includes the following features: • 26 programmable line and feature buttons Cisco CallManager Administration Guide 46-4 OL-1047-01 . and Meet-Me Conference. basic feature phone designed primarily for common-use areas with medium telephone traffic such as lobbies or break rooms. Forward All. It includes the following features: • • Four dedicated feature buttons for Line. Group Call Pickup. Message Waiting. This IP phone includes the following features: • • • • 12 programmable line and feature buttons An LED associated with each of the 12 feature and line buttons to indicate feature and line status A two-line LCD display (20 characters per line) for call status and identification An internal two-way speakerphone and microphone mute Cisco IP Phone 30 VIP The Cisco IP Phone 30 VIP offers many of the same features as PBX or plain old telephone service (POTS) telephones.

you can choose to allow the phone to auto-register itself with the Cisco CallManager database. By enabling auto-registration. refer to the “Configuring Cisco IP Phones” section on page 46-5. but require fewer configuration settings. calling party name. Configuring Cisco IP Phones When connecting a Cisco IP Phone to your IP telephony network. Cisco AutoAttendant. you can automatically add phones to the database. such as Cisco SoftPhone. calling party number. and digits dialed An internal two-way speakerphone with microphone mute A transfer feature button CTI Ports CTI ports are virtual devices that are used by software-based Cisco CallManager applications such as Cisco SoftPhone. Cisco CallManager Administration Guide OL-1047-01 46-5 .323 clients include Microsoft NetMeeting devices and NetVision Symbol phones.323 clients. • • For general instructions on how to configure settings for CTI ports. and Cisco IP Interactive Voice Response (IVR). refer to the documentation and online help provided with that application. For instructions on how to configure H. H. CTI ports are configured through the same Cisco CallManager Administration area as phones. but require fewer configuration settings.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Cisco IP Phones • • • • An LED associated with each of the 26 feature and line buttons to indicate feature and line status A two-line LCD for displaying date and time. They are configured through the same Cisco CallManager Administration pages as phones. refer to the “Configuring Cisco IP Phones” section on page 46-5.323 Clients H. For information on how to configure CTI ports for use with a specific application.

H. Refer to the Bulk Administration Tool Guide for Cisco CallManager for detailed instructions on using BAT. page 46-14 Displaying the MAC Address of a Phone The Media Access Control (MAC) address is a unique 12-character hexadecimal number that identifies a Cisco IP Phone or other hardware device. The MAC address is a required field for Cisco IP Phone device configuration. page 46-11 Resetting a Phone. you might not want to use auto-registration. update. If you do not use auto-registration. 000B6A409C405 for Cisco IP Phone 7900 Family models or SS-00-0B-64-09-C4-05 for Cisco IP Phone SP 12+ and 30 VIP models). Instead. You can also delete. and are covered in the procedures in this section. For example. Related Topics • • • • • • Displaying the MAC Address of a Phone. do not use spaces or dashes and do not include the "SS" that may precede the MAC address on the label. page 46-13 Copying an Existing Phone. you must manually add phones to the Cisco CallManager database or use the Bulk Administration Tool (BAT). page 46-6 Adding a Phone. auto-registration does not allow you to assign specific directory numbers to a phone. numbers are assigned sequentially based on the next available number designated in Cisco CallManager. in many cases. and copy phones from Cisco CallManager. reset. and delete operations on large numbers of Cisco IP Phones.Chapter 46 Configuring Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager However. It is located on a label on the bottom of the phone (for example. When entering the MAC address in Cisco CallManager fields. Cisco CallManager Administration Guide 46-6 OL-1047-01 .323 clients and CTI ports are also configured in this area of Cisco CallManager Administration. page 46-7 Deleting a Phone. modify. page 46-12 Updating a Phone. BAT is a plug-in application that enables system administrators to perform batch add.

press 6 on the phone keypad to begin displaying the Network Config options. use the arrow buttons to locate Network Config options. Step 3 Select Phone from the Device Type drop-down list box and click Next. you must add the phone to Cisco CallManager. The Add a New Device page displays. Cisco IP Phone 12 SP+ and 30VIP models — press ** to display the MAC address on the second line of the LCD display. Step 4 Select the appropriate phone type (Cisco IP Phone model. The Add a New Phone page displays. • • For more information about displaying additional configuration settings on Cisco IP Phones. you cannot modify it. CTI ports are virtual devices used by Cisco CallManager applications such as Cisco SoftPhone and Cisco AutoAttendant Cisco CallManager Administration Guide OL-1047-01 46-7 . Adding a Phone Before a Cisco IP Phone can be used. Procedure Step 1 Step 2 Open Cisco CallManager Administration. use the arrow buttons to highlight the Network Configuration menu option.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Cisco IP Phones To display the MAC address when the phone is powered on: • Cisco IP Phone 7960 and 7940 models — press Settings. then use the arrow keys to scroll the Network Config option display to the MAC address. H. or CTI port) from the phone type drop-down list and click Next. Select Device > Add a Device.323 client. refer to the Cisco IP Phone 7900 Family Administration Guide and the individual Getting Started publications provided with Cisco IP Phones. The Phone Configuration page displays. and press the Select softkey. Cisco IP Phone 7910 — Press Settings. • • Once you select a phone type.

Refer to the “Setting Device Defaults” section on page 15-1. Refer to the “Setting Device Defaults” section on page 15-1. Device Pool Defines sets of common characteristics for devices.323 clients and CTI ports • Description Load Information Clarifies the purpose of the device. The value entered here overrides the default value for this type of device. Only the settings appropriate to the selected phone type will appear on your screen. Enter the appropriate settings as described in Table 46-1. Cisco CallManager group. The value entered here overrides the default values for this type of device. date/time group. and calling search space for auto-registration Cisco CallManager Administration Guide 46-8 OL-1047-01 . • Value can include 1 to 15 characters. Usage Notes • • Value must be 12 hexadecimal characters.Chapter 46 Configuring Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager • Step 5 H. dash.323 clients can be Symbol NetVision phones or Microsoft NetMeeting clients. This field is only displayed for hardware Cisco IP Phones Device Name Identifies software-based telephones. Only available for H. such as region. Specifies custom software for a Cisco IP Phone. These settings are not available for all phone types. Table 46-1 IP Phone Configuration Settings Field Device Information MAC Address Description Media Access Control (MAC) address that identifies Cisco IP Phones (hardware phones only) Refer to the “Displaying the MAC Address of a Phone” section on page 46-6. dot. including alphanumeric. or underscores.

speed dial. The Central Office (CO) prepends the number with the area code if you do not specify it. Not available for H. The value entered here overrides the default value for this type of device.323 Client-Specific Device Information Outgoing Caller ID Pattern Specifies the number to send as Caller ID for outgoing calls. Usage Notes Calling Search Space Specifies the collection of Route Partitions searched to determine how a dialed number should be routed. and so on) is used for each button.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Cisco IP Phones Table 46-1 IP Phone Configuration Settings (continued) Field Location Description Specifies the remote location accessed using restricted bandwidth connections. where XXXX is equal to an extension number or directory number (X is a number from 0 to 9) and NNN is the office code. 5555000 = Fixed Caller ID. For example. NNNXXXX = variable Caller ID. Button Template Determines the configuration of buttons on a phone and identifies which feature (line.323 clients or CTI ports. The CO appends the number with the area code if you do not specify it. Refer to the “Setting Device Defaults” section on page 15-1. Use when you want the Corporate number to be sent instead of the exact extension from which the call is placed. in North America: • H. • Cisco CallManager Administration Guide OL-1047-01 46-9 .

Usage Notes • • Originator—send the directory number of the calling device. • Caller ID Presentation Determines whether the central office transmits or blocks caller ID.Chapter 46 Configuring Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager Table 46-1 IP Phone Configuration Settings (continued) Field Calling Party Selection Description Determines what to display if a call to this device is forwarded or transferred. it enables delivery of the display IE (incoming exclusion) in SETUP and CONNECT messages for the calling and called party name delivery service.245 Empty Capabilities Set message. Select Restricted if you do not want the Central Office to send caller ID. Display IE Delivery Media Termination Point Required Used for H. First Redirect Number—send the directory number of the redirecting device. Cisco CallManager Administration Guide 46-10 OL-1047-01 . to implement features that H. Cisco IP Phone . Select Allowed if you want the Central Office to send caller ID.323 does not support (such as hold and transfer).External Data Locations (leave blank to use the default) Directory Information Specifies the location (UL) of Only used for Cisco IP Phone 7960 and the help text for the information 7940 models. By default. (i) button. Specifies the primary and secondary servers from which the phone obtains directory information. Only used for Cisco IP Phone 7960 and 7940 models. Display IE Delivery is disabled. When this box is checked. Last Redirect Number—send the directory number of the last device to redirect the call.323 devices that do not support Determines whether or not a Media Termination Point is used the H.

page 46-13 Deleting a Phone Perform the following procedure to delete a Cisco IP Phone from Cisco CallManager.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Cisco IP Phones Table 46-1 IP Phone Configuration Settings (continued) Field Services Messages Description Usage Notes Specifies the location (URL) for Only used for Cisco IP Phone 7960 and Cisco IP Phone Services. Add a directory number to this phone. page 46-11 Updating a Phone. Cisco CallManager Administration Guide OL-1047-01 46-11 . Related Topics • • • • Resetting a Phone. Refer to the “Resetting a Phone” section on page 46-12. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Specifies the voice mail pilot Only used for Cisco IP Phone 7960 and directory number for messaging. Step 3 Enter search criteria to locate a specific phone and click Find. 7940 models. Select Device > Phone. You must reset the phone after making changes to apply the new settings. The Find and List Phones page displays. page 46-19 Deleting a Phone. Refer to the “Adding a Directory Number” section on page 46-19. page 46-12 Adding a Directory Number. Step 6 Step 7 Step 8 Click Insert. 7940 models.

Step 4 Click the Reset button next to the phone you want to reset.Chapter 46 Configuring Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager A list of phones that match the search criteria appears. Step 3 Enter search criteria to locate a specific phone and click Find. page 46-15 Adding a Phone. A list of phones that match the search criteria appears. Before You Begin If a call is in progress. Select Device > Phone. Procedure Step 1 Step 2 Open Cisco CallManager Administration. page 46-7 Resetting a Phone Perform the following procedure to reset a Cisco IP Phone using Cisco CallManager. Step 4 Click the Delete icon next to the phone you want to delete. Step 5 Click OK. Cisco CallManager Administration Guide 46-12 OL-1047-01 . A message appears verifying that you want to delete the phone. the phone does not reset until the call is finished. The Find and List Phones page displays. Related Topics • • Finding a Phone. The Reset Device page displays. Step 5 Click one of the following: • Restart Device—Restarts a device without shutting it down (re-registers the phone with Cisco CallManager).

Select Device > Phone. A list of phones that match the search criteria appears. Step 4 Select the name of the phone you want to update from the list. The Phone Configuration page displays. page 46-7 Cisco CallManager Administration Guide OL-1047-01 46-13 . Step 5 Step 6 Step 7 Enter desired changes. Step 3 Enter search criteria to locate a specific phone and click Find. page 46-7 Updating a Phone Perform the following procedure to update a Cisco IP Phone from Cisco CallManager. The Find and List Phones page displays. page 46-15 Adding a Phone. Click Update. Related Topics • • Finding a Phone. page 46-15 Adding a Phone. Click Reset to reset the phone and apply the new settings. Procedure Step 1 Step 2 Open Cisco CallManager Administration.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Cisco IP Phones • Reset Device—Shuts down a device and bring it back up (performs a complete shut-down and re-initialization of the phone). Related Topics • • Finding a Phone.

The Find and List Phones page displays.Chapter 46 Configuring Cisco IP Phones Configuring Cisco IP Phones in Cisco CallManager Copying an Existing Phone If you want to manually add several similar phones to the Cisco CallManager database. Perform the following procedure to copy a phone’s settings. page 46-19 Finding a Phone. page 46-15 Adding a Phone. you can add one and then copy its basic settings to apply to another phone. you can add and configure lines for the new phone. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Click Insert. You must change at least the Media Access Control (MAC) address before inserting the new phone into the database. page 46-7 Cisco CallManager Administration Guide 46-14 OL-1047-01 . Step 3 Enter search criteria to locate a specific phone and click Find. Once it is added. Related Topics • • • Adding a Directory Number. The Phone Configuration page displays. Select Device > Phone. Step 5 Step 6 Step 7 Enter the MAC address of the new phone. Step 4 Click on the Copy icon for the phone whose settings you want to copy. Enter additional desired changes. A list of phones that match the search criteria appears.

A list of the first 20 discovered devices appears. The total number of devices and pages are also listed on this page. The Find and List Phones page displays. Follow these steps to search for a specific Cisco IP Phone in the Cisco CallManager database. Click Find. Cisco CallManager Administration Guide OL-1047-01 46-15 . Select Device > Phone. Step 3 Select one of the following options from list of fields: • • • • • Device Name Description Directory Number Calling Search Space Device Pool Step 4 Select one of the following options from the list of patterns: • • • • • • begins with contains ends with is exactly exists is empty Step 5 Step 6 Enter the item to search for in the Find field.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Finding a Phone Finding a Phone Because you might have thousands of Cisco IP Phones in your network. The devices in the list are sorted by the field you selected in Step 3. Cisco CallManager enables you to search for phones based on specified criteria. Procedure Step 1 Step 2 Open Cisco CallManager Administration.

page 46-5 Tips for Finding a Phone Searching by Calling Search Space or Device Pool If you select calling search space or device pool. select Device Name from the list of fields.Chapter 46 Configuring Phone Features Configuring Cisco IP Phones in Cisco CallManager Step 7 To view the next set of discovered devices. page 46-15 Configuring Phone Features Cisco CallManager enables you to configure these phone features on Cisco IP Phones: call waiting. page 46-16 Configuring Cisco IP Phones. page 46-17 Cisco CallManager Administration Guide 46-16 OL-1047-01 . You can select one of these options from the drop-down list box below the Find button. then click Find. page 46-17 Configuring Call Forward. Finding All Phones in the Database To find all phones registered in the database. call park. Related Topics • • Tips for Finding a Phone. call forward. and call pickup. select “is not empty” from the list of patterns. Note Analog phones and fax machines connected to gateways (such as a Cisco VG200) are not included in this list. the options available in the database display. Related Topics • • Configuring Call Waiting. click Next. Only phones configured in Cisco CallManager Administration are listed here. Related Topics • Finding a Phone.

Call waiting is configured on the Configure a Directory Number web page in Cisco CallManager Administration. page 46-17 Configuring Call Pickup. There are three types of call forward: • • • Call forward all—Forwards all calls. page 46-19 Configuring Call Park Call park allows a user to place a call on hold so that anyone connected to the Cisco CallManager system can retrieve it. Cisco CallManager Administration Guide OL-1047-01 46-17 . Related Topics • Adding a Directory Number. Call forward no answer—Forwards calls when the phone is not answered after four rings. Call waiting is configured on the Configure a Directory Number web page in Cisco CallManager Administration. Related Topics • Adding a Directory Number. page 46-19 Configuring Call Forward Call forward is a phone feature that allows a user to configure a Cisco IP Phone so that all calls destined for it ring another phone. When the second call arrives. page 46-18 Configuring Call Waiting Call waiting lets users receive a second incoming call on the same line without disconnecting the first call. Call forward busy—Forwards calls only when the line is in use.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Phone Features • • Configuring Call Park. the user hears a brief call waiting indicator tone.

and disabling ring on a line. page 46-19 Configuring Call Pickup. Cisco CallManager Administration Guide 46-18 OL-1047-01 . page 39-1 Configuring Call Pickup Call pickup allows you to use your phone to answer another ringing phone in your designated call pickup group. The call park extension is added when configuring phone features in Cisco CallManager Administration. You configure call pickup when configuring phone features in Cisco CallManager. if a user is on an active call at extension 1000. Refer to the “Configuring Call Pickup” section on page 40-1 for details. configuring call forward. 1234) must be added in Cisco CallManager Administration. when adding a directory line. and call waiting.Chapter 46 Configuring Directory Numbers Configuring Cisco IP Phones in Cisco CallManager For example. This area of Cisco CallManager Administration is where you perform tasks such as adding or removing directory lines. the call park extension (in this case. To use call park. Anyone connected to the system can then dial 1234 to retrieve the call. setting the display text that appears on the called party’s phone when a call is placed from a line. These sections provide instructions for working with directory lines. you can configure and modify directory lines assigned to specific phones. The call pick up group indicates a number that can be dialed to answer calls to this directory number (in the specified partition). However. See the “Adding a Directory Number” section on page 46-19 for details. page 40-1 Configuring Directory Numbers Using Cisco CallManager. Related Topics • • Adding a Directory Number. Related Topics • Configuring Call Park. call pickup. they can park the call to a call park extension such as 1234. you can indicate the call pickup group.

The Configure a Directory Number page displays in a separate window. page 46-23 Updating a Directory Number. The Phone Configuration page displays. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Cisco CallManager Administration Guide OL-1047-01 46-19 . The Find and List Phones page displays. Step 3 Enter search criteria to locate a specific phone. page 46-25 Adding a Directory Number Follow these instructions to add a directory line to a specific phone. Step 5 Select an unassigned line (Line 1. and so on). Select Device > Phone.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Directory Numbers Related Topics • • • • Adding a Directory Number. Step 4 Select Device Name. page 46-19 Deleting a Directory Number. Step 6 Enter the appropriate settings as described in Table 46-2. Line 2. Before You Begin You must add a Cisco IP Phone to Cisco CallManager before adding a directory line. A list of discovered devices appears. page 46-24 Shared Line Appearances. See the “Adding a Phone” section on page 46-7 for details. with the lines listed on the left side.

Applies to all devices using this directory number. Indicates a number that can be dialed to answer calls to this directory number (in the specified partition). Usage Notes • Directory Number Values can include a maximum of 50 numeric characters except for (. • • Partition Indicates the route partition to which the directory number belongs. • Call Waiting Specifies whether this directory number uses call waiting when a line is busy (On). If the words Shared Line appear in red next to the directory number. responds with a busy signal (Off). or uses the system-wide default setting (Default). Applies to all devices using this directory number.) and (@). the directory number appears on more than one device in the same partition.Chapter 46 Configuring Directory Numbers Configuring Cisco IP Phones in Cisco CallManager Table 46-2 Directory Line Configuration Settings Field Directory Number Description Indicates a dialable phone number. Collection of partitions that are searched for numbers called from this directory number. Call Forward and Pickup Settings Call Pickup Group Cisco CallManager Administration Guide 46-20 OL-1047-01 . Can appear in more than one partition. Unique in combination with the Directory Number. • Directory Number Settings Calling Search Space • Changes cause update of the numbers listed in the Call Pickup Group field. Refer to the “Shared Line Appearances” section on page 46-25 for more information. Unique in combination with partition.

• Leave this field blank to have the system display the extension.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Directory Numbers Table 46-2 Directory Line Configuration Settings (continued) Field Forward All Description Indicates the directory number to which all calls are forwarded. Any dialable phone number. Typically use the user’s name or the directory number. Forward Busy. Usage Notes • Any dialable phone number. including an outside destination. • Forward Busy Indicates the directory number that a call is forwarded to when the line is in use. • • Forward No Answer Indicates the directory number that a call is forwarded to when no one answers after four rings. Applies to all devices using this directory number. including an outside destination. including an outside destination. Applies to all devices using this directory number. and Forward No Answer directory numbers. Any dialable phone number. • • Calling Search Space Indicates the Calling Search Space to use when forwarding to the specified destination. Calling Search Space can be configured for Forward All. Applies to all devices using this directory number. Applies to all devices using this directory number. • Line Settings for this Phone Display Indicates text that appears on the called party’s phone when a call is placed from this line. Applies only to the current device. • • • Cisco CallManager Administration Guide OL-1047-01 46-21 . Maximum of 30 alphanumeric characters.

page 46-7 Deleting a Directory Number. Click Reset Devices. on this phone. Step 7 Step 8 Click Update. page 46-24 Cisco CallManager Administration Guide 46-22 OL-1047-01 . • • Cisco IP Phone 7960—The text is displayed on the LCD.Chapter 46 Configuring Directory Numbers Configuring Cisco IP Phones in Cisco CallManager Table 46-2 Directory Line Configuration Settings (continued) Field Label Description Usage Notes Indicates the text for the line button Applies only to the current device. Other Cisco IP Phones—The text is not displayed but could be used when printing button templates. Indicates phone number (or mask) used to send Caller ID information when placing a call from this line. page 46-23 Updating a Directory Number. Related Topics • • • • Finding a Phone. Applies only to the current device. The X characters must appear at the end of the pattern. Maximum of 30 number and “X” characters. Disable ring on this line External Phone Number Mask Stops the phone from ringing to indicate incoming calls. page 46-15 Adding a Phone.

page 46-24 Cisco CallManager Administration Guide OL-1047-01 46-23 . page 46-15 Adding a Directory Number. Step 3 Enter the search criteria to locate a specific phone and click Find. The Phone Configuration page displays. Step 5 Select the line you want to delete. page 46-19 Updating a Directory Number. The Directory Number configuration page displays. The Find and List Phones page displays.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Configuring Directory Numbers Deleting a Directory Number Perform the following procedure to delete a directory number from a specific phone. Step 7 Click OK. Step 4 Select a Device Name. Step 6 Click Delete. with the lines listed on the left side. The Phone Configuration page displays with the line deleted. Related Topics • • • Finding a Phone. A list of discovered devices appears. A message appears verifying that you want to delete the line. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Step 8 Click Reset. Select Device > Phone.

page 46-7 Adding a Directory Number. The Phone Configuration page displays. Procedure Step 1 Step 2 Open Cisco CallManager Administration. Step 6 Step 7 Step 8 Enter the desired changes. Click Update. page 46-19 Deleting a Directory Number. Step 4 Select the name of the phone to update. page 46-23 Cisco CallManager Administration Guide 46-24 OL-1047-01 .Chapter 46 Configuring Directory Numbers Configuring Cisco IP Phones in Cisco CallManager Updating a Directory Number Follow these instructions to update a directory number assigned to a specific phone. Step 5 Select the line you want to update. with the lines listed on the left side. Select Device > Phone. Click Reset Devices. A list of phones that match the search criteria appears. Related Topics • • • • Finding a Phone. The Directory Number Configuration page displays. The Find and List Phones page displays. Step 3 Enter search criteria to locate a specific phone. page 46-15 Adding a Phone.

Delete will remove the directory number only on the current device. change the directory number or partition • • number for the line and update the device. To stop sharing a line appearance on a device: – If the shared line is not line 1. The following notes and tips apply to using shared line appearances with Cisco CallManager: • • You create a shared line appearance by assigning the same directory number and partition to different lines on different devices. Call Waiting. Do not use shared line appearances on any phone that will be used with Cisco WebAttendant. Related Topics • • • Adding a Directory Number. you must first delete the line from the device. For example. a directory number (line) is considered to be a shared line if it appears on more than one device in the same partition. a shared line can be set up so that a directory number appears on line 1 of a manager’s phone and also on line 2 of their assistant’s phone. and then re-add the line with a new directory number or partition. page 46-23 Updating a Directory Number. If you change the Calling Search Space.Chapter 46 Configuring Cisco IP Phones in Cisco CallManager Shared Line Appearances Shared Line Appearances In a Cisco CallManager system. • • In the case of a shared line appearance. Another example of a shared line would be a single incoming 800 number that is set up to appear as line 2 on every sales representative’s phone in an office. If a line will be shared with other devices. the changes are applied to all devices that use that shared line. or Call Forward and Pickup settings on any device that uses the shared line. This is referred to as a shared line appearance. Other devices are not affected. page 46-24 Cisco CallManager Administration Guide OL-1047-01 46-25 . – If the shared line is line 1. the words Shared Line are displayed in red next to the directory number in the Configure a Line Number page in Cisco CallManager Administration. page 46-19 Deleting a Directory Number.

Chapter 46 Shared Line Appearances Configuring Cisco IP Phones in Cisco CallManager Cisco CallManager Administration Guide 46-26 OL-1047-01 .

For example. All phones must have at least one line assigned. these features are implemented differently on various models. or create a new template. For example. assigned to the remaining buttons. you can create a template that reassigns this button to a different feature. Phones can have additional lines assigned. other models have fixed buttons or on-screen program keys for these features that are not Cisco CallManager Administration Guide OL-1047-01 47-1 . depending on the Cisco IP Phone model. some models configure features such as Hold or Transfer using phone button templates. When adding phones. page 47-5 Modifying Phone Button Templates. such as speed dial and call forward.C H A P T E R 47 Configuring Phone Button Templates Cisco CallManager includes several default phone button templates. such as speed dial. Creating and using templates is a fast way to assign a common button configuration to a large number of phones. page 47-1 Adding Phone Button Templates. The following sections provide details about using and working with the phone button templates: • • • Understanding Default Phone Button Templates. Phones also generally have several features. page 47-9 Understanding Default Phone Button Templates Although all Cisco IP Phones support similar features. if users in your company do not use the conference feature. Normally this is button 1 (with a feature index of 1). you can assign one of these templates to the phones.

Chapter 47 Understanding Default Phone Button Templates

Configuring Phone Button Templates

configurable. Also, the maximum number of lines or speed dials supported is different for some phone models. These differences require different phone button templates for specific models. A default phone button template is provided for each Cisco IP Phone model. The default templates can be used as is to quickly configure phones. They can also be copied and modified to create custom templates. Custom templates enable you to make features available on some or all phones, restrict the use of certain features to certain phones, configure a different number of lines or speed dials for some or all phones, and so on, depending on how the phone will be used. For example, you may want to create a custom template that can be applied to phones that will be used in conference rooms. Refer to the “Adding Phone Button Templates” section on page 47-5 and the “Guidelines for Creating Custom Templates” section on page 47-7 for more information.
Related Topics
• • • • • •

Default Cisco IP Phone 7960 Template, page 47-2 Default Cisco IP Phone 7940 Templates, page 47-3 Default Cisco IP Phone 7910 Templates, page 47-3 Default Cisco IP Phone 30 SP+ Template, page 47-3 Default Cisco IP Phone 30 VIP Template, page 47-4 Default Cisco IP Phone 12-Series Template, page 47-4

Default Cisco IP Phone 7960 Template
The default Cisco IP Phone 7960 template uses buttons 1 and 2 for lines, and assigns buttons 3 through 6 as speed dial. Other phone features, such as call park, call forward, redial, hold, resume, voice mail, conferencing, and so on are accessed using soft keys on the Cisco IP Phone 7960.
Related Topics
• •

Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Cisco CallManager Administration Guide

47-2

OL-1047-01

Chapter 47

Configuring Phone Button Templates Understanding Default Phone Button Templates

Default Cisco IP Phone 7940 Templates
Two preconfigured phone button templates are provided for the Cisco IP Phone 7940:
• •

7940 (2-Line)—Uses button 1 and 2 for lines. 7940 (1-Line)—Uses button 1 for line 1 and button 2 for speed dial.

All Cisco IP Phone 7940 phones use one or the other of these templates. Phone features, such as call park, call forward, redial, hold, resume, voice mail, conferencing, and so on are accessed using soft keys on the Cisco IP Phone 7940.
Related Topics
• •

Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Default Cisco IP Phone 7910 Templates
The default phone button template for the Cisco IP Phone 7910 (named Default 7910), uses button 1 for message waiting, button 2 for conference, button 3 for forwarding, buttons 4 and 5 for speed dial, and button 6 for redial. The Cisco IP Phone 7910 has fixed buttons for Line, Hold, Transfer, and Settings.
Related Topics
• •

Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Default Cisco IP Phone 30 SP+ Template
The default Cisco IP Phone 30 SP+ template uses buttons 1 through 4 for lines, button 5 for call park, button 6 for redial, buttons 8 through 13 and 22 through 25 for speed dial, button 14 for message waiting indicator, button 15 for forward, and button 16 for conference.

Cisco CallManager Administration Guide OL-1047-01

47-3

Chapter 47 Understanding Default Phone Button Templates

Configuring Phone Button Templates

Note

For the Cisco IP Phone 30 SP+ only, button 26 must be assigned Automatic Echo Cancellation (AEC).
Related Topics
• •

Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Default Cisco IP Phone 30 VIP Template
The default Cisco IP Phone 30 VIP template uses buttons 1 through 4 for lines, button 5 for call park, button 6 for redial, buttons 8 through 13 and 22 through 25 for speed dial, button 14 for message waiting indicator, button 15 for call forward, and button 16 for conference.
Related Topics
• •

Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Default Cisco IP Phone 12-Series Template
All Cisco IP Phone 12 Series phones (12 S, 12 SP, 12 SP+) use the default Cisco IP Phone 12 SP+ template. The default Cisco IP Phone 12 SP+ template uses buttons 1 and 2 for lines, button 3 for redial, buttons 4 through 6 for speed dial, button 7 for hold, button 8 for transfer, button 9 for forwarding, button 10 for call park, button 11 for message waiting, and button 12 for conference.
Related Topics
• •

Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Cisco CallManager Administration Guide

47-4

OL-1047-01

Chapter 47

Configuring Phone Button Templates Adding Phone Button Templates

Adding Phone Button Templates
Creating and using templates is a fast way to assign a common button configuration to a large number of phones. For example, if users in your company do not use the conference feature, you can create a template that reassigns this button to a different feature, such as speed dial. Default templates for each Cisco IP phone model are included with the Cisco CallManager. When adding phones, you can assign one of these templates to the phone, or create one of your own.
Before You Begin

If you are creating a custom phone button template, refer to the to the guidelines for creating new phone button templates. See the “Guidelines for Creating Custom Templates” section on page 47-7.
Procedure
Step 1 Step 2

Open Cisco CallManager Administration. Select Device > Phone Button Template. Decide which method to use to create this template:

Based on existing template—the new template exactly duplicates the existing template. You must update this new template if you want it to be different from the original. New design for a specific phone—You must set up each button individually.

• Step 3

Choose a method to create this template:

Select a template and click Copy to create a new template. The new template exactly duplicates the existing template and automatically assigns it a new name. You must update this new template if you want it to be different than the original.

Select a phone and click Continue to create a new template and assign each button individually. The new template is preset with only the required settings for that specific phone type.

Step 4

Make desired changes to the fields described in Table 47-1.

Cisco CallManager Administration Guide OL-1047-01

47-5

Chapter 47 Adding Phone Button Templates

Configuring Phone Button Templates

Table 47-1 Phone Button Configuration Settings

Field Template Name

Description Unique name used by Cisco CallManager to identify the template. Specifies the function of the phone button when the template is used. Specifies the instance of a feature so that templates can have multiple line and speed-dial buttons.

Usage Notes
• •

Use any 1-50 characters. Each template must have a unique name.

Feature Index

Label

Text that appears when the template Cisco IP Phone 79xx model phones ignore this setting. is displayed in the Administration interface or printed on some Cisco IP Phones.
Step 5 Step 6

Click Insert to add the new template. Click View Button Layout to verify the button layout.

Related Topics
• • •

Guidelines for Creating Custom Templates, page 47-7 Understanding Default Phone Button Templates, page 47-1 Modifying Phone Button Templates, page 47-9

Cisco CallManager Administration Guide

47-6

OL-1047-01

Chapter 47

Configuring Phone Button Templates Adding Phone Button Templates

Guidelines for Creating Custom Templates
Use the following guidelines when creating custom phone button templates:

Be sure that phone users receive a quick reference card or getting started guide that describes the most basic features of the custom template. If you create a custom template to be used by employees in your company, ensure that it includes the following features and that you describe them on the quick reference card you create for your users:
– Cisco IP Phone 7960, 7940— Line (one or more). – Cisco IP Phone 7910—Forward all. – Cisco IP Phone 12 SP+—Line (one or more), hold, call park, and

forward all.
– Cisco IP Phone 30 VIP—Line (one or more), call park, and forward all. •

Consider the nature of each feature in order to determine how to configure your phone button template. You might want multiple buttons assigned to Speed Dial and Line. However, you will usually require only one of the other features described in Table 47-2. For each feature you select, you must also select the number of times you would like this feature to appear on the phone button template (the Feature Index). Most features appear only once. The feature index tells the user which line or speed dial corresponds to that button (for example, Line 1, Speed Dial 2, and so on).

Table 47-2 Phone Feature Description

Feature AEC

Description If you are configuring a template for the Cisco IP Phone 30VIP, you must include one occurrence of this feature and assign it to button 26. Provides Auto Echo Cancellation (AEC) to reduce the amount of feedback the called party hears when the calling party is using a speakerphone. Users should press the AEC button on a Cisco IP Phone 30SP+ when using speakerphone. This button does not need to be pressed when speakerphone is not in use. No configuration is necessary for this feature to work. Used in conjunction with a headset apparatus so the user can press a button on the headset apparatus to answer and release (disconnect) calls.
Cisco CallManager Administration Guide

Answer/release

OL-1047-01

47-7

Chapter 47 Adding Phone Button Templates

Configuring Phone Button Templates

Table 47-2 Phone Feature Description (continued)

Feature Auto answer Call park

Description If this feature is programmed on the template, activating this button causes the speakerphone to go off-hook automatically when an incoming call is received. Used in conjunction with a call park number or range so that when the user presses this button, the call is parked at a directory number for later retrieval. You must have a call park number or range configured in the system for this button to work, and you should provide that number or range to your users so they can dial into the number(s) to retrieve calls. Call Pickup allows users to pick up incoming calls within their own group. The appropriate call pickup group number is dialed automatically when a user activates this feature. When users press this button, they are initiating an Ad-Hoc conference and will be conferencing other participants in one at a time. Only the person initiating an Ad-Hoc conference needs a Conference button. An Ad-Hoc conference device must be configured in Cisco CallManager Administration for this button to work. Users press this button to forward all calls to the designated directory number. Users can designate the forward all in the User Web pages, or you can designate a forward all number for each user in Cisco CallManager Administration. Group Call Pickup allows users to pick up incoming calls within their own group or in other groups. Users must dial the appropriate call pickup group number when using this feature Users press this button to place an active call on hold. To retrieve a call on hold, users press the flashing line button or lift the handset and press the flashing line button for the call on hold. The caller on hold hears a tone every 10 seconds to indicate the hold status. No configuration is necessary for this feature to work. Users press this button to dial a number or to answer an incoming call. You must have added line numbers on the user phone for this button to work. When users press this button, they are initiating a Meet-Me conference and they expect other invited users to dial into the conference. Only the person initiating a Meet-Me conference needs a Meet-Me button. You must have configured a Meet-Me conference device in Cisco CallManager Administration for this button to work.

Call pickup

Conference

Forward all

Group call pickup

Hold

Line Meet-Me conference

Cisco CallManager Administration Guide

47-8

OL-1047-01

Chapter 47

Configuring Phone Button Templates Modifying Phone Button Templates

Table 47-2 Phone Feature Description (continued)

Feature Message waiting None Redial Speed-dial Transfer

Description Users press this button to connect to the voice messaging system. Use None to leave a button unassigned. Users press this button to redial the last number dialed on the Cisco IP Phone. No configuration is necessary for this feature to work. Users press this button to speed dial a specified number. Users can designate speed-dial numbers in the User Web pages. Users press this button to transfer an active call to another directory number. No configuration is necessary for this feature to work.
Related Topics
• • •

Understanding Default Phone Button Templates, page 47-1 Adding Phone Button Templates, page 47-5 Modifying Phone Button Templates, page 47-9

Modifying Phone Button Templates
You can make changes to the default templates included with Cisco CallManager or to custom templates you created. You can rename existing templates and modify them to create new ones, update custom templates to add or remove features, lines, or speed dials, and delete templates that are no longer being used.
Related Topics
• • •

Renaming a Phone Button Template, page 47-10 Deleting a Phone Button Template, page 47-11 Updating a Phone Button Template, page 47-12

Cisco CallManager Administration Guide OL-1047-01

47-9

Chapter 47 Modifying Phone Button Templates

Configuring Phone Button Templates

Renaming a Phone Button Template
Renaming a template does not affect the phones that use that template. All Cisco IP Phones that use this template continue to use this template once it is renamed. You can use this feature to create a copy of an existing template that you can modify.
Procedure

Follow these steps to rename a phone button template:
Step 1 Step 2

Open Cisco CallManager Administration. Select Device > Phone Button Template. A listing of current phone button templates appears on the left side of the screen.

Step 3

Click the phone button template you want to rename. The phone button template configuration page displays.

Step 4 Step 5

Enter the new name in the Template Name field. Click Update. The template re-displays with the new name.

Related Topics
• • •

Adding Phone Button Templates, page 47-5 Deleting a Phone Button Template, page 47-11 Updating a Phone Button Template, page 47-12

Cisco CallManager Administration Guide

47-10

OL-1047-01

Chapter 47

Configuring Phone Button Templates Modifying Phone Button Templates

Deleting a Phone Button Template
You can delete old or out-of-date phone templates that are not currently assigned to any of the phones in your system. You cannot delete a template that is assigned to one or more devices. All Cisco IP Phones using the template you want to delete must be reassigned to a different phone button template before you can delete the template.
Procedure
Step 1 Step 2

Open Cisco CallManager Administration. Select Device > Phone Button Template. A listing of current phone button templates appears on the left side of the screen.

Step 3

Click the phone button template you want to delete. The phone button template configuration page displays.

Step 4

Click Delete. A message displays verifying that you want to delete the template.

Step 5

Click OK to delete the template. A message appears verifying that the template was deleted.

Step 6

Click OK to continue.

Related Topics
• • •

Adding Phone Button Templates, page 47-5 Updating a Phone Button Template, page 47-12 Renaming a Phone Button Template, page 47-10

Cisco CallManager Administration Guide OL-1047-01

47-11

Chapter 47 Modifying Phone Button Templates

Configuring Phone Button Templates

Updating a Phone Button Template
You can update a phone button template to add or remove features, add or remove lines and speed dials, or assign features, lines, and speed dials to different buttons on the phone. If you update a phone template, be sure to inform affected users of the changes. Follow these instructions to update a phone button template.
Before You Begin

When you update a template, the change affects all phones that use the template.
Procedure

Follow these steps to update an existing phone button template:
Step 1 Step 2

Open Cisco CallManager Administration. Select Device > Phone Button Template. A listing of current phone button templates appears on the left side of the screen.

Step 3

Click the phone button template you want to update. The phone button template configuration page displays.

Step 4 Step 5

Enter the desired changes. Click Update. The template reappears with the changes assigned to it. You must restart devices using the template after updating it.

Step 6

Click Restart Devices to apply the updated phone button template.

Related Topics
• • •

Adding Phone Button Templates, page 47-5 Deleting a Phone Button Template, page 47-11 Renaming a Phone Button Template, page 47-10

Cisco CallManager Administration Guide

47-12

OL-1047-01

P

A R T

7

User Configuration

The following chapters explain how to configure user and directory information: • Chapter 48, “Adding a New User” • Chapter 49, “Searching the Global Directory”

.

and the name and directory number of that device must be specified in the user area. they must be associated with a device. page 48-2 Assigning Devices to a User. the devices function whether or not you complete this information.C H A P T E R 48 Adding a New User The User area in Cisco CallManager Administration allows the administrator to display and maintain information about Cisco CallManager users. Refer to the “Searching the Global Directory” section on page 49-1 for details on updating information on existing users. Cisco WebAttendant. This chapter includes the following topics: • • Adding a User. Generally. information that you enter here is also accessed by Directory Services. you must complete the information in the User area for all users and their directory numbers. and the User Web pages. For users to have Web access so they can change their speed dial and forward numbers on the Web. page 48-3 Cisco CallManager Administration Guide OL-1047-01 48-1 . completing user information is optional. However. If you want to provide these features to your users. and also for resources such as conference rooms or other areas with phones (this is useful for Cisco WebAttendant).

This directory also provides the MetaLink utility. and network-specific configuration information. Click User > Add a New User. which migrates the configuration information for Cisco CallManager from the relational database system where it has been stored to the embedded directory where it becomes available for use with Cisco JTAPI. Cisco CallManager Administration Guide 48-2 OL-1047-01 . Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. you have access to the Cisco CallManager directory. Cisco JTAPI uses the directory to determine which devices it has the privilege to control. Complete all the user fields in the User Information window. The directory stores user profiles. An asterisk (*) designates required fields.Chapter 48 How Cisco JTAPI uses the Directory Adding a New User How Cisco JTAPI uses the Directory After you install Cisco JTAPI. application logic. Using the Embedded Directory Installing the Cisco CallManager also installs an embedded directory on the Cisco CallManager machine. This section summarizes what you need to know about using the directory. such as the location of network resources and system administrator authentication. Adding a User The following procedure provides instructions on adding a user.

The manager name entered in the optional Manager field must already exist in the directory as a user. The User Device Assignment window consists of a device filter area and a list of available devices. Step 4 When you have completed the user information. page 49-1 Using Advanced User Search. Related Topics The following list contains additional information and procedures related to this section: • • • • How Cisco JTAPI uses the Directory. you can assign devices over which they will have control. they have the ability to control certain settings for that phone. can be controlled by applications that are identified as users. Or. page 48-2 Assigning Devices to a User. you can either Save your changes and add the user by clicking Insert. page 49-3 Assigning Devices to a User Once you have added a user. Other devices. if you want to associate devices to this user.Chapter 48 Adding a New User Assigning Devices to a User Note Cisco CallManager automatically generates the Auto Attendant Name Dialing field once all the other fields are completed. such as CTI ports. can be controlled by users. Cisco CallManager does not permit modifying the user ID once it is created. such as speed dial and call forwarding. Some devices. When users have control of a phone. page 48-3 Using Basic User Search. such as phones. continue with the “Assigning Devices to a User” procedure. Cisco CallManager Administration Guide OL-1047-01 48-3 . These areas are described in the this section.

The list displays in groups of twenty devices and can be navigated using the buttons at the bottom of the window. enter the criteria by which you wish to search using the following methods: – select the device name. or directory number. To assign devices to a user. For example. Previous. you must access the User Information window for that user. each line extension appears in the list. all available devices that match your criteria appear in the Available Devices list. to list all extensions that begin with ‘5’. you would select ‘Directory Number’ ‘begins with’ and then enter 5 in the text box. the devices previously assigned to that user appear in a group at the beginning of the device list. or directory number. Cisco CallManager Administration Guide 48-4 OL-1047-01 . Next. Refer to the “Using Basic User Search” section on page 49-1 for information on accessing information on existing users. – enter a text or number entry. If you are modifying the device assignment for an existing user. You can page through the device list by clicking First. or you can jump to a specific page by entering the page number in the page entry box and then clicking Page. description. To limit the list of available devices to a specific selection. and Last. Available Devices Once you have specified the search criteria to display devices. – select the comparison operator. description.Chapter 48 Assigning Devices to a User Adding a New User Available Device List Filters The device filter allows you to limit your list of devices by entering search criteria based on all or part of the device name. You can associate one or more devices to the user by selecting the checkbox next to that device. If a device has multiple extensions associated with it. You need to select only one line extension to select all the lines associated with that device.

or directory number the comparison operator a text or number entry Then. page 48-2 Using Basic User Search. click Select Devices. click Insert if you are assigning devices to a new user or Update if you are assigning devices to an existing user. You can assign one primary extension from the devices to which the user is assigned by clicking the radio button in the right column for that device. Step 4 Related Topics The following list contains additional information and procedures related to this section: • • • • How Cisco JTAPI uses the Directory. limit the list of available devices by enter the search criteria in the device filter area. page 49-3 Cisco CallManager Administration Guide OL-1047-01 48-5 . perform the following steps to assign devices: Step 1 Step 2 Click Associate Devices. Once you have completed the assignment. If you wish. you can click Personal Information to return to the User Information window. page 48-2 Adding a User. description. page 49-1 Using Advanced User Search.Chapter 48 Adding a New User Assigning Devices to a User Once the user’s User Information window displays. Or. Step 3 Select the check box of one or more devices you want to associate with the user. You should specify • • • the device name.

Chapter 48 Assigning Devices to a User Adding a New User Cisco CallManager Administration Guide 48-6 OL-1047-01 .

Its primary purpose is to maintain the associations of devices with users. as indicated in the following list: Cisco CallManager Administration Guide OL-1047-01 49-1 . page 49-1 Using Advanced User Search.C H A P T E R 49 Searching the Global Directory The Global Directory for Cisco CallManager (release 3. if you enter 'li’ in the search field. This chapter includes the following topics: • • Using Basic User Search. last name or user ID match that substring. You can access the Global Directory by using either a basic or an advanced user search. last name. the search results would include users whose first name. Refer the “Adding a New User” section on page 48-1 for details on adding and configuring a new user. and user ID fields for matches of any substring that you enter as search criteria. page 49-3 Using Basic User Search The Basic User search utility searches the first name. Cisco CallManager uses Lightweight Directory Access Protocol (LDAP) to interface with a directory that contains user information. This is an embedded directory supplied with Cisco CallManager. For example.0 and later) contains every user within a Cisco CallManager directory.

On the User Information window.Chapter 49 Using Basic User Search Searching the Global Directory Last name Johnson Ni Collins Lin Ivey First Name Charlie Liang Manny Mike Gabriel User ID cjohnson lni mcollins michaell Gabrieli If you enter two or more substrings separated by spaces. The page refreshes to the User Search page. refer to the “Assigning Devices to a User” section on page 48-3 for more information. The following procedure contains information about how to use the Global Directory Basic User Search engine. Related Topics The following list contains additional information and procedures related to this section: • • How Cisco JTAPI uses the Directory. To save changed information. page 48-2 Adding a User. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open Cisco CallManager Administration. Enter the first name. you can view or modify this user’s information. From the resulting list of matching names. or substring of the user for whom you are searching in the User Search field. page 48-2 Cisco CallManager Administration Guide 49-2 OL-1047-01 . the search will look for matches of any of the substrings in any of the three search fields. If you want to view or modify this user’s device assignment. user ID. click Update. last name. Click User > Global Directory. click on the desired name to get specific information on that user.

The following procedure contains information about how to use the Global Directory Advanced User Search engine. Cisco CallManager Administration Guide OL-1047-01 49-3 . and will look for matches where any of your specified criteria is true. Procedure Step 1 Step 2 Step 3 Open Cisco CallManager Administration. if you enter ‘Ling’ for first name and ‘Chu’ for last name. if you enter ‘john jerry’.Chapter 49 Searching the Global Directory Using Advanced User Search • • Assigning Devices to a User. Click User > Global Directory. the search will return the user named Ling Chu. Tips Use ORs with multiple entries in a single field. For example. the search will return all users whose first names are John or Jerry. For example. If you enter a substring in two or more search fields. page 49-3 Using Advanced User Search With the Advanced User Search utility. and ANDs across fields. page 48-3 Using Advanced User Search. the search will interpret the request with the OR relationship operator. you can enter search criteria using three search fields and built-in Boolean logic to perform more complex searches. The page refreshes to the Advanced User Search page. For example. Click Advanced Search. the search will interpret the request with the AND relationship operator and look for matches where both criteria are true. if you enter: First Name: john jane Last Name: jones smith UserID: jjones jsmith the search will be for (firstname='john’ OR 'jane’) AND lastname='jones’ OR 'smith’) AND (userid='jjones’ OR 'jsmith’). If you enter two or more names or substrings separated by spaces in any one field.

Related Topics The following list contains additional information and procedures related to this section: • • • • How Cisco JTAPI uses the Directory. page 48-2 Assigning Devices to a User. you can view or modify this user’s information. and user ID search criteria of the user for whom you are searching in the appropriate fields. page 49-1 Cisco CallManager Administration Guide 49-4 OL-1047-01 .Chapter 49 Using Advanced User Search Searching the Global Directory Step 4 Step 5 Enter the first name. Step 6 Step 7 Step 8 Once the desired user appears is the search list. click Update. page 48-2 Adding a User. last name. click on the user ID or name to display the Update User Information window. Click Clear to delete all entries from the fields. you can enter new search criteria and then click Search. refer to the “Assigning Devices to a User” section on page 48-3 for more information. Note Click Refine Search if you want to further limit your search. On the User Information window. or click Reset to populate the fields with the last search criteria. Click Search. When refining a search. page 48-3 Using Basic User Search. To save changed information. If you want to view or modify this user’s device assignment.

P A R T 8 Appendices The following appendices contain additional information related to Cisco CallManager and IP telephony: • Appendix A. “Cisco JTAPI Installation and Configuration” • Appendix C. “Creating Custom Cisco IP Phone Rings” . “Cisco TAPI Service Provider Installation and Configuration” • Appendix B.

.

page A-16 Installing the Cisco TAPI Service Provider The Cisco TAPI Service Provider software is installed either directly from the Cisco CallManager CD-ROM.C H A P T E R A Cisco TAPI Service Provider Installation and Configuration The following sections outline the installation of the Cisco TAPI Service Provider (TSP) and describe some of the issues you need to be aware of after installation. perform the following steps: Cisco CallManager Administration Guide OL-1047-01 -1 . or by browsing to the Cisco CallManager server and installing the Cisco TSP from the Applications > Install Plugins menu. page A-14 Setting up Client-Server Configuration. page A-9 Installing the Wave Driver. page A-10 Verifying the Cisco TAPI Service Provider Installation. To install the Cisco TSP from the Cisco CallManager CD-ROM. The topics include: • • • • • • • Installing the Cisco TAPI Service Provider. page A-1 Activating the Cisco TAPI Service Provider. page A-4 Uninstalling the Cisco TAPI Service Provider. page A-3 Configuring the Cisco TAPI Service Provider.

“http://callmanager/main. Cisco CallManager Administration Guide -2 OL-1047-01 . Step 2 Step 3 Step 4 Step 5 Note Once the installation is complete. Press Enter. Double-click on My Computer Double-click on the CD-ROM drive. On the Cisco TSP-Welcome window. Click Cisco Telephony Service Provider. Click Application > Install Plugins. perform the following steps: Procedure Step 1 Open a Web browser and enter the URL for Cisco CallManager Administration in the URL address text box (for example.asp”). Double-click on the Installs folder. you must install the Cisco Wave drivers and then restart the computer. Follow the online instructions. Refer to “Installing the Wave Driver” section on page A-10 for more information.Chapter Installing the Cisco TAPI Service Provider Cisco TAPI Service Provider Installation and Configuration Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Insert the Cisco CallManager CD-ROM.exe. Double-click Cisco TSP. click Continue. Follow the online instructions. To install the Cisco TSP from the Cisco CallManager.

perform the following steps: Procedure for Windows 2000 Step 1 Step 2 Step 3 Open the Control Panel. Cisco CallManager Administration Guide OL-1047-01 -3 . Double-click Telephony. Click Add. Procedure for Windows NT. Double-click Phone and Modem Options. The Cisco TSP will be loaded by TAPI as required. Step 7 At this point. To manually add the Cisco TSP to the list of telephony drivers. it is added to the set of active TAPI service providers.Chapter Cisco TAPI Service Provider Installation and Configuration Activating the Cisco TAPI Service Provider Activating the Cisco TAPI Service Provider When the Cisco TSP is installed. Windows 98. you can do so from this window. it can be manually added to this set. If it has been removed or if some problem has occurred. Click the Telephony Drivers tab. On the Add Provider dialog box. The Cisco IP PBX Service Provider is now included in the provider list on the Phone and Modem Options window. On the Phone and Modem Options dialog box. you can either configure the Cisco TSP or click Close to complete the setup. select Cisco IP-PBX Service Provider. Note If the Cisco TSP is either not there or you removed it previously and want to add it now. and Windows 95 Step 1 Step 2 Step 3 Open the Control Panel. click the Advanced tab. Step 4 Step 5 Step 6 Click Add.

select Cisco IP-PBX Service Provider. Click Add. Configuring the Cisco TAPI Service Provider You configure the Cisco TSP by setting parameters on the Cisco IP-PBS Service Provider configuration window. On the Add Driver dialog box. The provider list on the Phone and Modem Options window now includes the Cisco IP PBX Service Provider. Cisco CallManager Administration Guide -4 OL-1047-01 . you can either configure the Cisco TSP or click Close to complete the setup. you can do so from this window. Step 4 Step 5 Step 6 Step 7 At this point.Chapter Configuring the Cisco TAPI Service Provider Cisco TAPI Service Provider Installation and Configuration Note If the Cisco TSP is either not there or you removed it previously and want to add it now. Click Add. as illustrated in Figure 0-1.

Chapter Cisco TAPI Service Provider Installation and Configuration Configuring the Cisco TAPI Service Provider Figure 0-1 Cisco IP-PBX Service Provider Configuration Cisco CallManager Administration Guide OL-1047-01 -5 .

Silence Detection If you use silence detection. However. you must specify the energy level at which the wave driver declares that silence is in effect. if you enter “5” here. If some phones or gateways on your network do not perform silence suppression. This number is the maximum number of lines that can be simultaneously opened using both LINEMEDIAMODE_AUTOMATEDVOICE and LINEMEDIAMODE_INTERACTIVEVOICE. If the checkbox is checked (default).Chapter Configuring the Cisco TAPI Service Provider Cisco TAPI Service Provider Installation and Configuration Table 0-1 contains a list of the fields that must be set and their descriptions: Table 0-1 Cisco IP-PBX Service Provider Configuration Fields Field group Automated Voice Calls Description The number of Cisco wave devices you are using determines the number of possible automated voice lines (the default is five). Because all devices on the network suppress silence and stop sending packets. check the option to Enumerate only lines that support automated voice so that the Cisco TSP sees only lines associated with a CTI port device. the system ignores this value. and the default is 200. the wave driver looks for the absence of audio stream RTP packets. the wave driver must analyze the content of the media stream and at some threshold. this checkbox informs the wave driver which method to use to detect silence on lines that support automated voice calls using the Cisco Wave Driver. If you change this number. you also need to remove and then reinstall any Cisco wave devices that you installed. For example. this provides a very efficient method for the wave driver to detect silence. If all phones and gateways perform silence suppression. If you are not developing a third-party call control application. We recommend that you use one line per device. You need to create the same number of CTI port devices in the Cisco CallManager. This value of the 16-bit linear PCM energy level has a range of zero to 32767. declare that silence is in effect. Cisco CallManager Administration Guide -6 OL-1047-01 . if some phones or gateways do not perform silence suppression. you need to create five CTI port devices in Cisco CallManager. This method is CPU-intensive but handles media streams from any type of device.

If the CallManager is on a different machine. no notification goes to the TSP about the new device. The Cisco TSP returns these lines to the application when the Cisco TSP issues lineInitializeEx. The TSP uses the CallManager directory to retrieve devices for a user. If a device is added to a user's control list from the CallManager user administration pages.Chapter Cisco TAPI Service Provider Installation and Configuration Configuring the Cisco TAPI Service Provider Table 0-1 Cisco IP-PBX Service Provider Configuration Fields (continued) Field group Security Description Users need to enter their user name and password in the Cisco IP PBX Service Provider configuration dialog box to access devices. click the Local CallManager radio button. encrypts them. click the CallManager IP Address radio button and enter the IP address or click the CallManager Name radio button and enter the host name. The Synchronous Message Timeout designates the time the TSP should wait to receive a response to a synchronous message. select the Poll for New Devices checkbox at the bottom of the configuration dialog box. it reads the user name and password and sends them in the ProviderOpen request to the Cisco CallManager. To enable dynamic device updates. The value displays in milliseconds. the TSP polls the directory for new devices if this feature is enabled. If the application attempts to open an unregistered device. and stores them in the registry. When the Cisco TSP initializes. CallManager Location If the TSP is on the same machine as the CallManager. The Cisco CallManager creates each user’s user name and password in the administration pages. If dynamic device updates are required. Devices and lines are assigned to that user. and the default is 15000 ms. Message Timeout New Device Detection Cisco CallManager Administration Guide OL-1047-01 -7 . The application is responsible for retrying the lineOpen until it succeeds. the Cisco TSP responds to the lineOpen request with the error LINEERR_RESOURCEUNAVAIL. Only one user name and password can be active at a time. The list of devices that the Cisco TSP receives from the Cisco CallManager is the entire list of devices the user is allowed to access regardless of whether the device is registered.

Select Cisco IP-PBX Service Provider. Step 5 Step 6 Enter values for the fields on this dialog box. Double-click Phone and Modem Options. The system displays the Cisco IP PBX Service Provider dialog box. Click Configure. you must restart the telephony service before an application can run and connect with its devices. Refer to Table 0-1 for field information: Click OK to save changes. and Windows 95 Step 1 Step 2 Step 3 Step 4 Open the Control Panel. Note After the TSP is configured. The system displays the Cisco IP PBX Service Provider dialog box. Click Configure.Chapter Configuring the Cisco TAPI Service Provider Cisco TAPI Service Provider Installation and Configuration Perform the following steps to configure Cisco TSP: Procedure for Windows 2000 Step 1 Step 2 Step 3 Step 4 Open the Control Panel. Step 5 Step 6 Enter values for the fields on this dialog box. Double-click Telephony. Refer to Table 0-1 for field information: Click OK to save changes. Procedure for Windows NT. Windows 98. Cisco CallManager Administration Guide -8 OL-1047-01 . Select Cisco IP-PBX Service Provider.

Double-click the Telephony icon. Click Remove to delete the Cisco TSP from the list. Procedure for Windows NT. Click the Advanced tab. perform the following steps: Procedure for Windows 2000 Step 1 Step 2 Step 3 Step 4 Step 5 Open the Control Panel. Highlight the Cisco IP-PBX Service provider.Chapter Cisco TAPI Service Provider Installation and Configuration Uninstalling the Cisco TAPI Service Provider Note After configuring the TSP. Double-click the Phone and Modem icon. Click Remove to delete the Cisco TSP from the list. To make these changes. Click the Advanced tab. Uninstalling the Cisco TAPI Service Provider This process uninstalls Cisco TAPI Service Provider and removes it from the provider list. Windows 98. and Windows 95 Step 1 Step 2 Step 3 Step 4 Step 5 Open the Control Panel. Highlight the Cisco IP-PBX Service provider. the telephony service must be restarted before an application can run and connect with its devices. Cisco CallManager Administration Guide OL-1047-01 -9 .

Click Add a New Device and click Next. I want to select the hardware from a list. Select Sound. The Cisco TAPI Wave Driver displays on the screen.INF and click Open. Click No.) Caution Due to a restriction in Windows NT. perform the following steps. (Do this even if you are performing your own media termination. Click Next. Click Browse and change to the Wave Drivers folder in the folder where the Cisco TSP is installed. Click OK in the Install From Disk window. Cisco CallManager Administration Guide -10 OL-1047-01 . video and game controllers and click Next. Windows 98 and Windows 95 do not support it. Double-click Add/Remove Hardware. The procedures in this section for installing and uninstalling the Cisco wave driver on Windows NT include instructions on how to prevent existing wave drivers from being overwritten or removed. Click Have Disk. Click Next. Click Next. Select OEMSETUP.Chapter Installing the Wave Driver Cisco TAPI Service Provider Installation and Configuration Installing the Wave Driver Cisco wave driver is available for Windows 2000 and Windows NT only. Click Add/Troubleshoot a Device and click Next. To install the Cisco wave driver. the software may overwrite or remove existing wave drivers from the system when you install or remove the Cisco wave driver on a Windows NT system. You should install Cisco wave driver if you plan to use first-party call control. Procedure for Windows 2000 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Open the Control Panel.

Click Browse and change to the Wave Drivers folder in the folder where the Cisco TSP is installed. open the Control Panel. perform the following steps: a. but do not restart the system when prompted. c. Click OK. Cisco CallManager Administration Guide OL-1047-01 -11 .Chapter Cisco TAPI Service Provider Installation and Configuration Installing the Wave Driver Step 14 Step 15 Step 16 Click Yes. Click Yes to restart. To do this. a. Follow the on-screen instruction. Click OK. Click Finish. Click Unlisted or Updated Driver. Click Next. The file is given a . perform the following steps. After the registry information is saved. Select the Drivers32 key located in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\ CurrentVersion e. To do this. f. Double-click Multimedia. d. Click Save.reg extension. Enter a filename and select the location to save. Click OK. Click Add. Click Start > Run. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Select Registry > Export Registry File. Examine the contents of the registry to verify the new driver was installed and the old drivers still exist. b. Procedure for Windows NT Step 1 Before you add the Cisco wave driver. you must save the wave driver information from the registry in a separate file. Click Start > Run. Enter regedit in the text box.

select Edit > Modify. c. select Edit > New > String Value and enter a value name. Close the registry by selecting Registry > Exit.Chapter Uninstalling the Wave Driver Cisco TAPI Service Provider Installation and Configuration b. wave3. Cisco CallManager Administration Guide -12 OL-1047-01 . e. b. You can compare this registry list to the contents of the . For each missing wave value. Select Cisco TAPI Wave Driver and click Next. add the appropriate waveX string values for any missing wave values that should be installed on the system. and so on. a. Uninstalling the Wave Driver To remove the Cisco wave driver. Select Uninstall/Unplug a device and click Next. c.dll” displays in the data column. If necessary. Enter regedit in the text box. Double-click Add/Remove Hardware. wave2. Click OK. Verify that the previously existing wave values appear in the data column for wave1.reg file in a text editor and viewing it and the registry window side-by-side. d. Click Next.reg file you saved in Step 1 by opening the . Select the Drivers32 key located in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\ CurrentVersion Make sure the driver “avaudio32. Step 11 Restart the computer. perform the following steps: Procedure for Windows 2000 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Open the Control Panel. and click OK. Select Uninstall a device and click Next. Then. enter the value data. This is the Cisco wave driver. d.

open the Control Panel. Enter a filename and select the location to save. Click the Devices tab. c. Examine the contents of the registry to verify the Cisco wave driver was removed and the old drivers still exist. Click Start > Run. Procedure for Windows NT Step 1 Before you add the Cisco wave driver.reg extension. perform the following steps. Cisco CallManager Administration Guide OL-1047-01 -13 . Click Finish.Chapter Cisco TAPI Service Provider Installation and Configuration Uninstalling the Wave Driver Step 7 Step 8 Select Yes. Click the ‘+’ symbol next to Audio Devices to view all the audio devices. After the registry information is saved. Click OK. b. Click Finish. Click Save. b. In the left window. The file is given a . Click Remove. f. you must save the wave driver information from the registry in a separate file. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Select Registry > Export Registry File. d. To do this. Double-click Multimedia. select the Drivers32 key located in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\ CurrentVersion e. Click Start > Run. a. c. I want to uninstall this device and click Next. Do not restart the system. Click Audio for Cisco Sound System. Enter regedit in the text box. To do this. Enter regedit in the text box. perform the following steps: a. Click OK.

a. add the appropriate waveX string values for any missing wave values that should be installed on the system.exe Procedure For Windows 2000 Step 1 Step 2 Open the Dialer application by locating it in Windows Explorer and double-clicking it. e. Click Edit > Options. d. Verify that the previously existing wave values appear in the data column for wave1. wave2. In the left window. select the Drivers32 key located in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\ CurrentVersion Make sure the Cisco wave driver “avaudio32. b. the dialer application is located in C:\Program Files\Windows NT\dialer. Cisco CallManager Administration Guide -14 OL-1047-01 . You can compare this registry list to the contents of the .Chapter Verifying the Cisco TAPI Service Provider Installation Cisco TAPI Service Provider Installation and Configuration d. Step 10 Restart the computer. For Windows NT and Windows 2000. For each missing wave value. the dialer application is located in C:\Windows\dialer. Then select Edit > Modify. c. If necessary. wave3. Verifying the Cisco TAPI Service Provider Installation You can use the Microsoft Windows Phone Dialer Application to verify that the Cisco TSP is operational. enter the value data.reg file in a text editor and viewing it and the registry window side-by-side.reg file you saved in Step 1 by opening the .dll” does not appear in the data column.exe For windows 95 and Windows 98. Close the registry by selecting Registry > Exit. and click OK. select Edit > New > String Value and enter a value name. and so on.

Test the network link between the Cisco TSP and the Cisco CallManager by using the ping command to check connectivity. Step 2 Step 3 Step 4 Select one of the lines from the Line drop down menu. select Phone Call in the Dial as box. If there are no lines in the Line drop-down list box. and Windows 95 Step 1 Open the Dialer application by locating it in Windows Explorer and double-clicking it: A dialog box appears requesting the line and address that you want to use. check the following items: • • • Make sure the Cisco TSP was configured properly. Click OK. Cisco CallManager Administration Guide OL-1047-01 -15 . select one of the Cisco Lines in the Phone Calls drop down menu. Procedure for Windows NT. In the Line Used For area. then there might be a problem between the Cisco TSP and the Cisco CallManager. Make sure Address is set to Address 0. If you encounter problems during this procedure. Make sure the Cisco CallManager server is functioning. and then click Place Call. Windows 98. Enter a number to dial. you have verified that the Cisco TSP is operational on the machine where the Cisco TSP is installed. or if no lines appear in the line drop-down list on the dialer application. If the call was successful. Click OK.Chapter Cisco TAPI Service Provider Installation and Configuration Verifying the Cisco TAPI Service Provider Installation Step 3 Step 4 Step 5 Step 6 Step 7 Select Phone as the Preferred Line for Calling. Enter a number to dial. Click Dial.

refer to the Microsoft Windows Help feature.Chapter Setting up Client-Server Configuration Cisco TAPI Service Provider Installation and Configuration Setting up Client-Server Configuration For information on setting up a client-server configuration in Windows 2000. refer to Microsoft’s White Papers. Cisco CallManager Administration Guide -16 OL-1047-01 . For information on client-server configuration in Windows NT.

or on both. • • • • Installing the Cisco JTAPI Software. on a separate machine. The Cisco JTAPI classes are installed wherever JTAPI applications will run. page B-2 Verifying the Installation. whether on Cisco CallManager. page B-14 Cisco CallManager Administration Guide OL-1047-01 -1 . Installation requires 5 MB of local disk space. page B-4 Configuring Cisco JTAPI Tracing. Installation of the Cisco JTAPI implementation is necessary before Cisco JTAPI applications will function correctly.C H A P T E R B Cisco JTAPI Installation and Configuration Cisco Java Telephony API (JTAPI) implementation consists of Java classes that reside on all client machines running Cisco JTAPI applications. page B-4 Administering User Information for JTAPI and TAPI Applications. This section discusses the software installation and configuration required to ready the Cisco JTAPI environment for programming and running applications.

Follow the instructions in the pop-up windows.asp where: Name is the name or IP address of the Cisco CallManager Click Application > Install Plugins. Save the file on your desktop or run it from the download site. is C:\WINNT\Java\lib.exe) in Program Files\JTAPITools JTAPI sample applications(makecall.Chapter Installing the Cisco JTAPI Software Installing the Cisco JTAPI Software Perform the steps below to install the CiscoJTAPI software: Procedure Step 1 Step 2 Step 3 Step 4 Log in to the computer where you want to install the Cisco JTAPI client software. Installed files The cisco JTAPI installation utility installs the following items on the local disk drive: • • • • JTAPI java classes in %SystemRoot%\java\lib JTAPI Preferences (jtprefs. muzak. jtrace) in Program Files\JTAPITools JTAPI documentation in Program Files\JTAPITools Cisco CallManager Administration Guide -2 OL-1047-01 . for example. Click the Cisco JTAPI link. Step 5 Step 6 Step 7 Step 8 Note Install Cisco JTAPI software on the default drive as directed by the installation software. The default directory. Open a web browser. when Windows NT is installed in C:\WINNT. Go to the Cisco CallManager administration pages: http://Name/CCMAdmin/main. Close all Windows programs.

Cisco JTAPI will also run on Sun JDK1. all you need is a Java 1.1. you already have a compatible version of the Microsoft Virtual Machine.3190 or later is required. Windows 98.com/java. To use JTPREFS (application to set Cisco JTAPI tracing parameters) and the sample applications bundled with Cisco JTAPI. however.microsoft. On all other Microsoft platforms such as Windows 95. Cisco CallManager Administration Guide OL-1047-01 -3 . You can download the latest version of the Microsoft Java Virtual Machine from http://www. verify the current version of the Microsoft Virtual Machine by running the command "jview /?" and noting the version printed at the top of the console. If you are installing Cisco JTAPI on a Windows 2000 Workstation or Server.Chapter Installing the Cisco JTAPI Software Note To run many JTAPI applications.1-compatible environment such as the Sun JDK 1.2.x or Microsoft Virtual Machine (bundled with Internet Explorer 4. and Windows NT.0 and higher). Microsoft Java Virtual Machine 5.00.

trace destinations. navigate to the directory where you installed Cisco JTAPI Tools. Perform the following steps: Procedure Step 1 From the Windows NT command line. Refer to the “Adding a New User” section for details. and CallManager names. phone1 and phone2 are directory numbers of IP phones or virtual phones that are controlled by the user according to the user configuration. Step 2 Configuring Cisco JTAPI Tracing You use the Cisco JTAPI tracing preferences application (JTPREFS.Chapter Verifying the Installation Verifying the Installation When you perform the procedure in this section. this directory is Program Files\JTAPITools. login and password are the user ID and password that you configured in the Cisco CallManager User Configuration page. The Cisco JTAPI Preferences utility is installed by default in the directory Program Files\JTAPITools. Cisco CallManager Administration Guide -4 OL-1047-01 . Execute the following command: Jview makecall <server name> <login> <password> 1000 <phone1> <phone2> where server name is the hostname or IP address of the Cisco CallManager (for example. select Start > Programs > Cisco JTAPI. a call is placed in order to test the Cisco TJAPI installation and configuration. By default.EXE) to configure trace levels. CTISERVER). To open Cisco JTAPI preferences.

page B-8 Cisco CallManager. The JTAPI version number is shown in the window title. page B-11 Other JTAPI Preferences Settings. page B-12 JTAPI Preferences on non-Microsoft environments. page B-13 Figure 0-1 illustrates the trace level window of the Cisco JTAPI preferences application. The following topics are discussed: • • • • • Debug Levels.Chapter Trace Levels Trace Levels This section describes how to use the Cisco JTAPI preferences application. page B-7 Log Destination. Cisco CallManager Administration Guide OL-1047-01 -5 .

highest level debugging events Cisco CallManager Administration Guide -6 OL-1047-01 .low level warning events INFORMATIONAL .status events DEBUG .Chapter Trace Levels Figure 0-1 Cisco JTAPI Trace Levels The Trace Level tab allows you to enable or disable the following JTAPI trace levels: • • • WARNING .

as described below: Cisco CallManager Administration Guide OL-1047-01 -7 . Figure 0-2 Cisco JTAPI Debug Levels When the DEBUG trace level is enabled.Chapter Trace Levels Debug Levels Figure 0-2 illustrates the debug level window. you may enable or disable additional debugging levels in the Debug Levels tab.

miscellaneous low-level debug trace Log Destination Figure 0-3 illustrates the log destination window.internal CTICLIENT implementation trace PROTOCOL_DEBUGGING .to trace JTAPI methods and events JTAPI_IMPLDEBUGGING .full CTI protocol decoding MISC_DEBUGGING .internal JTAPI implementation trace CTI_DEBUGGING .to trace Cisco CallManager events that are sent to the JTAPI implementation CTIIMPL_DEBUGGING . Cisco CallManager Administration Guide -8 OL-1047-01 .Chapter Trace Levels • • • • • • JTAPI_DEBUGGING .

tracing is sent to the standard output or console (command) window. Log destination fields are described as follows: Use Java Console When this option is enabled. Cisco CallManager Administration Guide OL-1047-01 -9 .Chapter Trace Levels Figure 0-3 Cisco JTAPI Log Destination The Log Destination tab allows you to configure how JTAPI will create traces and how they will be stored.

as shown in the figure the trace files would rotate between jtapiTrace01. Log files are sized in increments of one megabyte. Directory Name Base Allows you to specify a folder name where the trace files will be contained. returning to the first log file after filling the last. When the path is not specified. will cause the trace files to be placed in a new folder sequential to the last folder written.log. Use the Same Directory This option allows you to specify if the same folder name should be used for each instance of an application. CiscoJtapi02. In this case. the default is the application's path. Cisco JTAPI detects the last folder present in the trace path and automatically increments the numeric index. Cisco JTAPI rotates through the log files in numerical order.log. jtapiTrace02. Use Rotating Log Files This option allows you to direct the traces to a specific path and folder in the system. For example. each application instance. whether successive or simultaneous. When enabled.Chapter Trace Levels Use Syslog When this option is enabled. There can be no fewer than two log files and no more than ninety-nine. Cisco CallManager Administration Guide -10 OL-1047-01 .log and so on. Syslog collector is the service by which traces are collected and directed to the CiscoWorks2000 server. traces are sent to a UDP port as specified in the Syslog Collector and Port number fields. Path Allows you to specify the path name where the trace files will be written to.log. File Name Base and File Name Extension These values are used to make up the trace file names with a numerical index appended to the file base name to indicate the order in which the files are created. JTAPI will trace the log files to the same directory. successive instances of a JTAPI application will restart the log files starting at index 01. If the 'File Name Base' and 'File Name Extension' were left blank Cisco JTAPI will pick the trace files names as CiscoJtapi01. When disabled.log and jtapiTrace10.

Chapter Trace Levels Cisco CallManager Figure 0-4 illustrates the Cisco CallManager window Figure 0-4 Cisco JTAPI CallManager This tab allows you to define a list of Cisco CallManagers that a JTAPI application can present the user for optional Cisco CallManager connectivity. Cisco CallManager Administration Guide OL-1047-01 -11 .

use the format below: <Parameter>=<value> For example: RouteSelectTimeout=5000 The following table lists the additional parameters. These parameters and their values must be edited manually in the jtapi. These parameters are low-level and may be needed only for troubleshooting and debugging purposes. their functions. and default values.ini file.Chapter Trace Levels Other JTAPI Preferences Settings There are a number of parameters that are not configurable through the JTAPI Preferences application.ini file located by default in %Sysroot%\java\lib. Parameter RouteSelectTimeout Function Specifies the amount in milliseconds for JTAPI to wait for a response to a Route event Instructs the implementation to do periodic measurements of its internal queues Default 5000 PeriodicWakeupEnabled 0 PeriodicWakeupInterval QueueStatsEnabled Specifies the frequency in milliseconds to 50 do periodic measurements Instructs the implementation to trace queue statistics 0 1 DeviceListUpdateEnabled Instructs the implementation to update the list of provider controlled devices periodically DeviceListUpdateInterval Specifies the frequency in milliseconds to 30 do device list updates Cisco CallManager Administration Guide -12 OL-1047-01 . When editing parameters in the jtapi. you would not need to modify these unless instructed by support personnel. Typically.

Chapter Trace Levels Parameter AlwaysQueryCallInfo Function Instructs the implementation to always query the call information for tracing purposes Default 1 CtiRequestTimeout Specifies the time in milliseconds that 30 JTAPI will wait for a response from a CTI request JTAPI Preferences on non-Microsoft environments For non-Microsoft environments.JTAPIIMPL_DEBUGGING.PROTOCOL_DEBUGGING. CTIIMPL_DEBUGGING. a jtapi.MISC_DEBUGGING JTAPI_DEBUGGING=1 JTAPIIMPL_DEBUGGING=1 CTI_DEBUGGING=1 CTIIMPL_DEBUGGING=1 PROTOCOL_DEBUGGING=0 MISC_DEBUGGING=0 UseSystemDotOut=0 UseSyslog=0 SyslogCollector= SyslogCollectorUDPPort= UseTraceFile=1 TraceFileSize=1048576 NumTraceFiles=10 UseSameDirectory=1 Directory= TracePath=d:/public/traces FileNameBase=jtapiTrace FileNameExtension=log CallManagers=ctiserver.ini file must be created manually and placed in the CLASSPATH. ctiserver2 Cisco CallManager Administration Guide OL-1047-01 -13 .INFORMATIONAL. The following are the parameter names with sample values: Traces=WARNING.DEBUG WARNING=0 INFORMATIONAL=0 DEBUG=1 Debugging=JTAPI_DEBUGGING.CTI_DEBUGGING.

The list of devices assigned to the user represent the phones that the user needs to control from the application (e.Chapter Administering User Information for JTAPI and TAPI Applications Administering User Information for JTAPI and TAPI Applications JTAPI and TAPI applications require that users be administered in the directory and be given privilege to control one or more devices. make calls.g. Cisco CallManager Administration Guide -14 OL-1047-01 . Follow the procedures for adding a user and assigning devices to a user in the “Adding a New User” section before using a JTAPI or TAPI application. answer calls).

The PCM files.xml File Format.xml) that describes the ring list options available at your site are installed in the TFTP directory on each Cisco CallManager server. page C-3 Note The procedure described here only applies to creating custom phone rings for the Cisco IP Phone 7940 and 7960 models. This appendix describes how you can customize the phone ring types available at your site by creating your own PCM files and editing the RingList. The following topics are covered: • • • Creating a Custom Phone Ring.C H A P T E R C Creating Custom Cisco IP Phone Rings Cisco IP Phones ship with two default ring types that are implemented in hardware: Chirp1 and Chirp2. page C-2 PCM File Requirements for Custom Ring Types. Cisco CallManager also provides a default set of additional phone ring sounds that are implemented in software as pulse code modulation (PCM) files.xml file. Cisco CallManager Administration Guide OL-1047-01 -1 . along with an XML file (named RingList. page C-2 RingList.

xml file defines an XML object that contains a list of phone ring types. Step 2 Step 3 Step 4 RingList. Place the new PCM files you created in the C:\ Program Files\Cisco\TFTPPath directory on the Cisco TFTP server for each Cisco CallManager in your cluster. Refer to the “RingList.Chapter Creating a Custom Phone Ring Creating a Custom Phone Ring Use the following procedure to create a custom phone ring.xml file. Save your modifications and close the RingList. Procedure Step 1 Create a PCM file for each custom ring (one ring per file). along with a sample RingList. This file is located in the C:\ Program Files\Cisco\TFTPPath directory of the Cisco TFTP server for each Cisco CallManager. Use an ASCII editor to edit the RingList.xml file. The PCM files must comply with the format guidelines listed in the “PCM File Requirements for Custom Ring Types” section on page C-3.xml File Format” section on page C-2 for information about how to format this file. The CiscoIPPhoneRingList XML object uses the following simple tag set to describe the information: <CiscoIPPhoneRingList> <Ring> <DisplayName/> <FileName/> </Ring> </CiscoIPPhoneRingList> Cisco CallManager Administration Guide -2 OL-1047-01 . Each ring type contains a pointer to the PCM file used for that ring type and the text that will be displayed on the Ring Type menu on a Cisco IP Phone for that ring.xml File Format The RingList.xml file.

FileName specifies the name of the PCM file for the custom ring to associate with DisplayName. DisplayName defines the name of the custom ring for the associated PCM file that will be displayed on the Ring Type menu of the Cisco IP Phone.raw</FileName> </Ring> </CiscoIPPhoneRingList> PCM File Requirements for Custom Ring Types The PCM files for the rings must meet the following requirements for proper playback on Cisco IP Phones: • • • • • • • • Raw PCM (no header) 8000 samples per second 8 bits per sample uLaw compression Maximum ring size — 16080 samples Minimum ring size — 240 samples Number of samples in the ring must be evenly divisible by 240 Ring should start and end at the zero crossing You can use any standard audio editing packages that supports these file format requirements to create PCM files for custom phone rings. that are required for each phone ring type.xml file that defines two phone ring types is shown below: <CiscoIPPhoneRingList> <Ring> <DisplayName>Analog Synth 1</DisplayName> <FileName>Analog1. Cisco CallManager Administration Guide OL-1047-01 -3 .Chapter PCM File Requirements for Custom Ring Types In the above definition: • • • • Ring contains two fields.raw</FileName> </Ring> <Ring> <DisplayName>Analog Synth 2</DisplayName> <FileName>Analog2. The DisplayName and FileName fields must not exceed 25 characters. A sample RingList. DisplayName and FileName. Up to 50 rings can be listed.

Chapter PCM File Requirements for Custom Ring Types Cisco CallManager Administration Guide -4 OL-1047-01 .

19-1 analog gateways 45-3 attendant console 8-1 administration 8-3 Cisco WebAttendant 8-1 hunt groups and pilot points 8-6 audio quality 5-1 auto-registration 4-1 disabling 4-6 enabling 4-2 reusing auto-registration numbers 4-7 C call admission control 5-1 calling search spaces 22-1 adding 22-1 copying 22-3 deleting 22-4 updating 22-3 call processing. 16-1 allocation of 5-1 calculations for admission control 19-4 usage per call 16-1 batch phone operations 46-1 Bulk Administration Tool (BAT) 46-1 Cisco CallManager Administration Guide OL-1047-01 5 .I N D E X A admission control 5-1. configuring 13-1 server configuration 11-1 starting and stopping 20-1 updating 12-5 Cisco CallManager Group 3-2 Cisco Catalyst 6000 gateways 45-4 DSP services card 45-5 E1/T1 line card 45-5 Cisco IP Phones 46-1 B bandwidth 5-1. distributed 2-1 Cisco Access gateways 45-3 analog 45-3 digital 45-4 Cisco CallManager 11-1 adding 12-1 configuring 12-1 deleting 12-6 groups.

description 46-3 adding 46-7 auto-registration 4-1 batch operations 46-1 configuring 46-5 configuring phone features 46-16 deleting 46-11 device loads for 7-6 directory numbers 46-18 finding and listing 46-15 MAC address. phone button 47-1 understanding 46-2 updating 46-13 Cisco IP Phone Services 41-1 Cisco Messaging Interface 30-1 adding service 30-5 commonly changed service parameter fields 30-2 configuring trace parameters 30-10 deleting service 30-6 Cisco TAPI Service Provider A-1 activating A-3 configuring A-4 installation and configuration A-1 Cisco CallManager Administration Guide installing A-1 installing the wave driver A-10. configuring 43-11 MWI On/Off numbers. displaying 46-6 resetting 46-12 templates. setting 43-8 port wizard 43-3 resetting ports 43-17 understanding 43-1 updating ports 43-18 Cisco uOne Port wizard 43-3 adding a new uOne server and ports 43-3 adding ports 43-6 deleting ports 43-7 Cisco VG200 gateway 45-6 configuring FXO ports 45-38 configuring FXS ports 45-35 closest-match routing 6-11 clusters 2-1 6 OL-1047-01 . A-12 setting up the client-server configuration A-16 uninstalling A-9 verifying the installation A-14 Cisco Telephony Interface (CTI) CTI ports 46-5 Cisco Telephony Interface (CTI) route point 42-1 Cisco uOne 43-1 adding ports 43-12 configuring CallManager for uOne 43-1 copying ports 43-19 deleting ports 43-16 MWI device. description 46-4 30 VIP. description 46-4 7940. description 46-4 7910.Index 12 SP+. description 46-3 7960.

Index compared to groups 3-1 described 2-1 CMI (Cisco Messaging Interface) 30-1 CMLocal Date/Time Group 14-1 communication protocols. gateway 45-1 compression of data 16-1 configuring call park 39-1 adding a number 39-2 assigning directory numbers to a group 40-5 configuring 40-2 configuring call park number 40-2 deleting a group number 40-4 deleting a number 39-4 updating a group number 40-3 updating a number 39-3 configuring call pickup described 40-1 configuring Cisco TFTP 31-1 configuring command line parameters 31-5 configuring trace parameters 31-9 deleting command line parameters 31-7 deleting service 31-4 inserting service 31-2 configuring conference bridges 33-1 adding a hardware device 33-8 adding a Meet-Me number pattern 33-14 adding a software device 33-6 Ad-Hoc 33-4 deleting a conference device 33-11 deleting a Meet-Me number pattern 33-17 Meet-Me 33-5 two types of conferences 33-3 understanding conference devices 33-2 updating a conference device 33-10 updating a Meet-Me number pattern 33-15 updating conference bridge parameters 33-12 configuring gateways 45-1 configuring media termination point 34-1 adding 34-5 avoiding call failure/user alert 34-4 call hold 34-2 call park 34-2 call transfer 34-2 CiscoIpVoiceMediaStreamingApp 34-1 conferencing 34-2 deleting 34-8 IpVoiceMediaStreamer 34-1 planning MTP configuration 34-3 transcoders 34-1 updating 34-7 configuring route filters 23-1 adding 23-5 adding clauses 23-9 copying 23-7 deleting 23-11 removing clauses 23-10 updating 23-7 configuring route groups 24-1 Cisco CallManager Administration Guide OL-1047-01 7 .

Index adding 24-2 adding devices 24-3 deleting 24-7 removing devices 24-5 understanding 24-2 updating 24-6 configuring route lists 25-1 adding 25-6 adding route groups 25-8 changing the order of route groups 25-11 deleting 25-12 removing route groups 25-10 understanding called party transformation settings 25-4 understanding calling party transformation settings 25-2 configuring service parameters 35-1 adding 35-5 adding new service 35-3 deleting 35-9 deleting a service 35-4 updating 35-7 configuring trace 36-1 adding a configuration 36-10 alarm conditions 36-2 components 36-7 deleting a configuration 36-13 deleting a service 36-14 error messages 36-2 event level 36-6 event log 36-7 levels 36-2 options 36-2 output debug string 36-7 recommended settings 36-9 services 36-3 system log 36-7 time 36-3 updating a configuration 36-12 user mask 36-3 configuring transcoder 37-1 configuring 37-3 copying 37-5 deleting 37-6 MTPs 37-1 updating 37-4 Control Center 38-1 starting and stopping services 38-2 using 20-2 CTI ports 46-5 CTI route point 42-1 adding 42-2 deleting 42-4 finding and listing 42-5 modifying 42-3 resetting 42-6 custom phone button templates adding 47-5 guidelines for creating 47-7 Cisco CallManager Administration Guide 8 OL-1047-01 .

Index D data compression 16-1 Date/Time Group 14-1 default settings for devices 15-1 device defaults 15-1 updating 15-2 device loads 7-6 understanding 7-6 updating 7-7 verifying 7-9 device pool 17-1 adding 17-1 deleting 17-4 updating 17-3 devices 15-1 Cisco uOne ports 43-1 defining common characteristics 17-1 device defaults 15-1 device loads 7-6 gatekeeper 44-1 gateways 45-1 phones 46-1 understanding device support 7-1 DHCP 7-2 understanding 7-2 digital gateways 45-4 directory numbers 46-18 adding 46-19 auto-registration 4-1 configuring 46-18 deleting 46-23 searching 45-46 updating 46-24 discard digits Instructions 6-12 distributed system. configuring 2-3 Domain Name System (DNS) 11-1 E E1 gateways 45-4 enterprise parameters 18-1 external phone number mask 4-4 external route plan wizard 28-1 confirming the external route plan 28-10 creating an external route plan 28-2 deleting an external route plan 28-11 entering location information 28-5 finishing the external route plan 28-11 generating the external route plan 28-9 providing gateway information 28-8 providing tenant information 28-4 selecting gateways 28-6 setting the routing options 28-2 understanding 6-25 Cisco CallManager Administration Guide OL-1047-01 9 .

Index F FXO 45-38 configuring ports on the Cisco VG200 45-38 Foreign Exchange Office 45-2 FXS 45-35 configuring ports on the Cisco VG200 45-35 Foreign Exchange Station 45-2 configuring 45-35 Cisco VG200 ports 45-35 loop start ports 45-31 ports 45-27 deleting 45-42 digital 45-4 E1 45-4 finding and listing 45-44 H. configuring ports on MGCP gateway 45-38 group call pickup adding a group number 40-2 assigning directory numbers to a group 40-5 G G.323 45-6 ISDN 45-10 MGCP 45-21 modifying 45-41 PRI 45-10 resetting 45-42 searching 45-45 station 45-3 T1 45-4 trunk 45-3 updating 45-43 Global Directory Advanced User Search 49-3 Basic User Search 49-1 Global Directory 49-1 Lightweight Directory Access Protocol (LDAP) 49-1 ground start.729 16-1 gatekeeper 44-1 adding 44-1 configuring 44-1 deleting 44-6 modifying 44-7 restarting or resetting 44-6 gateways 45-1 adding 45-7 analog ports 45-27 digital 45-9 H.711 16-1 G.323 45-23 analog 45-3 Cisco Catalyst 6000 45-4 Cisco VG200 45-6 communication protocols 45-1 Cisco CallManager Administration Guide 10 OL-1047-01 .723 16-1 G.

32-5 adding members 32-5 configuring 32-5 deleting members 32-9 described 8-6 updating 32-9 viewing 32-9 LDAP directory 9-1 Cisco CallManager directory 9-1 using the embedded directory 9-2 LDAP parameters 18-1 Lightweight Directory Access Protocol (LDAP) 9-1 locations 19-1 adding 19-5 defined 19-1 deleting 19-7 interaction with regions 19-3 updating 19-7 used in admission control 5-1 loop start configuring gateway ports 45-31 configuring on MGCP gateway 45-40 Cisco CallManager Administration Guide OL-1047-01 11 .Index deleting a group number 40-4 updating a group number 40-3 groups. gateway configuration 45-10 K keypad templates 47-1 L H H.323 45-2 adding gateways 45-23 gateway 45-6 H.225 45-2 H.323 clients 46-5 hub-and-spoke topology 5-1 hunt groups 8-6. Date/Time 14-1 I introduction 1-1 IP address 11-1 ISDN. CallManager adding 13-2 compared to clusters 3-1 components of 3-2 configuring 13-1 deleting 13-6 updating 13-4 groups.

default templates 47-3 7960. default template 47-3 30 VIP.Index M MAC address 46-6 phone 46-6 server 11-2 Media Access Control (MAC) address 11-2 phone 46-6 server 11-2 messaging Cisco Messaging Interface (CMI) 30-1 Cisco uOne 43-1 MGCP 45-21 adding gateways 45-21 configuring ground start ports 45-38 configuring loop start ports 45-40 Media Gateway Control Protocol 45-2 MWI (message waiting indicator) 43-8 MWI device for uOne 43-11 MWI On/Off numbers 43-8 P parameters enterprise 18-1 LDAP 18-1 partitions 21-1 adding 21-1 deleting 21-2 phone button templates 47-1 12-Series. default templates 47-3 7940. default template 47-4 30 SP+. default template 47-2 adding 47-5 deleting 47-11 guidelines for creating 47-7 renaming 47-10 understanding 47-1 updating 47-12 phone features 46-16 call forward 46-17 call park 46-17 call pickup 46-18 call waiting 46-17 configuring 46-16 phones 46-1 adding 46-7 N Network Interface Card (NIC) 11-2 O overview 1-1 Cisco CallManager Administration Guide 12 OL-1047-01 . default template 47-4 7910.

configuring 46-16 finding and listing 46-15 MAC address.Index auto-registration 4-1 batch operations 46-1 Cisco IP Phone 12 SP+ 46-4 Cisco IP Phone 30 VIP 46-4 Cisco IP Phone 7900 Family 46-2 Cisco IP Phone 7910 46-4 Cisco IP Phone 7940 46-3 Cisco IP Phone 7960 46-3 Cisco IP Phone Services 41-1 configuring 46-5 deleting 46-11 device loads for 7-6 directory numbers 46-18 directory numbers. gateway configuration 45-10 Q quality of sound 5-1 R redundancy 3-1 configuring 3-5 types of 3-1 with distributed call processing 3-3 regions 16-1 configuring 16-1 interaction with locations 19-3 used with admission control 19-3 resetting Cisco CallManager 20-1 restarting Cisco CallManager 20-1 route filters understanding tags 23-2 Route Pattern considerations for using 6-24 understanding 6-24 route patterns 26-1 adding 26-1 copying 26-5 deleting 26-6 updating 26-4 Cisco CallManager Administration Guide OL-1047-01 13 . displaying 46-6 phone button templates 47-1 resetting 46-12 understanding Cisco IP Phones 46-2 updating 46-13 pilot points 8-6. configuring 46-18 features. 32-2 adding 32-2 configuring 32-2 deleting 32-4 described 8-6 updating 32-4 viewing 32-4 plug-ins 8-10 Cisco WebAttendant client 8-10 PRI.

Index route pattern wildcards and special characters 6-7 copying 27-5 deleting 27-6 understanding 27-1 updating 27-4 trunk gateways 45-3 S server configuration 11-1 services 38-2 Control Center 20-2. 48-3 user information 48-1 Cisco CallManager Administration Guide 14 OL-1047-01 . Cisco 43-1 port wizard 43-3 user information adding a user 48-2. 48-3 associate devices 48-2. 38-2 Telephony Call Dispatcher (TCD) 8-9 shared line appearances 46-25 Skinny Gateway Protocol 45-1 sound quality 5-1 starting and stopping 38-2 station gateways 45-3 U understanding distributed call processing 2-1 understanding route plans route plan overview 6-1 understanding 6-1 Understanding Service Parameters 10-1 Cisco CallManager service parameters 10-2 T T1 gateways 45-4 TCD (Telephony Call Dispatcher) 8-9 service parameters 32-18 starting 32-20 TFTP understanding 7-2 TFTP server 7-3 accessing 7-3 identifying 7-4 time zones 14-1 translation patterns 27-1 adding 27-2 Cisco database layer service parameters 10-29 Cisco IP voice media streaming service parameters 10-28 Cisco messaging interface service parameters 10-22 Cisco telephony call dispatcher service parameters 10-30 Cisco TFTP service parameters 10-20 uOne.

8-16 users.Index using route plan report 29-1 viewing all records 29-2 viewing in a file 29-3 Telephony Call Dispatcher (TCD) 8-9 tips and troubleshooting 8-14. configuring 32-14 client. installing 32-13 client installation 8-10 client requirements 8-10 configuring CallManager for 8-3 described 8-1 directory database 8-11 hunt groups. Cisco 8-1. configuring 32-5 performance monitors 8-14 phone guidelines 8-4 pilot points. configuring 32-2 pilot points and hunt groups 8-6 redundancy 8-13 TCD service parameters 32-18 Cisco CallManager Administration Guide OL-1047-01 15 . 32-1 administration 8-3 client. adding 32-10 wausers 8-11 wizards 43-3 Cisco uOne Port wizard 43-3 V voice gateways 45-1 voice mail 43-1 Cisco uOne 43-1 voice quality 5-1 W WebAttendant.

Index Cisco CallManager Administration Guide 16 OL-1047-01 .

Sign up to vote on this title
UsefulNot useful