Release Notes for Cisco Unity Express 2.3

These release notes support Cisco Unity Express 2.3 up to and including Cisco Unity Express 2.3.4. These release notes are updated as needed.

We recommend that you read the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/customer/tech_tips/index/fn.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.

Software Licenses and Factory-Set Limits

Different license levels are available for Cisco Unity Express software for the network module or the AIM and for Cisco Unified CallManager or Cisco Unified CallManager Express. To download Cisco Unity Express software licenses, you must have an account on Cisco.com. In Cisco.com, go to the Software Center for Cisco Unity Express at:

http://www.cisco.com/cgi-bin/tablebuild.pl?topic=278535672

The following Cisco Unity Express licenses are available for Cisco Unity Express 2.3:

Table 4 Cisco Unity Express Network Module

Cisco Unity Express Network Module

Cisco Unified CallManager:

•SCUE-LIC-200CCM-2.3.x

•SCUE-LIC-250CCM-2.3.x

•SCUE-LIC-25CCM-2.3.x

•SCUE-LIC-100CCM-2.3.x

•SCUE-LIC-12CCM-2.3.x

•SCUE-LIC-50CCM-2.3.x

•SCUE-LIC-150CCM-2.3.x

Cisco Unified CallManager Express

•SCUE-LIC-12CME-2.3.x

•SCUE-LIC-25CME-2.3.x

•SCUE-LIC-50CME-2.3.x

•SCUE-LIC-100CME-2.3.x

•SCUE-LIC-150CME-2.3.x

•SCUE-LIC-200CME-2.3.x

•SCUE-LIC-250CME-2.3.x

Cisco Unity Express AIM

Cisco Unified CallManager

•SCUE-LIC-12CCM-2.3.x

•SCUE-LIC-25CCM-2.3.x

•SCUE-LIC-50CCM-2.3.x

Cisco Unified CallManager Express

•SCUE-LIC-12CME-2.3.x

•SCUE-LIC-25CME-2.3.x

•SCUE-LIC-50CME-2.3.x

Note Before release 4.0, Cisco Unified CallManager was known as Cisco CallManager.

Factory-set system limits are determined by the ordered license. Limits for the NM-CUE-EC are shown in Table 5 and Table 6. Limits for the NM-CUE are shown in Table 7 and Table 8. Limits for the 1 GB AIM-CUE are shown in Table 9 and Table 10.

2The default mailbox size calculation includes the allocation for the General Delivery Mailboxes (GDMs).

Table 10 1-GB AIM-CUE Maximum Number of Mailboxes, Groups, Owners, and Members

Cisco Unity Express License/Software SKU

Default Number of Personal Mailboxes

Default Number of General Delivery Mailboxes

Total Number of Mailboxes

Number of Users

Number of Groups

Number of Owners

Number of Members

SCUE-LIC-12CCMSCUE-LIC-12CME

12

5

17

24

20

100

200

SCUE-LIC-25CCMSCUE-LIC-25CME

25

10

35

50

20

100

200

SCUE-LIC-50CCMSCUE-LIC-50CME

50

15

65

100

20

100

200

Software Upgrade Overview

Depending on the Cisco Unity Express version you are upgrading from, different software upgrade methods are available. The following methods are supported to upgrade to Cisco Unity Express 2.3:

•Upgrade using the online installer with the software install upgrade command. For specific procedures, see the Upgrading an Existing Software Image section in the Cisco Unity Express 2.3 Installation and Upgrade Guide.

Table 11 provides a matrix of the upgrade processes available for the different software releases using the following conventions:

•A = Upgrade Using Online Installer

•B = "Clean" Installation Upgrade Using Online Installer

•C = "Clean" Installation Upgrade Using Boot Helper. For software upgrades where other upgrade options are available, Cisco recommends using this upgrade process only if the other methods are unsuccessful.

Caution If you upgrade using either of the "clean" installation processes, the existing configuration files on the system are not preserved. Any voice mail, greetings or passwords configured on the system are lost.

To preserve your configuration, you must first back up the existing configuration files and restore them after performing the upgrade. If the configuration files are not backed up before performing the upgrade, then Cisco Unity Express must be reconfigured.

