Cisco CAB-DV10-8M= Datasheet

Cisco CAB-DV10-8M= Datasheet
Cisco Preferred Architecture for
Midmarket Collaboration
Design Overview
December 2014
© 2014 Cisco Systems, Inc. All rights reserved.
Preface
Contents
Preface .......................................................................................................................................................... 4
Documentation for Cisco Preferred Architectures ..................................................................................................... 4
About This Guide ...................................................................................................................................................... 4
Introduction .................................................................................................................................................... 5
Technology Use Cases ............................................................................................................................................. 5
Architectural Overview .............................................................................................................................................. 6
Cisco Business Edition 6000 ..................................................................................................................................... 8
Core Applications............................................................................................................................................. 8
High Availability ............................................................................................................................................... 9
Cisco Integrated Services Router.............................................................................................................................. 9
Endpoints ..................................................................................................................................................... 11
Recommended Deployment .................................................................................................................................... 12
Call Control .................................................................................................................................................. 13
Recommended Deployment .................................................................................................................................... 14
Benefits ................................................................................................................................................................... 14
Deployment Best Practices ..................................................................................................................................... 14
Cisco Unified Communications Manager and IM and Presence Service ....................................................... 14
Cisco Unified Survivable Remote Site Telephony ......................................................................................... 15
Dial Plan ........................................................................................................................................................ 16
Admission Control.......................................................................................................................................... 18
Conferencing ............................................................................................................................................... 19
Recommended Deployment .................................................................................................................................... 20
Audio and Video Conferencing ...................................................................................................................... 20
Benefits ................................................................................................................................................................... 20
Deployment Best Practices ..................................................................................................................................... 21
Audio and Video Instant Conferences ........................................................................................................... 21
Audio and Video Permanent Conferences ..................................................................................................... 21
Cisco Collaboration Meeting Rooms (CMR Premises) .................................................................................. 21
Scheduled Audio Conferences ...................................................................................................................... 22
Scheduled Video Conferences ...................................................................................................................... 22
WebEx Enabled TelePresence (CMR Hybrid) ............................................................................................... 23
Support for Multiple Call Processing Sites .............................................................................................................. 24
Collaboration Edge ...................................................................................................................................... 25
Recommended Deployment .................................................................................................................................... 26
Headquarters ................................................................................................................................................. 26
Remote Sites ................................................................................................................................................. 26
Teleworker Sites ............................................................................................................................................ 26
Benefits ................................................................................................................................................................... 26
Deployment Best Practices ..................................................................................................................................... 26
Cisco Expressway ......................................................................................................................................... 26
Connectivity for Audio and Video over the Internet ........................................................................................ 28
PSTN Gateway .............................................................................................................................................. 29
Virtual Private Network .................................................................................................................................. 30
Applications ................................................................................................................................................. 31
Cisco Unity Connection ........................................................................................................................................... 32
Recommended Deployment .......................................................................................................................... 32
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 2
Preface
Benefits .......................................................................................................................................................... 32
Deployment Best Practices ............................................................................................................................ 32
Cisco Unified Contact Center Express .................................................................................................................... 33
Recommended Deployment .......................................................................................................................... 33
Benefits .......................................................................................................................................................... 34
Deployment Best Practices ............................................................................................................................ 34
Cisco TelePresence Management Suite and Extensions ........................................................................................ 34
Cisco TelePresence Management Suite Provisioning Extension (TMSPE) ................................................... 34
Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE) .................................. 35
Recommended Deployment .......................................................................................................................... 35
Benefits .......................................................................................................................................................... 35
Cisco Prime Collaboration Provisioning Standard ................................................................................................... 36
Recommended Deployment .......................................................................................................................... 36
Benefits .......................................................................................................................................................... 36
Appendix ...................................................................................................................................................... 37
Product List ............................................................................................................................................................. 37
Licensing Options.................................................................................................................................................... 38
Sample Order .......................................................................................................................................................... 39
Sample Bill of Materials ........................................................................................................................................... 40
Infrastructure ................................................................................................................................................. 40
Licensing ....................................................................................................................................................... 42
Cisco Unified IP Phones and TelePresence Video Endpoints ....................................................................... 45
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 3
Preface
Preface
Cisco Preferred Architectures provide recommended deployment models for specific market segments based on common
use cases. They incorporate a subset of products from the Cisco Collaboration portfolio that is best suited for the targeted
market segment and defined use cases. These deployment models are prescriptive, out-of-the-box, and built to scale with
an organization as its business needs change. This prescriptive approach simplifies the integration of multiple systemlevel components and enables an organization to select the deployment model that best addresses its business needs.
Documentation for Cisco Preferred Architectures
• Cisco Preferred Architecture (PA) design overview guides help customers and sales teams select the appropriate
architecture based on an organization’s business requirements; understand the products that are used within the
architecture; and obtain general design best practices. These guides support sales processes.
• Cisco Validated Design (CVD) guides provide details for deploying components within the Cisco Preferred
Architectures. These guides support planning, deployment, and implementation (PDI).
• Cisco Collaboration Solution Reference Network Design (SRND) guide provides detailed design options for Cisco
Collaboration. This guide should be referenced when design requirements are outside the scope of Cisco Preferred
Architectures.
About This Guide
The Cisco Preferred Architecture for Midmarket Collaboration design overview is for:
• Sales teams that design and sell collaboration solutions
• Customers and sales teams who want to understand the overall collaboration architecture, its components, and
general design best practices
Readers of this guide should have a general knowledge of Cisco Voice, Video, and Collaboration products and a basic
understanding of how to deploy these products.
This guide simplifies the design and sales process by:
• Recommending products in the Cisco Collaboration portfolio that are built for the midmarket and that provide
appropriate feature sets for this market
• Detailing a collaboration architecture and identifying general best practices for deploying in midmarket organizations
• Including a sample Bill of Materials (BoM) with products that target the midmarket price point
For detailed information about configuring, deploying, and implementing this architecture, consult the related CVD
documents on the Design Zone for Collaboration.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 4
Introduction
Introduction
In recent years, many new collaborative tools have been introduced to the market, enabling organizations to extend
collaboration outside the walls of their businesses. Providing access to collaborative tools for employees outside the office
is no longer a luxury; it is mandatory for businesses to stay relevant in today’s market. Today’s users expect immediate
access to these tools from a wide variety of portable and mobile devices. Many of these same tools can be extended to
customers and partners, helping strengthen these relationships.
Organizations realize the added value that collaboration applications bring to their businesses through increased
employee productivity and enhanced customer relationships. Not long ago, interoperability among collaboration
applications was sparse, and applications were difficult to deploy and use. Since then, significant advances have been
made in the collaboration space, simplifying deployment, improving interoperability, and enhancing the overall user
experience. Additionally, individuals have adopted a wide variety of smart phones, social media, and collaboration
applications in their personal lives.
Organizations can now feel comfortable providing collaboration applications that employees will quickly adopt and that
provide maximum value. These new collaboration tools enhance an organization’s overall business processes, make its
employees more productive, and open the door to new and innovative ways for communicating with business partners
and customers. Today’s collaboration solutions offer organizations the ability to integrate video, audio, and web
participants into a single, unified meeting experience.
Technology Use Cases
Organizations want to streamline their business processes, optimize employee productivity, and enhance relationships
with partners and customers. The Cisco Preferred Architecture (PA) for Midmarket Collaboration delivers capabilities that
enable organizations to realize immediate gains in productivity and enhanced relationships. Additionally, the following
technology use cases offer organizations opportunities to develop new, advanced business processes that deliver even
more value in these areas:
• Consolidate communications infrastructure — Bring together voice, video, and data into a single IP network to
simplify management and support effective communications.
• Incorporate video into meetings — Improve communications, relationships, and productivity by making it easier to
meet face-to-face over distance.
• Extend telephony with video — Facilitate face-to-face video communications directly from end-user phones or
softphone applications.
• Support teleworkers and branch offices — Let employees work from multiple locations, whether satellite offices,
home offices, or when traveling.
• Collaborate with external organizations — Easily share information, interact in real time, and communicate using
technologies beyond email and telephone.
• Create flexible work areas and office spaces — Scale office space and create work areas that foster employee
inclusiveness, collaboration, innovation, and teamwork.
• Deploy a Unified Communications architecture — Provide the entire global organization with a single
communications tool set for all users.
Information about Cisco Collaboration Technologies and use cases is available on Cisco.com.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 5
Introduction
Architectural Overview
The Cisco PA for Midmarket Collaboration provides end-to-end collaboration targeted for deployments of up to 1,000
users. This architecture provides high availability for critical applications and incorporates products developed and priced
for the midmarket. The consistent user experience provided by the overall architecture facilitates quick user adoption,
enabling an organization to recognize immediate value for its investment. Additionally, the architecture supports an
advanced set of collaboration services that extend to mobile workers, partners, and customers through the following key
services:
• Voice communications
• Instant messaging and presence
• High-definition video and content sharing
• Rich media conferencing
• Enablement of mobile and remote workers
• Business-to-business voice and video communications
• Unified voice messaging
• Customer care
Because of the adaptable nature of Cisco endpoints and their support for IP networks, this architecture enables an
organization to use its current data network to support both voice and video calls. In general, it is a best practice to deploy
a collaboration solution with proper quality of service (QoS) configured throughout the network. Voice and video IP traffic
should be classified and prioritized to preserve the user experience and avoid negative effects such as delay, loss, and
jitter. For more information about LAN and WAN QoS, see the Cisco Collaboration SRND.
The Cisco PA for Midmarket Collaboration, shown in Figure 1, provides highly available and secure centralized services.
These services extend easily to remote offices and mobile workers, providing availability of critical services even if
communication to headquarters is lost. Centralized services also simplify management and administration of an
organization’s collaboration deployment.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 6
Introduction
Figure 1.
Cisco Preferred Architecture for Midmarket Collaboration
Table 1 lists the products in this architecture. For simplicity, products are grouped into modules to help categorize and
define their roles. The content in this guide is organized in the same modules.
Table 1.
Components for the Cisco Preferred Architecture for Midmarket Collaboration
Module
Component
Description
Call Control
Cisco Unified Communications Manager
(Unified CM)
Provides endpoint registration, call processing, and media
resource management
Cisco Unified Communications Manager IM and
Presence Service
Provides instant messaging and presence services
Cisco Integrated Services Router (ISR)
Provides Survivable Remote Site Telephony (SRST) functionality
Endpoints
Cisco Unified IP Phones, Cisco TelePresence video
endpoints, and Cisco Jabber
Enable real-time voice, video, and instant messaging
communications for users
Conferencing
Cisco TelePresence Conductor
Manages conferencing resources
Cisco TelePresence Server
Provides video conferencing resources
Cisco WebEx Software as a Service (SaaS)
Provides subscription-based web conferencing delivered through
WebEx Collaboration Cloud
Cisco Expressway-C
Enables interoperability with third-party systems and firewall
traversal
Cisco Expressway-E
Supports remote endpoint registration to Cisco Unified CM and
enables business-to-business communications
Cisco ISR
Provides either public switched telephone network (PSTN) or
Cisco Unified Border Element (CUBE) connectivity
Collaboration Edge
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 7
Introduction
Module
Component
Description
Applications
Cisco Unity Connection
Provides unified messaging and voicemail services
Cisco Unified Contact Center Express (Unified CCX)
Provides customer interaction management services
Cisco Prime Collaboration Provisioning Standard
Provides administrative functions (provisioning) for Cisco Unified
Communications applications
Cisco Business Edition 6000
Cisco Business Edition (BE) 6000 is a packaged system designed specifically for organizations with up to 1,000 users,
and it is the foundation of this architecture. Cisco BE 6000 is built on a virtualized Cisco Unified Computing System (UCS)
that is prepared and ready for use, with a preinstalled virtualization hypervisor and application installation files. The Cisco
BE 6000 solution offers premium voice, video, messaging, instant messaging and presence, and contact center features
on a single, integrated platform. For these reasons the BE 6000 is an ideal platform for the Cisco PA for Midmarket
Collaboration. For more information about the Cisco BE 6000, consult the data sheet.
Core Applications
The Cisco PA for Midmarket Collaboration is built on two Cisco BE 6000 high-density servers to provide high availability
for applications within the architecture (Figure 2). Virtualizing multiple applications on a single server lowers cost,
minimizes rack space, lowers power requirements, and simplifies deployment and management. Virtualization also
accommodates redeploying hardware and scaling software applications as organizational needs change.
Figure 2.
Cisco Preferred Architecture for Midmarket Collaboration Deployed on Cisco BE 6000
*The TMS node in Figure 2 includes TMS, TMSPE, TMSXE, and an embedded SQL server.
In this architecture, the following seven applications and Cisco Prime Collaboration Provisioning Standard are deployed
on one Cisco BE 6000 server, while a second instance of most applications is deployed on a second Cisco BE 6000
server, providing hardware and software redundancy for:
• Cisco Unified Communications Manager
• Cisco Unified Communications Manager IM and Presence Service
• Cisco Unity Connection
• Cisco Expressway, consisting of Expressway-C and Expressway-E
• Cisco TelePresence Conductor
• Cisco Unified Contact Center Express
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 8
Introduction
Cisco recommends always deploying redundant configurations to provide the highest availability for critical business
applications; however, a non-redundant Cisco BE 6000 server configuration may be deployed for organizations that do
not require full redundancy.
Note:
Space is available on the second Cisco BE 6000 server for additional Cisco Unified Communications
applications.
High Availability
The Cisco PA for Midmarket Collaboration provides high availability for all deployed applications by means of the
underlying clustering mechanism present in all Cisco Unified Communications applications.
Clustering replicates the administration and configuration of deployed applications to backup instances of those
applications. If an instance of an application fails, Cisco Unified Communications services — such as endpoint
registration, call processing, messaging, business-to-business communication, and many others — continue to operate on
the remaining instance(s) of the application. This failover process is transparent to the users. In addition to clustering, the
Cisco PA for Midmarket Collaboration provides high availability through the use of redundant power supplies, network
connectivity, and disk arrays.
The one exception to this is the TMS solution of applications. In order for TMS to be fully redundant, an external SQL
database is required as well as the Large Deployment of TMS, TMSPE, and TMSXE. To keep costs low for midmarket
customers, the recommended deployment is a single instance of the TMS solution with an embedded SQL server.
Cisco Integrated Services Router
Cisco Integrated Services Routers (ISR) and Aggregation Services Routers (ASR) provide Wide Area Network (WAN) and
Cisco Unified Communications services in a single platform. In the Cisco PA for Midmarket Collaboration, the Cisco ISR
and ASR can provide the following functions (Figure 3):
• Media resources (MTP and transcoder) for Cisco Unified Communications Manager
• External connectivity to Internet
• IP routing and network services such as DHCP, DNS, NTP, and others
• Cisco Unified Survivable Remote Site Telephony (SRST) to support calls during WAN failures
• Voice gateway to the Public Switched Telephone Network (PSTN) or Cisco Unified Border Element (CUBE) for
Session Initiation Protocol (SIP) trunks
• Integrated data and voice connectivity to service providers
• Multiprotocol Label Switching (MPLS) WAN connectivity for an organization’s network
• Virtual Private Network (VPN) client to establish secure tunnels to the VPN concentrator
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 9
Introduction
Figure 3.
Cisco ISR and ASR Functions
The Cisco ISR and ASR have additional slots that support add-on modules such as wireless controllers and VMware ESXi
servers. Deployments can use various Cisco ISR and ASR models to support different features, to scale, and to
accommodate additional services. The modular design enables the Cisco ISR and ASR to be deployed at headquarters,
remote locations, or branch locations. For more information about the various Cisco ISR and ASR models, see the
product documentation.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 10
Endpoints
Endpoints
Cisco Collaboration endpoints provide a wide range of features, functionality, and user experiences. Cisco endpoints
range from low-cost, single-line phones and soft clients to three-screen Cisco TelePresence endpoints, allowing an
organization to deploy the right variety of endpoints to meet users’ needs (Figure 4). Additionally, these devices enable
users to access multiple communication services such as:
• Voice calls
• Video calls
• Conferencing
• Voicemail
• Presence
• Instant messages (Cisco Jabber)
• Desktop sharing
Figure 4.
Architecture for Endpoints
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 11
Endpoints
Recommended Deployment
Cisco Unified CM is the call control server for the Cisco PA for Midmarket Collaboration. Cisco Unified IP Phones, Jabber
clients, and TelePresence video endpoints use SIP to register directly to Cisco Unified CM. The Unified CM cluster’s
failover mechanism provides endpoint registration redundancy. If a WAN failure occurs and endpoints at remote locations
cannot register to Unified CM, they use SRST functionality for local and PSTN calls, but some services such as voicemail
and presence might not be available.
Cisco recommends the endpoints listed in the following tables because they provide optimal features for this design.
Cisco has a range of endpoints with various features and functionality that an organization can also use to address its
business needs.
Table 2.
Cisco Unified IP Phones
Product
Description
Cisco Unified IP Phone 6901 or
Cisco Unified IP Phone 7821
Public space phone
Cisco Unified IP Phone 8800 Series
General office use, multiple-line phone
Cisco Unified IP Phone 8831
IP conference phone
Table 3.
Cisco TelePresence and Video Endpoints
Product
Description
Cisco EX Series
Personal TelePresence endpoint for the desktop, with remote access
Cisco DX Series
Personal TelePresence endpoint for the desktop
Cisco MX Series
TelePresence multipurpose room endpoint
Cisco SX Series
Integrator series TelePresence endpoint
Table 4.
Cisco Jabber
Product
Description
Mobile:
Soft client with integrated voice, video,
voicemail, instant messaging, and presence
functionality for mobile devices and personal
computers
Jabber for Android
Jabber for iPhone and iPad
Desktop:
Jabber for Mac
Jabber for Windows
Table 5.
Comparison of Endpoint Features and Capabilities
Product(s)
Audio
Video
Content
Sharing
Unified CM
High Availability
Mobile and
Remote Access
Video
SRST
Audio
SRST
IP Phone 6901
Y
N
N
Y
N
N
Y
IP Phone 7821
Y
N
N
Y
N
N
Y
IP Phone 8800 Series
Y
N
N
Y
N
N
Y
IP Phone 8831
Y
N
N
Y
N
N
Y
EX Series
Y
Y
Y
Y
Y
N
N
DX Series
Y
Y
Y1
Y
N
N
N
MX Series
Y
Y
Y
Y
Y
N
N
SX Series
Y
Y
Y
Y
Y
N
N
Jabber Mobile
Y
Y
N
Y
Y
N
N
Jabber Desktop
Y
Y
Y
Y
Y
Y
Y
1. The Cisco DX70 and DX80 are the only DX Series endpoints that support content sharing
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 12
Call Control
Call Control
Call control is the core element for any communications deployment. It provides endpoint registration, call processing, and
call admission control. Call control design considerations include the enterprise dial plan, endpoint addressing scheme,
calling party presentation, call admission control, codec selection, PSTN connectivity, and general trunking requirements,
as well as other factors.
Cisco Unified CM provides a common call control platform for all Cisco Collaboration deployments (Figure 5). Having a
highly available and common call control component for a communications infrastructure is crucial to provide consistent
services for all devices and communication types and to preserve a uniform dial plan and a consistent feature set across
the enterprise.
Adding the IM and Presence Service to a Cisco Unified CM deployment provides instant messaging, network-based
presence, and federation for third-party chat servers, and it enables the use of Cisco Jabber for instant messaging,
presence, and audio and video communications.
Figure 5.
Architecture for Call Control
Table 6 lists the roles of the call control components in this architecture and the services they provide.
Table 6.
Components for Call Control
Module
Component
Description
Call Control
Cisco Unified Communications Manager
(Unified CM)
Provides call routing and services, dial plan, and bandwidth management;
and enables Cisco Jabber desk phone control
Cisco Unified Communications Manager
IM and Presence Service
Provides Cisco Jabber support for instant messaging and user-based
presence and third-party federation
Cisco Integrated Services Router (ISR)
Provides Survivable Remote Site Telephony (SRST) to support call control
functions during a WAN outage
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 13
Call Control
Recommended Deployment
• Deploy two Cisco Unified CM servers in a cluster configuration that includes a publisher node and a subscriber
node for redundancy.
• Deploy two IM and Presence Service servers in a cluster configuration that includes a publisher node and a
subscriber node for redundancy.
• Enable Cisco SRST on the Cisco ISR as a backup service at remote sites to provide high availability.
Note:
If full redundancy is not required, a single server may be deployed without loss of functionality.
Benefits
This deployment provides the following benefits:
• Call control is centralized at a single location that serves multiple remote sites.
• Management and administration are centralized.
• Common telephony features are available across voice and video endpoints.
• Single call control and a unified dial plan are provided for voice and video endpoints.
• Critical business applications are highly available and redundant.
Deployment Best Practices
Cisco Unified Communications Manager and IM and Presence Service
Publisher-Subscriber Deployment Model
A Cisco Unified CM cluster or an IM and Presence Service cluster consists of one publisher node and one subscriber
node (Figure 6).
• The publisher node is the server that is installed first. This server contains the cluster’s configuration database.
Cluster-wide configuration is written to the publisher’s database and replicated on the subscriber.
• The subscriber node is the server that is installed second. It contains a replica of the publisher’s database. The
subscriber is updated automatically whenever the publisher’s configuration changes.
Clustering provides an automatic redundancy mechanism for endpoints and for Cisco Unified CM services, such as the
ability to receive and process incoming calls. Cisco recommends configuring the Unified CM cluster with the subscriber
node as the primary call-processing server and the publisher node as the backup call-processing server. This
configuration applies to the IM and Presence Service cluster, too. If the IM and Presence Service subscriber node goes
down, then IM and presence capabilities will still be available for Cisco Jabber clients.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 14
Call Control
Figure 6.
Cisco Unified CM Cluster
SIP Trunk Recommendations
Use SIP trunks from Cisco Unified CM to communicate with all the components in the Cisco PA for Midmarket
Collaboration, including external entities such as third-party systems. SIP trunks offer the following benefits:
• SIP trunks provide a standards-based environment that reduces operations and maintenance complexity of the end-
to-end solution.
• SIP trunks are enhanced with presence information.
• SIP trunks are recommended for video communications.
Configure a SIP trunk from the Cisco Unified CM cluster to external components in the deployment, such as
TelePresence Conductor and the IM and Presence Service. Specify each server for the external component as a
destination in the SIP trunk configuration. This configuration provides continuation of services if a node goes down.
Cisco Unified Survivable Remote Site Telephony
The Cisco Survivable Remote Site Telephony (SRST) feature is critical for remote sites that require continuation of voice
services during WAN outages. SRST runs on the same Cisco ISR that provides WAN and PSTN connectivity for the
remote site.
Deploy SRST on the Cisco ISR in the following cases:
• The remote site has local PSTN connectivity.
• The remote site does not have local PSTN connectivity but has more than 25 users.
To avoid interruption of external voice services if a WAN outage occurs, provide local PSTN connectivity at the remote
site. SRST is required only if the remote site’s WAN reliability does not match that site’s required service level for voice
service availability.
If a WAN failure occurs at a site with SRST and local PSTN access, the following services will be available:
• Internal point-to-point voice calls and video calls (with enhanced SRST only)
• External voice calls through the PSTN
• Call hold, transfer, and conference
• Music on hold
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 15
Call Control
Note:
SRST is not available for Cisco EX, MX, or SX Series endpoints. See the SRST data sheet for information about
endpoints that support SRST.
Dial Plan
A structured, well-designed dial plan is essential to successful deployment of any call control system. When designing a
dial plan, consider the following main factors:
• Dialing habits
• Endpoint addressing
• Routing
• Directory integration
• Classes of service
Dialing Habits
Dialing habits describe what end users can dial to reach various types of destinations. Dialing habits can first be classified
as numeric dialing (for example, 914085550123) or alphanumeric dialing (for example, [email protected]).
Typically, different types of destinations require support for different dialing habits. For example:
• PSTN toll call: 91-<10 digits>
• PSTN international call: 9011-<country code + national significant number>
• Abbreviated intra-site dialing: for example, 4XXX
• Abbreviated inter-site dialing: for example, 8-<site code>-<intra-site number>
• +-dialing from directories: “+” followed by a fully qualified global PSTN number as described in ITU recommendation
E.164
• URI dialing: for example, [email protected] for intra-company and inter-company dialing. Endpoints typically allow
omission of the right-hand side (host portion) of the URI and they automatically append the local host portion, so
that [email protected] can also be abbreviated as bob.
Further dialing habits might have to be defined for services such as call pick-up, voicemail, and others. Also, future growth
should be considered so that more users and more sites can be added as needed without redesigning the dial plan.
Identifying dialing habits is most important when defining an enterprise dial plan in order to avoid overlaps between any
two dialing habits. For example, a trunk access code of 9 prohibits abbreviated intra-site dialing starting with 9. Avoiding
overlaps between dialing habits is crucial to avoid inter-digit timeouts, which lead to bad user experiences.
In migration scenarios, the dialing habits supported by the existing system can be used as a first estimate of the dialing
habits required in the new system. On the other hand, migration to a new communications system can also serve as a
reason to get rid of outdated customs and practices.
Endpoint Addressing
Each endpoint registered with the enterprise call control must have a unique numeric address. Endpoint addresses in
Cisco Unified CM are equivalent to the directory numbers provisioned on the lines of the endpoints. Use fully qualified
PSTN numbers (E.164 numbers) with a leading “+” as endpoint addresses. This format is typically referred to as +E.164
format. The benefits of using +E.164 endpoint addresses include:
• Wide use in voice networks
• No need to develop and maintain an enterprise numbering scheme
• Easy creation of correct caller ID presentation for all on-cluster and off-cluster call flows
• Easy implementation of directory lookups
• Simplified alternate routing to the PSTN in cases of WAN failure or bandwidth constraints
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 16
Call Control
For endpoints without assigned PSTN-based direct inward dial (DID) numbers (no E.164 number representation exists),
create enterprise-wide unique endpoint addresses outside of the default +E.164 domain. These endpoint addresses
should be in line with the internal dialing habit defined to reach these endpoints. If, for example, the abbreviated inter-site
dialing habit to reach a set of non-DID endpoints in a given site is 84915XXX, then these non-DID endpoints should use
this numbering scheme for their endpoint addresses.
In addition to the primary numeric endpoint addresses, administrators can provision alphanumeric URIs (for example,
[email protected]) in Cisco Unified CM to serve as aliases for the primary addresses, and users can enter the URI as an
alternate way to dial the destination endpoint.
Routing
The routing portion of the dial plan enables users to reach the correct destinations when they use the defined dialing
habits.
The primary numeric routing is based on +E.164 numbers. External routes to other transport networks such as the PSTN
also use the +E.164 scheme. Endpoint addresses in +E.164 format provide +E.164 on-net dialing without any further
configuration. All other numeric dialing habits, such as abbreviated inter-site and intra-site dialing, are implemented as
overlays by adding the appropriate translation patterns to the dial plan to map from the implemented dialing habit to the
+E.164 global routing address format. This allows users to reach the same endpoint by means of different dialing habits,
depending on user preference.
Alpha-numeric URIs, as aliases for numeric addresses, provide an alternative means of reaching endpoints. The benefits
of URI dialing and routing include:
• Conformity with the native dialing habit on most video systems
• Easier business-to-business connectivity
• Direct mapping from instant messaging identifiers to addresses (easier escalation of business-to-business IM
sessions to voice and/or video), although technically IM identifiers and SIP URIs are not necessarily identical
If an endpoint is enabled for business-to-business calls over the Internet, Cisco recommends associating a SIP URI to the
device so that the business-to-business routing logic can be based on SIP URIs.
As with numeric routing, if an alias or SIP URI is recognized as an internal destination and is associated with a specific
device, then Cisco Unified CM sends the call to that device. However, if the dialed SIP URI does not match any registered
endpoint alias, Cisco Unified CM uses SIP route patterns to determine where to send the call. For example, if the dialed
alias [email protected] does not exist internally, Cisco Unified CM uses a SIP route pattern (such as *.com) to send
the call to Expressway-C as a business-to-business call.
Directory Integration
To enable users to search contacts and dial from the directory, integrate Cisco Unified CM with the organization’s LDAP
directory. Although Cisco Unified CM allows the creation of local user contacts, LDAP directory integration is required
when using Cisco Jabber because it provides a single location for directory management and enables users to
authenticate to Cisco Unified CM and Cisco Jabber by using their LDAP directory credentials.
Cisco Unified CM pulls user and contact information from LDAP directories and synchronizes user parameters — name,
surname, username, telephone number, and SIP URI — when changes occur. For example, use the telephoneNumber
attribute to populate the Telephone Number field in the Cisco Unified CM directory. The format of phone numbers in the
corporate directory must be globally significant and must match one of the defined dialing habits. Corporate directories
typically should have all phone numbers in +E.164 format (leading “+” followed by the fully qualified global number) as
long as a DID exists. Only this format allows the phone number in the corporate directory to be used universally inside
and outside the enterprise. Non-DID numbers that are not in +E.164 format could be used to dial uses internally from the
directory, but they would have no significance outside the enterprise. Use the mail attribute to populate the Directory URI
field in the Cisco Unified CM directory if URI dialing is used.
The IM and Presence Service pulls user and contact information from Cisco Unified CM.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 17
Call Control
Class of Service
Classes of service define which users can access which services, such as allowing only emergency and local calls from
lobby phones while allowing unrestricted calls from executive phones. The complexity of the dial plan is directly related to
the number of differentiated classes of service it supports.
To define classes of service, configure partitions and calling search spaces in Cisco Unified CM. The number of classes of
services supported by a dial plan depends on the granularity and complexity of the classes. For more information about
classes of service and details on enterprise dial plan design, see the Cisco Collaboration SRND.
Admission Control
Call admission control (CAC) mitigates congestion on WAN links due to excessive audio and video traffic. In cases where
the administrator needs to control how many media calls flow over various links in the WAN topology, Cisco Unified CM
Enhanced Location Call Admission Control (ELCAC) provides a solution. ELCAC supports various WAN topologies and
gives the administrator the ability to statically model the WAN network topology to support admission control for audio and
video calls.
Cisco Unified CM uses locations and links to model how the WAN network topology routes media between groups of
endpoints within a location for audio and video conference calls.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 18
Conferencing
Conferencing
The ability for three or more people to communicate in real time by using voice and video technologies is a core
component of collaboration. Cisco rich media conferencing builds upon existing infrastructure in place for point-to-point
calls, offering users a consistent voice and video experience (Figure 7).
Figure 7.
Architecture for Conferencing
Table 7 lists the roles of the conferencing components in this architecture and the services they provide.
Table 7.
Components for Conferencing
Module
Component
Description
Conferencing
Cisco TelePresence
Conductor
Manages and allocates conferencing resources requested from Unified CM.
Cisco TelePresence Server
Provides voice and video conferencing.
Optimizes resources by making unused resources available for greater scalability in
conferencing.
Available on dedicated hardware platforms and on virtual machines.
Can be deployed concurrently with Cisco TelePresence Conductor (remotely managed mode)
or as a standalone conference resource (locally managed mode).
Cisco WebEx Software as a
Service (SaaS)
Cisco Preferred Architecture for Midmarket Collaboration
Subscription-based web conferencing delivered through WebEx Collaboration Cloud
PAGE 19
Conferencing
There are three types of conferences:
• Ad hoc or instant — A conference that is not scheduled or organized in advance. For example, a call between two
parties who add other parties to the call is an ad hoc conference.
• Rendezvous or permanent — A conference that requires callers to dial a predetermined number or URI to reach a
shared conferencing resource. Meet-me, static, and permanent are other names for this type of conference.
• Scheduled — A conference planned in advance with a predetermined start time. Typically, conference resources
are guaranteed to be available upon the start of the scheduled conference.
Recommended Deployment
Audio and Video Conferencing
• Deploy Cisco TelePresence Server on Multiparty Media 400v (mm400v) in remotely managed mode for instant and
permanent conferences.
◦ Deploy Cisco TelePresence Conductors on the primary BE 6000 server for management of instant and
permanent TelePresence Servers. Deploy a redundant Cisco TelePresence Conductor on the backup Cisco
BE 6000 server and integrate it with Cisco Unified CM.
◦ Integrate the TelePresence Conductor cluster with Cisco Unified CM through SIP trunks and registered media
resource conference bridges.
• Deploy the TelePresence Server 7010 in locally managed mode for scheduled video conferences.
◦ Integrate the TelePresence Server for scheduled conferences with Unified CM through SIP trunks and route
patterns.
◦ Deploy Cisco TelePresence Management Suite to manage locally managed TelePresence Servers. Deploy
Cisco TelePresence Management Suite Provisioning Extension for provisioning of personal collaboration
meeting rooms (CMRs).
• Deploy Cisco WebEx Software as a Service for scheduled web conferences.
• Integrate Cisco WebEx conferencing with on-premises voice and video conferencing through the CMR Hybrid
(formerly, WebEx Enabled TelePresence) solution.
• As an alternative, an entirely cloud-based conferencing solution is available for customers concerned with keeping
capital expenditure costs low.
Note:
If full redundancy is not required, a single server may be deployed without loss of functionality.
Benefits
This deployment provides the following benefits:
• Users have a consistent experience for launching and joining various types of conferences.
• A single conferencing platform provides on-premises audio and video conferencing.
• CMR Hybrid allows users to connect to meetings either from their video and audio devices or through the WebEx
cloud with a meeting client running on their desktop or mobile devices.
• It provides users with real-time, high-definition video conferencing, including the ability to share content easily over
a dedicated presentation channel.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 20
Conferencing
Deployment Best Practices
Audio and Video Instant Conferences
For ad hoc audio and video conferences, use an on-premises MultiParty Media 400v TelePresence Server managed by
TelePresence Conductor as a media resource. TelePresence Conductor conference templates are referenced by multiple
virtual IP addresses. These TelePresence Conductor virtual IP addresses register with Cisco Unified CM as ad hoc
conference bridges and are used in media resource group lists (MRGLs) and media resource groups (MRGs). Unified CM
uses MRGLs and MRGs to prioritize and allocate media resources such as conference bridges, music on hold sources,
annunciators, transcoders, and media termination points (MTPs).
If endpoints have access to the appropriate MRGL, they can request these resources. Resources local to the initiating
endpoint are preferred over remote resources (Figure 8).
Figure 8.
Media Resource Group List (MRGL) Example
A single TelePresence Conductor cluster can have multiple conference templates configured to provide a variety of
service levels and experiences for ad hoc audio and video conferences. With this architecture, administrators can
segment their users and provide restrictions on ad hoc conference size, media properties, and additional features such as
content sharing.
Audio and Video Permanent Conferences
Audio and video permanent conferences use the same TelePresence Conductor and TelePresence Server architecture
as audio and video ad hoc conferences. Permanent conferences are directed to TelePresence Conductor through Cisco
Unified CM route patterns and the existing dial plan. Users can dial either a directory number or a URI to reach an audio
or video permanent conference. Cisco TelePresence Conductor handles ad hoc and permanent conferences on a firstcome, first-served basis, making them best-effort services.
Cisco Collaboration Meeting Rooms (CMR Premises)
Cisco Collaboration Meeting Rooms (CMRs) greatly simplify the deployment of on-premises audio and video
conferencing. Cisco CMRs enable an administrator to quickly configure and provision conferences, providing each user
with their own personal conference space. Users browse to a website with a simple interface and create their conference,
specifying preferences such as welcome screen text, participant layout, and conference PIN protection.
Cisco TelePresence Management Suite Provisioning Extension (TMSPE) enables rapid provisioning of TelePresence
users and their respective personal CMRs for large-scale deployments. TMSPE is an optional addition to TMS and runs
on the same Windows Server as the TMS application.
Administrators create a CMR template in TMS to specify the base dial plan for CMR URIs and numeric aliases. When
users create and personalize their CMRs, they receive instructions for how to dial in to their meetings, and these numbers
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 21
Conferencing
and URIs are in line with the CMR template configured in TMS. As users create their CMRs, TMSPE provisions and
configures the necessary settings on TelePresence Conductor, and no further interaction is needed from an administrator.
Scheduled Audio Conferences
Customers with audio-only phones can use Cisco WebEx Software as a Service (SaaS) to host conferences. This solution
provides voice and video conferencing with content sharing capability on a single platform. Participants join the
conferences using the meeting client running on their desktop or mobile device.
Cisco WebEx Software as a Service
Cisco WebEx SaaS is a subscription-based service delivered through the WebEx Collaboration Cloud, where all the
meetings are hosted. Few components are deployed on-premises, so this option is well suited for customers who manage
their communications budget as an operational expenditure.
WebEx Collaboration Cloud is highly available and has redundancy built into the infrastructure to handle component
failure. Deploy Cisco WebEx SaaS using WebEx audio for web conferencing. Cisco highly recommends enabling HD
video for the optimal video experience and enabling SSO to allow integration with the organization’s LDAP directory for
access using common credentials.
For additional information on Cisco WebEx Software as a Service, see the product documentation.
Scheduled Video Conferences
For scheduled video conferences, use a dedicated and locally managed Cisco TelePresence Server 7010 as the
conferencing resource (Figure 9). Integrate the TelePresence Server to Cisco Unified CM with SIP trunks, and manage it
through Cisco TMS. Inside Cisco TMS, use IP Zones for optimal bridge selection (if more than one 7010 is deployed)
based on the location of the endpoints scheduled for the conference.
Figure 9.
Architecture for Video Conferencing
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 22
Conferencing
WebEx Enabled TelePresence (CMR Hybrid)
Cisco WebEx Enabled TelePresence combines the scheduled on-premises video conference and the WebEx cloud-based
conference into a single meeting. Participants can join the scheduled meeting using the WebEx meeting client or a
TelePresence device, and they experience two-way video, audio, and content sharing from their respective devices. As
illustrated in Figure 10, Cisco recommends deploying Cisco Expressway-C and Expressway-E to handle calls to and from
the WebEx cloud, and Cisco Expressway Rich Media Session Licenses are required. The same locally managed Cisco
TelePresence Server 7010 discussed in the previous section on Scheduled Video Conferences can be used for CMR
Hybrid.
Note:
For simplicity the entire BE 6000 architecture is not shown in Figure 10.
Figure 10.
Architecture for CMR Hybrid
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 23
Conferencing
Support for Multiple Call Processing Sites
Organizations may choose to implement more than one Cisco TelePresence Conductor cluster for any of the
following reasons:
• Administrational separation — This includes the need to keep users from different parts of the organization on
separate infrastructures or to have different departments operate different parts of the communications
infrastructure.
• Geographic footprint — Physical limitations such as excessive latency between endpoints and conferencing
resources could degrade the user experience (for example, US users might not have a productive collaborative
meeting if they use conferencing resources located in Europe).
• Multiple Unified CM clusters — If more than one Unified CM cluster is already deployed due to the previous
reasons, Cisco recommends also deploying multiple TelePresence Conductor clusters.
Deploy multiple TelePresence Conductor clusters along with local TelePresence Server resources (Figure 11). Implement
a global dial plan, as discussed in the Call Control section, to enable users to access conferences regardless of where the
TelePresence Conductor or TelePresence Server is located.
Figure 11.
Multiple Call Processing Sites with Conferencing
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 24
Collaboration Edge
Collaboration Edge
Business demand for connectivity between organizations by leveraging the Internet has increased significantly over the
past few years. For many organizations, this connectivity is a fundamental requirement for conducting day-to-day
activities. Moreover, securely connecting mobile workers and remote sites to each other and to headquarters is critical
functionality that enables organizations to accomplish their business goals. The Cisco PA for Midmarket Collaboration
addresses these needs with the Collaboration Edge architecture shown in Figure 12.
Figure 12.
Architecture for Collaboration Edge
Table 8 lists the roles of the Collaboration Edge components in this architecture and the services they provide.
Table 8.
Components for Collaboration Edge
Module
Component
Description
Collaboration Edge
Cisco Expressway-E
The traversal server that enables secure VPN-less mobile and remote access for
TelePresence endpoints and Jabber clients. The traversal server resides in the
DMZ. The solution also provides business-to-business calling, protocol
interworking, and cloud connectivity.
Cisco Expressway-C
The traversal client that creates a secure, trusted connection through the firewall
to Expressway-E. The traversal client resides inside the enterprise network. The
solution provides mobile and remote access, business-to-business calling,
protocol interworking, and cloud connectivity.
Cisco ISR with PSTN Interfaces
Enables local PSTN connectivity
Cisco ISR with Cisco Unified
Border Element (CUBE) software
Enables connectivity from an organization’s network to the service provider
network for SIP trunks via CUBE
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 25
Collaboration Edge
Recommended Deployment
Headquarters
• Deploy a Cisco Expressway-C and Expressway-E server pair to enable remote Jabber and TelePresence video
endpoint registrations, IM and Presence, and secure business-to-business connectivity through the firewall. Cluster
both Expressway-C and Expressway-E servers in both pairs.
• Deploy Cisco ISR as the PSTN gateway, or enable CUBE functionality on the Cisco ISR for voice connectivity from
the organization’s network to the service provider network through a SIP trunk.
Note:
If full redundancy is not required, a single server pair (Expressway-C and Expressway-E) may be deployed.
Remote Sites
• Deploy Cisco ISR as the PSTN gateway.
Teleworker Sites
• For video-enabled sites, deploy Cisco TelePresence endpoints utilizing the Expressway-C and Expressway-E
infrastructure at headquarters or another site.
• In addition, the Cisco Jabber client can be used without the VPN, regardless of the location of the endpoint (internal
or external to the organization).
• Legacy audio and video-enabled phones can be deployed with VPN technologies. Depending on the phone type,
some of them have an embedded VPN client and may be deployed without a VPN hardware client. For more
information on each phone model, refer to the product documentation.
Benefits
This deployment provides the following benefits:
• The Cisco ISR supports standards-based interfaces and various PSTN types, so it can be deployed globally.
• Instead of traditional PSTN interfaces, CUBE functionality can be enabled on the Cisco ISR if a SIP trunk is used.
• The Cisco ISR can be used for WAN connectivity.
• Cisco Expressway provides calling, presence, instant messaging, voicemail, and corporate directory services for
Cisco Jabber and TelePresence video endpoints.
• Cisco Expressway enables video communications between organizations, partners, and vendors over the Internet.
Deployment Best Practices
Cisco Expressway
Cisco Expressway provides secure firewall and NAT traversal for mobile Cisco Jabber and TelePresence video endpoints
(Figure 13) and secure business-to-business communications (Figure 14). Cisco Expressway consists of two applications:
Expressway-C and Expressway-E.
Deploy Cisco Expressway-C inside the network, and deploy Expressway-E in the demilitarized zone (DMZ) by connecting
separate network ports on Expressway-E to the organization’s network and to the DMZ.
Cisco fully supports a virtualized Expressway-E in the DMZ; however, a dedicated server can be deployed based on the
company’s security requirements.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 26
Collaboration Edge
Figure 13.
Traversal for Registrations Through Firewall with Expressway-C and Expressway-E
Figure 14.
Traversal for Business-to-Business Calls Through Firewall with Expressway-C and Expressway-E
Cisco Expressway-C
Place Expressway-C in the trusted network inside the organization. Deploy Expressway-C to:
• Function as a traversal client and establish a secure connection to Expressway-E through the firewall
• Establish secure or non-secure connection to Cisco Unified CM
• Integrate with an existing internal video network that uses H.323
• Enable business-to-business calls to external entities that communicate using SIP or H.323
• Provide interworking between H.323 and SIP protocols for H.323 business-to-business communications
• Enable mobile and remote access capabilities and call signaling for Cisco-supported endpoints, directing them to
Cisco Unified CM for SIP registration and/or the IM and Presence Service (See the Endpoints section for
information on which endpoints support mobile and remote access.)
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 27
Collaboration Edge
Cisco Expressway-E
Because Expressway-E is reachable directly from the untrusted, external network, it should be placed in a DMZ for
security. The organization’s firewall policies control communications to and from this server. Deploy Expressway-E to:
• Function as a traversal server and allow secure communications to and from Expressway-C
• Enable audio and video connections to other organizations using SIP or H.323 on the Internet
• Provide secure communications to cloud-based services, such as CMR Cloud to the WebEx cloud
• Provide DNS SRV lookup service to resolve outbound calls and to receive inbound calls over the Internet
• Process registration and IM and presence information from Cisco endpoints on the external network and use secure
traversal communications to pass the information to Expressway-C
• Provide interworking between protocols (between SIP and H.323, and between IPv4 and IPv6) for business-to-
business communications
Licensing
Cisco Expressway can be used for mobile and remote access with no additional investment. However, if business-tobusiness calling is enabled, Rich Media licenses are required. Each business-to-business call requires two Rich Media
licenses. License Cisco Expressway for the anticipated maximum concurrent business-to-business sessions.
Connectivity for Audio and Video over the Internet
URI dialing is the best practice for audio and video dialing over the Internet. Cisco recommends assigning alphanumeric
URIs to all devices that will send or receive calls over the Internet. Any device on Cisco Unified CM can be reached over
the Internet by dialing the assigned alphanumeric SIP URI or the required directory number (DN) by dialing <+E.164
number>@domain. For example, a Jabber user might have a SIP URI set to [email protected] and a phone number set
to +14085551234. If someone dials [email protected] or [email protected] from an external location on the
Internet, Alice would receive the call on the Jabber client and all devices that share the same number.
Users on Cisco Unified CM have to dial the full SIP URI to reach a user or device from a different organization over
the Internet.
The architecture for business-to-business Internet connectivity includes a client/server solution: Expressway-C and
Expressway-E. Both servers can be deployed in standalone mode or in a cluster. Deploy the same number of cluster
peers for Expressway-C clusters as for Expressway-E clusters.
Cisco recommends deploying dedicated Expressway-C and Expressway-E clusters per customer-chosen Internet
breakout to minimize having outbound business-to-business calls traverse the WAN by routing them, instead, to an
Internet breakout close to the client that initiated the call. This minimizes the business-to-business call-related utilization of
the enterprise WAN.
Considerations for Outbound Business-to-Business Calls
• When multiple Expressway-C and Expressway-E pairs are deployed, Unified CM can redirect an outbound call to
the edge server that is nearest to the calling endpoint, thus minimizing WAN traffic.
• For call routing over the Internet, use public DNS service records. DNS SRV records map a domain to an edge
system servicing that domain for that protocol. For example, if a remote user dials [email protected], then the
remote system uses DNS to query for the host offering the SIP service for the domain ent-pa.com.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 28
Collaboration Edge
Mobile and Remote Access
The mobile and remote access feature enables Jabber clients and Cisco EX, SX, C, and MX Series endpoints to register
securely to Cisco Unified CM through Expressway-E and Expressway-C without any VPN. A Jabber client can send and
receive several types of collaboration flows (audio, video, instant messaging, and presence), while a hardware endpoint
can send audio and video streams. When multiple edges are deployed, Cisco recommends using Geo-DNS services to
provide the best network option based on assigning the closest edge in the DNS response.
The mobile and remote access functionality also leverages Expressway-C and Expressway-E. Both business-to-business
and mobile and remote access services are supported on the same server.
PSTN Gateway
Because landlines and mobile phones use the PSTN for local and international calls, external connectivity to the PSTN
from an organization’s IP telephony network is a requirement (Figure 15).
Figure 15.
PSTN Connectivity
Use Cisco ISR with a time-division multiplexing (TDM) module as the PSTN gateway at headquarters. This configuration
enables the gateway to implement media interworking for the organization’s incoming and outgoing PSTN calls.
At remote sites, deploy a Cisco ISR for local PSTN connectivity using voice modules. For more information about Cisco
ISR, see the data sheet.
Table 9.
Recommended PSTN Gateways
Location
PSTN Gateway
Headquarters
ISR G2 3900 series
Remote Sites
ISR G2 2900 series
If SIP trunks are used to connect to a service provider for voice calls, enable CUBE functionality on the Cisco ISR that is
deployed at headquarters. When deploying Cisco ISR with CUBE functionality, observe the following recommendations:
• Deploy CUBE in the demilitarized zone (DMZ).
• Enable the firewall for NAT to convert the external address to the address of CUBE.
• Enable the firewall to inspect voice calls.
Cisco Unified CM routes calls through SIP trunks to gateways, CUBE, or Cisco Expressway based on the dial plan. For
dial plan recommendations, see the Dial Plan section.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 29
Collaboration Edge
PSTN Connectivity for Voice
Enable PSTN connectivity for voice calls by using either an analog or ISDN interface. A Cisco ISR with analog or ISDN
cards provides these interfaces. Connectivity is usually local, and a site with PSTN interfaces uses its local ISR as a voice
gateway. Follow these recommendations for deploying an ISR for PSTN connectivity:
• PSTN interface (analog or ISDN)
◦ The device providing these interfaces is a Cisco ISR with analog or ISDN cards.
◦ Connectivity is usually local; a site with PSTN interfaces uses its local ISR as a voice gateway.
◦ Redundancy is achieved by deploying multiple ISRs. Cisco Unified CM has the ability to route traffic to the
closest available router.
• SIP trunks to the service provider, and ISR or CUBE as a border element
◦ This deployment is typically used in a centralized architecture. Remote sites either do not have local connectivity,
or they have local connectivity but use it only for backup voice services. In this case the WAN connectivity has to
be sized to accommodate PSTN calls traversing the WAN to the central site where CUBE is deployed.
◦ Redundancy can be achieved by deploying multiple ISRs, sometimes to different voice carriers. Cisco Unified
CM has the ability to route traffic to the closest available router.
ISDN Connectivity for Video
Although many organizations now use the Internet for business-to-business video connectivity, legacy interoperability with
ISDN networks might still be required if the called party is not reachable through the Internet. To provide ISDN
connectivity for video, use the Cisco TelePresence ISDN GW 3241 as a standalone unit.
Virtual Private Network
A virtual private network (VPN) enables an organization’s network to be extended to remote and teleworker sites,
providing those sites with full access to corporate services. Use the organization’s existing VPN to extend collaboration
services to teleworkers, or use Cisco IP Phones with VPN clients.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 30
Applications
Applications
In addition to the call processing and media resource components, the Cisco PA for Midmarket Collaboration includes the
following Cisco applications to enhance usability, functionality, and management (Figure 16):
• Unity Connection to provide messaging
• TelePresence Management Suite for conference scheduling and Collaboration Meeting Room (CMR) administration
• Unified Contact Center Express (CCX) for customer care
• Prime Collaboration Provisioning Standard for user and device provisioning
Figure 16.
Architecture for Applications
Table 10 lists the roles of the application components in this architecture and the services they provide.
Table 10.
Components for Applications
Module
Component
Description
Applications
Cisco Unity Connection
Provides unified messaging and voicemail services
Cisco TelePresence Management
Suite and extensions
Provides scheduling, web conferencing integration, and other advanced
video features
Cisco Unified Contact Center
Express (CCX)
Provides customer interaction and interactive voice response (IVR) services
Cisco Prime Collaboration
Provisioning Standard
Provides administrative functions (moves, adds, changes, and deletions) for
Cisco Unified Communications applications
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 31
Applications
Cisco Unity Connection
Cisco Unity Connection enables users to access and manage voice messages in a variety of ways, such as by email
inbox, web browser, Cisco Jabber, Cisco Unified IP Phone, TelePresence, smartphone, tablet, and many more. Users can
interact with Unity Connection either through phone keypad keys or through voice commands that they speak into the
phone handset, headset, or speakerphone.
Recommended Deployment
• Deploy two Unity Connection servers for each Cisco Unified CM cluster to provide high availability and redundancy.
• Use SIP trunks to integrate Unity Connection with Unified CM. Configure two SIP trunks, one for each Unity
Connection server in a pair.
• Enable the speech-activated voice command interface to maximize productivity of mobile workers.
Benefits
• Users can access the voicemail system and retrieve their voice messages by using their IP phones, mobile devices,
and various email client applications with either a dialed number or a SIP URI.
• Cisco Unity Connection allows users to customize personal settings from a web browser.
• Cisco Unity Connection offers a natural and robust speech-activated user interface that allows users to browse and
manage voice messages using simple and natural speech commands.
Note:
If full redundancy is not required, a single server may be deployed without loss of functionality.
Deployment Best Practices
Cisco Unity Connection supports a cluster configuration in active/active mode to provide both high availability and
redundancy. A Unity Connection cluster consists of a maximum of two nodes, one publisher and one subscriber in an
active/active deployment (Figure 17). If one Unity Connection node fails, the other active node in the cluster handles all
the calls, IMAP requests, and HTTP requests for the Unity Connection cluster. Each server in the Unity Connection cluster
must have enough voice messaging ports to handle all calls for the cluster.
Figure 17.
Cisco Unity Connection Cluster
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 32
Applications
Single Inbox, one of the unified messaging features in Cisco Unity Connection, synchronizes voice messages in Unity
Connection and Microsoft Exchange mailboxes. Unity Connection supports the Single Inbox feature with on-premises
Microsoft Exchange, cloud-based Microsoft Exchange, or Microsoft Office 365 server, thereby providing unified
messaging for voicemail. All voice messages, including those sent from Cisco Unity Connection ViewMail for Microsoft
Outlook, are first stored in Cisco Unity Connection and are immediately replicated to the Microsoft Exchange mailbox of
the recipient. This feature can be configured for each individual user separately.
Unity Connection imports the user information from the enterprise LDAP directory.
Each mailbox must have a unique voicemail number. Unity Connection supports both E.164 and +E.164 formats for the
extension of an end-user account (user with a voice mailbox). Unity Connection also supports alternate extensions
per user.
The voicemail pilot number designates the directory number that users dial to access their voice messages. Unified CM
automatically dials the voice messaging number when users press the Messages button on their phone. The voicemail
pilot number can be an internal extension or a dedicated PSTN number.
Visual Voicemail allows user to access voicemail using the graphical interface on the IP phone. Users can view a list of
messages and play messages from the list. Users can also compose, reply to, forward, and delete messages. Each
voicemail message displays data including the date and time when the message was left, urgency level, and
message length.
For more information on Cisco Unity Connection, refer to the product documentation.
Cisco Unified Contact Center Express
Cisco Unified Contact Center Express (CCX) enables organizations to provide powerful agent queuing and interactive
voice response (IVR) services to internal and external customers. These services enable customers to connect easily with
the right employees in an organization for sales inquiries or product support.
Recommended Deployment
Deploy two Unified CCX servers for high availability, with one active node and one standby node to handle failover in case
of component failure (Figure 18). Also configure a primary and a backup Cisco BE6000 server for the JTAPI interface of
the Telephony and Resource Manager-Contact Manager (RmCm) subsystems in Unified CCX.
Note:
If full redundancy is not required, a single server may be deployed without loss of functionality.
Figure 18.
Cisco Unified Contact Center Express Cluster
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 33
Applications
For contact center deployments, use Cisco Finesse as the agent and supervisor desktop. Cisco Finesse is a browserbased application implemented through a Web 2.0 interface with no client-side installation required, and it is highly
customizable. In addition, Cisco Finesse supports E.164, which adheres to the dial plan design recommendations
discussed in the Dial Plan section.
Benefits
This deployment provides the following benefits:
• Recorded greetings and customized prompts provide sophisticated call handling.
• Unified CCX supports external customer interaction.
• Unified CCX facilitates internal company communication for activities such as help desk.
Deployment Best Practices
As with the other components in the Cisco PA for Midmarket Collaboration, Unified CCX should be deployed with high
availability that includes active and standby nodes. Unified CCX downloads the end-user information from Unified CM that
is synchronized with the organization’s LDAP directory. This minimal configuration enables external callers to dial a single
number into the organization and then use simple dial-by-name or dial-by-extension functionality without the need for
telephone operators to connect external calls. Depending on the organization’s structure and business model, Unified
CCX could also be used for the following additional workflow configurations:
• Sales
• Customer support
• Internal IT helpdesk
• Human resources
These automated, call-directed workflows provide value to the organization by quickly and easily connecting a person with
a need to the appropriate resource within the organization for assistance.
For information about Cisco Unified Contact Center Express, see the data sheet.
Cisco TelePresence Management Suite and Extensions
Cisco TelePresence Management Suite (TMS) runs on a Windows Server instance, and it provides the scheduling and
call initiation functions for the organization. Users are imported from Active Directory, and the permissions model allows
for access control to various components and configured systems. User features such as directories and One Button to
Push (OBTP) are also provided to controlled endpoints by the TMS application. TMS utilizes a Microsoft SQL database for
all information about users, devices, and scheduled conferences. In addition to the core TMS application, the following
two additional applications provide supplemental features and services to enhance the overall video communications
experience.
Cisco TelePresence Management Suite Provisioning Extension (TMSPE)
TMSPE provides the functionality to create collaboration meeting rooms (CMRs) for users according to the permissions
and feature limits defined by the administrator. In addition to the CMR functionality, TMSPE also engages other
scheduling options, besides the administrator booking page, within the TMS application. One of these options includes the
ability to schedule WebEx Enabled TelePresence, bringing WebEx functionality and scale to meetings.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 34
Applications
Cisco TelePresence Management Suite Extension for Microsoft Exchange (TMSXE)
TMSXE allows end users to schedule meetings using their Microsoft Outlook clients and including room video systems.
Room resources in Microsoft Exchange are mapped to systems within TMS. When resources are booked in Exchange,
TMSXE provides TMS with the following information:
• User requesting the meeting
• Meeting subject
• All TMS associated resources
The TMS scheduling engine then uses conference templates to build the meeting and provides connection information
back through Exchange to the end user.
Recommended Deployment
Deploy a single instance of TMS for the organization, and leverage the integrated system navigator folder structure to
organize all endpoints and infrastructure devices. Even multinational and global organizations can benefit from a single
instance of TMS to facilitate video connections.
For Cisco BE 6000 deployments, TMS and all of its supporting components can be installed on a single Windows server
instance. This is called a TMS Regular Deployment and is subject to the following constraints:
• TMS Solution — TelePresence Management Suite (TMS), TelePresence Management Suite Provisioning Extension
(TMSPE), TelePresence Management Suite Extension for Microsoft Exchange (TMSXE), and an embedded
Microsoft SQL server all reside on a single virtual machine.
• TMS
◦ Maximum of 200 controlled systems
◦ Maximum of 100 concurrent participants
◦ Maximum of 50 concurrent ongoing scheduled conferences
• TMSXE
◦ Up to 50 endpoints bookable in Microsoft Exchange
• TMSPE
◦ Up to 1,000 Collaboration Meeting Rooms
Redundancy for TMS and TMS Extensions
Redundancy of TMS and its extensions is different from other components in the Preferred Architecture. TMS and TMSPE
operate in an active/passive node model instead of clustering.
Redundancy for TMS requires an external Microsoft SQL database on a separate server from the TMS application server.
This instance of SQL may be shared by other applications within the organization. Also necessary for redundancy to work
effectively, a network load balancer (NLB) must be deployed in front of the TMS/TMSPE application server. Because this
is outside the scope of a TMS deployment on the BE 6000, redundancy for TMS and its extensions is not included in the
Cisco PA for Midmarket Collaboration.
See the Cisco TelePresence Management Suite Installation and Upgrade Guide for details on larger deployments with full
redundancy for TMS and TMS extensions.
Benefits
The benefits of a properly configured and deployed TMS instance, with the software extensions, provide end users with a
user-friendly and feature-rich experience.
• Conferences for video, voice, and web participants are scheduled through a single unified interface.
• On supported endpoint devices, users can launch a conference session with One Button to Push (OBTP), according
to the device schedule.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 35
Applications
Cisco Prime Collaboration Provisioning Standard
Cisco Prime Collaboration Provisioning Standard provides a centralized provisioning interface that simplifies
administration of day-to-day activities, such as moves, adds, changes, and deletions (MACD) of user devices and
services in an organization (Figure 19).
Figure 19.
Cisco Prime Collaboration Provisioning Standard
Recommended Deployment
Deploy Cisco Prime Collaboration Provisioning Standard on the primary BE6000 server. A single instance of Cisco Prime
Collaboration Provisioning Standard can support the entire organization.
Benefits
• A consistent, unified approach simplifies the management of multiple Cisco collaboration technologies such as
Cisco Unified IP Phones, Cisco Unified CM, and other application servers.
• Features such as bulk-based provisioning, phone MACDs, and consolidated views simplify user and service-related
configuration and administration.
• A self-service portal eases support by enabling users to make authorized changes.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 36
Appendix
Appendix
Product List
This product list identifies the Cisco products in the Preferred Architecture for Midmarket Collaboration, along with their
relevant software versions.
Product
Product Description
Recommended Software Version
Cisco Unified Communications Manager
and IM and Presence Service
Call control, instant messaging, and presence services
10.5
Cisco Unity Connection
Voicemail services
10.5
Cisco Expressway-C and Expressway-E
Mobile and remote access and business-to-business
communications
8.2
Cisco Contact Center Express
Customer interaction management services
10.5
Cisco Prime Collaboration Provisioning
Standard
Provisioning and monitoring services for voice and video
deployments
10.5
Cisco TelePresence Conductor
Video conferencing resource management
2.3
Cisco TelePresence Server
Audio and video conferencing resources
4.0
Cisco ISR G2
PSTN gateway, SRST, and external connectivity to the Internet
IOS 15.3.3M
Cisco Unified IP Phone 7800 Series
General office use, multi-line phone
10.1(1.9)
Cisco Unified IP Phone 8800 Series
General office use
10.2(1)
Cisco Unified IP Phone 8831
IP conference phone
9.3(3)
Soft client with integrated voice, video, voicemail, and instant
messaging and presence functionality for mobile devices and
personal computers
Jabber for Windows: 9.7.1
1
Cisco Jabber
Jabber for Mac: 9.6
Jabber for iPhone and iPad: 9.6.2
Jabber for Android: 9.6.1
Cisco DX Series
Personal TelePresence endpoint for the desktop
10.2(1)
Cisco EX Series
Personal TelePresence endpoint for the desktop
TC7.2
Cisco TelePresence MX Series
TelePresence multipurpose room endpoint
TC7.2
Cisco TelePresence SX Series
Integrator Series TelePresence endpoint
TC7.2
1. Minimum Cisco Jabber version required to support Cisco Expressway mobile and remote access capabilities.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 37
Appendix
Licensing Options
This table identifies the licensing options.
License Type
User Connect
Licensing (UCL)
Essential
User Connect
Licensing (UCL)
Basic
User Connect Licenses
(UCL) Enhanced /
Enhanced Plus
Unified Workspace
Licensing (UWL)
Standard
Unified Workspace
Licensing (UWL)
Professional
Number of User
Profiles
1
1
1
1
1
Supported Device
Type
Analog / Voice
Voice
Video
Video
Video
Number of
Supported Devices
Single
Single
Single / Dual
Multiple1
Multiple1
Jabber IM and
Presence2
Yes
Yes
Yes
Yes or WebEx
Yes or WebEx
Jabber Voice and
Video Client
—
—
Yes
Yes
Yes
Personal Video
Conference Bridge
—
—
—
Optional
Yes3, screen licenses for
50 users or more
Voice Messaging
Optional
Optional
Optional
Yes
Yes
WebEx Meetings
Optional
Optional
Optional
Optional
Yes, 1:10 Meeting Center
ports
Contact Center
Optional
Optional
Optional
Optional
Yes, 1:25 Standard
Express Agent
—
—
—
BE6K-UCL-ENH / BE6KUCL-ENHP
BE6K-UWL-BE
CUWL-PRO-K9 NEWUWL-PRO
1. Cisco UWL enables the first 10 devices per user on installation. If more devices are required, contact [email protected]
2. Available to all users when using the Cisco Unified Communications Manager IM and Presence Service on the BE 6000 server. One-year
WebEx Messenger subscriptions are available as an option for Cisco UWL users.
3. Cisco UWL Professional enables a 4-port personal video conference per user with the purchase of 50 or more Cisco UWL Professional licenses.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 38
Appendix
Sample Order
This sample order is for a deployment with redundant Cisco BE 6000 servers for an organization with 250 users. The
products in the Bill of Materials (BOM) were chosen to address the midmarket price point and to enable organizations to
scale. Cisco has a range of products that provide various features and functionality. Organizations can choose different
products based on their business needs.
Figure 20.
Components in the Sample Deployment
Table 11.
Components in the Sample Deployment
Product
Quantity
Cisco BE 6000 HD servers for redundancy
2
Cisco Multiparty Media 400v
1
Cisco TelePresence Server running on TS 7010
1
Cisco ISR 3900 series for headquarters with CUBE licenses
1
Cisco ISR 2900 series for branches with 25 SRST licenses each and PSTN interfaces
2
Cisco TelePresence SX20 room system
1
Cisco TelePresence MX300 G2 systems
2
Cisco TelePresence EX90 desktop system
1
Cisco DX70 collaboration endpoint
11
Cisco Unified IP Phone 8811 multi-line phones
228
Cisco Unified IP Phone 6901 single-line phones for public areas in the organization
25
User, Agent, and Server licenses
—
Note:
Licensing for the Cisco TelePresence Server 7010 is not included in this BoM.
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 39
Appendix
Sample Bill of Materials
Infrastructure
Item
Description
Quantity
BE6K-STBDL-PLS-K9=
Cisco BE6000 High Density Server Export Restricted SW
2
CON-SNT-BE6KSTBL SMARTNET 8X5XNBD CSC BE 6000UCS C Serv TRC39.0 SWHype
2
CAB-9K12A-NA Power Cord 125VAC 13A NEMA 5-15 Plug North America
4
UC-RAID-9271 MegaRAID 9271-8i + Battery Backup for C240 and C220
2
LIC-SW-VMVCS-K9 Software Release Key for Encrypted Virtual VCS Application
2
LIC-VCS-10+ Video Comm Server 10 Add Non-traversal Network Calls
2
BE6K-SW-9X10X Cisco Business Edition 6000 - Software App Version 9.X 10.X
2
VMW-VS5-SNS Cisco UC Virt. Hypervisor 5.x - SnS
2
UC-PSU-650W 650W Power Supply Unit For UCSC C220 Rack Server
4
CIT-HDD300GI2F105 300GB 6Gb SAS 15K RPM SFF HDD/Hot Plug/Drive Sled Mounted
CIT-PCIE-IRJ45 Intel i350 Quad Port 1Gb Adapter
CTI-VCSC-BE6K-PAK Config Only E-Delivery VCS Control PAK PID
2
2
R2XX-RAID5 Enable RAID 5 Setting
2
LIC-VCSE-5+ Video Communication Server - 5 Traversal Calls
VMW-VS5-HYP-K9 Cisco UC Virt. Hypervisor 5.x (2-socket)
UC-MR-1X082RY-A 8GB DDR3-1600-MHz RDIMM/PC3-12800/Dual Rank/1.35v
Description
CISCO3925-V/K9
2
LIC-VCS-GW Enable GW Feature (H323-SIP)
CIT-CPU-E5-2665 2.40 GHz E5-2665/115W 8C/20MB Cache/DDR3 1600MHz
Item
16
Cisco 3925 Voice Bundle PVDM3-64 UC License PAK FL-CUBE25
4
2
2
12
Quantity
1
CON-SNT-3925V SMARTNET 8X5XNBD Cisco 3925 Voice Bundle UC License PAK
1
S39UK9-15303M Cisco 3925-3945 IOS UNIVERSAL
1
SL-39-SEC-K9 Security License for Cisco 3900 Series
FL-SRST Cisco Survivable Remote Site Telephony License
PWR-3900-AC Cisco 3925/3945 AC Power Supply
PWR-3900-AC/2 Cisco 3925/3945 AC Power Supply (Secondary PS)
CAB-AC AC Power Cord (North America) C13 NEMA 5-15P 2.1m
1
1
1
1
1
C3900-SPE100/K9 Cisco Services Performance Engine 100 for Cisco 3925 ISR
1
FL-CUBEE-25 Unified Border Element Enterprise License - 25 sessions
1
PI-MSE-PRMO-INSRT Insert Packout - PI-MSE
1
SL-39-IPB-K9 IP Base License for Cisco 3925/3945
1
SL-39-UC-K9 Unified Communication License for Cisco 3900 Series
1
3900-FANASSY Cisco 3925/3945 Fan Assembly (Bezel included)
1
HWIC-BLANK Blank faceplate for HWIC slot on Cisco ISR
1
ISR-CCP-EXP Cisco Config Pro Express on Router Flash
1
MEM-3900-1GB-DEF 1GB DRAM (512MB+512MB) for Cisco 3925/3945 ISR (Default)
1
MEM-CF-256MB 256MB Compact Flash for Cisco 1900 2900 3900 ISR
1
PVDM3-64 64-channel high-density voice and video DSP module
1
SM-D-BLANK Blank faceplate for DW slot on Cisco 2951 and 3925
1
SM-S-BLANK Removable faceplate for SM slot on Cisco 290039004400 ISR
1
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 40
Appendix
Item
Description
Quantity
C2951-VSEC/K9
Cisco 2951 Voice Sec. Bundle PVDM3-32 UC&SEC Lic FL-CUBE10
2
CON-SNT-2951VSEC SMARTNET 8X5XNBD Cisco 2951 Voice Sec. Bundle UC and SEC
S2951UK9-15303M Cisco 2951 IOS UNIVERSAL
FL-SRST Cisco Survivable Remote Site Telephony License
FL-CME-SRST-25 Communication Manager Express or SRST - 25 seat license
VIC2-2FXO Two-port Voice Interface Card - FXO (Universal)
PWR-2921-51-AC Cisco 2921/2951 AC Power Supply
CAB-AC AC Power Cord (North America) C13 NEMA 5-15P 2.1m
FL-CUBEE-5 Unified Border Element Enterprise License - 5 sessions
PI-MSE-PRMO-INSRT Insert Packout - PI-MSE
SL-29-IPB-K9 IP Base License for Cisco 2901-2951
2
2
2
2
2
2
2
4
2
2
SL-29-UC-K9 Unified Communication License for Cisco 2901-2951
2
HWIC-BLANK Blank faceplate for HWIC slot on Cisco ISR
6
ISR-CCP-EXP Cisco Config Pro Express on Router Flash
2
MEM-2951-512MB-DEF 512MB DRAM (1 512MB DIMM) for Cisco 2951 ISR (Default)
2
MEM-CF-256MB 256MB Compact Flash for Cisco 1900 2900 3900 ISR
2
PVDM3-32 32-channel high-density voice and video DSP module
2
SL-29-SEC-K9 Security License for Cisco 2901-2951
SM-S-BLANK Removable faceplate for SM slot on Cisco 290039004400 ISR
2
4
Item
Description
Quantity
CTI-7010-TPSMK2-K9
Cisco TelePresence Server 7010 Mk2
1
CON-ECDN-7KTPSMK2 ESS WITH 8X5XNBD Cisco TelePresence Server 7010 Mk2
1
PWR-CORD-US-C US power cord
1
LIC-AESCDN6-K9 AES and HTTPS Enable Upgrade
1
LIC-7010-TPSRV-K9 License Key For 7010 TelePresence Server software Image
SW-7010-V4.X-K9 Software Image for 7010 TelePresence Server v4.x
Item
Description
VTS-LSVR-M3
Cisco Multiparty Media 400v HW-only
1
1
Quantity
1
CON-SNT-VTSLSVR3 SMARTNET 8X5XNBD Cisco Multiparty Media 400v TelePresence
1
CIT3-RAID-MZ-220 Cisco UCS RAID SAS 2008M-8i Mezz Card for C220 (0/10/10)
1
CIT3-MR-1X082RY-A 8GB DDR3-1600-MHz RDIMM/PC3-12800/Dual Rank/1.35v
CIT3-PSU-450W 450W power supply for C-series rack servers
CIT3-A03-D300GA2 300GB 6Gb SAS 10K RPM SFF HDD/hot plug/drive sled mounted
R2XX-RAID1 Enable RAID 1 Setting
8
2
2
1
CIT3-CPU-E5-2667B 3.30 GHz E5-2667 v2/130W 8C/25MB Cache/DDR3 1866MHz
2
CAB-9K12A-NA Power Cord 125VAC 13A NEMA 5-15 Plug North America
2
Cisco Preferred Architecture for Midmarket Collaboration
PAGE 41
Appendix
Item
Description
Quantity
L-VTS-UPG-PAK
Cisco Virtual Telepresence Server e-delivery Upgrade PAK
1
CON-ECMU-LVTSUP SWSS UPGRADES Cisco Virtual Telepresence Server e-deli
L-AES-VTS-K9 AES and HTTPS option for VTS
L-VTS-TPSINTOP Order L-VTS-UPG-PAK for e-Delivery Virtual TS Interop Lic
1
1
1
Licensing
Cisco BE 6000 and User Licenses
Item
Description
Quantity
R-CBE6K-K9
Cisco Business Edition 6000-Electronic SW Delivery-Top Level
1
CON-NEMU-RCBE6KK SNTC SWSS UPGRADES Cisco Business Editi
BE6K-SW-10.X Business Edition 6000 v10 export restricted software
BE6K-START-UWL25 BE 6000 - User License Starter Bundle with 25 UWL Licenses
BE6K-UCL-ESS Cisco Business Edition 6000 - Essential User Connect License
BE6K-UCL-TP-RM Cisco Business Edition 6000 - Telepresence Room System User
BE6K-UWL-STD Cisco Business Edition 6000 - Workspace License Standard
1
1
1
25
3
175
JABBER-TABLET Jabber for iPad and Android Tablet
25
JABBER-DESKTOP Jabber for Desktop for PC and Mac
25
CCX-10-5E CCX 10 Enhanced 5 seat Promo Bundle
1
EXPWY-VE-C-K9 Cisco Expressway-C Server Virtual Edition
1
EXPWY-VE-E-K9 Cisco Expressway-E Server Virtual Edition
1
SW-EXP-8.X-K9 Software Image for Expressway with Encryption Version X8
LIC-EXP-RMS Expressway Rich Media Session
CON-NEMU-LICEXPRM SNTC SWSS UPGRADES Expressway Rich Media Session
1
10
10
CCX-10-E-SVR-LIC CCX 10.0 ENH Server License
1
UCM-10X-ESS-UCL BE6K UCM 10X Essential User Connect License - Single
25
CON-NEMU-UCMESSUC SNTC SWSS UPGRADES BE6K UCM 10X Essenti
25
LIC-EXP-AN Enable Advanced Networking Option
1
PC-10X-STANDARD-K9 Prime Collaboration Standard 10.x
UCM-10X-TP-UCL BE6K UCM 10X Telepresence Room User Connect License - single
CON-NEMU-UCMUCLTP SNTC SWSS UPGRADES BE6K UCM 10X Telepre
LIC-EXP-SERIES Enable Expressway Series Feature Set
1
3
3
2
JABBER-TABLET-RTU Jabber for Tablet Right to Use
1
CCX-10-PAK CCX 10.0 autoexpanded PAK
1
LIC-EXP-E-PAK Expressway Series Expressway-E PAK
1
LIC-EXP-TURN Enable TURN Relay Option
1
LIC-EXP-E Enable Expressway-E Feature Set
UCXN-10X-SCPORTS BE6K - Unity Connection 10x - VM Speech Connect Ports
UCXN-10X-UWLSTD BE6K - Unity Connection 10x - VM UWL Standard License
1
2
200
LIC-EXP-GW Enable GW Feature (H323-SIP)
2
JABBER-DSK-K9-RTU Jabber for Desktop Right to Use
1
BE6K-UXL-START BE6K Starter Pack - Single Fulfillment Enforcement
LIC-SW-EXP-K9 License Key Software Encrypted
Cisco Preferred Architecture for Midmarket Collaboration
1
2
PAGE 42
Appendix
BE6K-PAK Cisco Business Edition 6000 - PAK - Single Fulfillment
CCX-10-N-E-LIC CCX 10.0 ENH Seat Qty 1 LICENSE ONLY
CON-NEMU-CCX10NEL SNTC SWSS UPGRADES CCX 10.0 ENH Seat Qty 1 LICENSE ONLY
UCM-10X-UWLSTD BE6K UCM 10X CUWL BE Users - Single Fulfillment
CON-NEMU-UCMUWLST SNTC SWSS UPGRADES BE6K UCM 10X CUWL BE
WEBEX-MC-BE-PAK WebEx Cloud Provisioning - Enabling MC and/or IM for BE 6K
WBX-IM1-NH-UWL Included WebEx Messenger Users ( 1 Year Term)
1
5
5
200
200
1
200
Cisco Contact Center Express High Availability License
Item
Description
Quantity
CCX-10-ADD-K9
CCX 10.0 Add-on Licenses
1
CON-NEMU-CCX10AK9 SNTC SWSS UPGRADES CCX 10.0 Add-on Licenses
1
CCX-10-EHA-LIC CCX 10.0 ENH HA LICENSE ONLY
CCX-10-PAK CCX 10.0 autoexpanded PAK
1
1
Cisco UWL Professional Personal Multiparty and Cisco Expressway Licenses
Item
Description
CUWL-PRO-K9
Unified Workspace Licensing - Top Level for PRO - 9.x/10.x
CON-NEMU-CUWK9PRO SNTC SWSS UPGRADES Unified Workspace Li
LIC-PM-V-USR-UWL Personal Multiparty Video for Virtual Machine
Quantity
1
1
50
JABBER-DESKTOP Jabber for Desktop for PC and Mac
50
JABBER-TABLET Jabber for iPad and Android Tablet
50
SW-VTS-V4.X-PMP-K9 Software Image v4.X for Virtual TelePresence Server
CCX-10-NEW-STD-UWL CCX 10.x NEW STANDARD for UWL
CCX-10-S-SEAT1-UWL CCX 10.x STD Seat Qty 1 (agent or supervisor) for UWL
SME-10-UWL Session Manager 10.0 Auto-expanding user for licensing
2
1
2
10
JABBER-DSK-K9-RTU Jabber for Desktop Right to Use
1
JABBER-TABLET-RTU Jabber for Tablet Right to Use
1
LIC-VTS-PMP-PAK PAK for e-Delivery Virtual TS Lic
LIC-VTS-PMPUWL-1SL Cisco TelePresence Server Resource License
LIC-AES-VTS-PMP-K9 AES and HTTPS option for VTS
LIC-EXP-AN Enable Advanced Networking Option
LIC-EXP-SERIES Enable Expressway Series Feature Set
LIC-EXP-TURN Enable TURN Relay Option
LIC-SW-EXP-K9 License Key Software Encrypted
LIC-VTS-PMP-INTOP TelePreence Server Third Party Interop Key
1
10
2
6
12
6
12
2
LIC-VTS-PMP-K9 Cisco VM TelePresence Server Release Key
2
UCXN-10X-SC-PORTS Unity Connection 10.x SpeechConnect Ports
2
UCXN-10X-UWL-PRO Unity Connection 10.x CUWL PRO Users
WBX-MC1-NH-UWL Included WebEx MC/MTGS Named Host Users (1 Year Term)
UCM-10X-UWL-PRO UC Manager 10.x CUWL PRO Users
VTS-PMP-K9 Cisco VM Telepresence Server
SW-EXP-8.X-K9 Software Image for Expressway with Encryption Version X8
Cisco Preferred Architecture for Midmarket Collaboration
50
50
50
2
1
PAGE 43
Appendix
LIC-EXP-E Enable Expressway-E Feature Set
6
LIC-EXP-E-PAK Expressway Series Expressway-E PAK
1
LIC-EXP-GW Enable GW Feature (H323-SIP)
UWL-PRO-PAK CUWL PRO 9.x PAK
12
1
LIC-UWL-PRO-A Services Mapping SKU Under 1K UWL PRO users
50
CON-NEMU-LICUWLPA SNTC SWSS UPGRADES Services Mapping SKU
50
WBXMTSVR2-UWLUSRK9 WebEx Meetings Server 2.x Users
WBXMTSVR-UWL-K9 Webex Meetings Server 2.x Software Kit
50
1
EXPWY-VE-E-K9 Cisco Expressway-E Server Virtual Edition
6
EXPWY-VE-C-K9 Cisco Expressway-C Server Virtual Edition
6
LIC-TMS-APL-S80100 TMS Appliance Lic Key Base Software Image Used During DF
SW-TMS-14.X-K9 TMS Base Software Image Version 14.X
WBX-IM1-NH-UWL Included WebEx Messenger Users ( 1 Year Term)
WEBEX-UWL-P-PAK WebEx PAK for CUWL PRO
NEW-UWL-PRO New CUWL Professional Edition User 1 User
UCAPPS-SW-10.X-K9 Version 10.x Software Kit
1
1
50
1
50
1
Cisco TelePresence Conductor Licenses
Item
R-VMCNDTRM-K9
Description
Quantity
Mid-market (Select) Virtual TP Conductor - 50 Call Sessions
1
CON-TPBS-RVMCNDK9 TP BASE Mid-mrkt Virt TelePres Cond-50 Call Ses
SW-CNDTR-V2.X-K9 Cisco TelePresence Conductor base software image v2.X
LIC-CNDTR-C50 Conductor 50 call sessions license
LIC-CNDTR-CL Conductor clustering support
LIC-SW-VMCNDTR-K9 Software Release Key for Virtual Conductor
LIC-VMCNDTR-PAK PAK for virtual Conductor
Note:
1
1
1
1
1
1
After the first 50 Cisco UWL Pro licensed users, customers are entitled to a Cisco TelePresence Conductor for
4-port personal video conferences. The additional TelePresence Conductor is for redundancy.
Cisco TelePresence Management Suite Licenses
Item
Description
Quantity
CTI-TMS-SW-K9
Cisco TelePresence Management Suite - Includes 10 Systems
1
CON-NEMU-CTITMSSW SNTC SWSS UPGRADES TMS Mgmt Suite Svr Lic-Incl 10 Syss
LIC-TMS-WXOT Cisco TMS WebEx Integration
1
1
LIC-TMS-10-INCL Cisco TMS - included 10 System License
1
LIC-TMS-SW-PAK TMS PAK for Configuration Use
1
SW-TMS-14.X-K9 TMS Base Software Image Version 14.X
1
LIC-TMS-APL-S80100 TMS Appliance Lic Key Base Software Image Used During DF
Cisco Preferred Architecture for Midmarket Collaboration
1
PAGE 44
Appendix
Cisco Unified IP Phones and TelePresence Video Endpoints
Item
Description
Quantity
CTS-SX20-PHD4X-K9
SX20 Quick Set HD NPP 4x PHDCam 1 mic remote cntrl
1
CON-ECDN-SX2PHD4X ESS WITH 8X5XNBD SX20 Qk Set HD NPP4x PHDCam1 mic RC
PWR-CORD-US-A Pwr Cord US 1.8m Black YP-12 To YC-12
CTS-RMT-TRC5 Remote Control TRC 5
1
1
1
LIC-SX20-PR Premium Resolution Option for SX20
1
LIC-SX20-DD Dual Display Option for SX20
1
BRKT-PHD4X-MONITR Bracket mounting for 4x PHDCam to monitor
CAB-2HDMI-3M HDMI to HDMI cable
CAB-HDMI-PHD4XS2 Custom 4xcamera cable; HDMI Control and Power (3m)
CTS-PHD1080P4XS2+ PrecisionHD Camera 1080p 4x SX20 auto expand
CTS-SX20CODEC-K9 SX20 Codec - encrypted
LIC-S52010-TC-K9 License Key Software Encrypted
LIC-SX20 SX20 License Key
LIC-SX20-HD High Definition Feature for SX20
LIC-SX20-NPP SX20 Natural Presenter Package (NPP) Option
CTS-QSC20-MIC+ Performance Mic - for auto expand only
SW-S52010-TC7-K9 SW Image for SX20 and MX200/300 (2nd gen) series endpoints
1
2
1
1
1
1
1
1
1
1
1
Item
Description
Quantity
CTS-MX300-K9
Cisco TelePresence MX300 55 Gen 2 PHD 1080p 8x Touch Mic
2
CON-ECDN-CTSMX300 ESS WITH 8X5XNBD Cisco TelePres MX300 55 Gen2 PHD 1080p
CTS-MX300-FSK Cisco TelePresence MX300 Gen 2 Floor Stand Kit
LIC-MX300-PR Cisco MX300 Gen 2 Premium Resolution SW Feature Option
PWR-CORD-US-E MX - Pwr cable United States 45m
2
2
2
2
LIC-TC-CRYPTO-K9 License key to activate sw encryption module
2
CTS-CTRL-DVX-10+ Touch 10 auto expand
2
CAB-DV10-8M- 8 meter flat grey Ethernet cable for Touch 10
CAB-NET-EN5M- Ethernet cable for MX300
CTS-MX300-UNIT MX300 Gen 2 integrated codec LCD camera speaker mic
SW-S52010-TC7-K9 SW Image for SX20 and MX200/300 (2nd gen) series endpoints
CAB-DVI-VGA-3.5MM- SX 3.5mm ster. jack-ster.jack/DVI-VGA cab6m auto expand
CTS-QSC20-MIC+ Performance Mic - for auto expand only
Cisco Preferred Architecture for Midmarket Collaboration
2
2
2
2
2
4
PAGE 45
Appendix
Item
Description
Quantity
CTS-EX90-K9
EX90 - NPP Touch UI
1
CON-ECDN-CTS-EX90 ESS WITH 8X5XNBD EX90 base system including NPP option
PWR-CORD-US-A Pwr Cord US 1.8m Black YP-12 To YC-12
1
1
LIC-EX90-DD EX90 DD Option
1
LIC-EX90-PR EX90 PR Option
1
LIC-S52000-TCX.XK9 License Key Software Encrypted
1
LIC-ECXX-NPP EX NPP option
1
CTS-CTRL-DV8 Touch Control for EX Series with cradle and handset
1
LIC-EX90 EX90 Product License Key
SW-S52000-TC7-K9 SW Image for C/EX/Profile/MX(1st gen) series endpoints
1
1
Item
Description
Quantity
CP-DX70-W-K9=
Cisco Desktop Collaboration Experience DX70 (White)
11
CON-SNT-CPDX70WK SMARTNET 8X5XNBD Cisco Desktop Collaboration Experience D
CP-PWR-CORD-NA Power Cord North America
11
11
Item
Description
Quantity
CP-6901-C-K9=
Cisco UC Phone 6901 Charcoal Standard handset
25
CON-SNT-6901CHST SMARTNET 8X5XNBD Cisco Unified IP Phone 6901 CharcoalST
Item
CP-8811-K9=
25
Description
Quantity
Cisco IP Phone 8811 Series
238
CON-SNT-CP8811K9 SMARTNET 8X5XNBD Cisco IP Phone 8811 Series
Cisco Preferred Architecture for Midmarket Collaboration
238
PAGE 46
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement