Guest

Cisco Personal Assistant

Release Notes for Cisco Personal Assistant Release 1.4(4)

  • Viewing Options

  • PDF (332.7 KB)
  • Feedback
Release Notes for Cisco Personal Assistant Release 1.4(4)

Table Of Contents

Release Notes for Cisco Personal Assistant Release 1.4(4)

Contents

System Requirements and Supported Software

Hardware Requirements

Software Requirements

Requirements for Integrating Cisco Unity with Personal Assistant

Supported Optional Software

Determining the Personal Assistant Version

Upgrading to Personal Assistant 1.4(4) from Version 1.4(x)

Upgrading to Personal Assistant 1.4(4) from Version 1.3(x)

New and Changed Requirements and Support—Release 1.4(4)

Cisco Security Agent for Cisco Personal Assistant, Version 1.1(2)

Cisco Unity Version 4.0(4) with Exchange

New and Changed Functionality—Release 1.4(4)

Installation and Upgrade Notes

Updating JTAPI Files When Cisco CallManager Is Upgraded After Personal Assistant 1.4(x) Is Installed

Upgrading the IP Telephony Operating System

Limitations and Restrictions

Cisco Unity Phone Password Cannot Be Reset in Personal Assistant

Effect on Access to User Interface When Cisco CallManager Is Unavailable

Encoding for Cisco Unity Recorded Names and Voice Messages

Extension Not Always Displayed for Calls Through a Gateway

Outlook 2002 Service Pack 2 Problems with Address Book Synchronization

Personal Assistant Cannot Be Uninstalled

Personal Assistant Configuration on the Network

Personal Assistant with Cisco CallManager 3.2(3)

Rule Processing for Systems with Other JTAPI Applications

Text to Speech

Voice-Message Labeling When Calling from Another User Phone

Voice Messages Cannot Be Forwarded to Multiple Users Without Using a Caller Group

Caveats

Open Caveats—Release 1.4(4)

Resolved Caveats—Release 1.4(4)

Documentation Updates

Errors

Conferencing and Addressing Voice Messages to Caller Groups: Cisco Personal Assistant User Guide

Directory Search Filters for Active Directory: Cisco Personal Assistant Installation and Administration Guide

Setting the Voice-Mail Access Number: Cisco Personal Assistant User Guide

Skipping Choices in Disambiguation: Cisco Personal Assistant User Guide

Omissions

Configuring Error Handling—Cisco CallManager Version 4.0 or Later: Cisco Personal Assistant Installation and Administration Guide

Dialing by Name and Department or Location: Cisco Personal Assistant User Guide

Troubleshooting Information

Cisco Personal Assistant Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco Personal Assistant Release 1.4(4)


Revised August 2, 2004

These release notes contain requirements, upgrade instructions, new and changed support, new and changed functionality, limitations and restrictions, open and resolved caveats, and documentation updates for Cisco Personal Assistant Release 1.4(4).

The latest software upgrades for Personal Assistant are available on the Cisco Personal Assistant Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/assist.


Note Items in release notes—excluding caveats—may be revised to correct or to clarify information after the initial publication date (the date the software was released). When an item has been changed, the phrase "Revised <date>" is included in the text of the item.


 

Contents

This document contains the following sections:

System Requirements and Supported Software

Determining the Personal Assistant Version

Upgrading to Personal Assistant 1.4(4) from Version 1.4(x)

Upgrading to Personal Assistant 1.4(4) from Version 1.3(x)

New and Changed Requirements and Support—Release 1.4(4)

New and Changed Functionality—Release 1.4(4)

Installation and Upgrade Notes

Limitations and Restrictions

Caveats

Documentation Updates

Troubleshooting Information

Cisco Personal Assistant Documentation

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

System Requirements and Supported Software

Hardware Requirements

A server that meets Personal Assistant specifications. Refer to the Current Supported Platforms for Cisco Personal Assistant 1.4 list at http://cisco.com/en/US/products/sw/voicesw/ps2026/products_data_sheets_list.html.


Caution Cisco TAC does not provide any assistance for installing, customizing, or troubleshooting Personal Assistant on a platform that is not on the Current Supported Platforms for Cisco Personal Assistant 1.4 list.

Software Requirements

Cisco CallManager on a separate server. Versions 4.0(x), 3.3(x), and 3.2(x) are supported.

LDAP-enabled directory services such as the Cisco CallManager integrated DC directory, Microsoft Active Directory, or Netscape Directory Services for storing corporate and personal directory information (names, phone numbers, e-mail addresses, etc.).

A web browser. Internet Explorer 6.0 and Netscape Navigator 7.0 are supported.

