 Feedback
|
Table Of Contents
Release Notes for Cisco CallManager Release 3.3(5)
Determining the Software Version
Compatibility Matrix and Supported Upgrades
Requirement for Installation of Java Virtual Machine
Operating System Installation Guidelines
Changes to Type-Specific Information in the Gateway Configuration Settings
Forced Authorization Codes and Client Matter Codes
Cisco IP Telephony Backup and Restore System (BARS)
Extension Mobility Enhancements
Changes to Support MSJVM Removal
Router-based Conference Capability
Conference Bridge Types for Router Based Conferences
Calling Search Space Enhancements
Default Trace Level Changed for Cisco Database Layer Monitor Service
New Service Parameter to Enable Music On Hold Duplex Streaming
Application Error During an Upgrade
Adding Cisco CallManager Servers
Using the Ping Command During Installation
Locale Installer for Cisco CallManager Release 3.3(5)
MLA for Cisco CallManager 3.3(5)
Cisco CallManager Renamed After Restarting Services
VirusScan on Cisco CallManager Servers
Supported Characters in the Directory
Cisco CallManager Integration with Corporate Directories
Installing IPMA Assistant Console on Microsoft Windows XP
Cisco VG248 Analog Phone Gateway (VG248) Support
Settings Access on Cisco IP Phone 7940/7960
Cisco CallManager Attendant Console Support
Changing the Attendant Console Password
Using Cisco CallManager Attendant Console with Windows XP SP2
Upgrading Cisco CallManager Extension Mobility
Adding Cisco CallManager Servers as Members of a Windows Domain
Resolved Caveats for Cisco CallManager - Release 3.3(5)
Open Caveats for Cisco CallManager - Release 3.3(5)
Microsoft Outlook Support with Cisco WebDialer
Mandatory Parameter for Cisco WebDialer API Reference
Date/Time Configuration Changes
Using Valid Characters in Cisco CallManager User IDs
Cisco CallManager Dialed Number Analyzer Private Phrase Requirement
Cisco CallManager Dialed Number Analyzer Service Startup Type
Supported Number of Alphanumeric Characters in the AAR Group Name Field
Default Value for the Extension Mobility Alphanumeric Userid Service Parameter
Updated Directory Path for Music On Hold Drop Directory
Default Value for Display IE and Redirecting IE Delivery Fields
Support for Overlap Route Patterns
Cisco CallManager Attendant Console
Adding and Deleting Users by Using Cisco CallManager Administration
Associating H.323 Devices to Users
Changes to Gateway Support with Cisco CallManager
Specifying Options that Display on the User Options Window
Meet-Me Conference Limitations
New Service Parameter for Cisco CallManager Extension Mobility
Defining the Quality of Service (QoS) Values
Quality Report Tool Configuration Settings
Exporting and Importing Phones with More Than One User
Device Profile Default Configuration
Subscribing Services to a Device Profile Default
User Settings in Cisco CallManager Administration
Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration
Reinstalling Dialed Number Analyzer after a Cisco CallManager Upgrade
Dependency Between Cisco CallManager and CTI Manager
Using Wildcard Characters in Device Searches
Removing a Subscriber Server from Cisco CallManager
Using Script Files to Remove a Subscriber Server from Cisco CallManager
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco CallManager Release 3.3(5)
April 6, 2005
These release notes describe the new features and caveats for Cisco CallManager release 3.3(5).
Before you install Cisco CallManager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
For a list of the open and resolved caveats for Cisco CallManager release 3.3(5), see "Resolved Caveats for Cisco CallManager - Release 3.3(5)" section and "Open Caveats for Cisco CallManager - Release 3.3(5)" section. Updates for these release notes occur with every maintenance and major release.
To access the documentation suite for voice products, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/
You can access the latest software upgrades and release notes for Cisco CallManager 3.3 on Cisco Connection Online (CCO) at
http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml
Contents
These release notes discuss the following topics:
•
Compatibility Matrix and Supported Upgrades
•
•
•
Introduction
Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Make sure that you install and configure Cisco CallManager release 3.3 on a Cisco Media Convergence Server (MCS).
You may also install Cisco CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
Caution
Access the correct Cisco-approved server configuration for IBM server or HP server at
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html
For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 3.3.
Determining the Software Version
To determine the software version of Cisco CallManager 3.3, open Cisco CallManager Administration; then, click Details on Cisco CallManager Administration. The following information displays:
•
•
•
Compatibility Matrix and Supported Upgrades
You can find the minimum versions with which Cisco CallManager release 3.3(5) has been tested and which previous release of Cisco CallManager has upgrade support at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Note
Related Documentation
Refer to the Cisco CallManager Document Guide for a list of documents that are related to Cisco CallManager release 3.3 at
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/doc_gd
Along with the documents that are listed in the Cisco CallManager Document Guide, the following list specifies other related documents for Cisco CallManager:
•
•
•
•
•
•
•
•
•
New and Changed Information
This following sections describe new features and changes that are pertinent to this release of Cisco CallManager. The sections include configuration tips for the administrator, information about users, and where to find more information.
•
•
•
•
•
•
•
•
•
•
•
Requirement for Installation of Java Virtual Machine
The Microsoft Java Virtual Machine (MSJVM) technology allows Java applications to run on Microsoft Windows-based computers. Some versions of Microsoft Internet Explorer (a component of the Windows operating systems) included MSJVM, but Microsoft has since discontinued distribution of MSJVM in its software and announced end-of-life support for the product.
MSJVM was installed by default in all client workstation versions of the current Windows operating systems, except for the following versions:
•
•
Note
•
•
•
Tip
JRE Installation
As part of the Cisco CallManager installation, the system provides the Sun JRE client software in a zip file that is installed on the Cisco CallManager server.
Note
Tip
To install the JRE software on the client PC, follow these steps:
Procedure
Step 1
The following shows an example of the zip file name:
J2RE_Client_1.4.2_05.zip
Note
Step 2
Step 3
Step 4
The following shows an example of the installation executable file name:
j2re-1_4_2_04-windows-i586-p.exe
Note
The JRE software installs in the C:\Program Files\Cisco\Java\JRE directory.
Note
For detailed information about installing and upgrading Cisco CallManager release 3.3(5), refer to Installing Cisco CallManager Release 3.3(5) and Upgrading Cisco CallManager 3.3(5).
Operating System Installation Guidelines
Ensure that Cisco IP Telephony operating system version 2000.2.6 with the latest service release 2000.2-6-sr5 (or later) is installed before you upgrade to Cisco CallManager release 3.3(5).
Changes to Type-Specific Information in the Gateway Configuration Settings
After you install Cisco CallManager 3.3(5), the system leaves the following check boxes in the Cisco CallManager Administration Gateway Configuration window unchecked by default for some gateways:
•
•
•
This setup affects the following gateways:
•
•
•
•
•
If you upgrade your server to Cisco CallManager 3.3(5) and you did not uncheck the check boxes before the upgrade, the check boxes remain checked after the upgrade. If you add an affected gateway after the upgrade, the check box remains unchecked.
To determine when you should check the check box(es), refer to the guidelines that are specified in the Cisco CallManager Administration Guide.
Where to Find More Information
•
Forced Authorization Codes and Client Matter Codes
Forced Authorization Code (FAC) and Client Matter Code (CMC) allow you to manage call access and accounting. CMC assists with call accounting and billing for billable clients, while FACs regulate the types of calls that certain users can place.
Client Matter Codes force the user to enter a code to specify that the call relates to a specific client matter. You can assign CMC to customers, students, or other populations for call accounting and billing purposes. The Forced Authorization Code feature forces the user to enter a valid authorization code before the call completes.
The CMC and FAC features require that you make changes to route patterns and perform configuration tasks for CMC and FAC in Cisco CallManager Administration (Choose Feature > Client Matter Code or Feature > Forced Authorization Code).
You can use BAT to insert, update, and delete CMC and FAC and CDR Analysis and Reporting (CAR) to run reports that provide call details for authorization code names, authorization levels, and CMCs.
Caution
Note
How This Feature Affects the User
When enabled, these features force the user to enter a valid account code or authorization code before the call completes. A distinctive tone prompts the user.
You should tell affected end users how to recognize the audio prompts and the codes that users need to enter as well as the consequences or symptoms that are associated with failing to enter a valid code.
Currently, the end-user documentation does not contain any instructions about how to use these features.
Where to Find More Information
•
•
•
•
Cisco WebDialer
Cisco WebDialer allows Cisco IP Phone users to make telephone calls by using web and desktop applications. When you enable your company directory search page by using Cisco WebDialer, a user can make calls by clicking a hyperlinked telephone number.
In Cisco CallManager 3.3(3), users obtain Cisco WebDialer as a download from www.cisco.com. In Cisco CallManager 3.3(5), Cisco WebDialer exists as a service in Cisco CallManager Serviceability.
How This Feature Affects the User
Some current versions of model-specific user guides do not mention Cisco WebDialer features, even though the phone supports these features and the feature might be accessible to end users. Refer users to Customizing Your Cisco IP Phone on the Web for instructions about using these features.
Where to Find More Information
•
Cisco IP Telephony Backup and Restore System (BARS)
Cisco CallManager 3.3(5) uses the Cisco IP Telephony Backup and Restore System (BARS) for backup and restore operations, including backing up data, restoring data, and restoring servers. This application, which you can use for manual or scheduled backups, supports compatible versions of Cisco CallManager, Cisco Emergency Responder, Cisco Customer Response Applications/Solutions (CRA/CRS), and Cisco CDR Analysis and Reporting (CAR).
Where to Find More Information
•
•
New and Updated Phone Support
The following information describes new and updated phone support for this Cisco CallManager release. The applicable documentation may not provide the following information:
•
•
•
•
•
Where to Find More Information
•
•
•
•
•
Extension Mobility Enhancements
Cisco CallManager 3.3(5) includes the following enhancements to Extension Mobility.
IP Phone Support
Cisco CallManager 3.3(5) extends Cisco CallManager Extension Mobility functionality to Cisco IP Phones 7905, 7912, 7970, and Cisco IP Communicator.
How This Feature Affects the User
Some current versions of model-specific user guides do not mention Cisco Extension Mobility, even though the phone supports these features and the features may be accessible to end users. Refer users to Customizing Your Cisco IP Phone on the Web for instructions about using these features.
Changes to Support MSJVM Removal
Cisco CallManager 3.3(5) includes the following changes to Extension Mobility in support of the MSJVM dependency removal. (See the "Requirement for Installation of Java Virtual Machine" section for more information about MSJVM.)
•
•
•
•
http://<Cisco Extension Mobility server>/manager/list
where:
Cisco Extension Mobility server specifies the IP address of the server that has the Cisco Extension Mobility service running on it.
Note
•
•
To disable Extension Mobility, you must deactivate the Cisco Extension Mobility service from the Cisco CallManager Serviceability Service Activation window; then, restart the Cisco Tomcat Web Service for the changes to take effect.
•
This parameter defined the template to use when a user logged into a Cisco IP Phone 7940; the system no longer requires this parameter for logins.
Note
Where to Find More Information
For additional information, refer to the Cisco CallManager Extension Mobility chapter in the Cisco CallManager Features and Services Guide.
Cisco Security Agent
Cisco CallManager 3.3(5) supports Cisco Security Agent with specific Cisco CallManager profiles. Cisco Security Agent provides host intrusion detection capability on Cisco CallManager servers.
Where to Find More Information
•
Image Authentication
Image authentication prevents tampering with the binary image; that is, the firmware load, prior to loading it on the phone. Tampering with the image causes the phone to fail the authentication process and reject the image. Image authentication occurs through signed binary files that are automatically installed with this version of Cisco CallManager. Likewise, firmware updates that you download from cisco.com also provide signed binary images.
Cisco IP Phone models 7970, 7960, 7940, 7912, 7910, 7905G, and 7902G support image authentication with Cisco CallManager release 3.3(5).
Router-based Conference Capability
The Cisco 1700, Cisco 2600, Cisco 2600XM, Cisco 2800, Cisco 3600, Cisco 3700, and Cisco 3800 series voice gateway routers provide conferencing capabilities for Cisco CallManager. These routers provide the following features:
•
•
Note
Router-enabled conferencing provides the capability to support voice conferences in hardware. Digital Signaling Processors (DSPs) convert multiple Voice over IP media streams into time-division multiplexing (TDM) streams that are mixed into a single conference call stream. The DSPs support both Meet-me and ad hoc conferences by Cisco CallManager.
The Cisco routers that support conferencing provide support for the following codecs:
•
•
•
Conference Bridge Types for Router Based Conferences
Cisco IOS Conferencing and Transcoding for Voice Gateway Routers
The Cisco IOS Conferencing and Transcoding for Voice Gateway Routers feature uses the NM-HDV or NM-HDV-FARM network modules. This feature enables G.711, G.729, G.729a, G.729b, G.729ab participants to join in a single conference and it provides support for up to six parties in a single conference call.
•
•
Cisco IOS Enhanced Conferencing and Transcoding for Voice Gateway Routers
The Cisco IOS Enhanced Conferencing and Transcoding for Voice Gateway Routers feature uses the onboard Cisco Packet Voice/Fax Digital Signal Processor Modules (PVDM2) on the Cisco 2800 and 3800 series voice gateway routers or the NM-HD or NM-HDV2 network modules.
This feature enables G.711 a/u-law, G.729, G.729a, G.729b, G.729ab, GSM FR, and GSM EFR participants to join in a single conference and it provides support for up to eight parties in a single call.
•
•
Tip
For more information about Cisco IOS Conferencing and Transcoding for Voice Gateway Routers or Cisco IOS Enhanced Conferencing and Transcoding for Voice Gateway Routers, refer to the IOS documentation that you received with your router.
International Dial Plan
Cisco CallManager International Dial Plan provides country-specific dialing functionality for countries outside the North American Numbering Plan (NANP). The international dial plan includes route pattern wildcards, special characters, calling party transformation settings, and called party transformation settings that non-NANP dial plans use. It also describes the Discard Digit Instructions (DDIs) and tags that dial plans of specific countries use. Cisco CallManager currently supports international dial plans for Japan, the Netherlands, and Portugal.
Where to Find More Information
•
Calling Search Space Enhancements
Cisco CallManager 3.3(5) provides database enhancements for Calling Search Spaces, so you can make updates to Calling Search Spaces during regular business hours. Cisco removed the Restart Devices button from the Calling Search Space Configuration window in Cisco CallManager Administration because you do not need to restart the associated devices after you update a calling search space. To save your updates, remember to click Update after you make changes.
Default Trace Level Changed for Cisco Database Layer Monitor Service
In Cisco CallManager 3.3(5), the default trace level for the Cisco Database Layer Monitor service changed from Error to Significant.
If you change the default trace level before you upgrade the cluster to Cisco CallManager 3.3(5), your setting does not change after the upgrade. If you do not change the default trace level before the upgrade, the setting changes to Significant.
New Service Parameter to Enable Music On Hold Duplex Streaming
Cisco CallManager 3.3(5) introduces a new service parameter, Duplex Streaming Enabled, for music on hold (MOH). This service parameter determines whether MOH uses duplex (two-way) or simplex (one-way) audio streams.
You can configure one of the following values for this service parameter:
•
•
Set the Duplex Streaming Enabled service parameter by using Cisco CallManager Administration to access the service parameters (Service > Service Parameters). Choose the server where the Cisco CallManager application resides. On the Cisco CallManager Service Parameters Configuration window, scroll down to the Cluserwide Parameters (Service) section to configure the Duplex Streaming Enabled parameter.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg49352.
For detailed information about configuring service parameters, refer to the Cisco CallManager Administration Guide.
Important Notes
The following section contains important information that may not have been available in the initial release of documentation for Cisco CallManager release 3.3(5), and includes the following topics:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Application Error During an Upgrade
When you upgrade to Cisco CallManager 3.3(5), you may encounter the following error message:
InsertCDR.exe - Application Error, The instruction at "0x10250fe7" referenced memory at "0x0000000." The memory could not be read. Click OK to terminate program.
You should click OK to exit the dialog box and to continue with the installation of Cisco CallManager 3.3(5). Clicking OK does not terminate your installation; in fact, clicking OK will allow you to successfully upgrade your Cisco CallManager system.
Adding Cisco CallManager Servers
In Cisco CallManager Administration, make sure that you add each server only once on the Server Configuration window (System > Server). If you add a server by using the host name and add the same server by using the IP address, Cisco CallManager cannot accurately determine component versions for the server after a Cisco CallManager upgrade. If you have two entries in Cisco CallManager Administration for the same server, delete one of the entries before you upgrade.
Using the Ping Command During Installation
The publisher database server serves as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server.
If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server before you begin the installation. The installation process necessitates this connection, so the publisher database server can be copied to the local drive on the subscriber server.
To make sure that a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. Use only a hostname (for example, hostname.cisco.com) with the ping command. If the ping command is not successful, you must exit the installation program, fix the problem, and begin the installation process again.
Locale Installer for Cisco CallManager Release 3.3(5)
For optimal performance, be sure that you use Cisco IP Telephony Locale Installer version 3.3(5) with Cisco CallManager release 3.3(5).
Note
Refer to the readme file that is posted with the Cisco IP Telephony Locale Installer software on http://www.cisco.com for the complete list of supported languages. For a list of available locale installers that are supported for use with specific versions of Cisco CallManager, go to the following URL: http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/locale-installer.shtml.
Tip
Note
MLA for Cisco CallManager 3.3(5)
To maintain full multilevel administration access functionality in Cisco CallManager 3.3(5), you must use Cisco CallManager Multilevel Administration Access, release 1.2(4). If you do not install Cisco MLA 1.2(4), you will only be able to log in to Cisco CallManager Administration with the administrator password.
Cisco CallManager Renamed After Restarting Services
If you deactivate the Cisco CallManager service in Cisco CallManager Serviceability, the Cisco CallManager where you deactivated the service no longer exists in the database. Hence, you cannot choose the Cisco CallManager for configuration operations in Cisco CallManager Administration because it will not display in the graphical user interface (GUI).
If you reactivate the Cisco CallManager service on the Cisco CallManager, the database creates a Cisco CallManager and adds a "CM_" prefix to the server name or IP address; for example, if you reactivate the Cisco CallManager service on a server with an IP address of 172.19.140.180, CM_172.19.140.180 displays in Cisco CallManager Administration. You can choose the new Cisco CallManager in Cisco CallManager Administration.
VirusScan on Cisco CallManager Servers
If you are using Microsoft Windows OS version 2000.2.4SR5 or 2000.2.5 with McAfee Netshield 2000 or McAfee VirusScan Enterprise Edition, you may encounter a problem authenticating to Cisco CallManager Administration or accessing some areas of Cisco CallManager Administration. Cisco CallManager displays an "HTTP Error 500-12 Application Restarting" error message.
To resolve this problem, you will need to upgrade McAfee Netshield and McAfee VirusScan to use VirusScan Engine Version 4.2.60 or later. You can obtain the latest Virus Scan updates from the Network Associates website.
Region Configuration
The Region Configuration window displays an Items per page drop-down list box that allows you to list 10, 20, 50, 100, or All configured regions. If you choose to display 100 or more regions, Cisco CallManager may experience performance degradation.
QSIG Support
Cisco offers support for Q.SIG basic call and ID services for selected MGCP-controlled gateways and for selected PBX. ID services support depends upon the PBX type. You can find a list of compatible gateways for which Cisco CallManager release 3.3(5) has been tested at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm
Supported Characters in the Directory
Caution
Cisco CallManager only supports ISO-Latin1 and ASCII characters in the User area of Cisco CallManager Administration.
After you download the locale installer, you can display field names in the User area of Cisco CallManager Administration in your chosen language. However, Cisco CallManager only supports ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127 in the fields and in all user accounts and passwords that are needed to access these windows. If a user enters data that is not in the allowed character range, a dialog box displays and states that the user must enter data by using only ISO-Latin1 characters and non-ISO-Latin1 characters in the range 0-127.
CDR Analysis and Reporting (CAR) supports all ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127.
Cisco CallManager Integration with Corporate Directories
If you have integrated Cisco CallManager with Active Directory or Netscape Directory, you must run the Cisco Customer Directory Configuration Plugin that is packaged with this release on all the Cisco CallManager servers in the cluster, beginning with the publisher. You must complete this step after you successfully upgrade your Cisco CallManager server to release 3.3(5).
To ensure that Cisco CallManager can install the latest schema and new configuration information in the directory, you must enter a user who has the rights to update the schema in the Directory Administrator DN.
For more information about installing the Cisco Customer Directory Configuration Plugin, refer to Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager Release 3.3.
Installing IPMA Assistant Console on Microsoft Windows XP
The installation of Assistant Console for IPMA service fails with Internet Explorer 6 on Windows XP because it does not include Microsoft Java Virtual Machine (JVM). (This does not cause a problem if the system has Microsoft Windows XP Service Pack 1 installed.) If the system does not have Microsoft Windows XP Service Pack 1, you can use the Netscape browser or install the Sun Java Virtual Machine plug-in for Internet Explorer from http://java.sun.com/getjava/download.html.
After installing the Sun JVM plugin, continue the IPMA assistant console installation from http://<server>/ma/Install/IPMAConsoleInstallJar.jsp where <server> represents the IP address of the Cisco CallManager server.
Cisco VG248 Analog Phone Gateway (VG248) Support
When using the VG248 with Cisco CallManager 3.3, add the device as a Cisco VG248 gateway and configure each port as VGC phone model. This consolidates the 48 analog or SMDI ports onto a single device. However, you still must configure these ports in the VG248 interface, and you should not enter any values in the Port Specific fields of the Phone Configuration window. Because these fields are not operational when you are using the VG248 1.2(1) or earlier software, you must configure these settings locally on the VG248.
For details about using the VG248 with this and other Cisco CallManager versions, see the "Configuring VG248 Ports Using Cisco CallManager" in the Cisco VG248 Analog Phone Gateway Software Configuration Guide for details:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/apg/vg248/v1_2/sw_confg/index.htm.
To view the latest compatibility information about the VG248 and Cisco CallManager, access the Cisco VG248 Analog Phone Gateway Version Release Notes on www.cisco.com at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/apg/vg248/v1_2/rel_note/vg248rn6.htm.
Changing User IDs
Cisco CallManager does not support changing an existing user ID in the directory. Some applications, such as Cisco IPMA and Extension Mobility, may not function properly if you change the user ID.
Settings Access on Cisco IP Phone 7940/7960
Users cannot access any button settings when you disable Settings Access for an individual Cisco IP Phone. This includes the settings to change the ring type, volume level, and contrast level.
Cisco CallManager Attendant Console Support
Cisco CallManager Administration 3.3(5) provides the Cisco CallManager Attendant Console 1.2(1) plug-in, although Cisco CallManager Administration Guide 3.3(5) and Cisco CallManager System Guide 3.3(5) support Cisco CallManager Attendant Console 1.1(3). To obtain documentation for attendant console 1.2(1), click the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/attendnt/call_att/index.htm.
Changing the Attendant Console Password
After you create the ac user, as described in the Cisco CallManager Features and Services Guide, you can change the ac user password, if necessary, by using the following procedure.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
The utility generates an encrypted password.
Step 7
Step 8
Step 9
Step 10
Refer to the Cisco CallManager Attendant Console documentation for additional information.
Using Cisco CallManager Attendant Console with Windows XP SP2
When you start Cisco CallManager Attendant Console for the first time after you install Windows XP SP2, a dialog box displays that indicates that Windows Firewall has blocked some features of the ACClient application. To create an exception in the Windows Firewall, so you can continue using Cisco CallManager Attendant Console, click Unblock. The operating system configures the exception automatically.
If you do not click Unblock when you open Cisco CallManager Attendant Console for the first time after you install Windows XP SP2, use the following procedure to create an exception, so you can continue using Cisco CallManager Attendant Console:
Procedure
Step 1
The Windows Firewall dialog box displays.
Step 2
Step 3
The Add a Program dialog box displays.
Step 4
The ACClient displays in the application list on the Exceptions tab of the Windows Firewall dialog box.
Step 5
The Edit a Program dialog box displays.
Step 6
The Change Scope dialog box displays.
Step 7
Step 8
Upgrading Cisco CallManager Extension Mobility
If you run Cisco CallManager Extension Mobility and Cisco CallManager 3.1 or 3.2 before the upgrade, you must perform additional configuration tasks after the upgrade, so Cisco CallManager Extension Mobility runs as expected. For more information about configuration tasks, refer to the Cisco CallManager Extension Mobility upgrade section of the Cisco CallManager Features and Services Guide for 3.3.
Adding Cisco CallManager Servers as Members of a Windows Domain
Cisco does not recommend adding Cisco CallManager servers as members of a Microsoft Windows domain. However, if your system architecture is dependent on servers joining a Windows domain, then you must disable the Network Time Protocol (NTP) software that is installed by Cisco CallManager when you add the server as a member of a domain and use Microsoft time service. You must disable the NTP service on every server in your cluster.
Note
Note
Follow this procedure to disable the Cisco-installed NTP software on a server:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Caution
When you have completed your upgrade and you are adding the server to the Windows domain, you must disable the Cisco-installed NTP services once again.
If you are joining the server to a Microsoft Windows 4.0 domain, you must also perform an additional procedure for synchronizing time. Refer to How to Synchronize the Time on a Windows 2000-Based Computer in a Windows NT 4.0 Domain at http://www.microsoft.com.
End User Notes
The following section contains important information that affects the end user. Some features affect Cisco IP Phone end users but might not be included in model-specific documentation for the end user. Cisco suggests that you pass the information on to affected end users.
Attendant Console
The following guidelines apply to Attendant Console:
•
•
•
Ring Settings
The Ring Settings window, a feature in the Cisco IP Phone User Options GUI, allows end users to assign distinctive ring tones to their phone line(s) from their computers. Users can access the Ring Settings window from the User Options main menu. The system administrator determines feature availability.
Cisco IPMA
The following guidelines apply to IPMA:
•
•
User Login Name and Password
Cisco CallManager supports only ISO-Latin1 (ISO-8859-1) characters and non-ISO-Latin1 characters in the range 0-127 in user login fields. This restriction affects services or applications that retrieve user login data from the Cisco CallManager database (such as the Cisco IP Phones, Cisco User Options, and the Cisco IPMA service).
If a user enters data that is not in the allowed character range, a dialog box displays and states that the user must enter data by using only ISO-Latin1 characters and non-ISO-Latin1 characters in the range 0-127. System administrators can advise end users who encounter this error message to enter a user name and/or password in only one of the following languages: Danish, Dutch, English, French, German, Italian, Norwegian, Portuguese, Spanish, Swedish, Hungarian, Polish, Greek, or Japanese.
Phone Hardening
Phone hardening options allow you to configure settings that restrict phone features and functionality for security purposes.
As part of phone hardening, you can disable user access to Cisco CallManager User Options and some phone settings (including those settings that are normally accessible via the Settings button). Because disabling access to these features will directly impact end users, you should advise affected users about the restrictions.
For more information about phone hardening, refer to the "Cisco IP Phone" chapter in the Cisco CallManager System Guide.
End-user documentation mentions the possibility of restricted access to some settings; however, Cisco suggests that you provide more detailed information to users who are affected by phone hardening.
Note
Resolved Caveats for Cisco CallManager - Release 3.3(5)
The Cisco CallManager Release Notes no longer list resolved caveats. Instead, you can find the latest resolved caveat information through Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip
To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
Using Bug Toolkit
To access Bug Toolkit, you need the following items:
•
•
•
To use Bug Toolkit, follow this procedure.
Procedure
Step 1
Log on with your Cisco.com user ID and password.
Step 2
Step 3
To view all caveats for Cisco CallManager, go to the "Search for bugs in other Cisco software and hardware products" section, and enter Cisco CallManager in the Product Name field. Alternatively, you can scroll through the product name list and click Cisco CallManager.
Step 4
Step 5
a.
•
A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.
•
A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features and/or enhancements.
b.
•
Note
•
•
•
c.
Note
d.
•
•
•
e.
Bug Toolkit returns the list of caveats on the basis of your query.
•
•
Note
Saving Bug Toolkit Queries
Bug Toolkit allows you to create and then save your queries to monitor a specific defect or network situation. You can edit a saved search at any time to change the alert conditions, the defects being watched, or the network profile.
Follow this procedure to save your Bug Toolkit queries.
Procedure
Step 1
Step 2
A new window displays.
Step 3
Step 4
•
•
Note
Bug Toolkit saves your bugs and searches, and makes them available through the My Stuff window. (The My Stuff window allows you to view, create, and/or modify existing bug groups or saved searches. Choose the My Stuff link to see a list of all your bug groups.)
Step 5
•
•
•
•
•
Step 6
Step 7
Note
Open Caveats for Cisco CallManager - Release 3.3(5)
Table 1 describes possible unexpected behaviors by Cisco CallManager release 3.3(5), sorted by component. Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager release 3.3(5).
Tip
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco CallManager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco CallManager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•
•
•
•
•
Note
Tip
Note
Documentation Updates
This section provides documentation changes that were unavailable when the Cisco CallManager release 3.3(5) documentation suite was released.
This section contains the following types of updates:
Errors
This section includes errors that the Cisco CallManager Documentation suite contains and includes the following topics:
•
•
•
•
•
•
•
•
•
•
•
Locale Installer
The Cisco CallManager Documentation Guide for Release 3.3(3) incorrectly refers to Using the Cisco IP Telephony Locale Installer for Cisco CallManager 3.3(3). The correct document is Using the Cisco IP Telephony Locale Installer with Cisco CallManager 3.3(3)sr1.
Microsoft Outlook Support with Cisco WebDialer
The Cisco WebDialer API Reference chapter in the Cisco WebDialer Guide states that the makeCallSoap interface (that plug-in clients such as Microsoft Outlook Plug-In use) is accessed by initiating a Simple Object Access Protocol (SOAP) request to a specified URL. The specified URL contains the IP address of the Cisco CallManager server. However, Cisco does not provide a Cisco WebDialer plug-in that works with Microsoft Outlook. If you require this type of plug-in, contact a third-party vendor or partner.
Mandatory Parameter for Cisco WebDialer API Reference
The Cisco WebDialer API Reference chapter in the Cisco WebDialer Guide incorrectly specifies a mandatory parameter for the makeCallProxy interface as appuid. The correct parameter to use is appid. This mandatory parameter must properly reflect appid for the Cisco WebDialer API to function correctly.
Date/Time Configuration Changes
The Cisco CallManager Administration Guide incorrectly states that the "local time zone of CallManager" option exists in the Date/Time Configuration window, Time Zone parameter. However, the drop-down box in Cisco CallManager 3.3(5) does not offer this option.
If you upgrade from a compatible Cisco CallManager release and you use "local time zone of CallManager" in the configuration, the Cisco CallManager database determines the appropriate time zone for the publisher database server and then displays that time zone as replacement for the CallManager time zone.
If you perform a fresh installation of Cisco CallManager, the default setting for Time Zone in the Date/Time Group equals GMT (Monrovia, Casablanca.
User Configuration Settings
The "Adding A New User" chapter in the Cisco CallManager Administration Guide erroneously states that Cisco CallManager does not allow you to use the following special characters in any field in the User Information window: =, +, <, >, #, ;, \, , "", and blank spaces.
This information is not correct; Cisco CallManager does allow input of special characters in the First Name, Last Name, UserID, and User Password fields in the User Configuration Settings.
The "Adding A New User" chapter in the Cisco CallManager Administration Guide also contains incorrect information about the "View page in" field.
Table 2 describes the "View page in" user configuration setting.
Using Valid Characters in Cisco CallManager User IDs
The "Add A New User" chapter in the Cisco CallManager Administration Guide and the Cisco CallManager online help documentation contain incorrect information about the use of special characters in the User ID field.
Specifically, the UserID field in the User Configuration Settings under the
User > Add a New User menu incorrectly states that you may use special characters when you configure a Cisco CallManager user ID.Do not use special characters, such as =, +, <, >, #, ;, \, , "" and blank spaces. You must use alphanumeric characters only.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef71945.
Cisco CallManager Dialed Number Analyzer Private Phrase Requirement
The "Installing Cisco CallManager Dialed Number Analyzer" chapter in the Cisco CallManager Dialed Number Analyzer Guide contains incorrect information about the Private Phrase Requirement in Step 6.
Procedure
Step 1
The Install Plugins window displays.
Step 2
Step 3
Step 4
Step 5
The Enter Private Phrase window displays.
Step 6
Step 7
If the private phrase is incorrect, a message displays. Return to Step 6. If the private phrase is correct, the Ready to Install the Program window displays.
Step 8
Step 9
The tool installs the Cisco Dialed Number Analyzer service on the machine.
Cisco CallManager Dialed Number Analyzer Service Startup Type
The "Installing Cisco CallManager Dialed Number Analyzer" chapter in the Cisco CallManager Dialed Number Analyzer Guide contains incorrect information about the service startup type being set to "Manual" after successful installation of DNA. The Dialed Number Analyzer service startup type actually gets set to "Automatic."
Therefore, the text in the Cisco CallManager Dialed Number Analyzer Guide should include the following statement:
When installation is successful, the Dialed Number Analyzer service installs and starts. The service startup type gets set to Automatic.
Supported Number of Alphanumeric Characters in the AAR Group Name Field
The "Automated Alternate Routing Group Configuration" chapter in the Cisco CallManager Administration Guide and the Cisco CallManager online help documentation contain incorrect information about the number of alphanumeric characters that the AAR Group Name field can include.
Specifically, the documentation specifies that the AAR Group Name field can contain up to 50 alphanumeric characters when it can accommodate 20 alphanumeric characters.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef90651.
Default Value for the Extension Mobility Alphanumeric Userid Service Parameter
The Setting Service Parameters section in the Cisco CallManager Features and Services Guide, Cisco CallManager Extension Mobility chapter incorrectly states that the default value for the clusterwide service parameter, Alphanumeric Userid, specifies False. The default value should reflect True.
The following information updates Step 9 in this chapter:
Step 9)
At the Alphanumeric Userid field, choose True to allow the UserID to contain alphanumeric characters. Choosing False allows the UserID to contain numeric characters only.
The default value specifies True.
You must restart the Cisco Tomcat Service if you change this setting.
Note
Updated Directory Path for Music On Hold Drop Directory
The "Services" chapter in the Cisco CallManager System Guide and the "Music on Hold" chapter in the Cisco CallManager Features and Services Guide contain incorrect path information about the default input directory for the Music on Hold drop directory. The correct path for the MOH audio source files should reflect:
c:\Program Files\Cisco\MOH\DropMOHAudioSourceFilesHere
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef56629
Default Value for Display IE and Redirecting IE Delivery Fields
The "Trunk Configuration" chapter and the "Gateway Configuration" chapter in the Cisco CallManager Administration Guide incorrectly display "unchecked" as the default value for the check boxes used by the following fields:
•
•
•
The correct default value should specify "checked" for these fields.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef96910 and http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef96929
Support for Overlap Route Patterns
Cisco CallManager does not support the use of overlap route patterns with MGCP gateways that are configured with FXO ports. The "Route Pattern Configuration" chapter and the "Gateway Configuration" chapter in the Cisco CallManager Administration Guide do not contain this information.
Cisco CallManager continues to support overlap route patterns for BRI and PRI MGCP-controlled digital interfaces.
Changes
This section contains changes that have occurred since the original release of the Cisco CallManager Administration Guide release 3.3. These changes do not currently appear in the release 3.3 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application.
•
•
•
•
•
•
•
Cisco CallManager Attendant Console
The name Cisco CallManager Attendant Console now appears as Cisco CM Attendant Console on the drop-down menu items under Service in Cisco CallManager Administration. The menu items for Cisco CallManager Attendant Console User and Cisco CallManager Attendant Console Server now appear as Cisco CM Attendant Console User and Cisco CM Attendant Console Server.
Cisco CallManager Attendant Console supports Cisco IP Phone models 7902, 7905, 7912, 7940, 7960, and 7970. The Cisco CallManager System Guide only reflects support for Cisco IP Phone models 7960/7940.
Calling Search Space
When you update a Calling Search Space in Cisco CallManager Administration, you do not have to restart the devices for the changes to take effect.
Note
Custom Phone Rings
The "Custom Phone Rings" chapter now exists in the Cisco CallManager Features and Services Guide.
Adding and Deleting Users by Using Cisco CallManager Administration
The Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager Release 3.3 does not contain all of the steps that are now required for adding and deleting users by using Cisco CallManager Administration. The following information provides an update to this procedure.
Procedure
Step 1
Note
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
A dialog box prompts you to restart dependent services. These services may differ depending on your configuration.
Step 13
Step 14
You may now add, update, or delete users within Cisco CallManager Administration. Refer to the latest version of the Cisco CallManager Administration Guide for information about how to perform these tasks.
Associating H.323 Devices to Users
In Cisco CallManager release 4.0, administrators could not associate H.323 devices with a user; therefore, the administrator could not configure features on the H.323 endpoints in the Cisco CallManager Administration User Configuration window.
Cisco CallManager release 3.3(5) corrects this behavior by displaying all devices, in addition to CTI-controllable devices, and by allowing the administrator to choose H.323 devices in the Device Association window.
For devices that are not CTI-controllable, such as H.323 devices, an asterisk (*) displays next to the device icon. All device association behavior remains identical regardless of the type of device for which the feature is configured.
Changes to Gateway Support with Cisco CallManager
Support exists for the following gateway types with Cisco CallManager release 3.3(5):
Cisco 1880
The "Gateway Configuration" chapter in the Cisco CallManager Administration Guide and the "Understanding Cisco CallManager Voice Gateways" chapter in the Cisco CallManager System Guide incorrectly list the Cisco 1880 router as a supported Cisco IOS MGCP gateway for use with Cisco CallManager. Cisco no longer supports the Cisco 1880 router for use with Cisco CallManager.
Cisco 1750, Cisco 1751, Cisco 1760
The "Understanding Cisco CallManager Voice Gateways" chapter in the Cisco CallManager System Guide incorrectly lists the Cisco 1750 router as a supported Cisco IOS H.323 gateway for use with Cisco CallManager. The Cisco 1751 router and the Cisco 1760 router replace the Cisco 1750 router. Cisco no longer supports the Cisco 1750 router for use with Cisco CallManager.
Cisco 2801
Cisco CallManager adds support for the Cisco 2801 router as a Cisco IOS MGCP gateway that is configurable for use with Cisco CallManager release 3.3(5).
Specifying Options that Display on the User Options Window
Cisco CallManager 3.3(5) adds support for Administrator configuration of the CCMUser Parameters in the Cisco CallManager Administration Enterprise Parameters Configuration window. These parameters allow the Administrator to configure the appropriate enterprise parameter settings in Cisco CallManager Administration to enable or disable the options that display to phone users on the Cisco CallManager User Options window.
From the Cisco CallManager User Options window, users can customize and control phone features and settings. (For detailed information about the Cisco CallManager User Options, refer to Customizing Your Cisco IP Phone on the Web.)
Note
The following values may be configured by the Administrator for the CCMUser Parameters:
•
•
•
•
•
•
•
•
•
•
•
•
•
Perform the following procedure to configure the options that appear on the Cisco CallManager User Options window.
Procedure
Step 1
The Enterprise Parameters Configuration window displays.
Step 2
•
•
Step 3
For more information, refer to the latest version of the Cisco CallManager Administration Guide.
Ad Hoc Conference Limitations
Cisco CallManager supports a maximum of 100 simultaneous ad hoc conferences for each Cisco CallManager server.
Meet-Me Conference Limitations
Cisco CallManager supports a maximum of 100 simultaneous meet-me conferences for each Cisco CallManager server.
Omissions
This section lists new and additional information that the current Cisco CallManager documentation does not include:
•
•
•
•
•
•
•
•
•
•
•
•
New Service Parameter for Cisco CallManager Extension Mobility
Cisco CallManager 3.3(3) introduces a new service parameter for Cisco CallManager Extension Mobility. The Cisco CallManager Extension Mobility chapter in the Cisco CallManager Features and Services Guide does not document this information.
At the service parameter field, Remember last user logged in, you can choose True to specify that the Extension Mobility application remembers the user ID of the last user that logged in to the phone. The default value for the service parameter specifies False.
Note
This setting proves useful in situations where individuals use their own phone on a regular basis and no one else uses that phone. For example, user may use Cisco CallManager Extension Mobility to enable the types of calls that are allowed from a phone. Individuals who are using their office phone in a logout state can make only internal or emergency calls, but after logging in using Cisco CallManager Extension Mobility, the user also can make local, long-distance, and international calls. In this scenario, only this user regularly logs in to the phone. It makes sense to set the Extension Mobility application to remember the last user ID that is logged in.
In a true hoteling scenario, where users can come into any office and use any phone on a temporary basis, set this parameter to false.
H.323 Configuration Settings
Additions to the Phone Configuration Settings table in the Phone Configuration chapter in Cisco CallManager Administration Guide include the following configuration settings for H.323.
Table 3 displays these settings.
Defining the Quality of Service (QoS) Values
Because the "NA" and "Infinity" values for the QoS parameters that the Cisco CallManager Serviceability CDR Analysis and Reporting (CAR) tool uses are case-sensitive, you must enter these values exactly as shown; the system does not support other forms.
Quality Report Tool Configuration Settings
Cisco CallManager 3.3 introduces the Quality Report Tool (QRT) feature. The Cisco CallManager 3.3 release documentation does not provide specific information about configuring and using the QRT feature.
The Cisco CallManager Features and Services Guide for Cisco CallManager release 4.1 will include the following information about QRT:
•
•
•
•
•
•
QRT Overview
The Quality Report Tool, a voice-quality and general problem-reporting tool for Cisco IP Phones, extends to IP phones as a Windows NT service.
As a feature within the Cisco Extended Functions service, QRT automatically loads with the Cisco CallManager installation. The Cisco CallManager system administrator enables the QRT feature through the use of softkey templates.
Perform these steps after installation to enable QRT availability for users and to set up reporting capabilities:
1.
2.
3.
4.
Note
User Interfaces
You can choose to enable two different user modes, depending upon the amount of information that you want users to submit:
•
The system supports interview mode only when the IP phone is in the Connected or On Hook call state.
•
The system supports silent mode only when the IP phone is in the Connected, Connected Conference, or Connected Transfer call state.
When users experience problems with their IP phones, they can invoke QRT by pressing the QRT softkey on their Cisco IP Phone to easily and accurately report voice quality and other general problems.
Creating a Softkey Template with the QRT Softkey
Perform the following procedure to create a new softkey template with the QRT softkey.
Procedure
Step 1
The Softkey Template Configuration window displays.
Step 2
Step 3
The Softkey Template Configuration window displays with new information.
Step 4
Step 5
The Softkey Template Configuration redisplays with new information.
Step 6
The Softkey Layout Configuration window displays. You must add the QRT softkey to the Connected, Connected Conference, Connected Transfer, and On Hook call states.
Step 7
The Softkey Layout Configuration window redisplays with the Unselected Softkeys and Selected Softkeys lists.
Step 8
Step 9
Step 10
Note
Configuring the QRT Softkey Template in Device Pool
Perform the following procedure to add the QRT softkey template to the device pool.
Procedure
Step 1
The Device Pool Configuration window displays.
Step 2
You can add the template to the default device pool if you want all users to have access to the QRT softkey, or you can create a customized device pool for QRT feature users.
Step 3
Step 4
Adding the QRT Softkey Template in Phone Configuration
Perform the following procedure to add the QRT softkey template to each user phone.
Procedure
Step 1
The Find and List Phones window displays.
Step 2
In the Softkey Template field, choose the softkey template that contains the QRT softkey from the drop-down list box.
Step 3
Activating the Cisco Extended Functions Service for QRT
Follow this procedure to activate the Cisco Extended Functions service for use with the QRT feature.
Procedure
Step 1
A list of Cisco CallManager servers displays.
Step 2
Step 3
Step 4
Configuring Alarms and Traces for QRT
Follow this procedure to configure alarms and SDI traces through Cisco CallManager Serviceability.
Procedure
Step 1
A list of Cisco CallManager servers displays.
Step 2
Step 3
Step 4
Step 5
Step 6
A list of Cisco CallManager servers displays.
Step 7
Step 8
Step 9
Step 10
For more information, refer to the Cisco CallManager Serviceability Administration Guide.
Setting the Cisco Extended Functions Service Parameters for QRT
Set the Cisco Extended Functions service parameters by using Cisco CallManager Administration to access the service parameters (Service > Service Parameters). Choose the server where the QRT application resides and then choose the Cisco Extended Functions service.
Cisco recommends that you use the default service parameters settings unless the Cisco Technical Assistance Center (TAC) instructs you to do otherwise.
Cisco Extended Functions includes the following parameters for QRT:
•
Recommended default value specifies False (silent mode).
•
Recommended default value specifies -1 (poll until the call ends).
•
Recommended default value specifies 30.
•
Recommended default value specifies
C:\Program Files\Cisco\QRT\QRT.xml.•
Recommended default value specifies 250.
•
Recommended default value specifies 2000.
Using the QRT Viewer
You can use the QRT Viewer to view the IP phone problem reports that the Quality Report Tool generates. The QRT Viewer allows you to filter, format, and view the tool-generated phone problem reports, so they provide you with the specific information that you need.
For detailed information about accessing, configuring, using, and customizing the IP phone problem reports, refer to the Cisco CallManager Serviceability Administration Guide.
Exporting and Importing Phones with More Than One User
When you use BAT to export phone records that have multiple users who control a phone, the export utility generates a unique phone record for each user. (The phone information remains the same, but each record has a different user ID.)
When you import the exported file that contains phones with multiple users, the first phone record inserts with the associated user. However, subsequent phone records fail to insert, even though BAT attempts to insert all records and accepts the user association to the phone. In this case, the log file for the import transaction shows that the phone insertions failed for all users except the first user who is associated with the phone.
Device Profile Default Configuration
The online help for the Cisco CallManager application does not include information about Device Profile Defaults. The following sections provide information about configuring and updating device profile defaults:
•
•
•
•
•
Device Profile Default Overview
Use the device profile default whenever a user logs on to a phone model for which no user device profile exists. To create a device profile default for each phone model that supports Cisco Extension Mobility, use the Cisco CallManager Device Profile Default Configuration window. The maximum number of device profile defaults cannot exceed the number of phone models that support Cisco CallManager Extension Mobility.
For example, a user logs on to a Cisco IP Phone model 7960 for which there is a user device profile. The user device profile for the user gets downloaded to the phone to which the user logged on. Later, the same user logs on to a Cisco IP Phone model 7940 for which no user device profile exists. In this case, the device profile default for the Cisco IP Phone model 7940 gets downloaded to the phone.
A device profile default comprises the set of attributes (services and/or features) that are associated with a particular device. Device profiles include device type, user locale, phone button template, softkey template, and Cisco IP Phone services.
Adding a New Device Profile Default
The device profile default contains attributes such as device type, phone template, user locale, expansion modules, softkey template, and subscribed Cisco IP Phone services. Perform the following procedure to add a device profile default.
Procedure
Step 1
The Device Profile Default Configuration window displays.
Step 2
Step 3
Step 4
The device profile displays in the Device Profile Default pane.
Updating Device Profile Defaults
This section describes how to update a device profile default.
Procedure
Step 1
Step 2
The Device Profile Default Configuration window displays the profile information of the profile that you chose.
Step 3
Step 4
Deleting a Device Profile Default
This section describes how to delete a device profile default.
Procedure
Step 1
Step 2
The Device Profile Default Configuration window displays the profile information of the profile that you chose.
Step 3
A message displays that states that this action cannot be undone.
Step 4
Device Profile Default Configuration Settings
Table 4 describes the fields that are available in the Cisco CallManager Device Profile Default Configuration window.
Subscribing Services to a Device Profile Default
To subscribe a service such as Cisco CallManager Extension Mobility to the device profile default, perform the following procedure:
Procedure
Step 1
Step 2
The Device Profile Default Configuration window displays the profile information of the profile that you chose.
Step 3
The Subscribe Cisco IP Phone services window displays.
Step 4
Step 5
The window displays with the service that you chose. If you want to choose a different service, click Back and repeat Step 4.
Step 6
Step 7
The service appears in the Subscribed Services list.
User Settings in Cisco CallManager Administration
The Cisco CallManager Administration Guide does not provide information for all the user settings that display in Cisco CallManager Administration.
Table 5 provides a description of the user settings.
Name Change for the Cisco IAD 2400 Gateway Type in Cisco CallManager Administration
In the "Add a New Gateway" window in Cisco CallManager Administration, the "Cisco IAD 2420 (end of sale product)" gateway type has replaced the Cisco IAD 2400 gateway type.
Use the Cisco IAD 2420 gateway type to add a new Cisco IAD 2420 gateway to Cisco CallManager.
Note
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef30742.
Reinstalling Dialed Number Analyzer after a Cisco CallManager Upgrade
The Cisco CallManager Dialed Number Analyzer Guide does not contain the following information about reinstalling DNA after a Cisco CallManager upgrade.
If you upgrade Cisco CallManager on any server in a cluster, you must reinstall the Dialed Number Analyzer plug-in on that node in the cluster if you want the upgraded Dialed Number Analyzer version to be installed on your machine.
Follow these procedures to uninstall Dialed Number Analyzer and to reinstall the upgraded version of Dialed Number Analyzer:
Procedure to Uninstall Dialed Number Analyzer
Step 1
a.
The Add/Remove Programs dialog displays and shows a list of programs that are installed on the machine.
b.
c.
Alternatively, you can uninstall Dialed Number Analyzer by using the Dialed Number Analyzer Uninstall utility, as described below:
a.
b.
Procedure to Reinstall Dialed Number Analyzer
Step 1
The Install Plugins window displays.
Step 2
Step 3
Step 4
The InstallShield Wizard for the Cisco Dialed Number Analyzer window displays.
Step 5
The Enter Private Phrase window displays.
Step 6
Step 7
If you enter an incorrect private password phrase, the system displays a message. Return to Step 6 to re-enter the private password phrase.
When you enter the correct private password phrase, the Ready to Install the Program window displays.
Step 8
Step 9
The tool installs the Cisco Dialed Number Analyzer service on the machine.
Note
Personal Directory
Personal Directory provides a personal address book that is stored in the Cisco CallManager LDAP directory, a Cisco IP Phone synchronizer, and two Cisco IP Phone services: Personal Address Book and Personal Fast Dials.
The Cisco CallManager documentation does not contain the following information about configuring and using Personal Directory:
•
•
•
•
•
System Requirements
The system requires the following components for use with Personal Directory:
•
•
•
•
•
Note
Configuring Personal Directory
To configure the Personal Directory, you must configure the Personal Address Book Service and the Personal Fast Dials Service.
•
•
Configuring the Personal Address Book Service
You configure the Personal Address Book by adding the service to Cisco CallManager Administration and configuring the service parameters.
Follow this procedure to configure the Personal Address Book service:
Procedure
Step 1
The Cisco IP Phone Services Configuration window displays.
Step 2
Step 3
Step 4
http://<CallManager hostname or IP address>/ccmpd/xmlAddressBookInput.asp
Step 5
Step 6
The Configure Cisco IP Phone Service Parameter window displays.
Step 7
Step 8
Step 9
The Cisco IP Phone Services Configuration window displays.
Step 10
Personal Address Book Service Parameter Settings
Table 6 shows the service parameter settings for the three service parameters required for the Personal Address Book service. Where indicated, use the exact parameter name.
Note
Configuring the Personal Fast Dials Service
You configure Personal Fast Dials by adding the service to Cisco CallManager Administration and configuring the appropriate service parameters.
Follow this procedure to configure the Personal Fast Dials service:
Procedure
Step 1
The Cisco IP Phone Services Configuration window displays.
Step 2
Step 3
Step 4
http://<CallManager hostname or IP address>/ccmpd/xmlFastDials.asp
Step 5
Step 6
The Configure Cisco IP Phone Service Parameter window displays.
Step 7
Step 8
Step 9
The Cisco IP Phone Services Configuration window displays.
Step 10
Personal Fast Dials Service Parameter Settings
Table 7 shows the service parameter settings for the three service parameters that are required for Personal Fast Dials service. Where indicated, use the exact parameter name.
Downloading the Cisco IP Phone Address Book Synchronizer
Users must install the Cisco IP Phone Address Book Synchronizer plug-in on their computers before they can use the Personal Directory.
Use the following procedure to download the Cisco IP Phone Address Book Synchronizer installation file. After you download the file, you can distribute it to the users in your network.
Procedure
Step 1
Step 2
Follow the online instructions.
Step 3
a.
b.
Preparing the Phone User for Personal Directory
After you have added the Personal Directory services and configured the service parameters, provide the phone user with the following information:
•
•
•
•
•
Dependency Between Cisco CallManager and CTI Manager
The Cisco CallManager Serviceability System Guide does not include the following information about the dependency between Cisco CallManager and CTI Manager.
In a Cisco CallManager cluster, both the Cisco CallManager service and CTI Manager must be activated for the system to function properly. If CTI Manager is activated and the Cisco CallManager service is deactivated, CTI Manager does not start or it terminates unexpectedly.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef89601.
Using Wildcard Characters in Device Searches
The Cisco IP Phones chapter in the Cisco CallManager System Guide does not document the following information about using wildcard characters in device searches.
Cisco CallManager only supports SQL wildcards for device searches in the Cisco CallManager Administration Find and List Phones window. Therefore, you can perform a wildcard search for phones by using the percent sign (%) character, which matches any string of characters.
For example, if the Cisco CallManager database contains device names SEP1234 and SEP5678, you can query for all devices that include SEP by using the wildcard search SEP%. This query would return a list that includes SEP1234 and SEP5678.
Be aware that you cannot perform a wildcard search by using the asterisk (*) because the * character is not a recognized SQL wildcard.
For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCed91256.
Removing a Subscriber Server from Cisco CallManager
The following information provides the steps for removing a subscriber server from Cisco CallManager.
You can delete a subscriber server from the Cisco CallManager cluster by using the Server Configuration window in Cisco CallManager Administration. This deletion removes the server from the Cisco CallManager Administration database, but it does not delete all server dependencies.
To fully delete a server from the system, you must perform the following steps:
Procedure
Step 1
For additional information, refer to the Cisco CallManager Administration Guide, Deleting a Server chapter.
Tip
Step 2
Refer to the Cisco CallManager Serviceability Administration Guide, Service Activation chapter, for more information.
Step 3
Refer to the Cisco CallManager Administration Guide, Deleting a Server chapter, for more information.
Step 4
See the "Remove Redundant DCD Replication Agreements" section for more information.
Remove Redundant DCD Replication Agreements
After you remove the subscriber server from the cluster, you must clean the DCD replication information from the publisher DCD by running the Clean_publisher command file. (This command file only executes on the publisher server.)
You can access this command file on servers that are running Cisco CallManager release 3.3 and later. Cisco CallManager installs the Clean_publisher command file on the server during installation of the Cisco Directory component.
To clean the DCD replication information, enter the following command from any directory on the publisher server:
c:\Clean_publisher.cmd
Note
Using Script Files to Remove a Subscriber Server from Cisco CallManager
To remove a subscriber server from Cisco CallManager, see the "Removing a Subscriber Server from Cisco CallManager" section.
If your attempts to remove a server were not successful, perform the following steps:
Procedure
Step 1
See the "Remove Subscriber Information" section.
Step 2
For more information, refer to the Cisco CallManager Administration Guide, Appendix A.
Remove Subscriber Information
If the server removal was unsuccessful, run the script file that cleans up subscriber-related database records and removes the SQL replication information. Run the script file for the publisher server and the script file for the subscriber server.
See the "Contents of the RemovePublisher.bat Script File" section and the "Contents of the RemoveSubscriber.bat Script File" section for more information.
Tip
Run RemovePublisher.bat Script on Publisher Server
Execute the RemovePublisher.bat script file from the Cisco CallManager publisher server for the cluster that contains the subscriber that you want to remove. This script runs from the command prompt from any directory.
Tip
From any directory on the publisher server, enter the following command:
<path where you saved the script>:\RemovePublisher "server" "database" "name_of_server_to_delete_from_database connection string"
To find the database connection string name, follow these steps:
Procedure
Step 1
Step 2
Step 3
Step 4
For example, DSN=CiscoCallManager;Server=ABC2.
When you run this command from the command prompt, errors display; no separate error log file gets generated.
To view the contents of the script file, see the "Contents of the RemovePublisher.bat Script File" section.
Contents of the RemovePublisher.bat Script File
Example 1 displays the contents of the script file that cleans up subscriber-related database records and removes the SQL replication information from the publisher server.
Example 1 Script File Contents
@echo off@if "%3x" == "x" goto Usageecho Install stored procedure in database %2echo USE %2>>temp.sqlecho GO >>temp.sqlecho DROP PROCEDURE dblRemoveServerFromDB >>temp.sqlecho GO >>temp.sqlecho CREATE PROCEDURE [dblRemoveServerFromDB] >>temp.sqlecho (@servername NVARCHAR(50)) AS >>temp.sqlecho BEGIN TRANSACTION >>temp.sqlecho DECLARE @nodeid NVARCHAR(50), @deviceid NVARCHAR(50), @pnsid NVARCHAR(50) >>temp.sqlecho -- >>temp.sqlecho PRINT 'Get the Node ID' >>temp.sqlecho SELECT @nodeid=pkid from ProcessNode where name=@servername >>temp.sqlecho -- >>temp.sqlecho PRINT 'Delete associated Device and MediaMixer' >>temp.sqlecho WHILE (SELECT COUNT(*) FROM Device WHERE fkProcessNode=@nodeid) ^> 0 >>temp.sqlecho BEGIN >>temp.sqlecho SELECT @deviceid=pkid from Device where fkProcessNode=@nodeid >>temp.sqlecho PRINT 'Delete MediaMixer' >>temp.sqlecho DELETE FROM MediaMixer WHERE fkDevice=@deviceid >>temp.sqlecho PRINT 'Delete MOHServer' >>temp.sqlecho DELETE FROM MOHServer WHERE fkDevice=@deviceid >>temp.sqlecho PRINT 'Delete Device' >>temp.sqlecho DELETE FROM Device WHERE pkid=@deviceid >>temp.sqlecho END >>temp.sqlecho -- >>temp.sqlecho PRINT 'Delete associated CallManager records' >>temp.sqlecho DELETE FROM CallManagerGroupMember FROM CallManagerGroupMember AS M >>temp.sqlecho JOIN CallManager AS C ON C.pkid=M.fkCallManager WHERE C.fkProcessNode=@nodeid >>temp.sqlecho DELETE FROM CallManager WHERE fkProcessNode=@nodeid >>temp.sqlecho -- >>temp.sqlecho PRINT 'Delete associated ProcessConfig records' >>temp.sqlecho DELETE FROM ProcessConfig WHERE fkProcessNode=@nodeid >>temp.sqlecho -- >>temp.sqlecho PRINT 'Delete associated AlarmConfig records' >>temp.sqlecho DELETE FROM AlarmConfig FROM AlarmConfig AS A JOIN ProcessNodeService >>temp.sqlecho AS S ON A.fkProcessNodeService=S.pkid WHERE S.fkProcessNode=@nodeid >>temp.sqlecho PRINT 'Delete associated ProcessNodeService records' >>temp.sqlecho DELETE FROM ProcessNodeService WHERE fkProcessNode=@nodeid >>temp.sqlecho -- >>temp.sqlecho PRINT 'Delete associated ComponentVersion records' >>temp.sqlecho DELETE FROM ComponentVersion WHERE fkProcessNode=@nodeid >>temp.sqlecho -- >>temp.sqlecho PRINT 'Delete the node' >>temp.sqlecho DELETE FROM ProcessNode WHERE pkid=@nodeid >>temp.sqlecho -- >>temp.sqlecho COMMIT TRANSACTION >>temp.sqlecho GO >>temp.sqlecho -- Execute procedure on server %1echo exec dblRemoveServerFromDB '%3' >>temp.sqlosql -S %1 -d %2 -E -e -i temp.sqldel temp.sqlecho USE %2 >temp1.sqlecho GO >>temp1.sqlecho sp_dropsubscription @publication = '%2', @subscriber = '%3', @article='all' >>temp1.sqlecho GO >>temp1.sqlosql -S %1 -d %2 -E -e -i temp1.sqldel temp1.sqlgoto endd:Usage@echo Usage:RemoveServerFromDB "server" "database" "name_of_server_to_delete_from_ProcessNode.Name"@echo Example: RemoveServerFromDB . CCM0300 fred.cisco.com:enddContents of the RemoveSubscriber.bat Script File
Example 2 displays the contents of the script file that removes the SQL replication information from the subscriber server.
Example 2 Script File Contents
@echo off@if "%2x" == "x" goto Usageecho Install stored procedure in database %2echo sp_removedbreplication @dbname = %2 >temp1.sqlecho GO >>temp1.sqlosql -S %1 -d %2 -E -e -i temp1.sqldel temp1.sqlgoto endd:Usage@echo Usage: RemoveSubscription "server" "database"@echo Example: RemoveSubscription . CCM0300:enddObtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation DVD
Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/
•
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an emergency, you can also reach PSIRT by telephone:
•
•
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0501R)
Copyright © 2005 Cisco Systems, Inc. All rights reserved.
