.
Cisco Unified CallManager Device Package 7.1.2
(22010-1)
Release Notes
These Device Package
release notes contain important information about installation procedures and
resolved caveats for Cisco Unified CallManager Device
Package release 7.1.2(22010-1).
1.
Note: Before you
install this
Determining
the Software Version
Compatibility
Matrix and Supported Upgrades
Important
Notes & Recommendations
Resolved
Caveats for Cisco Unified CallManager Device Package
This
Device Package includes the following resolved DDTS’s:
Locale
Installer for Cisco Unified CallManager
Cisco
Product Security Overview
Reporting
Security Problems in Cisco Products
Obtaining
Technical Assistance
Cisco
Technical Support Website
Definitions
of Service Request Severity
Obtaining
Additional Publications and Information
This document provides installation instructions
for this
2.
Note:
Failure to follow installation instructions as described may result in
inconsistent
Make sure that you
install and configure this release of
You can determine the
version of
This
7.1.2 |
3.
Note: Review the Show/Software on the
4.
NOTE: Be aware that the release of
5. Endpoint firmware: http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser Endpoint documentation, including release notes: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/english/
File |
MD5 |
cmterm-devicepack7.1.2.xxxx-x.cop.sgn |
|
Cisco
Unified CallManager Device Package 7.1.2(22010-1) includes the following
firmware versions:
Device-type |
Load-name |
Version |
3911_3951-sip |
3911_3951-sip.8-1-2 |
8.1(2.0) |
3911_3951-sip |
3911_3951-sip.8-1-2SR1 |
8.1(2.0) |
6608 |
6608-4.0.0.32-mgcp |
D00404000032.bin/D0054322.bin |
6608cfb |
6608cfb-4.0.0.03-sccp |
C00104000003.bin/C002E031.bin |
6608mtp |
6608mtp-4.0.0.06-sccp |
M00104000006.bin/M002E031.bin |
6624 |
6624-4.0.0.13-mgcp |
A00204000013.bin/A0034322.bin |
69xx-sccp |
69xx-sccp.8-5-2-0 |
8.5(2.0) |
7902 |
7902-8.0.2-sccp |
8.0(2.0) |
7905 |
7905-8.0.1.1-sip |
8.0(1.1) |
7905 |
7905-8.0.3-sccp |
8.0(3.0) |
7910 |
7910-5.0.7.0-sccp |
5.0(7.0) |
7911_7906-sccp |
7911_7906-sccp.8-5-2 |
8.5(2.0) |
7911_7906-sccp |
7911_7906-sccp.8-5-2SR1 |
8.5(2.0) |
7911_7906-sip |
7911_7906-sip.8-5-2 |
8.5(2.0) |
7911_7906-sip |
7911_7906-sip.8-5-2SR1 |
8.5(2.0) |
7912 |
7912-8.0.1.1-sip |
8.0(1.1) |
7912 |
7912-8.0.3-sccp |
8.0(3.0) |
7914-sccp |
7914-sccp.5-0-4 |
5.0(4.0) |
7915 |
7915.1-0-3 |
1.0(3.0) |
7916 |
7916.1-0-3 |
1.0(3.0) |
7920-sccp |
7920-sccp.3-0-2 |
3.0(2.0) |
7921-sccp |
7921-sccp.1-3-3 |
1.3(3.0) |
7925-sccp |
7925-sccp.1-3-3 |
1.3(3.0) |
7931-sccp |
7931-sccp.8-5-2 |
8.5(2.0) |
7931-sccp |
7931-sccp.8-5-2SR1 |
8.5(2.0) |
7931-sip |
7931-sip.8-5-2 |
8.5(2.0) |
7931-sip |
7931-sip.8-5-2SR1 |
8.5(2.0) |
7935-sccp |
7935-sccp.3-2-19 |
3.2(19.0) |
7936-sccp |
7936-sccp.3-3-20 |
3.3(20.0) |
7937-sccp |
7937-sccp.1-3-3 |
1.3(3.0) |
7940-7960 |
7940-7960-8.12.00-sip |
8.12(0.0) |
7940-7960-sccp |
7940-7960-sccp.8-1-1 |
8.1(1.0) |
7941_7961-sccp |
7941_7961-sccp.8-5-2 |
8.5(2.0) |
7941_7961-sccp |
7941_7961-sccp.8-5-2SR1 |
8.5(2.0) |
7941_7961-sip |
7941_7961-sip.8-5-2 |
8.5(2.0) |
7941_7961-sip |
7941_7961-sip.8-5-2SR1 |
8.5(2.0) |
7942_7962-sccp |
7942_7962-sccp.8-5-2 |
8.5(2.0) |
7942_7962-sccp |
7942_7962-sccp.8-5-2SR1 |
8.5(2.0) |
7942_7962-sip |
7942_7962-sip.8-5-2 |
8.5(2.0) |
7942_7962-sip |
7942_7962-sip.8-5-2SR1 |
8.5(2.0) |
7945_7965-sccp |
7945_7965-sccp.8-5-2 |
8.5(2.0) |
7945_7965-sccp |
7945_7965-sccp.8-5-2SR1 |
8.5(2.0) |
7945_7965-sip |
7945_7965-sip.8-5-2 |
8.5(2.0) |
7945_7965-sip |
7945_7965-sip.8-5-2SR1 |
8.5(2.0) |
7970_7971-sccp |
7970_7971-sccp.8-5-2 |
8.5(2.0) |
7970_7971-sccp |
7970_7971-sccp.8-5-2SR1 |
8.5(2.0) |
7970_7971-sip |
7970_7971-sip.8-5-2 |
8.5(2.0) |
7970_7971-sip |
7970_7971-sip.8-5-2SR1 |
8.5(2.0) |
7975-sccp |
7975-sccp.8-5-2 |
8.5(2.0) |
7975-sccp |
7975-sccp.8-5-2SR1 |
8.5(2.0) |
7975-sip |
7975-sip.8-5-2 |
8.5(2.0) |
7975-sip |
7975-sip.8-5-2SR1 |
8.5(2.0) |
7985 |
7985-4-1-7-0-sccp |
4.1(7.0) |
ata |
ata-3.2.4-sccp |
3.2(4.0) |
·
To minimize call-processing interruptions during the
upgrade process, make sure that all servers are running the same version of
·
Make sure that the servers are online
before you begin this Device Package installation.
1.
Note:
Procedure
NOTE: Apply this patch to all of your
When applying this Device Package to enable new
device support, a cluster-wide reboot is required for those devices to register
successfully. A clusterwide reboot IS NOT
required when running to update existing firmware/support.
For
Cisco Unified CallManager 7.1, you must do all
software installations and upgrades by using the Software Upgrades menu
options. The system can upload and process only software that
2.
Note: In order to change the loads manually, you do NOT need to reinstall
this Device Package. The new files will be present in the TFTP folder. Go to CCMAdmin->Device->Device Settings->Device Defaults
and manually change the name of the load file (for specific device(s)) to the
new load and click UPDATE.
Note: If
you are rebooting the cluster, the next step does not need to be done.
3.
The
The Device Package cannot be uninstalled. However, you can change
the device defaults for devices you wish to roll back. From the
Log
File Information
The system creates log files which may be viewed via the
following process:
·
Using Cisco Unified CallManager Serviceability Real-Time Monitoring Tool,
select Trace & Log Central\Remote Browse\Install and Upgrade Logs.
·
Using Cisco Unified CallManager Serviceability Real-Time Monitoring Tool,
select Trace & Log Central\Collect Files\Install and Upgrade Logs.
·
Using Cisco Unified CallManager Serviceability Real-Time Monitoring Tool,
select Trace & Log Central\Query Wizard\Install and Upgrade Logs.
·
Using Cisco Unified CallManager Serviceability Real-Time Monitoring Tool,
select Trace & Log Central\Schedule Collection\Install
and Upgrade Logs.
7.1(2.22010.1) |
|
Online User
Guide not available for 7925 model phone |
|
Need to check
in the RTLite phone load due to a new UE change |
|
Noise
Reduction causes saturated speech on Handsfree Send
|
|
Noise
Reduction causes saturated speech on Handsfree Send
|
|
Placeholder
of CIA1859 HeadsetHandset Monitor |
|
7911 Turbo
CR2 LCD flicker in normal condition |
7.1(2.22008.1) |
|
Need to check
in the RTLite phone load for dev pack build |
|
Adding En
Bloc dialing Product Specific Configuration parameters |
7.1(2.21007.1) |
|
Update Cisco
7921 7925 support files for Release 133 |
7.1(2.21006.1) |
|
Checkin Cisco 7925 firmware version 133 to CUCM |
7.1(2.21003.1) |
|
JPNKatakana strings used on 7937s QRT EM CallBack and Corp Dir |
7.1(2.21002.1) |
|
Add
enhancements for 1100 and 1300 series CTS |
7.1(2.11001.1) |
|
Check in
794060 SIP P0S381200 COP files to Clearcase for
Linux CCM |
For optimal performance, be sure
that you use the
Each release of
4.
Note:
When using locales,
You can access the most current
http://www.cisco.com/univercd/home/home.htm
You can access the
You can access international
http://www.cisco.com/public/countries_languages.shtml
For additional
information about
To access the documentation
suite for voice products, navigate to the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/.
To access the latest software
upgrades and related documentation for
Registered
http://www.cisco.com/en/US/partner/ordering/
http://www.cisco.com/go/marketplace/
You can find instructions for ordering
documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order
You can send comments about technical documentation
to bug-doc@cisco.com.
You can submit comments by using the response card
(if present) behind the front cover of your document or by writing to the
following address:
Attn: Customer Document Ordering
We appreciate your comments.
From this site, you can perform these tasks:
A current list of security advisories and notices
for
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
We
encourage you to use Pretty Good Privacy (PGP) or a compatible product to
encrypt any sensitive information that you send to
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an
emergency, you can also reach PSIRT by telephone:
Obtaining Technical Assistance
For all customers, partners, resellers, and
distributors who hold valid
The
http://www.cisco.com/techsupport
Access to all tools on the
5.
Note: Use the
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
For S1 or S2 service requests or
if you do not have Internet access, contact the
To open a service request by telephone, use one of
the following numbers:
Asia-Pacific: +61 2 8446 7411
(Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of
http://www.cisco.com/techsupport/contacts
Definitions of Service
Request Severity
To ensure that all service requests are reported in
a standard format,
Severity 1 (S1)—Your
network is “down,” or there is a critical impact to your business
operations. You and
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
Severity 3 (S3)—Operational performance of
your network is impaired, but most business operations remain functional.
You and
Severity 4 (S4)—You
require information or assistance with
Obtaining Additional Publications and Information
Information about
·
·
· Packet magazine is the
· iQ Magazine is the quarterly
publication from
· Internet Protocol
Journal is a quarterly journal published by
· World-class
networking training is available from
C
All other
trademarks mentioned in this document or Website are
the property of their respective owners. The use of the word partner does not
imply a partnership relationship between
Copyright © 2009
Cisco Systems, Inc. All rights reserved.