Guest

Cisco Unity

Release Notes for Cisco Unity Voice Connector for Exchange Release 10.0(1)

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

Release Notes for Cisco Unity Voice Connector Release 10.0(1) for Microsoft Exchange

Contents

Compatibility with Networking Options and Cisco Unity Versions

System Requirements

Voice Connector for Exchange 2000: Requirements

Hard Disk Space Requirements

Voice Connector for Exchange 5.5: Requirements

Downloading the Voice Connector

Installing the Voice Connector

Installing the Voice Connector for Exchange 2000

Installing the Voice Connector for Exchange 5.5

Uninstalling the Voice Connector

Determining the Voice Connector Version in Use

Uninstall Procedures

New and Changed Functionality

New and Changed Functionality—Release 10.0(1)

Enhanced Logging Capabilities

Hot Fix Changes

VPIM Support

SMTP Networking Changes

Caveats

Open Caveats—Release 10.0(1)

Resolved Caveats—Voice Connector 10.0(1)

Cisco Unity Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


Release Notes for Cisco Unity Voice Connector Release 10.0(1) for Microsoft Exchange

Revised February 6, 2003

These release notes contain compatibility information, system requirements, installation instructions, new and changed functionality, and open and resolved caveats for Cisco Unity™ Voice Connector Release 10.0(1) for Microsoft Exchange.

The Voice Connector is a Cisco Unity (with Microsoft Exchange) networking component that enables messaging between:

•Cisco Unity servers that access separate directories (SMTP Networking).

•Cisco Unity servers and other voice messaging systems by way of AMIS, VPIM, or the Cisco Unity Bridge.

Voice Connector version 10.0(1) is available on the Cisco Unity 4.0 DVD and CD 1, and is available for download on the Cisco Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Contents

•Compatibility with Networking Options and Cisco Unity Versions

•System Requirements

•Downloading the Voice Connector

•Installing the Voice Connector

•Uninstalling the Voice Connector

•New and Changed Functionality

•SMTP Networking Changes

•Caveats

•Cisco Unity Documentation

•Obtaining Documentation

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

Compatibility with Networking Options and Cisco Unity Versions

Voice Connector 10.0(1) is supported for use in the following combinations of networking options and Cisco Unity versions.

Table 1 Supported Networking Options and Cisco Unity Versions

Networking Option
Cisco Unity Version

VPIM

4.0(1) and later

SMTP

3.1(5) and later

Bridge (all versions)

3.1(3) and later

AMIS

3.1(2) and later


If you are using Voice Connector 10.0(1) with Cisco Unity 3.1(5) for SMTP Networking, see the "SMTP Networking Changes" section. Refer also to the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0, which is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guide_books_list.html.

System Requirements

See the applicable section, depending on the Exchange version:

•Voice Connector for Exchange 2000: Requirements

•Voice Connector for Exchange 5.5: Requirements

Voice Connector for Exchange 2000: Requirements

Install the Voice Connector on an Exchange 2000 server. If the Exchange 2000 and Cisco Unity servers are in different routing groups, a routing group connector must be installed. Although the Voice Connector can be installed on the Cisco Unity server (if Exchange 2000 is also on the server), this is not recommended for performance reasons.

Do not install the Voice Connector on a server in an Exchange cluster. Microsoft does not support third-party connectors on an Exchange cluster server.

In order to view Voice Connector properties in Exchange System Manager, Microsoft Windows Script Host version 5.6 or later must be installed on the Exchange server on which the Voice Connector is installed. Note that if the Exchange server uses an earlier version of Windows Script Host, the Voice Connector functions properly, but you will not be able to view Voice Connector properties in Exchange System Manager.

Hard Disk Space Requirements

The Exchange 2000 private store consumes more hard disk space after the Voice Connector is installed. Administrators should plan to have sufficient space available on the Exchange 2000 server that will host the Voice Connector for Exchange 2000. Lack of disk space introduces a risk of experiencing severe problems on the Exchange server.

The required space is directly related to the amount of traffic processed by the Voice Connector per 24 hours, and the file size of the messages. Table 2 provides storage requirements for the Exchange server to handle the increase in size of the Priv1.edb and Priv1.stm files. These requirements are in addition to the current storage requirements on the server to handle activity not related to the Voice Connector.

Table 2 Additional Storage Space Needed for Voice Message Processing

Messages Processed
Per 24 Hours
Average Message Size
Additional Storage Required

20,000

1 min - G.711 (~640 KB)

