Guest

Cisco Unified Communications Manager (CallManager)

Release Notes for Cisco Unified CallManager Release 4.2(3)

  • Viewing Options

  • PDF (877.9 KB)
  • Feedback
Release Notes for Cisco Unified CallManager Release 4.2(3)

Table Of Contents

Release Notes for Cisco Unified CallManager Release 4.2(3)

Contents

Introduction

System Requirements

Supported Platforms

Determining the Software Version

Compatibility Matrix and Supported Upgrades

Related Documentation

New and Changed Information in Cisco Unified CallManager 4.2(3)

Cisco Unified CallManager 4.2(3) Installation and Upgrade Guidelines

Installation and Upgrade

Upgrade Assistant Utility

Backup and Restore

Operating System Installation Guidelines

Upgrading to Cisco Unified CallManager Release 4.2(3)

New and Changed Cisco Unified CallManager Features

Original Calling Party on Transfer

Hold Reversion

Advanced Ad Hoc Conference Features

MGCP T.38 Enhancements

SCCP Optimization

Connected Number Display

TFTP Enhancements

New and Changed Information for Cisco Unified IP Phones

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone Support for Cisco CallManager 4.2(3) Features

Cisco Unified CallManager Applications

Cisco Extension Mobility Enhancement

Multilevel Precedence and Preemption (MLPP) Supplementary Services

Cisco Unified CallManager Bulk Administration Tool Features

Cisco Unified CallManager Administration Configuration Tips

BAT Performance

New and Changed Information for Cisco Unified CallManager Serviceability

Addition of a New Alarm and Alert to Detect Failed Login Attempts for MLA Accounts

New and Changed Information for Third-Party API

CDR Definitions

Cisco Unified JTAPI Developers Guide for Release 4.2(3)

Cisco Unified TAPI Developers Guide for Release 4.2(3)

Installation Notes

Limitations and Restrictions

Important Notes

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled

Using MICs for Phone Authentication

Caveats

Resolved Caveats for Cisco Unified CallManager - Release 4.2(3)

Using Bug Toolkit

Saving Bug Toolkit Queries

Open Caveats for Cisco Unified CallManager - Release 4.2(3)

Troubleshooting

Documentation Updates

Updates

MLA: Adding an AD User to User Group Gets Error Number: -1005

Path Replacement to RP with Partition Works for <none> PR CSS

H.323 Information Settings on a H.323 Client Documentation Updates

Cisco WebDialer Does Not Close All Windows After Dialing

PRI Protocol Type Field Updates

Cisco Unified CallMananger Sent H323 Redirecting Number IE in UUIE

Extension Mobility Configuration Step Is Missing

Enabling Auto Registration

Music On Hold Configuration

Logged Into Hunt Group on Phone Configuration Window

TAPS and Autoregister

CDR Search for Extension

Errors

Bulk Administration Tool User Guide Title Error

Cisco Unified CM Administration Guide Contains Incorrect Information About Configuring Music on Hold

Changes

Device Mobility Info Configuration Window

Device Pool Configuration Window

Behavior Enhancements to Join

Omissions

CTI Monitored Lines

Malicious Call Identification Restrictions

TAPS Installation Procedure for CCM4.1(3)SR2 and Subsequent Releases

Find/List Windows

Obtaining Documentation

Cisco.com

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco Unified CallManager Release 4.2(3)


June 23, 2008

Table 1 Modification History

Date
Change Made

06/23/2008

Under Important Notes, added "CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later" section

01/17/2008

In the Errors section, added the "Cisco Unified CM Administration Guide Contains Incorrect Information About Configuring Music on Hold"

11/16/2007

Corrected "Upgraded Memory Requirement" section


These release notes describe the new features and caveats for Cisco Unified CallManager release 4.2(3).


Note To view the release notes for previous versions of Cisco Unified CallManager, go to: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_2/rel_note/index.htm


Before you install Cisco Unified CallManager, Cisco recommends that you review the "Caveats" section for information about issues that may affect your system.

For a list of the open and resolved caveats for Cisco Unified CallManager release 4.2(3), see the "Resolved Caveats for Cisco Unified CallManager - Release 4.2(3)" section and the "Open Caveats for Cisco Unified CallManager - Release 4.2(3)" section. Updates for these release notes occur with every maintenance release 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 all versions of Cisco Unified CallManager on Cisco Connection Online (CCO) at the following URL:

http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

Contents

These release notes discuss the following topics:

Introduction

System Requirements

Related Documentation

New and Changed Information in Cisco Unified CallManager 4.2(3)

Installation Notes

Limitations and Restrictions

Important Notes

Caveats

Troubleshooting

Documentation Updates

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Introduction

Cisco Unified CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco Unified 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 Unified CallManager Release 4.2(3) on a Cisco Media Convergence Server (MCS).

You may also install Cisco Unified CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.


Note Cisco Unified CallManager 4.1(3) and subsequent releases require upgraded memory for Cisco Unified CallManager servers. See the "Upgraded Memory Requirement" section for additional information.



Caution The installation does not complete if you do not have the exact configuration.

Access the supported Cisco-approved server configuration for an IBM server or an HP server at the following URL:

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 Unified CallManager Release 4.2(3).

Supported Platforms

To find which servers support Cisco Unified CallManager 4.2 releases, refer to the Guide to Cisco Unified CallManager Upgrades and Server Migrations at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html

Determining the Software Version

To determine the software version of Cisco Unified CallManager, open Cisco Unified CallManager Administration; then, click Details on the main Cisco Unified CallManager Administration window. The following information displays:

Cisco Unified CallManager System version

Cisco Unified CallManager Administration version

Database information and database DLL versions

Compatibility Matrix and Supported Upgrades

You can find which application versions are compatible with Cisco Unified CallManager release 4.2(3) and which previous releases of Cisco Unified CallManager have upgrade support by referring to the Cisco Unified CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm


Note Be aware that the release of Cisco Unified Communication products does not always coincide with Cisco Unified CallManager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CallManager release 4.2(3). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco Unified IP telephony products.


Related Documentation

Refer to the Cisco Unified CallManager Documentation Guide for a list of documents that are related to Cisco Unified CallManager release 4.2 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_2/doc_gd

Along with the documents that are listed in the Cisco Unified CallManager Documentation Guide, the following list specifies other related documents for Cisco Unified CallManager Release 4.2:

System Error Messages for Cisco Unified CallManager 4.2

New and Changed Information in Cisco Unified CallManager 4.2(3)

Cisco Unified CallManager 4.2(3) supports the product name changes for the suite of Cisco Unified Communications system of voice, video, and IP communications products and applications. This name change updates all product and application names in the user interface with the exception of the following services and performance counter for Cisco Unified CallManager Serviceability:

Feature Services

Cisco Unified CallManager service supports Cisco Unified CallManager.

Cisco Unified CallManager Attendant Console Server service supports Cisco Unified CallManager Attendant Console.

Cisco IP Manager Assistant service supports Cisco Unified CallManager Assistant.

Cisco Dialed Number Analyzer service supports Cisco Unified CallManager Dialed Number Analyzer.

Network Services

The Cisco Unified CallManager Admin service supports Cisco Unified CallManager Administration.

The Cisco Unified CallManager Serviceability service supports Cisco Unified CallManager Serviceability.

The Cisco Unified CallManager Serviceability RTMT service supports the Cisco Unified CallManager Real-Time Monitoring Tool (RTMT).

Perfmon

The Cisco Unified CallManager object provides information about calls, applications, and devices that are registered with the Cisco Unified CallManager.

The Cisco Unified CallManager Attendant Console (Cisco Unified CallManager Attendant Console Server service) object provides information about the Cisco Unified CallManager Attendant Console.

The Cisco Unified CallManager System Performance object provides system performance information about Cisco Unified CallManager. The Cisco IP Manager Assistant (IPMA) Service object provides information about the Cisco Unified CallManager Assistant application.

You can find more information on Cisco Unified Communications system of voice, video, and IP communications products and applications at www.cisco.com/go/unified.

The following sections describe new features and changes that are pertinent to Cisco Unified CallManager, Release 4.2(1) or later. The sections may include configuration tips for the administrator, information about users, and where to find more information.

Cisco Unified CallManager 4.2(3) Installation and Upgrade Guidelines

Operating System Installation Guidelines

Upgrading to Cisco Unified CallManager Release 4.2(3)

New and Changed Cisco Unified CallManager Features

New and Changed Information for Third-Party API

Installation Notes

Cisco Unified CallManager Bulk Administration Tool Features

New and Changed Information for Cisco Unified CallManager Serviceability

Installation Notes

New and Changed Information for Third-Party API

Cisco Unified CallManager 4.2(3) Installation and Upgrade Guidelines

This section includes information about the guidelines that apply to Cisco Unified CallManager 4.2(3) installation and upgrade procedures:

Installation and Upgrade

Upgrade Assistant Utility

Backup and Restore

Installation and Upgrade

Cisco Unified CallManager 4.2(3) implements the following installation and upgrade guidelines:

See the "Compatibility Matrix and Supported Upgrades" section for more information about supported upgrade paths.

This section includes the following topics:

Upgraded Memory Requirement

Adding Cisco Unified CallManager Servers as Members of a Windows Domain

Upgraded Memory Requirement

The Cisco Unified CallManager installation requires a minimum of 2 GB of memory on the Cisco Unified CallManager publisher server. If the installation process detects less than 2 GB of memory, the installation aborts.

The installation process performs a similar check on the Cisco Unified CallManager subscriber server; it may allow the installation to continue if it detects less than the minimum requirement.


Note To avoid system problems, such as dropped calls, make sure that your servers have a minimum of 2 GB of memory installed.


Adding Cisco Unified CallManager Servers as Members of a Windows Domain

Cisco does not recommend adding Cisco Unified CallManager servers as members of a Microsoft Windows domain. To prevent failures that may occur by the server being a member of a domain, Cisco Unified CallManager 4.1(3) modified the installation process to abort the installation and display the following message if it detects that the server is in a Windows domain:

"The installation has detected that the server exists in a domain. When a server exists in a domain, authentication between servers may fail, or the non-default domain security policies may be too restrictive for the Cisco Unified CallManager installation to build critical NT Accounts during an upgrade. Your server must be removed from the domain and added to a workgroup to reduce installation and upgrade errors, failures, or a total system failure, which would result in a loss of data and a complete reinstallation of Cisco Unified CallManager. The installation will now abort."

To continue, you must first remove the Cisco Unified CallManager server from the Windows domain and add it as a Workgroup member before you can install or upgrade Cisco Unified CallManager on your server.

If your system architecture depends on servers joining a Windows domain, you must disable the Network Time Protocol (NTP) software, which Cisco Unified CallManager installed, 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.

Follow this procedure to disable the Cisco-installed NTP software on a server:

Procedure


Step 1 Choose Start > Programs > Administrative Tools > Services.

Step 2 Double-click the Network Time Protocol service.

Step 3 In the Startup type field, choose Disabled.