If you are integrating Personal Assistant with a messaging system, one of the following systems on a separate server:

Cisco Unity. Versions 4.0(x) and 3.1(x) with Exchange 2003, Exchange 2000, or Exchange 5.5 are supported.

Avaya Octel messaging.

Note that for voice-mail browsing in Personal Assistant, Cisco Unity with Exchange is required. Users cannot browse voice mail on other messaging systems in Personal Assistant.

If you are supporting e-mail paging, an SMTP-compliant e-mail paging server.

If you are sending Personal Assistant error messages to Syslog for collection and analysis, a CiscoWorks 2000 server in your network. CiscoWorks 2000 RME 3.3 is supported.

To view Personal Assistant documentation in PDF format, Adobe Acrobat Reader. Versions 5.0 and later are supported.

Requirements for Integrating Cisco Unity with Personal Assistant

The values for the fields that you choose in the Unique Attribute for Corporate Directory and Unique Attribute for Message Store fields must be identical for each user. (For example, if you select the fields cn for the corporate directory and sAMAccountName for the Exchange message store, the values in the two fields must match for each user.)

For information about setting the fields, refer to the "Messaging Configuration" section in the "Personal Assistant Administration Page Reference" appendix of the Cisco Personal Assistant Installation and Administration Guide, Release 1.4 at http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/assist14/ag/ag141/index.htm.

Cisco Unity messages and recorded names must be encoded in G.711 Mu-Law format.

Supported Optional Software

The following optional software has been qualified by Cisco for use with Personal Assistant:

Cisco Security Agent for Cisco Personal Assistant versions 1.1(x) and 1.0(1).

Note that supported software on a Personal Assistant server running Cisco Security Agent for Cisco Personal Assistant is more limited than the software supported on a server that is not running Cisco Security Agent for Cisco Personal Assistant. Refer to the "Supported Optional Software" section of Release Notes for Cisco Security Agent for Cisco Personal Assistant at http://www.cisco.com/en/US/products/sw/voicesw/ps2026/prod_release_notes_list.html.

McAfee NetShield version 7.0.

Determining the Personal Assistant Version

To Determine the Personal Assistant Version in Use


Step 1 In the Personal Assistant administration interface, go to the Help > About Cisco Personal Assistant page.

Step 2 Click Details. The Personal Assistant version is displayed in the message.


Upgrading to Personal Assistant 1.4(4) from Version 1.4(x)

Revised August 2, 2004

Personal Assistant version 1.4(4) is available only as a patch release that you download from the Personal Assistant Software Download page. The patch file must be installed on each Personal Assistant server.

We recommend that before you upgrade Personal Assistant, you upgrade the IP telephony operating system to the latest version. New versions can include security patches, cumulative security patches, engineering specials, BIOS and driver updates, and other customizations specific to Cisco platforms and applications.

Cisco IP telephony operating system releases and information are available at http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des.

Do the eight procedures in this section as applicable and in the order listed to upgrade Personal Assistant on a system that is currently running Personal Assistant 1.4(x).

Note that Personal Assistant will be out of service while the system is upgraded. Plan to upgrade the software on a day and time when the suspension of Personal Assistant will have the least impact.

If virus-scanning software is installed on the Personal Assistant server, disable the virus-scanning services so that they do not interfere with the upgrade program. Otherwise, skip to the next procedure, "To Disable the Cisco Security Agent Service (If Applicable)."

To Disable Virus-Scanning Services (If Applicable)


Step 1 Refer to the virus-scanning software documentation to determine the names of the virus-scanning services.

Step 2 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 3 Disable each virus-scanning service:

a. In the right pane, double-click the service.

b. Click the General tab, and click Stop.

c. In the Startup Type list, click Disabled, and click OK.

Step 4 When all virus-scanning services have been disabled, close the Services MMC.


If Cisco Security Agent for Cisco Personal Assistant is installed on the Personal Assistant server, disable the Cisco Security Agent service so that it does not interfere with the upgrade program. Otherwise, skip to the next procedure, "To Upgrade Personal Assistant Software by Using the Patch File."

To Disable the Cisco Security Agent Service (If Applicable)


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 2 In the right pane, double-click Cisco Security Agent.

Step 3 Click the General tab, and click Stop.

Step 4 In the Startup Type list, click Disabled, and click OK.

Step 5 Click OK to close the Cisco Security Agent Properties dialog box.

Step 6 Close the Services MMC.


To Upgrade Personal Assistant Software by Using the Patch File


Step 1 On a computer with a high-speed Internet connection, go to the Cisco Personal Assistant Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/assist.


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


Step 2 Click the file Pa-fmu.1-4-4.exe.

Step 3 Follow the on-screen prompts to complete the download.

Step 4 On the Personal Assistant server, browse to the location where you saved the downloaded file, and double-click it.

Step 5 Follow the on-screen prompts to complete the software upgrade.


For each locale, you must configure two Personal Assistant services—PASPREC_<Locale> and PASPCS_<Locale>—to log on as an account with local administrator privileges or with domain administrator privileges for the Personal Assistant domain.

If you are using Personal Assistant clusters, do the first procedure, "To Configure Two Services to Log On with Domain Administrator Privileges (If Using Personal Assistant Clusters)."

If you are not using Personal Assistant clusters, do the second procedure, "To Configure Two Services to Log on with Local Administrator Privileges (If Not Using Personal Assistant Clusters)."

To Configure Two Services to Log On with Domain Administrator Privileges (If Using Personal Assistant Clusters)


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 2 In the right pane, double-click PASPREC_<Locale>.

Step 3 Click the Log On tab.

Step 4 Click This Account.

Step 5 Click Browse.

Step 6 In the Select User dialog box, in the Look In list, click the name of the domain to which the Personal Assistant server belongs.

Step 7 Double-click the name of the account with Personal Assistant domain administrator privileges.

Step 8 Enter and confirm the password.

Step 9 Click Apply.

Step 10 Click the General tab.

Step 11 Click Stop.

Step 12 Click Start.

Step 13 Click OK.

Step 14 In the right pane, double-click PASPCS_<Locale>.

Step 15 Repeat Step 3 through Step 13.

Step 16 Repeat Step 2 through Step 15 for each additional locale.

Step 17 When you are finished configuring the services, close the Services window.


To Configure Two Services to Log on with Local Administrator Privileges (If Not Using Personal Assistant Clusters)


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 2 In the right pane, double-click PASPREC_<Locale>.

Step 3 Click the Log On tab.

Step 4 Click Local System Account.

Step 5 Click OK.

Step 6 Click the General tab.

Step 7 Click Stop.

Step 8 Click Start.

Step 9 Click OK.

Step 10 In the right pane, double-click PASPCS_<Locale>.

Step 11 Repeat Step 3 through Step 9.

Step 12 Repeat Step 2 through Step 11 for each additional locale.

Step 13 When you are finished configuring the services, close the Services window


Do the following procedure to have Personal Assistant update speech-recognition grammars and user information from the corporate directory.

To Refresh the System


Step 1 Log on to the Personal Assistant Administration interface.

Step 2 Click System > Speech Services.

Step 3 On the Speech Services Configuration page, click Refresh Now.

Note that the refresh can take up to one hour, depending on the size of the corporate directory, the number of locales installed, and the number of directory hierarchies configured.

Step 4 After the refresh is complete, verify the refresh status by clicking Refresh Details.

If the refresh was not successful, refer to Personal Assistant troubleshooting information to fix the problem. Otherwise, Personal Assistant services may not be running.


If virus-scanning software is installed on the Personal Assistant server, re-enable the virus-scanning services after the system refresh completes successfully. Otherwise, skip to the next procedure, "To Re-enable the Cisco Security Agent Service (If Applicable)."

To Re-enable Virus-Scanning Services (If Applicable)


Step 1 Refer to the virus-scanning software documentation to determine the names of the virus-scanning services.

Step 2 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 3 Re-enable each virus-scanning service:

a. In the right pane, double-click the service.

b. On the General tab in the Startup Type list, click Automatic, and click OK.

c. In the right pane, right-click the service, and click Start.

Step 4 When all virus-scanning services have been re-enabled, close the Services MMC.


If Cisco Security Agent for Cisco Personal Assistant is installed on the Personal Assistant server, you must re-enable the Cisco Security Agent service before it can monitor the Personal Assistant server again.

To Re-enable the Cisco Security Agent Service (If Applicable)


Step 1 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 2 In the right pane, double-click Cisco Security Agent.

Step 3 On the General tab, in the Startup Type list, click Automatic.

Step 4 Click Start.

Step 5 Click OK to close the Cisco Security Agent Properties dialog box.

Step 6 Close the Services MMC.


Upgrading to Personal Assistant 1.4(4) from Version 1.3(x)

Because Personal Assistant version 1.4(4) is available only as a patch release, you must first upgrade the system to Personal Assistant version 1.4(3), 1.4(2), or 1.4(1), then follow the instructions in the "Upgrading to Personal Assistant 1.4(4) from Version 1.4(x)" section.

To upgrade to Personal Assistant 1.4(3), 1.4(2), or 1.4(1) from version 1.3(x), refer to the "Installing and Upgrading Personal Assistant" chapter of the Cisco Personal Assistant Installation and Administration Guide, Release 1.4. The guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/assist14/ag/ag141/index.htm.

(Note that to upgrade to Personal Assistant 1.4(3), 1.4(2), or 1.4(1) from version 1.2(x), you must first upgrade to version 1.3(x). Refer to the Cisco Personal Assistant 1.3 Administration Guide at http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/assist3/eng/admgd/index.htm.)

Upgrading from Personal Assistant version 1.1 is not supported.

New and Changed Requirements and Support—Release 1.4(4)

This section contains information about new and changed requirements and support in the Personal Assistant Release 1.4(4) time frame only. Refer to the release notes of the applicable version for information on new and changed requirements and support with earlier versions of Personal Assistant. Release notes for all versions of Personal Assistant are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2026/prod_release_notes_list.html.

Cisco Security Agent for Cisco Personal Assistant, Version 1.1(2)

Cisco Security Agent for Cisco Personal Assistant version 1.1(2) is qualified for use with Personal Assistant version 1.4(4).

Cisco Unity Version 4.0(4) with Exchange

Personal Assistant 1.4(4) supports Cisco Unity version 4.0(4) with Exchange 2003, Exchange 2000, or Exchange 5.5.

Personal Assistant versions earlier than 1.4(4) support Cisco Unity version 4.0(4) only with Exchange 5.5.

New and Changed Functionality—Release 1.4(4)

There is no new or changed functionality for Personal Assistant 1.4(4). See the "Resolved Caveats—Release 1.4(4)" section.

Refer to the release notes of the applicable version for information on new and changed functionality with earlier versions of Personal Assistant. Release notes for all versions of Personal Assistant are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2026/prod_release_notes_list.html.

Installation and Upgrade Notes

For detailed information on installing a new Personal Assistant 1.4(x) system, refer to the Cisco Personal Assistant Installation and Administration Guide, Release 1.4 at http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/assist14/ag/ag141/index.htm.

Updating JTAPI Files When Cisco CallManager Is Upgraded After Personal Assistant 1.4(x) Is Installed

If you upgrade to Cisco CallManager version 4.0(x), 3.3(x), or 3.2(x) after you have installed Personal Assistant 1.4(x), you must update the JTAPI files on each Personal Assistant server. Personal Assistant includes the latest JTAPI files for each supported version of Cisco CallManager.

You can run a script to install the latest JTAPI files corresponding to the version of Cisco CallManager:

Cisco CallManager 4.0(x)

Run the Pa-ccm40.bat script from the Program files\Cisco systems\Personal assistant\Lib folder.

Cisco CallManager 3.3(x)

Run the Pa-ccm33.bat script from the Program files\Cisco systems\Personal assistant\Lib folder.

Cisco CallManager 3.2(x)

Run the Pa-ccm32.bat script from the Program files\Cisco systems\Personal assistant\Lib folder.



Note Running a script stops and restarts the Personal Assistant services, so you should plan to run the script when the suspension of Personal Assistant will have the least impact.


Upgrading the IP Telephony Operating System

As a best practice, we recommend that you maintain the IP telephony operating system on the Personal Assistant server with the latest update or service release. New versions can include security patches, cumulative security patches, engineering specials, BIOS and driver updates, and other customizations specific to Cisco platforms and applications.

Cisco IP telephony operating system releases and information are available at http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des.

Limitations and Restrictions

Cisco Unity Phone Password Cannot Be Reset in Personal Assistant

The Cisco Unity phone password cannot be reset by using the Personal Assistant Administration interface. When the Personal Assistant system is configured to authenticate users by using the Cisco Unity phone password as the Personal Assistant PIN, users can change their PINs only by resetting their phone passwords in Cisco Unity.

Effect on Access to User Interface When Cisco CallManager Is Unavailable

If the system is using the Cisco CallManager directory (DC Directory) as the corporate directory, users cannot log on to the Personal Assistant user web interface when the Cisco CallManager publisher is unavailable.

Encoding for Cisco Unity Recorded Names and Voice Messages

Personal Assistant cannot load Cisco Unity recorded names unless they are encoded in CCITT Mu-Law format (G.711 Mu-Law). Similarly, Personal Assistant cannot play Cisco Unity messages unless they are encoded in G.711 Mu-Law format.

Extension Not Always Displayed for Calls Through a Gateway

When a call goes through a gateway, Personal Assistant may not display the caller extension. Depending on the Cisco CallManager or gateway settings, Personal Assistant may display the media port number instead.

