CCNA Voice 640-461 Cert Guide

1. CHAPTER 8 Administrator and End-User Interfaces CCNA Voice 640-461 Cert Guide

2. CUCM Cisco Unified Communications Manager GUI and CLI: • Must use HTTPS (or Secure Shell [SSH]) for the command line. • Cisco Unified Communications Manager Administration available through (https://<node_ip>/ccmadmin) • Cisco Unified Serviceability available through (https://<node_ip>/ccmservice) • Disaster Recovery System available through (https://<node_ip>/drf)

3. CUCM Cisco Unified Communications Manager GUI and CLI: • Cisco Unified Operating System Administration available through (https://<node_ip>/cmplatform) • Cisco Unified Reporting available through (https://<node_ip>/cucreports) • Command-Line Interface • All can be accessed through the navigation pull-down

4. Cisco Unified Communications Manager Interface: • System menu: Includes tasks for the configuration of CM groups, Presence groups, Device Mobility Groups, Device Pools, Regions, Locations, Enterprise and Service Parameters, Survivable Remote Site Telephony (SRST), and others. • Call Routing menu: Includes tasks to define the call routing system, Call Hunting, Class of Control, Intercom, and features such as Call Park, Call Pickup, and many more. • Media Resources menu: Under this menu, resources such as Music On Hold (MOH), annunciator, media termination points, and transcoders can be defined and hold-music files managed. • Advanced Features menu: Under this menu, VoiceMail integrations, Inter-company Media Engine Configuration, Extension Mobility Cross-Cluster, and VPN features are configured.

5. Cisco Unified Communications Manager Interface: • Device menu: Provides configuration pages for gateways, gatekeepers, trunks, IP phones, and Remote Destinations, plus many device settings, including phone button and softkey templates. • Application menu: Accesses the CUCM Assistant Configuration Wizard and the Plug-ins menu. • User Management menu: Accesses the Application User, End User, Group, and Role configuration pages. • Bulk Administration menu: Provides many options to perform repetitive configuration tasks (such as adding many users or phones) in an automated way. There are many additional and powerful capabilities of the BAT tool not listed here. • Help menu: Provides access to the local searchable help files, the This Page help, and the About information page.

6. Cisco Unified Communications Manager Interface:

7. Cisco Unified Serviceability Administration Interface: • Alarm menu: Provides Configuration and Definition options for alarms to monitor system performance and health. • Trace menu: Provides the Configuration and Troubleshooting Trace Settings submenus, which monitor the system and troubleshoot.

8. Cisco Unified Serviceability Administration Interface: • Tools menu: Under this menu, the CDR Analysis and Reporting submenu provides an interface to gather call logs and report on calls made using the system. The Service Activation screen provides the interface to activate installed services for the first time (or deactivate them later). There are two Service Control Centers: Network and Feature (see the following Note). Using this interface, administrators can stop, start, or restart activated services. The Serviceability Reports Archive provides access to the reporting interface for system and trend analysis. The CDR Management interface allows administrators to configure and check Call Detail Record (CDR) storage disk utilization. The Audit Log Configuration page provides settings for what will be included in audit logs. • SNMP menu: The submenus (V1/V2c, V3, and SystemGroup) control Simple Network Management Protocol (SNMP) connectivity and authentication to network management applications.

9. Cisco Unified Serviceability Administration Interface: • Help menu: Provides access to the searchable Contents help, This Page help, and About information.

10. Cisco Unified Serviceability Administration Interface:

11. Cisco Unified Serviceability Administration Interface: • Monitor hardware-resource utilization (CPU, disk space) • Check and upgrade software versions • Verify and change IP address information • Manage Network Time Protocol (NTP) server IP addresses • Manage server security including IPSec and digital certificates • Create a TAC remote assistance account • Ping other IP devices

12. Cisco Unified Serviceability Administration Interface:

13. Disaster Recovery System Interface: • The Disaster Recovery System (DRS) provides a backup (with scheduler) and restore capability. Access to this interface uses the Platform Administration account defined at install (as does the OS Admin interface). Additional accounts can be created for access by other individuals.Backups can be written to a local DLT tape drive or to an SFTP server. A scheduler is provided for automated backups, or an immediate start to the backup can be selected. Individual server or full cluster backups may be performed.

14. Cisco Unified Reporting Interface: • The Cisco Unified Reporting interface provides a simplified method to access system reports. These reports gather information from existing logs and format the data into simple, useful, one-click reports. Data is collected from logs across the cluster (Publisher and Subscribers) to provide summarized information and highlight issues or irregularities that might impact operation of the cluster. The interface also warns if running a particular report could adversely impact server operation and affect performance or take excessive time.

15. CLI: • The CLI is typically accessed using SSH, although it is possible to directly connect a keyboard and monitor. Initially, the only account that can log on using the CLI is the Platform Administration account defined during install, although additional accounts can be created to allow access. • Partial List of Commands: • Shut down or restart the system • Change versions after an upgrade • Start, stop, and restart services • Modify network settings (IP Address, mask, gateway, and so on) • Use network tools such as ping, traceroute, and packet capture • Use the DRS (backup and restore) • Add and modify Platform Administration accounts • Display server load and process information • Check server status, including software versions, CPU, memory and disk utilization, hardware platform, and serial numbers, and so on

16. User Management in CUCM (Roles and Groups): • The CUCM application defines a consistent and simple method of assigning (and limiting) administrative privilege to users. Users are assigned to groups; Groups are assigned Roles; Roles define privileges to applications. The following sections provide some detail on this structure. • Roles define a set of privileges to the resources in an application. Resources may be a CUCM administration web page, a report tool, or a feature section within a CUCM web page.

17. User Management in CUCM (Roles and Groups): • Privilege: • No Access: The role denies access to the resource; for example, a web page will not load, and an error appears instead. • Read: The role allows the resource to be displayed but not edited: for example, a web page may load, but none of the fields or settings can be modified. Buttons such as Add, Insert, Delete, or Update do not appear. • Update: The role allows full access to the resource, including editing and modification (and deletion where applicable). • 39 Standard roles are defined in CUCM 8.0

18. User Management in CUCM (Roles and Groups): • Custom roles can be defined in addition • CUCM Administration • CUCM Serviceability • Cisco Computer Telephone Interface (CTI) • CUCM Administrative XML (AXL) database

19. User Management in CUCM (Roles and Groups):

20. User Management in CUCM (Roles and Groups): • The privileges defined by the Role are inherited by the user account by way of their membership in the Group.As with Roles, it is likely that the administrative requirements in most scenarios will be met by using the Standard Groups and Role associations. If this is not the case, custom Groups can be created and associated with Standard or Custom Roles to exactly meet administrative

21. User Management in CUCM (Roles and Groups):

22. CUC Cisco Unity Connection GUI and CLI: • CUC provides for six administrative interfaces: • Cisco Unity Connection Administration (https://<ip-address>/cuadmin) • Cisco Unified Serviceability (https://<ip-address>/ccmservice) • Cisco Unity Connection Serviceability (https://<ip-address>/cuservice) • Cisco Unified Operating System Administration (https://<ip-address>/cmplatform) • Disaster Recovery System (https://<ip-address>/drf) • Command-Line Interface

23. Cisco Unity Connection Administration: • Users: Provides access to the local user database to create or edit users. User import and synchronization menu options are also listed here. • Class of Service: Defines the features available to the user, including Licensed and Advanced features, and may apply other user interaction limits. Class of Service is a flexible and powerful method of controlling users’ interaction with CUC, particularly for licensed features. There is no limit to the number of Classes of Service that can be created, making it possible to build a diverse and specific range of Classes of Service to cover any combination of requirements.

24. Cisco Unity Connection Administration: • Templates: Provide a way to define common settings for Users, Contacts, or Call Handlers. When creating a new one of these three types of object, selecting the appropriate template applies all but the individually specific information for each object, making the process faster and more accurate. • Contacts: A System Contact is an account that provides interaction with CUC without an associated mailbox. Perhaps a consultant works in a customer office and interacts with customer team members on a daily basis, but has a mailbox on the system at his consulting firm’s corporate office. A System Contact can provide a directory entry for CUC users to send messages to, with the messages being relayed to the consultant’s mailbox at the corporate office.

25. Cisco Unity Connection Administration: • Distribution Lists: Allow one message to be delivered to multiple users. As many distribution lists as needed can be created. A Class of Service setting can prevent users from sending to System Distribution Lists. • Call Management: Defines Call Handlers. Call Handlers are the foundation structures of CUC and can be configured to answer calls, play greetings, route calls, and take messages. Specialized call handlers include Directory Handlers, which allow a caller to search the directory and either call or leave a message for the selected user, and Interview Handlers, which interact with caller by playing a series of recorded questions, then collecting the answers in a single message. • Message Storage: Allows mailbox quotas to be set, enforcing limits on mailbox size to prevent running out of disk space.

26. Cisco Unity Connection Administration: • Networking: Configures multiple CUC systems in either a Digital Networking or VPIM environment. • Dial-Plan: Provides for the creation of additional Partitions and Search Spaces to control visibility and access to messaging components. It is useful to “hide” part of the CUC system from certain users or functions.

27. Cisco Unity Connection Administration: • System Settings: The System Settings submenus provide global configuration settings. Some of the submenus are summarized here: • Licenses: Tracks and displays the licenses available to the system. Licenses are tied to the MAC address of the NIC on the server. • Holiday Schedules: The three system schedules (All Hours, Weekdays, and Voice Recognition Update Schedule) can be modified but not deleted; new schedules can be added to customize the system. • External Services: CUC can be configured to access user calendar and contact information held by Microsoft Exchange. This information can then be incorporated into Personal Call Routing Rules. Likewise, if Cisco Unified MeetingPlace is available in the network, CUC can pull conference information from the server so users can view and join meetings from their Personal Communications Assistant or from the phone. • LDAP: The submenus allow the configuration of LDAP Synchronization (User import) and LDAP Authentication (redirection of password authentication to LDAP).

28. Cisco Unity Connection Administration: • System Settings: The System Settings submenus provide global configuration settings. Some of the submenus are summarized here: • SMTP: CUC can notify users of new messages via e-mail; the submenus configure details for the integral SMTP server. • Advanced: Several configuration submenus are found under the Advanced submenu, including the SMPP entry, in which CUC can be configured to send Short Message Peer to Peer/Short Message Service text message notifications to mobile phones. • Telephony Integrations: Lists and configures the phone systems with which CUC is integrated, port groups and ports. • Tools: Includes the Bulk Administration Interface and the Task Management (automated maintenance and troubleshooting) system.

29. Cisco Unity Connection Administration:

30. Cisco Unity Connection Serviceability: • CUC provides an additional application called Cisco Unity Connection Serviceability, which despite the similar name provides a very different functionality. • CUC Serviceability is primarily a troubleshooting tool, with tools to define alarms, traces and logs, plus service controls (Activate/Deactivate, Start/Stop/Restart) for CUC-specific feature services.

31. Cisco Unified Presence Server (CUPS): • Cisco Unified Presence Server (CUPS) provides five administrative interfaces: • Cisco Unified Presence Administration (https://<ip-address>/cupadmin) • Cisco Unified Serviceability (https://<ip-address>/ccmservice) • Cisco Unified Operating System Administration (https://<ip-address>/cmplatform) • Disaster Recovery System (https://<ip-address>/drf) • Command-Line Interface

32. Cisco Unified Presence Administration Interface: • System: Provides integration configuration for CUCM, definition of inbound and outbound Access Control Lists, and Licensing status and management. • Presence: Provides definition of gateways providing Presence information from CUCM or calendar integration with Microsoft Outlook. Interdomain federation across different presence domains using Session Initiation Protocol (SIP) or Extensible Messaging and Presence Protocol (XMPP) can be configured. SIP is commonly used with Microsoft Office Communications Server (OCS), while XMPP is typically used with Google Talk. • Messaging: CUPS can be used with external databases (PostgreSQL compliant) or third-party servers to enable IM retention regulatory compliance (Persistent messaging).

33. Cisco Unified Presence Administration Interface: • Application: CUPS applications, such as Desk Phone Control and IP Phone Messenger, are configured here. • User Management: Follows a Groups-and-Roles structure similar to CUCM. User accounts can be imported and synchronized from CUCM. • Bulk Administration: A similar interface to CUCM provides bulk configuration of repetitive tasks, with scheduler capability. • Diagnostics: Accesses system status and troubleshooting tools, plus a System Dashboard for quick review of system configurations.

34. Cisco Unified Presence Serviceability: • Similar to the CUC Serviceability interface • Alarms and events monitoring for troubleshooting purposes • Access to CUPS service trace logs • Monitor real-time CUPS component behavior via CUCM RTMT • Feature Service activation, deactivation, and control; Network Service control • Reports archive • SNMP configuration • Disk usage monitoring for log partition on local and cluster servers

35. End of Chapter 8