Step 4 Click Stop.

Step 5 Click OK.



Note During installation, you must choose to install Cisco Unified CallManager as a server in a workgroup.



Note Do not make any modifications to the installed NTP configuration file (NTP.CONF); otherwise, you may encounter synchronization problems with CDRs, Traces, and Event Logging. Cisco does not support any modifications to the installed NTP configuration file.



Caution Cisco Unified CallManager 4.2(3) will abort the installation process if it detects that the server is in a Windows domain. Therefore, you must first remove the Cisco Unified CallManager server from the Windows domain and add it as a workgroup member before you can install or upgrade Cisco Unified CallManager on your server.

When you complete your upgrade and you are adding the server to the Windows domain, you must disable the Cisco-installed NTP services 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 Microsoft documentation.

For more information, refer to http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg67072

Upgrade Assistant Utility

Cisco Unified CallManager Upgrade Assistant Utility 4.2(3) replaces previous versions.

This release of Cisco Unified CallManager Upgrade Assistant Utility supports multiple version upgrades; that is, you can use Cisco Unified CallManager Upgrade Assistant Utility version 4.2(3) or later to detect the health of your servers before you upgrade to Cisco CallManager Release 3.3(5), 4.0(2a), 4.1(3), 4.2(1), or 4.2(3)

For additional information, refer to Using Cisco Unified CallManager Upgrade Assistant Utility 4.2(3) at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_2/install/upgrade/index.htm

Backup and Restore

The following guidelines apply to Cisco Unified CallManager backup and restore procedures:

The Cisco Unified IP Telephony Backup and Restore System (BARS) version 4.0(11) or later supports Cisco Unified CallManager 4.2(3).

Cisco Unified CallManager Release 3.3 and later no longer supports Cisco Unified IP Telephony Applications Backup Utility version 3.5.

For additional information about backup and restore procedures, refer to the Cisco Unified IP Telephony Applications Backup website at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/backup/


Note Check the Cisco Unified CallManager Compatibility Matrix for the latest information about supported compatibility combinations. See the "Compatibility Matrix and Supported Upgrades" section for more information.


Where to Find More Information

Installing Cisco Unified CallManager Release 4.2(3)

Upgrading Cisco Unified CallManager Release 4.2(3)

Operating System Installation Guidelines

For information about installing the operating system, refer to "Cisco Unified CallManager 4.2(3) Installation and Upgrade Guidelines" section


Tip Refer to the following URL for information about the latest version of the Cisco-provided operating system, installation procedures, and release notes: http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/install/index.htm.



Note Newer servers, such as the MCS-7835-H1-IPC1, require an operating system installation kit that contains CD/DVD media. Use the operating system upgrade only to upgrade earlier versions of the operating system to the new level (service packs, hotfixes, configuration settings, BIOS, firmware, and drivers).


Where to Find More Information

Installing Cisco Unified CallManager 4.2(3)

Upgrading to Cisco Unified CallManager Release 4.2(3)

For detailed information about upgrading to Cisco Unified CallManager 4.2(3), refer to Upgrading Cisco Unified CallManager Release 4.2(3). For additional guidelines about Cisco Unified CallManager installation and upgrades, see the "Cisco Unified CallManager 4.2(3) Installation and Upgrade Guidelines" section.


Tip To verify which versions of Cisco Unified CallManager are compatible for upgrade, refer to the most recent version of the Cisco Unified CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm



Note For information about upgrading to Cisco Unified CallManager Release 3.3 or 4.0, refer to the appropriate version of the Upgrading Cisco Unified CallManager document.


New and Changed Cisco Unified CallManager Features

The following sections describe new and changed information that relates to Cisco Unified CallManager features:

Original Calling Party on Transfer

Hold Reversion

Advanced Ad Hoc Conference Features

MGCP T.38 Enhancements

SCCP Optimization

Connected Number Display

TFTP Enhancements

Original Calling Party on Transfer

When the Original Calling Party on Transfer feature gets enabled, the original calling party name and number display on calls that are transferred by using the Cisco Unity voice-messaging system.

Administrators enable this feature by setting the Cisco Unified CallManager service parameter, Display Original Calling Number on Transfer from Cisco Unity, to True. This parameter determines whether Cisco Unified CallManager displays the original calling party number for calls that are transferred from the Cisco Unity voice-messaging system. Valid values specify True (display the original calling number when a call is transferred from a Cisco Unity voice messaging port) or False (display the number of the Cisco Unity voice-messaging port through which the call was transferred). The default setting specifies False.

Where to Find More Information

Cisco Unified IP Phones, Cisco Unified CallManager System Guide

Hold Reversion

The Hold Reversion feature alerts a phone user when a held call exceeds a configured time limit. When the held call duration exceeds the limit, Cisco Unified Call Manager generates alerts, such as a ring or beep, at the phone to remind the user to handle the call. The held call becomes a reverted call when the hold duration exceeds the configured time limit.

For example, if you configure this feature to notify you when a call remains on hold past 30 seconds, Cisco Unified CallManager sends an alert, such as a ring or beep, to the phone after 30 seconds. You can also configure reminder alerts at configured intervals. A user can retrieve a reverted call on hold by going off hook, which deactivates the feature.

As administrator, you configure hold reversion timers and other feature settings in Cisco Unified CallManager Administration for the cluster or for a line.

The Hold Reversion Duration timer specifies the wait time before a reverted call alert is issued to the holding party phone.

The Hold Reversion Notification Interval timer specifies the frequency of the periodic reminder alerts to the holding party phone.

The Reverted Call Focus priority specifies which call type, incoming calls or reverted calls, has focus for user actions, such as going off hook.

Cisco Unified CallManager Administration Configuration Tips

Be aware that the clusterwide Hold Reversion Duration timer and Hold Reversion Notification Interval timer are required settings for Cisco CallManager service updates.

At installation, the Hold Reversion Duration timer specifies 0, which disables the feature.

You cannot configure hold reversion settings for directory numbers (DNs) that are associated with phones that do not support this feature.

Configure the Maximum Hold Duration Timer system setting to a value that is greater than 0; otherwise, a reverted call can remain on hold until the Maximum Call Duration Timer expires.

If you configure the Maximum Hold Duration Timer to a value that is less than the Hold Reversion Duration timer, the hold reversion feature does not activate.

If you leave either the Hold Reversion Duration timer setting or Hold Reversion Notification Interval timer setting blank in the Directory Number Configuration window, Cisco Unified CallManager uses the hold reversion timer settings for the cluster. If you configure a value for either timer (including 0) in the Directory Number Configuration window, Cisco Unified CallManager uses the timer settings for the line.

If you configure the Hold Reversion Duration timer for either the cluster or a line to a value that is greater than 0 but do not configure the Hold Reversion Notification Interval timer, Cisco Unified CallManager sends just one alert, when the call assumes the reverted state. If you configure the Hold Reversion Notification Interval timer for either the cluster or the line but do not configure Hold Reversion Duration timer to a value that is greater than 0, the hold reversion feature does not activate.

Only Cisco Unified IP Phones that support the hold reversion feature display the hold reversion timer settings in the Directory Number Configuration window. If a Cisco Unified IP Phone that supports hold reversion shares a line with a phone device that does not support hold reversion, the hold reversion configuration settings display only for the line on the supporting device.

If a shared line device disables this feature, hold reversion gets disabled on all other devices that share that line.

If the ring settings configured for the phone specify Disabled, the phone will not ring, flash, or beep for the hold reversion feature.

To fully disable the hold reversion feature after it is enabled, be sure to disable the Hold Reversion Duration timer on every line in addition to disabling the clusterwide settings.

GUI Changes

The following changed windows in Cisco CallManager Administration contain hold reversion configuration settings:

Device Pool Configuration—Contains the new Reverted Call Focus Priority settings.

Directory Number Configuration—Contains the new Hold Reversion Duration timer and Hold Reversion Notification Interval settings for a line.

Service or Enterprise Parameter Changes

The following new service parameters support hold reversion:

Hold Reversion Duration timer—Enables the call reversion feature and sets the reverted call alert timer for the cluster.

Hold Reversion Notification Interval—Sets the periodic reminder alerts for the cluster.

The Maximum Hold Duration Timer and Maximum Call Duration Timer service parameters interact with the hold reversion feature.

User Tips

When a user puts a call on hold, the Hold icon appears next to the caller ID and the corresponding line button flashes green.

If the Hold Reversion feature is enabled for a phone, calls left on hold will revert back to ringing on that phone after a certain length of time. These "reverting" calls remain on hold until the user resumes them.

The phone indicates the presence of a reverting call by:

Alerting the user at intervals with a single ring (or flash or beep, depending on your phone line setting).

Briefly displaying a "Hold Reversion" message in the status bar at the bottom of the phone screen.

Displaying the animated Hold Reversion icon next to the caller ID for the held call .

On Cisco Unified IP Phones 7971G-GE, 7970G, 7961G-GE, 7961G, 7941G-GE displaying a flashing amber line button (depending on the line state).

When the reverted call has focus, users can go of hook and retried the reverted call by:

Picking up the handset

Pressing the speaker button on the phone

Pressing the headset button

Selecting the line associated with the reverted call

Pressing the Resume softkey

Cisco Unified IP Phone Support

The following Cisco Unified IP Phones support the Hold Reversion feature:

7971G and 7971GE

7970G

7961G and 7961GE

7960G

7941G and 7941GE

7940G

7911G

7906G


Note Cisco Unified IP Phones require firmware version 8.0(3) or later for the hold reversion feature. An exception is Cisco Unified IP Phone 7960G and 7940G, that require firmware version 8.0(2) or later.


BAT Considerations

You can configure the Hold Reversion Duration timer and Hold Reversion Notification Interval timer on the line configuration window in the BAT phone template.

CTI Considerations

You can use hold reversion with some Cisco-provided applications, such as Cisco Unified CallManager Attendant Console. CTI applications can access hold reversion functionality when the feature is enabled for a line or the cluster. A new event, CtiCallHoldReversionEv, indicates when a held call becomes a reverted call on a CTI-monitored device. You can enable or disable this event through the CTI call event filter.

To enable this feature with CTI applications, ensure that the CTI application is certified to work with this feature and this Cisco Unified CallManager release. Otherwise, the CTI application may fail. Because existing CTI applications may be affected by hold reversion feature, the system disables this feature by default.

Where to Find More Information

Hold Reversion, Cisco Unified CallManager Features and Services Guide

Device Pool Configuration, Cisco Unified CallManager Administration Guide

The Cisco Unified IP Phone administration guides for Cisco Unified IP Phones that support hold reversion and this version of Cisco Unified CallManager

Cisco Unified IP Phone User Guides

Cisco Unified CallManager Locale Installer

Advanced Ad Hoc Conference Features

Enhancements to the ad hoc conference feature provide the following advanced capabilities:

A conference participant other than the controller can now add or remove participants.

Conference participants can now chain multiple ad hoc conferences together in linear or nonlinear fashion.