Outlook 2002 Service Pack 2 Problems with Address Book Synchronization

With some versions of Microsoft Outlook 2002 Service Pack 2, Outlook can crash when users try to access an Outlook contact created by the synchronization with their address books.

The problem with Outlook 2002 Service Pack 2 is known and occurs when any application creates contacts.

To avoid the problem, install Outlook 2002 version 10.<4608 or later>.4219 SP-2.

For more information, refer to caveat CSCuk45497. (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 http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.)

Personal Assistant Cannot Be Uninstalled

Personal Assistant does not provide a program for uninstalling the software.

Personal Assistant Configuration on the Network

The following list describes limitations and restrictions on how Personal Assistant can be configured on the network:

You cannot install Personal Assistant on the same server as any other Cisco IP Telephony applications, such as Cisco CallManager, Cisco Interactive Voice Response, and Cisco Auto Attendant. The installation program will terminate if it detects any such applications already installed on the server.

You cannot install Personal Assistant on a Windows domain controller.

To integrate Personal Assistant with Cisco Unity 4.0(x) or 3.1(x) (with Exchange 2003, 2000, or 5.5), you must have those applications installed on your network on servers separate from Personal Assistant. If you are using Windows 2000 domains on your network, you must install Personal Assistant in the same domain as the Exchange server or in a domain trusted by its domain.

You cannot mix different versions of Personal Assistant components in the same cluster.

You cannot install the enhanced text-to-speech server on the Cisco CallManager server or on the Cisco Unity server.

Personal Assistant with Cisco CallManager 3.2(3)

When the system is using Cisco CallManager 3.2(3), Personal Assistant cannot access the Cisco CallManager PIN to use as the Personal Assistant PIN.

The first time users access an authenticated feature, Personal Assistant prompts them to set a PIN, even if they have already set a PIN in Cisco CallManager. Personal Assistant continues to authenticate against the PIN set in Personal Assistant. The Cisco CallManager PIN cannot be reset by using the Personal Assistant Administration interface.

In addition, Personal Assistant cannot access the Cisco CallManager locale preference. As a result, the Cisco CallManager locale is not presented to users for locale synchronization when they log on to the Personal Assistant user web interface for the first time.

Rule Processing for Systems with Other JTAPI Applications

To allow another JTAPI application (such as IPMA) to intercept and process an incoming call first when Personal Assistant and other JTAPI applications are installed on the same Cisco CallManager cluster, you must disable rule processing on calls made through the Personal Assistant route point.

Text to Speech

Personal Assistant ships with an American English text-to-speech engine. If you plan to use another locale for speech recognition and for the web-based interfaces, we recommend that you use enhanced text to speech (a licensed Personal Assistant feature).

Enhanced text to speech supports all of the locales in which Personal Assistant is available except Canadian French. (If you are making Canadian French available for speech recognition, select European French when you install enhanced text to speech.)

Voice-Message Labeling When Calling from Another User Phone

When a user makes a call through Personal Assistant from another user phone, if the call is transferred to voice mail and the user leaves a message, the message is not labeled as being from the user who called. Instead, it is labeled as being from the user to whom the phone is associated.

Voice Messages Cannot Be Forwarded to Multiple Users Without Using a Caller Group

Personal Assistant allows a user to forward a Cisco Unity voice message to either a single user or to a caller group.

Caveats

This section describes 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 http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

Note that this section contains caveat information for Personal Assistant Release 1.4(4) only. Refer to the release notes of the applicable version for caveat information for earlier versions of Personal Assistant. Release notes for all versions of Personal Assistant are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2026/prod_release_notes_list.html.

Open Caveats—Release 1.4(4)

Table 1 Cisco Personal Assistant Release 1.4(4) Open Caveats 

Caveat Number
Severity
Component
Description

CSCed55308

2

app-serviceability

No Cisco CallManager equivalent CTI New Call Accept Timer in Personal Assistant.

Workaround

Do the following steps to increase the CTI New Call Accept Timer value on the Personal Assistant server:

1. Copy the jtapi.ini file from the applicable directory under %paroot% to the directory %paroot%\lib.

2. Change the RouteSelectTimeout value (the default is 5000 ms) in the jtapi.ini file to match the CTI New Call Accept Timer value set in Cisco CallManager.

3. Restart the Personal Assistant server and Personal Assistant webadmin services.

CSCdz06857

3

dialbyname

After upgrading Personal Assistant, Cisco Unity recorded names cannot be loaded for use as Personal Assistant spoken names.

