Guest

Cisco Unity

Release Notes for Cisco Unity-CM TSP Release 8.1(1)

  • Viewing Options

  • PDF (174.6 KB)
  • Feedback
Release Notes for Cisco Unity-CM TSP Release 8.1(1)

Table Of Contents

Release Notes for Cisco Unity-CM TSP Release 8.1(1)

Contents

System Requirements

System Requirements—Cisco Unity

System Requirements—Cisco Unity Connection

Determining the Software Version

Cisco Unity-CM TSP

Cisco Unity

Cisco Unity Connection

Downloading Cisco Unity-CM TSP Version 8.1(1)

Installing the Cisco Unity-CM TSP

Installing the Cisco Unity-CM TSP on a Cisco Unity 4.x System

Installing the Cisco Unity-CM TSP on a Cisco Unity 3.1(x) System

Installing the Cisco Unity-CM TSP on a Cisco Unity Connection 1.x System

New and Changed Requirements and Support—Release 8.1(1)

New and Changed Functionality—Release 8.1(1)

Integrations Through SCCP Support RFC 2833

Installation and Upgrade Notes

Uninstalling the Cisco Unity-CM TSP

Caveats

Open Caveats—Release 8.1(1)

Resolved Caveats—Release 8.1(1)

Troubleshooting

Cisco Unity and Cisco Unity Connection Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unity-CM TSP Release 8.1(1)


Published November 11, 2005

These release notes contain download and installation instructions, information on new and changed functionality, and caveats for Cisco Unity-CM TAPI service provider (TSP) Release 8.1(1).

The Cisco Unity-CM TSP is used only for the Cisco CallManager and Cisco CallManager Express integrations that use only Skinny Call Control Protocol (SCCP) end points.

Cisco Unity-CM TSP version 8.1(1) is automatically installed with Cisco Unity Connection version 1.1(1). To use version 8.1(1) with Cisco Unity 4.1(1) or a supported earlier version, download it from the Cisco Unity-CM TSP Software Download page on Cisco.com (see the "Downloading Cisco Unity-CM TSP Version 8.1(1)" section).

For a list of qualified version combinations of the Cisco Unity-CM TSP with Cisco CallManager, Cisco CallManager Express, and Cisco Unity or Cisco Unity Connection, see the applicable compatibility matrix:

For a Cisco Unity system, http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

For a Cisco Unity Connection system, http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.

Contents

System Requirements

Determining the Software Version

Downloading Cisco Unity-CM TSP Version 8.1(1)

Installing the Cisco Unity-CM TSP

New and Changed Requirements and Support—Release 8.1(1)

New and Changed Functionality—Release 8.1(1)

Installation and Upgrade Notes

Caveats

Troubleshooting

Cisco Unity and Cisco Unity Connection Documentation

Obtaining Documentation and Submitting a Service Request

System Requirements

See the applicable section, depending on the product:

System Requirements—Cisco Unity

System Requirements—Cisco Unity Connection

System Requirements—Cisco Unity

A supported version of Cisco Unity running on the Cisco Unity server:

For an integration with Cisco CallManager, Cisco Unity 3.0(1) through 4.1(x).

For an integration with Cisco CallManager Express, Cisco Unity 4.0(5) or later.

An account with local administrator privileges must be used to upgrade the Cisco Unity-CM TSP. Otherwise, no Cisco Unity ports will be available after the upgrade.

If you are changing the number of voice messaging ports on the Cisco Unity system, you must adjust the ports in Cisco CallManager before installing the Cisco Unity-CM TSP. Refer to the "Changing the Number of Voice Messaging Ports" section in the applicable version of the Cisco CallManager integration guide for Cisco Unity. Cisco CallManager integration guides for Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

If you are setting up a Cisco CallManager integration for the first time, refer to the applicable version of the Cisco CallManager integration guide for Cisco Unity, instead of using the instructions in these release notes. Cisco CallManager integration guides for Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

System Requirements—Cisco Unity Connection

A supported version of Cisco Unity Connection 1.x running on the Connection server.

An account with local administrator privileges must be used to upgrade the Cisco Unity-CM TSP. Otherwise, no Cisco Unity Connection ports will be available after the upgrade.

If you are changing the number of voice messaging ports on the Cisco Unity Connection system, you must adjust the ports in Cisco CallManager before installing the Cisco Unity-CM TSP. Refer to the "Changing the Number of Voice Messaging Ports" section in the applicable version of the Cisco CallManager integration guide for Cisco Unity Connection. Cisco CallManager integration guides for Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.

