preferred architecture for enterprise collaboration · •what is "preferred...
TRANSCRIPT
Preferred Architecture for Enterprise Collaboration
Part 2: Collaboration Edge, Core Applications and SizingGlen Lavers, Luca Pellegrini, Matthew Jordy, Laurent Pham
BRKCOL-2421
Preferred Architecture for Enterprise Collaboration
There are two Preferred Architecture for Enterprise Collaboration sessions at
Cisco Live this week:
» BRKCOL-2420
Part 1: Call Control, ConferencingWednesday, June 10th @ 8 AM
» BRKCOL-2421
Part 2: Collaboration Edge, Core
Applications, and SizingWednesday, June 10th @ 1 PM
Cisco Live Session Details
You arehere
• What is "Preferred Architecture"?
• Collaboration Edge
• Expressway• B2B Communications
• Mobile and Remote Access
• Design Considerations
• PSTN Access• Voice and Video Gateways
• Cisco Unified Border Element
• Design Considerations
Agenda
• Core Applications
• Unity Connection
• Prime Collaboration Deployment
• Prime Licensing Manager
• Simplified Sizing
• Call Control (Communications Manager and IM & Presence)
• Conferencing (TMS, Telepresence Server, Conductor)
• Collaboration Edge
• Applications
What is “Preferred Architecture”?
The Preferred Architecture for Collaboration process was created to simplify selling and designing. It is a design where Cisco experts make the design decisions for you following the 80/20 rule. Its advise from the SRND you would give your best friend if they asked you “just tell me what I need to do”.
What does the PA aim to accomplish?
Simplify• Simplify selling and deployment
Empower
• Allow generalists to understand collaboration deployment and what is preferred
Clarify• Reduce complexity of overall deployment choices
Guidance
• Give existing customers a reference to move their deployment toward
Influence• Feed simplification (and design issues) back to Development
PA Process Figure it out:
Define Collaboration Preferred Architecture
Build and validate:
Build it in the lab and validate concepts
Extend:
Move it into GB test beds, Cisco on Cisco,
Alpha and EFT process
Define
Define additional Preferred Architectures (Voice, Video)
Write it down:
Document Preferred Architectures for the
field and partners
Feedback:
Feed gaps found during the “build and validate” phase back into product
teams
Post-Sales
process
Pre-Sales
Process
Collaboration Preferred Architectures & CVDs
PA OverviewPA CVD
Cisco Validated Design
• Design Overview Document
• Targeted to Presales
• What (w/ Some Why)!
• Detailed Design and Deployment
Guidance
• Post Sales Design and Deployment
• What, Why, and How!
• Process Driven Guide
www.cisco.com/go/cvd/collaboration !
Cisco Validated Design
Applications
• Detailed, Deployment Guidance
• Post Sales Design and Deployment
• What, Why, and How!
• Process Driven Guide
• Plugs into the PA CVD
Post-Sales
Process
Coming
Soon!!!
Mid Market PA/CVD Document Mapping!
www.cisco.com/go/cvd/collaboration
www.cisco.com/go/ucsrnd
Use Case PA Overview CVD
Voice Only PA for Midmarket Voice Unified Comm. using BE6000 CVD
Collaboration Edge Using BE6000 CVD
Standalone Video PA for Video Video Conferencing using BE6000 CVD
Collaboration Edge Using BE6000 CVD
Full Collaboration PA for Midmarket
Collaboration
Unified Comm. using BE6000 CVD
Video Conferencing using BE6000 CVD
Collaboration Edge Using BE6000 CVD
Helpdesk using Cisco UCCX CVD
*
* Fits both Mid-Market and Enterprise
Enterprise PA/CVD Document Mapping!
Use Case PA CVD
Voice N/A N/A
Standalone Video PA for Video Video Conferencing
using BE6000 CVD
Full Collaboration PA for Enterprise
Collaboration
PA for Enterprise
Collaboration CVD
www.cisco.com/go/cvd/collaboration
www.cisco.com/go/ucsrnd
*
* Fits both Mid-Market and Enterprise
Preferred Architecture for Collaboration Enterprise Cisco Validated Design (CVD)
• Functions: Dial Plan (Dialing Habits, Endpoints/ILS/GDPR), Trunking, SRST, CTI, DNS, Cert Mgmt, Provisioning, EM
Call ControlUCM, IM&P, ISR, CUBE
• Functions: Ad hoc, Rendezvous, Scheduled, CMR, CMR Hybrid, Personal Multiparty
ConferencingUCM, Conductor, TS, TMS
• Functions: Mobile Remote Access (MRA), B2B, IM&P Federation, PSTN Access, ISDN Video
EdgeUCM, Expressway, CUBE, ISR
• Functions: Applications and Tools: VM Deployment, Licensing, Voice Messaging
ApplicationsUcx, PCD, PLM
• Functions: Sizing numbers for products built on a set of calculated assumptionsSizing
Architecture:
Component
Role, HA,
Security,
Scalability
Deployment:
Process and
Configuration
Sizing
• Recommendation: Centralized Call Processing Model (Single Call Processing Cluster)
• Full-Mesh Distributed Call Processing Deployment Model (Multiple Call Processing clusters) may be required. This model is based on multiple iterations of the Centralized Call Processing Deployment Model
Call ControlArchitecture and Deployment Models: Simplification
IM&P
Branch1 Branch2
UCM IM&P
Branch1 Branch2
UCM IM&P
Branch1 Branch2
UCM
• Single Collaboration Design (Voice, Video, IM&P, Conferencing, Edge)
• Collaboration-friendly dial plan which makes easy to add video to voice, IM&P to voice and video
• Simplified: deployment model, design, dial-plan, video architecture, IM&P integration, sizing, etc.
• Modular architectural approach for scalability
• Add additional services avoiding re-configuration costs
• Future Proof the Architecture
• Customizing the PA??? GO TO THE SRND FOR GUIDANCE
Preferred ArchitecturesBenefits
Collaboration Edge
Collaboration Edge
• Connect to customers and partners, independent of the technology they are implementing and the public network they are using.
• Provide for a resilient, flexible and extendable architecture.
• Provide any hardware and software client with the ability to access any public network (Internet and PSTN).
• Provide secure VPN-less access to collaboration services for Cisco mobile and remote clients and endpoints.
Design Objectives
Introducing Cisco Collaboration Edge ArchitectureIndustry’s Most Comprehensive Any-to-Any Collaboration Solution
All the capabilities of Cisco Any-
to-Any collaboration to-date• TDM & analog gateways
• ISDN Video gateways
• Session border control
• Firewall traversal
• Standards-based & secure
TeleworkersMobile
Workers
B2B
Consumers
3rd Parties
Analog Devices
Branch Office
PSTN or IP PSTN
TDM or IP PBX
Cloud Services
Overview
SRV Records for B2B and MRA
SRV record format for SIP and H.323 (RFC 2782)
Name of the
service
Protocol and
domain name
(TCP, UDP...)
DNS Time-To-Live: how much
time the server caches the
record before it flushes the
cache
DNS Class.
Always “IN”
Priority: Lowest
priority means
“preferred”.
Weight: load-
balances records
with same
priority
Port: TCP or
UDP port for
the service
Targed: hostname or
IP Address for the host
Providing the service
_sip. _tcp.example.com86400 IN 10 60
5060expe.example.comSRV
_collab-edge. _tls.example.com 8443
Service Discovery
Bigbox
Smallbox
_sips._tcp.example.com?
60%
40%
Backupbox
_sips._tcp.example.com. 86400 IN SRV 10 60 5061 bigbox.example.com.
_sips._tcp.example.com. 86400 IN SRV 10 40 5061 smallbox.example.com.
_sips._tcp.example.com. 86400 IN SRV 20 0 5061 backupbox.example.com.
Dial:
60%
40%
Bigbox
Backupbox
Dial:
_sips._tcp.example.com. 86400 IN SRV 10 60 5061 bigbox.example.com.
_sips._tcp.example.com. 86400 IN SRV 10 40 5061 smallbox.example.com.
_sips._tcp.example.com. 86400 IN SRV 20 0 5061 backupbox.example.com.
Smallbox
Service Discovery
Cisco Collaboration SRV Records SRV record format for SIP and H.323 (RFC 2782)
SIP B2B _sips._tcp.domain 5061 TLS
_sip._tcp.domain 5060 TCP
_sip._udp.domain 5060 UDP
H.323 B2B _h323ls._udp.domain 1719 RAS
_h323cs._tcp.domain 1720 H.225
MRA _collab-edge._tls.domain 8443 Jabber login
_xmpp-server._tcp.domain 5269 XMPP Federation
Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. 23
DMZEnterprise Network
1. Expressway-E is the traversal server installed in DMZ. Expressway-C is the traversal client installed inside the enterprise network.
2. Expressway-C initiates traversal connections outbound through the firewall to specific ports on Expressway-E with secure login credentials.
3. Once the connection has been established, Expressway-C sends keep-alive packets to Expressway-E to maintain the connection
4. When Expressway-E receives an incoming call, it issues an incoming call request to Expressway-C.
5. Expressway-C then routes the call to Unified CM to reach the called user or endpoint
6. The call is established and media traverses the firewall securely over an existing traversal connection
Unified
CM
Firewall Expressway-E FirewallExpressway-C
Internet
Outside Network
Media
Signaling
Expressway Firewall Traversal Basics
Business-to-Business Communications
B2B Dial Plan
• By default every line has a directory number
• By assigning one or more alphanumeric SIP URI to a line, a user’s line can be reached by dialing:
• <directory number>@domain
• <alphanumeric SIP URI>@domain
• This is independent from the phone/videodevice model type
Numbers and alphanumeric SIP URIs together on CUCM
Unified CM ExpEExpC
Internet
Unknown
edge
B2B Call Flow Single Edge SIP to SIP call
DNSHierarchy
Expressway-C
Expressway-E
VCS-E
Calls [email protected]
Forward SIP Invite to companyB.com using IP address received via DNS
Sends SIP 200 OK
VCS-C
COMPANY B
Internet
COMPANY A
B2B Call Flow
• SIP (TLS,TCP, UDP) and H.323 are enabled globally
• Expressway always tries SIP TLS/TCP/UDP or H.323 based on the native protocol
• For SIP: Media encryption mode can be forced. Auto: depends on endpoints request only. Best Effort: will fallback to unencrypted if encryption is not available
SIP TLS, TCP, UDP or H.323?
Expressway-E
DNS Zone
Outbound CallsMultiple Edges
Internet
HQ San Jose
Branch Office RCD
Company B
CUCM IM&P
Expressway-E_SJC
Expressway-E_RCD
Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. 29
Outbound CallsCalling Search Space
SJC_B2B
Partition XPY-C_SJC
SJC_B2BSJC_Internet
SIP Route Pattern Route List RL_Internet_SJC
RCD_B2B
Partition
RCD_B2BRCD_Internet
Phone in SJC
Phone in RCD
Calling Search Space SIP Route Pattern Route List RL_Internet_RCD
Trunk_To_
XPY-C_RCD
XPY-C_SJC
XPY-C_RCD
XPY-C_RCD
XPY-C_SJC
Trunk_To_
XPY-C_SJC
XPY-C_RCD
*.*
*.*
Route Groups
Route Groups
Inbound CallsMultiple Edges
Company A Site 2
Company A Site 1
Internet
Edge 1
Edge 2
Looking for
_sip._tcp.companya.com
Edge 1 or Edge 2?
CUCM cluster
Inbound Calls
• If the edges are in the same region, resolving the SRV records into multiple edges with same priority and weight would allow load-balancing
• If one edge has to be used as a backup, SRV records can have higher priority for the active edge, and a lower priority for the stand-by edge
• If the edges are on different regions, two mechanisms could be put in place• Routing based on the minimal distance between the edge and the calling device (maximizes
quality) – based on GeoDNS: preferred
• Routing based on the minimal distance between the edge and the called device (minimizes costs) – GeoDNS not required: alternative (covered in the PA doc)
Multiple Edges
Inbound CallsMinimal distance between the calling device and nearest edge
Internet
Company A US Site
Company B
US Site
WAN
Company A
EMEA Site
CUCM cluster
Inbound Calls
• Geo DNS is a service delivered by many Internet organization, such as Godaddy, Amazon Route 53 and others, which allow to forward the inbound call to the edge which is nearest to the calling device
• We’ve chosen Amazon Route 53 as an example but this is not a recommendation
• Route 53 can route the call based on different metrics, such as:
• minimal latency: measured between the calling device and the edge
• geolocation: based on IP addresses
Minimal distance between the edge and the calling device
Geo DNS: latency routing and round-robin configuration settings for B2B calls and MRA
SRV Record CNAME Record A-Records Expressway-E
_sips._tcp.example.com
_collab-edge._tls.example.com
expe.example.com
location: us-east-1
us-expe.example.com
weight: 50
A1.B1.C1.D1
A2.B2.C2.D2
us-expe.example.com
weight: 50
A2.B2.C2.D2
A1.B1.C1.D1
expe.example.com
location: eu-west-1
emea-expe.example.com
weight: 50
X1.Y1.W1.Z1
X2.Y2.W2.Z2
emea-expe.example.com
weight: 50
X2.Y2.W2.Z2
X1.Y1.W1.Z1
Latency routing
Latency routing
Fallback alias for point-to-point and multipoint calls: Unity Connection call flow
Expressway-EExpressway-C
A.B.C.D
Unity Connection
Cisco Unified CM
Cisco Unified Presence Server
+391000
1. Dial A.B.C.D
2. Fallback alias
set to voice mail
pilot
3. “Please dial
the extension or
the name”
4. User enters “luca”, both devices ring at the same time
IP Address Dialing for H.323 Internet devices: Inbound Calls
+391000812000
IP Address Dialing: Outbound Calls
• Cisco Unified CM doesn’t support native IP address dialing
• Workaround: instruct the users to append a suffix such as: 10.10.10.10@ip. This will match the SIP Route Pattern “ip”
• Other workarounds: instruct the user to use “*” instead of “.” such as “10*10*10*10”. This will match one the following Route Pattern pointing to the Expressway: “!*!*!*!”
• On Expressway, regex match would be (\d\d?\d?)(\*)(\d\d?\d?)(\*)(\d\d?\d?)(\*)(\d\d?\d?) and replacement string \1\.\3\.\5\.\7
Cisco Unified CM IP dialing
Mobile and Remote Access
Firewall Traversal Capabilities Expanded
X8.1 release and above delivers 3 key capabilities enabling the Expressway Mobile and Remote Access feature
• XCP Router for XMPP traffic
• HTTPS Reverse proxy
• Proxy SIP registration to Unified CM
Firewall Expressway EExpressway C
HTTPs (provisioning, visual voicemail, directory)
SIP (audio, video)
XMPP (IM&P)
Unity
Cisco Unified CM
IM and Presence
Split DNS SRV Record Requirements
• _collab-edge record needs to be available in Public DNS
• Multiple SRV records (and Expressway-E hosts) can be deployed for HA
• A GEO DNS service can be used to provide unique DNS responses by geographic region
• _cisco-uds record needs be available only in internal DNS
_collab-edge._tls.example.com. SRV 10 10 8443 expwy1.example.com.
_collab-edge._tls.example.com. SRV 10 10 8443 expwy2.example.com.
_cisco-uds._tcp.example.com. SRV 10 10 8443 ucm1.example.com.
_cisco-uds._tcp.example.com. SRV 10 10 8443 ucm2.example.com.
Expressway & Jabber Service Discovery
Inside firewall (Intranet)
Collaboration
Services
Unified
CM
Public DNS
DNS SRV lookup _cisco-uds._tcp.example.com
Not Found ✗
expwyNYC.example.com✓
TLS Handshake, trusted certificate verification
DNS SRV lookup _collab-edge._tls.example.com
Outside firewall(Public Internet)
DMZ
HTTPS: get_edge_config?service_name=_cisco-
uds&service_name=_cuplogin
Expressway
E
Expressway
C
Global Deployment Topology & Geo DNS
SIP Trunk
SIP Line
Expressway Traversal
Unified CM
regional
clusters
SME global
aggregation
US Europe Asia
US SME
SJC
DFW
RTP PAR
AMS
LON
EU SMEAsia SME
TKY
HKG
BGL
Expressway
edge access
Geo DNS
DNS SRV lookup
_collab-edge._tls.example.com
expwy.us.example.com
expwy.uk.example.com
expwy.jp.example.com
Features
• XMPP Federation to other companies
• SSO compliant via IdP and Reverse HTTPS Proxy in DMZ
• Multiple UCM and IM&P clusters and domains supported
• Desktop devices supported (78XX, 88XX, DX, TC series families)
Expressway Design Considerations
MRA and B2B in the same box
• Not possible to use port 5060 and 5061 for B2B trunk, use others instead (i.e.5560 and 5561)
• TLS or TCP on B2B Trunk, encrypted or non-encrypted media configurable
• Two zones for MRA, a TLS and a TCP zoneif mixed mode enabled on UCM.
Unified CM
ExpEExpC B2B Traversal zone
• Encryption configurable
• H.323 configurable
Internet
Unknown
edge
MRA Traversal zone
• Always encrypted
• SIP, HTTPS, XMPP
PSTN Access
Gateways and CUBE Product Portfolio
2900 Series ISR-G2 (2901, 2911, 2921, 2951)
ASR 1004/6 RP2
3900 Series ISR-G2 (3925, 3945)
3900E Series ISR-G2 (3925E, 3945E)
800/1861 ISR
ASR 1002-X
ISR 4451-X
ASR 1001-X
46
ISR 4431
ISR-4K (4321, 4331)
ISR 4351
ISDN GW 3241
ISDN GW MSE 8321
CUBE and Voice Gateways
CUBE
Video Gateways
CUBE Deployment Scenarios
IP Voice Network
Cisco Unified CM
Cisco Unified
Border Element
SIP Softswitch
Class 5 switch
Class 4/Class 5
switches
PSTN
Enterprise NetworkVoice Carrier Network
Enterprise Network
Demarcation Line
Carrier Network
Demarcation Line
Session Border
Controller
Interconnection Zone
Centralized Voice Connection using CUBE and voice gateways
• Topology hiding when connecting to carrier SBC for IP PSTN access
• Delayed offer to early offer conversion and vice versa
• In-band and out-of-band DTMF support, DTMF conversion, fax passthrough and T.38 fax relay, volume and gain control
• Call admission control (CAC) based on resource consumption such as CPU, memory, call arrival spike detection
• RTP to sRTP interworking and security features
• Mid-call supplementary services including hold, transfer and conference
• Conversion of multicast music on hold (MoH) to unicast MoH.
• Billing statistics and CDR collection
CUBE for centralized IP PSTN
Calling Search Space
PSTNInternationalPartition CUBE1
PSTNInternational
SJCInternational
Route Pattern \+! Route List RL_PSTN
PSTNInternationalPartition
RCDInternational
Calling Search Space
SJC_GW
Device Pool set to
RCDPhone
Device
Pool
LRG_PSTN1 LRG_PSTN2
SJCPhone CUBE_US_PSTN GW_SJC_PSTN
RCDPhone CUBE_US_PSTN GW_RCD_PSTN
Route Group Trunk
GW_SJC_PSTN Trunk_To_SJC_GW
GW_RCD_PSTN Trunk_To_RCD_GW
Phone in SJC
Phone in RCD
LRG_PSTN_2
First choice for SJC users Backup for SJC users
Backup for RCD users
LRG_PSTN_1
RCD_GW
First choice for RDC users
Centralized IP PSTN access with local GW as backup
Device Pool set to
SJCPhone
Core Applications
Third-Party Solution
WebExCisco
Conferencing
Collab Edge
Internet
Headquarters
Remote Site
Mobile/Teleworker
TelePresence Server Conductor
Endpoints
Expressway-C
PSTN /
ISDN
Integrated/Aggregated Services Router
Integrated Services Router
DMZ
TelePresence Management Suite
Expressway-E
Instant Message and Presence
Unified Communications
Manager
Call Control
MPLS WAN
Applications
Unity Connection
PrimeCollaboration
Core Applications
• The Preferred Architecture (PA) for Enterprise Collaboration focuses on a
subset of core applications that are common for most collaboration
deployments.
• The core applications covered by the PA for Enterprise Collaboration:
» Cisco Unity Connection
» Cisco Prime Collaboration Deployment
» Cisco Prime Licensing Manager
• Many other applications and tools are available for collaboration deployments.
While these are not covered here, the overall PA architecture is designed in
such a way that these additional applications may be added as required for your
specific deployment. (See Appendix slides for a list of some of these applications)
Overview
Core Applications
» Cisco Unity Connection enables voicemail and unified messaging across a wide-range of end-user platforms
» Cisco Prime Collaboration Deployment (PCD) eases deployment of new infrastructure components, enabling faster initial setup
» Cisco Prime Licensing Manager (PLM) single tool to enable license workflows and manage licensing for collaboration infrastructure components.
Key Benefits
Cisco Unity Connection
Core Applications
• Design Objectives
» Ensure highly available voice messaging services including leaving message, message
waiting indication, and message retrieval
» Provide access to voice messaging features from hardware and software-based endpoints.
» Facilitate mailbox management and message retrieval via telephone, email, or visually
from a software client.
• Prerequisites:
» Deploy Cisco Unified CM and ensure it is functioning appropriately (refer to Call Control section).
» Download appropriate Cisco Unity Connection VMWare OVA template and bootable .iso.
» Deploy Microsoft Active Directory and ensure directory services are properly configured.
» Deploy Microsoft Exchange and ensure email services are functioning normally.
Cisco Unity Connection: Design Objectives and Prerequisites
• Redundant Unity Connection nodes
• SIP Trunk integration to Unified CM
• Integrations to directory and mail:
» Microsoft Active Directory
» Microsoft Exchange
• Call forwarding to Unity Connection
• Direct call to voicemail or visual
mailbox navigation (Visual Voicemail)
• Email access to voicemail (Single Inbox)
Core ApplicationsCisco Unity Connection: Architecture
Unified CM
Unity Connection
Publisher
Subscriber
Microsoft
Active
Directory
Directory
Mailbox
synchronization
Directory synchronization
Voicemail access
via VoIP to TUI or
via REST/HTTPS
(Visual Voicemail)
Voicemail
Email access to
voicemail
(Single Inbox)
SIP
VoIP or REST/HTTPS
Email (SMTP/HTTPS)
SIP
Messaging(On-Premise or
Cloud-Based)
Microsoft
Exchange
Core Applications
1. Provision the Unity Connection Cluster – Deploy two node cluster for high availability
» Determine OVA configuration size (based on number of users) and network and security parameters for
each node (hostname, IP address/mask, default gateway, DNS, NTP, username/password, etc.).
» Deploy/install publisher, add subscriber details under cluster configuration, then deploy the subscriber.
2. Configure Unified CM for Unity Connection Integration – Configure SIP trunks, call routing, and
voicemail settings for integration to Unity Connection cluster.
» Configure two SIP trunks (one per Unity Connection node) and call routing constructs (Route Pattern/List/
Group).
» Configure voicemail constructs (Voicemail Pilot number, MWI on/off, Voicemail Profile).
3. Unity Connection Base Configuration – Configure Unity Connection to enable Unified CM
integration, user provisioning, and voicemail capabilities.
» Configure phone systems settings, ports (port codec, port groups), and call routing to enable integration
with Unified CM.
» Enable directory sync with Active Directory and configure templates for user provisioning of mailboxes
and self enrollment.
Cisco Unity Connection: Deployment Overview (1 of 2)
Refer to the CVD
Alternatively use Prime Collaboration Deployment
Core Applications
4. Enable Single Inbox – Unified messaging feature enabling synchronization of voice messages in Unity
Connection with user’s Microsoft Exchange mailbox.
» Configure Unified Messaging Services account and role in Active Directory/Exchange, and configure Unity
Connection settings (SMTP, authentication method/protocol, and user enablement).
» Install ViewMail for Outlook (available at Cisco.com), configure email account and Unity Connection server.
5. Enable Visual Voicemail – Provide visual access to voicemail boxes for listing and playing messages
» Configure appropriate Unity Connection settings: Class of service (CoS) and API options settings
» On Unified CM configure voicemail UC service for each Unity Connection node and add the services to a
UC Service Profile.
6. Voicemail in SRST Mode – Configure branch ISRs with SRST to route calls to Unity Connection voicemail
system via PSTN when IP WAN is down.
» Configure call forward no answer/busy and POTS dial-peer to route calls via the PSTN to Unity Connection.
» Ensure Redirected Dialed Number Information Service (RDNIS) is configured and carrier propagates so that
callers are directed to the appropriate voicemail box rather than the automated attendant prompt.
7. HTTPS Interworking of two or more Unity Connection Clusters – Configure HTTPS networking to
enable directory information sharing and message exchange between multiple clusters.
Cisco Unity Connection: Deployment Overview (2 of 2)
Refer to the CVD
Core Applications
• Unity Connection Cluster Deployment (publisher + subscriber)
» Nodes: Must be the same OVA size and integrate to the same Unified CM cluster.
» Connectivity: Maximum RTT = 150 ms. For every 50 voice messaging ports 7 Mbps of
bandwidth is required.
• Unified CM Integration
» Dual SIP trunks, route group with ‘Top Down’ algorithm for call routing: Unity Connection
subscriber 1st (primary), publisher 2nd (backup).
» Visual Voicemail – UC Service: Set the Unity Connection publisher as the primary
voicemail service and subscriber as the secondary service within the UC service profile.
• Capacity Planning
» Reserve 20% of total system ports for dial out/non-answering operations (message
notification, MWI, etc.)
Cisco Unity Connection: Design Considerations
Sub Pub
X
Cisco Prime Collaboration Deployment
Core Applications
• Design Objectives
» Simplify collaboration application node deployments by enabling automated unattended
installation of collaboration application server nodes
» Facilitate configuration of common network and security settings for all collaboration
applications.
• Prerequisites:
» Download OVA and bootable .iso file for Cisco Prime Collaboration Deployment (PCD)
» Deploy PCD virtual machine as a standalone application instance on VMWare ESXi host.
» Determine which collaboration applications will be deployed (Unified CM, IM & Presence, Unity
Connection) and the number of nodes required based on overall size of the deployment.
Cisco Prime Collaboration Deployment: Design Objectives and Prerequisites
Core ApplicationsCisco Prime Collaboration Deployment: Architecture
VMWare
EXSi
host
• Cisco collaboration application .iso install
files located on Prime Collaboration
Deployment (PCD).
• PCD network file system (NFS) mount on
ESXi host(s) to facilitate .iso file access.
• Collaboration application node virtual
machines (VMs) manually created on the
ESXi host.
• PCD installs collaboration application
clusters on the target VMs.
.iso.iso
.iso
CM_Sub
VM
CM_Sub
VM
IM&P_Pub
VM
IM&P_Sub
VM
IM&P_Sub
VM
UCXN_Pub
VM
UCXN_Sub
VM
Prime Collaboration Deployment
CM_Pub
VM
Core Applications
1. Prepare for Collaboration Application Deployment – Download the OVA templates and bootable
Cisco ISO images for the target collaboration application(s) and release. SFTP .iso images to the
/fresh_install directory of Cisco Prime Collaboration Deployment (PCD).
2. Create Virtual Machines (VMs) on the ESXi Host(s) using OVA Templates – Create one VM for
each application node using appropriate application OVA template based on deployment size.
3. Add ‘ESXi Host’(s) to PCD – Enter ESXi host(s) information via the administrative interface of PCD.
4. ‘Define New UC Cluster’(s) in PCD – Add VM nodes and configure network parameters and functions
as well as cluster-wide network and security settings (DNS, NTP, usernames/passwords, certificate
information). [Two clusters required: 1 for Unified CM/IM & P, 1 for Unity Connection]
5. ‘Add Install Task’(s) in PCD – Select UC cluster for installation and select installation files (.iso) for
cluster node types. [Two installation tasks required: 1 for Unified CM/IM & P, 1 for Unity Connection]
6. PCD Completes Installation Process – All collaboration application server nodes are installed with
base configuration and now ready for further configuration.
Cisco Prime Collaboration Deployment: Deployment Overview
Cisco Prime License Manager
Core Applications
• Design Objectives
» Enable simplified, enterprise-wide management and tracking of user-based licensing for
collaboration applications.
» Provide enterprise-level reporting of usage and entitlement
» Facilitate license fulfillment using electronic or license file methods.
» Simplify procurement of additional licenses when number of users increases.
• Prerequisites:
» Download Cisco Prime License Manager OVA template and bootable .iso file.
» Determine number and types of users to be licensed for collaboration applications (Unified
CM and Unity Connection)
Cisco Prime License Manager: Design Objectives and Prerequisites
Core ApplicationsCisco Prime License Manager: Architecture
• Cisco Prime License Manager (PLM) enables
license fulfillment:
» Electronic [requires Internet connectivity]
OR
» Manual license file request
• Licenses received (over the network or via
email)
• Licenses applied to system and propagated
to synchronized application instances.
Unified CM Unity Connection
PublisherPublisher
Prime License
Manager
Cisco.com
Core Applications
1. Deploy and Install Cisco Prime Licensing Manager (PLM) – Install PLM as a virtual machine
on a VMWare ESXi host.
2. Add Product Instances – Add Unified CM and Unity Connection product instances to PLM
(one per cluster). Use ‘Test Connection’ to verify communication between the collaboration
applications and PLM.
3. Determine Licensing Requirement for Products – Based on number of users within
deployment determine number and types of licenses required.
» Use the License Usage and License Planning menu options to determine number and type of required
licenses based on current user count as well as to calculate and prepare for future license requests.
4. Perform New License Fulfillment – Acquire and install collaboration user licenses.
» Enter PAK (product activation key) and retrieve licenses electronically via the Internet
» Alternatively, generate license request and submit along with PAK via Cisco License Registration site
(http://www.cisco.com/go/license) to receive license file via email. Install received license file.
Cisco Prime License Manager: Deployment Overview
Simplified Sizing
Traditional Sizing for Cisco Collaboration
Collaboration Sizing Tool (CST)
http://tools.cisco.com/cucst
Simplified Sizing for the Preferred Architecture (PA)
• The Preferred Architecture (PA) offers Simplified Sizing rules with corresponding assumptions (e.g. average BHCA per user, number of DN per device, etc…)
PA Simplified Sizing vs. Collaboration Sizing Tool
Deployment within the
PA Sizing Assumptions?
Use PA
Simplified Sizing
Use Collaboration
Sizing Tool
Sizing Cisco Unified CM
Publisher
TFTP 1 TFTP 2
< 5k devices and users
Publisher
TFTP 1 TFTP 2
Between 5k and 10k
devices and users
Call Processing subscriber pair Call Processing subscriber pair
Call Processing subscriber pair
7.5k OVA (2 vCPUs) is deployed for both deployments
7.5k OVA supported on BE7000M or larger
Why using the 7.5k OVA for Cisco Unified CM?
With the 7.5k OVA
• Let’s consider the deployment with 10,000 users/devices
With the 10k OVA
Sizing Unified CM – PA Assumptions
• PA Assumptions:
• Up to 4 BHCA per user
• Up to 2 DNs per device
• Each user can use Extension Mobility
• No SW Conference Bridge
• Up to 500 CTI ports and 100 CTI Route Points per Call Processing pair
• Up to 3,000 partitions, 6,000 CSS, 12,000 Translation Patterns
• etc…
• Refer to the Preferred Architecture CVD for the complete list of assumptionshttp://www.cisco.com/go/cvd/collaboration
Sizing IM and Presence
• In the PA, IM & Presence is deployed with 2 servers
• The number of users (full UC) dictate which OVA is used
Between
2k and 5k users
Between
5k and 15k users
2k-user OVA (1 vCPU)
5k-user OVA(2 vCPUs)
15k-user OVA(4 vCPUs)
Those 3 OVAs are supported on BE7000M or larger
Less than
2k users
Sizing TelePresence Server
• Add TelePresence Servers as needed
PlatformCluster
Support
HD 1080p port
capacity1
HD 720p port
capacity2
SD 480p port
capacity2
Multiparty Media
410vNo 27 54 81
Multiparty Media
820 (blade)Yes 30 60 90
1Includes content sharing 720p@15fps2Includes content sharing 720p@5fpsTelePresence Servers support a maximum of 200 audio connections on any platform
Data sheet: http://www.cisco.com/c/en/us/products/collateral/conferencing/telepresence-server/data_sheet_C78-7287571.html
Sizing TelePresence Conductor
• In the PA, 2 TelePresence Conductor servers are deployed
• The number of concurrent participants dictates which OVA to use
< 50 total concurrent
participants
Small OVA (2 vCPUs, 4GB RAM)
< 2,400 total concurrent
participants
Large OVA
(2 vCPUs, 6GB RAM) or
Dedicated Appliance
Both OVAs are supported on BE6000M or largerA TelePresence Conductor cluster supports up to 30 TS servers
Sizing TelePresence Management Suite (TMS)
< 200 controlled systems
< 100 concurrent participants
< 50 concurrent ongoing scheduled
conference
<1000 Collaboration Meeting Rooms
TMS/
TMSPE/TMSXE
TMS/
TMSPE/TMSXE
TMS/TMSPE TMS/TMSPE
TMSXE TMSXE
Regular Deployment (1 vCPU OVA)
< 5,000 controlled systems
< 1,800 concurrent participants
< 250 concurrent ongoing scheduled
conference
< 48,000 Collaboration Meeting Rooms
Large Deployment (4 vCPUs OVAs)All OVAs are supported on BE6000M or larger
Sizing Expressway - Deployment
• Equal number of nodes in Expressway-C vs. Expressway-E clusters
• Up to 6 nodes per Expressway C/E cluster
Expressway-C Expressway-E
Internet
Sizing Expressway
Expressway C/E
Cluster
Redundancy
Model
MRA Proxy
RegistrationsVideo Audio-only
2 nodes N+1 2,500 150 300
3 nodes N+1 5,000 300 600
6 nodes N+2 10,000 600 1,200
Expressway Deployment with CE500 / Medium OVA (2 vCPUs) on BE6000M or larger
Expressway C/E
Cluster
Redundancy
Model
MRA Proxy
RegistrationsVideo Audio-only
2 nodes N+1 2,500 500 1,000
3 nodes N+1 5,000 1,000 2,000
6 nodes N+2 10,000 2,000 4,000
Expressway Deployment with CE1000 / Large OVA (8 vCPUs) on Specs-based
Sizing Unity Connection
• Cisco Unity Connection is deployed with 2 servers in an active/active mode
• The number of users dictate which OVA is used
Between
1k and 5k users
Between
5k and 10k users
5k-user OVA(2 vCPUs)
10k-user OVA(4 vCPUs)
Both OVAs are supported on BE7000M or larger
Collaboration Virtual Machine Placement Tool
• VM placement and Hardware Sizing
Virtual Machine Placement Tool (VMPT): http://www.cisco.com/go/vmpt
Deployment example with 5k users / 5k devices
MM410v
BE7KM
BE7KM
BE7KM
BE7KM
Summary
• Preferred Architecture Introduction
• Collaboration Edge
• Applications
• Simplified Sizing
Closing
Additional Information• Cisco Collaboration Solutions Design Guidance:
http://www.cisco.com/go/ucsrnd
» Cisco Collaboration Systems 10.x Solution Reference Network Designs (SRND)
» COMING SOON: Cisco Collaboration Systems 11.0 Solution Reference Network Designs (SRND)
• Cisco Enterprise Preferred Architecture:
http://www.cisco.com/go/cvd/collaboration
» Cisco Preferred Architecture for Enterprise Collaboration, Design Overview
» Cisco Preferred Architecture for Enterprise Collaboration, CVD
• To continuously improve the Preferred Architecture Documentation we need your feedback. For questions, suggestions and clarifications please send email to [email protected]
Cisco Customer Connection ProgramConnect with Cisco & Peers
17,000+
Members
• Influence Collaboration product direction
• Access to early adopter & beta trials
• Contribute to advisory groups
• Monthly technical & roadmap briefings
• Exclusive perks at Cisco Live
– Collaboration Cloud Fusion: Vision & Architecture (speaker: Jonathan Rosenberg, VP/CTO CTG)
– 5 NDA Roadmap Sessions + Microsoft Interop
– Q&A Open Forum with Product Management
– Reserved seats at Work Human Innovation Talk (Wed. 3:30 – 4:30)
Visit the Customer Connection Program -
Collaboration zone in the Cisco Campus
Join the Customer Connection program
Explore the Collaboration community
New CCP members get a thank-you gift
Continue the Conversation using Cisco Spark
• Sign up free for Cisco Spark at http://www.ciscospark.com/
• Download the application from iOS App Store, Google Play Store, or from http://download.ciscospark.com/
• Visit the World of Solutions Cisco Spark area for demos
• Use Cisco Spark to continue the conversation or ask any additional questions with the speaker for this session. The room name is BRKCOL-2421
• How to get added to the Cisco Spark room for this session
• To opt in, send an email to [email protected] with the message “Please add me to the BRKCOL-2421 room”
Complete Your Online Session Evaluation
Don’t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online
• Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card.
• Complete your session surveys though the Cisco Live mobile app or your computer on Cisco Live Connect.
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Table Topics
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you
Appendix
Core Applications
Application Name Functions Integration Method
Contact Center Enterprise
(CCE)
Provides internal and external customer collaboration
technologies, including agent login, Interactive Voice Response
(IVR) for call vectoring, outbound connection methods, and
omnichannel agent interactions.
Enterprise contact centers operate on a dedicated
Unified CM cluster that is trunked to the enterprise
Unified CM cluster.
Contact Center Express
(CCX)Provides dial-by-name and a subset of Contact Center ideal for
small contact centers or internal use.Communicates to Unified CM using JTAPI.
TelePresence Content
Server (TCS)
Provides video, audio, and content recording functionality that can
be included in scheduled calls through a check-box in TMS or
dialed, allowing any endpoint to easily be a recording station.
Registers with Cisco TelePresence VCS-Control
and communicates with Unified CM devices via
SIP trunk between Unified CM and VCS Control.
Show and Share Provides an internal stored video content portal.
TCS automatically uploads content to Show and
Share. No other integration to call control is
required.
Prime Collaboration
ProvisioningProvides an administrative portal for "Day 2" operations.
Standalone software that communicates through
SSH and HTTPS interfaces of infrastructure
devices and endpoints.
Prime Collaboration
AssuranceProvides quality and fault detection services for collaboration
deployment administrator.
Stand alone software that communicates through
SSH and HTTPS interfaces of infrastructure
devices and endpoints.
Additional Applications to Enhance Preferred Architecture* (1 of 2)
* This is not an exhaustive list of applications that can be integrated with the Enterprise Preferred Architecture
Core Applications
Application Name Functions Integration Method
Prime Collaboration
AnalyticsProvides up to one year of usage data for usage and fault trend
analysis by the collaboration deployment administrator.
Deployed with Prime Collaboration Assurance and
utilizes data collected by that application.
Attendant ConsoleGives corporate operators or receptionists a desktop application
to handle incoming calls.
Standard version installs on the end user’s
Windows computer and connects to Unified CM.
Advanced version runs on a dedicated server, and
the end users log into the application..
Media SenseProvides recording for both full-time and selective recording
scenarios in Unified CM.
Recording Profiles are configured in Unified CM,
and MediaSense is connected to Unified CM and
Cisco Unified Border Element through SIP trunks.
Jabber GuestProvides click-to-connect functionality for business-to-consumer
(B2C) collaboration.
Requires a dedicated Expressway-C and
Expressway-E pair, using a distinct domain from
the enterprise Expressway-C and Expressway-E
implementation used for Mobile and Remote
Access and business-to-business video calls.
Unified CM has SIP trunks to this dedicated
Expressway pair.
Additional Applications to Enhance Preferred Architecture* (2 of 2)
* This is not an exhaustive list of applications that can be integrated with the Enterprise Preferred Architecture