This is seen when upgrading to Personal Assistant version 1.3(3) and later. It happens because Personal Assistant looks for the names in the wrong location.

Workaround

Provide Personal Assistant with the correct location where Cisco Unity is installed by setting the value PROMPTS_DIR = \C$\Commserver\Stream Files in the PAROOT/Etc/VMBootstrap3.properties file.

CSCea54794

3

dialbyname

Administrators cannot access subsequent pages after logging on to the Personal Assistant Administration interface by using http://<Server name>/pasystemadmin.

Workaround

Log on to the interface by using either of the following URLs, as applicable:

http://<Server IP address>/pasystemadmin

http://localhost/pasystemadmin.

CSCea92089

3

systemadmin

Dialing by name and department fails. For example, when a user says "Department," or enters touch tone(s) 4 or 4# for the dial by name and department option, the call is dropped.

This happens when the system administrator has created the department, but a Personal Assistant system refresh has not yet been successfully completed.

Workaround

Go to the System > Speech Services Configuration page, and click Refresh Now to manually refresh the system.

CSCeb55027

3

other

The Personal Assistant server suddenly restarts. An error message like this appears in the system event log: "Transmit No Buffers."

This problem was observed on a Personal Assistant 1.3(4.1) system running on a 7835-1000 and integrated with Cisco CallManager version 3.2(2c)ES77.2.

There is no workaround.

CSCeb69998

3

pauseradmin

The error message, "Please enter a Call Pickup Timeout of no more than 60 seconds" appears when a user attempts to save the configuration on the Preferences -> Settings page.

The default call pickup timeout value for the user is limited to 60 seconds or less. If the Call Pickup Timeout field on the Settings page is blank, Personal Assistant uses the timeout value set by the administrator. Therefore, if the user does not fill in a timeout value, and if the administrator set a timeout value greater than 60 seconds, the error message displays when the user tries to save the information on the page.

Workaround

On the Settings page, enter a user call pickup timeout value of no more than 60 seconds.

CSCec45657

3

other

After Personal Assistant is newly installed or upgraded, some Personal Assistant services do not start and the following error message appears when attempting to log on to the Personal Assistant Administration interface:

Initialization Error - There was an error initializing the System Administration server: javax.servlet.ServletException: com.cisco.pa.util.PAAdminException: LDAPURL: no such key. Please restart PAWebAdmin service.

The problem might occur with Personal Assistant 1.4(1) and earlier installs or upgrades.

Workaround

1. Make a backup copy of the file Program Files\Cisco Systems\Personal Assistant\etc\PABootStrap.properties.

2. Open the file in a text editor.

3. Under the heading Internal Directory Server URL, replace DS=Default with LDAPURL=ldap://x.x.x.x:8404 where x.x.x.x is the IP address of the Cisco CallManager publisher with the DCD directory database. Do not add spaces or returns to the file.

4. Save the file.

5. Restart the Personal Assistant server.

CSCed45076

3

rulesadmin

Personal Assistant incorrectly reports that rule set activation and de-activation by phone is successful.

This happens when Personal Assistant is running with a Cisco CallManager cluster integration and the Cisco CallManager publisher is unavailable.

Workaround

Restore the Cisco CallManager publisher to the operating state.

CSCed48543

3

other

Refreshes fail with compilation failures, prompt response times increase, and previously un-generated or recorded names are not generated.

This occurs when a Personal Assistant cluster is configured with an idle failover server, and the primary Personal Assistant server suffers a catastrophic failure such as a loss of power or a loss of network connectivity.

Workaround

Remove the primary server from the System Administrator Speech Recognition Server list and the License Manager list. In addition, if enhanced TTS is configured for the primary server, remove the server from the System Administrator enhanced TTS page. Manually refresh the system.

CSCee46918

3

other

Callers hear a 5-second delay when Personal Assistant is transferring calls to Cisco Unity voicemail.

The problem occurs when voicemail ports are included in a device pool that also includes media resources (MOH).

Workaround

Configure a device pool exclusively for voicemail ports.

CSCuk45496

3

other

Personal Assistant plays the main menu prompt during a dial-by-location or dial-by-department session.

When Personal Assistant does not find the spoken name in the location or department specified, or does not recognize the name, it replays the main menu prompt instead of replaying the dial-by-location or dial-by-department prompt.

Workaround

Say "Location" or "Department," to return to the dial-by-location or dial-by-department mode.

CSCuk45601

3

other

Personal Assistant speech recognition is slow to respond to voice input.

This occurs the first time speech recognition is used after either the Personal Assistant server is restarted or the system is refreshed.

There is no workaround.

CSCuk45726

3

voicemail