You can enable or disable these advanced capabilities by setting the value of two new service parameters.

When multiple conferences are chained together, all the participants can hear and talk to each other. However, the ConfList softkey does not display a full list of all the participants in all the chained conferences. ConfList can only display the participants in its own conference and displays a linked conference as "Conference". The conferences do not get merged into a single conference.

Service or Enterprise Parameter Changes

Two new Service Parameters support this feature enhancement:

This parameter determines whether advanced Ad Hoc conference features are enabled. Advanced Ad Hoc conference features include the ability for conference participants other than the conference controller to add new participants to an existing Ad Hoc conference, the ability for any non-controller conference participant to drop other participants from the conference via the ConfList and RmLstC softkey, and whether Ad Hoc conferences can be linked together using features such as conference, join, direct transfer, and transfer. Valid values specify True (allow advanced Ad Hoc conference features) or False (do not allow advanced Ad Hoc conference features).

Nonlinear Ad Hoc Conference Linking Enabled—This parameter determines whether more than two ad hoc conferences can link directly to an ad hoc conference in a nonlinear fashion. Nonlinear conference linking occurs when three or more ad hoc conferences link directly to one other ad hoc conference. Linear conference linking occurs when one or two ad hoc conferences link directly to one other ad hoc conference. For this parameter to work, ensure the Advanced Ad Hoc Conference Enabled service parameter is set to True. Valid values specify True (allow nonlinear conference linking, so three or more ad hoc conferences can link to a single other conference) or False (do not allow nonlinear conference linking; allow only linear linking).


Note Keep the Nonlinear Ad Hoc Conference Linking Enabled parameter set to the default value unless a Cisco support engineer instructs otherwise.



Caution When conferences are linked in nonlinear fashion and the Nonlinear Ad Hoc Conference Linking Enabled service parameter is set to true, the conference resources may not get released when all the real participants drop out of the conference, leaving the conference bridges connected to each other when no one is using the conference. This can happen because each conference only knows the participants that connect directly to its own conference bridge. The conferences cannot detect when all the real participants in the other conference dropped out. To reduce the risk of tying up unused conference resources, restart conference bridges more frequently.

Cisco Unified IP Phone Support

The following Cisco Unified IP Phones support the Advanced Ad Hoc Conference feature:

7971G and 7971GE

7970G

7961G and 7961GE

7941G and 7941GE

7960G

7940G

7912G

7911G

7906G

7905G

User Tips

Ad hoc conference enhancements allow any conference participant to add and remove conference participants and to join standard conferences the same way conference originators do.

To add new participants to an existing conference

From a connected call, press Confrn. (You may need to press the more softkey to see Confrn.)

Enter the participant phone number.

Wait for the call to connect.

Press Confrn again to add the participant to your call.

Repeat to add additional participants.