If you are setting up a Cisco CallManager integration for the first time, refer to the applicable version of the Cisco CallManager integration guide for Cisco Unity Connection, instead of using the instructions in these release notes. Cisco CallManager integration guides for Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.

Determining the Software Version

This section contains procedures for determining the version in use for the following software:

Cisco Unity-CM TSP

Cisco Unity

Cisco Unity Connection

Cisco Unity-CM TSP

To Determine the Cisco Unity-CM TSP Version


Step 1 Browse to the applicable directory, depending on the Windows version:

Windows 2003

Windows\System32 directory

Other versions

WinNT\System32


Step 2 Right-click AvSkinny.tsp, 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-CM TSP version is displayed in the Value window.


Cisco Unity

To Determine the Cisco Unity Version


Step 1 In the Cisco Unity Administrator, go to the System > Configuration > Software Versions page. The Cisco Unity version is displayed in the Cisco Unity Build Number field.


Cisco Unity Connection

To Determine the Cisco Unity Connection Version by Using Cisco Unity Connection Administration


Step 1 In Cisco Unity Connection Administration, scroll to the bottom of the navigation bar.

Step 2 Click About. The Connection version is displayed below "Cisco Unity Connection."


You can also use the Cisco Unity Connection Server Status utility to determine the version. This is useful when Connection is not running.

To Determine the Cisco Unity Connection Version by Using the Cisco Unity Connection Server Status Utility


Step 1 In the Cisco Unity Connection Server Status utility, click the Server Status tab. The Connection version is displayed in the Version field.


Downloading Cisco Unity-CM TSP Version 8.1(1)

Do the procedure in this section only if you are installing Cisco Unity-CM TSP 8.1(1) for use with a system running Cisco Unity version 4.1(1) or earlier, or a Cisco Unity Connection version later than 1.1(1). (Version 8.1(1) is automatically installed with Cisco Unity Connection 1.1(1).)

To Download the Cisco Unity-CM TSP


Step 1 Confirm that the Cisco Unity server or the Cisco Unity Connection server has at least 6 MB of hard-disk space available for the download file and the extracted files.

Step 2 On a computer with a high-speed Internet connection, go to the Cisco Unity-CM TSP Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-cm-tsp.


Note To access the software download page, you must be logged on to Cisco.com as a registered user.


Step 3 Download the file CiscoUnityCMTSP8.1.1.exe to the directory of your choice.

Step 4 Unzip the file CiscfsoUnityCMTSP8.1.1.exe to the default directory or to the directory of your choice.

Step 5 Delete the file CiscoUnityCMTSP8.1.1.exe to free hard disk space.


Installing the Cisco Unity-CM TSP

See the applicable section, depending on the product and version:

Installing the Cisco Unity-CM TSP on a Cisco Unity 4.x System

Installing the Cisco Unity-CM TSP on a Cisco Unity 3.1(x) System

Installing the Cisco Unity-CM TSP on a Cisco Unity Connection 1.x System

(Note that version Cisco Unity-CM TSP 8.1(1) is automatically installed with Cisco Unity Connection 1.1(1).)

Installing the Cisco Unity-CM TSP on a Cisco Unity 4.x System

Do the procedure in this section only if you are installing Cisco Unity-CM TSP 8.1(1) on a Cisco Unity version 4.x system.

If you are changing the number of voice messaging ports on the Cisco Unity system, you must add a voice messaging port to Cisco CallManager for each port that you are connecting to Cisco Unity before you install the Cisco Unity-CM TSP. Refer to the "Changing the Number of Voice Messaging Ports" section in the applicable version of the Cisco CallManager integration guide for Cisco Unity. Cisco CallManager integration guides for Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

You can keep the previous voice messaging ports, and the Cisco Unity-CM TSP configuration is automatically retained.

To Install the Cisco Unity-CM TSP on a Cisco Unity 4.x System


Step 1 Stop Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Stop Cisco Unity).

Step 2 Browse to the directory in which you saved the extracted Cisco Unity-CM TSP files in the "Downloading Cisco Unity-CM TSP Version 8.1(1)" section, and double-click SkinnySetup.exe.

Step 3 Follow the on-screen prompts.

Step 4 Restart the Cisco Unity server.


Installing the Cisco Unity-CM TSP on a Cisco Unity 3.1(x) System

