Release Notes for Cisco Unity Express 2.1

November 8, 2005

Cisco Unity Express 2.1.3

Text Part Number OL-7213-03

These release notes support Cisco Unity Express (CUE) 2.1 up to and including Cisco Unity Express 2.1.3. These release notes are updated as needed to describe new hardware support, features, and related documents.

We recommend that you view 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.

Note The user documentation for Cisco Unity Express refers to this release as 2.1. The 2.1.3 release is the third release version for Cisco Unity Express 2.1. Future maintenance release versions of Cisco Unity Express 2.1 may be released.

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

The following Cisco Unity Express licenses are available for the Cisco Unity Express 2.1 release:

Cisco Unity Express Network Module

•Licenses for Cisco Unified CallManager:

–SCUE-12CCM-2.1.3

–SCUE-25CCM-2.1.3

–SCUE-50CCM-2.1.3

–SCUE-100CCM-2.1.3

•Licenses for Cisco CallManager Express:

–SCUE-12CME-2.1.3

–SCUE-25CME-2.1.3

–SCUE-50CME-2.1.3

–SCUE-100CME-2.1.3

Cisco Unity Express AIM

•Licenses for Cisco Unified CallManager:

–SCUE-12CCM-2.1.3

–SCUE-25CCM-2.1.3

–SCUE-50CCM-2.1.3

•Licenses for Cisco CallManager Express:

–SCUE-12CME-2.1.3

–SCUE-25CME-2.1.3

–SCUE-50CME-2.1.3

Note Prior to release 4.0, Cisco Unified CallManager was known as Cisco CallManager.

Factory-set system capacities for mailboxes, storage hours, ports, scripts, and prompts are determined by the ordered license. System capacities for the NM-CUE and NM-CUE-EC are shown in Table 4 and Table 5. System capacities for the AIM-CUE are shown in Table 6 and Table 7.

Software Upgrade Overview

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

•Upgrade using the online installer with the software install upgrade command. For specific procedures, see the following documentation:

Table 8 provides a matrix of the upgrade processes available for the different software releases. The upgrade process key for Table 8 is as follows:

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

Table 8 Cisco Unity Express Software Upgrade Process Matrix

Upgrade from this release:

To this release:

2.1.3

2.1.2

2.1.1

2.0.2

2.0.1

2.1.2

A, C

—

—

—

—

2.1.1

B, C

A, C

—

—

—

2.0.2

B, C

B, C

B, C

—

—

2.0.1

B, C

B, C

B, C

B, C

—

1.1.2

C

C

C

C

C

Caution If you upgrade using either of the "clean" installation processes, the existing configuration files on the system are not preserved. 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.

The following are important notes to consider when planning your software upgrade:

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

•Using the online installer, you can only upgrade to Cisco Unity Express Release 2.1.3 from Cisco Unity Express Release 2.1.2. You must perform a clean installation of Release 2.1.3 to upgrade from any other version. Not all files are required to perform the upgrade using the online installer. Table 3 lists the Cisco Unity Express Release 2.1 files required to upgrade the software using the online installer.

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

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

•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 from the beginning.

Upgrade Error Messages

When performing an online upgrade to CUE 2.1.3, a series of error messages are generated as the existing system shuts down and prepares for the install and cutover to the newly downloaded image. These messages are harmless, and happen because the running software tries to stop programs in the process of shutting down.

The following error messages may display on the CUE console during the online upgrade, but can be disregarded:

1Prior to Release 4.0, Cisco Unified CallManager was known as Cisco CallManager.

Cisco Unity Express Compatibility with Cisco Unified CallManager

Cisco Unity Express Compatibility with Cisco CallManager Express

Table 10 lists the Cisco Unity Express releases that are compatible with different versions of Cisco CallManager Express. This table applies to Cisco Unity Express software licenses with the format SCUE-LIC-xxCME.

New Features and Enhancements in Cisco Unity Express 2.1.2

New Features and Enhancements in Cisco Unity Express 2.1.1

Cisco Unity Express Release 2.1 introduces a number of important features and enhancements, including the following:

•Administration Via Telephone

