|
|
These topics address problems you might encounter, and provide ways to resolve them; also included are other tasks associated with problem resolution.
These topics provide resolutions to problems users might encounter:
If users cannot log in to the Personal Assistant user interface, verify that they are using the correct log-in name. The log-in name should match the unique user attribute you defined in the System Configuration settings. For example, if your company is using the employee e-mail address as the unique user attribute, verify that users are entering their e-mail address and not another attribute, such as their phone number.
Related Topics
If users cannot use speech commands and are forced to use touch-tone dialing to interact with Personal Assistant:
If users report that they are being directed to the operator too often when using Personal Assistant, check the Dial by Name settings on the Personal Assistant server. See the "Fine-Tuning Speech Recognition (Dial By Name)" section.
Related Topics
If users report they are given too many options when using dial-by-name, you should reduce the Max Disambiguate parameter of the Dial by Name settings on the Personal Assistant server.
Related Topics
Using the JTAPI Configuration options in the Personal Assistant Administration interface, you can designate the call pickup time. This determines how long Personal Assistant waits for a call to be picked up before it moves on to the next defined dial rule.
However, users can also configure the call pickup time (by selecting Preferences > Settings from the user interface), and this setting takes precedence. For example, if the server setting is 20 seconds, but a user has set their setting to 10 seconds, Personal Assistant uses 10 seconds as the call pickup time.
If users state that they are being transferred too quickly to voice mail, check the call pickup setting in both the administrator and user interfaces.
Related Topics
You can configure dial rules through the Personal Assistant Administration and User interfaces. However, rules configured in the Administration interface take priority over those configured through the User interface. Therefore, if a user has configured a dial rule that conflicts or produces different results than one you configured as the administrator, their rules are ignored.
Related Topics
Under normal circumstances, users should not experience dropped calls while using Personal Assistant. However, if you have recently changed settings on the Personal Assistant server and saved the settings, the server might have restarted. If you do not have any failover servers, Personal Assistant might have been unavailable during this restart.
If a user is actively interacting with Personal Assistant when the server becomes unavailable, the call will drop. However, if Personal Assistant has already completed its role in the call, such as a successful transfer, the call will not bed dropped.
To prevent calls from being dropped while Personal Assistant is being used, limit the changes and restarts to the Personal Assistant server to off-peek or other times of lower demand. Also, if you do not have a failover server, consider adding one in order to more reliably support your users.
Related Topics
These topics provide resolutions to problems you might encounter when managing Personal Assistant:
If you recently added a new speech recognition server or additional license manager hosts, you must refresh the servers before they can support users. See "Configuring Personal Assistant Global Settings" section.
The Personal Assistant Control Center provides you with information about the status of the Personal Assistant servers. To access the Control Center, select System>Control Center from the Personal Assistant administration web interface.
Table 6-1 indicates the possible server status. Use this information to determine the current server status and to resolve any problems.
| Icon | Explanation | Solution |
|---|---|---|
| Server is stopped. | You or Personal Assistant have stopped the server. Personal Assistant stops the servers during a normal refresh. |
| Server is experiencing connectivity or permission errors. | Verify that the Personal Assistant servers are connected and up and running properly. If you have added Personal Assistant to a Windows 2000 domain, ensure that the server has administrator privileges in the domain. This is configured during installation. |
| Server is started. | Server is functioning normally. |
Related Topics
You can start and stop the Personal Assistant servers, speech recognition servers, and license managers through the Personal Assistant administrative web interface. This can help you add or remove servers from the Personal Assistant and speech server clusters in an orderly manner. It can also help you bring down a server that is not functioning properly.
Procedure
Personal Assistant opens the control center. The control center is divided into three sections:
The status of one type of server does not affect the status of any other type of server on the same system. For example, you can stop a license manager without stopping the Personal Assistant server on the same system, and vice versa.
Step 2 Find the Personal Assistant server, speech-recognition server, or license manager you want to start or stop, and click the Start or Stop button that is on the same line as the server.
You can start or stop all of the Personal Assistant servers, speech-recognition servers, or license managers as a group by clicking the Start All or Stop All button associated with the group.
Tips
Related Topics
When you contact Cisco Technical Support for help with a problem you are having with Personal Assistant, Cisco might request that you collect trace and debug information.
Because collecting trace and debug information will affect Personal Assistant's performance, you should only turn on tracing and debugging at Cisco's request. The generated information is for Cisco's use in resolving product problems.
To collect trace and debug information, perform the following steps.
Procedure
Personal Assistant opens the Server Configuration page.
Step 2 From the left column, select the server from which you need to collect debug or trace information.
Personal Assistant displays the settings for the server.
Step 3 Scroll down to the Personal Assistant Debug Package List and Personal Assistant Trace Package List sections. Select the packages that Cisco Technical Support has requested. The lists in each section are identical; make sure that you select the package in the list Cisco requested. Packages selected in the Debug list generate trace information plus extra debug data. If Cisco request you select all packages, click Select All from the appropriate list.
The available packages include:
Step 4 Click Save Settings to save and activate your changes.
Personal Assistant begins generating the requested trace and debug information.
The information is placed in a log file in the /log subdirectory of the Personal Assistant installation directory. Or, if you configured Personal Assistant to use the CiscoWorks 2000 Syslog facility when you installed Personal Assistant, the data is sent to syslog. Send this information to the Cisco Technical Support group with which you are working.
Step 5 When you have finished generating debug and trace information, turn off debug and trace by clicking Clear All for each section in which you have made a selection. Then, click Save to complete the change.
Related Topics
You can manage the status of the Personal Assistant server remotely using CiscoWorks2000 or another SNMP-based network management system. CiscoWorks2000 is the standard Cisco network management system, but it is not bundled with Personal Assistant. For more information about CiscoWorks2000, Campus Manager, and Topology Services, refer to the documentation, available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/index.htm
These topics provide information to assist you in integrating Personal Assistant with network management systems:
Personal Assistant uses the Cisco Discovery Protocol (CDP) to periodically send out CDP messages, on the active interface, to a designated multicast address. These messages contain information such as device identification, interface name, system capabilities, SNMP agent address, and time-to-live. Any Cisco device with CDP support can locate a Personal Assistant server by listening to these periodic messages.
Using information provided through CDP, the CiscoWorks2000 Server can detect the Personal Assistant Server, and the Campus Manager application, Topology Services, can build topology maps displaying the Personal Assistant server.
Personal Assistant supports the SYSAPPL-MIB that allows you to use CiscoWorks2000 or a third-party SNMP browser to remotely access information about the following Personal Assistant components:
The SYSAPPL-MIB uses the Simple Network Management Protocol (SNMP). Personal Assistant supports the following SYSAPPL-MIB tables:
During installation of Personal Assistant, you can choose whether to integrate with Cisco Syslog Collector (see the "Personal Assistant Installation Procedures" section for details). Cisco Syslog Collector and Cisco Syslog Analyzer are offered with CiscoWorks2000 as part of the Resource Management Essentials package. You can also adapt Syslog output from Personal Assistant for use with other network management systems.
The Cisco Syslog Collector keeps common system logs of messages reported to the Personal Assistant.
The Cisco Syslog Analyzer controls and displays all events efficiently so they can easily be read, interpreted, and used for system maintenance and problem solving.
Posted: Thu May 3 11:13:31 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