18 GB

10,000

1 min - G.711 (~640 KB)

9 GB

5,000

1 min - G.711 (~640 KB)

5 GB

20,000

1 min - G.729a (~80 KB)

4 GB

10,000

1 min - G.729a (~80 KB)

2 GB

5,000

1 min - G.729a (~80 KB)

1 GB


Voice Connector for Exchange 5.5: Requirements

Install the Voice Connector on an Exchange 5.5 server that is in the same Exchange site as Cisco Unity. Although the Voice Connector can be installed on the Cisco Unity server (if Exchange 5.5 is also on the server), this is not recommended for performance reasons. Following are additional requirements:

•For SMTP networking, the Voice Connector must be installed on the same Exchange server as the Exchange Internet Mail Service.

•Install only one instance of the Voice Connector in the Exchange site.

•If the Exchange server on which the Voice Connector will be installed is running Windows NT 4.0, the Microsoft Active Directory Services Client Extension (DSClient) for Windows NT 4.0 must be installed on the server prior to installing the Voice Connector. The DSClient requires Windows NT 4.0 Service Pack 6a. For information on downloading and installing the DSClient from the Microsoft website, refer to the following Microsoft Knowledge Base articles:

–Q288358—HOW TO: Install the Active Directory Client Extension

–Q295166—INFO: Advanced Installation of Directory Services Client for Windows NT 4.0

–Q295168—INFO: Files Installed by Directory Services Client Extension for Windows NT 4.0

–Q289105—INFO: Support for ADSI on Windows NT 4.0

–Q216290—INFO: Determining Which Version of ADSI Is Installed

Downloading the Voice Connector

To download the Voice Connector

Step 1 Uninstall any previous versions of the Voice Connector. See the "Uninstalling the Voice Connector" section.

Step 2 On a computer with a high-speed Internet connection, go to the Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml, and click Cisco Unity Voice Connector under "Cisco Unity Software."

Step 3 Download the applicable file to the directory of your choice, depending on the Exchange version:

Exchange 2000

CiscoUnityVoiceConnector10.0.1-Ex2000.exe

Exchange 5.5

CiscoUnityVoiceConnector10.0.1-Ex55.exe


Step 4 Unzip the downloaded file and extract the files to the directory of your choice. The extracted files must be accessible from the Exchange server on which the Voice Connector will be installed. (The Voice Connector setup program creates several folders within the folder in which the Exchange server software is installed and copies files to these folders.)

Step 5 Delete the downloaded zip file to free hard disk space.

Installing the Voice Connector

See the applicable section, depending on the Exchange version:

•Installing the Voice Connector for Exchange 2000

•Installing the Voice Connector for Exchange 5.5

Installing the Voice Connector for Exchange 2000

Do the following two procedures in the order listed.

To install the Voice Connector for Exchange 2000

Step 6 Log on to the Exchange server on which you are installing the Voice Connector.

Step 7 As a best practice, back up the Exchange server before installing the Voice Connector.

Step 8 Disable any virus-scanning services on the Exchange server.

Step 9 Uninstall any previous versions of the Voice Connector. See the "Uninstalling the Voice Connector" section.

Step 10 If you are installing the Voice Connector from the Cisco Unity 4.0 DVD or CD1, insert the disc in the computer, and browse to the VoiceConnector-Ex2000 directory.

If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.

Step 11 Double-click Install.exe, and click Next.

Step 12 In the Address Types dialog box, check the address types of the messages that the Voice Connector will be handling:

Voice
If you are using SMTP Networking.
AMIS

If you are using AMIS Networking.

Bridge

If you are using Bridge Networking.

VPIM

If you are using VPIM Networking.


Step 13 Click Next.

Step 14 If you did not check the VPIM check box in the Address Types dialog box, skip to Step 15.

If you checked the VPIM check box, enter settings in the VPIM Transport Sink dialog box, if applicable:

a. Optionally, check the Install SMTP Transport Event Sink check box. If you are installing the Voice Connector on multiple Exchange servers, in most cases you install the Transport Event Sink only once. The Exchange server on which the Transport Event Sink is installed should be the Exchange server that will receive incoming VPIM messages. Only one instance of the Transport Event Sink is necessary when all VPIM messages will be routed through a single Exchange server. When incoming VPIM messages will be routed through multiple Exchange servers, the Voice Connector and Transport Event Sink should be installed on each of the servers.