Cisco Unity Express Release 2.1 introduces the Administration Via Telephone (AVT), previously known as the Greeting Management System (GMS). The ability for an administrator, or other privileged user, to create and address broadcast messages is added to this Telephony User Interface (TUI) based management tool in Release 2.1. Also new with Release 2.1 is the ability to add recorded names and locations to the Unity Express local directory for easier addressing of messages to remote users. Administrators also use the AVT to record and manage Cisco Unity Express automated attendant prompts and alternate greetings for the automated attendant.

•Capacity Enhancements

Release 2.1 introduces the Cisco Unity Express Network Module Enhanced Capacity (NM-CUE-EC), which supports 16 ports of concurrent voice mail or automated-attendant sessions for all license levels. Release 2.1 also improves the port capacity of the AIM-CUE on all integrated services routers (Cisco 2800 and Cisco 3800 series) and Cisco 3700 series routers from the previous limitation of four ports to six ports of concurrent voice mail or automated attendant for all license levels. When running on a Cisco 2600XM or Cisco 2691 multiservice access router, the AIM-CUE will continue to support four ports. The AIM-CUE will detect on which platform it is running and adjust the port capacity automatically.

•Spoken Name Confirmation

Cisco Unity Express provides spoken name confirmation for all local recipients and beginning with Release 2.1, many remote recipients. Spoken name confirmation ensures that the correct recipient has been selected when a user addresses a voice-mail message. The confirmation includes the remote location information, if applicable, to ensure that the message is sent to the correct user and location. Cisco Unity Express uses an extension to the local directory populated by the administrator or vCard information available through the VPIM message to provide spoken name for remote users.

•Distribution Lists

The public and private distribution list function provided by Cisco Unity Express allows a voice-mail message to be simply and quickly addressed to a list of predefined recipients, saving time and minimizing keying errors. Cisco Unity Express includes an "all users" public distribution list and the ability for a privileged user to define up to 15 other public lists. Individual users may define up to 5 private lists of their own. A member of a distribution list may be a user, a GDM, a group, or other distribution lists. Remote users and blind addresses may also be members of distribution lists.

•Broadcast Messages

Like distribution lists, broadcast messages also allow a message to be delivered to multiple recipients, specifically, all the users on the local Cisco Unity Express system or all the users at a remote location. Additionally, broadcast messages mean that important communications are given top priority in the recipient's voice message queue. These special messages are played out before any other messages and will remain in the user's mailbox until the message is retrieved in full or expires, ensuring critical communications are heard. Broadcast messages are managed through Administration Via Telephony, a privileged user interface that, in addition to other system management functionality, allows broadcast messages to be created, broadcast messages to be sent to local users and remote locations and broadcast message expiries to be defined.

•Undelete Messages

If a message is inadvertently deleted during a Cisco Unity Express voice mail-message session, the user now has the option to undelete the message and return it to an active state within the same session. This feature provides users with improved voice message management.

Beginning with Release 2.1, as a configuration option any licensed number of General Delivery Mailboxes may be repurposed as personal mailboxes, expanding the capacity of each license level from 12, 25, 50, and 100 up to 17, 25, 65, and 120 personal mailboxes, respectively.

•Automated Attendant Enhancements

The Cisco Unity Express automated attendant has been enhanced with holiday schedules and business hours for use with the standard automated attendant or an automated attendant script that has been customized using the Cisco Unity Express Editor.

•Calling Line Identification (CLID) Information Availability for all Voice Messages

As a configuration option, Calling Line Identification information is now available for all voice-mail messages, whether the call originates from another Cisco Unity Express user on the same system or from the PSTN.

•Password and PIN Minimum Length Flexibility

Prior to Cisco Unity Express Release 2.1, the minimum length for a password and PIN was fixed at three. Beginning with Release 2.1, the minimum password and PIN length is configurable through either the CLI or the GUI.

•Password and PIN Expiry Time

This functionality permits the administrator to configure the password and PIN expiry time on a system-wide basis. The expiry time is the time in days for which the password and PIN are valid. When this time is reached, the user must enter a new password or PIN. If this option is not configured, passwords and PINs do not expire.

•Restore to Factory Defaults

