Collaboration Architecture-2013 Cisco Live Local
 

Collaboration Architecture-2013 Cisco Live Local

on

  • 4,377 views

The Cisco Collaboration Architecture's modular elements work together to deliver compelling collaboration experiences with companies. This framework enables you to develop an investment plan that ...

The Cisco Collaboration Architecture's modular elements work together to deliver compelling collaboration experiences with companies. This framework enables you to develop an investment plan that helps to ensure interoperability with your existing and future assets.

Statistics

Views

Total Views
4,377
Views on SlideShare
4,377
Embed Views
0

Actions

Likes
3
Downloads
457
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Collaboration Architecture-2013 Cisco Live Local Collaboration Architecture-2013 Cisco Live Local Presentation Transcript

  • Local Edition
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionCollaboration ArchitecturePete DePalmaCollaboration CSE
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicPrerequisites•  You have a basic understanding of networking concepts•  LAN, WAN, IOS, CLI, SNMP, SYSLOG, etc.•  You have a good understanding of CUCM•  You have a solid understanding of following core Cisco UC componentsand what they do•  CUBE, CUCM IM/P, Unity Connection, VCS-C/E•  You have a basic understanding of base UC protocols or standards•  SIP, XMPP, H.323, DNS•  You are familiar with Cisco video infrastructure and its components
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicAgenda•  Core Components with Clustering over the WAN andDual DC•  SIP Trunking and Gateway TIPs•  Dial Plan (URI)•  CUCM + Video Architecture•  Collaboration on the Edge•  Medianet
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionClustering Over The WAN or Dual DataCenter Architecture
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM Clustering Over The WANNetwork Requirements•  Delay (Latency)80ms Maximum Round Trip Time (RTT)between any two servers (increased in v6.1)Measure Delay from IOS next to VoS you aretesting•  JitterNo certain restriction, however IPPrecedence 3 ICCS traffic should beminimized using Quality of Service (QoS)features. (CBWFQ)•  Error RateNo Loss; Although Unified CM will toleraterandom errors, they could result in impairedperformance of the clusterHigh Quality point-to-point circuitrecommended (w/ SLA)CSACSE-R2#pingProtocol [ip]:Target IP address: 10.89.178.1Repeat count [5]:Datagram size [100]: 500Timeout in seconds [2]:Extended commands [n]: ySource address or interface:Type of service [0]: 104Set DF bit in IP header? [no]:Validate reply data? [no]:Data pattern [0xABCD]:Loose, Strict, Record, Timestamp, Verbose[none]:Sweep range of sizes [n]:Type escape sequence to abort.Sending 5, 500-byte ICMP Echos to 10.89.178.1, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 mef = dscp 46 = 101110 = tos 0xb8 (184) = ip prec 5af31 = dscp 26 = 011010 = tos 0x68 (104) = ip prec 3af32 = dscp 28 = 011100 = tos 0x70 (112) = ip prec 3cs3 = dscp 24 = 011000 = tos 0x60 (96) = ip prec 3
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM Clustering Over The WANWhat is Intra Cluster Communications?Intra Cluster Communications (ICC)  Database traffic from the IBM Informix Dynamic Server (IDS)database. Per Subscriber  ICC Signaling (ICCS) real-time traffic, which consists of signaling, calladmission control, and other information regarding calls as they areinitiated and completed.  CTI Manager real-time traffic used for CTI devices involved in calls orfor controlling or monitoring other third-party devices on the UnifiedCM servers.  Calculate BW for all the above
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Publicccm.exe ccm.execcm.exe ccm.exeCTIManager MoHServerTFTPServerPublisherSoftwareConferencingDatabase SubscribersDatabase (DB)ReplicationUnified CMClusterCUCM Clustering Over The WANUnified CM Clustering: DB Replication and ICCSDBDBDBDBDBDB DBDBDBDBDBDBDBDB DBDBICCSDBDBCall Processing ServersMAX = 21 MAX = 16
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM CoW Bandwidth CalculationICCS per BHCA across WAN•  A minimum of 1.48Mbps (T1) bandwidth is required for 0 (zero) up to10,000 BHCA from a site across the WAN.•  For deployments with more than 10,000 BHCA, the following equationshould be used (Delay, max RTT in msec) :‒  Total Estimated ICCS Bandwidth (Mbps) = [Maximum BHCA/10000]*[1 +(0.006*Delay)]•  When shared lines are involved across the WAN, there is additionaloverhead. The following equation should be used:[Maximum BHCA/10000]*[1 + (0.006*Delay) + (0.012 * Delay * Shared-line) + (0.65 * Shared-line)]Shared-line = Avg number of additional phones on which a DN is shared across theWAN.#1
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCoW Bandwidth CalculationDB Traffic Per Remote Subscriber•  Minimum of 1.544 Mbps (T1) bandwidth is required for database and other inter-server traffic for every subscriber server remote to the publisher.•  3 Subscriber servers located across WAN from Pub:3 x 1.544 Mbps = 4.632 MbpsPUB SUB2SUB3SUB4SUB1#2P2P ConnectionMPLS Guaranteed
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM CoW Bandwidth CalculationCTI over WAN for 8.6(2)+  For customers who also want to deploy CTI Manager at another site across from other CUCM Subscribers,the following formula can be used to calculate the CTI bandwidth (Mbps):Total CTI Bandwidth (Mbps) =[Maximum BHCA/10000]*.53  For customers who also want to deploy JTAPI over the WAN to CUCM subscriber(s), the following formulacan be used to calculate the CTI bandwidth (Mbps):Total CTI Bandwidth (Mbps) =[Maximum BHCA/10000]*.28PUBCTI ManagerProcessSUB#3UCCXP2P ConnectionMPLS GuaranteedCTI Controlled DevicesSUBCTI ManagerProcessX
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicTECVVT-1001CUCM CoW Bandwidth CalculationExample: Dallas, Chicago, Denver
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Deployment‒ RTT = 80msecDallas – Publisher, 2 Subscriber nodesChicago – 2 Subscriber nodes, 1 TFTPDenver – 2 Subscriber nodes•  BHCA estimates out‒ Dallas phones call 4000 Chicago/1000 Denver phones per hourBHCA = 5000‒ Chicago phones call 6000 Dallas/1500 Denver phones per hourBHCA = 7500‒ Denver phones call 500 Chicago/2500 Dallas phones per hourBHCA = 3000‒ Total BHCA = 15500CUCM CoW Bandwidth CalculationExample: Dallas, Chicago, Denver
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Total ICCS BandwidthBHCA = 5000 (to Chi/Den)6000 (from Chi) + 2500 (from Den)= (13500/10000)*(1+0.006*80)= 1.35 * (1+0.006*80)= 1.998 Mbps•  Total DB Bandwidth= 5*(1.544)= 7.72 Mbps•  Total Dallas Bandwidth= 9.718MbpsCUCM CoW Bandwidth CalculationsExample - Dallas to MPLSBandwidthBandwidth MPLSDallasDenverChicagoBandwidth
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Total ICCS BandwidthBHCA = 7500 (to Dal/Den)4000 (from Dal) + 500 (from Den)= (12000/10000)*(1+0.006*80)= 1.20 * (1+0.006*80)= 1.776 Mbps•  Total DB Bandwidth= 3*(1.544)= 4.632 Mbps•  Total Calculated Bandwidth= 6.408 MbpsCUCM CoW Bandwidth CalculationsExample – Chicago to MPLSBandwidthBandwidthMPLSDallasDenverChicagoBandwidth
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Total ICCS BandwidthBHCA = 3000 (to Chi/Dal)1000 (from Chi) + 1500 (from Dal)= (10000/10000)*(1+0.006*80)= 1 * (1+0.006*80)= 1.48 Mbps•  Total DB Bandwidth= 2*(1.544)= 3.088 Mbps•  Total Calculated Bandwidth= 4.568MbpsCUCM CoW Bandwidth CalculationsExample – Denver to MPLSBandwidthMPLSDallasDenverChicagoBandwidthBandwidth
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM Session Manager Edition”SME” - What and Why•  SME = CUCM …there is no difference in the SW•  Introduced and supported in CUCM 7.1(2)•  SME deployed for‒ Trunk aggregation‒ Dial Plan aggregation‒ In combination with the above, logical separation of functions‒ Massive CPS aggregation
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM Session Manager AdditionDelay and BWPre-UC 9.1CoW BW and delay (80ms) same as CUCMUC 9.1+BW 1.544 Mbps between call processing and/or between pub and subsDelay <500ms between call processing nodesor between pub and subs
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicUnity ConnectionArchitecture ReviewSIP Trunk From CUCM to UcxnUnity ConnectionCUCMUp to 250 Sessionsor “Ports”TUIEmailClient /VMOHTTPEWSMediaSenseJabber Mini Inbox•  Scalable to 20,000 Users with all featureSpeech Rec, Single Inbox, Integrated Messaging, etc.•  CUCM shall be SIP Integrated•  Exchange Integration via EWS (Office 365 as well)•  Clients connect in various ways•  Google Integration via Esnatech•  MediaSense for video voicemail (10.x)IMAPEmailClientSecure IMAP ServicesWeb ServicesGoogle API’sEsnatechOffice365EWS
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSecondaryWriteable DBPrimaryUnity Connection CoWHA FunctionalityUnity Connection HA PairUp to 20,000 UsersUp to 250 PortsAccess to all User Interfaces (TUI, VUI, IMAP, Admin, etc…)HeartbeatsDatabaseMessagesSecurity and CertificatesPrimaryWriteable DBUp to 250 PortsSecondaryProxy to PrimarySplit Brain Recovery (SBR)DatabaseProxy to Primary
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicDallasExchangeMailbox ServerUnity Connection CoWCoW BW ConsiderationsUnity ConnectionActive/Active ClusterCUCMClusterChicagoExchangeNetworkBandwidth/LatencyWANGuaranteed bandwidth with no steady-state congestion:–For 50 voice messaging ports on each server—7 Mbps–For 100 voice messaging ports on each server—14 Mbps–For 150 voice messaging ports on each server—21 Mbps–For 200 voice messaging ports on each server—28 Mbps–For 250 voice messaging ports on each server—35 MbpsClustering over the WAN with Single Inboxdoubles the bandwidth requirements if Exchangeis only accessible over the WAN connectionFor more than 2000 users and/or more than 80 millisecondsof latency, see Design Guide.Guaranteed bandwidth with no steady-state congestion:–For 50 voice messaging ports on each server—14 Mbps–For 100 voice messaging ports on each server—28 Mbps–For 150 voice messaging ports on each server—42 Mbps–For 200 voice messaging ports on each server—56 Mbps–For 250 voice messaging ports on each server—70 MbpsUse the CLI command utils cucnetworking dscp on to markintracluster data and message trafficwith a differentiated services codepoint (DSCP) value of 18
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicUnity Connection and SMECentralization of Ucxn with SMEPlaces call toEurope ClusterPhoneFNA to Ucxn with redirected number(Orig. Called Pty #)(e)MWI relayUnsolicited Notify•  To deliver a FNA/RONA to correct mailbox,Ucxn must see Original Called Party/Redirecting Number•  Ucxn controls MWI in SIP environmentswith SIP Unsolicited Notify•  If H.323 trunks or H.323/MGCP GWs arepresent in the mix, enabled redirectingnumber IE delivery (not shown)•  Apply SIP trunk security profile to all trunksin path – make sure “Accept UnsolicitedNotifications”•  Must Configure “Redirecting DiversionHeader Delivery” on SIP trunks (bothinbound and outbound)
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Previously called CUPS (Cisco Unified Presence Server), now calledCUCM IM and Presence Server•  Unified CM IM & P shares a user database (native) with UCM•  User’s are then synchronized to Unified CM IM & P from UCM (via CUCMLocal or LDAP)•  One CUCM IM&P cluster can only service one CUCM cluster•  Multiple CUCM IM&P clusters can service one CUCM clusterCUCM IM and Presence ServerRelationship to CUCM
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicIM-Only ModeFull Unified Comm. ModeOption 1 Option 2CUCM IM and Presence Server2 Modes of Operation
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicVolatile Persistent Data (Login state)Times Ten Soft State Data (Presence info)IDS Global User Data ReplicationCisco  Unified  Presence  Cluster  Cisco  UCM    CTI/QBESIP TrunkAXL/SOAPCUCM IM and Presence ServerSingle Cluster Architecture – All WorkloadsSub Cluster15,00015,00015,00045,0007,500 7,5007,500 7,5007,500 7,50015,000 015,000 015,000 0IM, Presence, and Other Work Loads (Call Control, VM, etc.)
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicVolatile Persistent Data (Login state)Times Ten Soft State Data (Presence info)IDS Global User Data ReplicationCisco  Unified  Presence  Cluster  Cisco  UCM    CTI/QBESIP TrunkAXL/SOAPCUCM IM and Presence ServerSingle Cluster Architecture – IM/P OnlySub Cluster25,00025,00025,00075,00012,500 12,50012,500 12,50012,500 12,50025,000 025,000 025,000 0**IM and Presence Only
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicDelay 80ms5 Mbps per sub-clusterMPLSCUCM and CUCM IM&P should be local to one anotherDelay between CUCM IM&P sub-clusters relative to # of ContactsCUCM IM and Presence ServerIntra-Cluster BW and Delay
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  This is not just federation,but proprietary Cisco-on-Cisco intra-domain, inter-cluster exchange of full UCworkloads (voice, video, IM/P, directory)•  Assumes same domain<user>@abc.com•  If these were differentdomains, then would simplybe inter-domain federation•  BW relative to # of Contactsand User distributionamongst servers. Consistsof contacts being monitoredand messaged•  Implicit Federation (Cisco-on-Cisco intra-domainfederation)Unified CM IM & P  Cisco  UCM  Unified CM IM & P  Cisco  UCM  CUCM IM and Presence ServerInter-Cluster PeeringXMPPAXLSOAPURI Re-writes
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public  Provide site redundancy for disaster recovery  UCCX Local to CUCM, else see CTIoW requirements  Latency: 80 ms RTT between UCCX nodes  Latency: 80 ms RTT between UCCX and Exchange for agent email  Latency: 300 ms RTT between UCCX and remote agentsMPLS  1.2 Mbps between UCCX servers (DB replication, heartbeat, etc.)  800 Kbps between UCCX and CUCM (JTAPI)  In example above, 2 Mbps  Does not include mediaUnified Contact Center Express (UCCX)CoW BW and Latency
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  VCS-C and VCS-E primarily becomingsystem for Internet Video FirewallTraversal including video to/from TP-enabled WebEx•  Utilizes H.460 or variant to traverseFW…meaningonly outbound ports needed on FWNo H.323 or SIP applicationinspection wanted or needed•  Beginning to register all devices toCUCM•  VCS can be completely virtualized•  Why?To securely enable B2B calls overthe Internet to your entire UCInfrastructureVery, very important feature comingin AugustVideo Control Server (VCS)What and Why?
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMPLSVCS (Video Control Server)Dual Data Center Design – Common ExampleVCS-C-2Internet 2VCS-E-2VCS-C-1Internet 1VCS-E-1H.323 and SIP SRV Records for inbound routing and redundancy (not all records shown)_sip._tcp.cisco.com service = 0 0 5060 vcs-e-1.cisco.com_sip._tcp.cisco.com service = 0 0 5060 vcs-e-2.cisco.com_h323cs._tcp.cisco.com service = 0 0 1720 vcs-e-1.cisco.com_h323cs._tcp.cisco.com service = 0 0 1720 vcs-e-2.cisco.com“cisco.com”DNS automatic discovery of vcs-c.cisco.comto IP address of VCS-C-1 and 2Endpoint will re-register appropriatelyCUCM cluster can use SIP routingto route outbound appropriatelyVCS-E-1 outage, CUCM does notknow, so VCS-C-1 should routeover to VCS-C-2 for outboundredundancyX Neighbor zone for any VCS-C-2registered endpoints
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionSIP Trunking and Gateway Tips
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  SIP Trunks support the “Run On All Unified CM Nodes” and “Up to 16 destination IP addresses” features•  H323 and MGCP Trunks to gateways use standard CUCM Groups and 1 IP destination•  Using standard Call Manager Groups (rather than Run on All Nodes) increases call set up traffic between nodeswithin a cluster•  Note – MGCP Trunks are only active on one node in the Call Manager Group (as the signaling channel is backhauled to CUCM)•  Cisco’s focus on SIP. Not H.323 or MGCP•  MGCP complicates upgrades (CUCM/IOS version dependent)H323ICT Trunk H323 Trunk AH323 Trunk BSelected outbound TrunkRoute ListSIPICT Trunk MGCP Trunk AMGCP Trunk BSelected outbound TrunkRoute ListCUCM and SIP TrunkingSIP versus H.323/MGCP
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Outbound SIP Trunks, H323 Inter Cluster Trunks and Route Lists can take advantage of the Route Local Rule byusing the “Run On All Unified CM Nodes” feature•  The Route Local Rule•  If the CUCM node that the inbound call arrives on – also has an instance of the selected outbound trunk for thatcall – then use this node to onward route the call•  The Route Local rule reduces (and can eliminate) call set up traffic between CUCM nodes within a clusterCUBECUBESIP TrunkSIP/H323ICT TrunkCUBECUBESIP Trunk ASIP/H323ICT TrunkRoute ListSIP Trunk BCUCM and SIP TrunkingSIP- Run on All Nodes
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  OPTIONS Ping is activated on a per SIP Trunk basis and run on each node’s SIP daemon to each destination•  Use between CUCM servers, or between CUBE and CUCM servers. But, 3rd party supported also•  CUCM will not attempt to establish a new call to an unavailable remote peer•  SIP Trunk - “In Service” whilst one remote peer is reachable•  SIP Trunk - “Out Of Service” state when all remote peers are unreachable•  Provides dynamic reachability detection•  Pre CUCM 8.5 Trunks - Per call time outSIP TrunkSIP ICT TrunkCUBECUBECUCM and SIP TrunkingOptions Ping (CUCM 8.5+)
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSIP Trunk SP SIP TrunkCUBEIP PSTNA(408)100-1010(510)100-1010(919)200-2010(919)200-2000(510)100-1000(408)100-1000voice class e164-pattern-map 100e164 919200200.e164 510100100.e164 408100100.dial-peer voice 1 voipdestination e164-pattern-map 100codec g729r8session target ipv4:10.1.1.1voice class e164-pattern-map 100url flash:e164-pattern-map.cfgdial-peer voice 1 voipdestination e164-pattern-map 100codec g711ulawsession target ipv4:10.1.1.1! This is an example of thecontents of E164 patterns textfile stored in flash:e164-pattern-map.cfg919200201051010010104081001010Site ASite BSite CSite ASite BSite CG729 SitesG711 SitesProvides the ability to combine multipledestination-patterns targeted to thesame destination to be grouped into asingle dial-peerCUBEDial Plan Enhancements
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUBEInbound Dial Peer Matching EnhancementsSIP Trunk SP SIP TrunkCUBEAInbound LAN Dial-PeerIPPSTNInbound WAN Dial-PeerInbound CallsOutbound Callsdial-peer voice 5 voipincoming called-number 654321dial-peer voice 6 voipanswer-address 555dial-peer voice 7 voipdestination-pattern 555voice class uri 1001 siphost ipv4:10.1.1.1voice class uri 2001 siphost ipv4:10.2.1.1dial-peer voice 1 voipincoming uri via 1001dial-peer voice 2 voipincoming uri request 2001dial-peer voice 3 voipincoming uri to 2001dial-peer voice 4 voipincoming uri from 1001Received:INVITE sip:654321@10.2.1.1 SIP/2.0Via: SIP/2.0/UDP 10.1.1.1:5060;x-route-tag="cid:orange@10.1.1.1";;branch=z9hG4bK-23955-1-0From: "555" <sip:555@10.1.1.1:5060>;tag=1To: ABC <sip:654321@10.2.1.1:5060>Call-ID: 1-23955@10.1.1.1CSeq: 1 INVITEContact: sip:555@10.1.1.1:5060Supported: timerMax-Forwards: 70Subject: BRKUCC-2934 SessionContent-Type: application/sdpContent-Length: 2261234Priority
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUBEMedia ForkingCisco Search/Play demo app-or-Partner Applicationmedia class 1recorder parametermedia-recording 20dial-peer voice 1 voipdescription dial-peer that needs to be forkedsession protocol sipv2media-class 1dial-peer voice 20 voipdescription dial-peer pointing toMediaSensesession protocol sipv2session target ipv4:<Mediasense_IP>Needs to matchSIPSIPSIPASP SIPCUBERTPRTP RTPMediaSense•  Gateway full time recording•  Recording at the dial-peer level•  CUBE calls the MediaSense Server•  Entire call recorded from cradle to grave•  Record entire time a customer in the IVR•  Record even after subsequent transfers•  CUCM 10.x, Centralized Ad-hoc recording by phone(CUCM to CUBE APIs)
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUBEHigh AvailabilityASR1006DualForwardingplane HWDual Controlplane HW(CPU)CUSP CUSP•  L2 Box-to-Box redundancy•  ISR G2 (Stateful failover)•  ASR 1001 & ASR 1004 (Stateful failover)•  Local redundancy and geographical if layer 2 SLA’s met•  ASR needs L2 swjtch for control/data checkpointing•  Clustering with load balancing•  All platforms•  Load balancing by•  SP call agent•  Cisco Unified SIP Proxy•  Local and geographical redundancy•  Inbox redundancy•  ASR 1006•  Stateful failover•  Local redundancyActiveVirtualIPCUBECUBEVirtualIPStandbySIP SPSIP SPISR-G2 HA
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionDial PlanURI Focused
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  What is it?‒ SIP Uniform Resource Identifier‒ Typically copy your email addressex. alice@cisco.com‒ Popular for Internet video calls today, willbecome way to call in future•  Why?, b/c its globally routable and friendly•  But E.164 is not going away any time soon•  Cisco UC 9.x implements blended identity•  In CUCM, is an alias to the DN‒ Primary plus up to 4 more will ring DN SIP URI DialingIntro
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSIP URI RoutingThe Routing Problem – This ain’t like E.164 routing•  Host part of URIsmight identify home cluster•  Reachability establishedthrough SIP route patterns forhost parts•  Requires hierarchical URI scheme42alice@sfo.cisco.com bob@nyc.cisco.comjkrohn@fra.cisco.comny.cisco.comfra.cisco.com•  What if it is flat???alice@cisco.comjkrohn@cisco.combob@cisco.com
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicILS NetworkingURI Learning /Routing•  Components of end-to-endURI dialing/routing‒  ILS networking‒  URI propagation‒  SIP trunk‒  SIP route pattern•  ILS networking is foundation for exchange or URI reachability information•  SIP connectivity is foundation for call routing based on SIP route patterns•  URI propagation is enabled independent of ILS networking‒  Establish ILS topology, then build supporting SIP trunking topology underneath‒  For small number of clusters, ILS topology usually will follow SIP trunking topology43ILS networkingURI propagation jerry@cisco.com (sjc.cisco.com) gerrard@cisco.com (fra.cisco.com)jerry@cisco.comgerrard@cisco.comSIP TrunksSIP Route Patternfra.cisco.comSIP Route Patternsjc.cisco.comjerry@cisco.comsjc.cisco.comgerrard@cisco.comfra.cisco.com
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  How do we route calls between VCS andCUCM environments•  VCS does not talk ILS•  From VCS, can direct calls into any CUCMcluster, as all URIs known in the ILS network•  Be as specific as possible from VCS to CUCM(ex. *.cisco.com)•  Default SIP route towards VCS towardsInternet•  So how do we solve a flat naming spacewithout routing loops?SIP RP*.*Search Rule*.cisco.comCUCM and VCS TogetherURI Routing Example
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM, loop prevention via CSS andPTsVia ILS, CUCM has full knowledge of all specificURIs, so no need for SIP route patterns amongstclustersCUCM Trunks have CSS on themDon’t allow the CUCM inbound trunk from VCS tosee the SIP route pattern of *.*VCS has 3 mechanisms:Search Rule, call coming from specific zone (trunk)is not sent back from where it come unless it’s beenmodifiedHop Count (0, does not route)Source Zone (trunk)1. Joe callssally@cisco.comvia Jabber2. CUCM cluster(s) checkILS DB, nothing found, sofollows *.* SIP routepattern towards VCS3. VCS-C checks localzone for sally@cisco.comNothing found, sends “anyalias” to VCS-E4. VCS-E checks localzone for sally@cisco.comNothing found, ifunmodified, stops routingXCUCM and VCSURI Routing and Loop Prevention
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  RegistrationNatively register video endpoints to CUCM w/SIP if limitations are not an issue(FECC, Phone Book)H.323 endpoints will be registered to VCSSIP old endpoints can be registered to VCS•  SIP to H.323 Interworking takes places on VCS•  +E164 scheme for numbers (H.323 ID on VCS registered endpoints)•  SIP on all CUCM or VCS registered endpoints and SIP VCS endpointsCUCM and VCS TogetherMisc. Dial Plan Recommendations
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Single Number Reach (SNR) on CUCMConcept of “Remote Destinations” . May have many (RD1, RD2…)•  FindMe on VCS“SNR for the video world”, but URI-basedConcept of FindMe URI (ex. joe@cisco.com) and device specific URIs (ex. joe.movi@cisco.com,joe.ex90@cisco.com)Used when you have multiple video devices provisionedFindMe URI is what is called, device URIs are dialed and searched for•  In Mixed CUCM / VCS environment, Goal is toHave all devices ring on both CUCM side and VCS side when user is dialed on either sideAvoid loopsCUCM and VCS TogetherSNR and FindMe
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  In this Example 1, FindMe is onVCS and is needed, so VCS “owns”user’s main URIs and will not routeit to CUCM•  Disable all device-specific URIsfor FindMe in TMS (uncheck “initial”)•  Add globalized number on CUCMside to FindMe in TMS and checkinitial•  For each device on VCS (ex.EX90, Movi), add the specific URIas an alternate/remote destinationin CUCM options pagesCUCM and VCS TogetherSNR Functionality with FindMe Example 1
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 49Unified CMVCS-CJoe’s VCS DevicesVCS Expressway*.* to SME Any Alias to VCS-ESMEJabber (movi)EX 90Registered joe.ex90@cisco.comRegistered joe.movi@cisco.comjoe@cisco.com called from VCS orInternetFindMe URIjoe@cisco.com 85551212FindMe to 85551212Regular E.164 routing85551212SNR to RD’sJoe’s CUCM Phone85551212EX 90RD1 joe.ex90@cisco.comRD2 joe.movi@cisco.com*.* toVCS-CAny Alias to VCS-CRoute (8d{7}) toCUCMRegular E.164 routing85551212CUCM and VCS TogetherSNR in Action (With FindMe) - Example 1Someone Calls
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  In this Example 2, all video usersare also on CUCM and using baseSNR feature.•  Here, CUCM owns your main URI•  For each device on VCS (ex.EX90, Movi), add the specific URI asan alternate/remote destination inCUCM options pagesCUCM and VCS TogetherSNR Only (Without FindMe) - Example 2
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 51Unified CMVCS-CJoe’s VCS DevicesVCS Expressway*.* to SME Any Alias to VCS-ESMEJabber (movi)EX 90Registered joe.ex90@cisco.comRegistered joe.movi@cisco.comjoe@cisco.comRoute *@cisco.comILS Route joe@cisco.comto CUCM85551212Joe’s CUCM Phone85551212EX 90RD1 joe.ex90@cisco.comRD2 joe.movi@cisco.com*.* toVCS-CAny Alias to VCS-Cjoe@cisco.com isalias to 85551212Ring 85551212CUCM and VCS TogetherSNR in Action (Without FindMe) - Example 2Someone Calls
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 52Unified CMVCS-CVCS ExpresswaySMEjoe@cisco.comRoute *@cisco.comILS Route joe@cisco.comto CUCMJoe’s CUCM Devices85551212joe@cisco.comEX 90Any Alias to VCS-Cjoe@cisco.com isalias to 85551212Ring joe@cisco.com whichis alias to 85551212(shared line from there)CUCM and VCS TogetherNo Jabber Video / All CUCM Registered - Example 3Someone Calls fromInternet
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionCUCM and Video ArchitectureVideo is the new Voice
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Cisco strategy moving forwardUtilize API into video infrastructure (Conductor + Bridges)Utilize Cisco MRGLs and intelligent bridge selectionGoal is to leverage a single video infrastructure across entire system and UC workloadsGoal to service standard to immersive TP for ad-hoc, rendezvous, and scheduled callsGoal is to optimize bridge resources, bridge placement and media pathWith H.265 and optimized bridging technologiesH.265 SVC, SW switching Mixed with HW bridgingDesktop video a reality•  PVDM3sCUCM and Video ArchitectureCisco’s Bridging Strategy
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Is at the heart of Cisco’s bridging strategy•  Conductor is a layer of abstraction between callcontrol and video bridging resourcesIt virtualizes pools of MCUsIt leverages mixed pool resourcesIt has bridging intelligence, can create custom policy•  A product which will evolve with technology•  Must understand types of conferencesAd-Hoc (ex. CUCM), Rendezvous, ScheduledCUCM and Video ArchitectureConductor – What is itMCU 2MCU 1MCU PoolConductor
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSIP Trunk SIP/H.323 registration SIP/XML RPC SCCP registration•  Audio conferencingDistributed pool of ad hocvoice resources (nodifferent than today)•  Centralized Video FW/Internet Traversal•  Centralized VideoConferencingAd hoc: Conductorscentralized, connected toeach UC ManagerRendezvous: Conductorcluster trunked to SMEScheduled: Separate MCU(s) or TelePresence Server(s) registered to local VCS•  Distributed Ad-hoc andRendezvous resourcesUnified CM Unified CMUnified CMSessionManagementEditionAd hocRendezvousvideo conferencingConductorAd hoc voiceconferencingScheduled VideoconferencingAd hoc voiceconferencingAd hocRendezvousvideo conferencingAd hoc voiceconferencingAd hocRendezvousvideo conferencingTMSCUCM and Video ArchitectureConductor Architecture Today Multi-Cluster CUCM ExampleVCS-C VCS-E(Centralized)
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCM and Video ArchitectureFuture Conductor CapabilitiesAd-hocCUCM ManagedRendezvous / ScheduledVCS / Conductor ManagedCUCMor VCSTP Conductor Orchestrator“Virtual Bridge”“Virtual Bridge” – Pooled MCUs•  Leverage combined resources for Rendezvous/Scheduled and Ad-hoc conference calls (Audio andVideo). Freely mix/match MCUs•  Will intelligently contain Full-HD from HD, from SDcalls to optimize DSPs (TP Server only)User Site A schedulesConference: 2 endpointsSite A, 3 at Site B•  Optimally places endpoints on MCUs to minimizebandwidth and resources. Centralized CAC onCUCMWAN1 Stream Across WAN,uses minimal resourceson both bridges usingrules in TP ConductorTP Conductor Rule: If URI contains“lecture”, automatically record and streamTCSSite A (ad-hoc andRendezvous/Sched)Site B (ad-hoc andRendezvous/Sched)
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSIP Trunk SIP/H.323 registration SIP/XML RPC SCCP registration•  Centralized video FW/Internet Traversal•  Single centralized Conductorattached to all CUCMs withcentralized CAC•  Distributed Resourcesservicing all types of calls(Ad hoc, Rendezvous, andScheduled)•  CUCM registered devices•  Greatly Simplified!!!Unified CM Unified CMUnified CMSessionManagementEditionAd hocRendezvousScheduled videoconferencingConductorAd hoc voiceconferencingAd hoc voiceconferencingAd hocRendezvousScheduled videoconferencingAd hoc voiceconferencingAd hocRendezvousScheduled videoconferencingTMSCUCM and Video ArchitectureConductor Architecture Tomorrow Multi-Cluster CUCM ExampleVCS-C VCS-E
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCUCMandVideoArchitectureConductorOperation
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionCollaboration on the Edge
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCollaboration on the EdgeCisco Firewall Traversal•  Securely release your internal UC networkfor B2B voice and video communication overthe InternetURI Dialing•  It is a client/server applicationVCS-C is a client to the VCS-E server•  Uses only outbound ports•  No application FW inspection needed“Fixup” SIP or H.323
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  Combining traditional video withWebEx videoVideoSchedulingContent Sharing•  $0 feature•  User Experience with ActivePresence•  What are the RequirementsSee versioningCollaboration on the EdgeWebEx-Enabled TelepresenceTMS 14.2MCU 4.4+or TS 3.0+
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCollaboration on the EdgeWebEx-Enabled TP Scheduling Experience Add WebEx,TP, or bothAdd TP portsto the meetingAdd WebEx tothe meeting•  Simplified scheduling•  Combined WebEx / Video OutlookPlugin•  OBTP TelePresence and WebEx•  TMS Scheduling and Emailscheduling support
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicCollaboration on the EdgeAnyConnect VPN – Option 1•  Requires AnyConnect application•  For optimal end-user experience‒  deploy using client-side certificate authentication (no usercredentials)‒  “Always on” user experience. Almost Transparent to end user•  VPN-on demand with trusted network detection andoptimal GW selection‒  iOS automatically launches with UC Apps•  Access to all applications on devices•  Consistent point-of-entry (VPN strategy)•  AnyConnect Futures (next-gen security)•  Will you have AnyConnect on mobile devices anyways?Jabber Clientswith AnyConnectInternetASAInternalNetwork
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicOutside corporate firewall (Public Internet) Inside corporate firewall (Intranet)Jabber ClientsIPCommunicationsImmersive TelePresencePersonalTelePresenceIM andPresenceVisualVMDirectoryInsideFirewallVCSExpresswayVCSControlUCMOutsideFirewallCollaboration on the EdgeThe Collaboration Edge – Option 2JCFHTTPSUDS/HTTPSVoiceVideoTURNServer
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLocal EditionMedianet
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetWhat? Why?•  What is it?Video is the catalystBlueprint using old and new network features yielding the deepest visibility into your networkinfrastructureApplication aware and dynamic•  Business DriversVideo and explosion of endpoints of different typesHigher expectations of the UC experience  and of the networkReduction of complexity, operational efficiencyWith H.265 and optimized bridging technologies, desktop video a reality
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetPerformance Monitor = VisibilityClassic Netflow / Flexible NetflowNetflow – Interface-based policyScalable, some layer 7 intelligenceProvides bit-rate metrics on flowsLacks RTP Performance MetricsHowever a critical technology for MedianetMedianet Performance MonitorNetwork device discovers traffic flowAdmin defines metrics to gauge performanceUses Modular CLI (Class-Map / Service-Policy)Per-Hop Collection of RTP and TCP metrics*Proactive MonitoringCan also export to Netflow CollectorExports to Netflow Collector• Works with Medianet Mediatrace
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetPerformance Monitor AlertsInstruct monitor to react on upperthreshold limitWill trigger alerts (syslog / snmp)If jitter is greater than 10ms, alertPerformance Monitor detected12msSends alert, along with the detailsof the flow
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetPerformance Monitor Alone?•  I have flow stats on a per-hop basis and I have detailed flow information I can nicely configure•  Below, if I go into each WAN router and issue show commands for a particular flow, I can cobble together andperform manual fault Isolation on RTP stats buried in routers along the media path!•  But who in the heck is going to do that?•  Performance Monitor by itself is not user friendly…way too manual. I need some way to automate the collection flowswhen needed, then illustrate them.
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetMediatrace• Automatic Node DiscoveryAlong Path• Gathers Performance Statsfrom Network Nodes, hop-by-hop• Asks each node along the pathfor information on the particularflow• Initiator – Consumer• Responder – Sender• Below, output cryptic and hardto analyzeHow do I automate this and putit in a usable format??
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetPrime Collaboration Manager • Performs the Mediatrace(even from endpoints in9.0)• Hop by Hop analysis ofMediatrace output• Media Trace supportedon many infrastructuredevices and endpoints(see end of presentation)• Collection of CPUmemory stats on devices(system keyword)• CPCM is asking a devicefor a Media Trace alongthe media path renderingthe collective Perf.Monitor stats.• Triggered by alerts
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetApplication AwarenessNetwork Based Application RecognitionSimplified Policy Configuration (app definitions in router)Deep Packet Application-Level InspectionHistorically used to classify, schedule, queue trafficHas Integration with Flexible Netflow / PerformanceMonitor for monitoringOnly common applications definedFlow MetadataNeed Metadata = Data about Data (in our case, data aboutflows)Need Metadata to be produced by some application(Windows / Linux machine)Need Metadata to be visible, consumed and understood bythe network (Routers and Switches)Need Metadata to be shared to the network edgeNeed Metadata to be transported across the network out-of-band to make the network aware of flows and their identityMust also integrates with Performance Monitor and QoSpolicies
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetFlow Metadata
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicMedianetUsing Flow Metadata for QoS policy – Desktop Example using WebEx•  Before metadata, cannot tell difference between flows inside of a WebEx session•  With Medianet and Metadata support, a WebEx browser tells MSI who reports reported metadata and flow to route•  The router associated the metadata with the flow and relays to network via RSVP (maybe other protocols some day)•  Router configured via MQC-style service policy to monitor flow for that metadata tags in a class-map•  Below is outcome. ACL would have been 30 plus lines of IOS commands.•  ***The same Metadata/class-map technique used with Performance Monitor can be used for Queuing and Scheduling oninterfaces• Used “match protocol” for NBAR,but not all applications supported• Now using “match application”• Can also match on metadata freetext strings
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  JabberShipping with Metadata support only, MSI separately installed (admin priv)Customer concerns around managing large scale, mobile desktop video deploymentsBandwidth management and control (overcomes DSCP marking challenges)Troubleshooting and Performance management (granular level capacity planning and performance monitoring)Adding support for Performance Monitoring and Mediatrace in CY13 – 10.0 system release•  WebExWindows browser only today, MSI separately installed (admin priv)Same visibility issues on desktop as JabberSlightly ahead. Supports Performance Monitoring and Mediatrace for TCP and RTP to Cisco Prime•  CTS/EX/CFull featured MSI embedded and managed by Cisco Prime Collaboration ManagerMedianetEnabled Endpoints
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public•  We canTap into metadata capabilities using the MSI which is now embedded in Cisco endpointsMetadata capabilities can be used for both visibility and QoS techniques, auto-configured ports for QoS, andpacing devices in the right VLAN (not just for phones)•  We will haveMSI built into all of our collaboration endpoints moving forwardMSI could also be used by an endpoint to pull its location and obtain registration information to find it’s serverMSI Generate IPLSA and IPSLA-VO when idle for endpointsWe publish MSI, so key strategic partners can implement MSI into products we integrate with3rd party NMS take advantage of MSI registration. MSI uses DHCP or DNS to find NMS and registers usingREST•  This is a Cisco differentiatorMedianetWhere are we headed
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicNew Collaboration SRND9.xWhat is the Collaboration SRND?Evolution of our UC SRND and TP design guides:  Evolve from UC and TP design to Collaboration  Make video pervasive through doc  Change overall tone of document from voice to collaboration  Emphasize recommended but include supported  Expand scope to include more Social, Cloud and Mobile  Combine UC and TP/Video Design GuidanceCollaboration SRND
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicFeedback•  Give us your feedback and you could win fabulousprizes. Winners announced daily.‒  Receive 20 Passport points for each session evaluationyou complete‒  Complete your session evaluation online now(open a browser throughour wireless network to access our portal) or visit one ofthe Internet stations throughout the Convention Center.•  Don’t forget to activate your Cisco Live Virtualaccount for access to all session material,communities, and on-demand and liveactivities throughout the year.Activate your account at the Cisco booth in theWorld of Solutions or visit www.ciscolive.com.79
  • © 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicRegister for Cisco Live - OrlandoCisco Live - OrlandoJune 23 – 27, 2013www.ciscolive.com/us8080