Do the procedure in this section only if you are installing Cisco Unity-CM TSP 8.1(1) on a Cisco Unity version 3.1(x) system.

Note that if you are changing the number of voice messaging ports on the Cisco Unity system, you must add a voice messaging port to Cisco CallManager for each port that you are connecting to Cisco Unity before you install the Cisco Unity-CM TSP. Refer to the "Changing the Number of Voice Messaging Ports" section in the applicable version of the Cisco CallManager integration guide. Cisco CallManager integration guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

You can keep the previous voice messaging ports, and the Cisco Unity-CM TSP configuration is automatically retained.

To Install the Cisco Unity-CM TSP on a Cisco Unity 3.1(x) System


Step 1 Stop Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Stop Cisco Unity).

Step 2 Browse to the directory in which you saved the extracted Cisco Unity-CM TSP files in the "Downloading Cisco Unity-CM TSP Version 8.1(1)" section, and double-click SkinnySetup.exe.

Step 3 Follow the on-screen prompts.

Step 4 In the Cisco Unity-CM TSP dialog box, in the Select Cisco CallManager list, click the Cisco CallManager server to which Cisco Unity is connected.

If the Select Cisco CallManager list is empty, click Add, enter the IP address of the Cisco CallManager server to which Cisco Unity is connected, then click OK.

Step 5 In the Cisco Unity-CM TSP Settings dialog box, verify the information in the following three fields:

Primary CallManager IP Address

Number of Voice Ports

Device Name Prefix (The prefix must match the prefix for the Voice Mail ports. Note that the device name prefix is case-sensitive.)

Step 6 Confirm that the dial numbers in the MessageWaitingOffDN and MessageWaitingOnDN fields match the Cisco CallManager settings on the applicable Cisco CallManager Administration page:

Cisco CallManager
version 3.2(1) and later

Settings are on the Features > Voice Mail > Message Waiting page in Cisco CallManager Administration.

Cisco CallManager
version 3.1(4) and earlier

Settings are on the Service > Service Parameters page in Cisco CallManager Administration


If the dial numbers are not in the MessageWaiting fields of the Cisco Unity-CM TSP Settings dialog box, enter them.

Step 7 Confirm that the Cisco CallManager Device list displays the correct number of Cisco Unity ports and that the port names match the names of the Voice Mail ports.

Step 8 Click OK.

Step 9 In the Cisco Unity-CM Service Provider dialog box, click Test.

Step 10 In the Test Configuration and Connection dialog box, click OK.

Step 11 If the configuration is correct, the Test Succeeded dialog box appears. Click OK, then skip to Step 13.

If incorrect information was entered during configuration, the Error dialog box appears. Errors can be caused by:

Entering the wrong IP address for the Cisco CallManager server during configuration.

Entering the wrong device name prefix during configuration.

Step 12 Correct errors in the Service Provider dialog box.

In Windows 2000 or Windows 2003, on the Start menu, click Settings > Control Panel > Phone and Modem Options > Advanced > Cisco Unity-CM Service Provider > Settings.

or

In Windows NT, on the Start menu, click Settings > Control Panel > Telephony > Telephony Drivers > Cisco Unity-CM Service Provider > Settings.

Step 13 Restart the Cisco Unity server.


Installing the Cisco Unity-CM TSP on a Cisco Unity Connection 1.x System

Do the procedure in this section only if you are installing Cisco Unity-CM TSP 8.1(1) on a system running a version of Cisco Unity Connection later than 1.1(1). (Note that version 8.1(1) is automatically installed with Cisco Unity Connection 1.1(1).)

If you are changing the number of voice messaging ports on the Connection system, you must add a voice messaging port to Cisco CallManager for each port that you are connecting to Cisco Unity Connection before you install the Cisco Unity-CM TSP. Refer to the "Changing the Number of Voice Messaging Ports" section in the applicable version of the Cisco CallManager integration guide for Cisco Unity Connection. Cisco CallManager integration guides for Connection are available at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.

You can keep the previous voice messaging ports, and the Cisco Unity-CM TSP configuration is automatically retained.

To Install the Cisco Unity-CM TSP on a Cisco Unity Connection 1.x System


Step 1 Stop Cisco Unity Connection (right-click the Cisco Unity Connection icon in the system tray, then click Stop > Cisco Unity Connection).