b. If you checked the Install SMTP Transport Event Sink check box, enter the domain name used in your e-mail addresses/recipient policy in the SMTP Domain box. The domain does not have to be the same domain as that of the server on which the SMTP Transport Event Sink is being installed. Typically, the domain entered in the SMTP Domain box is the same as the domain that will be entered on the Primary Location page.

c. Click Next.

Step 15 On the Confirm Directory dialog box, click Next to launch the setup.

Step 16 When the setup is complete, click Finish to exit Setup and restart the server.

To view Voice Connector properties in Exchange System Manager, Windows Script Host version 5.6 or later must be installed on the Exchange server. (Note that if the Exchange server uses an earlier version of Windows Script Host, the Voice Connector functions properly, but you will not be able to view Voice Connector properties in Exchange System Manager.)

To determine whether to update Windows 2000 Script Host

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 Browse to the directory Winnt\System32.

Step 3 Right-click the file Wshom.ocx, and click Properties.

Step 4 Click the Version tab.

Step 5 In the Item Name list, click Product Version to view the version in the Value box.

If the version is earlier than 5.6, update Windows Script Host so the Voice Connector properties can be displayed in Exchange System Manager. (Go to the downloads page of the Microsoft website, and do a keyword search for Windows Script Host. Follow the installation instructions.)

Installing the Voice Connector for Exchange 5.5

To install the Voice Connector for Exchange 5.5

Step 1 Log on to the Exchange server on which you are installing the Voice Connector.

Step 2 As a best practice, back up the Exchange server before installing the Voice Connector.

Step 3 Disable any virus-scanning services on the Exchange server.

Step 4 Uninstall any previous versions of the Voice Connector. See the "Uninstalling the Voice Connector" section.

Step 5 If you are installing the Voice Connector from the Cisco Unity 4.0 DVD or CD 1, insert the disc in the computer, and browse to the VoiceConnector-Ex55 directory.

If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.

Step 6 Double-click Setup.exe, and click Next.

Step 7 Enter the port number that Exchange uses for LDAP, and click Next.

To find the port number, open the Exchange Administrator, and under the Cisco Unity server container, browse to Configuration\Protocols\LDAP.

Step 8 In the Address Types dialog box, check the address types of the messages that the Voice Connector will be handling:

Voice
If you are using SMTP Networking.
AMIS

If you are using AMIS Networking.


Step 9 Click Next twice.

Step 10 In the User Information dialog box, enter your Windows password and click Next.

Step 11 When the setup is complete, click Finish. The Voice Connector service starts automatically.

Step 12 Enable virus-scanning services on the server.

Uninstalling the Voice Connector

The uninstall procedure that you use depends on the Cisco Unity Voice Connector version in use, and whether the Voice Connector is installed on an Exchange 2000 server or on an Exchange 5.5 server. As of Cisco Unity 4.0(1), the Voice Connector itself was assigned a version separate from the Cisco Unity version. Voice Connector version 10.0(1) is included with Cisco Unity 4.0(1).

To determine the version of an installed Voice Connector, see the "Determining the Voice Connector Version in Use" section.

In the "Uninstall Procedures" section, do the procedure that is applicable to your installation, depending on the versions of Exchange, Cisco Unity, and the Voice Connector.

Determining the Voice Connector Version in Use

This section contains two procedures. Do the procedure for your version of Cisco Unity.

To determine the Voice Connector version in use: Cisco Unity 4.0 and later, Voice Connector 10.0 and later

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Windows Explorer or My Computer, browse to the appropriate folder:

•Exchange 2000:<ExchangeServerPath>\VoiceGateway\bin

•Exchange 5.5:<ExchangeServerPath>\connect\voice\bin

Step 3 Right-click GwIvc.exe, and select Properties.

Step 4 Click the Version tab in the Properties window.

Step 5 Click Product Version in the Item Name box to view the product version in the Value box.

To determine the Voice Connector version in use: Cisco Unity 3.0 through 3.1

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Windows Explorer or My Computer, browse to the appropriate folder:

•Exchange 2000:
<ExchangeServerPath>\VoiceGateway\bin\LocalizedFiles\ENU.

•Exchange 5.5:<ExchangeServerPath>\voice\bin\LocalizedFiles\ENU.

Step 3 Right-click SetupRes.dll, and select Properties.

Step 4 Click the Version tab in the Properties window to view the File Version.

Uninstall Procedures

This section contains four procedures. Do the procedure that applies to your installation.