This functionality allows administrators to work with Cisco Unity Express as if it were just shipped from the Cisco factory. This feature enables reusing or rotating inventory from site to site or for administrator training purposes.

Important Notes

U.S. Daylight Savings Time Changes Require Reconfiguration of Time Zones

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.

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.

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.

AIM-CUE with 512-MB Compact Flash Storage Capacity May Crash

The Cisco Unity Express AIM-CUE module equipped with 512 MB of compact flash may crash if the voice-mail storage capacity is completely used up. This is expected to occur when recording time exceeds 6 hours. Previously, the product had been specified to support 8 hours of voice-mail storage. Cisco recommends that the AIM-CUE module with 512 MB of compact flash be replaced with an AIM-CUE module with 1 GB of compact flash. For more specific information, see the Field Notice at the following URL:

http://www.cisco.com/warp/customer/770/fn61964.shtml

French Language Support in Cisco Unity Express Release 2.1

French (European) language prompts which were not supported in Cisco Unity Express Release 2.1.1 are supported in Cisco Unity Express Release 2.1.2.

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.

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.

This section lists open caveats in Cisco Unity Express 2.1.3, 2.1.2 and 2.1.1.

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

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

The following caveats are resolved in Cisco Unity Express Release 2.1.3:

•CSCsb32599

Symptoms: With caller ID announcement in the Cisco Unity Express voicemail system, when a message is left from a number that overlaps with an existing network location ID, Cisco Unity Express assumes the message was from the network location and strips off the overlapping portion when playing back the caller ID.

For example, with a network location ID of 5 and a voicemail message left from 5550100, Cisco Unity Express assumes this is from mailbox 550100 at location 5 and plays out the caller ID in the voicemail system as such.

Workaround: There is no known workaround.

•CSCsb33807

Symptoms: In a rare situation, if the telco switch is not sending a proper disconnect signal, Cisco Unity Express loops the call between the VM and AA causing the AA greetings to get recorded in a subscribers voice mailbox, filling the voice mailbox.

Workaround: There is no known workaround.

•CSCeh08681

Symptoms: If a user tries to remove a mailbox assigned to a group right after Cisco Unity Express comes up, (this is the first action performed), either through GUI or CLI, the operation fails. The GDM does get deleted successfully on a second attempt.

Workaround: Try again! It will work the second time.

•CSCeh10237

Symptoms: The default broadcast message expiry time is 30 days. But this can be configured to a maximum of 365 days. When the broadcast message expiry time is configured to 365 days, the time rolls over a year and the broadcast expiry time is set to the current date.

The second problem is if the broadcast expiry time on 31 December is set for 1 January (next year), the prompt plays "The message will expire on 1st of January" rather then "The message will expire tomorrow".

Workaround: Do not configure the broadcast message expiry time to 365 days. Configure a value between 1 and 364.

Condition: Cisco Unity for Domino 4.0(5) using VPIM Networking to send VPIM messages to Cisco Unity Express 2.1(2). Intermittently there may be problems with the audio attachments in the message that is being received by the Cisco Unity Express that is causing the crash to occur.

Workaround: There is no known workaround.

•CSCeh14151

Symptoms: Upon trying to add/modify members from the Everyone Public list, the user hears the prompt "Sorry, you are not authorized to edit this list". The control then goes back to the previous menu and the following prompts are played out:

"To add a member, press 1. To hear the current members, press 2..."

"For help, press 0."

If user does not select any of the given choices and allows a timeout, the call gets disconnected.

The correct behavior is that after playing out "Sorry, you are not authorized to edit this list", the control should go two levels up to the menu which asks the user to enter the public list number.

Workaround: Do not allow the timeout. Press * to go back to the main distribution list menu.

•CSCeh15213

Symptoms: Sometimes a misqueued message in network message queue can hold up the delivery of other network messages which has an earlier timestamp than the misqueued message.

Workaround: Currently there is no workaround. The user must wait until the misqueued message is pushed into the running job queue.

•CSCeh47505

Symptoms: A Cisco Unity Express subscriber attempting to reply to a VPIM message from an unknown caller to Cisco Unity either hears "Sorry, this system is temporarily unable to complete your call. Please call again later." The call is then disconnected or receives a failure on sending the reply they have recorded.

