Guest

Cisco Unity

Release Notes for Cisco Unity Release 3.1(2c)

 Feedback

Table Of Contents

Release Notes for Cisco Unity Release 3.1(2c)

Contents

Supported Product Combinations for Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager

Determining the Cisco Unity Version in Use

Upgrading to Cisco Unity 3.1(2c)

New and Changed Support

New and Changed Support—Release 3.1(2c)

AMIS-Compliant Voice Messaging Systems Qualified for Use with Cisco Unity

New and Changed Functionality

New and Changed Functionality—Release 3.1(2c)

Changing the Display Language for Cisco Unity Event Log Messages

Resolved Caveats

Resolved Caveats—Release 3.1(2c)

Resolved Caveats—Release 3.1(2b)

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for Cisco Unity Release 3.1(2c)


Published March 19, 2002

These release notes contain upgrade information, new and changed functionality, and resolved caveats for Cisco Unity Release 3.1(2c).

For Cisco Unity 3.1(2c), 3.1(2b), and 3.1(2) open caveats, refer to Release Notes for Cisco Unity Release 3.1(2), available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/rel_note/cu312rn.htm. For Cisco Unity 3.1(2) new and changed support, new and changed functionality, limitations and restrictions, resolved caveats, and documentation updates, also refer to Release Notes for Cisco Unity Release 3.1(2).

Access the latest software upgrades for Cisco Unity on the Cisco Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Contents

These release notes contain the following sections:

Supported Product Combinations for Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager

Determining the Cisco Unity Version in Use

Upgrading to Cisco Unity 3.1(2c)

New and Changed Support

New and Changed Functionality

Resolved Caveats

Obtaining Documentation

Obtaining Technical Assistance

Supported Product Combinations for Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager

Cisco Unity version 3.1(2c) has been qualified for the following product combinations with the Cisco Unity-CM TSP and Cisco CallManager.

Table 1 Supported Product Combinations 

Cisco Unity
Cisco Unity-CM
TSP
Cisco CallManager

3.1(2c)

6.0(1),
3.1(2)

3.2(1), 3.1(3), 3.1(2c), 3.0(12), 3.0(11)


For the most current list of all qualified product combinations—including combinations qualified since the release of Cisco Unity version 3.1(2c)—refer to the "Supported Product Combinations for Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.


Note In versions earlier than 3.1(1), the Cisco Unity-CM TSP was known as the AV-Cisco TSP.


Determining the Cisco Unity Version in Use

The following three procedures describe ways to determine the Cisco Unity version.

To determine whether the Cisco Unity version is 3.1(2), 3.1(2b), or 3.1(2c) by using the CD1.ID file


Step 1 Using Notepad, open the CD1.ID file on the Cisco Unity CD 1 disc or disc image.

Step 2 The following information indicates the Cisco Unity version:

UN312ML1A
Cisco
Unity
3.1(2)
A

Cisco Unity version 3.1(2)

UN312ML1B
Cisco
Unity
3.1(2)
B

Cisco Unity version 3.1(2b)

UN312ML1C
Cisco
Unity
3.1(2)
C

Cisco Unity version 3.1(2c)



To determine whether the Cisco Unity version is 3.1(2) or 3.1(2b) by looking at the Setup.exe file on the Cisco Unity server


Step 1 Browse to the directory CommServer\ConfigurationSetup, and locate the Setup.exe file.

Step 2 The date, time, and size of the Setup.exe file indicate the Cisco Unity version:

12/31/2001
19:08
901 KB

Cisco Unity version 3.1(2)

2/1/2002
12:46
896 KB

Cisco Unity version 3.1(2b)



To determine whether the Cisco Unity version is 3.1(2) or 3.1(2c) by looking at the AvCsMgr.exe file on the Cisco Unity server


Step 1 Browse to the CommServer directory.

Step 2 Right-click AvCsMgr.exe, and click Properties.

Step 3 In the Properties window, click the Version tab.

Step 4 In the Item Name list, click Product Version. The Cisco Unity version is displayed in the Value window.


Upgrading to Cisco Unity 3.1(2c)

On the Software Center website, the file CiscoUnity3.1.2bPatchFrom3.1.1.exe and the Cisco Unity 3.1(2b) CD1 disc image have been replaced with the following:

CiscoUnity3.1.2cPatchFrom3.1.1.exe file

Replaces the file
CiscoUnity3.1.2bPatchFrom3.1.1.exe
(which replaced the file
CiscoUnity3.1.2PatchFrom3.1.1.exe)

Cisco Unity 3.1(2c) CD1 disc image

Replaces the disc image
Cisco Unity 3.1(2b) CD1
(which replaced the disc image
Cisco Unity 3.1(2) CD1)


For download and upgrade instructions, refer to the applicable section in Release Notes for Cisco Unity Release 3.1(2), depending on your version of Cisco Unity:

"Upgrading to Cisco Unity 3.1(2) from Version 3.1(1)"

"Upgrading to Cisco Unity 3.1(2) from Version 3.0 or 2.4(6)"

The Cisco Unity 3.1(2) release notes are available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/rel_note/cu312rn.htm.

New and Changed Support

New and Changed Support—Release 3.1(2c)