Table 11 Cisco Unity Express Software Upgrade Process Matrix

Upgrade From:

To:

2.3.4

2.3.3

2.3.2

2.3.1

2.2.2

2.2.1

2.1.3

2.1.2

2.1.1

2.0.2

2.0.1

2.3.3

B, C

2.3.2

B, C

B, C

—

—

—

—

—

—

—

—

—

2.3.1

B, C

B, C

B, C

—

—

—

—

—

—

—

—

2.2.2

A, B, C

A, B, C

A, B, C

B, C

—

—

—

—

—

—

—

2.2.1

B, C

B, C

B, C

B, C

B, C

—

—

—

—

—

—

2.1.3

B, C

B, C

B, C

B, C

B, C

A, B, C

—

—

—

—

—

2.1.2

B, C

B, C

B, C

B, C

B, C

B, C

A, B, C

—

—

—

—

2.1.1

B, C

B, C

B, C

B, C

B, C

B, C

B, C

A, B, C

—

—

—

2.0.2

B, C

B, C

B, C

B, C

B, C

B, C

B, C

B, C

B, C

—

—

2.0.1

B, C

B, C

B, C

B, C

B, C

B, C

B, C

B, C

B, C

B, C

—

1.1.2

B, C

B, C

B, C

B, C

B, C

B, C

C

C

C

C

C

When planning your software upgrade, consider the following:

•If you upgrade the software using the online installer, downgrading to an earlier software version is currently not supported.

•If a non-2.3.x license is installed, several null node name error messages are shown on the console display after Populating internal database.... during the bootup sequence. This can be resolved by installing a 2.3.2 version license. This is benign and can be safely ignored. The new licenses only fix the display error. Also, 2.3.x licenses are backward compatible with 2.1.3.

•When you upgrade, make sure to upgrade to the same type of license. For example, if you are running the license SCUE-LIC-50CME, make sure to upgrade to another SCUE-LIC-xxCME license. You can upgrade to a license that offers support for more personal mailboxes. To increase your mailbox license, you must purchase a new license.

•If your system is using an AIM-CUE module with 512 MB compact flash, you must upgrade to the AIM-CUE module with 1 GB compact flash before upgrading the software to Cisco Unity Express 2.3.

•The online installer is not available on the AIM-CUE module with 512 MB compact flash.

•Downgrading to a license with support for fewer personal mailboxes is not supported. If you want to change the system to support fewer mailboxes, and you cannot restore any previous backups on the larger system, then you must purchase a new license and perform a new installation.

•If you are upgrading from a previous release with non-U.S. English audio prompts installed, you cannot upgrade to Cisco Unity Express 2.3.1, since these languages were not supported in that release. However, you can upgrade to Cisco Unity Express 2.3.2 or 2.3.3 and the languages will be supported.

Software Compatibility

Cisco Unity Express compatibility with other software application versions is described in the following sections:

Caution Cisco Unity Express 2.3.x does not support versions of Cisco Unified CallManager prior to release 4.1(2). If you are using an earlier version of Cisco Unified CallManager, then you must upgrade to release 4.1(2) or higher to interoperate with Cisco Unity Express 2.3.x.

Cisco Unity Express Language Support

Cisco Unity Express 2.3 supports different languages for the telephony user interface and the VoiceView Express user interface. The GUI pages, CLI commands and the IMAP interface are only available in English.

One language can be installed on the system at one time. Table 15 lists the languages that are supported, and the minimum Cisco Unity Express release required.

Note In Cisco Unity Express release 2.3.1, only United States English was supported.

New Features and Enhancements in Cisco Unity Express 2.3.4

Cisco Unity Express 2.3.4 introduces support for the following enhancement:

•The Cisco Unity Express voicemail system has been updated to support the date changes in United States timezone Daylight Saving Time that take effect in March, 2007. These timezone changes were mandated by the U.S. Energy Policy Act of 2005.

New Features and Enhancements in Cisco Unity Express 2.3.3