Conditions: This can occur when using VPIM networking between Cisco Unity Express and Cisco Unity and Cisco Unity is configured to allow unknown callers to address messages to VPIM subscribers, which correspond to subscribers on Cisco Unity Express. The message is successfully delivered to the Cisco Unity Express subscriber and can be reviewed. The problems occur if an attempt is made to reply to the message. If a prefix is defined for the location corresponding to Unity, the subscriber hears a failsafe conversation and is disconnected. If the location does not have a prefix defined, an attempt to send a recorded reply results in an error.

Workaround: No workaround is available other than not to attempt a reply to a message of this type. A reply should not be allowed anyway because the problem occurs only with the handling of the condition.

Note that messages of this type are delivered from non-mail-user@unitydomain and if remote caching is enabled, Cisco Unity Express can place an entry in the cache table. Then, when a message is announced to the receiving subscriber, the "from" value does not include an extension number. The subscriber hears only "From extension at Cisco Unity location name".

•CSCsa75464

Symptoms: A non-delivery receipt is received in response to a fax message which says "Could not deliver the message in the time limit specified. Please retry or contact your administrator". If delivery is attempted again, the same error results. The receipt may be received 2 days after sending the original message, depending on the SMTP delivery delay settings configured on the sending system.

Conditions: This can occur when using VPIM networking between Cisco Unity Express and Cisco Unity and an attempt is made to send a fax message to a subscriber on the Unity Express system.

Workaround: There is no known workaround.

•CSCsa75447

Symptoms: A non-delivery receipt is sent to a Cisco Unity Express subscriber indicating that message delivery failed because the format was not accepted by the remote system, though the remote system does support the format.

Conditions: This can occur when the mailbox for the intended recipient is full and can no longer accept messages. In this case the delivery failure reason is reported incorrectly as unsupported format when it should indicate mailbox full.

Workaround: There is no known workaround.

•CSCeg86775

Symptoms: When sending a network message between 2 locations and the phone prefix information for the 2 locations does not match on the sending and receiving systems, the message is rejected by the receiving system. This generates a Non Delivery Receipt in the senders mailbox. If the phone prefix information is then corrected for the 2 locations and the user resends the message attached to the Non Delivery Receipt, the message is still rejected. The message has the fully translated network addresses of the sender and recipient and one of these is now incorrect.

Workaround: Make sure that phone prefix information configured at a location matches the phone prefix information configured at each matching remote location. Also, users should not use the resend option of the Non Delivery Receipt menu to resend the message to the intended recipient. Instead, they should re-record the message and send it again using the normal message send menu.

•CSCeg89943

Symptoms: When a global broadcast message is recorded to send to all the configured locations and the network messaging is disabled just before sending the message, a Non Delivery Record is not generated for the local broadcast message. However, if the network messaging is disabled before recording the message, the system does not allow the admin to record the broadcast message.

Workaround: Do not disable the network messaging after recording a broadcast message and before sending the broadcast message to all configured locations.

•CSCeh11196

Symptoms: When addressing a message and the message is not currently addressed to any one, the menu prompt "To add a name, press 1. To send the message, press #. To exit press *" is played. When "3" is pressed in response, the call disconnects after playing the prompt "Sorry. That is a not a valid selection. Please try again". Instead, the system should play the error prompt and play the menu prompt again.

Workaround: Do not press "3" in response to this prompt. Or, Login to the mailbox again and readdress and re-record the message.

•CSCsa82454

Symptoms: After running Disk cleanup to recover space on a Cisco Unity Express system where the hard drive has filled up, the system may not boot or not all functions may work.

Workaround: There is no known workaround. Under some circumstances, the system needs to have its software loaded fresh again and the configuration and data restored from backup.

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

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

The following caveats are open in Cisco Unity Express Release 2.1.2:

•CSCsb05032

Symptoms: When Cisco Unity Express gets NDR for broadcast message, it saves the attached message as a broadcast message instead of a network broadcast message.

Conditions: Sending a broadcast message to a remote site with an invalid vpim id causes Cisco Unity Express to receive an NDR for that broadcast message. Cisco Unity Express saves the attached message as a local broadcast message, so all the local mailboxes get the broadcast message.

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

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