•To uninstall the Voice Connector for Exchange 2000: Cisco Unity 3.1 and later, Voice Connector 10.0 and later

•To uninstall the Voice Connector for Exchange 2000: Cisco Unity 3.0

•To uninstall the Voice Connector for Exchange 5.5: Cisco Unity 3.1(2) and later, Voice Connector 10.0 and later

•To uninstall the Voice Connector for Exchange 5.5: Cisco Unity 3.1(1), 3.0(x), or 2.4(6.x)

To uninstall the Voice Connector for Exchange 2000: Cisco Unity 3.1 and later, Voice Connector 10.0 and later

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In the Windows Control Panel, in Add/Remove Programs, click Exchange 2000 Voice Connector.

Step 3 Follow the on-screen prompts to uninstall the Voice Connector.

Step 4 On the Windows Start menu, click Programs > Microsoft Exchange > System Manager.

Step 5 Expand Servers\<Server name>\<Storage group>\Mailbox Store\Mailboxes for the server on which the Voice Connector was installed.

The mailbox for the Voice Connector is named "AvExchangeIVC_<servername>" or "Exchange 2000 Voice Connector (<servername>)."

Step 6 Right-click Mailboxes in the left pane and select Run Cleanup Agent.

Step 7 After the Cleanup Agent has run, right-click each Voice Connector mailbox marked with the red 'X' icon and select Purge. Click Yes in the warning dialog box.

Step 8 Close the Exchange System Manager.

To uninstall the Voice Connector for Exchange 2000: Cisco Unity 3.0

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 Verify that the Windows Services program is closed.

Step 3 On the Windows Start menu, click Programs > Microsoft Exchange > System Manager.

Step 4 Expand Connectors.

Step 5 Right-click the Voice Connector, and click Stop.

Step 6 After the service stops, right-click the Voice Connector, and click Delete.

Step 7 Expand Servers\<Server name>\<Storage group>\Mailbox Store\Mailboxes for the server on which the Voice Connector was installed.

The mailboxes are listed in the right pane. The mailbox name for the Voice Connector is AvExchangeIVC.

Step 8 Right-click Mailboxes in the left pane, and select Run Cleanup Agent.

Step 9 After the Cleanup Agent has run, right-click the Voice Connector mailbox marked with the red 'X' icon, and select Purge. Click Yes in the warning dialog box.

Step 10 Close the Exchange System Manager.

To uninstall the Voice Connector for Exchange 5.5: Cisco Unity 3.1(2) and later, Voice Connector 10.0 and later

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In the Windows Control Panel, in Add/Remove Programs, select the Voice Connector.

Step 3 Follow the on-screen prompts to uninstall the Voice Connector.

To uninstall the Voice Connector for Exchange 5.5: Cisco Unity 3.1(1), 3.0(x), or 2.4(6.x)

Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In the CD-ROM drive, insert Cisco Unity Disc 1 for the version of the Voice Connector that is installed, and browse to the VoiceGateway folder.

Step 3 Double-click Setup.exe, and click Next.

The Setup program detects that the Voice Connector is already installed, so the Uninstall dialog box appears.

Step 4 Click Next, and click Yes in the warning dialog box.

Step 5 When the uninstall is complete, click Finish to exit the program and restart the server.

New and Changed Functionality

New and Changed Functionality—Release 10.0(1)

Enhanced Logging Capabilities

Voice Connector 10.0(1) includes enhanced logging capabilities. For more information, refer to the "Logs and Traces" chapter of the Cisco Unity Troubleshooting Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.

Hot Fix Changes

The changes made to the Unity3.1.4_and_3.1.5_VoiceConnectorHotfix—which fixed problems with SMTP Networking—are included in Voice Connector 10.0(1). For more information, see the "SMTP Networking Changes" section.

VPIM Support

Voice Connector 10.0(1) enables Cisco Unity with Exchange to support Voice Profile for Internet Mail (VPIM) version 2. (VPIM requires Cisco Unity 4.0(1) or later.) VPIM allows the exchange of voice, fax, and text messages between Cisco Unity and other VPIM-compliant voice messaging systems. For more information, refer to the "VPIM Networking" chapter of the Networking in Cisco Unity Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guide_books_list.html.

SMTP Networking Changes

The implementation of SMTP Networking changed in Cisco Unity 3.1(5) and later. Voice Connector 10.0(1) is designed to work with the new implementation of SMTP Networking in Cisco Unity. Because of the changes, Voice Connector 10.0(1) is required for SMTP Networking in Cisco Unity 3.1(5) and later.