Cisco Unity Express 2.3.3 introduces support for the following enhancements:

•New language support:

Chinese (Mandarin)

Korean

Japanese

New Features and Enhancements in Cisco Unity Express 2.3.2

Cisco Unity Express 2.3.2 introduces support for the following enhancements:

•New language support:

French (Canada)

Spanish (Mexico)

Note Cisco Unity Express 2.3.2 also provides support for languages that were not available in version 2.3.1.

New Features and Enhancements in Cisco Unity Express 2.3.1

Cisco Unity Express 2.3.1 introduces support for the following enhancements:

•Increased system capacity on the NM-CUE-EC—The NM-CUE-EC supports custom prompts, increased number of mailboxes, increased number of remote and cached users, larger storage capacity, and an increased number of public distribution lists.

•Integrated Messaging—Cisco Unity Express end-users can access and manage their voice messages and e-mail using an e-mail client. This feature is only supported on the NM-CUE and NM-CUE-EC

•VoiceView Express—Cisco Unity Express end users can browse, listen, manage, and create their voice messages and manage their mailbox options from their Cisco IP phone. Only Cisco IP phones 7940, 7941, 7960, 7961, 7970, and 7971 support VoiceView Express. This feature is only supported on the NM-CUE and NM-CUE-EC.

VoiceView Express does not support Korean and Chinese when the CUE is working with CME.

•Future message delivery—End-users can schedule messages to be delivered at a future time to users on local or remote systems.

•Local broadcast privilege—End-users with this privilege can send broadcast messages only to other end-users on the local system.

•Mailbox selection—This configurable option specifies the mailbox to be used in case of call forward. SIP phones are not supported.

Important Notes

•Beginning in March, 2007, the dates for United States Daylight Savings Time were changed to begin at 2 a.m. on the second Sunday of March, and end at 2 a.m. on the first Sunday in November. This change will affect voicemail timestamps during the weeks that were previously part of Standard Time. Cisco Unity Express sets the Daylight Savings Time start and end dates automatically on the basis of timezone.

–If you are using Cisco Unity Express release 2.3.3 or earlier, you must manually change the United States Daylight Savings Time start and end date settings using the clock timezone command. To configure the timezone using the GUI, go to Administration > Network Time Zone Settings and change the timezone accordingly.

–If you are using Cisco Unity Express 2.3.4 or later, the new United States Daylight Savings Time start and end dates are set automatically when the timezone is configured.

For more information, see Field Notice FN#62682: U.S. Daylight Saving Time (DST) policy changes effective March 2007 - for all Cisco Unity Express (CUE) releases prior to 2.3.4. For more information about how the U.S. Daylight Savings Time policy changes affect other Cisco products, see Field Notice FN#81675: U.S. Daylight Saving Time (DST) Changes for 2007.

•Cisco Unity Express 2.3.1 supports United States English only. Customers using other languages in previous releases cannot upgrade to Release 2.3.1. However, these languages are supported in Cisco Unity Express Release 2.3.2, so customers can upgrade from earlier 2.2 releases to Release 2.3.2 or 2.3.3.

•The online installer method using the software install upgrade command is not supported for upgrading to 2.3.1. However, this method is supported for upgrading to Cisco Unity Express 2.3.4 from the 2.2.2 release.

Caveats

Caveats describe unexpected behavior in Cisco Unity Express software releases. Severity 1 caveats are the most serious caveats. Severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only selected severity 3 caveats are included in the caveats document.

This section contains open and resolved caveats for the current Cisco Unity Express maintenance release.

The following information is provided for each caveat:

•Symptoms—A description of what is observed when the caveat occurs.

•Conditions—The conditions under which the caveat has been known to occur.

•Workaround—Solutions, if available, to counteract the caveat.

Note If you have an account on Cisco.com, you can use Bug Toolkit to find select caveats of any severity. To reach Bug Toolkit, log in to Cisco.com by clicking the Log In button on the right side, go to the drop down menu on the top bar of the page and select Technical Support: Tools & Utilities: Software Bug Toolkit (under Troubleshooting Tools). Another option is to enter the following URL in your web browser: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