The following caveats are resolved in Cisco Unity Express Release 2.1.2:

•CSCeg85429

Symptoms: If a script containing a time step is created on a personal computer in one timezone and executed in another timezone, the time ranges in the time step do not reflect the set time range.

Conditions: The time set in the time step is stored as a calendar object with Jan. 1, 1999 as the base time. At run time, to find whether the current time falls in one of the time ranges, just the current time (hour, minute and second) are compared with the time in the time step.

If the time zones of the time in the time step is different from the current time zone, the time comparison to find whether the current time falls in one of the time ranges does not work.

This problem appears even when the timezone is changed on the personal computer.

Workaround: Change the time on the personal computer with which the script is edited to the timezone where this script will be used.

•CSCeg51165

Symptoms: The voice mail time stamp for Australia NSW runs one hour ahead of the clock on Cisco Unity Express.

Conditions: This occurs only on an AIM-CUE, not NM-CUE.

Workaround: There is no workaround.

•CSCeh63819

Symptoms: The router might crash after receiving and processing a malformed DNS packet.

Conditions: The problem only happens in parsing a malicious compressed string.

Workaround: There is no workaround.

•CSCed30264

Symptoms: If a caller does a zero-out to an extension and that extension has Call Forward Busy or Call Forward All to VoiceMail and the call gets forwarded to VoiceMail, the caller hears a prompt "Sorry, this extension does not have a mailbox associated with it." In this case, the caller is not able to leave a message. However, if that extension has Call Forward No Answer to VoiceMail and the call gets forwarded to VoiceMail, the caller hears the mailbox greeting and is able to leave a voice mail.

Conditions: This problem exists only in Cisco Unified CallManager mode. It does not exist in Cisco CallManager Express mode.

Workaround: There is no workaround.

•CSCeg60609

Symptoms: The Cisco Unity Express Script Editor and CRS Script Editor can not be installed on the same machine.

Conditions:

Workaround: There is no workaround.

•CSCeg63452

Symptoms: When recording a message from a 7912 phone in Cisco Unity Express, the begin-recording Prompt from VoiceMail is not always audible. This happens intermittently but only for this model of IP phone.

Conditions:

Workaround: There is no workaround.

•CSCeh55158

Symptoms: With Cisco Unity Express 2.0.1 and 2.1.1, the AIM-CUE disk can be come full, resulting in the Call Unity Express module rebooting or not booting at all. The behavior resembles that which is described in http://www.cisco.com/warp/public/770/fn61964.shtml

Conditions: The symptoms can arise after uninterrupted operation for some period of time and many messages have been recorded and deleted.

Workaround: Currently, preventative action requires you to periodically reboot the AIM-CUE module. It is not necessary to reload the entire router.

If the Cisco Unity Express module does not boot, the same workarounds as described in http://www.cisco.com/warp/public/770/fn61964.shtml can be used. The disk compact utility frees up disk space and should restore system operation. This utility is available through the Cisco TAC.

•CSCeh60198

Symptoms: Uploading a script with the GUI fails and gives the error message:

Conditions: If a user on Cisco CallManager Express or Cisco Unified CallManager has a space in the user ID, when an attempt is made to import that user to Cisco Unity Express, this error message appears.

Workaround: Do not create user IDs with spaces on Cisco Unified CallManager or Cisco CallManager Express.

•CSCec64232

Symptoms: The Cisco Unity Express module fails to reload.

Conditions: On rare occasions, when the Cisco Unity Express module is reloaded from the CLI or GUI, it might get stuck during the reload process. The CLI console will display messages similar to the following, and the module will not reload:

MONITOR EXIT...

INIT: Switching to runlevel: 6

INIT: Sending processes the TERM signal

Workaround: Reset the Cisco Unity Express module using the Cisco IOS CLI from the router.

•CSCed58324

Symptoms: The Cisco Unity Express system is slow to reboot.

Conditions: Occasionally on a reboot, the Cisco Unity Express system will not come online after 1200 seconds. The following messages are seen on the system console:

waiting 1201 ...TIMEOUT

It looks like things are stuck, trying a monitor interrupt.