To remove any conference participant (press ConfListt, highlight the participant's name and press Remove).

To drop the last participant that was added to the conference (press RmLstC).

To join two standard conferences on the same line, press Join or DirTrfr.


Note Tell your users that you have enabled ad hoc conference enhancements.


CTI Considerations

CTI supports the following ad hoc conference feature enhancements:

Allow non controller participant in an ad hoc conference to add a new party by using the CTI interface and the phone interface.

CTI does not support dropping a conference participant from the CTI interface; however, you can drop a participant by using the phone interface.

Allows ad hoc conference chaining.

CAR/CDR Considerations

Cisco Unified CallManager now adds the requestor party (party that added the participant) to the CDR comment field because the requester can be a participant other than the controller. The tags for the requestor information specify ConfRequestorDn and ConfRequestorDeviceName.

Cisco Unified CallManager now adds the origConversationID field to the CDR in addition to the destConversationID field from previous releases, so the call that links two chained conference bridges includes a different conversation ID for each side of the call.

Cisco Unified CallManager now adds the requestor party (party that requested the removal of a participant) in the CDR comment field to track the drop requestor. The tags for the drop requestor information include DropConfRequestorDn and DropConfRequestorDeviceName.

Where to Find More Information

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager System Guide

Call Detail Record Definitions for Cisco Unified CallManager

Cisco Unified IP Phone User Guides

MGCP T.38 Enhancements

The 4.2.(3) Cisco Unified CallManager releases, T.38 fax relay adds the following support:

Cisco Unified CallManager supports CA-controlled MGCP T.38 fax relay.

Fax calls use T.38 in CA-controlled mode if IOS enables T.38 (default).

Fax calls use fax pass-through (or Cisco fax relay) if IOS disables T.38 (transparent to Cisco Unified CallManager).

Both H.323 and MGCP (IOS only) support T.38 fax relay. For T.38 fax relay interworking between H.323 gateways and MGCP gateways, ensure MGCP gateways are configured to operate in CA-controlled mode.

Cisco Unified CallManager Administration Configuration Tips

The minimum required release of MGCP GW specifies version 12.4.8.

If an MTP/Transcoder gets inserted in the T.38 call (regardless of protocol), the MTP/Transcoder must support T.38 codec mode. Currently, the only MTP/Transcoders that support T.38 codec mode and are compatible with Cisco Unified CallManager 4.2(3) are those provided by the C6K platform.

Using the supported IOS releases requires no specific configuration. Default IOS configuration works.

Ensure the following CLI does not exist in the IOS gateway configuration:

mgcp fax t38 inhibit (should not inhibit)

no mgcp package-capability fxr-package (need fxr-package)

You must establish fax calls initially as voice calls. In this release, no support exists for direct T.38 fax calls without first setting up the media as an audio stream.

No reversion to voice mode occurs when the fax transmission completes. Cisco Unified CallManager waits for the call to be cleared by either side through control messages such as H.225 Release Complete message, Q.931 Disconnect message, or other signaling protocol messages.

IOS Configuration Tips

The default IOS configuration supports T38 fax relay, as long as the IOS is version 12.4(7.12) or 12.4(7.14)T or later. Ensure the IOS MGCP gateway is configured to operate in CA-controlled MGCP T.38 fax relay mode.

To double check for support, review the IOS gateway configuration to ensure that the following CLI is present:

no mgcp fax t38 inhibit

mgcp package-capability fxr-package

Be aware that the IOS MGCP gateway may be configured to fall back to H323 mode when Cisco Unified CallManager fails. If such configuration is enabled, the MGCP call preservation feature that is normally expected in a multinode cluster does not function if no Cisco Unified CallManager is available. To avoid nonfunctional call preservation feature, disable the fallback to H323 mode by using the following command:

no ccm-manager fallback-mgcp

Where to Find More Information

Cisco Unified CallManager Administration Guide

Cisco Unified CallManager System Guide

Cisco IOS Fax and Modem Services over IP Application Guide

SCCP Optimization

Because this feature consumes resources, ensure this feature gets enabled only when you are getting signaling delays for SCCP phones. Most users do not require this option.

Cisco Unified CallManager sends the bundled messages to the phone when the station buffer is full, as soon as it receives a media-related message, or when the Bundle Outbound SCCP Messages timer expires.


Note For Cisco Unified IP Phones 7960G and 7940G, the firmware version that supports improved SCCP messaging specifies 8.0(2).


In SCCP Version 9, SCCP message structures get altered to allow variable- length messages instead of a fixed-length character array that consumes bandwidth.

Cisco Unified CallManager Administration Configuration Tips

To specify a setting other than the default setting (100 msec) for the Bundle Outbound SCCP Messages timer, configure a new value for the cluster in the Service Parameters Configuration window for the Cisco Unified CallManager service. The range specifies 15 msec to 500 msec.

GUI Changes

The Phone Configuration window contains a new Remote Device check box in the Device Information section that identifies a phone as a remote device during registration and enables the SCCP Optimization feature when checked.

Service or Enterprise Parameter Changes

The Bundle Outbound SCCP Messages timer represents a new service parameter that sets a time limit for holding buffered messages if the buffer is not yet full.

Cisco Unified IP Phone Support

The following Cisco Unified IP Phones support SCCP optimization:

7971G and 7971GE

7970G

7961G and 7961GE

7960G

7941G and 7941GE

7940G

7920

7912G

7911G

7906G

7905G

CTI Considerations

This feature applies only to remote phones; therefore, no CTI considerations associate with this feature in this release.

Where to Find More Information

Cisco Unified IP Phone Configuration, Cisco Unified CallManager Administration Guide

Connected Number Display

When a call routes through a translation or route pattern, routes to a Call Forward All or Call Forward Busy destination, or gets redirected through a call transfer or CTI application, the connected number display updates to show the modified number or redirected number.

The Connected Number Display restriction restricts the connected line ID presentation to dialed digits only for the duration of the call.

Cisco Unified CallManager Administration Configuration Tips

To turn off phone display updates, so the phone displays only the dialed digits, set the Cisco Unified CallManager service parameter, Always Display Original Dialed Number, to True.

Service or Enterprise Parameter Changes

The Always Display Original Dialed Number new service parameter enables the connected number display restriction, which ensures privacy and blocks connected number updates for redirected calls. The default value for this setting specifies False.

User Tips

Only Cisco Unified SCCP IP Phones that support this version of Cisco Unified CallManager support dialed number display.

The connected number display restriction applies to all calls that originate in the cluster. When set to true, this setting interacts transparently with existing Cisco Unified CallManager applications, features, and call processing. The setting applies to all calls that terminate inside or outside the cluster.

CTI Considerations

When this feature is enabled, calls that are routing to a CTI route point display only the dialed digits on the originating phone.

Security Considerations

This feature addresses customer privacy issues as well as connected number ID number displays that are meaningless to phone users.

Where to Find More Information

Call Display Restrictions, Cisco Unified CallManager Features and Services Guide

TFTP Enhancements

TFTP enhancements include support for centralized TFTP in a multiple cluster environment.

Centralized TFTP in a Multiple Cluster Environment

A Centralized TFTP server supports multiple clusters within one large campus environment. The Centralized TFTP server design allows phones to be moved within a campus. It also supports a mixed OS multicluster environment.

Devices that are registered and configured in any cluster can be directed to a single TFTP server (Centralized TFTP server) that will then serve files to those devices. The following sections describe how the Centralized TFTP server works in a Cisco Unified CallManager multicluster environment:

Master TFTP Server

Alternate File Locations

Sending Files to the Master TFTP Server

Centralized TFTP with Secure Clusters

Configuration Tips for Centralized TFTP

Master TFTP Server

You can configure a single TFTP server to build the configuration files for devices in its cluster to serve all security, firmware, and configuration files to those devices. This single server, a Master TFTP Server, serves files from all other Cisco Unified CallManager clusters. The TFTP server in the other clusters, which are considered off-cluster TFTP servers, will build files only for devices that are configured for that particular cluster. All endpoint requests get sent to the Master TFTP Server, either by hard coding or by DHCP configuration at the endpoint.

The Master TFTP Server queries off-cluster TFTP servers if the requested file is not found locally. When the Master TFTP Server receives a file request, it looks first in its local caches and hard disk for the requested file. If the file does not exist there, then the Master TFTP Server will request the file from the off-cluster TFTP servers in sequential order. The request will eventually time out if the response is not received within a set time.

Alternate File Locations

To enable Centralized TFTP, you must configure the parameters for the Alternate File Locations only on the Master TFTP Server. You can specify up to 10 Alternate File Locations by using the TFTP service parameter window. For more information on service parameters, refer to the Service Parameters Configuration in the Cisco CallManager Administration Guide.

You can use either of the following syntax examples:

host://<IP of the off-cluster TFTP server> (for example, host://10.10.134.24)

HOST://<IP of the off-cluster TFTP server> (for example, HOST://10.10.134.24)

If network DNS resolution is also supported, you can also use one of the following syntax examples:

HOST://<name of the off-cluster TFTP server> (for example, HOST://cluster2-tftp)

HOST://<name of the off-cluster TFTP server> (for example, HOST://cluster3-tftp)

You must use the format of the preceding syntaxes.

Sending Files to the Master TFTP Server

When an off-cluster TFTP server receives a request from the Master TFTP Server, it searches for the file and, if found, sends the requested file back to the Master TFTP Server by using HTTP. The Master TFTP Server then uses TFTP to send the requested file to the device that originally requested the file. Should the off-cluster TFTP server not have the requested file, it will respond to the Master TFTP Server with "File Not Found" (HTTP Error 404). The Master TFTP Server continues the process with the next off-cluster TFTP server until either the file is located or no remaining options exist.

When the off-cluster server is busy, it sends "HTTP Error 503" to the Master TFTP Server, so it should try the request again later. This message will also get sent to the endpoint device that made the original request.

Centralized TFTP with Secure Clusters

All off-cluster servers that are operating in secure mode must add the Master TFTP Server or servers IP address to the cluster's CTL file. (Without this updated CTL file, phones that register to a cluster where security is enabled and that attempt to download their configuration files will fail.) After the CTL file is updated, reboot the servers, so they can participate in the secure Centralized TFTP environment.

To update the CTL file for the TFTP servers, download the CTL Client plug-in by using Application > Install Plugins from Cisco Unified CallManager Administration. For more information about the CTL client and how to configure TFTP for security, refer to the Cisco Unified CallManager Security Guide.

Configuration Tips for Centralized TFTP

The following list comprises tips to remember when you are configuring a centralized TFTP environment:

Only the Master TFTP Server gets configured with alternate file locations.

Off-cluster TFTP servers must have no alternate file locations configured.

You can configure 1 to 10 Alternate File Locations in the Cisco TFTP Service Parameters Configuration window. If Alternate File Location 1 contains an empty parameter value, TFTP will stop searching for alternate servers. For example, if Alternate File Locations 2 through 10 are configured, Location 1 is empty, and TFTP is searching for servers, it will not search Alternate File Locations 2 through 10.

If autoregistration is enabled in the Cisco Unified CallManager cluster where the Master TFTP Server resides, phones that are configured in the Cisco Unified CallManager cluster where the off-cluster TFTP server phones reside may inadvertently get configured in the same Cisco Unified CallManager cluster where the Master TFTP Server resides. This scenario could occur when an Off-cluster TFTP Server may be busy rebuilding its configuration files at the same time that a phone requests its configuration file.

Where to Find More Information

Cisco TFTP, Cisco Unified CallManager System Guide

New and Changed Information for Cisco Unified IP Phones

This section provides information about the following topics:

Cisco Unified IP Phone 7906G

Cisco Unified IP Phone Support for Cisco CallManager 4.2(3) Features

Cisco Unified IP Phone 7906G

The system supports Cisco Unified IP Phone 7906G, a new basic phone, on Cisco Unified CallManager release 4.1(3) and later. The Cisco Unified IP Phone 7906G supports IEEE 802.3af inline power, security, and other phone features including Group Listen.Supported Cisco Unified IP Phones

Where to Find More Information

Cisco Unified IP Phone 7906G Installation Guide

Cisco Unified IP Phone 7906G and 7911G Phone Guide

Cisco Unified IP Phone 7906G and 7911G Administration Guide

Cisco Unified IP Phone Support for Cisco CallManager 4.2(3) Features

Table 1 lists Cisco Unified IP Phones and the new Cisco Unified CallManager 4.2(3) features they support.


Note The following phones operate with Cisco Unified CallManager 4.2(3); however, they do not support new Cisco Unified CallManager 4.2(3) features: Cisco Unified IP Phones 7985G, 7936, 7935, Cisco Gateway VG248, and Cisco ATA 186 and 188New Features Supported by Cisco Unified CallManager Release 4.2(3)


.

Table 2 Cisco Unified IP Phone Support for Cisco Unified CallManager 4.2(3) Features

Cisco Unified CallManager 4.2(3) Feature
Cisco Unified IP Phone Support
For more information

Hold Reversion

7971G and 7971GE
7970G
7961G and 7961GE
7960G
7941G and 7941GE
7940G
7911G
7906G

See the Table 1"Hold Reversion" section.

Ad Hoc Conference

7971G and 7971GE
7970G
7961G and 7961GE
7960G
7941G and 7941GE
7940G
7912G
7911G
7906G
7905G

See the "Advanced Ad Hoc Conference Features" section.

SCCP Optimization

7971G and 7971GE
7970G
7961G and 7961GE
7960G
7941G and 7941GE
7940G
7920
7912G
7911G
7906G
7905G

See the "SCCP Optimization" section.

MLPP Supplementary Services

7971G and 7971GE
7970G
7961G and 7961GE
7960G
7941G and 7941GE
7940G
7911G
7906G

See the "Multilevel Precedence and Preemption (MLPP) Supplementary Services" section.



Note For information about these features, see "New and Changed Cisco Unified CallManager Features" section.


MLPP Supplementary Services


Note For information about MLPP Supplementary Services, see "Multilevel Precedence and Preemption (MLPP) Supplementary Services" section.


Cisco Unified CallManager Applications

The following sections describe the Cisco Unified CallManager 4.2(3) applications enhancements:

Cisco Extension Mobility Enhancement

Multilevel Precedence and Preemption (MLPP) Supplementary Services

Cisco Extension Mobility Enhancement

The Cisco Extension Mobility enhancement eliminates the phone dependency on phone button templates.The following factors determine this model equivalency between the various phones:

Various features that are supported by the phone

Number of buttons supported on the phone

The Cisco Extension Mobility enhancement introduces two support features for the Cisco Unified IP Phones:

Support Feature Safe on phone button template

Phones can use any phone button template that has the same number of buttons that the phone supports.

In Release 4.2(3), Cisco Unified IP Phone 7970 and 7971 act as Feature Safe to each other.

Support Size Safe on phone button template

Phones can use any phone button template that is configured in Cisco Unified CallManager Administration regardless of the number of buttons that the phone supports.


Note No Cisco Unified IP Phones currently support Size Safe feature.


Cisco Unified CallManager Administration Configuration Tips

The following sections provide configuration scenarios that are using the Extension Mobility enhancement.

Configuration Scenario - 1

1. 1. Use the User Device Profile Configuration window to create a 7970 User Device Profile that is called `User Profile Test' that uses the 7970 Phone Button Template and configure it with the following lines:

DN: 1050, 1051 and 1052

Speed Dial: 5051, 5052, 5053, 5054 and 5055

2. Use the User Configuration window to create a user that is named `cisco' and associate the User Device Profile that is called User Profile Test with this user.

3. Use the Phone Configuration window to configure a Cisco Unified IP Phone 7970 and a Cisco Unified IP Phone 7971 with extension mobility and configure each phone to use the Standard Phone Button Template.

4. When the user logs in to a Cisco Unified IP Phone 7970 with the User Profile User Profile Test, all the lines (DNs) and speed dials display on the phone screen.

5. When the user logs in to a Cisco Unified IP Phone 7971 with the User Profile User Profile Test, only the lines (DNs) display on the phone screen.

Configuration Scenario - 2

1. Use the Phone Button Template Configuration window to create a 7971 Phone Button Template that is called `7971 Test' with the following lines:

8-Line / 0-Speed Dial

2. Use the Device Profile Default Configuration window to associate the `7971 Test' Phone Button Template with a Cisco Unified IP Phone 7971.

3. Use the Phone Configuration window to configure a Cisco Unified IP Phone 7971 with extension mobility.

4. When the user logs in to a Cisco Unified IP Phone 7971 with User Profile Test, only the lines (DNs) display on the phone screen.

Where to Find More Information

Cisco Extension Mobility, Cisco Unified CallManager Features and Services Guide

Cisco Unified IP Phone Configuration, Cisco Unified CallManager Administration Guide

Default Device Profile Configuration, Cisco Unified CallManager Administration Guide

Device Profile Configuration, Cisco Unified CallManager Administration Guide

Phone Button Template Configuration, Cisco Unified CallManager Administration Guide

Multilevel Precedence and Preemption (MLPP) Supplementary Services

MLPP Supplementary Services supports the following features:

MLPP Support for Multiple Appearance Lines—The system currently supports MLPP support for multiple appearance lines.

Call Forwarding—Ensure no precedence calls are forwarded to off-net endpoints (for example, cell phones). Additionally, ensure forwarded calls retain the original precedence across multiple forwarding hops.

For CFA (Call Forward All) scenarios, precedence calls will get routed to the AP target of the original called party immediately. The CFA target does not get used for MLPP calls.

For CFB (Call Forward Busy) scenarios, precedence calls will get forwarded to the configured CFB destination, subject to the hop count limits that were previously described and the state of open appearances on the called party endpoint.

For the CFNA (Call Forward No Answer) scenario, the system attempts a single forward attempt (hop) to the CFNA target of the original called party. If that endpoint does not answer prior to the no answer timer expiring, the call then gets sent to the MAP target of the original called party.

Three-Way Calling—The three-way calling enhancement allows each connection of a three-way call to maintain its original precedence level. The phone that is performing the split operation of the three-way call uses the higher precedence level of the two calls when different precedence levels are used. This enhancement also supports preemption of conference bridge resources. If a conference bridge is saturated with calls, individual streams gets preempted when a new, higher precedence, three-way call gets set up.

Transfer— When a call transfer is made at different precedence levels, the switch that initiates the transfer class marks the connection at the highest precedence level of the two segments.

This enhancement upgrades the precedence level of a call leg that is involved in a transfer operation. For example, party A calls party B at Priority. Party B then initiates a transfer to C and dials the Flash precedence digits when dialing. When the transfer completes, the precedence level of party A gets upgraded from Priority to Flash.


Note The precedence level upgrade does not work over ICT or PRI trunks.


Call Pickup—This enhancement adds the criteria of highest precedence to the call pickup algorithm. The enhancement includes the following requirements:

If a call pickup group has more than one party in an unanswered condition, and the unanswered parties are at different precedence levels, a call pickup attempt in that group will retrieve the highest precedence call first.

If multiple calls of equal precedence are ringing simultaneously, a call pickup attempt in that group will retrieve the longest ringing call first.

This release supports group pickup functionality for MLPP calls. Operation follows normal call pickup functionality.

For MLPP calls, this release does not support Other Group Pickup.

Hunt Pilot/Hunt List—Normal hunt algorithm logic occurs until all lines in the hunt group are busy. When all lines are busy, the lowest precedence call gets selected for preemption. When preemption occurs, normal line group `no answer' timer continues. When timer expires, next lowest precedence call in hunt group gets selected for preemption. MLPP enhancements support the following three hunt algorithms:

Top down

Longest idle time

Circular

Cisco Unified CallManager allows multiple line groups to be configured for a hunt group.

Cisco Unified CallManager Administration Configuration Tips

Keep the following tips in mind.

MLPP support for multiple appearance lines.

Cisco recommends, but does not require, Cisco Unified IP Phones be set with max calls=4 and busy trigger=2.

The system does not support assigning the same DN twice to the same station by using multiple partitions when interacting with MLPP supplemental services.

Ensure the `Auto Line Select' option gets disabled for all Cisco Unified IP Phones because the highest precedence call may not be answered when multiple alerting calls are incoming.

Call Forwarding—All MLPP endpoints include a configured MAP (MLPP Alternate Party) target directory number. Usually the attendant number gets used as a `last resort' destination for forwarded MLPP calls. If the endpoint does not follow the prescribed configuration when a MAP is needed, the MLPP call originator receives a reorder tone that indicates that the called party configuration does not include the required MAP configuration. This tone only gets received if the call would have been directed to the attendant when no other forwarding options are available or configured.

Three-Way Calling

The Maximum Ad Hoc Conference service parameter gets set to 3. This limits ad hoc calls to three participants.

Activate the Cisco IP Voice Media Streaming App service to service three-way calls. Do not use the IOS DSP form to service conference calls.

MLPP three-way calls do not interoperate with the conference chaining features that are in Release 4.2.

Transfer—No configuration requirements exists for transfer. This feature gets enabled automatically when MLPP is enabled, and the phones support the Transfer softkey.

Cisco Unified IP Phone Support

The following Cisco Unified IP Phones support MLPP enhancements:

7971G and 7970GE

7970G

7961G and 7961GE

7960G

7941G and 7941GE

7940G

7911G

7906G

User Tips

An MLPP-enabled call now retains its priority and preemptive status when you

Put the call on hold

Transfer the call

Add the call to a three-way conference

Answer the call by using PickUp

Serviceability Considerations

Activate the IP Voice Media Streaming App service to service three-way calls.

Where to Find More Information

Cisco Unified IP Phone User Guides

MultiLevel Presence and Preemption, Cisco Unified CallManager Features and Services Guide

Service Activation, Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Bulk Administration Tool Features

Cisco Unified CallManager Bulk Administration Tool (BAT), a web-based application, performs bulk transactions to the Cisco Unified CallManager database. This section introduces the changes to BAT for Cisco Unified CallManager 4.2.

Cisco Unified CallManager Administration Configuration Tips

The following configuration tips apply.

Install BAT from the Applications > Plugins window.

GUI Changes

Phone and UDP Configuration windows

Added Hold Reversion Notification Interval setting for a line.

Added support for Feature-safe and size safe models

BAT Performance

Table 1 lists the performance values for various BAT transactions.


Note The following performance data occurs at laboratory conditions, and this data can change depending on Cisco Unified CallManager activity. Off-peak hour numbers only provide an approximate guidance to judge the overall time for transaction.


Table 3 BAT Performance Measures for Various Transactions

Transaction
Records Processed/Minute
Forced Authorization Codes

Insert FAC

200

Delete FAC

500

Client Matter Codes

Insert CMC

250

Delete CMC

500

Call Pickup Groups

Insert CPG

200

Delete CPG

500

Phones/Users

Validate Phones/Users

100

Insert Phones/Users

15

Users

Insert Users

150

Update Users

65

Reset Password/PIN Query

500

Reset Password/PIN Custom

350

Generate User Reports

500

Export Users - Specific

250

Export Users - All

200

Delete Users - Query

300

Delete Users - Custom

300

Manager Assistants

Manager/Assistant Insert

75

Manager/Assistant CSV-Based Delete

300

Manager/Assistant Query-Based Delete

300

Manager/Assistant Custom File-Based Delete

300

UDP Transactions

Validate UDP

300

Insert UDP Specific Details

65

Export All Details

50

Add lines UDP

75

Report UDP

125

Delete UDP

70

Phone Transactions

Validate Phones

250

Insert Specific Phones

45

Export All Details

75

Update Phones

150

Add lines for Phones

75

Reset/Restart Phones

500

Generate Phone Reports

300

Delete Phones (Query)

75


New and Changed Information for Cisco Unified CallManager Serviceability

Cisco Unified CallManager Release 4.2(3) provides the following enhancement to Serviceability:

Addition of a New Alarm and Alert to Detect Failed Login Attempts for MLA Accounts

Cisco Unified CallManager 4.2(3) adds a new alarm that is generated when the system detects failed login attempts on any MLA accounts. By default, the new MLAUserLoginFailed alarm gets sent to the Sys Log, Event Log and RIS (Real-time Information System) Data Collector. You can use a corresponding precanned alert, MLAUserLoginFailed, which is configurable by using RTMT (Real-Time Monitoring Tool) to send e-mail to an administrator when the number of login failures exceeds a configured threshold. This alert gets enabled by default. Administrators can enable and disable this alert and set the threshold, frequency, e-mail settings, and other properties for the MLAUserLoginFailed alert in Alert Central in RTMT.

You can view the Alarm Definition Details for the MLAUserLoginFailed alarm by choosing Alarm > Definitions in Cisco Unified CallManager Serviceability and searching for theMLAAlarmCatalog.

Where to Find More Information

Cisco Unified CallManager Serviceability Administration Guide

Cisco Unified CallManager Serviceability System Guide

New and Changed Information for Third-Party API

This following sections describe new features and changes that are pertinent to this release of Cisco Unified CallManager and third-party APIs.

CDR Definitions

Cisco Unified JTAPI Developers Guide for Release 4.2(3)

Cisco Unified TAPI Developers Guide for Release 4.2(3)

CDR Definitions

Advanced Ad Hoc Conference

Changes for CDR for the advanced ad hoc conference enhancements include:

The addition of origConversationID to the CDR supports the advanced ad hoc conference enhancements. This field identifies the conference ID that is associated with the originating leg of the call. In most cases, this field equals 0. Default equals 0. For conference chaining scenarios, the origConversationID and destConversionID fields identify which conferences are chained together.

The party that added the participant, known as the requestor party, appears in the CDR comment field. The following tags apply for the requestor information: ConfRequestorDn and ConfRequestorDeviceName.

Cisco Unified JTAPI Developers Guide for Release 4.2(3)

Cisco Unified JTAPI previously got upgraded whenever Cisco Unified CallManager was upgraded. With the 4.2 versions of Cisco Unified CallManager, Cisco Unified JTAPI does not need to be upgraded if your application does not use any of the new features that are introduced in the 4.2 release. Cisco JTAPI for Cisco Unified CallManager Release 4.1 will work with Cisco Unified CallManager release 4.1, if the 4.2 features are not enabled.

Cisco Unified JTAPI from the 4.2 versions of Cisco Unified CallManager does not work with earlier versions of Cisco Unified CallManager. If Cisco Unified CallManager is downgraded from version 4.2 to version 4.1, you need to downgrade Cisco Unified JTAPI as well.

Cisco Unified JTAPI for Cisco Unified CallManager Release 4.2(3) introduces the following new features:

Advanced Ad Hoc Conference

You can disable this feature, which is backward compatible, as long as the feature is disabled through a systemwide service parameter called Advanced Ad hoc Conference. When the feature is enabled and conference chaining is done on application-controlled devices, the system might require applications to make changes to handle conference chaining events

The Conference Add enhancement includes the following changes:

In this release Cisco Unified JTAPI exposes a new method, getOriginalConferenceControllerAddress(), to return the terminal connection of the original controller. This method exists on the CiscoConferenceStartedEv.

The getConferenceControllerAddress() method will return the requestor, which is the latest party to add a member to the conference. When the conference call is initially set up, the requestor specifies the same as the controller.

The Conference Chaining enhancement includes the following changes:

Cisco Unified JTAPI does not provide CiscoConferenceStarted/Ended and CiscoTransferStarted/Ended events when two conferences are chained together by DirectTransfer, Transfer, Join, or Conference.

Cisco Unified JTAPI provides an interface on CiscoCall to identify chained conference calls and return enumerated chained conference connections.

Cisco Unified JTAPI creates a connection for the conference chain link when a chained conference is created. The system provides this event with CAUSE_CONFERENCE when a conference chain is created through conference and with CAUSE_TRANSFER when a conference chain is created by transfer.

Cisco Unified JTAPI provides a CiscoCallChangedEv event when the last conference participant is moved to another conference in the chain. Events get provided with CAUSE_CONFERENCE.

Cisco Unified JTAPI provides a CiscoCallChangeEv event when a party is added to a chained conference call by using consult/conference steps and also for the case where more than two calls are joined together, when more than one call is a conference call.

Cisco Unified JTAPI provides CiscoConferenceChainAddedEv event to application when a conference chain is added to the call.

Cisco Unified JTAPI provides CiscoConferenceChainRemovedEv event to application when a conference chain is removed from the call.

Refer to the Cisco Unified JTAPI Developers Guide for Release 4.2(3) for the complete details of advanced ad hoc conference implementation in this release.

Hold Reversion

Cisco Unified CallManager supports hold reversion on Cisco SCCP IP Phones. The Hold Reversion feature only applies to the user hold; it does not apply to the network hold or hold that results from a feature invocation.

After a holding party puts a call on hold for a certain length of time, the holding party receives a hold reversion notification ring and a prompt display message. The user can do any of the following things to retrieve the held call:

Pick up the hand set

Press the speaker button

Press the headset button

Select the line on which the call is held and then press the resume softkey.

Be aware that the "Hold Reversion Duration Timer" and the "Hold Reversion Interval Timer" are both line based and Service parameter based. You can configure call focus priority as Device Pool based.


Note Enabling this feature could break CTI applications that have not been certified with this release. Verify that any CTI applications (Cisco or third party) are certified to work with this feature.


Hold reversion will not affect Transfer/Conference feature operations. Hold reversion will happen only for the call that the user puts on hold.

Cisco Unified JTAPI provides CiscoCallCtlTermConnHeldReversionEv to an application when hold reversion occurs.

To get a CiscoCallCtlTermConnHeldReversionEv, applications need to add CallObserver.

JTAPI call state, connection state, and terminal connection state remain unchanged when hold reversion occurs.

Cisco Unified TAPI Developers Guide for Release 4.2(3)

The new features that are introduced in Cisco Unified TAPI for Cisco Unified CallManager Release 4.2(3) follow:

Advanced Ad Hoc Conference

This feature remains backward compatible as long as the feature is disabled. You can disable the feature through a system-wide service parameter called "Advanced Ad hoc Conference." When the feature is enabled and conference chaining is done on application-controlled devices, applications must make changes to handle conference chaining scenarios because chained conference bridge will appear as normal conference participant.

The following requirements assume that the system-wide service parameter is enabled unless otherwise specified:

TAPI must allow a non-Controller to add a party to a conference

TAPI must specify that lineGetCallStatus for non-Controllers have a dwCallFeatures that includes PREPAREADDCONF

TAPI must provide a unique identifier for chained conference calls in the connected ID field

Refer to the Cisco TAPI Developers Guide for Cisco Unified CallManager for Release 4.2(3) for the complete details of the advanced ad hoc conference implementation in this release.

Hold Reversion

When Hold Reversion occurs on a call, the application that is monitoring the line will receive a LINE_CALLDEVSPECIFIC event with the hold reversion indication. However, the hold reversion LINE_CALLDEVSPECIFIC will be sent only once to the TAPI application even though there could be multiple hold reversion reminder tones on the phone when hold reversion interval timer times out.

The Hold Reversion feature will not change the TAPI call state.

The application has to set the Hold Reversion flag on a particular line in order to receive Hold Reversion notification on that line. The Hold Reversion flag on a line can be set using the cCiscoLineDevSpecificSetStatusMessage. In case the application sets the Hold Reversion flag for a line after the hold reversion has occurred on that line, then the application will still get the Hold Reversion notification for that particular call, if the call is still On Hold.

Please refer to the Cisco TAPI Developers Guide for Cisco Unified CallManager Release 4.2(3) for the complete details of the Hold Reversion implementation in this release.

Installation Notes

For complete installation information, refer to the following document:

Installing Cisco Unified CallManager Release 4.2(3)

For installation information specific to Cisco Unified CallManager Release 4.2(3), see the following sections:

System Requirements

Cisco Unified CallManager 4.2(3) Installation and Upgrade Guidelines

Operating System Installation Guidelines

Upgrading to Cisco Unified CallManager Release 4.2(3)

Limitations and Restrictions

You can find which application versions are compatible with Cisco Unified CallManager Release 4.2(3) and which previous release of Cisco Unified CallManager has upgrade support by referring to the Cisco Unified CallManager Compatibility Matrix at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm


Note Be aware that the release of Cisco Unified IP telephony products does not always coincide with Cisco Unified CallManager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CallManager Release 4.2(3). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco Unified IP telephony products.


Important Notes

The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager Release 4.2(3).

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled

Using MICs for Phone Authentication

CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later

In previous releases, during the Unified CM installation, the installxml.vbs VB script got used to parse all the display instances and rules in the XML files, and upload the data into a table in the default database. In Unified CM Release 3.3 and later, the DBInstall.dll function CInstallXML performs the parsing of the XML files.

The troubleshooting guide for Cisco Unified CallManager (and Cisco CallManager) suggests that you can initialize the installxml.vbs script to fix problems with blank parameters after an upgrade. Do not initialize the installxml.vbs script as the troubleshooting guide recommends. Initializing the script erases all service parameters on the server.


Caution Cisco Unified CM releases 3.3.x or later do not use the installxml.vbs script. Running this script erases all Service Parameters in the server.

Configuring Regions (Region Relationship) for SIP Devices with the MTP Required Option Enabled

When you configure a region relationship, you must ensure that you choose an audio codec that has sufficient bandwidth for all the devices that will be used in a call. This includes configuring the codec for devices that will be in the same region as well as devices that are in different regions. When you configure a trunk or third-party phone to use the SIP protocol and Media Termination Point Required is enabled, Cisco Unified CallManager Administration only allows you to choose a G.711 codec in the MTP Preferred Originating Codec field. When you assign the SIP trunk or third-party SIP phone with the MTP Required option enabled to the device pool for that region, you must verify that the region relationship between the SIP device and the MTP device is configured to use a codec with equal or greater bandwidth (G.711 or wideband codec).

Using MICs for Phone Authentication

Cisco recommends that you use manufacturer-installed certificates (MICs) for LSC installation only. Cisco supports LSCs to authenticate the TLS connection with Cisco Unified CallManager. Because MIC root certificates can be compromised, customers who configure phones to use MICs for TLS authentication or for any other purpose do so at their own risk. Cisco assumes no liability if MICs are compromised.

Caveats

This section contains information about resolved and open caveats for Cisco Unified CallManager, Release 4.2(3), and instructions for using the online tools that will help you monitor the current status of caveats in the following sections:

Resolved Caveats for Cisco Unified CallManager - Release 4.2(3)

Open Caveats for Cisco Unified CallManager - Release 4.2(3)

Resolved Caveats for Cisco Unified CallManager - Release 4.2(3)

You can find the latest resolved caveat information for Cisco Unified CallManager Release 4.2(3) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.


Tip You need an account with Cisco.com (Cisco Connection Online) to use Bug Toolkit to find open and resolved caveats of any severity for any release.

To access Bug Toolkit, log on to the following URL:
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl


This section includes the following topics:

Using Bug Toolkit

Saving Bug Toolkit Queries

Using Bug Toolkit

To access Bug Toolkit, you need the following items:

Internet connection

Web browser

Cisco.com user ID and password

To use Bug Toolkit, follow this procedure.

Procedure


Step 1 To access the Bug Toolkit, go to the following URL:
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

Log on with your Cisco.com user ID and password.

Step 2 Click the Launch Bug Toolkit hyperlink.

Step 3 If you are looking for information about a specific caveat, enter the ID number in the Enter known bug ID: field.

To view all caveats for Cisco Unified CallManager, go to the "Search for bugs in other Cisco software and hardware products" section, and enter Cisco Unified CallManager in the Product Name field. Alternatively, you can scroll through the product name list and click Cisco Unified CallManager.

Step 4 Click Next. The Cisco Unified CallManager search window displays.

Step 5 Choose the filters to query for caveats. You can choose any or all of the available options:

a. Choose the Cisco Unified CallManager version:

Choose the major version for the major releases (such as, 4.2, 4.1, 4.0).

A major release contains significant new features, enhancements, architectural changes, and/or defect fixes.

Choose the revision for more specific information; for example, choosing major version 4.2 and revision version 1 queries for release 4.2(3) caveats.

A revision (maintenance) release primarily contains defect fixes to address specific problems, but it may also include new features and/or enhancements.

b. Choose the Features or Components to query; make your selection from the "Available" list and click Add to place your selection in the "Limit search to" list.

To query for all Cisco Unified CallManager caveats for a specified release, choose "All Features" in the left window pane.


Note The default value specifies "All Features" and includes all of the items in the left window pane.


To query only for Cisco Unified CallManager-related caveats, choose "ciscocm" and then click Add.

To query only for phone caveats, choose "ciscocm-phone" and then click Add.

To query only for gateway caveats, choose "voice-gateway" and then click Add.

c. Enter keywords to search for a caveat title and description, if desired.


Note To make queries less specific, use the All wildcard for the major version/revision, features/components, and keyword options.


d. Choose the Set Advanced Options, including the following items:

Bug Severity level—The default specifies 1-3.

Bug Status Group—Check the Fixed check box for resolved caveats.

Release Note Enclosure—The default specifies Valid Release Note Enclosure.

e. Click Next.


Bug Toolkit returns the list of caveats on the basis of your query.

You can modify your results by submitting another query and using different criteria.

You can save your query for future use. See the "Saving Bug Toolkit Queries" section.


Note For detailed online help with Bug Toolkit, click Help on any Bug Toolkit window.


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 Perform your search for caveats, as described in the "Using Bug Toolkit" section.

Step 2 In the search result window, click the This Search Criteria button that displays at the bottom of the window.

A new window displays.

Step 3 In the Name of saved search field, enter a name for the saved search.

Step 4 Under My Bug Groups, use one of the following options to save your defects in a bug group:

Click the Existing group radio button and choose an existing group name from the drop-down list box.

Click the Create new group named: radio button and enter a group name to create a new group for this saved search.


Note This bug group will contain the bugs that are identified by using the search criteria that you have saved. Each time that a new bug meets the search criteria, the system adds it to the group that you chose.


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 Under Email Update Options, you can choose to set optional e-mail notification preferences if you want to receive automatic updates of a bug status change. Bug Toolkit provides the following options:

Do NOT send me any email updates—If you choose this default setting, Bug Toolkit does not send e-mail notifications.

Send my updates to:—Click the radio button to choose this option to send e-mail notifications to the user ID that you enter in this field. Additional notification options include

Updates as they occur—Bug Toolkit provides updates that are based on status change.

Weekly summaries—Bug Toolkit provides weekly summary updates.

Apply these email update options to all of my saved searches—Check this check box to use these e-mail update options for all of your saved searches.

Step 6 To save your changes, click Save.

Step 7 A window displays the bug group(s) that you have saved. From this window, you can click a bug group name to see the bugs and the saved searches; you can also edit the search criteria.



Note For complete Cisco Unified IP Phone firmware release note information, refer to the applicable firmware release notes for your specific IP phone at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/


Open Caveats for Cisco Unified CallManager - Release 4.2(3)

Table 4 describes possible unexpected behaviors by Cisco Unified CallManager Release 4.2(3), sorted by component. Unless otherwise noted, these caveats apply to all Cisco Unified CallManager 4.x releases up to and including Cisco Unified CallManager Release 4.2(3).


Tip For more information about an individual defect, click the associated Identifier in Table 4 to access the online record for that defect, including workarounds.


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 Unified CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified 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 Unified 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 Unified CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.

003.003(002.079) = Cisco Unified CallManager Release 3.3(3)

003.003(003.144) = Cisco Unified CallManager Release 3.3(4)

004.000(000.123) = Cisco Unified CallManager Release 4.0(1)

004.000(001.008) = Cisco Unified CallManager Release 4.0(2)

004.001(002.201) = Cisco Unified CallManager Release 4.1(3)


Note Because defect status continually changes, be aware that Table 4 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.



Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to the following URL: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl


Table 4 Open Caveats for Cisco Unified CallManager Release 4.2(3) 

Identifier

Headline

Component: AXL

CSCse16202

AXL does not support authentication password with special characters.

CSCsf06438

GetLineResponse could return a callPickupGroup with only the UUID, this breaks customer appln as the definition of XNCallPickupGroup states "name" is mandantory.

CSCsf07468

In the GetPickupGroupResponse, the Pickup group member has the same UUID as the CallPickup group itself.

CSCsf08952

The patternUrgency tag is not handled properly in transPattern API.

Component: Backup-Restore

CSCse73047

Description for Event ID 1003 in Cisco BARS cannot be found.

Component: BAT

CSCsd81999

BAT Phone Template Configuration should not allow editing of Authentication Mode or Generate Authentication String when Certificate Operation = No Pending Operation. Currently, it allows both these fields to be edited.

CSCse15880

When a user attempts to insert 4000 phones, "https://<hostname>/BAT/UserOptionsProcess.asp?src=config" times out and gives the following error "The page can not be displayed". After the phones are added, the "Transaction status-Microsoft Internet Explorer" windows changes to Show Latest Status and does not close unless the user "X"s it.

CSCse50825

When you click Validate, a screen pops up and disappears so quickly that it cannot be read.

CSCse62027

Base Templates populate NARD values as 4 & 60 instead of blank

CSCse69331

Extension Mobility information does not get reported in phone reports if Extension Mobility is the only field.

CSCse69350

Upgrade LSC Help Page gives HTTP 404 - File not found

CSCse69383

BAT does not display any errors when an LSA upgrade fails because of non-applicable phone.

CSCse76120

Cisco Unified IP Phone service name is not displayed in the device profile template page.

CSCse78752

Adding phones by using BAT fails.

CSCse90221

BAT validation of phones fails for NO ANSWER RING DURATION.

CSCse90548

An error occurs on the FXS Endpoint Configuration page for VG200 Templates.

CSCsf03746

Help window provided for BAT still shows the previous BAT version.

CSCsf08851

If you follow the BAT support URL from Add/Remove programs you get this error: HTTP 404 File Not Found.

CSCsf08862

User ID Lookup causes JavaScript error when the user is selected from the orphaned window.

CSCsf12029

Cisco Unified CallManager user interface for TAPS installation displays incorrect URL for the TAPS plug-in.

CSCsf18558

BAT can delete device profiles used as logout profiles.

Component: CAR

CSCse82536

CAR database mail alerts are not generated when the configured threshold is reached.

CSCse82542

Autogenerated reports fail after the parameters are changed for autogeneration.

Component: CCM Builds

CSCsf02724

The RisPort.wsdl file does not exist after a installing Cisco Unified CallManager.

Component: CM-CTI

CSCsd93166

Failing over jtapi and eapim to other side of PG - agent loses call.

CSCse97223

Calls to CTI devices are not prepended with national/international/etc. prefixes from MGCP Pri gateways.

CSCse98850

Provider Open failed on second user.

CSCse98865

Through the TAPI application, lineOpen with 2500 CTI devices is slower than previous data.

CSCse99459

CCNE exception when CTI Port (NonController) adds a party to a conference.

Component: CM Documentation

CSCse98501

Pilot Point window Help For This Page is missing drop-down contents.

CSCsf08074

Cisco Unified CallManager documentation should be updated for 4.2(3).

Component: CM-Program Management

CSCse30573

Compatibility Matrix Needs to Be Updated with CSA 2.0(4)

CSCse33464

Compatibility Matrix page: CallManagerRename is not happening.

Component: Call Processing

CSCsc45119

CallControl: MaxCallDuration events are logged as Event Type Error.

CSCsc72754

CallControl: There is no CLI restriction on forwarded calls.

CSCse23953

CallControl: Calls involving T1CAS show visual callpickup alert in calling party.

CSCsf17786

CDR:

CSCsc22985

DataBase: Forwarding should use pkid instead of partition name.

CSCsf09509

When a node in a cluster with several hundred phones registered goes down, the device manager causes excessive traces.

CSCsd88476

HoldReversion: Hold Reversion Interval timer keeps running after call is parked.

CSCsf07100

Ring setting (Phone Active)** does not work.

CSCsf08108

No transition is defined for SsRegisterTransactionErr during call park.

CSCsd19304

MediaControl: Call fails after put on hold and then resumed.

CSCsd81015

MediaControl: Cisco Unified CallManager uses internal msec packet size, ignoring the size proposed by caller.

CSCse88939

MGCP: Global ISDN switch type "primary-qsig" is missing in the Help For This Page information.

CSCse89401

MLPP: Destination phone has Call Forward All enabled. Incoming call to the phone should result in a 1/2 second splash ring before being forwarded.

CSCsc15482

SCCP: Phone does not display the precedence bubble during a conference.

CSCsc85460

SCCP: Phone doesn't ring in for second call when first call with ringback exits.

CSCsd14697

SCCP: Service buttons disappear from SCCP phone after Cisco Unified CallManager is restarted.

CSCsd85096

SCCP: External phone number mask is displayed as Unknown with X's.

CSCse87777

SCCP: Called party number contains a number prefix.

CSCse93438

SCCP: Dialing occurs slowly when digits are entered before the phone gets taken off the hook.

CSCsd30084

SS-CallBack: Callback should be proper in an scenario.

CSCsd76592

SS-CallBack: QSIG Setup ccRingout sent out before ccExecPossible operation is finished.

CSCsd87137

SS-CallBack: Callback on shared line calling itself deviates from expected behavior.

CSCsd89815

SS-CallBack: Set callback on a DP sharing DN with device and logout, callback is not cleared.

CSCse69196

CallPark across ICT is not proper in a transfer.

CSCse70509

CallPark Reversion is not occurring.

CSCse93175

After a parked call is retrieved, the call prefix does not display on the caller information.

CSCse88710

SS-dcallpark:BLF displays busy when dpark DN is released in a shared line.

CSCse78498

SS-dcallpark: Dpark reversion not happening in inter-cluster call

CSCsd05494

SS-Pathreplace: Conference of a Call Forward All call does not display the conference label.

CSCsd39059

SS-Pathreplace: When CFUR is triggered and path replacement is involved, the display on the calling side is "From.." rather than "To..", and vice versa for the called party.

CSCsd97615

SS-Transfer: Fast reorder tone is received during Dirtrfr.

CSCse82461

Supplementary Service: Callpickup notification is being sent to devices previously assigned to the Callpickup group but currently not in the same partition as the CallPickup group.

CSCsc62081

System: Cisco Unified CallManager SDL Out of Service / In Service causes unexpected Unity failover.

CSCse89822

System: MWI ON/OFF may not function properly if an Extension Mobility user is not logged in at the time a new voice message is left for the user or all messages are read.

CSCse47335

Unknown: The reported "Time Spent in Code Yellow" is not consistent with the actual CodeYellowEntry and CodeYellowExit times.

Component: Database

CSCsb10231

Need ring settings for Phone Idle state for Cisco Unified IP Phone 7905, 7912, and 7902.

CSCse05539

Aupair service terminates within function: CDBNotifyClient:isRunning

CSCse41788

Change Notification Fails - DBLCNQueue Counts Rise - DBL Ptr Corruption

CSCse70772

DA entries get corrupted due to out of order change notification for DN

CSCse71912

Inappropriate (non-specific) error message displays when user attempts to add a route group when the publisher server is down.

CSCse79385

Cisco Unified CallManager rename is not reflected in the server deletion warning message.

CSCse91890

Database rules are missing for H323 Gateway enableoutboundfaststart.

CSCse98622

CFA not accepted.

CSCse99090

System allows an E164Mask (External Phone Number Mask) with invalid characters when you are adding or updating devices by using AXL.

Component: Database Administration

CSCsd00303

Inappropriate (non-specific) error message is displayed when a user makes a mistake attempting to change his password.

CSCse65056

Remote scripting error displays when the default voice mail pilot is updated.

CSCse71907

Deleting a Call Park number when the publisher server is down should cause an appropriate error.

CSCse71910

User can add application dial rules when the publisher server is down.

CSCse76427

User can add Trunks to more than one route group with different subscription types.

CSCse77849

Error occurs when an ad hoc conference parameter is changed.

CSCse79387

Cisco Unified CallManager Group rename is missing in the Cisco Unified CallManager Dependency record detail page.

CSCse82661

Search by description returns an incomplete number of records.

CSCse90229

Phone configuration causes a remote scripting error instead of the appropriate error message.

CSCse94395

When an invalid name is given for the TimeSchedule Name a misleading message displays.

CSCse97065

Active directory supports up to 20 characters for a user ID, DCD supports up to 30 characters. However, the Cisco Unified CallManager Userprefs window supports 30 characters for both.

CSCsf05323

Select item combination box in Find/List phone page shows pickup group number instead pickup group name.

CSCsf08871

User ID Lookup causes JavaScript error when the user is selected from the orphaned window.

CSCsf10467

CSS/Partition Lookup causes JavaScript error when selected from the orphaned window.

Component: Directory

CSCse46596

User that is running Cisco Unified CallManager integrated with Active Directory has set up the registry as "directory access = true" but is unable to change the password.

CSCse82475

Active directory plug-in wizard fails to exit gracefully on inability to modify Active directory schema.

CSCse83978

Some Cisco Unified IP Phones 7961 do not display the Corporate Directory option when the Directories button on the phone is pushed.

Component: IPMA Service

CSCec83549

Wizard: IPMA wizard displays a blank screen when the status has longer text.

CSCsc64863

ActiveAssistants counter increases by two when an assistant logs in.

CSCsc99257

There is a thread leak with IPMA activated but CTI disabled.

CSCsd18457

Intrcpt softkey causes IPMA Manager failure in proxy line mode.

CSCsd92632

Warning message should display only once when a user adds assistants.

CSCsd95694

IPMA configuration wizard does not create button template for 7941/61/71

CSCsd97429

Text is required on IPMA Configuration window for subscribing an assistant phone.

CSCsd97559

HTTP Request Cancelled message is displayed when Answer Manager Call from Assistant.

CSCse72192

Real-Time Monitoring Tool counters shows the wrong value for IPMA services.

CSCse78611

Phone does not get refreshed when user logs out of browser.

CSCse98778

Documentation on IPMA IP Phone Service needs improvement.

CSCsf12044

Auto-configuration option on IPMA configuration window causes an error.

Component: JTAPISDK

CSCse86546

getOriginalConferenceController returns unknown error after Controller DParks.

CSCsf13584

JTAPI Test tool causes an error when a CTI Port (Non Conference Controller) tries to add another party (or CTI Port) to a conference.

[Advance Ad-Hoc Conference Parameter is enabled]

Component: MLA

CSCed68455

MLA User Group Configuration window displays distorted Last Name/First Name/Dept

CSCse73106

User Group Warning Message does not print First/Last Name of Users with quote character.

CSCse79746

From phone DN window when user clicks on call pick group view details, an error message "ASP file is not found in the mapping" displays.

CSCsf15551

Device Mobility mode settings are not available to users.

Component: QED

CSCsd61445

Misleading phone type for Cisco Unified IP Phones 7941G and 7961G.

CSCse30883

Output Attenuation Field Range need to be changed for MGCP FXO ports.

Component: Security

CSCsd55710

capF crash on the publisher server.

Component: Server Web Pages

CSCsb51883

A remote scripting error is not being properly displayed in some windows.

Component: TAPISDK

CSCsd75183

Call information fails for Called IdName for a park/unpark scenario.

CSCsf12058

TSP cannot join two ad hoc conferences using LineDevSpecific. TSP puts the call in onholdpending state after the join request is sent.

Component: TFTP

CSCse72780

 

Component: Upgrade Assistant

CSCsb47902

After an upgrade, Hunt Pilots may not get created successfully.

CSCsc28286

Upgrade Assistant does not properly flag invalid VM profile names.

CSCsd46630

Upgrade Assistant should check whether DCOM is enabled or not.

CSCsf16293

Upgrade Assistant does not catch a potential Subscriber upgrade failure because of empty CCMAdministrator, CCMSysUser and IPMASysUser passwords in the registry of the Publisher.

Component: Webdialer-Service

CSCse80961

CTIProvider is not closed when Webdailer service is deactivated.



Note For complete Cisco Unified IP Phone firmware release note information, refer to the applicable firmware release notes for your specific Cisco Unified IP Phone at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/


Troubleshooting

For troubleshooting information, refer to the Troubleshooting Guide for Cisco Unified CallManager, Release 4.2(3). This document provides troubleshooting procedures for Cisco Unified CallManager systems. The Troubleshooting Guide for Cisco Unified CallManager provides guidance for network administrators responsible for managing the Cisco Unified CallManager system, for enterprise managers, and for employees. This document does not cover every possible trouble event that might occur on a Cisco Unified CallManager system but instead focuses on those events that are frequently seen by the Cisco Technical Assistance Center (TAC) and frequently asked questions from newsgroups.

Documentation Updates

Updates

Errors

Changes

Omissions

Updates

MLA: Adding an AD User to User Group Gets Error Number: -1005

Path Replacement to RP with Partition Works for <none> PR CSS

H.323 Information Settings on a H.323 Client Documentation Updates

Cisco WebDialer Does Not Close All Windows After Dialing

PRI Protocol Type Field Updates

Cisco Unified CallMananger Sent H323 Redirecting Number IE in UUIE

Extension Mobility Configuration Step Is Missing

Enabling Auto Registration

Music On Hold Configuration

Logged Into Hunt Group on Phone Configuration Window

TAPS and Autoregister

CDR Search for Extension

MLA: Adding an AD User to User Group Gets Error Number: -1005

The Multilevel Administration Access Configuration chapter of the Cisco Unified CallManager Administration Guide adds the following note to the "Adding Users to a User Group" section:


Note The following configuration must take place for users that were added outside Cisco Unified CallManager through direct addition of the user to Active Directory (AD) that is integrated with Cisco Unified CallManager: When you add a user to a user group, you must first use Cisco Unified CallManager to associate the user with a device, or you must configure at least one of the users attributes in Cisco Unified CallManager. (You do not need to perform this configuration for users that were added within Cisco Unified CallManager.)

The following error results if you do not follow the preceding configuration for directly added Active Directory users:

Error Number: -1005

Description: User or User Profile doesn't exist or user profile attribute not set for the user <username>


Path Replacement to RP with Partition Works for <none> PR CSS

The Understanding IP Telephony Protocols chapter of the Cisco Unified CallManager System Guide revision to the "Path Replacement" section now contains the following text:

Cisco Unified CallManager provides the Path Replacement Calling Search Space service parameter, so you can configure the calling search space that the cooperating PINX uses to send the outbound SETUP message to the requesting PINX. If you do not specify a value for the Path Replacement Calling Search Space service parameter, the requesting PINX uses the calling search space of the end user that is involved in the call.

H.323 Information Settings on a H.323 Client Documentation Updates

The Cisco Unified IP Phone Configuration chapter of the Cisco Unified CallManager Administration Guide revision to the "Phone Configuration Settings" section revises the following fields to now contain revised descriptions:

[H.323 Information] Outgoing Caller ID Pattern

[H.323 Information] Calling Party Selection

[H.323 Information] Calling Party Presentation

Cisco WebDialer Does Not Close All Windows After Dialing

Because this issue required changes to the phone user documentation, the Cisco WebDialer chapter of the Cisco Unified CallManager Features and Services Guide includes a reference to the pertinent phone user documentation in the "Where to Find More Information" section.

PRI Protocol Type Field Updates

The Gateway Configuration chapter of the Cisco Unified CallManager Administration Guide corrects omissions in the description of the PRI Protocol Type field on the Gateway Configuration window and updates the E1/T1 PRI Port Configuration Settings section.

Cisco Unified CallMananger Sent H323 Redirecting Number IE in UUIE

The Gateway Configuration chapter and Trunk Configuration chapter of the Cisco Unified CallManager Administration Guide change the field definition for all occurrences of the Redirecting Number IE - Inbound and Redirecting Number IE - Outbound fields.

Extension Mobility Configuration Step Is Missing

The Cisco Unified CallManager Extension Mobility chapter of the Cisco Unified CallManager Features and Services Guide revises the configuration checklist for enabling extension mobility. The Configuration Checklist for Cisco Unified CallManager Extension Mobility section provides the updated procedure.

Enabling Auto Registration

The Auto-Registration Configuration chapter of the Cisco Unified CallManager Administration Guide provides a more detailed procedure for enabling auto-registration. The Enabling Auto-Registration section provides the updated procedure.

Music On Hold Configuration

The Music On Hold chapter of the Cisco Unified CallManager Features and Services Guide provides updated definitions for the following configuration parameters:

Maximum Half Duplex Streams

Maximum Multicast Connections

The Music On Hold Server Configuration Settings section provides the updated definitions.

Logged Into Hunt Group on Phone Configuration Window

The Phone Configuration chapter of the Cisco Unified CallManager Administration Guide provides the following information about the Logged Into Hunt Group check box.

The system checks the Logged Into Hunt Group check box by default for all phones and indicates that the phone is currently logged into a hunt list (group). When the phone gets added to a hunt list, the administrator can log the user in or out by checking (and clearing) this check box.

Users use the HLog softkey on the phone to log the phone in or out of the hunt list.

The Understanding Route Plans chapter of the Cisco Unified CallManager System Guide provides additional information about the Log Out of Hunt Groups feature.

TAPS and Autoregister

TAPS works with all phones that autoregister and have SEP or ATA as device name prefixes; however, this capacity has not been tested on all available models.

CDR Search for Extension

The Cisco Unified CallManager Serviceability System Guide does not provide accurate information on how CDR Search by User Extension works for Cisco Unified CallManager CDR Analysis and Reporting. Instead, use the following text for information on how the feature works:

CDR Search by User Extension—Available for CAR administrators. You can search CDRs by user or directory number (calling, original called, or final called) to analyze call details for the first 100 records that satisfy the search criteria. If more than 100 records are returned, the system truncates the results. You can search for calls by using specific numbers for the period that you specify, which helps you trace calls that are placed from or to any specific numbers for diagnostic or informational purposes. All associated records, such as transfer and conference calls, appear together as a logical group.

Errors

This section includes information about errors in the Cisco Unified CallManager Documentation suite:

Bulk Administration Tool User Guide Title Error

Cisco Unified CM Administration Guide Contains Incorrect Information About Configuring Music on Hold

Bulk Administration Tool User Guide Title Error

The Bulk Administration Tool User Guide is incorrectly named the Cisco Unified CallManager Bulk Administration Guide in the following documents:

Cisco Unified CallManager System Guide, Release 4.2(3)

Cisco Unified CallManager Administration Guide, Release 4.2(3)

Cisco Unified CallManager Features and Services Guide, Release 4.2(3)

Cisco Unified CM Administration Guide Contains Incorrect Information About Configuring Music on Hold

MOH audio sources cannot be specified at the device pool level for AC. It has to be specified in a common profile first and then that common profile can be assigned to the AC pilot point.

The correct method is published here:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a008070eb07.html

Changes

This section contains changes that have occurred since the original release of the Cisco Unified CallManager Release 4.2 documentation. These changes may not appear in the current documentation or the online help for the Cisco Unified CallManager application:

Device Mobility Info Configuration Window

Device Pool Configuration Window

Behavior Enhancements to Join

Device Mobility Info Configuration Window

One field combines the subnet and subnet mask fields on the Device Info Configuration Window: [Network Address]/[Network Prefix Length].

Device Pool Configuration Window

Fields on the Device Pool Configuration window comprise the following groups: Device Pool Settings, Roaming Sensitive Settings, and Device Mobility Related Information settings. The Device Mobility Related Information settings overwrite device level settings when the device is roaming in the same device mobility group.

Behavior Enhancements to Join

The following information documents the enhancements made to the Join feature that is described in Cisco Unified IP Phones, Cisco Unified CallManager System Guide.

Join does not create a consultation call and does not put the active call on hold. To implement Join, choose at least two calls and then press the Join softkey on one of the calls. Join can include more than two calls, which results in a call with three or more parties. Join supports up to 16 participants in a call. To choose an active or held call, highlight the call and press the Select softkey. A selected call has a checked indicator shown next to it on the phone.

The call that initiates the Join gets automatically included, even if not selected. The active call gets included even if not selected.

If all the calls in the join are a basic call, then the call that initiated the join is the primary call. If any call in the join is a conference call (that is, it was in a conference before being joined), then that call is the primary call.

The selected status of the final call after the join depends on the selected status of the primary call before the join. If the primary call was selected, then after the join, the final call remains selected. If the primary call was not selected, then after the join, the final call remains unselected.


Note If more than one call in the join is a conference call, the join will fail (join supports only 1 conference call).


Omissions

This section lists new and additional information that the current version of the Cisco Unified CallManager documentation may not include:

CTI Monitored Lines

Malicious Call Identification Restrictions

TAPS Installation Procedure for CCM4.1(3)SR2 and Subsequent Releases

CTI Monitored Lines

To calculate the number of CTI monitored lines in a system, use the following formula:

number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines

Malicious Call Identification Restrictions

The Malicious Call Identification chapter of the Cisco Unified CallManager Features and Services Guide does not list SIP trunk as a restriction. Malicious Call Identification (MCID) does not support SIP trunks.

TAPS Installation Procedure for CCM4.1(3)SR2 and Subsequent Releases

There is a new procedure for installing and configuring Cisco Tool for Auto-Registered Phone Support (TAPS) in IPCCx 4.0 as follows:

Step 1 After installing the TAPS plugin, go to the AAR Management page in CRS Admin and upload the TAPS AAR.aar file. After uploading TAPS.aar, an application called TAPS gets created and the TAPS.aef script gets uploaded.

Step 2 Browse to C:\TAPS\.

Step 3 Open the TAPS application from the Application Management page.

Step 4 From the Script* pull-down menu, select TAPS.aef.

Step 5 Click Update.

Find/List Windows

Some of the Cisco Unified CallManager Administration Find/List windows display different field options than what is documented in the online help and the Cisco Unified CallManager Administration Guide.

Obtaining 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

Documentation DVD

Ordering Documentation

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:

http://www.cisco.com

You can access international Cisco web sites at this URL:

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

Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

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

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

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

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco 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-9883

We 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:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

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

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

This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.

See the "Reporting Security Problems in Cisco Products" section for additional information.

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:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

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

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

See the following sections for additional information:

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation 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, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation 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 Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


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 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 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)
Extension MobilityEA: +32 2 704 55 55
USA: 1 800 553-2447

For 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.

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

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

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

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

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

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