As of Cisco Unity3.1(5), extension addresses are not automatically generated for Cisco Unity subscribers. (Extension addresses for SMTP Networking have the format VOICE:<Delivery Location Dial ID>_<Extension>.) Instead of assigning an extension address to each Cisco Unity subscriber, Voice Connector 10.0(1) parses the address and looks for a matching primary location and a matching subscriber extension at that location to obtain the e-mail address for the recipient.

If you are using Voice Connector 10.0(1) with Cisco Unity 3.1(5) for SMTP Networking, refer to the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0, which is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guide_books_list.html.

Note that caveat CSCdz34890—a Cisco Unity caveat, not a Voice Connector caveat—is related to SMTP Networking:

Description—Using SMTP Networking, when a subscriber at site A sends a message to a subscriber at site B, when the subscriber at site B listens to the message, the conversation does not offer the option to press 4 to reply to the message. However, by pressing 4, the subscriber can reply to the message (even though the option is not offered).

Conditions—This happens any time a subscriber sends a message from site A to site B by using SMTP Networking, and site B does not have an Internet Subscriber configured for the sending subscriber in site A. This defect is reproducible in Cisco Unity 4.0(1), and in Cisco Unity 3.1(4) and 3.1(5).

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 more information on the caveats in this section, in addition to 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.

Open Caveats—Release 10.0(1)

Table 3 Cisco Unity Voice Connector Release 10.0(1) Open Caveats 

Caveat Number
Description

CSCdw92235

The Exchange 2000 private store consumes more hard disk drive storage space after the Voice Connector is installed. This behavior occurs on Exchange 2000 servers on which the Voice Connector for Exchange 2000 is installed and large amounts of VPIM, Bridge or AMIS voice messages are being processed.

Workaround

The size of the Exchange Priv1.edb and Priv1.stm storage files on the Exchange 2000 server where the Voice Connector is installed may appear to be infinitely increasing at first, but the size of these files will eventually plateau at a size relative to the heaviest 24-hour period of processing. Nightly Exchange 2000 online defragmentation and cleanup will create available space within the file for processing, but the size of either of these files will never automatically decrease even if traffic lessens.

To decrease the size of these files, offline defragmentation must be performed. Note that this may result in only a temporary reduction in the size of these files if Voice Connector traffic remains heavy.

See the "Hard Disk Space Requirements" section for more information.

CSCdx53729

The Voice Connector for Exchange 2000 is not visible or accessible in the Connectors section of the Exchange System Manager on other Exchange 2000 servers in the organization. This problem happens when attempting to view the Voice Connector properties from the Exchange System Manager on another Exchange 2000 server in the organization in which the Voice Connector has never been installed and Cisco Unity is not installed.

Workaround

To view and access Voice Connector properties

1. Log on to the Exchange server on which the Voice Connector is installed.

2. On the Windows Start menu, click Programs > Microsoft Exchange > Exchange System Manager.

3. Expand the Connectors container in the left-hand pane.

4. Right-click Exchange 2000 Voice Connector (<server name>), and click Properties.

To see where the Voice Connectors are installed

1. From any Exchange 2000 server in the organization, open the Exchange 2000 System Manager.

2. In the left pane, expand Tools.

3. Expand Monitoring and Status.

4. Click Status.

All instances of the Voice Connectors installed on any Exchange 2000 server in the organization will display in the right pane.

CSCdx84958

When a VPIM message is sent to a Cisco Unity subscriber whose Exchange mailbox is over the size limit to receive messages, the message is not delivered and no NDR is generated. An error is displayed in the Voice Connector log file: "Error Delivering VPIM message (Got NDR)->Unhandled Case." The default location for the log files is on the Exchange server on which the Voice Connector is installed, in one of the following folders, depending on the Exchange version:

•Exchange 2000: <Exchange Server Path>\VoiceGateway\LogFiles

•Exchange 5.5: <Exchange Server Path>\IvcData\LogFiles

Workaround

There is no known workaround.

CSCdx86386

When a remote system rejects a VPIM message that Cisco Unity is attempting to deliver during the initial SMTP session, the resulting NDR is not delivered to the sending Cisco Unity subscriber. However, the NDR can be viewed in the Exchange badmail directory at Exchsrvr\Mailroot\Vsi #\BadMail.

Workaround

There is no known workaround.

CSCdy49912

