© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 11© 2012 Cisco and/or its affiliates. All rights re...
Agenda• Unified Call Control• Unified Conferencing• Borderless Collaboration Edge Architecture• Key Takeaways• Q&A
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 3Unified Call Control
Collaboration ArchitectureCall Control Products, Versions and Baseline supportSupported Products and Versions• CUCM versio...
Collaboration ArchitectureCall Control: Strategic VisionAll SIP based Endpoints registerto CUCMCUCM Call Control provides ...
Collaboration ArchitectureCall Control: Deployment Models• Based on SRND Deployment Models1. Campus Deployment Model2. Cen...
Collaboration ArchitectureCall Control: Campus Deployment ModelCampus SiteThe most basic deployment model :• Single Site• ...
Collaboration ArchitectureCampus Deployment Model: Benefits and Considerations• Decision to use VCS for endpoint registrat...
Deployment Models: Centralized Call Processing ModelCentralized CUCM and Centralized VCS• Single Central Site with Call Co...
Centralized CUCM and Centralized VCS: Benefits andConsiderations• Primary considerations are CAC, Dial Plan and TCO• This ...
SME and Directory VCS -Existing VCS environmentIP WANSession Management EditionDirectory VCSSIPCampus SiteTMSUnified CMRem...
SME and Directory VCS – Existing VCS environment: Benefitsand Considerations• This model is proposed for customers who hav...
SME with multiple Centralized CUCM & VCS deployments:CUCM Centric DeploymentIP WANSession Management EditionSIPCampus Site...
SME with multiple Centralized CUCM & VCS deployments –CUCM Centric Deployment: Benefits and Considerations• This model is ...
Additional Deployment OptionsAbove and beyond the core designs (Campus, Centralized, Distributed)1) Centralized CUCM, Dist...
TC Endpoint RegistrationCUCM only or Greenfield siteUnified CMPSTN/ISDNVCS-CRegister Endpoints on VCS if you require :IPv6...
TC Endpoint RegistrationExisting VCS / VCS & CUCM UsersPSTN/ISDNVCS-CKeep Endpoints on VCS if you require :TMS Directly Ma...
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 18UnifiedConferencing
Collaboration Conferencing ArchitectureProducts, Versions and Baseline supportUnified CMTMSConferencingVPNEdgePSTNTDMISDNV...
Collaboration Conferencing ArchitectureVisionUnified CMAd hocRendezvousand scheduledconferencingOrchestrationSchedulerConf...
Collaboration Conferencing ArchitectureToday’s RecommendationVCS-CUnified CMAd hocRendezvousvideo conferencingScheduled Vi...
Deployment Models – Centralized Call ProcessingCampus with centralized conferencingGeneral Considerations:• Conductor shou...
Collaboration Conferencing ArchitectureDeployment Models:• Campus• Centralized Call Control• Distributed Call Control with...
Deployment Models: Centralized Call ProcessingCampus with centralized conferencingAd hocRendezvousvideo conferencingVCS-CU...
Deployment Models: Centralized Call ProcessingCampus with centralized conferencingBenefits:• The Unified CM Conference But...
Deployment Models: Centralized Call ProcessingCentralized Unified CM with distributed conferencingSIP Trunk SIP/H.323 regi...
Deployment Models: Centralized Call ProcessingCampus with centralized conferencingBenefits:• The Unified CM Conference But...
IP WANIP WANDeployment Models: Distributed Call ProcessingSME with distributed conferencingSIP Trunk SIP/H.323 registratio...
Deployment Models: Distributed Call ProcessingSME with distributed conferencingBenefits:• The Unified CM Conference Button...
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 31BorderlessCollaboration EdgeArchitecture
Collaboration Enterprise Edge ArchitectureProducts, Versions and Baseline SupportUnified CMTMSConferencingVPNEdgePSTNTDMIS...
Collaboration Enterprise Edge ArchitectureOverviewScenarios:• Extend enterprise network with VPN• Endpoint registrations• ...
Collaboration Enterprise Edge ArchitectureVisionUnified CMEnterprise call control,IM&P and conferencingSIP TrunkSIP/H.323S...
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 35Unified CM &applicationsExpresswayFirewall Traver...
Collaboration Enterprise Edge ArchitectureToday’s RecommendationVCS-CUnified CMScheduled voiceconferencingSIP Trunk SIP/H....
Collaboration Enterprise Edge ArchitectureVPNBenefits• Extend enterprise network to remote locations, teleworkers, or mobi...
Collaboration Enterprise Edge ArchitectureVCS ExpresswayBenefits• NAT/FW Traversal• URI and Number based call routing• Int...
Collaboration Enterprise Edge ArchitectureGatewaysBenefits• ISR gateways for PSTN connectivity• Cisco TelePresence gateway...
Collaboration Enterprise Edge ArchitectureConsiderations• There is no single box solution• IM may not possible when using ...
Key Takeaways• Multiple architectures supported for both CUCM and VCS centric customers• Endpoint registration supported o...
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 42Cisco ConfidentialCisco Connect 42© 2012 Cis...
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 43© 2011 Cisco and/or its affiliates. All rights re...
Complete Your Paper“Session Evaluation”Give us your feedback and you could win1 of 2 fabulous prizes in a random draw.Comp...
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 49Thank you.
Upcoming SlideShare
Loading in...5
×