Cannot access voice mail, calendar (for rules processing), or paging servers.

This occurs when one of the server names or mailbox names have changed after the first access attempt.

Workaround

Delete the MAPI profile from the Windows registry.

1. Log on to Windows by using the account under which the PAServer service is running.

2. On the Windows Start menu, click Run, then enter regedt32.exe, and press Enter.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.)

3. If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

4. Expand the registry key
HKEY_CURRENT_USER > Software > Microsoft > Windows NT > CurrentVersion > Windows Messaging Subsystem > Profiles.

5. Right-click Unity System Profile, and click Delete.

6. Close the registry editor.

The new profile should be automatically created the first time someone accesses voice mail through the Personal Assistant server.

CSCuk47244

3

telephony

CTI route points fail to register with a Personal Assistant cluster failover server.

The condition occurs when a change requiring a server restart is made to a CTI route point on the Server Configuration page and the primary Personal Assistant server does not restart. Because only the primary server is directed to restart, the failover servers continue to run with the original configuration.

Workaround

Manually stop and restart the PAServer service on the failover servers. Note that the workaround interrupts Personal Assistant.


Resolved Caveats—Release 1.4(4)

Table 2 Cisco Personal Assistant Release 1.4(4) Resolved Caveats 

Caveat Number
Severity
Component
Description

CSCed78784

2

voicemail

During voice mail browsing, disambiguating causes calls to terminate.

CSCin73916

2

voicemail

Users cannot browse voicemail if the system is using Personal Assistant 1.4(3) or earlier and Cisco Unity 4.0(4) with Exchange 2000 or 2003.

CSCed32457

3

pauseradmin

On the Personal Assistant Administration user interface, the Default Call Pickup Timeout field on the Destination Groups > Edit Destinations page and/or the Call Pickup Timeout value on the Preferences > Settings page may incorrectly display a timeout value of zero.

CSCed63354

3

systemadmin

Speech refreshes fail when the LDIF file contains special characters such as ©.

CSCin69101

3

telephony

When the system is using a Cisco CallManager version earlier than 4.0, Personal Assistant interchanges callers and called parties while processing rules that use destination groups, transfer calls to voicemail, or have call screening enabled.


Documentation Updates

Errors

This section lists errors in the current Cisco Personal Assistant documentation and gives corrected information. The correct information will be incorporated in a future documentation release, or as otherwise noted.

Conferencing and Addressing Voice Messages to Caller Groups: Cisco Personal Assistant User Guide

The "Caller Groups" section in the "Setting Up Caller Groups to Apply Rules to Multiple Callers" chapter of the Cisco Personal Assistant User Guide incorrectly states that when users include a caller group in a conference call or have voice messages sent or forwarded to the group, Personal Assistant tries each member's work phone, then mobile phone, then home phone number, in that order.

Instead, it should say that when users use a caller group in a conference call or have voice messages sent or forwarded to the group, Personal Assistant calls the first number it locates in the work, mobile, or home number fields, in that order. If no one answers the phone, Personal Assistant does not include the member.

Directory Search Filters for Active Directory: Cisco Personal Assistant Installation and Administration Guide

In the "Configuring the Corporate Directory" section in the "Configuring Personal Assistant" chapter of the Cisco Personal Assistant Installation and Administration Guide, Step 6 of the procedure "To Configure the Corporate Directory" instructs you to enter
(&(objectclass=user)(objectcategory=Person)(legacyExchangeDN=*))
in the Directory Search Filter field when the corporate directory is Active Directory.

Instead, it should instruct you to enter
(&(objectclass=user)(objectcategory=Person)(legacyExchangeDN=*))
when the message store is Exchange 2003 or Exchange 2000 and enter
(&(objectclass=user)(objectcategory=Person))
when the message store is Exchange 5.5.

The same error appears under Considerations for the Directory Search Filter field in Table A-3 in the "Corporate Directory Settings" section in the "Personal Assistant Administration Page Reference" appendix of the guide.

Setting the Voice-Mail Access Number: Cisco Personal Assistant User Guide

The "Setting Your Voice-Mail Access Number" section in the "Customizing Personal Assistant" chapter of the Cisco Personal Assistant User Guide incorrectly states that users must specify the phone number they use to access voice mail to have Personal Assistant route calls to voice mail.

Instead, it should say that users must specify their voice mailbox number to have Personal Assistant route calls to voice mail.

In addition, Step 2 of the procedure "To Set Your Voice-Mail Access Number" should instruct users to enter their voice mailbox number in the Voice Mailbox Number field. Typically, the number is the same as their phone number.