MONITOR EXITING...

And the system reboots. On this subsequent reboot, the system starts up and comes online with no problem.

Workaround: There is no workaround. The system comes online on the subsequent reboot.

Conditions: This symptom is observed on Cisco CallManager Express routers receiving inbound calls from SIP proxy or SIP registrar, which are transferred or forwarded to Cisco Unity Express.

Workaround: There is no workaround.

•CSCeg37049

Symptoms: There is a script refresh failure when scripts are uploaded.

Conditions: When scripts to Cisco Unity Express are uploaded via the GUI interface, the error "Script refresh failed" may sometimes occur. Subsequent uploads of any scripts, through either the GUI or the CLI, will then fail every time.

Workaround: Reload the Cisco Unity Express module by issuing the reload command in the CLI or by clicking on "Reload Unity Express" in the GUI web page Administration->ControlPanel.

•CSCeg43166

Symptoms: The following crash message is seen when the Cisco Unity Express network module or AIM boots up:

Conditions: The network module or AIM was powered off for more than a day, and when it was powered on the next day, during the boot process it crashed because of the cited exception. The network module or AIM booted successfully in subsequent attempts.

Workaround: There is no workaround.

•CSCeg49869

Symptoms: Entering an abbreviated command for displaying group privileges results in an incomplete display.

Conditions: If the abbreviated form of CLI is used on Cisco Unity Express for displaying privileges associated with the groups, the command output displays only the groups and not the privileges associated with the groups. For example, the show groups pri command (privileges abbreviated to pri) displays only group names. It does not display the privileges associated with each group.

Workaround: Instead of using abbreviations for this command, use the full form of the command show groups privileges to display the privilege information associated with each group.

•CSCeg50567

Symptoms: Error message appears during system reboot.

Conditions: Occasionally on a system reboot, the system may fail to come online, and produce an error message, stating that it failed with error status 139 as follows:

EXITED: ${ROOT}/usr/wfavvid/run exit status 139

The system will then reboot successfully.

Workaround: There is no workaround. Allow the system to reboot, because it will come online without a problem.

•CSCeg64699

Symptoms: Trying to import CTI ports fails with the following message appearing:

IOException:http://172.16.0.0/CCMApi/AXL/v1/soapisapi.dll

Conditions: On the configure->callmanager web page, if the web password is entered incorrectly, when you attempt to verify the password, the CTI port import action fails. When you enter the correct password, the CTI ports can be imported.

Workaround: There is no workaround.

•CSCeg65651

Symptoms: The sender receives a Non Delivery Receipt message when the remote system does not accept a message.

Conditions: When a voice mail is addressed to a distribution list or to more than 10 recipients, and if any of the intended recipients is a local mailbox that is disabled, the sender will receive a Non Delivery Receipt message for each disabled mailbox that states that the "Remote system was unable to accept the message" along with the local mailbox information.

If a voice mail is not addressed to a distribution list or to fewer than 10 recipients, and if any of the intended recipients is a local mailbox that is disabled, the sender will receive a notification that the mailbox is disabled along with the local mailbox information.

Workaround: There is no workaround.

•CSCeg71485

Symptoms: The network local location is disabled after a reload.

Conditions: If you delete the network local location and then save your configuration, when you reload Cisco Unity Express, the network local location will remain disabled.

Workaround: After Cisco Unity Express restarts, reenter the network local location id command to reenable networking at this location.

•CSCeg72131

Symptoms: The GUI Help page for "Adding members to a distribution list" has a broken link.

Conditions: On the GUI Help page for "Adding members to a distribution list", there is a link to "Related Link" to "Configuring Distribution Lists." If you click this link, a "Page not Found" error appears.

Workaround: Use the help menu bar on the left side of the screen to get to the help screen for "Adding members to a distribution list".

•CSCeg76878

Symptoms: Holidays configured for leap year may show as invalid after a restore.

Conditions: If a backup is being restored that has holidays configured for a leap year and if February 29 has been configured as a holiday for that year in the backup, then after the restore, an attempt to delete that holiday (February 29) might not succeed. An error message might be displayed, stating that the specified date is invalid.

(config)> no calendar holiday date 2005 02 29