The Voice Connector for Exchange 2000 does not function properly after the Exchange 2000 server on which it is installed is moved to a different routing group.

Workaround

Uninstall the Voice Connector first, then move the Exchange 2000 server to the new routing group, and reinstall the Voice Connector.

Additional Information

Using Exchange System Manager, Exchange 2000 servers can be moved between routing groups. When a server with the Voice Connector installed is moved, an error warns: "The server is unwilling to process the request. Facility: LDAP Provider, ID no: 80072035, Exchange System Manager." The server is moved to the new routing group anyway, and there is no indication of a problem. However, the Voice Connector is still in the original routing group. The Voice Connector shows no errors, but will not process or queue messages. Messages sent that require the Voice Connector are returned as undeliverable.

CSCdz20416

The symptoms of this defect vary depending on whether a Unity Phone Prefix is defined for the VPIM delivery location:

•Defined: Incoming VPIM messages are returned undeliverable because no matching subscriber was found for the extension. This happens even though a Cisco Unity subscriber with the extension is, in fact, defined on the system.

•Not defined: Incoming VPIM messages arrive from an SMTP location instead of the expected VPIM location. These voice messages will also be encoded with the G.726 codec, and so may not be playable over the phone or with ViewMail for Microsoft Outlook.

This problem occurs only when there is both an SMTP delivery location and a VPIM delivery location defined with the same SMTP domain name, and applies only to incoming VPIM messages that are from the VPIM delivery location with that same SMTP domain name.

Workaround

The order in which the Voice Connector checks for a matching delivery location is the order in which they were added. Since it accepts the first match with the correct prefix or with no prefix, deleting the SMTP location with the matching SMTP domain name and then reading it should force the VPIM delivery location to be found first and be used for incoming VPIM messages from that location/domain.


Resolved Caveats—Voice Connector 10.0(1)

Table 4 Cisco Unity Voice Connector Release 10.0(1) Resolved Caveats 

Caveat Number
Description

CSCdw89000

The Voice Connector for Exchange 2000 private byte memory (or virtual memory) usage increases over time proportionate to the total number of messages processed.

CSCdy36967

SMTP networking between Cisco Unity servers in different directories fails for a variety of reasons, depending on the version of Cisco Unity. The failure means that subscribers on one Cisco Unity server cannot exchange voice messages with subscribers on another Cisco Unity server that accesses a different directory.

To resolve problems related to SMTP Networking, changes were made to both Cisco Unity and the Voice Connector. The Cisco Unity changes to support SMTP Networking are in Cisco Unity 3.1(5) and later and in Voice Connector 10.0(1) and later.

CSCdu81233

Voice messages addressed to a subscriber in a different directory (using SMTP Networking) have the "From" address is in the wrong format.

CSCdv67880

Voice Connector install fails—MSVCP60.dll could not be found.

CSCdw06018

Error given if Messages to Process check box is altered in Voice Connector properties.

CSCdw16321

To send a message using ViewMail for Outlook to a subscriber in another directory (using SMTP Networking), the sender of the message must have an extension e-mail address of type VOICE.

CSCdw20515

If a blind addressed message is received through the Voice Connector for Exchange 2000, and the intended recipient name can not be resolved, a Non-Delivery Receipt is not returned to the original sender of the message.

CSCdw32294

The log file for the Voice Connector (Exchange 5.5 version only) has no date or time reference for data logged.

CSCdx85677

The Voice Connector appears to install successfully, but does not show up in the Services Control Panel or in the Exchange System Administrator.

CSCdy41481

Voice messages addressed to subscribers in a different directory (using SMTP Networking) are never successfully sent to the recipients. This problem happens when the messages are being sent through ViewMail, and the message does not have any voice recordings attached.


Cisco Unity Documentation

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

Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

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

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco web sites can be accessed from this 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 may have 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.

Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

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

http://www.cisco.com/en/US/partner/ordering/index.shtml

•Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) 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 Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

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

You can submit your comments by mail by writing to the following address:

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

We appreciate your comments.

Obtaining Technical Assistance

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

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

•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

To obtain customized information and service, you can self-register on Cisco.com at this 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 levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

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

Cisco TAC Website

You can use the Cisco TAC website 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 website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require 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 this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/en/US/support/index.html

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this 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). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html

•iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:

http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

•Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html

Release Notes for Cisco Unity Voice Connector Release 10.0(1) for Microsoft Exchange
Copyright © 2003 Cisco Systems, Inc. All rights reserved.