Skipping Choices in Disambiguation: Cisco Personal Assistant User Guide

The Cisco Personal Assistant User Guide incorrectly states that users can say "Skip" to skip to the next choice when Personal Assistant presents more than one match to a recorded name during a speech session.

Instead, users can say only "Next" to skip to the next choice. Note that users can also press the pound (#) key to skip.

Omissions

This section lists new and additional information that is not included in the current Cisco Personal Assistant documentation. The new and additional information will be incorporated in a future documentation release, or as otherwise noted.

Configuring Error Handling—Cisco CallManager Version 4.0 or Later: Cisco Personal Assistant Installation and Administration Guide

The procedure "To Create Route Points and Configure Error Handling for the Personal Assistant Interceptor Ports" in the "Creating Personal Assistant Interceptor Port Route Points and Configuring Error Handling—Cisco CallManager Version 4.0 or Later" section of the "Configuring Cisco CallManager for Personal Assistant" chapter of the Cisco Personal Assistant Installation and Administration Guide should include steps to configure the Forward Busy and Forward On Failure parameters for the Interceptor Port route point.

Do the following procedure instead of the procedure in the Cisco Personal Assistant Installation and Administration Guide.

To Create Route Points and Configure Error Handling for the Personal Assistant Interceptor Ports


Step 1 In Cisco CallManager, select Device > CTI Route Point. The Find and List CTI Route Points page opens.

Step 2 Click Add a New CTI Route Point. The CTI Route Point Configuration page opens.

Step 3 In the Device Name field, enter a unique meaningful name to identify this as a Personal Assistant route point interceptor number. (For example, if you are creating the 1XXX route point, PA1XXX or PARP1XXX might be useful names.)

Step 4 In the Device Pool list, click the applicable device pool.

Step 5 In the Calling Search Space list for the device, click the calling search space that is configured for Personal Assistant (for example, PACSS).

Step 6 Click Insert to add the new CTI route point.

Step 7 Click OK to add a directory number for line 1 of the CTI Route Point. The Directory Number Configuration window for line 1 opens.

Step 8 In the Directory Number field, enter the phone number to be used for a Personal Assistant interceptor port (for example, 1XXX).

Step 9 In the Partition list, click the phone partition that is configured for Personal Assistant (for example, PA).

Step 10 In the Calling Search Space list for line 1, click the same calling search space that you chose for the device in Step 5. Do not leave <None> as the calling search space for line 1.

Step 11 In the Voice Mailbox Profile list, click No Voice Mail. Otherwise, Personal Assistant cannot mark user messages with the sender name.

Step 12 In the Destination field for Forward No Answer, enter the same phone number that you entered in the Directory Number field in Step 8.

Step 13 In the Calling Search Space list for Forward No Answer, click the same calling search space that you chose for the directory number in Step 10.

Step 14 Repeat Step 12 and Step 13 for Forward Busy and Forward on Failure.

Step 15 Click Insert.

Step 16 Repeat Step 2 through Step 15 to create any additional route points.


Dialing by Name and Department or Location: Cisco Personal Assistant User Guide

Table 2-3, "Common Dialing Commands," in the "Using Speech-Enabled Directory Dialing" section in the "Using Personal Assistant to Make Calls, Forward Calls, and Access Voice Mail" chapter of the Cisco Personal Assistant User Guide should include the following entry in the Touchtone Key column for dialing by name and department or location:

Press 3 or 3# for location. Press 4 or 4# for department.

In addition, the spoken command column for dial by name and department or location includes the incomplete statement, "Personal Assistant searches for the person's number from a subgroup of your corporate directory."

The statement should say instead: "Personal Assistant searches for the person's number in both the corporate directory and users' entire personal address books. As it searches the corporate directory, it searches only the subgroup of entries for the specified department or location."

Troubleshooting Information

Personal Assistant troubleshooting information can be found:

In the Cisco Personal Assistant Installation and Administration Guide, Release 1.4 at http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/assist14/ag/ag141/index.htm.

On the Cisco Personal Assistant Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/assist.

Cisco Personal Assistant Documentation

For descriptions and URLs of Personal Assistant documentation on Cisco.com, refer to About Cisco Personal Assistant Documentation. The document is shipped with Personal Assistant and is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/assist/about/padoc.htm.

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 access the most current Cisco documentation at this URL:

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

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

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 Ordering tool:

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

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

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or 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

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:

http://www.cisco.com/techsupport

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:

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

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 automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

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:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

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:

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

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://cisco.com/univercd/cc/td/doc/pcat/

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:

http://www.ciscopress.com

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:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

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

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:

http://www.cisco.com/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

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