Architecting Impactful Visual Collaboration

561

Published on

Impactful visual communication is a crucial component to the success of any transformational Collaboration Architecture; as all forms of visual collaboration continue to assert themselves outside of the boardroom and become mobile, we need to migrate towards more extensible Collaboration architectures that can anticipate and accommodate this unprecedented level of growth.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
561
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Architecting Impactful Visual Collaboration

  1. 1. © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 11© 2012 Cisco and/or its affiliates. All rights reserved.Toronto, CanadaMay 30, 2013ArchitectingImpactful VisualCollaborationJohn BurnettTechnical Marketing Engineer, Call ControlCTG Solutions
  2. 2. Agenda• Unified Call Control• Unified Conferencing• Borderless Collaboration Edge Architecture• Key Takeaways• Q&A
  3. 3. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 3Unified Call Control
  4. 4. Collaboration ArchitectureCall Control Products, Versions and Baseline supportSupported Products and Versions• CUCM version 9.1• VCS version 7.2• VCS Endpoints version TC 6.1• TMS version 14.2Baseline support• Voice and Video Endpoints• Desktop Sharing• Encrypted Calls• RedundancyUnified CMTMSConferencingVPNEdgePSTNTDMISDNVoiceVideoVCS-CDSPCall Control
  5. 5. Collaboration ArchitectureCall Control: Strategic VisionAll SIP based Endpoints registerto CUCMCUCM Call Control provides :Additional FeaturesSimplified CACSimplified Dial PlanTC Endpoints can be registeredto CUCM todayGoal: Allow all TC Endpoints toregister with CUCM with the nextmajor UCM releaseLeverage VCS for CollaborationEdge & ConferencingUnified CMEndpoints
  6. 6. Collaboration ArchitectureCall Control: Deployment Models• Based on SRND Deployment Models1. Campus Deployment Model2. Centralized Call Processing Deployment Model3. Distributed Call Processing Model• These models combine investments in both CUCM & VCS• The following slides discuss the placement of CUCM and VCS only for eachDeployment option based on current product versions.• Endpoint Registration is discussed separately• Other deployment models are viable and supported
  7. 7. Collaboration ArchitectureCall Control: Campus Deployment ModelCampus SiteThe most basic deployment model :• Single Site• CUCM and VCS co-located• SIP Trunk between CUCM andVCS• Simplistic Dial Plan integration• CAC not required• TMS for solution-wide schedulingTMSVCS-CUnified CM
  8. 8. Collaboration ArchitectureCampus Deployment Model: Benefits and Considerations• Decision to use VCS for endpoint registration – depends on customer’s deployment and featurerequirements – discussed later• Single SIP Delayed Offer Trunk between CUCM and VCS• Trunk destinations can be IP addresses or can use DNS• Simplistic call routing - Default Routes between CUCM and VCS• Number/ URI not found on CUCM – send to VCS• Number/ URI not found on VCS – send to CUCM• Dial Plan• If this a newly installed VCS cluster• Use URI’s only or numbers only on VCS endpoints• Use SIP only on endpoints – simplifies migration to CUCM• If this is an existing VCS cluster• Try to avoid using both a number and a URI on a single endpoint – as this requires both SIPand H323 to be used. Calls to H323 addresses will be interworked via VCS (media hair-pinned via VCS)
  9. 9. Deployment Models: Centralized Call Processing ModelCentralized CUCM and Centralized VCS• Single Central Site with Call Control• Multiple Remote Sites – Endpoints only• SIP Trunk between CUCM and VCS• Simplistic Dial Plan integration• Isolated Call Admission Control mechanisms forCUCM and VCSRemoteOffice NIP WANCentral SiteTMSVCS-CUnified CM
  10. 10. Centralized CUCM and Centralized VCS: Benefits andConsiderations• Primary considerations are CAC, Dial Plan and TCO• This recommended design is based on the best current design bearing in mind a futuremigration of VCS endpoints to CUCM (See appendix and word doc for alternativedesigns)• No one design for the centralized deployment model addresses all design issues• Alternative designs address CAC at the expense of additional dial plan complexity andadditional VCS clusters that may become redundant once VCS endpoints are migratedto CUCM• With this design :• The dial plan is simplistic (as per the campus deployment model)• CAC challenges for calls between CUCM and VCS endpoints (within and between branches).• WAN bandwidth must be provisioned independently for VCS and CUCM• This segregated CAC architecture is a common feature of dual call control designs• Interworking on VCS should be done locally for best media routing experience.
  11. 11. SME and Directory VCS -Existing VCS environmentIP WANSession Management EditionDirectory VCSSIPCampus SiteTMSUnified CMRemoteOffice NIP WANCentral SiteTMSUnified CMRemoteOffice NIP WANCentral SiteTMSUnified CMVCS-CVCS-CVCS-C
  12. 12. SME and Directory VCS – Existing VCS environment: Benefitsand Considerations• This model is proposed for customers who have multiple VCS clusters deployed today• These customers will probably have regional VCS clusters and a Directory VCS deployedalready• In this design there are two separate Call Control domains – VCS and CUCM• Dial Plan• Is simplistic – a single SIP Trunk between SME and Directory VCS - default routes to eachdomain• Call Admission Control• Isolated Call Admission Control mechanisms for CUCM and VCS domains• CAC challenges for CUCM to VCS calls ( a known issue with dual call control )• If interworking cannot be avoided it should take place in the leaf VCS systems rather than theDirectory VCS
  13. 13. SME with multiple Centralized CUCM & VCS deployments:CUCM Centric DeploymentIP WANSession Management EditionSIPCampus SiteTMSVCS-CUnified CMRemoteOffice NIP WANCentral SiteTMSVCS-CUnified CMRemoteOffice NIP WANCentral SiteTMSVCS-CUnified CM
  14. 14. SME with multiple Centralized CUCM & VCS deployments –CUCM Centric Deployment: Benefits and Considerations• This model is an extension of the previous Campus and Centralized Deployment models• Proposed for customers who do not have VCS deployed today• The same design principles apply for Campus and Centralized deployments except for :• Dial Plan• With multiple CUCM and VCS clusters default routes can now no longer be used• For numeric dial plans – call routing needs to be regionalized to route calls via SME to other clusters• For alphanumeric dial plans – Use ILS and import URIs from each VCS cluster into the CUCM ILS domain• Call Admission Control• CAC challenges for CUCM to VCS calls within Centralized Deployments• CAC does work between clusters via SME
  15. 15. Additional Deployment OptionsAbove and beyond the core designs (Campus, Centralized, Distributed)1) Centralized CUCM, Distributed VCS Deployment Model2) Centralized CUCM, Hybrid - Centralized & Distributed VCS Deployment Model3) SME & Distributed Call Processing Deployment Model with Hybrid VCS deployments4) SME & VCS-D Distributed Call Processing Model with Hybrid VCS deployments• We will lead with the core designs (Campus, Centralized, Distributed)• Endpoint Registration is discussed separately• See Backup Slides
  16. 16. TC Endpoint RegistrationCUCM only or Greenfield siteUnified CMPSTN/ISDNVCS-CRegister Endpoints on VCS if you require :IPv6 VideoEndpoint Registration RedundancyUS DoD certificationUser Menu LockoutRelease Key ManagementEndpoints registered on CUCM gain the following key featuresand benefits:Single Dial Plan - Single Call Admission Control DomainCUCM Phones features :Voice Mail indicator /Call Forward All /Consultative TransferShared Lines /SNR /Ad Hoc conferencing /CTI Control /BLFCSS/Partitions /Hunt Groups/ Music on Hold/ Announcements
  17. 17. TC Endpoint RegistrationExisting VCS / VCS & CUCM UsersPSTN/ISDNVCS-CKeep Endpoints on VCS if you require :TMS Directly ManagedTMS ProvisionedIPv6 VideoEndpoint Registration RedundancyUser Menu LockoutRelease Key ManagementH323 and 3rd Party Endpoint registrationDownspeeding/ MOVI ClientsZone /Sub-Zone EncryptionUnified CMRegister endpoints on CUCM to enable the followingfeatures/functionality:Single Management point for Dial PlanSingle Call Admission Control DomainCUCM Phones features :Voice Mail indicator /Call Forward All /Consultative TransferShared Lines /SNR /Ad Hoc conferencing /CTI Control /BLFCSS/Partitions /Hunt Groups/ Music on Hold/ Announcements
  18. 18. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 18UnifiedConferencing
  19. 19. Collaboration Conferencing ArchitectureProducts, Versions and Baseline supportUnified CMTMSConferencingVPNEdgePSTNTDMISDNVoiceVideoVCS-CDSPCall Control Supported products and versions:• Packet Voice DSP Module (PVDM) version 3• Conductor version XC2.1• TelePresence Server 7010 and 8710 version 3.0• MCU 8510 version 4.4• MCU 53X0 version 4.4• UC Manager version 9.1.1• Video Communication Server (VCS) versionX7.2.2• TelePresence Management Suite (TMS) 14.2Baseline support:• Support for both voice and video endpoints• End-to-End encryption• Meeting types:• Ad hoc• Rendezvous• Scheduled (video calls only)• Maximum resiliency• Content support (for video calls)
  20. 20. Collaboration Conferencing ArchitectureVisionUnified CMAd hocRendezvousand scheduledconferencingOrchestrationSchedulerConferencingScheduled voiceconferencingHigh Level Overview:• Unified Audio, Video and WebExconferencing• Orchestration is provided toensure the best experience,ease of use and resiliency• Devices underneath theorchestration layer can behardware or software based anduse transcoding and/or switching
  21. 21. Collaboration Conferencing ArchitectureToday’s RecommendationVCS-CUnified CMAd hocRendezvousvideo conferencingScheduled VideoconferencingConductorAd hoc voiceconferencingTMSSIP Trunk SIP/H.323 registration SIP/XML RPC SCCP registrationScheduled voiceconferencingHigh Level Recommendation:• Audio conferencing• Audio transcoding and conferencing devices connected to UCManager (plus WebEx). Maintain existing audio conferencingbest practices• Video conferencing• Ad hoc and Rendezvous: Conductor added as a MediaResource Group/trunked to UC Manager with MCU orTelePresence Server behind• Scheduled: MCU or TelePresence Server registered to VCS• Conferencing devices• TelePresence Server 8710/7010: Video• MCU 8510/53X0: Video• PVDM3: Audio only no video
  22. 22. Deployment Models – Centralized Call ProcessingCampus with centralized conferencingGeneral Considerations:• Conductor should be clustered to add resiliency• Conductor has the following limitations (clustering does not affect these values):• 30 MCU’s or TS’s (or mix both)• 2400 concurrent calls• 1200 active conferences• Currently Conductor does not take in to account the audio-only ports on MCU or TS
  23. 23. Collaboration Conferencing ArchitectureDeployment Models:• Campus• Centralized Call Control• Distributed Call Control with Distributed Conferencing
  24. 24. Deployment Models: Centralized Call ProcessingCampus with centralized conferencingAd hocRendezvousvideo conferencingVCS-CUnified CMAd hocRendezvousvideo conferencingScheduled VideoconferencingConductorAd hoc voiceconferencingTMSSIP Trunk SIP/H.323 registration SIP/XML RPC SCCP registrationCampus SiteScheduled voiceconferencingAudio conferencing• Centralized pool of ad hoc voice resourcesVideo conferencing• Ad hoc and Rendezvous: Two Conductorsclustered and trunked to UC Manager withMCU or TelePresence Server resources splitfor maximum resiliency• Scheduled: Separate MCU(s) or TelePresenceServer(s) registered to VCS
  25. 25. Deployment Models: Centralized Call ProcessingCampus with centralized conferencingBenefits:• The Unified CM Conference Button ad hoc call escalation mechanism is supported• Rendezvous and ad hoc calls may both be hosted on a single MCU or TS if required• All TMS scheduling capabilities are supported• Advanced TS features such as optimized conferencing are available for ad hoc and rendezvous calls• CAC simplified with conferencing resources in single locationConsiderations:• Conductor should be clustered to add resiliency
  26. 26. Deployment Models: Centralized Call ProcessingCentralized Unified CM with distributed conferencingSIP Trunk SIP/H.323 registration SIP/XML RPC SCCP registrationVCS-CUnified CMAd hocRendezvousvideo conferencingScheduled VideoconferencingConductorAd hoc voiceconferencingTMSRemoteOffice NCentral SiteScheduled VideoconferencingAd hoc voiceconferencingScheduled voiceconferencingIP WANAudio conferencing• Distributed pools of ad hocvoice resourcesVideo conferencing• Ad hoc and Rendezvous: TwoConductors clustered andtrunked to UC Manager withMCU or TelePresence Server.Resources remain centralizedwhere the most bandwidth is.• Scheduled: Separate MCU(s)or TelePresence Server(s)registered to VCS, centralizedor optionally distributed ifremote office is large.
  27. 27. Deployment Models: Centralized Call ProcessingCampus with centralized conferencingBenefits:• The Unified CM Conference Button ad hoc call escalation mechanism is supported• Rendezvous and ad hoc calls may both be hosted on a single MCU or TS if required• All TMS scheduling capabilities are supported• Advanced TS features such as optimized conferencing are available for ad hoc and rendezvous calls• Media can be kept local to audio endpoints by using the closest ad hoc conferencing resource• Media can be local to video endpoints by using the closest scheduled video resources if distributed.• Scheduled video resources can be centralized or distributed since TMS can place calls on the most local MCU when IPzones are configuredConsiderations:• Conductor should be clustered to add resiliency• Latency between Conductor and the conferencing devices should be less than 1000ms• Ad hoc/rendezvous video conferencing resources are best placed in a centralized or high bandwidth to preventundesirable WAN bandwidth usage
  28. 28. IP WANIP WANDeployment Models: Distributed Call ProcessingSME with distributed conferencingSIP Trunk SIP/H.323 registration SIP/XML RPC SCCP registrationScheduled voiceconferencingVCS-CUnified CMVCS-CUnified CMVCS-CUnified CMSession Management EditionScheduled VideoconferencingAd hocRendezvousvideo conferencingConductorScheduledVideoconferencingAd hoc voiceconferencingScheduled VideoconferencingAd hoc voiceconferencingAd hocRendezvousvideo conferencingAd hoc voiceconferencingAd hocRendezvousvideo conferencingTMSIn the case of a directory VCS beingused the conferencing deploymentdoes not change, scheduled MCUsor TelePresence Servers register tothe most local VCS leaf cluster.• Audio conferencingDistributed pool of ad hocvoice resources• Video conferencingAd hoc: Conductorscentralized, connected to eachUC ManagerRendezvous: Conductorcluster trunked to SMEScheduled: Separate MCU(s)or TelePresence Server(s)registered to local VCS
  29. 29. Deployment Models: Distributed Call ProcessingSME with distributed conferencingBenefits:• The Unified CM Conference Button ad hoc call escalation mechanism is supported• Rendezvous and ad hoc calls may both be hosted on a single MCU or TS if required• All TMS scheduling capabilities are supported• Advanced TS features such as optimized conferencing are available for ad hoc and rendezvous calls• Media can be kept local to endpoints by using the closest conferencing resource• Single location for managing multipoint video resources from all sites via Conductor• Utilize exiting SME dial plan for rendezvous conferences Considerations:• Conductor should be clustered to add resiliency• For larger deployments multiple Conductor clusters may be required, but these very large deployments should be handledon a case by case basis to ensure the optimum result for customers
  30. 30. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 31BorderlessCollaboration EdgeArchitecture
  31. 31. Collaboration Enterprise Edge ArchitectureProducts, Versions and Baseline SupportUnified CMTMSConferencingVPNEdgePSTNTDMISDNVoiceVideoVCS-CDSPCall ControlVoice and VideoGatewaysPSTN/ISDNVPNconcentratorVCSExpresswayCUBESupported products and versions:• UC Manager version 9.1.1 or later• Video Communication Server (VCS) version X7.2.2• VCS Expressway X7.2.2• ASA VPN concentrator 9.0• Cisco IM&P server 9.1 or compatible• TelePresence Management Suite (TMS) 14.2• ISR / CUBE IOS 15.1.4M• ISDN Gateways 2.1• Endpoints TC6.1, Jabber 9.2Baseline support:• Registration for IP phones, video endpoints andJabber from Internet• Supplementary services for endpoints calls• Endpoint Presence• Able to dial E.164/URI/E911• Access directories / address book• PSTN connectivity (IP/TDM/ISDN)• Ability to support clusters (failover/load balancing)• Security for registration, signaling and media
  32. 32. Collaboration Enterprise Edge ArchitectureOverviewScenarios:• Extend enterprise network with VPN• Endpoint registrations• Basic calls and supplementary services• Soft clients with IM&P• Enterprise dial plan and directories• External video through VCS Expressways• Endpoint registrations (selective)• Basic calls and supplementary services• Enterprise dial plan and directories• Central PSTN control though Unified CM• Video gateways for ISDN• IP PSTN SIP trunking through CUBE
  33. 33. Collaboration Enterprise Edge ArchitectureVisionUnified CMEnterprise call control,IM&P and conferencingSIP TrunkSIP/H.323SIP/XML RPCPSTNLong Term Vision “End Goal”:Enterprise Edge• VCS ExpresswayEnterprise gateway• Integrated voice and video gatewayFirewall appliance• ASA /ISRIntegratedVoice & VideoGWExpressway
  34. 34. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 35Unified CM &applicationsExpresswayFirewall TraversalAnyConnectVPN• Layer 3 VPN Solution• Secures the entire device and it’scontents• AnyConnect allows users accessto any permitted applications &data• Expressway• Session-based firewall traversal• Allows access to collaborationapplications ONLY• i.e. Personal data not routedthrough enterprise network• Ex. JabberVideo (Movi)
  35. 35. Collaboration Enterprise Edge ArchitectureToday’s RecommendationVCS-CUnified CMScheduled voiceconferencingSIP Trunk SIP/H.323 SIP/XML RPCVoice GatewaysVideo GatewaysPSTN/ISDNVCS-ePSTNTDM/ISDNVoice/VideoVPNASACUBESIP/H.323/MGCP/QSIGHigh Level Recommendation:Extend collaboration network with VPN• Remote/teleworker endpoints registering to CUCM• Used with VPN router for devices not supported by VCSsuch as TX series, CTS series, IP phones• Endpoints that have built in VPN client• Support for Jabber IM and presence functionalityVideo over IP/Internet (VCS Expressway)• External connectivity using Internet (VPNless)• External endpoints such as EX series, C series, Profileseries, Jabber for iPad register with VCS Expressway• B2B video callsGateways• Voice gateways (TDM)• Video gateways (ISDN)• IP gateways with CUBE for voice
  36. 36. Collaboration Enterprise Edge ArchitectureVPNBenefits• Extend enterprise network to remote locations, teleworkers, or mobile workers• The VPN head-end options include• ASA, ISR or ASR• Voice, video, and data traffic is secured in an encrypted tunnel over the internet• voice and video can also be encrypted with TLS and SRTP inside the VPN tunnel for additionalsecurity but requires cluster wide encryption support (mixed mode) on CUCM.• Use cases• Cisco Jabber on phones, tablets, or laptops.• Teleworker• Remote locations
  37. 37. Collaboration Enterprise Edge ArchitectureVCS ExpresswayBenefits• NAT/FW Traversal• URI and Number based call routing• Interworking for protocols• Secure calls with TLS and SRTP• Supports Clustering• Redundancy for registration and call control• Scale based on per server / per cluster capacities• Use cases• Remote users• Mobile users• Business to business calling
  38. 38. Collaboration Enterprise Edge ArchitectureGatewaysBenefits• ISR gateways for PSTN connectivity• Cisco TelePresence gateways for Video• Prefix based dialing to differentiate voice and video calls• SIP trunking through service provider using CUBE• Use cases• PSTN or ISDN connectivity• Service provider trunk services
  39. 39. Collaboration Enterprise Edge ArchitectureConsiderations• There is no single box solution• IM may not possible when using VCS-e or CUBE deployments• No call preservation possible• VPN solution does not optimize media between the endpoints• Jabber soft clients cannot dial URI (fix coming in upcoming release, Movi and Jabber for ipad can dial URI)• Immersive endpoints can use VCS-CVCS-E for B2B calling• No automatic detection for voice calls and Video so they can be serviced by respective gateways, Todaynumber based calls can be routed to PSTN gateways and URI based calls to VCS Expressway
  40. 40. Key Takeaways• Multiple architectures supported for both CUCM and VCS centric customers• Endpoint registration supported on CUCM and VCS• Ad-hoc resources should be fronted by Conductor for both CUCM & VCS deploymentsfor redundancy and resiliency• To ensure availability, scheduled conferences should have dedicated MCU/TS resources• Expressway for remote and B2B video over the internet (VPN-less).• VPN for existing voice-centric applications
  41. 41. © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 42Cisco ConfidentialCisco Connect 42© 2012 Cisco and/or its affiliates. All rights reserved.Q&A
  42. 42. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 43© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 4343© 2012 Cisco and/or its affiliates. All rights reserved.Backup Slides
  43. 43. Complete Your Paper“Session Evaluation”Give us your feedback and you could win1 of 2 fabulous prizes in a random draw.Complete and return your paperevaluation form to the room attendantas you leave this session.Winners will be announced today.You must be present to win!..visit them at BOOTH# 100
  44. 44. © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 49Thank you.

×