Error: Specified date is invalid

This will not happen for any other date.

Workaround: Use the following CLI to delete this special case holiday:

(config)> no calendar holiday date 2005 02

This will delete all holidays in the month of February, including February 29.

•CSCeg79195

Symptoms: The system fails when the AIM-CUE drive is at capacity.

Conditions: On a system installed with an AIM-CUE with a 512-MB compact flash disk drive, if the drive becomes full, the system can become unstable and fail with various different error conditions, such as calls being disconnected at unexpected points.

Symptoms: A call is not routed successfully when a custom script is used.

Conditions: When the Cisco Unity Express script editor is used to create a custom script, if the Name To User step is used and in the step properties, the Maximum Retries value (on the Input tab) is 0 or 1, then when this step is executed, if no terminating character (# by default) is entered by the caller, the call will not be routed successfully (it will go to the "Timeout" branch of the step). If the Maximum Retires value is 0 or 1 and the Termination Character value is configured as None, then the call will never route to a user.

Workaround: Use a Maximum Retries value of 2 or greater, or require the caller (usually stated in the audio prompt) to enter a termination character (default # or *).

•CSCeg82340

Symptoms: Group names not matched.

Conditions: When doing a spell-by-name, Cisco Unity Express attempts to match group names as well as user names. Because the groups are not valid users, in the instances where a group name is matched, no selection can be made.

Workaround: Make sure group names do not overlap with regular user names. To see all phone keypad mappings, enter the show sysdb command from the Cisco Unity Express CLI and specify the includekeyPadMapping keyword.:

•CSCeg86775

Symptoms: Message is rejected when phone prefix information does not match on sending and receiving systems.

Conditions: When a network message between two locations is sent, if the phone prefix information for the two locations does not match on the sending and receiving systems, then the message will be rejected by the receiving system. This will generate a Non Delivery Receipt (NDR) in the sender's mailbox. If the phone prefix information is then corrected for the two locations and the user tries to resend the message attached to the NDR, then the message will still be rejected because the message has the fully translated network addresses of the sender and recipient as defined at the time of the original send and one of these is now incorrect.

Workaround: Make sure that the phone prefix information configured at a location matches the phone prefix information configured at each matching remote location. Also, the user should not use the resend option of the NDR menu to resend the message to the intended recipient. Instead, the user should re-record the message and send using the normal message send menu.

Conditions: When a global broadcast message is recorded to send to all the configured locations and if network messaging is disabled just before the message is sent, a Non Delivery Receipt (NDR) is not generated for the local broadcast message. However, If the network messaging is disabled before the message is recorded, the system does not allow the administrator to record the broadcast message.

Workaround: Do not disable network messaging after recording a broadcast message but before sending the broadcast message to all configured locations.

•CSCeg90146

Symptoms: Payload download status does not indicate the final size of the download.

Conditions: The payload download status does not indicate the final file payload size during the payload download using the install command.

Workaround: There is no workaround.

•CSCeh03529

Symptoms: Saving a configuration fails when other CLI or GUI commands are initiated at the same time.

Conditions: On a Cisco 2600XM with an AIM-CUE installed, if a save configuration is initiated from the GUI for a large configuration and there are CLI commands or other GUI commands initiated at the same time, the save may fail with the following error:

ERROR: CUE configuration save failed, Cannot set, commit failure

The reason for this error is that the GUI save configuration command is expected to complete in 4 minutes 30 seconds. If the command does not complete after this time passes, the GUI command is aborted with the cited error message.

Workaround: Issue the write configuration command from the CLI.

•CSCeh06960

Symptoms: An error message appears when the GUI is used to add a group with a mailbox.

Conditions: When using the GUI to add a group with a mailbox and the message expiry time is 0, the following error message may appear:

Expiry Time: Error setting attribute: Invalid value

If you then try to change the expiry time value, and click add on the mailbox GUI screen, the following error message may appear:

The owner already has a mailbox. Enter a different owner

Workaround: After the first error message is seen, go to the Voice Mail > Mailboxes screen in the GUI, click on the created mailbox, and edit the expiry time.

•CSCeh07703

Symptoms: When Init Wizard for Cisco Unity Express is run in conjunction with Cisco CallManager 4.1, when the Init Wizard is committed, the CTI ports may fail if the JTAPI user name is incorrectly entered.

Conditions: This problem is seen with Cisco Unified CallManager 4.1 only. With this version of Cisco CallManager, Cisco Unity Express is unable to correctly validate the JTAPI password entered by the administrator.

Workaround: There is no workaround. The users need to be imported again with the correct JTAPI username and password.

Conditions: When the Cisco Unity Express CLI is used to download a remote user spoken name from the Cisco Unity Express system, the operation fails to download the spoken name to the FTP server if the remote user does not have a spoken name configured. The Cisco Unity Express CLI session for which the download command was issued will be disconnected.

Workaround: Configure (that is, upload to Cisco Unity Express) a spoken name for the remote user before attempting to download the remote user spoken name from the Cisco Unity Express system.

Conditions: If a user tries to remove a mailbox assigned to a group through either the GUI or the CLI right after Cisco Unity Express comes up, (that is, this is the first action performed), the operation fails. The GDM does not get deleted.

Workaround: Try to remove the mailbox a second time. Performing this action a second time will successfully remove the mailbox.

•CSCeh10237

Symptoms: The broadcast message expiry time returns to the current date when it is configured to 365 days.

Conditions: The default broadcast message expiry time is 30 days. This value can be configured to a maximum of 365 days. When the broadcast message expiry time is configured to 365 days, the time rolls over a year and the broadcast expiry time is set to the current date.

Workaround: Do not configure the broadcast message expiry time to 365 days. Configure a value between 1 and 364.

•CSCeh11196

Symptoms: A call is disconnected when a menu selection is entered.

Conditions: When a message is addressed and if the message is not currently addressed to anyone, the menu prompt "To add a name, press 1. To send the message, press #. To exit, press *" is played. When the number 3 is pressed at this menu, the prompt "Sorry. That is a not a valid selection. Please try again" plays and the call is disconnected instead of returning to the menu.

Workaround: Do not press the number 3 when the menu prompt "To add a name, press 1. To send the message, press #. To exit, press *." is presented. An alternative workaround is to log in to the mailbox again and readdress and re-record the message.

•CSCeh15307

Symptoms: A configuration mismatch occurs between GUI and CLI configurations.

Conditions: In a Cisco Unity Express environment working with Cisco Unified CallManager, different applications can be associated with the same call-in number. For example, the Voicemail application can be associated with jtapi trigger 2111, and the AutoAttendant application can be associated with SIP trigger 2111. However, the call-in number page can show only one application. This can result in inconsistencies between CLI and GUI configurations.

Workaround: If there is a mismatch between a GUI and CLI configuration, always use the CLI to configure one application for the same trigger number (JTAPI and SIP triggers).

•CSCeh14151

Symptoms: A call gets disconnected if a user waits too long to enter a menu option.

Conditions: Upon trying to add/modify members from the Everyone Public list, a user hears the prompt "Sorry, you are not authorized to edit this list." The control then goes back to the previous menu, and the following prompts are played out:

To add a member, press 1. To hear the current members, press 2. For help, press 0.

If the user does not select any of the given choices, and allows a timeout, then the call gets disconnected.

The correct behavior is that after playing out "Sorry, you are not authorized to edit this list", the control should go two levels up to the menu that asks the user to enter the public list number.

Workaround: Do not allow the timeout. Press the * key to go back to the main distribution list menu.

•CSCsa62783

Symptoms: An error message appears when AVT is not configured.

Conditions: If a user goes to the Voice mail > Call Handling page and the Administration Via Telephone (AVT) number is not configured, then making changes to the voice-mail number and clicking apply gives the error "The AVT call-in number cannot be empty." The AVT number field is not shown as mandatory on this page.

Workaround: Configure a dummy number for the AVT, and then use the CLI to change the voice-mail number.

Related Documentation

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

You can find a listing of all new and revised Cisco technical documentation at this URL:

Documentation DVD

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

Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Tip 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 that has the most recent creation date in this public key server list:

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

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 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 TAC engineer. The TAC Service Request Tool is located at this URL:

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

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, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

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

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

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