Step 2 Browse to the directory in which you saved the extracted Cisco Unity-CM TSP files in the "Downloading Cisco Unity-CM TSP Version 8.1(1)" section, and double-click SkinnySetup.exe.

Step 3 Follow the on-screen prompts.

Step 4 Restart the Cisco Unity Connection server.


New and Changed Requirements and Support—Release 8.1(1)

There are no new or changed requirements with Cisco Unity-CM TSP Release 8.1(1).

Refer to the applicable release notes for information on new and changed requirements and support in earlier versions of the Cisco Unity-CM TSP. Release notes for all versions of the Cisco Unity-CM TSP are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

New and Changed Functionality—Release 8.1(1)

This section contains information about new and changed functionality for Cisco Unity-CM TSP Release 8.1(1) only. Refer to the applicable release notes for information on new and changed functionality in earlier versions of the Cisco Unity-CM TSP. Release notes for all versions of the Cisco Unity-CM TSP are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Integrations Through SCCP Support RFC 2833

To comply with RFC 2833, the Cisco Unity-CM TSP can process DTMFs (also known as AVT tones) that are sent in the RTP stream for integrations with Cisco CallManager through Skinny Call Control Protocol (SCCP). This functionality enables communication between Cisco Unity or Cisco Unity Connection on one side, and end points that are RFC 2833-compliant on the other side for integrations with future versions of Cisco CallManager.

Installation and Upgrade Notes

Uninstalling the Cisco Unity-CM TSP

It is not necessary to uninstall an earlier version of the Cisco Unity-CM TSP before installing version 8.1(1). The installation process automatically removes the older Cisco Unity-CM TSP.

Caveats

You can find the latest caveat information for Cisco Unity Connection version 1.1(1)—in addition to caveats of any severity for any release—by using Bug Toolkit, an online tool available for customers to query defects according to their own needs. Bug Toolkit is available at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.


Note To access Bug Toolkit, you must be logged on to Cisco.com as a registered user.


Note that this section contains caveat information for Cisco Unity-CM TSP Release 8.1(1) only. For caveat information for earlier versions of the Cisco Unity-CM TSP, refer to the applicable release notes. Release notes for all versions of the Cisco Unity-CM TSP are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Open Caveats—Release 8.1(1)


Note Table 1 lists caveats for the Cisco Unity and Cisco Unity Connection products.


Click a caveat number link to view the latest information for that caveat in Bug Toolkit.

Table 1 Cisco Unity-CM TSP Release 8.1(1) Open Caveats 

Caveat Number
Component
Severity
Headline

CSCsb87513

telephony

2

Unity VM ports fail to register w/ CCM upon Unity failback

CSCsb33436

telephony

3

With g.729 the packet preceding the CN packet is not always transmitted

CSCsb88560

telephony

3

port lock during supervised transfer if consult call accepts then drops


Resolved Caveats—Release 8.1(1)


Note Table 2 lists caveats for the Cisco Unity and Cisco Unity Connection products.


Click a caveat number link to view the latest information for that caveat in Bug Toolkit.

Table 2 Cisco Unity-CM TSP Release 8.1(1) Resolved Caveat 

Caveat Number
Component
Severity
Heading

CSCsb96445

telephony

2

Unity VM ports fail to register w/ CCM upon Unity failback

CSCsa94512

telephony

3

AvAudio.sys incorrectly reports out-of-sequence packets

CSCsb05840

telephony

3

AvAudio.sys incorrectly reports out-of-sequence packets

CSCsb53087

telephony

3

Skinny device test should not fail if ping server fails

CSCsb61083

telephony

3

Skinny device test should not fail if ping server fails

CSCeg13668

telephony

4

Unity should allow OutsideDialTone on outbound calls and transfers

CSCsb88043

telephony

4

Unity should allow OutsideDialTone on outbound calls and transfers


Troubleshooting

For information on troubleshooting the Cisco Unity-CM TSP and the phone system integration, refer to the Cisco Unity Troubleshooting Guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.

Cisco Unity and Cisco Unity Connection Documentation

For descriptions and URLs of Cisco Unity documentation on Cisco.com, see the Cisco Unity Documentation Guide. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.html.

For descriptions and URLs of Cisco Unity Connection documentation on Cisco.com, see the Cisco Unity Connection Documentation Guide. The document is shipped with Cisco Unity Connection and is available at http://www.cisco.com/en/US/products/ps6509/products_documentation_roadmaps_list.html.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.