To find the latest Cisco Unity Express DDTS information, go to Bug Toolkit and search, by product, for Cisco Unity Express. Once logged in to Bug Toolkit, select the option to search for bugs in other Cisco software and hardware products, and select the Cisco Unity Express Network Module.

Open Caveats—Cisco Unity Express Release 2.3.4

There are no open caveats in Cisco Unity Express Release 2.3.4.

Open Caveats—Cisco Unity Express Release 2.3.3

CSCsg11684

Symptom—After upgrading CallManager to version 4.2(3), CUE now reports that it is unable to determine CCM version when verifying Web and JTAPI username and password. Starting with version 4.2(3), CM has disabled non-secure access to http://x.x.x.x/CCMPluginsServer/CiscoJTAPIClient.exe.

CUE relied on this URL to determine the CCM version. So now, it fails to detect the correct CCM version. However, the default CUE JTAPI jar (skate, 4.1) registers successfully to a CCM 4.2(3) and the users are able to make calls.

The error seems to be benign for a majority of cases. The problems are:

•Although simple calls work, some complex call flows can fail.

•CUE is not able to import users from CCM through the GUI.

Conditions—Found when using CCM version 4.2(3) with the supported versions of CUE: 2.3(1), 2.3(2). All functionality remains, CTI ports and route points registered with CCM. VM and AA route points are dialable and functional.

While recording the message and DTMF digits are pressed, CUE receives some VAD packets and can not handle these VAD packet properly. The DTMF digits are lost after that.

Workaround—None.

CSCsd87985

Symptoms—During a semi-attended transfer, CUE plays the prompt: "Sorry we currently experiencing an internal system problems".

Conditions—Occurs when SCCP phone (A) calls AA (Auto-Attendant) and AA transfers (semi-attended transfer) the call to VM. While transferring, IllegalContactStateException is received and CUE plays "Sorry we are currently experiencing an internal system problem".

Workaround—None.

CSCse31911

Symptoms—There are three symptoms:

1. Calls from CUE to IP phones don't forward to voicemail and the calls are disconnected when ringing timeout expires.

2. Calls transferred from CUE to IP phones get no-way audio.

3. Calls from CUE to IP phones don't display the caller Id of the original calling party.

Conditions—This is seen with CME 3.3 and prior and CUE 2.3.1.

Workaround—Configure CUE to use blind transfer:

conf t

ccn subsystem sip

transfer-mode blind bye-also

CSCse15934

Symptoms—VVE shows calls are from Unknown caller, although the calls are from phones from the same CME.

Conditions—The user at Phone A calls the 4 digit number of Phone B (both are on the same CME) and CUE receives CFNA. The user at Phone A is able to leave a message for Phone B. The CME changes the 4 digit extension to the E164 number and that matches the E164 configured for Phone B in CUE. When user at Phone B checks voicemail through VVE, VVE displays the message Unknown caller.

Workaround—Configure the primary number as the E164 number and configure the E164 number as the primary number. This allows the primary number to be matched and VVE to show the first name and last name of the caller.

Open Caveats—Cisco Unity Express Release 2.3.1

This section describes possibly unexpected behavior by Cisco Unity Express 2.3.1. All the caveats listed in this section are open in Cisco Unity Express 2.3.1. This section describes severity 2 caveats and select severity 3 caveats.

CSCsb62184

Symptoms—The call gets disconnected and CUE plays the prompt "Goodbye" instead of transferring to the operator.

Condition— Symptoms occur when the operator number is configured to '0' CUE is upgraded to 2.3.1

Workaround—Configure the operator number.

CSCsd87985

Symptoms—While doing semi-attended transfer, CUE plays the prompt "Sorry we are currently experiencing an internal system problems".

Conditions—When a SCCP phone calls the Auto-Attendant (AA), and the AA transfers (semi-attended transfer) the call to voice-mail. While transferring, the system receives an IllegalContactStateException and the system displays the message shown above.

Resolved Caveats—Cisco Unity Express Release 2.3.4

Conditions—When CUE receives packets out of order or when receiving VAD packets, this may cause the voicemail greeting to be inaccessible.

