CUACS120101GUIDE
CUACS120101GUIDE
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower,
Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design),
Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are
service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without
Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study,
IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar,
PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath,
WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0907R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Document Conventions ii
Accessing Cisco Unified Attendant Console Standard When There Are No Valid Devices 3-4
APPENDIX E Using a Cisco Unified Communications Manager TFTP server for all non-TAPI functions E-1
INDEX
This guide describes how to install and configure Cisco Unified Attendant Console Standard.
Section Contains
Chapter 1, “Introduction to Cisco Unified Introduction to Cisco Unified Attendant Console
Attendant Console Standard” Standard
Chapter 2, “Installing Cisco Unified Attendant Preparing Cisco Unified Communications Manager
Console Standard” and installing Cisco Unified Attendant Console
Standard
Chapter 3, “Starting Cisco Unified Attendant Starting Cisco Unified Attendant Console Standard
Console Standard” and configuring operator details
Chapter 4, “Configuring Cisco Unified Configuring Cisco Unified Attendant Console
Attendant Console Standard” Standard, including managing sign in devices
Chapter 5, “Directories” Using and controlling directories
Chapter 6, “Keyboard Shortcuts” Setting up keyboard shortcuts
Appendix A, “Application Log Configuration Configuring application logging
and Collection”
Appendix B, “Import/Export File Formats” Formats of import and export files
Appendix C, “Phones Supported by Cisco List of supported Cisco phones
Unified Attendant Console Standard”
Document Conventions
The following textual and typographic conventions are used in this document:
Convention Usage
bold font Commands, keywords and user-entered text appear in bold type.
italic font Document titles, new or emphasized terms, and arguments for which you supply values
are in italic font.
[] Elements in square brackets are optional.
{x | y | z} Required alternative keywords are enclosed in braces and separated by vertical bars.
[x | y | z] Optional alternative keywords are enclosed in square brackets and separated by vertical
bars.
string A non-quoted set of characters. Do not use quotation marks around the string or the
string will include the quotation marks.
courier font Terminal sessions and information the system displays appear in courier font.
Tip Means the following information will help you solve a problem.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Timesaver Means the described action saves time. You can save time by doing what is described in the paragraph.
Warning Means reader be warned. In this situation, you might do something that could result in bodily injury.
Cisco Unified Attendant Console Standard is a Microsoft Windows-based attendant console application
for use with Cisco Unified Communications Manager (CUCM). For details of the supported versions,
see Cisco Unified Communications Manager Compatibility, page 2-4. Cisco Unified Attendant Console
Standard supports up to 5000 contacts on a single instance.
Cisco Unified Attendant Console Standard enables you to do the following:
• Control calls on your local IP Phone, XMPP client (such as Jabber), or Cisco IP Communicator
• Make, answer and end calls
• Hold and resume calls
• Blind/consult transfer calls to directory contacts or voicemail, or any other valid number
• Direct transfers
• Join calls
• Set Call Forward and Do Not Disturb on the operator phone
• Park calls
• Create and manage conference calls
• Import custom directories of contacts not in your Cisco Unified Communications Manager directory
• Create custom directories (directory groups) and export them to share with other operators
• Synchronize Cisco Unified Attendant Console Standard’s corporate (main) directory with a CUCM
or CSV file source directory
• During synchronization with your source directory:
– Map the fields from your source directory to the ones in the corporate directory
– Filter contacts, so that only certain ones are added to the corporate directory
– Modify contact numbers using BLF rules
• See the line state and presence of each contact
• View call history
• Specify the devices used to sign in to the application
• Log in to a hunt group when you sign in to the application
• Use Jabber presence integration in a single sign-on (SSO) environment
Online help on the application is available. For how to display the help, see Accessing Help on the
Application, page 1-3.
Component Function
Main menu Controls for using and configuring the application. Many of these controls are also
available when you right-click specific parts of the interface. For example,
controls relevant to the directories are displayed when you right-click in the
directory pane.
The extension used to sign in to the application. You can click this to sign out of
the application, or to log into and out of hunt groups.
Call Control pane Displays the active call information on any line on the console phone, including
the call status and duration, and controls for frequently used actions, such as
transferring or ending the call.
Component Function
Parked Calls pane Displays active parked calls, by default in the order in which they were parked.
Parked call information includes the park extension used, the identities of both the
caller and the DN that parked the call, and how long the call has been parked.
Call History pane Displays calls completed in the current session, by default listed in reverse
chronological order. You can change the order in which completed calls are listed.
This pane is not displayed by default; use View > Show Call History to display it.
Directory pane Displays the synchronized directory, directory groups and search results. Contact
information includes line state, presence and any notes. Includes the following
controls:
For more information on the Directory pane, see Viewing and Using Directories,
page 5-17.
You control the interface using both your mouse and keyboard. Many things that you can do with the
mouse you can also do using your keyboard, provided that the application interface is selected.
To install Cisco Unified Attendant Console Standard you must do the following:
1. Ensure that the PC running it satisfies the minimum hardware and software requirements. These are
described below.
2. Within Cisco Unified Communications Manager, create an Application User with associated
phones. If you are working in a non-SSO environment and intend to use the Presence facility within
Cisco Unified Attendant Console Standard, you must also set up an End User, as described in End
User Account Required For Presence, page 2-9. For more information about SSO, see Starting Cisco
Unified Attendant Console Standard, page 3-2.
3. Install the Cisco Unified Attendant Console Standard software. For instructions, see Installing or
Upgrading Cisco Unified Attendant Console Standard, page 2-9.
– Earlier builds will need the update (KB2919355) applied prior to installing Cisco Unified
Attendant Console
• Windows 10 (Desktop Mode)
For a summary of the operating systems and Cisco Unified Communications Manager versions
compatible with Cisco Unified Attendant Console Standard, see the table on page 2-5.
The following third party applications are required. If they are not installed on the PC prior to executing
the Cisco Unified Attendant Console Standard installer, they will be automatically installed.
• Microsoft Visual C++ 2010 Redistributable
• Microsoft Visual C++ 2015 Redistributable
• Microsoft .NET Framework 4.6.1
Note During the installation of Microsoft Visual C++ 2010 and C++ 2015 Redistributable, the system may
require a reboot. After the reboot, the installation will continue automatically.
Jabber Support
Both standard Jabber installations (locally installed on the operator computer) and VXME installations
(installed in a VXME environment) are supported as operator devices and end points.
Network Requirements
Cisco Unified Attendant Console Standard is a client application within the Cisco Unified
Communications Manager (CUCM) infrastructure, and does not establish any listeners, being only a
consumer of CUCM services. It should be installed on a Microsoft Windows computer that has been
configured according to your company's operating systems hardening guidelines, and with the following
network requirements considered.
The computer running Cisco Unified Attendant Console Standard must provide TCP/IPv4 and must be
able to access the Cisco Unified Communications Manager and the Cisco Unified IM&P Server/Cisco
WebEx Server. By default, these use the following two-way TCP ports:
• Cisco Unified Communications Manager – Port 443
• Cisco Unified IM&P Server – Port 5222
• Cisco WebEx Server - Port 5222
• TSP – Port 2748
If you have a firewall on your computer, you must configure firewall exceptions for these ports or for
any alternatives you may use in your installation.
Note Don’t forget to consider the default dynamic port range appropriate to your computer’s operating system
when defining its firewall settings, as described at https://support.microsoft.com/en-us/kb/832017.
Scalability
Cisco Unified Attendant Console Standard supports up to 5000 contacts on a single instance. You can
associate up to 5000 lines (not phones) with the Application User that connects Cisco Unified Attendant
Console Standard to the Cisco Unified Communications Manager: any more than that and system
performance may become degraded.
Directory Synchronization
Although the recommended maximum Cisco Unified Attendant Console Standard directory size is 5000
contacts, there is no theoretical limit to the number that can be stored. However, if many users (say 500)
with large directories (say 50000 contacts) simultaneously try to synchronize with Cisco Unified
Communications Manager it would struggle to cope.
Note Cisco Unified Communications Manager's User and CTI (TSP client) resources are perfectly adequate
to support this many concurrent Cisco Unified Attendant Console Standard users.
If you do have many concurrent Cisco Unified Attendant Console Standard users who are synchronizing
more than the recommended maximum number of contacts, we recommend that these users:
• Configure Cisco Unified Attendant Console Standard to sync the directory infrequently; for
example, once a day when they launch the application
• Stagger the times at which they synchronize or launch the application.
Presence
Cisco Unified Attendant Console Standard uses its user’s personal Jabber credentials to enable presence
indicators in its directory. So long as hundreds of users are not sharing the same Jabber credentials, the
load on the presence server will be distributed, and there will be no problems with presence.
Note The 32-bit version of TSP is required when running Cisco Unified Attendant Console under a 32-bit
operating system. The 64-bit version of TSP is required when running Cisco Unified Attendant Console
under a 64-bit operating system.
Note If the installation wizard is unable to download the TSP, you can fix the problem by doing the following:
a. In your web browser, under Tools, choose Internet Options.
b. In the dialog box, select the Advanced tab.
c. Under Security, deselect (uncheck) Check for publisher's certificate revocation.
d. Under Security, deselect (uncheck) Check for server certificate revocation
e. Click OK.
The operating system and Cisco Unified Communications Manager (CUCM) version compatibility is
summarized below:
Shared Lines
Shared lines are used when you:
• Have multiple phones but want one phone number
• Share call-handling with co-workers
• Handle calls on behalf of someone else, such as a manager
Shared lines in the user’s controlled phone are supported but with several caveats:
The user will only see full activity against the specific device they're logged into the application against.
Other devices with the same DN will not show calls in the Call Control area. Furthermore, if for example
Device A and Device B both have DN 1000, and a CUACS user logs in using Device A, 1000 will appear
in their call control area. They will accurately see all call control for Device A. Any call activity that
occurs on Device B will not be shown. Finally, call activity on non-user devices with the same DN as the
user’s device will cause changes in the BLF of the user’s line.
Extension Mobility allows users to temporarily use another phone as their own, during which time that
phone adopts the user’s configuration profile.
When logged into an Extension Mobility device, the Extension Mobility DN will be searchable at the
login screen and the device Extension Mobility is logged in will be selectable. If Extension Mobility is
not logged in before the application is started, the Extension Mobility DN will not be selectable
Cisco Unified Attendant Console Standard supports both shared lines and extension mobility, so long as
the device is associated with the Application User. You can associate up to 5000 lines (not phones) with
the Application User; any more than that and you may experience performance degradation.
All contacts sharing the same telephone number display the BLF status of the device that is the primary
line unless none of the contacts is the primary line (for example, if the primary line becomes unregistered
from Cisco Unified Communications Manager), in which case the device names are sorted in ascending
order and the contacts display the BLF status of the next device in this list. If the primary device goes
out of service but is still registered with Cisco Unified Communications Manager, no BLF status is
displayed until the primary device comes back into service.
Note For BLF status to work correctly with shared lines, you must ensure that all user roles described in
Assigning Roles to a User Group or Access Control Group, page 2-7 are assigned.
If you intend to have multiple operators using Cisco Unified Attendant Console Standard to answer calls
into a single destination (for example, an office’s main phone number), rather than relying on Shared
Lines for call distribution you should configure a hunt group (where each operator has a unique directory
number associated with the Line Group) in Cisco Unified Communications Manager, using Hunt Pilot
> Hunt Group > Line Group. This will prevent call control race conditions that could arise when
multiple answer requests for a single call are simultaneously sent to Cisco Unified Communications
Manager, and which could result in one request being fulfilled while the others return call control
failures.
Step 1 Use your internet browser to access Cisco Unified CM Administration, and then log in.
Step 2 In the main menu, choose User Management > User Settings > Access Control Group.
Step 3 Click Add New to create a new Access Control Group.
Step 4 Type a Name for the new Access Control Group.
Step 5 Click Save to save the Access Control Group.
Step 6 Assign roles to the user group, as described in Assigning Roles to a User Group or Access Control
Group, page 2-7.
Step 1 On the Find and List User Groups page, Find the User Group/Access Control Group you just created.
Step 2 In the Search Results, click Roles for the User Group/Access Control Group.
Step 3 Click Assign Role to Group.
The roles that can be assigned are listed.
Step 4 Select the following roles:
• Standard AXL API Access
• Standard CCM Admin Users
• Standard CTI Allow Calling Number Modification
• Standard CTI Allow Call Park Monitoring
• Standard CTI Allow Control of All Devices
• Standard CTI Allow Reception of SRTP Key Material
• Standard CTI Enabled
• Standard Serviceability
Step 5 If you are using phone models 69xx, 7931, 7965, 88xx, 89xx and 99xx, you must also select:
• Standard CTI Allow Control of Phones supporting Connected Xfer and conf
• Standard CTI Allow Control of Phones supporting Rollover Mode
Step 6 Click Add Selected to assign the roles.
Step 7 Click Save.
Step 1 Use your internet browser to access Cisco Unified CM Administration, and then log in.
Step 2 In the main menu, choose User Management > Application User.
Step 3 Click Add New.
Step 4 Enter information in the following fields:
• User ID (a name of your choice)
• Password
• Confirm Password (this must match the Password)
Step 5 Scroll down to the Permissions Information section and click Add to Access Control Group.
Step 6 Click Save to save the Application User.
Step 1 Use your internet browser to access Cisco Unified CM Administration, and then log in.
Step 2 In the main menu, choose User Management > Application User.
Step 3 Find and then select your Application User.
The Application User Configuration page appears.
Step 4 Under Device Information, select the relevant Available Devices and then add them to the Controlled
Devices list. To add many devices you will probably find it easier to click Find more Phones, and then
find, select and Add the devices using the dialog box displayed.
Step 5 Click Save.
Note To be able to install the software you must have administrator rights.
Step 1 Check that your Cisco Unified Communications Manager is compatible with this version of Cisco
Unified Attendant Console Standard, as described in Cisco Unified Communications Manager
Compatibility, page 2-4.
Step 2 Ensure that your Application User has all the required roles assigned, as described in Assigning Roles
to a User Group or Access Control Group, page 2-7.
Step 3 Browse to the installation location and run CUACS_Setup.exe.
The installation wizard appears.
Step 4 In the Welcome page, click Next.
Step 5 In the Cisco Unified Communications Manager Connection Details page, type the following:
• The Cisco Unified Communications Manager Host Name, Fully Qualified Domain Name
(FQDN) or IP address
• The Cisco Unified Communications Manager Application User ID to use
• The Password that corresponds with the Cisco Unified Communications Manager User ID.
and then click Next.
If you are manually upgrading your Cisco Unified Attendant Console Standard software, this page will
contain your current details.
Note During installation the Cisco Unified Communications Manager TSP appropriate to the Cisco Unified
Communications Manager you intend to use is downloaded and installed.
Step 7 In the Language Information page, select the language you want to use, and then click Next.
If you are manually upgrading your Cisco Unified Attendant Console Standard software, this page will
contain your current details.
Step 8 In the Cisco Unified Presence Server Connection Information page, type the following:
• The Server Address or URL required for hosted presence.
• The Domain containing the server
• The Cisco Unified Presence User Name to use
• The Cisco Unified Presence Password appropriate to the User Name
and then click Next.
If you are manually upgrading your Cisco Unified Attendant Console Standard software, this page will
contain your current details.
Step 9 In the Choose Destination Location page, either accept the default folder (recommended) or Browse to
the folder in which to install the application, and then click Next.
Step 10 In the Start Copying Files page, if the details are correct, click Next. If not, click Back and correct the
information.
Cisco Unified Attendant Console Standard is installed.
Step 11 In the InstallShield Wizard Complete page, select Yes, I want to restart my computer now, and then
click Finish.
If you have manually upgraded from one major version to another you will now need to relicense the
application for the new version, following the instructions in the next section.
Step 1 As a local administrator, sign in to each instance of Cisco Unified Attendant Console Standard that you
want to license and activate, and do the following:
a. Choose Help > About Cisco Unified Attendant Console Standard.
An information box appears. If the application is already licensed, its Registration Code is shown in
this box.
b. In the information box, click Register.
c. Note the Machine Code. This is the registration code for that instance.
Tip Keep these codes safe, as you require them to activate the 60 evaluation period and to license purchased
software.
Step 2 Use your internet browser to go the Cisco Unified Attendant Console Downloads and Licensing website.
Step 3 Enter your User Name and Password, and then click Log In.
Step 4 In the navigation bar, click ACTIVATE EVALUATION SOFTWARE.
Step 5 Select your Reseller, then select your Customer, and then select your Customer Site.
Note If your reseller, customer or site are not available, choose the options to add them.
Step 6 Select the Version and the Product that you have installed, and then click Next.
Step 7 Enter the Registration Codes collected in Step 1, and then click Next.
Step 8 Enter any additional email addresses to receive the registration file, and then click Submit.
If the registration codes are valid, a registration (RGF) file is e-mailed to you. The RGF file contains
activation keys and serial numbers for the 60 day evaluation period. The RGF file can hold licensing
information for multiple instances, but each license needs to be individually applied.
Step 9 Open the email and save the RGF file to a location that can be browsed by Cisco Unified Attendant
Console Standard.
Step 10 In Cisco Unified Attendant Console Standard, do one of the following:
• In the main menu, choose Help > About Cisco Unified Attendant Console Standard.
• Use the keyboard shortcut you have defined, as described in Defining and Editing Keyboard
Shortcuts, page 6-2.
Step 11 In the message box, click Register.
Step 12 In the License dialog box, either:
a. Select File Registration.
b. Type the name of or browse to the RGF file.
c. Click Validate.
or – if you know details of the license for the specific instance you are licensing
a. Select Key Registration.
b. Type an activation key Serial Number, which is included with the license in the RGF file.
c. Type the corresponding Registration Code.
d. Click Register.
Note If you have purchased à la carte upgrade licenses, or requested UCSS upgrade licenses through the Cisco
Product Upgrade Tool, you must ensure that the previous version’s 27-digit LACs are activated before
activating the upgrade LACs. If you do not do this the upgrade activation will fail.
If you have an upgrade agreement, you can manually upgrade any Cisco Unified Attendant Console
Department Edition (version 8.x or 9.x) installations to Cisco Unified Attendant Console Standard.
However, you must activate the Cisco Unified Attendant Console Department Edition LACs before you
can activate the upgrade LACs.
When you upgrade using UCSS licenses you can convert Cisco Unified Attendant Console Department
Edition license instances into the same number of Cisco Unified Attendant Console Standard instances.
You can upgrade either:
• All the Cisco Unified Attendant Console Department Edition seats into Cisco Unified Attendant
Console Standard at once.
• Some of the Cisco Unified Attendant Console Department Edition seats and then upgrade the
remainder later.
For example, if you had a Cisco Unified Attendant Console Department Edition LAC with 10 seats, you
can either activate all 10 LAC codes at once to obtain 10 Cisco Unified Attendant Console Standard
licenses, or you can, say, obtain 5 Cisco Unified Attendant Console Standard UCSS Upgrade licenses
today and the remainder later.
Note If you had 10 Cisco Unified Attendant Console Department licenses, and upgraded 5 of these to Cisco
Unified Attendant Console Standard version 10, you can upgrade the 5 remaining licenses to Cisco
Unified Attendant Console Standard version 11 using your old Cisco Unified Attendant Console
Department Registration Code or LAC.
If you have UCSS, you can convert each version 10 license you have to a version 11 license by supplying
either the Registration Code or LAC for that license.
Step 1 Use your internet browser to go the Cisco Unified Attendant Console Downloads and Licensing website.
Step 2 Enter your User Name and Password, and then click Log In.
Step 3 In the navigation bar, click ACTIVATE PURCHASED SOFTWARE.
Step 4 Select your Reseller, then select your Customer, and then select your Customer Site.
Note If your reseller, customer or site are not available, click the control to add them.
Step 5 Select the Version and the Product (CUAC Standard) that you have installed, and then click Next.
Step 6 Enter a unique Registration Code (one of the machine codes collected on page 2-12) and License
Activation Code pair for each instance, and then click Next.
Note Click to create new fields for any additional pairs of codes.
Step 7 If all the License Activation Codes are UCSS codes for Cisco Unified Attendant Console Standard, enter
details of the previously used Cisco Unified Attendant Console Department Edition Registration Code
and License Activation Code pairs that you wish to upgrade to Cisco Unified Attendant Console
Standard.
Step 8 In the License Request Confirmation page, optionally enter an additional e-mail address and click
Submit. If you want to change the codes you entered in Step 6 before proceeding, click Back.
A registration (RGF) file is e-mailed to you, and license request confirmation information is displayed
in the web page.
Step 9 Open the email and save the registration file to a location that can be browsed by Cisco Unified Attendant
Console Standard.
Step 10 In Cisco Unified Attendant Console Standard, do one of the following:
• In the main menu, choose Help > About Cisco Unified Attendant Console Standard.
• Use the keyboard shortcut you have defined, as described in Defining and Editing Keyboard
Shortcuts, page 6-2.
Step 11 In the message box, click Register.
Step 12 In the License dialog box, either:
a. Select File Registration.
b. Type the name of or browse to the RGF file.
c. Click Validate.
or – if you know details of the license for the specific instance you are licensing
a. Select Key Registration.
b. Type an activation key Serial Number, which is included with the license in the RGF file.
c. Type the corresponding Registration Code.
d. Click Register.
Relicensing Software
If you do any of the following you must re-license the software with a new registration code:
• Reinstall the operating system on the same hardware
• Install a different operating system on the same hardware
• Add or remove certain hardware (such as an NIC card)
• Change the machine name
• Perform a major upgrade of the Cisco Unified Attendant Console Standard software
To re-license Cisco Unified Attendant Console Standard, contact Cisco TAC and request a re-host. You
will need to provide them with either the original license activation codes or the SO number of your
purchase.
Cisco Single Sign On (SSO) is a facility to help users who run multiple Cisco Unified Communications
applications in a work session: once a user has signed in to any one of the applications they do not need
to sign in to any of the others.
Note Cisco Unified Attendant Console Standard supports the following single sign-on Identity Providers:
• Microsoft Active Directory Federation Services (ADFS)
• OpenAM
• Ping
How you start Cisco Unified Attendant Console Standard depends on whether your working
environment has SSO configured, and whether you have configured Cisco Unified Attendant Console
Standard to use it. SSO runs for a configurable length of time; if this expires while you are using Cisco
Unified Attendant Console Standard you are prompted to refresh your log in so that you can continue
working.
• For more information about SSO, including how to configure the Cisco Unified Communications
Manager to use it, see the relevant Cisco documentation.
• For more information about configuring Cisco Unified Attendant Console Standard to run in the
SSO environment, see Using Single Sign-on, page 4-3.
If Cisco Unified Attendant Console Standard is configured to use SSO, and if you launch it before any
other Cisco Unified Communications application you are presented with a web page asking for your SSO
End User Username and Password. Once you have entered this information, you will not need to sign in
to any other Cisco Unified Communications application during that work session. If you are working in
an SSO environment, and Cisco Unified Attendant Console Standard is configured to use it, you will not
be able to start it without being authenticated through this web page.
In an SSO environment, the End User accessed through the web page login provides the Presence
information; so an End User does not need to be set up in Cisco Unified Attendant Console Standard.
Outside the SSO environment, Cisco Unified Attendant Console Standard uses the End User credentials
configured under File > Options > Configuration to provide Presence information.
Note If the login details are invalid, a message appears and the application closes. Either try to log in again
using correct SSO details, or contact your network administrator.
The Cisco Unified Attendant Console Standard Sign In screen appears, containing either the number of
the last attendant phone used to sign in, or the text Extension, showing that you need to enter an attendant
phone number.
Step 3 In the Cisco Unified Attendant Console Standard Sign In screen:
To use the number in the field, proceed to Step 4.
To use a new extension number:
a. Type the number into the field. As you type, the application lists those devices available for signing
in that match the number (for more information on defining devices, see Managing Sign In Devices,
page 4-8). The more you type, the shorter the list becomes. The list contains the name and extension
number for each matching device.
Note If the Device List under the File > Options > Device List tab is empty, all devices associated with the
application user are available for signing in to Cisco Unified Attendant Console Standard. For more
information, see Assigning Devices to Application User to Enable Operator Log In and Directory
Contact BLF, page 2-8.
If the Device List contains one or more devices, you can sign in using one of them. If all the devices in
the Device List are invalid, you will be unable to sign in without the assistance of a system administrator,
as described in Accessing Cisco Unified Attendant Console Standard When There Are No Valid Devices,
page 3-4.
b. Select a number in the list by either double-clicking it, or by highlighting it and then pressing Enter.
You can close the list and clear the selection by pressing Esc.
Step 4 If the sign in extension is part of one or more hunt groups, and you want the application to log you into
them during sign in, select Log in to hunt groups at sign in.
Note If the partition of the line used to sign into the console is changed while the console is in use, the user
must sign out and sign back in to the console.
While the application is running, you can change the attendant console operator directory number (DN),
as described in Setting Operator Details, page 4-3.
Step 1 In the Sign In screen invalid extension message, click Administrative Override.
Note The Administrative Override link appears only when there is a Device List containing at least one device.
Signing Out
To sign out from your current attendant console session, do either of the following:
• In the main menu, click the extension number at the top right of the interface, and then select Sign
out of application.
• Use the Ctrl+S keyboard shortcut.
The sign in screen is displayed, and the application continues to run and any synchronization currently
in progress continues. When you sign out you are automatically logged out of any hunt groups to which
you belong.
To resume using the application, sign in as before.
This chapter describes how to configure Cisco Unified Attendant Console Standard.
All the configuration functions are contained within tabbed pages of the Options window, which you
access by choosing File > Options. You can password-protect the following Options tabs:
• Directory Filters
• Directory Mappings
• BLF Rules
• Device List
• Logging
Enabling password protection is described in Preventing Access To Options Tabs, page 4-2; disabling it
is described in Making Options Tabs Accessible, page 4-2.
This chapter also describes the following configuration procedures:
• “Setting Operator Details” on page 4-3
• “Using Single Sign-on” on page 4-3
• “Configuring Presence Server” on page 4-4
• “Connecting to a Different Cisco Unified Communications Manager” on page 4-6
• “Setting the Operator Voicemail Prefix” on page 4-7
• “Configuring Alerts” on page 4-7
• “Managing Sign In Devices” on page 4-8
For details of configuring synchronization with Cisco Unified Communications Manager, see
Configuring Synchronization, page 5-4.
For details of moving, stretching and hiding parts of the interface, see the Cisco Unified Attendant
Console Standard online Help.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note If a Device List is defined (see “Managing Sign In Devices” on page 4-8), the same restrictions as on the
sign in extension apply, but the list is not displayed when you start typing.
To use Cisco Unified Attendant Console Standard with Single Sign On, do the following:
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
To stop using Cisco Unified Attendant Console Standard with SSO, repeat the above procedure but clear
Use Single Sign-On. If you want to display Presence information outside of the SSO environment, you
must define which Presence Server to use, as described in the next section.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note The Presence credentials are stored in the configuration file using AES-256 encryption.
Note Contact User IDs must be formatted as full URIs. Subscription request will pass the unmodified contact
URI to the Presence Server.
Note Cisco Unified Attendant Console Standard will affix the specified domain to unmatched contacts. For
example:
– Configured Domain = cisco.com
– Contact User ID in directory = [email protected]
Subscription request will be made for [email protected]@cisco.com.
– Configured Domain = cisco.com
– Contact User ID in directory = [email protected]
Subscription request will be made for [email protected].
Once Cisco Unified Attendant Console Standard is installed, you can connect to a Cisco Unified
Communications Manager different from the one you specified during installation, and so use a different
source directory. However, the new Cisco Unified Communications Manager must be the same major
revision as the one specified during installation; you cannot upgrade to a later revision using this method.
To connect to a different Cisco Unified Communications Manager, do the following:
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note The Cisco Unified Communications Manager credentials are stored in the configuration file using
AES-256 encryption.
If your operator uses a separate voicemail number, you define its prefix.
To set the operator voicemail prefix, do the following:
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Configuring Alerts
Cisco Unified Attendant Console Standard alerts you when the following events occur (listed in order of
precedence):
1. Call is ended (not by console)
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
While importing sign in devices from a CSV file, the application checks that each device is associated
with the Application/End User configured in the Cisco TSP. If a device is not associated, it is shown as
invalid in the Device List.
If additional lines are later associated with a sign in device (using Cisco Unified Communications
Manager), they get added to the Device List. After these changes, attendants will still be able to sign in
using the old extension.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Note If there are multiple lines on the selected device, all the lines are selected and added to device list.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
You can import sign in devices from a CSV file with the format described in CSV Files for Importing
Sign In Devices, page B-3.
To import devices from a CSV file:
Note If you click View Sample you can view the required format of the CSV file for importing login devices.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
To remove devices:
Note If a device has multiple lines, all are deleted from the list. The device remains in the database.
Cisco Unified Attendant Console Standard displays one or more directories of contacts. Always
displayed is your corporate directory (shown in the interface as Directory), which is copied from one
or more of the following sources:
• Cisco Unified Communications Manager
• A comma-separated-variable (CSV) file. CSV file names have the .csv extension.
Note The CSV file can be on any shared network location to which Cisco Unified Attendant Console Standard
has read and write access. However, it the file does not include a unique identifier (Primary Key) for each
contact, it needs to be on the machine running Cisco Unified Attendant Console Standard.
Cisco Unified Communications Manager is the usual source of your corporate directory. Up to date
contact information is copied from the source into Cisco Unified Attendant Console Standard by the
synchronization process. For a description of this, see Directory Synchronization, page 5-3.
Directory Groups
You can also view and connect to contacts that are not in your synchronized directory but which you
want to be able to select quickly. These directory groups can contain any combination of the following:
• Contacts imported (copied) from sources other than those listed above. These sources are either CSV
files or Extensible Markup Language (XML) files. For more information, see Importing Contacts
Into Directory Groups, page 5-13.
• Contacts you enter yourself. For more information, see Manually Adding Contacts To Directory
Groups, page 5-14.
As well as importing contacts into directory groups, you can also export (copy) directory groups to CSV
files, so that they can be used by other attendants or even in other applications.
Note The format of CSV files imported/exported is different from that of CSV files used for synchronization.
You cannot amend contact records in the corporate directory. By contrast, directory groups are not
updated by synchronization; and you can amend the contact details they contain.
For more information, see “Directory Groups” on page 5-11.
4 5 6 7
9
1
11
8
2 3
10
Legend
1. Cisco Unified Attendant Console Standard.
2. Corporate directory.
3. Directory groups.
4. Cisco Unified Communications Manager.
5. CSV file for synchronization. For details of the format, see CSV File Formats, page B-2.
6. CSV file for importing and exporting. For details of the format, see CSV File Formats, page B-2.
7. XML file.
8. Synchronize contacts. Includes applying Directory Filter, Directory Mapping Rules and BLF rules.
9. Import contacts.
10. Export contacts.
11. Manually entered contact.
Contact Matching
When displaying inbound or outbound calls Cisco Unified Attendant Console Standard displays the
name of the matching contact, which is determined in the following way:
1. If the caller is a manually-created (speed dial) contact in the database, the name from there is
displayed.
2. If the caller is not manually created, but their name is synchronized in the database, that is displayed.
3. If there is no caller name in the database, it is retrieved from Cisco Unified Communications
Manager.
If Unknown Caller is displayed, the caller name has not been found. If Private Caller is displayed, the
caller is blocked.
Directory Synchronization
The process of copying contacts from your source directories into Cisco Unified Attendant Console
Standard is known as synchronization, because the information in the source and internal directories is
identical at the instant of copying. When synchronization occurs, the contacts from both the Cisco
Unified Communications Manager and the CSV file (if you specify one) are copied into Cisco Unified
Attendant Console Standard. The actual data that is displayed in your corporate directory depends not
only on what is in your sources but also on any directory field mappings, directory filters or BLF rules
you have configured.
If synchronization detects that a contact it is copying is already in Cisco Unified Attendant Console
Standard, it first validates the information (checks that it is correct) and then updates Cisco Unified
Attendant Console Standard with any information that has changed since the last synchronization. If a
synchronization fails mid-process – for example, because of a network failure – it starts again from the
beginning.
The synchronization process needs to know what contact data to copy from the source to your corporate
directory, and it gets this information from directory field mappings; for more information, including
how to set the mappings, see Directory Field Mappings, page 5-7.
You can choose to copy only certain contacts to Cisco Unified Attendant Console Standard by applying
a directory filter, this ensures that only those contacts that have the characteristics you specify in a series
of directory rules are added to the corporate directory. For example, you can synchronize the contacts
from only a specific department. For more information, see Directory Filtering, page 5-5.
During synchronization you can modify the first part of your contact telephone numbers, so that the
numbers in your corporate directory differ from those in your source directory. For example, you might
have telephone number stored in Cisco Unified Communications Manager as 01189728567, but in the
corporate directory you want to see it as 8567. You achieve this number conversion by creating BLF
Rules, which are applied during synchronization. For more information, see BLF Rules, page 5-8.
Note • The converted numbers must match the DNs monitored in TAPI, otherwise the line state will not be
displayed in the directories.
• These converted numbers are used by Cisco Unified Attendant Console Standard when it dials. If
you set up BLF rules, you also need to set up translations in Cisco Unified Communications
Manager to convert the numbers in Cisco Unified Attendant Console Standard back to the originals,
so that you can call those numbers.
Directory synchronization takes place at regular intervals that you define, and you can also configure
Cisco Unified Attendant Console Standard to synchronize with the source directory when you start the
application (this is the default situation). Additionally, you can manually start synchronization. For more
information, see Configuring Synchronization, page 5-4.
Configuring Synchronization
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
When you install Cisco Unified Attendant Console Standard, a set of default synchronization parameters
are created, which should work for your installation. However, you can change these parameters to the
values you require. Additionally, if you want to manually synchronize your system after changing its
configuration, use this procedure.
To configure synchronization, do the following:
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Step 5 If you do want to synchronize to a CSV file source, under CSV Detail, Browse to the File Location of
your CSV source, and either type its name or select it, and then click OK.
If you specify a CSV file source, the application synchronizes to both it and any specified Cisco Unified
Communications Manager when you restart the application.
If you do not have a CSV source, click Clear to clear this field.
To view a sample CSV file, click View Sample.
Step 6 Click Apply.
Note • Because all outbound numbers dialed by operators are subject to dial rules, you must ensure that
your Call Parking devices use numbers that do not cause a rule to be applied, otherwise you will be
unable to retrieve calls parked on these extensions.
• Before Application Dial Rules can be processed, CUACS will only pass through dialable characters
(including: *,+, 0-9, #). Any non-dialable characters will be dropped from contact directory numbers
when executing call control actions against them.
Directory Filtering
A directory filter consists of a series of directory rules that are applied during synchronization to ensure
that only certain contacts are copied to the corporate directory.
Each directory rule can compare one of the following contact details to a text string:
• Department
• Telephone
• Location
The rule makes the comparison according to one of the following conditions:
• Begins with
• Contains
• Is exactly
• Ends with
So, for example, you might only want to copy contacts whose Department Is exactly Sales. This would,
however, exclude anyone whose department is Sales America, for example. Or maybe you want to
synchronize those contacts whose Department Ends with ing, which would copy the contacts from both
Marketing and Engineering (and any other department ending in those letters).
Directory filters can consist of any number of directory rules, combined using these logical operators:
• AND
• OR
So, for example, you might have a rule that synchronizes only those contacts whose Department Is
exactly Sales AND their Location Ends with America, so that your corporate directory contains all the
new world sales staff. When you use more than two rules, the AND operator has precedence over OR;
so a rule with the structure X AND Y OR Z is equivalent to (X AND Y) OR Z.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Step 5 In the Options window, select the Configuration tab, and then, under Sync Detail, click Sync Now (this
control is disabled if there is already a synchronization in process). The filter is applied and only those
contacts satisfying the filter are copied to the corporate directory.
Destination Fields
Cisco Unified Attendant Console Standard supports the following contact destination fields:
• Department
• Directory URI
• Email
• First Name
• Home Phone
• Last Name
• Location
• Manager
• Middle Name
• Mobile
• Telephone (automatically mapped from source)
• User Field 1
• User Field 2
Source Fields
By default, Cisco Unified Attendant Console Standard has mappings set up for synchronizing contacts
from Cisco Unified Communications Manager (CUCM) and CSV files. However, you may wish to
change the default mappings, or define your own.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
BLF Rules
BLF rules are applied during synchronization to convert directory numbers to a different format by
searching for and replacing specific number prefixes. You can define sets of multiple rules to be applied
one after the other during synchronization, and you can define different sets of rules for synchronizing
from Cisco Unified Communications Manager and CSV files.
BLF rules are applied in the order they are listed in the BLF rules List. For example, if the first rule
modifies the number from 01189597895 to 8957, the next rule is applied to the modified number. By
moving rules up or down in the list, you change the order in which they are applied.
Note BLF rules will only be applied to contacts synchronized from CUCM, CSV or ALL, but not to imported
or manually added contacts.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note When multiple BLF rules are configured, the output of the first rule will become the input of the second
rule. If you are not satisfied with the final result of your transformed number, you may need to review
individual BLF rules or their order.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
To change the order in which BLF rules are applied during synchronization, do the following:
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Directory Groups
Directory groups contains special contacts – including contacts not in your source directory – that you
want to be able to select quickly. You must create your directory group before adding contacts to it. For
details of how to do this, see Creating Directory Groups, page 5-12.
You add contacts to directory groups by either of the following methods:
• Importing contacts from CSV files or XML files, as described in Importing Contacts Into Directory
Groups, page 5-13.
• Manually creating contacts, see Manually Adding Contacts To Directory Groups, page 5-14.
You can amend the name of a directory group, and the details of any contact in the group. You can also
export the contacts from directory groups to CSV files,
or
Step 1 Select the directory group, and then do one of the following:
• In the main menu, choose Edit > Delete directory group.
• Use the keyboard shortcut you have defined, as described in Defining and Editing Keyboard
Shortcuts, page 6-2.
or
• When you import from these types of file, no checks are made to see if the contact information is
duplicated in any directory group, including the one that you are importing the data into.
• The format of CSV files imported/exported is different from that of CSV files used for
synchronization.
At the start of the import process Cisco Unified Attendant Console Standard validates the file structure
and format. If either is incorrect, you are alerted to the fact and the process is aborted.
You can only import contacts into an existing directory group – either one that already contains contacts,
or a new one created especially for the purpose. See Creating Directory Groups, page 5-12.
To import contacts into a directory group, do one of the following:
Note You cannot type a file name or edit the name of a selected file.
Alternatively, you can drag (copy) contacts from the corporate directory or another directory group, and
then drop them into the target directory group.
Note • This creates a duplicate contact in the directory group. Take care not to create multiple duplicates.
• When editing contact properties or adding/editing a note, the changes will only occur for the
directory group contact against which you make the changes. That is, the changes will not copy from
the duplicate to the original or the other way around.
Note You can edit any fields in manually-added contacts, but you can only edit unmapped fields in contacts
that have been synchronized into the corporate directory; the edited data is retained when the contact is
synchronized. Should the field become mapped, the edited contact data in the corporate directory will
be overwritten during synchronization with the data mapped from the Call Manager.
Note You can edit the data in the white fields, but not in the shaded fields.
or
a. In the main menu, choose File > Options.
b. In the Options window, click the Import/Export tab.
or
• Right-click in any directory group, and then select Export Contacts.
or
• Use the keyboard shortcut you have defined, as described in Defining and Editing Keyboard
Shortcuts, page 6-2.
Step 2 Then do the following:
a. In File Name, click Browse and navigate to the target folder.
b. Either type a file name (to create a new CSV file) or select an existing file to export to. If you select
an existing file you are prompted to overwrite it; click Yes to overwrite the file.
Note The format of CSV files imported/exported is different from that of CSV files used for synchronization.
Legend
1. Search – type details of the contact to search for.
2. Search Preferences – define which contact information to search.
3. Directory tabs – select the directory to display. Includes both corporate directory and directory
groups. Drag the tabs to change their order, as described in Changing the Directory Tab Order,
page 5-18.
4. Create a new directory group.
5. Column headings – identify the data and enable you to change what columns are displayed, the
column order, and the contact sort order. These are described below.
6. Phone state – the state of the contact’s phone, such as Ringing, On hook, and Do not disturb.
Note If a contact DN includes spaces (for example, +44 123 456), the phone line state will not be
shown. However, a call can be made to this contact successfully.
7. Presence state – this mimics a Jabber or CUPC client, where a symbol indicates the real-time status
of the contact, such as Available, Do not disturb, and Away. All other contacts have their
subscriptions opened only when displayed in the Directory pane.
The following information can be displayed for each contact (columns displayed by default are shown
in bold):
• Last Name - always displayed
• First Name
• Telephone - always displayed
• Department
• Notes
• Middle Name
• Email
• Directory URI
• Mobile
• Home Phone
• Manager
• User Field 1
• User Field 2
• Location
How to change what columns of information are displayed is described Changing the Directory View,
page 5-19.
If the contact was imported or manually entered into Cisco Unified Attendant Console Standard you can
also edit the contact information.
The positions of the tabs are stored when you log out or exit the application, and the tabs are displayed
in the saved order when you next use it.
Note You can also change the order of the columns in the Directory pane by using your mouse to select
a column heading; you can then drag it to another place in the table.
The small arrowheads in the column heading row show the direction in which the column is sorted: an
up-arrow for ascending (normal alphanumeric) order, a down-arrow for descending (reverse) order, and
both arrows for default order. Repeatedly clicking the column heading toggles through these sort modes.
The sort column and sort order are remembered by the application when you log off or exit, and are
re-applied when you log in again.
Search Preferences
The Search Preferences enable you control which fields are searched and which contacts are displayed.
You can choose from one to five Searchable Fields from the following Available Fields (default
searchable fields shown in bold):
• First Name
• Last Name
• Telephone Number
• Department
• Email
• Middle Name
• Directory URI
• Mobile
• Note
• Home Phone
• Manager
• User Field 1
• User Field 2
• Location
Use the Left-arrow and Right-arrow buttons to move the field selected in either list to the other.
You can also limit which contacts are displayed in the search results using these Filters:
• Has Telephone – Display only those contacts with a telephone number assigned. All other contacts
are filtered out (excluded) from the search results.
• Has Emails – Display only those contacts with an email address assigned. All other contacts are
filtered out (excluded) from the search results.
Contact Notes
You can add notes to any contact record in the main directory, the search results, or any directory group.
The notes are text containing additional information about the contact. Notes are stored in the database
and are available whenever you sign in. If you delete a contact - for example by applying BLF rules -
any contact notes are also deleted. If you export a contact, their notes are also exported, and if you import
a contact with notes, they are visible in the application.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Note You must enter some text for you to be able to save it. When adding/editing a note, the changes will only
occur for the directory group contact against which you make the changes. That is, the changes will not
copy from the duplicate to the original or the other way around
Step 3 The notes are deleted from the contact Notes column.
Keyboard shortcuts enable you to quickly do things in the interface without needing to use the mouse or
menus.
The application comes configured with the following keyboard shortcuts.
Action Shortcut
Dial Ctrl+D
Answer Ctrl+A
End Call Ctrl+H
Hold Call Ctrl+L
Transfer Call (Blind transfer) Ctrl+X
Consult Transfer (speak to destination before transfer) Ctrl+T
Direct Transfer Ctrl+R
Join Call Ctrl+J
Park Call Ctrl+P
Start Conference Ctrl+N
Transfer to Voicemail Ctrl+O
Sign out of application Ctrl+S
Login/ Logout of Hunt Groups Ctrl+I
Open Help F1
Outbound Dialing Override Ctrl+Enter
Note You cannot use the same keyboard shortcut for more than one action.
Step 1 Access the Keyboard Shortcuts page, as described in Defining and Editing Keyboard Shortcuts,
page 6-2.
Step 2 Select the action from which to remove the keyboard shortcut.
Step 3 Click Clear Shortcut.
Step 4 Click Apply.
Step 1 Access the Keyboard Shortcuts page, as described in Defining and Editing Keyboard Shortcuts,
page 6-2.
Step 2 Do one of the following, as appropriate:
To reset all keyboard shortcuts to their default values, click Reset All Shortcuts to Default.
To reset a single keyboard shortcut to its default value:
a. Select the action to reset.
b. Click Reset Shortcut.
Step 3 Click Apply.
Note Access to the functions described in this section may be restricted by your system administrator, and you
may need a password to access the necessary Options tab. For more information, see Preventing Access
To Options Tabs, page 4-2.
Cisco Unified Attendant Console Standard can keep a log of all event that occur within the application.
This information can be used to gauge the application’s configuration and performance, and to help
troubleshoot any errors. You can control which application subsystems are monitored, which events are
logged, and the size and number of the log files.
Note You can configure a keyboard shortcut to do this. For instructions, see Chapter 6, “Keyboard Shortcuts”.
Configuring Logging
From the Options > Logging tab, adjust the following values as required:
• Number of Files: Type the maximum number of log files to be retained. Once the threshold is met,
the application will begin overwriting the log files starting with the oldest.
• The default value is 10.
• Max File Size (In MBs): Type the maximum file size, in MBs. Once the threshold is met, the log
file will close, and a new log file is opened.
• The default value is 20.
• Logging Level: Select the logging level that fits your logging needs.
• Debug is the most verbose, with each subsequent level moving down in verbosity until Fatal,
which is the least verbose.
• Logging Level - Custom, allows you to set a different logging level for the individual modules
of the application. Each line in the application log files notes the module it belongs to (for
example, a line marked ViewModel would be affected by the ViewModel module setting). A
custom level of logging is not suitable for general use.
• The default and recommended value is Debug.
Log Collection
Step 1 From the Options > Logging tab, select Collect Logs.
Step 2 You are prompted to browse to a folder, where the application logs can be saved to. After making your
selection, click OK.
• The Windows User account must have write-permissions to the specified folder.
Step 3 Once the log collection completes an alert indicating the success of the compressed log file creation and
the file path will appear. Click OK to dismiss the alert.
• The output will be stored in a .zip file containing all of the log files and a log configuration file.
Cisco Unified Attendant Console Standard can handle contact directory files in the following formats:
• XML File Format, page B-1
• CSV File Formats, page B-2
It can also import login devices from CSV files, with the format described in CSV Files for Importing
Sign In Devices, page B-3.
Tags
• <SpeedDialUsers> = the file contains XML data for import into Cisco Unified Attendant Console
Standard.
• <G> = Directory group name
• <E> = Individual contact
• <N> = Name
• <T> = Telephone number
• <M> = Email address
For example:
# * Copyright (c) 2017 by Cisco Inc.
# * All rights reserved.
#
# Here is a sample corporate directory file. It should contain
# comma separated entries, one line per user in the directory
# The values should in the following format:
#
# Last Name, First Name, Telephone number, Department, User Field 1, User Field 2, Site,
Building, Directory URI
#
# Empty values are legal (no department etc.)
#
# Lines starting with '#' or ';' are treated as comments
# and ignored. Empty or blank lines are ignored as well
Kathirine,Jim,25421,Marketing,,,,,[email protected]
Martha,Bryan,87952,Support,,,,,[email protected]
Luce,Richard,2548,Marketing,,,,,[email protected]
Meriall,Thomas,8763,Marketing,,,,,[email protected]
Harye,Walter,5563,Marketing,,,,,[email protected]
For example:
# * Copyright (c) 2017 by Cisco Inc.
# * All rights reserved.
#
# Here is a sample import file. It should contain
# comma separated entries, one line per user in the directory
# The values should be in the following format:
#
# Last Name, First Name, Telephone Number, Note, Group Name, Email, Directory URI, Middle Name, Mobile,
Home Phone, Site, Department, Manager, User Field 1, User Field 2
#
# Empty values are legal (no email etc.)
#
# If a Group Name is specified in the CSV file, it will take precedence over the Directory Group
selected at the Import screen.
#
# Lines starting with '#' or ';' are treated as comments
# and ignored. Empty or blank lines are ignored as well
For example:
# * Copyright (c) 2017 by Cisco Inc.
# * All rights reserved.
#
# Here is a sample device list file. It should contain
# comma separated entries, one line per device in the device list.
# The values should in the following format:
#
# DeviceName,Extension,LineNumber
#
# Empty values are not allowed (no DeviceName etc.)
#
# Lines starting with '#' or ';' are treated as comments
SEP2893FE130280,5868,1
SEP2893FEA2D22A,5873,1
SEP000C299DA714,5870,1
SEP88AE1DB0F66C,5869,1
SEP00141C48DDD9,5859,1
SEP00141C48DDD9,5870,2
Note Any devices in the file that lack one or more of the fields Device name, Extension, or Line number are
considered non-Cisco devices and will not be imported.
‡ If Log in to hunt groups at sign in is selected, the Cisco Unified Communications Manager resets
this phone type when the user logs in to the Cisco Unified Attendant Console Standard client.
This appendix describes notable problems with Cisco Unified Attendant Console Standard and their
solutions. It describes the following:
CUCM Upgrade Version Must Match Installed Version.
Reason
There has been a major Cisco Unified Communications Manager (CUCM) upgrade since Cisco Unified
Attendant Console Standard was installed.
Solution
Cisco Unified Attendant Console Standard can be configured to pass all AXL communications through
a Unified Communications Manager TFTP server (not running the CCM service), while sending all TAPI
communications to a node running the CCM service. This should only be a consideration for users that
wish to disable Tomcat services on their CTI managers.
setting 5-8
I
directory filters 5-3, 5-5
creating 5-6 import/export file formats B-1 to B-4
directory groups 5-11 to 5-17 importing contacts 5-1, 5-13
adding contacts manually 5-14 installing Cisco Unified Attendant Console
Standard 2-1 to 2-15
creating 5-12
interface, description 1-2
deleting 5-12
introduction to Cisco Unified Attendant Console
deleting contacts 5-15
Standard 1-1 to 1-3
exporting contacts 5-16
importing contacts 5-13
renaming 5-12 J
Directory pane 1-3
Jabber support 2-2
directory tabs 5-17
reordering 5-18
K
licensing 2-11
H
N
hardware requirements 2-1
network requirements 2-2
Help, accessing 1-3
hunt group login 3-3, 3-5
O
pane T
Call Control 1-2
troubleshooting D-1, E-1 to ??
Call History 1-3
TSP installation 2-10
Directory 1-3
Parked Calls 1-3
Parked Calls pane 1-3
U
phones supported C-1 to C-3
phone state, directory display 5-17 upgrading the software 2-9
R W
S X