The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Once the network, call routing, and call control infrastructure has been put in place for your Cisco Unified Communications and Collaboration System, additional applications and services can be added or layered on top of that infrastructure. There are numerous applications and services that can be deployed on an existing Cisco Unified Communications and Collaboration infrastructure, and the following applications and services are typically deployed:
The chapters in this part of the SRND cover the applications and services mentioned above. Each chapter provides an introduction to the application or service, followed by discussions surrounding architecture, high availability, capacity planning, and design considerations. The chapters focus on design-related aspects of the applications and services rather than product-specific support and configuration information, which is covered in the related product documentation.
This part of the SRND includes the following chapters:
This chapter covers Cisco Unified Communications Manager (Unified CM) applications, which provide numerous operational and functional enhancements to basic IP telephony. External eXtensible Markup Language (XML) productivity applications or IP Phone Services can run on the web server and/or client on most Cisco Unified IP Phones. This chapter also discusses a number of Unified CM integrated applications that provide additional functionality, such as Cisco Extension Mobility, Cisco Unified Communications Manager Assistant, and Cisco WebDialer.
This chapter examines voice messaging, a common and prevalent application within most Unified Communications and Collaboration deployments, which allows callers to send messages and allows subscribers of the system to retrieve messages. The chapter examines messaging deployment models, voice messaging features and functionality, voicemail networking, and design and deployment best practices for voice messaging applications.
This chapter discusses presence services, an increasingly critical piece of most Unified Communications and Collaboration deployments due to the productivity improvements that can be realized from user availability-based applications. This chapter defines presence and explores the various presence components and features, protocols, deployment models, redundancy, capacity, and general design guidelines.
This chapter looks at mobility applications, which are becoming extremely important given the growth of mobile work forces and the blurring of enterprise boundaries for Unified Communications and Collaboration features and services, resulting in an increased demand for mobility applications and services. This chapter discusses mobility solution architectures, functionality, and design and deployment considerations.
This chapter covers contact center solutions, an important and integral part of large Unified Communications and Collaboration deployments that require high-volume call center applications. This chapter examines call center solution architectures, functionality, and design and deployment implications.
This chapter provides an overview of various call recording and monitoring solutions available for Cisco Unified Communications and Collaboration systems for both audio and video calls. The chapter also outlines basic design considerations for call recording and monitoring solutions embedded within a Cisco Unified Communications and Collaboration solution.
As with other network and application technology systems, Unified Communications and Collaboration applications and services must be layered on top of the underlying network and system infrastructures. Unified Communications and Collaboration applications and services such as voice messaging, rich media conferencing, presence, mobility, contact center, and call recording rely on the underlying Unified Communications and Collaboration call routing and call control infrastructure and network infrastructure for everything from network connectivity to basic Unified Communications and Collaboration functions such as call control, supplementary services, dial plan, bandwidth management, and gateway services. For example, voice messaging and presence applications leverage the network infrastructure to reach users in campus sites, in branch sites, and on the Internet. Further, these same applications depend on the Unified Communications and Collaboration voice and video endpoints, call routing, PSTN connectivity, and media resources provided by the call routing and control infrastructure. In addition to relying on these infrastructure layers and basic Unified Communications and Collaboration services, applications and services are also often dependent upon each other for full functionality.
As with network, call routing, and call control infrastructures, critical Unified Communications and Collaboration applications and services should be made highly available to ensure that required features and functionality remain available if failures occur in the network or applications. It is important to understand the various types of failures that can occur and the design considerations around those failures. In some cases, the failure of a single server or feature can impact multiple services because many Unified Communications and Collaboration applications are dependent on other applications or services. For example, while the various application service components of a contact center deployment might be functioning properly, the loss of all call control servers would effectively render the contact center unusable because the deployment is dependent upon the call control servers to route calls to the call center applications.
For applications and services such as voice messaging and mobile collaboration, high availability considerations include temporary loss of functionality due to network connectivity or application server failures resulting in the inability of callers to leave messages, of users to retrieve messages, and of users to schedule or attend conferences. In addition, failover considerations for callers and users of voice messaging and mobile collaboration applications include scenarios in which portions of the functionality can be handled by a redundant resource that allows end users to continue to access services in the event of certain failures.
High availability considerations are also a concern for services such as presence and mobility. Interrupted network connectivity or server failures will typically result in reduced functionality or, in some case, complete loss of functionality. For presence services, this can mean that some or all devices and clients will be unable to send or receive presence or availability updates. For mobility services, high availability considerations include the potential for loss of specific functionality such as two-stage dialing or dial-via-office, or reduced functionality for features such as single number reach (resulting in situations where only the enterprise phone rings or only the mobile phone rings). Further, in some failure scenarios, enterprise endpoints and mobile clients might have to re-register, re-connect, and/or re-authenticate before full functionality is available again.
For contact center deployments, there are numerous servers and components for which high availability must be considered. Typically, an isolated single-server or single-component failure can be handled without loss of features or functionality as long as the server or component has been made redundant. In other situations, loss of multiple servers or components will typically result in loss of some features or functionality. In scenarios where there is complete loss of a particular component such as all call control servers, more catastrophic loss of features or functionality is possible.
When considering collaboration clients and applications, high availability is certainly important. Not only can specific collaboration features or functions become unavailable in failure scenarios, but in some cases presence-capable clients might be unable to connect to the network for even basic functionality such as registration and making or receiving calls. In other cases, clients or devices might have to reconnect and re-authenticate in order to return to service.
For applications and services such as voice messaging and rich media conferencing, capacity planning considerations include things like number of mailboxes or users, mailbox size, audio and video ports, and MCU sessions. In most cases additional capacity can be added by increasing the number of application servers and MCUs or by upgrading server or MCU hardware with higher-scale models, assuming the underlying network and call routing and control infrastructures are capable of handling the additional load.
Capacity planning considerations are also a concern for services such as presence and mobility. Scalability must be contemplated not only for things like numbers of configured and supported users and devices, but also for the number of integrations and connections between the applications and services. The volume of two-stage dialing and dial-via-office calls is of particular concern for mobility applications from the perspective of both the call control capacity and the PSTN gateway capacity. With presence services, on the other hand, critical scalability concerns include frequency of presence status changes and the propagation of those changes to the network, as well as text or instant message volumes. Typically, additional application servers or hardware upgrades will result in increased capacity for the applications and services, but the underlying call routing and control infrastructures must be capable of handling any increases in load.
When considering collaboration clients and application capacity planning, device registration and configuration are the most important scalability concerns. However, there are other scalability implications in terms of the back-end applications and services such as presence and messaging. Further, when deploying or integrating various clients with third-party applications and infrastructures, you must also consider the supported capacities for those third-party deployments.
For a complete discussion of system sizing, capacity planning, and deployment considerations related to sizing, refer to the chapter on Collaboration Solution Sizing Guidance.