Staying Connected with the Cisco UCS

While the Cisco Unified Communications Manager (CUCM) is at the heart of Cisco’s UC design, there are many additional components that greatly increase the organization’s capabilities to stay connected.

For example, a few of these additional server-based resources include:

Cisco Unified Presence

This feature-rich UC component uses standards-based protocols such as the Session Initiation Protocol (SIP) and the Jabber Extensible Communications Platform (XCP) to work with a range of native and third-party client ap­plications. Users are able to initiate such activities as instant messaging, presence, click to call, phone control, voice, video, visual voicemail, and web collaboration.

Cisco Unity Connection

Cisco Unity Connection is a Linux-based appliance that provides a robust unified messaging platform for Cisco’s Unified Communications suite of products. This product allows the user to access and manage voice messages in a variety of ways, using his/her email inbox, web browser, Cisco Unified IP Phone, smartphone, Cisco Unified Personal Communicator, etc.

Cisco Unified Contact Center

This powerful set of products comes in two variations:

  1. Enterprise — Delivers intelligent contact routing, call treatment, network-to-desktop computer telephony integration (CTI), and multichannel contact management for large-scale enterprise deployments
  2. Express — Designed for midmarket, enterprise branch, or corporate departments requiring a sophisti­cated customer interaction management solution for up to 400 agents

Cisco’s UC products evolved over the years from Windows applications installed on Microsoft Server plat­forms to predominantly appliance-based solutions installed on Linux platforms. The included system, network, and user features increased steadily with each release, but the most dramatic improvements can be seen in the most recent version of the Cisco UC, currently in version 8.x.

UC on UCS Requirements

Cisco supports virtualizing your Unified Communications solutions on the UCS system, according to these require­ments/considerations:

  1. Cisco UC applications supported in a virtual environment include:
    1. Unified Communications Manager 8.0(2)
    2. Unified Contact Manager Express 8.0(2)
    3. Cisco Unified Presence 8.0(1)
    4. Cisco Unity 7.0(2)
    5. Cisco Unity Connection 8.0(2)
  2. The only hypervisor supported initially is VMware vSphere ESXi version 4.x which includes more of the real-time enhancements required for UC than ESX.
  3. Bare-metal/physical/non-virtualized installs are not supported.
  4. Dedicated CPU/RAM/Storage is required for the VMs, oversubscription is not yet supported.
  5. VMware supported SAN storage is required.
  6. 1-4 Cisco Unified Communications Manager (CUCM) Virtual Machines per server, dependent on the model, with MCS 7845 parity per VM (7,500 users).
  7. Application co-residency is not yet supported – the ultimate goal is “mix and match.”
  8. Only “Basic” features supported (e.g., copy VM, restart VM, HA, SRM), “Advanced” features are deferred to future versions (e.g., vMotion, snapshots, DRM, templates, DPM, etc.) .
  9. The hardware BIOS, firmware, and drivers are managed by UCS and VMware, not by CUCM.
  10. The boot order is controlled by the VMware virtual machine’s BIOS instead of by the CUCM Application.

Related Courses
CIPT1v8.0 – Cisco IP Telephony part 1
CVOICEv8.0 – Implementing Cisco Unified Communications Voice over IP and QoS
CAPPSv8.0 – Integrating Cisco Unified Communications Applications

Excerpted from GlobalKnowledge.com

 

In this article

Join the Conversation

2 comments

  1. Shawn Reply

    Good article, but I have noticed that many white papers either have incorrect information or typos…this one has a typo you may want to fix.

    3. Bare-mental/physical/non-virtualized installs are not supported.

    What is a “Bare-mental” install? Should it not be “Bare-metal”?

    Thanks.

    Shawn

  2. Elizabeth Rainwater Reply

    Shawn- Thanks for catching that! I corrected it above.