|
These topics describe the fields on the pages of the Personal Assistant administrator's interface.
The Speech Services Configuration page is opened when you select System>Speech Services.
Use the Speech Services Configuration page to configure the speech servers and the speech-recognition characteristics used when a user dials a number by speaking the name of the party to be called or when accessing voice mail.
Personal Assistant comes preconfigured for dialing by name, so you only need to change these settings if you find they do not work well for your organization. You might want to change these settings if there are a large number of similarly named people in your organization, or if accents in your group prevent the speech-recognition software from confidently interpreting their requests. Trial and error is the only effective way to determine whether you need to make changes to these settings to best suit your needs.
If the speech-recognition software has too many problems understanding a caller, the caller is sent to the operator. Select System>Miscellaneous Settings to enter the operator extension.
Field | Description | Notes |
---|---|---|
The schedule for Personal Assistant to update user information from the corporate directory. Designate the time you desire for Personal Assistant to update its user information. Pick a time when directory updates are complete for the day, and there is reduced user access to Personal Assistant and the directory. Click Refresh to force Personal Assistant to update user information immediately. You might want to force a refresh if a large number of updates have been made to the directory and Personal Assistant is encountering a large number of speech-recognition errors. | Changes to the corporate directory require Personal Assistant to recompile its speech-recognition grammar and to update various information that is kept in cache, such as telephone numbers for call routing. The default time is 2:00 a.m. Refresh can take several minutes. | |
Speech License Configuration | ||
The license key for the speech-recognition software. You must enter a valid key to enable speech recognition. | Cisco provides this based on how many speech-recognition license ports you purchased. Changes to this setting take effect only after refresh. | |
Shows the maximum number of simultaneous speech ports available using this license code. | If users complain that they are too frequently routed to touch-tone dialing rather than dial-by-name, consider adding additional speech ports. | |
Speech Recognition Parameters | ||
The number of selections to present the user when more than one party matches the spoken name. For example, if you enter 3, and the user tries to call John Smith, if there are two or three John Smiths in the directory, Personal Assistant plays the spoken name or extension, allowing the user to choose the correct one. If more numbers match the spoken name than the Max Disambiguate value, Personal Assistant sends the user to the operator for assistance in reaching the person. | If only one number matches the spoken name, the number is dialed immediately. The default is 3. | |
Whether a user can interrupt Personal Assistant's prompts before they are finished. If you select true, a user can enter commands in the middle of a Personal Assistant prompt. If you select false, users must always wait until Personal Assistant finishes speaking. | The default setting is true. Use caution in disabling this feature. Typically, you should not disable it unless there is excessive background noise at the users' locations. | |
The percentage confidence level below which the user's request is rejected. Personal Assistant tells the user that the request could not be understood. The user can then repeat the request or try phrasing it differently. The speech-recognition software assigns a percentage confidence level to every session. If the software is less than the Rejection Confidence Level, Personal Assistant tells the user that the request could not be understood. The user can then repeat the request or try phrasing it differently. | The default is 45. Enter a number between 0 and 100. Do not include the percentage sign in the field. | |
The percentage confidence level below which the user is asked to confirm the speech-recognition software's interpretation of the request. If the software's confidence level is between the Rejection Confidence Level and the Reconfirm Confidence Level, Personal Assistant tells the speaker its interpretation of the request and asks the speaker to confirm the interpretation. | If the speech-recognition software's confidence level is higher than the Reconfirm Confidence Level, Personal Assistant completes the speaker's request without asking for confirmation. However, the speaker can tell Personal Assistant to cancel or stop the action. If you set this level too high, users will have to reconfirm most commands. If you set it too low, Personal Assistant might perform too many unintended tasks. The default is 60. Enter a number between 0 and 100. Do not include the percentage sign in the field. | |
The maximum number of speech-recognition errors allowed in a single dialog. One user session with Personal Assistant or voice mail consists of several dialogs; for example, the attempt to dial a person would be a single dialog. If the user exceeds this error count, Personal Assistant transfers the user to the operator. |
| |
The maximum number of speech-recognition errors allowed in an entire Personal Assistant or voice-mail session (that is, the sum of errors in each dialog). If the user exceeds this error count, Personal Assistant transfers the user to the operator. | The Max Total Error Count must be larger than Max Error Count. When the user is in voice mail, the user must encounter three times the error count configured here before the count is considered exceeded. | |
The maximum number of times the user can ask Personal Assistant or the voice-mail system for help within a single dialog. If the user asks for help more times than this number, Personal Assistant transfers the user to the operator. | When a user asks for help, Personal Assistant or the voice-mail system tells the user the various actions the user can perform at that point in the dialog. | |
The maximum number of times the user can ask Personal Assistant for help in an entire Personal Assistant or voice-mail session. If the user asks for help more times than this number, Personal Assistant transfers the user to the operator. | The Max Total Help Count must be larger than Max Help Count. When the user is in voice mail, the user must ask for help three times the count configured here before the count is considered exceeded. | |
A list of the speech servers. This list creates the speech-recognition server cluster.
| Use the Control Center to manage which speech servers are active. See the "Control Center" section. Changes to this setting take effect only after refresh. | |
A list of the speech-recognition license managers. This list identifies which Personal Assistant servers in the cluster will manage the licenses for the speech-recognition server cluster. The speech-recognition servers will not operate without a license manager that has a valid license.
| Cisco recommends that you identify two license managers. This ensures that a backup is available if one manager is disabled. Use the Control Center to manage which Personal Assistant servers have active license managers. See the "Control Center" section. Changes to this setting take effect only after refresh. | |
Save button | Click Save to save and activate changes. |
|
The Telephony Configuration page is opened when you select System>Telephony.
Use the Telephony Configuration page to configure the telephony providers that create the connection between Personal Assistant and Cisco CallManager.
Note You must create at least one JTAPI provider and one Skinny provider before you can configure a Personal Assistant server. These providers must be in the same Cisco CallManager cluster as the one to which the Personal Assistant server homes (that is, where the Personal Assistant server's telephone numbers are defined). See the "Server Configuration" section for more information on server configuration. |
Field | Description | Notes |
---|---|---|
Provider List | The left-hand column lists the providers you have already created. They are listed according to the provider group names you create when defining the provider. Click on a provider name to view the provider's characteristics. |
|
Insert button | Click Insert, after filling in the fields, to add the provider to the provider's list. | This button only appears when you first enter the Telephony Configuration page, when you click the New button, or after you delete a provider. |
New button | Click New to open a clear page so that you can add a new provider. | This button only appears if you click on a provider in the Providers List (left column). |
Save button | Click Save to save and activate your changes. | This button only appears if you click on a provider in the Providers List (left column). |
Delete button | Click Delete to delete the provider that you are currently viewing. You are prompted to confirm the deletion. | This button only appears if you click on a provider in the Providers List (left column). |
Provider Group Name | The name of the provider group you are adding. Enter a name you will find meaningful. When configuring Personal Assistant servers, you will select providers based on the names you enter in this field. You cannot change this name once you add it to the list. To change the name, you must create a new provider group, change the configuration of any Personal Assistant server using the old group name, then delete the old provider group. | You must create one JTAPI provider and one Skinny provider for every Cisco CallManager cluster in which Personal Assistant server's have their telephone numbers and route points defined. For example, if you have 5 Cisco CallManager clusters in which Personal Assistant servers have numbers defined, you must define at least 10 providers (5 JTAPI, 5 Skinny). |
Provider Type | The type of telephony provider, JTAPI or Skinny. | Personal Assistant uses both JTAPI and Skinny protocols, and must have providers for both. JTAPI is used for interceptor ports and route points; Skinny is used for media ports. |
Telephony Providers | A list of the providers you want to use as a provider group:
All CTI Managers or Cisco CallManager servers you specify for a single provider group must be within the same Cisco CallManager cluster. To add a provider to the list, enter the DNS name or IP address in the edit box and click Add. To remove a provider, select the provider in the list and click Remove. |
|
User Name and Password | A CTI user name and password, as defined in Cisco CallManager, that Personal Assistant will use to access the Cisco CallManager system for a JTAPI provider. In Cisco CallManager, you must associate the Personal Assistant devices and ports with this user name, so that Personal Assistant can control the CTI route points. | Do not specify a user name and password for a Skinny provider. The password appears as asterisks (**) to ensure security. |
The AA Prompt Configuration page is opened when you select System>AA Prompt.
Use the AA Prompt Configuration page to upload the prompt for a simple automated attendant, if you create one. A Personal Assistant automated attendant can only support dialing by name: you cannot use it to provide access to conferencing, voice mail, or other Personal Assistant features.
Note You must identify the automated attendant telephone number in the Personal Assistant server configuration. See the "Server Configuration" section for more information. |
Field | Description | Notes |
---|---|---|
The file to use as the automated attendant prompt. Click Browse to locate the file on a local or network-attached file system. The file must be a .wav file in CCITT u-Law format (G.711 u-Law). Because the Personal Assistant automated attendant only supports dial by name, your prompt should at least tell the caller to say the name of the person they are trying to reach. | Personal Assistant does not include a recording facility: you must create this file with an appropriate voice recording application. | |
Click Upload to upload the prompt file into the directory. | After the file is uploaded, and you have configured an AA number in the Personal Assistant server configuration, callers to AA number will hear your prompt and can then ask Personal Assistant to dial an employee by saying the employee's name. |
The Messaging page is opened when you select System>Messaging.
Use the Messaging page to enable paging and calendar-based dial rule processing, and to configure the connection with the voice-mail system.
Field | Description | Notes |
---|---|---|
Calendar Server Attributes | ||
DNS name or IP address of the Microsoft Exchange Server. |
| |
First name and last name of the administrator account on the Microsoft Exchange server.
| To find the administrator's first and last name:
| |
Paging Server Attributes | ||
Paging SMTP Server Name | The DNS name or IP address of the e-mail paging server. Personal Assistant uses this server to send e-mail pages to users who configure an e-mail paging address and define rules that use the address. |
|
The SMTP port used to send messages to the SMTP server. | The default setting is 25. | |
The domain to which the paging SMTP server belongs. |
| |
Voice-mail Server Attributes | ||
The Exchange mailbox name for the Unity profile created on every Personal Assistant server, for example, "Unity Messaging System." | This name is required if you are using any Cisco Unity voice-mail servers, optional otherwise. | |
The number of voice-mail ports allowed by your Cisco Unity license, which indicates the maximum number of simultaneous voice-mail sessions in Personal Assistant. You must determine the number of ports on the Cisco Unity system and enter this value for Personal Assistant. | The default setting is 2. This field is only required if you are using at least one Cisco Unity voice-mail server. | |
The delay (in milliseconds) between making a connection to the voice-mail system and submitting the DTMF redirection sequence for transferring a caller to the appropriate voice mailbox. The delay ensures that the connection to the voice-mail system is successful before entering the DTMF sequence. Redirection is used when processing call routing rules that transfer calls to voice-mail. | If you make this delay too long, the caller might get confused and hang up before getting the voice-mail for the party. If you make it too short, calls might get dropped due to a missed connection. Try 2000 for Cisco Unity systems, and 3000 for Octel systems. Experiment to determine if the setting is appropriate. | |
The unqualified DNS name of the voice-mail server you want to add, for example, unity1. Do not use fully-qualified names (such as unity1.domain.com) or IP addresses for the server name. If you use one of these, users will not be able to access voice-mail from Personal Assistant. | This field is optional for non-Cisco Unity servers. For Octel systems, leave the field blank. | |
The telephone extension used to access the voice-mail system you are adding. | This field is required for all voice-mail servers. | |
The redirection DTMF sequence for transferring a call internal to the corporate telephone network to the voice-mail system. This sequence is defined in the voice-mail system used on the server you are adding. For example, the default sequence, #X#2 for the Cisco Unity system, indicates that internal calls can be transferred to voice mail by pressing #, then the extension (represented by the variable X), # again, and then 2. Personal Assistant issues this DTMF sequence when a user's call processing rule says to transfer a call directly to voice mail. | See the documentation for your voice-mail system to determine the appropriate DTMF sequence. | |
The redirection DTMF sequence for transferring a call external to the corporate telephone network (that is, from the PSTN) to the voice-mail system. This sequence is defined in the voice-mail system used on the server you are adding. |
| |
Click Add Server to add the server to the list. | You must fill in the voice-mail server name (for Unity systems only), pilot number, and both DTMF fields before you can add a server. | |
A list of the voice-mail servers you have configured for use with Personal Assistant. To modify a server, change the server's attributes and click Update. To delete a server, click the trash can icon. |
| |
Click Synchronize to force Personal Assistant to load the spoken names kept in Cisco Unity for each user to the Personal Assistant spoken name for each user. By synchronizing the spoken names with Cisco Unity, users only need to record their spoken name once. | Synchronization is not supported with other voice-mail systems. | |
Save button | Click Save to save and activate your changes. |
|
The Dial Rules Configuration page is opened when you select System>Dial Rules.
Use the Dial Rules Configuration page to create global dialing rules. These rules can help you automatically strip numbers from or add numbers to telephone numbers that your users dial. For example, you could automatically add 9 in front of seven-digit numbers to permit users to access an outside line. These rules are applied when a user is dialing a number through Personal Assistant.
Field | Description |
---|---|
The section at the top of the page, which contains a fill-in-the-blanks sentence, where you can create a new dialing rule. Fill in the necessary blanks (you do not have to fill in every blank) and click Add Rule. A rule is only applied to a dialed number if all the conditions are met. The available conditions are:
The available actions are:
| |
An ordered list of the rules you have created. The rules are applied top to bottom, and the first rule that matches the dialed number is applied. Once a rule is applied, no subsequent rules are processed. You can modify, rearrange their priority, or delete rules:
|
The Directory Lookup Rules page is opened when you select System>Directory Lookup Rules.
Use the Directory Lookup Rules page to create rules for converting dialed numbers to numbers that exist in the corporate directory. This makes it possible for Personal Assistant to match the dialed number with the directory entry for the calling party. For example, if the incoming call is from 51234, but the corporate directory uses 10-digit numbers, you can create a rule to convert 51234 to 5555551234. This does not affect the number dialed, it only provides Personal Assistant with a valid number for looking up the user in the corporate directory.
The directory lookup rules only apply to incoming calls that are internal to the corporate telephone network.
Field | Description |
---|---|
The section at the top of the page, which contains a fill-in-the-blanks sentence, where you can create a new directory lookup rule. Fill in the necessary blanks (you do not have to fill in every blank) and click Add Rule. A rule is only applied to an incoming number if all conditions are met. The available conditions are:
The available actions are:
| |
An ordered list of the rules you have created. The rules are applied top to bottom, and the first rule that matches the incoming number is applied. Once a rule is applied, no subsequent rules are processed. You can modify, rearrange their priority, or delete rules:
|
The Directory Hierarchy page is opened when you select System>Directory Hierarchy.
Use the Directory Hierarchy page to create locations and departments that a client can use to narrow a dial by name directory search. For example, if you create a location called NewYork, clients can tell Personal Assistant to search the NewYork location for Roger Smith. This can help clients get the correct party when dialing a person with a common name.
The Corporate Directory Settings page is opened when you select System>Corporate Directory Settings.
Use the Corporate Directory Settings page to identify the corporate directory server. This is the directory that contains information, such as phone numbers and locations, on all of the employees in the corporation. Personal Assistant uses this information to find the phone number for an employee when someone tries to phone the employee using the employee's name.
Field | Description | Notes |
---|---|---|
The field within the directory that is unique for each record. This helps Personal Assistant correctly locate numbers when your users attempt to dial a person by name. If you are using the Cisco CallManager DC directory as your corporate directory, the unique user attribute name is cn. If you are using a different directory, ask the directory administrator for the unique name. | See the "Understanding How Personal Assistant Uses Directories" section for an explanation of how Personal Assistant uses directories. | |
The URL for the corporate directory, for example, ldap://server.domain.com. |
| |
The administrator name for the directory if authentication is required for accessing the directory. |
| |
The administrative password for the directory if authentication is required for accessing the directory. |
| |
The Distinguished Name (DN) for the user node of your corporate directory. |
| |
An LDAP expression for limiting the number of entries retrieved. For example, you could limit Personal Assistant's directory lookups to a specific location, thus only allowing clients to use name dialing for employees in the selected area. For example, if your directory includes a "location" field, and "newyork" is a valid location in your directory, a directory search filter for limiting searches to New York might be: (location=newyork)
| The expression you enter must be valid for the directory you are using. See the documentation supplied with the directory, and your directory administrator, for information on valid LDAP expressions for your corporate directory. | |
Save button | Click Save to save and activate your changes. |
|
The User Settings Administration page opens when you select System>User Settings.
Use the User Settings Administration page to manage Personal Assistant users.
Note You cannot reset the user's password through Personal Assistant. Personal Assistant uses the Cisco CallManager password for the user. To change or reset the password, you must use the Cisco CallManager interface. |
Field | Description | Notes |
---|---|---|
One or more users who you want to administer. If you enter more than one user ID, separate them with commas or spaces. For example: jones, smith
| The User ID is the unique name used in the corporate directory, for example, email address. | |
Click Reset in Reset Pin to clear the user's Personal Identification Number for Personal Assistant. The user must select a new PIN the next time he logs into Personal Assistant. | Resetting the PIN does not affect the user's data. | |
Click Reset in Reset Spoken Name to erase the user's spoken name for Personal Assistant. The user must record his name again the next time he logs into Personal Assistant. | The user can also reset the spoken name through the Personal Assistant user interface. | |
Click Delete to delete the users from the Personal Assistant directory. For example, if an employee leaves the company, deleting the employee's record from the corporate directory will not clear the Personal Assistant data from the directory. Similarly, if a cell phone is transferred from one employee to another, the cell phone number might stick with the old employee. Deleting the employee will clear the data. | Revise your company's procedures to ensure you delete the Personal Assistant data for former employee's along with the directory record. |
The Miscellaneous Settings page displays when you select System>Miscellaneous Settings.
Use the Miscellaneous Settings page to configure some system-wide settings for Personal Assistant.
Field | Description | Notes |
---|---|---|
The phone extension of the telephone operator for your organization. Enter a valid extension for a number dialed within your phone network. For example, if you can reach the operator within your phone network by dialing 5 digits, enter the 5-digit number (for example, 12345). | Personal Assistant might transfer a call to the operator for a variety of reasons, including when a call to Personal Assistant contains more speech-recognition errors than you allow for. You can configure settings that control when a call is transferred to the operator. See the "Speech Services Configuration" section. | |
The time, in seconds, that the receiver of a call is allotted to answer a call when Personal Assistant is processing a rule that requires Personal Assistant to ring a series of phone numbers. | If the call is not answered within the timeout window, Personal Assistant rings the next phone number as defined in the rule. | |
The interval, in seconds, for which each Personal Assistant server sends keep-alive messages to the other Personal Assistant servers within the cluster. If the other servers in the cluster do not receive a keep-alive message from a server within the expected interval, they assume the server is disabled and take over its calls. | The default is 30 seconds. Only change this setting if you find it does not suit your network (for example, disabled servers are not being identified quickly enough, or the cluster is creating too much keep-alive traffic). | |
The TCP port on which Personal Assistant servers listen for Personal Assistant inter-server communication. | The default is 2000. Only change this if another application on the server is already using this TCP port. | |
The fully-qualified DNS name of the CiscoWorks2000 server, for example, server.domain.com. | This name is only required if you select true for Write to Syslog. Do not use an IP address. | |
Whether Personal Assistant should write log messages to the CiscoWorks2000 Syslog facility (true), or simply write messages to a local log on the Personal Assistant server (false). | Personal Assistant must be able to contact the server for you to enable syslog. If the server is not reachable, Personal Assistant resets this setting to false. | |
The number of messages to collect before writing them to syslog. The larger the number, the less frequently data is written to syslog (improving system performance). However, if you buffer too many messages, syslog information might not be sufficiently up-to-date to be useful to you. | The default is 4 messages. | |
Save button | Click Save to save and activate changes. |
|
The Control Center page is opened when you select System>Control Center.
Use the Control Center page to start and stop the major services on the servers within the Personal Assistant and speech-recognition server clusters.
Field | Description | Notes |
---|---|---|
Controls the status of the Personal Assistant server service on the listed system. A server is started if there is an arrow icon beside it; it is stopped if there is a square icon beside it.
| A change to the status of the Personal Assistant server does not change the status of a license manager or resource manager on the same system. When you stop a server, the other servers in the cluster automatically take over the responsibilities of the stopped server. | |
Controls the status of the license manager service on the listed system. A license manager is started if there is an arrow icon beside it; it is stopped if there is a square icon beside it.
| The license manager controls how many simultaneous speech requests can be handled. | |
Controls the status of the speech server service on the listed system. A server is started if there is an arrow icon beside it; it is stopped if there is a square icon beside it.
| When you stop a server, the other servers in the cluster automatically take over the responsibilities of the stopped server. |
The Server Configuration page is opened when you select Servers>Server Configuration.
Use the Server Configuration page to add Personal Assistant servers to the Personal Assistant server cluster and configure them. These settings determine which user telephone extensions are assigned to each server, as well as how the server manages its resources.
Field | Description | Notes |
---|---|---|
A list of the Personal Assistant servers that you have inserted into the Personal Assistant server cluster (shown in the left column). Click a server to view or change its configuration. |
| |
Insert button | Click Insert, after filling in the fields, to add the Personal Assistant server to the server cluster. | The Insert button only appears when you first enter the Server page, or when you click the New button. |
New button | Click New to add a new Personal Assistant server to the cluster. If the New button is not displayed on the page (and the Insert button is displayed), then you can add a server without first clicking New. | The New button only appears if you click on a server in the Personal Assistant server list (left column). |
Save button | Click Save to save and activate your changes. | The Save button only appears if you click on a server in the Personal Assistant server list (left column). |
Delete button | Click Delete when viewing the configuration of a Personal Assistant server that you want to remove from the server cluster. You must click on the server you want to delete, in the server list, before you can delete it. | The Delete button only appears if you click on a server in the Personal Assistant server list (left column). |
A unique name for the Personal Assistant server. This is not the same as the server's DNS name or IP address. It is a name that Personal Assistant uses internally for identifying the server. | The name must be unique within the Personal Assistant cluster. Choose a naming convention that is meaningful to you. | |
The DNS name or IP address of the Personal Assistant server. |
| |
The start of the range of UDP ports that the Personal Assistant server will use for telephone calls. The number should be even: Personal Assistant will only use even port numbers. For example, if you use 32000 as the starting port, Personal Assistant will use ports 32000, 32002, 32004, and so forth. | The number of UDP ports used is based on the Personal Assistant Number of Telephony Ports setting. | |
The CTI Manager that will provide the JTAPI service required for the Personal Assistant and automated attendant CTI route points (telephone number). You must select a provider that resides in the same Cisco CallManager cluster in which the CTI route points are configured. | You must first configure a JTAPI provider. See the "Telephony Configuration" section for more information. | |
The telephone extension for the Personal Assistant server, which you must define as a CTI route point in Cisco CallManager. | Users call this number to reach Personal Assistant. If you are using more than one Personal Assistant server, you should consider configuring the "call forward busy" and "call forward" no answer extensions for the CTI route point to use the number of another Personal Assistant server. This ensures that a user can reach Personal Assistant even if the server the user calls is busy. See the "Setting Up Personal Assistant Server Load Balancing" section. | |
The telephone extension for a simple auto-attendant that will use Personal Assistant to allow callers to reach a user by saying the user's name. You must define this extension as a CTI route point in Cisco CallManager. | You must also record and configure a prompt for the auto-attendant. See the "Creating a Simple Automated Attendant" section for more information. | |
The Cisco CallManager server that will provide the Skinny service required for the media ports. You must select a provider that resides in the same Cisco CallManager cluster in which the Personal Assistant's CTI route point is configured. | You must first configure a Skinny provider. See the "Telephony Configuration" section for more information. | |
The start of the range of ports that will be used to terminate calls to Personal Assistant. When Personal Assistant answers a call, it is assigned to an available port in this range. | The number of telephony ports used is based on the Personal Assistant Number of Telephony Ports setting. | |
The number of ports available for user calls. The number you select must be based on how you have installed Personal Assistant, the hardware platform you are using, and whether you are configuring failover for the server (see the "Fail-over Server Names" section setting). See the "Creating Server Clusters" section for information about the maximum available ports for the various hardware platforms and installation configurations. | For example, if you enter 12, Personal Assistant can handle 12 simultaneous calls with users. If the server fails, and you have configured a failover server, the failover server must be able to take on 12 additional ports. | |
The CTI Manager that will provide the JTAPI service required for the Personal Assistant interceptor ports. You must select a provider that resides in the same Cisco CallManager cluster in which the Personal Assistant's CTI route points are configured. The provider you select here can be a different CTI Manager than the one selected for Route Address Provider. | You must first configure a JTAPI provider. See the "Telephony Configuration" section for more information. | |
The telephone extensions of the users that are using Personal Assistant. The numbers you list here must be defined as CTI route points in Cisco CallManager. Any number you enter here must already be configured in the Cisco CallManager cluster controlled by the CTI Manager identified in the Interceptor Port Provider field. You can specify:
If you are using more than one Personal Assistant server, you should divide the supported extensions among the Personal Assistant servers.
| Calls are directed to Personal Assistant so that the users' call-routing rules can be evaluated for incoming calls. Configuring an extension for Personal Assistant Interceptor Port Range is not enough to get a user's calls transferred to Personal Assistant. In Cisco CallManager, you must also update the partitions and calling search spaces. See the "Defining Partitions and Call Search Spaces for Personal Assistant" section and the "Setting Up Personal Assistant to Intercept Calls" section for more details. | |
A list of Personal Assistant servers that can take over for a server if it fails.
| Establishing failover servers requires careful planning. If you specify failover servers, your Personal Assistant servers must have enough available ports to take over for a failed server. See the "Creating Server Clusters" section and the "Creating Server Clusters" section. | |
A selection of subsystems for which you need to collect brief trace information. Only select subsystems at the request of Cisco Technical Support; the trace information is for Cisco's use to help resolve problems that you cannot solve yourself. If you select a subsystem for debug, you do not have to select it for trace. | See the "Collecting Trace and Debug Information" section for an explanation of each field. | |
A selection of subsystems for which you need to collect detailed debug information. Debug information includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Cisco's use to help resolve problems that you cannot solve yourself. | See the "Collecting Trace and Debug Information" section for an explanation of each field. |
The Server Status page is opened when you select Servers>Server Status.
Use the Server Status page to view the current status of the Personal Assistant servers and their subsystems. The status can help you identify problems that need to be addressed. The status is given using icons:
Icon | Meaning |
---|---|
| Up. The server, port, or other item is running correctly. |
| Down. The server, port, or other item is not running correctly. |
Field | Description | Notes |
---|---|---|
Server List | A list of the Personal Assistant servers that you have inserted into the Personal Assistant server cluster (shown in the left column). Click a server to view its status. |
|
Server | Whether the Personal Assistant server is available (up) or unavailable (down). | If the server is unavailable, try restarting it using the Control Center (see Control Center). If that does not solve the problem, check the server itself to determine the problem. The problem might also be the network connection to the server or the subnet where the server resides. |
Fail Over Server | The name of the server that has taken over for this server if it is unavailable and you have configured a failover server. |
|
Route Point | The status of the Personal Assistant route point. | If the route point is unavailable, check it in Cisco CallManager to determine the problem. |
AA Route Point | The status of the automated attendant route point. | If the route point is unavailable, check it in Cisco CallManager to determine the problem. |
Media Ports | The status of each media port you defined. |
|
Interceptor Ports | The status of each interceptor port you defined. |
|
Active Calls | The number of calls the server is currently handling. |
|
Posted: Thu Oct 3 14:25:54 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.