Workaround—None.

CSCsh30313

Symptoms—The NM-CUE, NM-CUE-EC, or AIM-CUE does not support the change in Daylight Saving Time (DST) for U.S. timezones mandated by the Energy Policy Act of 2005.

Conditions—Because of the change in Daylight Saving Time for U.S. timezones beginning in March 2007, the timestamps in the network module software will be one hour behind during selected times of the year.

Workaround—Upgrade the NM-CUE, NM-CUE-EC or AIM-CUE to support Cisco Unity Express 2.3.4.

Resolved Caveats—Cisco Unity Express Release 2.3.3

CSCsf04745

Symptom—With CUE version 2.3.1and 2.3.2, users are unable to have more than four active scripts (3 custom + the default) installed. Users try to add these scripts: voicemail > auto attendant.

Conditions—NM or AIM CUE running version 2.3.1, 2.3.2

Workaround—None in 2.3.1. In 2.3.2, load version 2.2.

CSCsg13714

Symptoms—CUE AA stops sending audio to callers.

Condition—CUE AA answers calls, but the caller hears no audio.

Workaround—Reload the CUE module.

CSCsg19045

Symptom—CUE runs out of memory and reloads.

Conditions—When using CUE with CME and DTMF, the relay method used is SIP-notify under the SIP subsystem, module runs out of memory.

Pressing DTMF digits and recording the message causes CUE to receives some VAD packets which CUE cannot handle properly. The DTMF digits are lost after that.

Workaround—None

CSCsd87985

Symptom—While doing semi-attended transfer, CUE plays the prompt "Sorry we currently experiencing an internal system problems".

Conditions—When SCCP phone (A) calls AA (Auto-Attendant) and AA transfers (semi-attended transfer) the call to VM, the system generates ant IllegalContactStateException and CUE plays the prompt "Sorry we are currently experiencing an internal system problem".

Workaround—None

CSCse35847

Symptom—The load/unload code is not working.

Conditions—The test result regarding the load/unload data is unexpected. It is having more load/unload operations than the one without the fix.

Workaround—None.

CSCse39392

Symptom—There is dead air on Auto Attendant voice mails, occurring intermittently. Dead air continues on all CUE calls until CUE is reset.

Resolved Caveats—Cisco Unity Express Release 2.3.1

There are no resolved caveats in Cisco Unity Express Release 2.3.1.

Caveats in Cisco Unified CallManager Express Release 4.0 that May Impact Your System

Note Although these caveats are not in Cisco Unity Express, these Cisco Unified CallManager Express caveats will affect the Cisco Unity Express environment. It is not the purpose of this document to describe Cisco Unified CallManager Express caveats, but to provide additional information about the interaction of Cisco Unity Express and Cisco Unified CallManager Express when necessary.

Symptoms—There is one way audio between two SCCP phones after a call is transferred from Cisco Unity Express.

Conditions—Sometimes the symptom does not occur, which indicates a timing issue.

Workaround—There is no workaround.

CSCsc98250

Symptoms—Cisco Unified CallManager Express does not send the Call-Info header in 200 OK in response to an INVITE message. DTMF negotiation fails in Cisco Unity Express.

Conditions—When Cisco Unified CallManager Express receives the INVITE message with the Call-Info header from Cisco Unity Express, Cisco Unified CallManager Express does not send the Call-Info header in 200 OK to Cisco Unity Express. This behavior is seen when Cisco Unity Express sends an INVITE message to the SIP phone on Cisco Unified CallManager Express. When Cisco Unity Express sends an INVITE message for the SCCP phone on Cisco Unified CallManager Express, the Call-Info header is received in 200 OK.

Workaround—There is no workaround.

CSCsd05820

Symptoms—After a is call transferred, Cisco Unified CallManager Express does not forward DTMF in the NOTIFY message to Cisco Unity Express.

Provides an overview of writing auto-attendant scripts for Cisco Unity Express Release 2.3 by using the Cisco Unity Express Script Editor and includes a line-by-line description of a sample script, and a script step reference.

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