AMIS-Compliant Voice Messaging Systems Qualified for Use with Cisco Unity

Centigram Voice Mail has been qualified for use with Cisco Unity version 3.1(2) and later.


Note When using AMIS networking with voice gateways, make sure the gateways can pass DTMF in both directions and that both the sending and receiving nodes can detect these digits. Otherwise, AMIS messages may be lost or misdirected, or other malfunctions may occur.


For the most current list of all supported AMIS-compliant voice messaging systems—including systems qualified since the release of Cisco Unity version 3.1(2)—refer to the "Supported AMIS-Compliant Voice Messaging Systems" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

New and Changed Functionality

New and Changed Functionality—Release 3.1(2c)

Changing the Display Language for Cisco Unity Event Log Messages

The Cisco Unity Diagnostic Tool allows you to temporarily change the display language for Windows Event log messages that are generated by Cisco Unity.

To change the Windows Event log display language for Cisco Unity-generated messages


Step 1 On the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Diagnostic Tool.

Step 2 In the left pane of the Cisco Unity Diagnostic Tool, click Cisco Unity Diagnostic Tool > Processes. The node expands to list each process that uses log manager.

Step 3 Right-click Processes or the individual process node of your choice.

Step 4 Click Change Cisco Unity Event Log Language.

Step 5 Click a new language from the list of available languages.

Step 6 Click Apply, then click OK.

Step 7 In the left pane of the Cisco Unity Diagnostic Tool, click Event Viewer (Local) then click the log file category you wish to view.

When the Cisco Unity Diagnostic Tool is closed, Cisco Unity Event log messages revert to the original language.


Resolved Caveats

This section describes only severity 1, 2, and select severity 3 caveats.

If you have an account with Cisco.com, you can use Bug Toolkit to find caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.


Note For Cisco Unity 3.1(2c), 3.1(2b), and 3.1(2) open caveats, refer to Release Notes for Cisco Unity Release 3.1(2), available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/rel_note/cu312rn.htm.


Resolved Caveats—Release 3.1(2c)

Table 2 Cisco Unity Release 3.1(2c) Resolved Caveats 

Caveat Number
Description

CSCae06736

Enhancement request: Allow the display language for Windows Event log messages generated by Cisco Unity to be set in the Cisco Unity Diagnostic Tool.

CSCdu38728

CSCdw61959

In Cisco Unity Import for Exchange 2000, the Exchange server list should contain a list of subscribers from the selected domain who reside on the selected Exchange server.

Note that caveat CSCdx00823, which has very similar symptoms to CSCdu38728 and CSCdw61959, is still open.

CSCdw11833

A buffer overrun causes MIU errors and a port lockup. (Applies to Cisco CallManager integrations only.)

CSCdw37376

In an organization with multiple Exchange 5.5 sites, the AMIS gateway fails to deliver outbound messages to Uamis mailboxes associated with Cisco Unity that are located on another Exchange site.

CSCdw39160

When Failover from Secondary is implemented, scheduled failback cannot be used. Either the primary server must be active when it is running, or the interleaved ports configuration must be used without enabling Failover from Secondary.

To implement the fix

Cisco Unity-CM TSP version 6.0(1) or later is required. (Applies to Cisco CallManager integrations only.)

CSCdw48240

Traces enabled or changed on the Cisco Unity Administrator Tools page are not saved.

CSCdw59379

CSCdw59570

CSCdw85596

CSCdv87611

Administrators should be able to log on to the Cisco Unity Administrator without requiring Local Admin rights on the Cisco Unity server.

CSCdw61404

During failover or failback, subscriber MWIs are not always illuminated and message notifications are not always sent when new messages arrive.

CSCdw68215

Cisco Unity stops responding after sitting idle for one week or longer.

CSCdw88890

Cisco Unity ports lock up and Cisco Unity stops answering calls or drops calls when a subscriber uses the speed-control keys in an environment with IP phones and the G.729a codec.

CSCdw91072

Calls in to the Cisco Unity system may receive the fail-safe message due to Cisco Unity losing connection to the SQL database.

CSCdw91796

The Cisco Unity Diagnostic Tool crashes when attempting to view a log file if a messaging DLL (*_MC.dll) is missing the string associated with logged output.


Resolved Caveats—Release 3.1(2b)

Table 3 Cisco Unity Release 3.1(2b) Resolved Caveats 

Caveat Number
Description

CSCdv73752

When the Exchange 5.5 Organization, Site, or Recipients container names contain a comma, a subscriber search in the Cisco Unity Administrator results in the following error message: "A runtime error has occurred. Do you wish to debug? Line 1055 Error: Expected."

CSCdw60729

During Cisco Unity configuration setup, after entering the server name and LDAP port, the following error message is displayed: "NamedProps error, hr=140064. Setup will not continue beyond this point."

CSCdw70697

The Cisco Unity Uninstall utility fails to run because the Subscriberkiller.exe file cannot be located.

CSCdw70707

When running the Bulk Edit utility, run-time error 713 occurs because the Msstdfmt.dll file was not installed.


Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

http://www.cisco.com

Translated documentation is available at the following URL:

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

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click the Fax or Email option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

http://www.cisco.com/register/

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.