Enabling Seamless Collaboration with Advanced Session Routing Architectures and Cisco Spark

Transcription

1

2 BRKUCC-3001 Enabling Seamless Collaboration with Advanced Session Routing Architectures and Cisco Spark Johannes Krohn, Technical Marketing Engineer

3 Cisco Spark How Questions? Use Cisco Spark to communicate with the speaker after the session 1. Find this session in the Cisco Live Mobile App 2. Click Join the Discussion 3. Install Spark or go directly to the space 4. Enter messages/questions in the space cs.co/ciscolivebot#brkucc Cisco and/or its affiliates. All rights reserved. Cisco Public

4 Agenda Characteristics of Global Deployments Reference Dial Plan Topologies Global Dial Plan Replication Applications B2B Routing Hybrid Calling with Cisco Spark Large Scale Hybrid Calling Considerations Summary

5 Abstract Global Call Control Architectures involve support for global dial plans and also multiple types of call controls including Communications Manager, Communications Manager Session Management Edition and Expressway complemented with Spark hybrid services. In this session we will cover design consideration for global call control architectures that allow the implementation of global dial plans. We will cover concepts like global +E.164 dial plans, URI dialing, B2B routing in a number of scenarios. For architectures involving multiple independent call controls we will discuss the pros and cons of full mesh trunk topologies vs. hub and spoke topologies involving Communications Manager Session Management Edition and how new concepts like ILS/GDPR can be used to build scalable global dial plans. Finally we will discuss how the integration with Spark hybrid services allows to build seamless integration of global collaboration deployments with Spark. A solid understanding of UCM dial plan fundamentals is a prerequisite. BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 5

6 Characteristics of Global Deployments

7 Characteristics of Global Deployments Scale # of sites # of users/devices Global Footprint single call control w/ global registrations multiple call controls w/ local registrations Regional PSTN access Country specific requirements numbering plan dialing habits dialing domains regulatory requirements BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 7

8 Call Control Consolidation Consolidation of call controls drives # of sites # of users/devices Operational aspects dial plan consolidation management consolidation improves efficiency Scalability limitations standard: 4 call control subscriber pairs each supporting up to 10k * devices Megacluster ** : 8 call control subscriber pairs each supporting up to 10k * devices Other Limits global reach (see next slides) organizational separation * starting with 11.5 scale beyond 10k per subscriber pair is possible but requires engineering review ** engineering review required (contact your account team) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 8

9 Single Call Control w/ Global Registrations BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 9

10 Single Call Control w/ Global Registrations Simplified global routing (single call control) Forwarding Delay impact on signaling (cut-through delay) Legal restrictions (for example data sovereignty) Call Control sizing limitations Reliability (WAN availability/performance) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 10

11 Single Distributed Call Control w/ Local Registrations BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 11

12 Single Distributed Call Control w/ Local Registrations Clustering over the WAN (CoW) requirements 1.5 Mbps between publisher and any subscriber 1.5 Mbps between any two sites max. 80ms RTT between any two subscribers * * great circle RTT Delhi-Los Angeles w/ speed of light: 80ms Simplified global routing (single call control) Forwarding Delay impact on signaling (cut-through delay) ok for intra-region Legal restrictions (data sovereignty) questionable Call Control sizing limitations Reliability (WAN availability/performance) Local survivability, but CoW requirements need to be met BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 12

13 Multiple Call Controls w/ Local Registrations BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 13

14 Multiple Call Controls w/ Local Registrations More complex global routing (between call controls) options discussed later topologies dial plan No Forwarding Delay impact on signaling for intra-region calls Legal restrictions easier to manage (in-country call control) Call Control sizing limitations less restrictive (user base distributed over call controls) WAN availability has no impact of intra-cluster calls Call control separation potentially also driven by organizational constraints Management overhead? (multiple call controls) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 14

15 Call Control Recommendation Limited to single region (country): RTT, legal,... potentially split cluster deployment (multi DC) for redundancy CoW requirements prohibit global deployment local call control failover possible for limited number of sites Not limited to single region Flexible call control deployment decisions: locality organizational legal requirements Interconnection of independent call controls: tbd BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 15

16 PSTN Access Centralized trunking vs. decentralized gateways/trunks Centralized trunking economy of scale; both provider and equipment cost subject to RTT limitations discussed before Limitations (international) number portability local survivability requirements emergency calling requirements WAN topology limitations (RTP bandwidth limitations) Recommendation: it depends hybrid solution BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 16

17 Numbering Plan/Dial Plan Fixed/variable length +1: 10 digit NANP +39, +43, +46, +49, +53,...: variable length NSN Length: +1: 10 digits +41, +61: 9 digits +971: 8 digits National dialing: w/ or w/o trunk access code 1: NANP (same as country code) ITU recommended 0: Europe, +91,... No access code (NDC dialing): +61, International dialing: various access codes 00: ITU recommended, Europe, +91, : NANP 0011: +61 Trunk access code: 9, 0,... Emergency calls: 911, 112/110, 000 Decoder ring: +39: Italy, +41: Switzerland, +43: Austria, +46: Denmark, +49: Germany, +53: Cuba, +61: Australia, +91: India, +971: United Arab Emirates Reference: BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 17

18 Country Specific Considerations Single call control: multiple national numbering plans multiple dialing domains (users sharing same dialing habits) Dial like the Romans do PSTN specifics number formats on trunks Legal considerations TEHO restrictions VoIP regulations legal intercept emergency calling requirements Recommended: consult local agencies for written(!) authoritative information BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 18

19 Reference Dial Plan

20 Requirements multiple national numbering plans per country dialing habits (different dialing domains) single dial plan logic for all countries support for intra-enterprise dialing habits abbreviated on-net (intra/inter-site) features services (VM, conferencing, etc.) URI dialing +E.164 dialing (from directories) Forced On-Net BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 20

21 Thoughts Core routing needs to be universal Adaptability to regional dialing Global addresses for DNs Enterprise specific numbers (ESN) vs. +E.164 Adaptability to regional (country specific) dialing habits Correct caller ID for all call flows default caller ID for calls from DN: DN as provisioned format which can be easily normalized to PSTN requirements BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 21

22 Reference +E.164 Dial Plan (10.x) CSSs Partitions Route Lists Route Groups Line CSS SJCInternational DN All IP Phone DNs (+E.164), urgent urgent DNs to avoid IDT URIs in same partition DN SJCtoE164 1XXX, Prefix All dialing normalisation is CoS un-specific! All normalisation patterns can be re-used 9.[2-9]XXXXXX, Pre-Dot, Prefix Routing is CoS specific. Site specificity only on site specific CoS (like local ) UStoE !, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL LRG based egress GW selection Local Route Group XYZ RG BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 22

23 Key UCM Features (10.0) Urgent Directory Numbers allows +E.164 DNs w/o inter-digit timeout due to overlap with variable length +E.164 patterns CSS Inheritance TPs uses activating CSS for secondary lookup saves redundant TPs, partitions, CSSes Multiple LRGs extends UCM 7.0s LRG capabilities to multiple classes of calls BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 23

24 Reference +E.164 Dial Plan (other dialing domains) CSSs Partitions Route Lists Route Groups ESCInternational DN All IP Phone DNs (+E.164), urgent DN ESCtoE164 9XXX, Prefix [1-9]!, Pre-Dot, Prefix [1-9]!#, Pre-Dot, # Prefix DEtoE !, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, # Prefix + 00.[1-9]!, Pre-Dot, Prefix [1-9]!#, Pre-Dot #, Prefix +49 Country specific dialing normalization Country (site) specific RPs XYZ RG PSTNInternational DEPSTNNational ESCPSTNLocal \ ! LOC RL Local Route Group BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 24

25 Reference +E.164 Dial Plan Summary +E.164 based routing +E.164 addresses (DNs) Dialing habits other than +E.164 implemented as overlay using translation patterns with CSS inheritance Egress gateway selection based on local route groups Multiple local route groups for differentiated egress GW selection For more information see: Cisco Collaboration System Solution Reference Network Designs (SRND) Cisco Live session BRKUCC-3000 recordings BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 25

26 Reference +E.164 Dial Plan Benefits +E.164 DNs provide AAR for free forced on-net for free Simple calling party handling globalize on ingress localize on egress Tool: calling party transformation patterns +E.164 core routing enables global deployment Dialing Normalization TPs to adapt to regional dialing habits BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 26

27 Topologies

28 Topologies with Multiple Global Call Controls Any-to-Any connectivity becomes complex with increasing # of call controls (n 2 ) hard/impossible to manage SIP trunk topology failover... BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 28

29 SME to Simplify Topology SME allows for simple hub and spoke topology Leaf clusters route all off-cluster (off-net) traffic to SME deterministic off-net decision covered later in this session Centralized inter-cluster routing decisions (centralized dial plan) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 29

30 Keeping Regional Traffic Regional All inter-cluster signaling is tied to SME even for call flows within region Although media goes direct this potentially causes media path setup delays BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 30

31 Keeping Regional Traffic Regional Multiple SMEs With regional SMEs signaling can be kept local.. but we add another layer of SIP trunks for SME interconnect SME of SME for really big topologies? BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 31

32 Keeping Regional Traffic Regional Single, distributed SME using Clustering over the WAN Distributed SME has nodes in every region signaling kept within region Still single point of administration BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 32

33 Distributed SME characteristics 500ms extended RTT between SME nodes (compared to 80ms) only SIP trunks Best Effort Early Offer or MTP-less Early Offer run on all nodes leaf clusters must accept inbound connections from all nodes leaf clusters must have all SME nodes as peers No endpoint registrations nor CTI devices No media resources (MTP, transcoder,...) on SME Reason: avoid intra-cluster signaling and media hair-pinning BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 33

34 SIP Trunks between Leaf and SME Leaf cluster has two upstream SIP trunks peering with regional SME nodes peering with remote SME nodes All SME nodes exist as peer in at least one SIP trunk Leaf accepts inbound sessions from all SME nodes Both trunks typically combined by RL/RG; priority order Alternative: selection of regional/remote trunk based on dialed destination do not over-engineer! BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 34

35 SIP Trunks between SME and Leaf SME has single SIP trunk to leaf cluster Peering with all leaf nodes SME accepts inbound connections from all leaf cluster nodes SIP trunk (RL) based redundancy not required as UCM distributes SIP trunk calls randomly between peers SIP OPTION ping to determine state of SIP peers BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 35

36 Recommendations Use SME to simplify SIP trunk topology Use single distributed SME whenever possible (scale, WAN) SIP trunks: SIP Best Effort Early Offer Run on all Nodes Multiple Destination Addresses OPTIONS ping PRACK See BRKUCC-2006 for more details Two Leaf to SME SIP trunks: regional vs. remote nodes BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 36

37 GDPR Applications

38 Problems to solve

39 On-Net/Off-Net decision w/ multiple call controls Maintained manually XXX XXX XXX XXX XXX XXX PSTN XXX XXX Each call control has to take independent on-net/off-net decisions Requires knowledge about remote on-net addresses Explicit configuration of remote address ranges or automatic learning? Complexity depending on number of prefixes! BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 39

40 Local On-Net/Off-Net w/ Centralized Dial Plan? SME to centralize dial plan, apps, PBX interconnect etc Default routing on leaf vs. local on/off-net decision Maintained manually Really? PSTN XXX XXX XXX XXX BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 40

41 GDPR to Action

42 GDPR learning and routing Global Learned E.164 Numbers nyc.route fra.route sfo.route nyc.route Global Learned E.164 Numbers sfo.route fra.route routestring: sfo.route Call controls establish ILS Exchange ILS Exchange routestring: nyc.route GDPR information flooded Each call control puts learned patterns/numbers in respective partitions and associated them with learned SIP route string Global Learned E.164 Numbers sfo.route nyc.route routestring: fra.route SIP route strings routed by SIP route patterns BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 42

43 Routing Call to remote Number using ILS Information Global Leaned +E.164numbers nyc.route fra.route 2) Match on learned numeric +E.164 pattern in digit analysis leads to SIP route string fra.route 1) Alice calls routestring: sfo.route ILS Exchange 3) call gets routed using SIP route pattern fra.route routestring: fra.route 4) is routeable using the trunk s CSS (is a local DN) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 43

44 Local On-Net/Off-Net w/ GDPR SIP Learned route E.164 string: pattern: east.route E.164 pattern: XXX (east.route) XXX (east.route) Learned E.164 pattern: XXX (east.route) XXX (east.route) SIP route string: west.route E.164 pattern: XXX XXX PSTN SIP route string: east.route E.164 pattern: XXX XXX XXX XXX XXX XXX BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 44

45 Local On-Net/Off-Net w/ GDPR Learned E.164 pattern: XXX (east.route) XXX (east.route) XXX (west.route) XXX (west.route) Learned E.164 pattern: XXX (east.route) XXX (east.route) SIP route string: west.route E.164 pattern: XXX XXX PSTN SIP route string: east.route E.164 pattern: XXX XXX XXX XXX XXX XXX BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 45

46 Local On-Net/Off-Net w/ GDPR Learned E.164 pattern: XXX SIP route string: (east.route) west.route XXX E.164 pattern: (east.route) XXX(west.route) XXX(west.route) Learned E.164 pattern: XXX (east.route) XXX (east.route) Learned E.164 pattern: XXX (west.route) XXX (west.route) SIP route string: west.route E.164 pattern: XXX XXX PSTN SIP route string: east.route E.164 pattern: XXX XXX XXX XXX XXX XXX BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 46

47 Local On-Net/Off-Net w/ GDPR Learned E.164 pattern: XXX (east.route) XXX (east.route) XXX (west.route) XXX (westroute) Learned E.164 pattern: XXX (east.route) XXX (east.route) Learned E.164 pattern: XXX (west.route) XXX (west.route) SIP route string: west.route SIP route string: east.route E.164 pattern: XXX XXX PSTN E.164 pattern: XXX XXX XXX XXX XXX XXX BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 47

48 Local On-Net/Off-Net w/ GDPR Digit analysis and route lookup is hop-by-hop Learned E.164 pattern: XXX (east.route) XXX (east.route) XXX (west.route) XXX (westroute) Learned E.164 pattern: XXX (east.route) XXX (east.route) Learned E.164 pattern: XXX (west.route) XXX (west.route) SIP route string: west.route SIP route string: east.route E.164 pattern: XXX XXX PSTN E.164 pattern: XXX XXX XXX XXX XXX XXX BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 48

49 GDPR Design Considerations

50 GDPR in an Enterprise Dial Plan Dialing learned numbers Up to three inter-cluster dialing habits to reach remote DN: Enterprise (8+7) based on enterprise alternate/pattern +E.164 based on +E.164 alternate/pattern URI Assuming that CoS does not depend on dialing habit all remote patterns can be put into single partition onnetremote CSSs SJCInternational DN Partitions DN All IP Phone DNs (+E.164) SJCtoE164 1XXX, Prefix [2-9]XXXXXX, Pre-Dot, Prefix ILS learned URIs are reachable from any device (, but the SIP route patterns potentially are not) Partition onnetremote added to all CSSes with CoS On-net onnetremote All patterns/numbers learned via GDPR + SIP route patterns for SIP route strings Also make sure to add SIP route pattern matching on SIP route strings to onnetremote partition BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 50

51 ILS Topology Single hub ILS hub (Distributed) SME as ILS hub, all other UCMs as spokes Straight forward Assumption: SIP trunking and ILS topology equivalent Why? BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 51

52 ILS Networking, URI Learning and Routing Components of end-to-end dialing/routing ILS networking GDPR propagation SIP trunk SIP route pattern 84969XXX route: fra.route route string: nyc.route ILS networking GDPR propagation 84953XXX (fra.route) 84969XXX (nyc.route) SIP Trunk route string: fra.route 84953XXX route: nyc.route SIP connectivity is foundation for call routing based on SIP route patterns ILS networking is foundation for exchange or GDPR reachability information GDPR propagation/exchange is enabled independent of ILS networking SIP trunk and ILS topology are independent! BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 52

53 ILS Topology Multiple hubs ILS hub Recommendation: all UCMs are ILS hubs Limit * : max 10 hubs Benefit: easier to troubleshoot, faster convergence ILS overhead of full-mesh is minimal (2 message per update interval) * Testing limit; not hard limit and not enforced BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 53

54 ILS Topology Growing the Network ILS hub ILS spoke hub/spoke relation Start with all UCMs being ILS hubs Keep adding ILS hubs until limit (10 hubs) is reached Continue to add UCMs as spokes and select close UCMs as their hub BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 54

55 ILS Topology Growing the Network ILS hub ILS spoke hub/spoke relation Start with all UCMs being ILS hubs Keep adding ILS hubs until limit (10 hubs) is reached Continue to add UCMs as spokes and select close UCMs as their hub Potentially identify few (starting with one) spoke supporting hubs BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 55

56 PSTN Access Centralized Benefits: centralized PSTN policy; think on/off-net decision w/o GDPR! resource consolidation BUT: site context lost source specific egress selection policy requires nasty workarounds BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 56

57 PSTN Access Distributed GDPR enables distributed deterministic on/off-net decision Enables source specific egress selection policy (LRG) TEHO still an option TEHO prefix advertisements as GDPR patterns specific partition for GDPR patterns vs. alternate numbers TEHO CoS possible BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 57

58 PSTN Access Distributed GDPR enables distributed deterministic on/off-net decision Enables source specific egress selection policy (LRG) TEHO still an option TEHO prefix advertisements as GDPR patterns specific partition for GDPR patterns vs. alternate numbers TEHO CoS possible BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 58

59 GDPR Route String Name Space us1.route *.route ea1.route ea2.route us2.route as1.route as2.route use pseudo TLD: example *.route avoid conflict with regular SIP routing name space hierarchy in line with SIP trunk topology one-tier hub/spoke flat name space: us1.route, us2.route, ea1.route,... explicit SIP route patterns on SME, wildcard SIP route pattern upstream on leaf BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 59

60 B2B Routing

61 B2B Call Flow Single Edge DNS Hierarchy Expressway-C Forward SIP Invite to companyb.com using IP address received via DNS VCS-E Expressway-E Calls Sends SIP 200 OK Internet VCS-C COMPANY A COMPANY B x.y@companyb.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 61

62 B2B w/ Expressway Single Edge B2B peer signaling media single B2B ingress & egress point media hair-pinning through Expressway-C/E suboptimal user experience BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 62

63 B2B w/ Expressway Multiple Edges, Egress Edge Selection B2B peer signaling media Egress edge selection on SME outbound B2B traffic sent to SME by leaf clusters site specific egress edge selection typically not required (.. and not possible due to loosing site context on SME) region specific egress edge selection based on upstream trunk LRG logic single SIP route pattern on SME for outbound B2B calls BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 63

64 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Closest to Calling Party B2B peer signaling media B2B edge identification based on DNS SRV lookup W/ multiple edges: use GEO DNS DNS SRV record resolution takes location (IP address) of orginator into account public DNS needs to provide GEO DNS service redundancy (failover to other edges) still an option BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 64

65 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Alternatives? B2B peer signaling media inter-region B2B sessions on enterprise WAN BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 65

66 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Alternatives? B2B peer signaling media inter-region B2B sessions on enterprise WAN Ingress edge selection based on called destination? Internal location of called party unknown externally called party specific ingress edge selection requires internal routing logic BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 66

67 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Closest to called party B2B peer signaling media Expressway searching logic allows to try alternate paths Solution concept: direct all ingress B2B traffic to master Expressway (DNS based) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 67

68 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Closest to called party B2B peer signaling media Expressway searching logic allows to try alternate paths Solution concept: direct all ingress B2B traffic to master Expressway (DNS based) master tries all options: inbound to SME and via other Expressways BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 68

69 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Closest to called party B2B peer signaling media Expressway searching logic allows to try alternate paths Solution concept: direct all ingress B2B traffic to master Expressway (DNS based) master tries all options: inbound to SME and via other Expressways SME routing logic cancels all but the desired path How? BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 69

70 B2B w/ Expressway Multiple Edges, Ingress Edge Selection Closest to called party Differentiated CoS for ingress B2B trunks Classification based on SIP route string learned for dialed destination Inter-region calls from edge easily prohibited Caveat: no ingress inter-region failover possible! CSS_B2B_US GDPR_US CSS_B2B_AS GDPR_US CSS_B2B_EA GDPR_US B2B peer GDPR_US signaling us1.route media us2.route GDPR_AS as1.route as2.route GDPR_EA ea1.route ea2.route BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 70

71 Hybrid Calling with Cisco Spark

72 Cisco Spark Hybrid Services Hybrid Services Message Meeting Call Connect existing Cisco calling capabilities to Cisco Spark capabilities in the cloud Communications Manager Business Edition Series HCS Delivered Services BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 72

73 Connected Calling Cisco On-Premises & Partner Hosted HCS Cisco Collaboration Cloud Call Service Connect - connects Cisco Spark & the enterprise phone system so they behave as one Your Spark app becomes an enterprise softphone Provides voice and video interoperability between Jabber and Spark User benefits: Choice: use Jabber or Spark to call anyone without worrying about which you or the other person is using One number: be reached on Spark, Jabber, or a deskphone. Choose to take the call on whichever suits you best at that moment Reach everyone: call company extensions, PSTN numbers, Spark only users, and even video bridge numbers Company dial plan: dial from the Spark app as you would from your deskphone - call PSTN numbers via enterprise phone system Make the most of video assets: en-route to the office start a call on a mobile device and hand off to a room system when you arrive BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 73

74 Call Connect Problem Statement Simultaneous Ring on Spark and Enterprise for: Spark-to-Spark calls Calls to the enterprise extension (B2B, on-net, PSTN) B2B calls On UCM simultaneaus ring can be achieved using Remote Destinations But: same URIs in Spark and Enterprise What can be used to route? Solution: use RD based call forking on UCM with new identity: Cloud URI BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 74

75 Cisco Spark SIP Address Single (unique!) Cisco Spark SIP address prefix defined per organisation Prefix is verified to be unique example.com Used to create Cisco Spark SIP Adress per User Cisco Spark SIP address provisioned as remote destination on Spark RD associated with user in UCM example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 75

76 Call Service Connect/Aware Architecture

77 Call Service Connect/Aware Architecture *.ciscospark.com example.com Expressway-E Expressway-C Communications Manager Expressway-C (Connectors) SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 77

78 Call Service Connect/Aware Architecture *.ciscospark.com example.com Expressway-E Expressway-C Spark clients connect to Cisco Collaboration Cloud over-the-top (OTT) Expressway-C (Connectors) Communications Manager SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 78

79 Call Service Connect/Aware Architecture *.ciscospark.com example.com Expressway-E Expressway-C Standard B2B/MRA setup. Not neccessarily needs to be dedicated to hybrid services Expressway-C (Connectors) Communications Manager SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 79

80 Call Service Connect/Aware Architecture *.ciscospark.com example.com Expressway-E Expressway-C (secure) SIP trunks for B2B, MRA and CSC calls. Expressway-C (Connectors) Communications Manager SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 80

81 Call Service Connect/Aware Architecture *.ciscospark.com example.com Expressway-E Expressway-C Communications Manager Expressway-C as connector platform: Management, Calendar, Call Expressway-C (Connectors) Call Connector SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 81

82 Call Service Connect/Aware Architecture *.ciscospark.com example.com Expressway-E Expressway-C HTTPS to connect to RESTful services (management, call state,...) Independent of Expressway-C/E for B2B/MRA Expressway-C (Connectors) Communications Manager SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 82

83 Call Service Connect/Aware Architecture Expressway-E Expressway-C AXL/SOAP: validation and provisioning: Users, devices, remote destinations,... Expressway-C (Connectors) Communications Manager CTIQBE: device monitoring (and control) SIP AXL/SOAP CTIQBE REST/HTTPS BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 83

84 Call Service Connect Call Flow

85 Refresher: Remote Destinations in UCM Someone calls Someone calls 1 7 Session routing numeric & URI 1 Incoming call from trunk Destination matches a URI associated with a DN Device identified the DN is associated with Session initiated with device DN is also associated with Spark RD (shared line) Session initiated to remote destination Outbound session to remote destination 6 DN Spark RD Phone/Client Remote destination bob@example.call.ciscospark.com 3 UCM Someone calls 4 BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 85

86 Refresher: Anchoring in UCM calls 1 Session routing numeric & URI 1 Incoming call from trunk Caller ID matches a remote destination Call treated as if it originated from Spark RD Destination matches a URI associated with a DN Device identified the DN is associated with Session initiated with device DN DN Spark RD Remote destination alice@example.call.ciscospark.com Phone/Client calls 6 UCM BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 86

87 Refresher: Anchoring w/ RD on Target calls calls Same as before DN is also associated with Spark RD (shared line) Session initiated to remote destination Outbound session to remote destination 1 3 DN Session routing numeric & URI DN Spark RD Remote destination alice@example.call.ciscospark.com 4 Phone/Client Spark RD Remote destination bob@example.call.ciscospark.com calls 6 UCM BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 87

88 Call Flow (Spark to Spark, Intra-Enterprise) Call initiated by entering a URI in the calls tab or by selecting entry in recents calls list example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. alice@example.org example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 88

89 Call Flow (Spark to Spark, Intra-Enterprise) Spark user identified via URI match If call was initiated by pressing call button in space or for Spark user in recents list then Spark user is identified directly example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 89

90 Call Flow (Spark to Spark, Intra-Enterprise) Call presented to Spark User example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 90

91 Call Flow (Spark to Spark, Intra-Enterprise) Call is forked to the caller s enterprise (caller is enabled for CSC) example.com alice@example.org Destination is bob s enterprise URI (only exists if destination DNS is enabled for CSC) _sip._tcp.example.com. _sip._tcp.example.org. Caller ID is caller s Spark SIP address: alice@example.call.ciscospark.com Expressway-E identified by SIP destination configuration in Spark organisation example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 91

92 Call Flow (Spark to Spark, Intra-Enterprise) Expressway-E/C routes call to UCM cluster 1 example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. alice@example.org 1 Home cluster routing based on SIP route header containing CFQDN of UCM cluster). Requires: example.org alice@example.org direct trunk from Expressway-C to clusters or: UCM 12.0 on SME BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 92

93 Call Flow (Spark to Spark, Intra-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. Call anchored example.com on Spark RD of caller () UCM routes to endpoint example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 93

94 Call Flow (Spark to Spark, Intra-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. UCM routes example.com to endpoint... and Spark RD of Bob and forks call to Bob s Spark SIP address (remote destination) alice@example.org example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 94

95 Call Flow (Spark to Spark, Intra-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. Expressway-C/E routes to cloud based on cloud domain: *.ciscospark.com example.com example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 95

96 Call Flow (Spark to Spark, Intra-Enterprise) X Loop is detected in cloud example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. alice@example.org example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 96

97 Call Flow (Spark to Spark, Inter-Enterprise) Call initiated as before but between Orgs (URI, 1:1 room,...) example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 97

98 Call Flow (Spark to Spark, Inter-Enterprise) Call presented to Spark User and forked call to calling user s enterprise (calling and called user enabled for CSC) DNS example.com _sip._tcp.example.com. _sip._tcp.example.org. alice@example.org example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 98

99 Call Flow (Spark to Spark, Inter-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. Call anchored example.com on Spark RD of caller () UCM routes to called URI (SIP route pattern) example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 99

100 Call Flow (Spark to Spark, Inter-Enterprise) DNS Expressway example.com routes to target based on SRV _sip._tcp.example.com. _sip._tcp.example.org. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 100

101 Call Flow (Spark to Spark, Inter-Enterprise) example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org Expressway-E/C routes call to UCM cluster BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 101

102 Call Flow (Spark to Spark, Inter-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. example.com UCM routes call to endpoint example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 102

103 Call Flow (Spark to Spark, Inter-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. example.com UCM routes call to endpoint... and Spark RD with Spark SIP address as remote destination example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 103

104 Call Flow (Spark to Spark, Inter-Enterprise) X Loop is detected by cloud example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. alice@example.org example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 104

105 Call Flow (B2B) DNS _sip._tcp.example.com. _sip._tcp.example.org. UCM routes example.com to called URI (SIP route pattern) example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 105

106 Call Flow (B2B) DNS _sip._tcp.example.com. _sip._tcp.example.org. Expressway example.com routes to target based on SRV example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 106

107 Call Flow (B2B) example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org Expressway-E/C routes call to UCM cluster BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 107

108 Call Flow (B2B) DNS _sip._tcp.example.com. _sip._tcp.example.org. example.com UCM routes call to endpoint... and Spark RD with cloud services URI as remote destination example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 108

109 Call Flow (B2B) Call is sent to Spark client No forking as the call is received from the enterprise example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 109

110 Call Flow (Intra-Enterprise) DNS _sip._tcp.example.com. _sip._tcp.example.org. example.com Destination can be dialed as URI or numeric. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 110

111 Call Flow (Intra-Enterprise) UCM routes to called user s client... and DNS Spark RD with Spark SIP address as remote destination _sip._tcp.example.com. _sip._tcp.example.org. Spark SIP address routed based on SIP route pattern and Expressway routing setup example.com example.org alice@example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 111

112 Call Flow (Intra-Enterprise) Call is sent to Spark client No forking as the call is received from the enterprise example.com DNS _sip._tcp.example.com. _sip._tcp.example.org. example.org BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 112

113 Spark Call Forking For calls initiated from Spark a call is always forked to the calling user s enterprise if the calling user is enabled for CSC Reason: this makes sure that Spark initiated calls are subject to the same policies and can use the same dialing habits as calls initiated within the enterprise (Spark RD CSS used) anchoring makes sure that the caller ID is set to the enterprise URI of the calling user For calls initiated from Spark a call is forked to the called user s enterprise if only the called user is enabled for CSC in this case the caller ID is the caller s Spark SIP address to allow call-back BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 113

114 CSC Forking for Spark 1:1 Calls Calling user Enabled for CSC Called user enabled for CSC Call forked to Yes Yes Calling user s enterprise Yes No n.a. n.a. Called Address Enterprise URI No Yes Called user s enterprise No No n.a. n.a. Enterprise URI BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 114

115 Large Scale Hybrid Calling Considerations

116 Scaling Hybrid Calling Deployments Scaling from a single region deployment to.. BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 116

117 Scaling Hybrid Calling Deployments.. multi-region Americas Europe Asia BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 117

118 Large Scale Hybrid Calling Deployment Considerations Downstream (from the cloud) routing Upstream (to the cloud) routing Media path BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 118

119 Large Scale Hybrid Calling Considerations: Downstream Routing

120 Status Quo Single SIP destination defined in Cisco Spark Control Hub can be _sips._tcp SRV record SRV record allows for load distribution over multiple peerings combined w/ Geo-DNS originator specific destination selection is possible Originator in the Cisco Spark Case is the SIP interop service BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 120

121 Multiple Expressway Pairs for CSC Both signaling and media experience cross-region delay Anchored on Expressway-C Source-specific Expressway selection ( close to calling ) only viable Expressway selection policy destination-specific requires UCM interaction (only UCM knows location of called party) would allow for distribution of load over multiple Expressway pairs BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 121

122 Geo-Diversity w/ Directory Expressway Deploy new directory Expressway route on CFQDN SIP route headers leave route header intact Call Signaling Optimization: On exp-amer.example.com exp-emea.example.com exp-asia.example.com Americas Europe Asia BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 122

123 Geo-Diversity w/ Directory Expressway Deploy new directory Expressway route on CFQDN SIP route headers leave route header intact Call Signaling Optimization: On Cisco Spark sends INVITE to configured SIP destination Route header refers to calling user s home cluster exp-amer.example.com exp-emea.example.com exp-asia.example.com Americas Europe Asia BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 123

124 Geo-Diversity w/ Directory Expressway Deploy new directory Expressway route on CFQDN SIP route headers leave route header intact Call Signaling Optimization: On exp-amer.example.com exp-emea.example.com exp-asia.example.com Americas Directory Expressway sends call to Expressway-E Europe local to the Asia calling user s home cluster based on received SIP route header Call Signaling Optimization: no Record-Route header inserted BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 124

125 Geo-Diversity w/ Directory Expressway Deploy new directory Expressway route on CFQDN SIP route headers leave route header intact Call Signaling Optimization: On Direct signaling between Cisco Spark and in-region Expressway-E established based on Route and Record-Route headers exchanged exp-amer.example.com exp-emea.example.com exp-asia.example.com Americas Europe Asia BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 125

126 Geo-Diversity w/ Directory Expressway Easy to implement Ingress into enterprise close to calling Special case: no dedicated Expressway redirection co-located on peering Expressway-Es suitable for few peerings BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 126

127 Large Scale Hybrid Calling Considerations: Upstream Routing

128 Upstream Route Selection Expressway-E Expressway-E uses _sips._tcp SRV record lookup for upstream routing callservice.ciscospark.com Resolves to scalable cloud ingress (load balancers) ;; QUESTION SECTION: ;_sips._tcp.callservice.ciscospark.com. IN SRV ;; ANSWER SECTION: _sips._tcp.callservice.ciscospark.com. 300 IN SRV l2sip-cfa-02.wbx2.com. _sips._tcp.callservice.ciscospark.com. 300 IN SRV l2sip-cfa-01.wbx2.com. BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 128

129 Upstream Route Selection Expressway-E All Expressway-Es use the SAME upstream destination(s) Media path is a different story (see later) Americas Europe Asia BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 129

130 Upstream Route Selection (UCM to Expressway-C) Multiple Expressways per UCM-Cluster Single SIP route pattern LRG based egress route selection LRG egress selection policy driven by device pool based settings (device pool of calling device) calls anchored on calling user s SparkRD: LRG of downstream trunk from Expressway calls originating from UCM registered devices: LRG of originating device Expressways on SME LRG determined by upstream leaf trunk no site specific egress Expressway selection probably not a limiting factor Else: push Expressways down to leaf clusters BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 130

131 Large Scale Hybrid Calling Considerations: Media Path

132 Regional Collaboration Cloud Peering CCP micro-service instances are distributed globally Control SIP Interconnect Conferencing exp-amer.example.com exp-emea.example.com Americas Europe Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 132

133 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com Alice calls Bob from UCM registered endpoint BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 133

134 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com ICT to Bob s cluster BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 134

135 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com Call extended to Bob s devices BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 135

136 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Call hits Bob s Spark RD: call forked to Bob s Spark SIP address (@example.call.ciscospark.com) SIP route pattern for example.call.ciscospark.com to select upstream route exp-emea.example.com Americas Europe Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 136

137 Enterprise initiated Alice Bob exp-amer.example.com Egress Expressway-C selection close to calling (Alice)? close to called (Bob)? Important: egress Expressway-C selection determines media path (media anchored on Expressway-C) Close to calling requires any-to-any peering of all UCM clusters to all Expressway-Cs (messy to provision) With SME between UCMs and Expressway-Cs LRG based egress Expressway-C selection based on upstream trunk s device pool on SME (recommended solution, see earlier) W/o SME: any-to-any peering of all UCM clusters to all Expressway-Cs required (messy to provision) LRG based egress selection based on device pool of calling device (or trunk) exp-emea.example.com Americas Europe Asia exp-asia.example.com Control SIP Interconnect Conferencing? BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 137

138 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Egress Expressway-C close to calling is selected (via SME or directly) exp-emea.example.com Americas Europe Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 138

139 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia Sent to Expressway-E exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 139

140 Enterprise initiated Alice Bob Upstream SIP Interconnect service selection Currently SRV _sips._tcp.callservice.ciscospark.com points to US Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 140

141 Enterprise initiated Alice Bob SIP interconnect to Control service signaling Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 141

142 Enterprise initiated Alice Bob Conferencing service selection Hint: geo IP lookup on last upstream peer Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 142

143 Enterprise initiated Alice Bob Control Signaling to Control service responsible for called user SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 143

144 Enterprise initiated Alice Bob Signaling to Spark application of called user Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 144

145 Enterprise initiated Alice Bob Control Simultaneous ring on Cisco Spark and on-premise SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 145

146 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Call answered on Spark: Media path established exp-emea.example.com Americas Europe Asia exp-asia.example.com BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 146

147 Enterprise initiated Alice Bob Control SIP Interconnect Conferencing exp-amer.example.com Americas Europe exp-emea.example.com Asia exp-asia.example.com Call answered on-prem: Media path established BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 147

148 Summary: Media Path Inter-region round-trip delay only affects signaling Media path optimised: in-region conferencing service selection (close to Expressway-E) BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 148

149 Closing

150 Summary Global Deployments require proper planning Aspects Multi-cluster planning (w/ and w/o SME) PSTN consolidation Country specific requirements (PSTN, legal, etc.) Global dial plan design Global Dial Plan Replication B2B SIP URI connectivity Cisco Spark Hybrid Calling enablement All the tools are there! BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 150

151 References/Additional Material National Numbering Plan Collection: Get Started with Cisco Spark Hybrid Services: Deploying Cisco Spark Hybrid Services (CVD Guide): Addtl. material: EMEA Country specific numbering plan information GDPR masterdeck Session PDF BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 151

152 Design and Deployment Best Practices for Cisco Collaboration What you would tell your best friend, if they asked you how to design their Cisco collaboration deployment? Preferred Architectures (PA) Prescriptive design and deployment best practices within a well-defined architecture containing common Cisco collaboration portfolio components Collaboration Solution Reference Network Design (SRND) Design guidance across the Cisco collaboration portfolio with a focus on enterprise, on-premises deployments Three preferred architectures (PAs) covering a wide range of customer deployment types and sizes:» On-Premises (Enterprise, Midmarket)» Cloud (Midmarket)» Hybrid (Enterprise) Versions aligning with major Collaboration System Releases (CSRs): 9.x, 10.x, 11.x, and 12.x* * Coming soon. Target Q1 CY Cisco and/or its affiliates. All rights reserved. Cisco Public

153 Cisco Spark How Questions? Use Cisco Spark to communicate with the speaker after the session 1. Find this session in the Cisco Live Mobile App 2. Click Join the Discussion 3. Install Spark or go directly to the space 4. Enter messages/questions in the space cs.co/ciscolivebot#brkucc Cisco and/or its affiliates. All rights reserved. Cisco Public

154 Please complete your Online Session Evaluations after each session Complete 4 Session Evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Live T-shirt All surveys can be completed via the Cisco Live Mobile App or the Communication Stations Complete Your Online Session Evaluation Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at Cisco and/or its affiliates. All rights reserved. Cisco Public

155 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Tech Circle Meet the Engineer 1:1 meetings Related sessions BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 155

156 Thank you

157

158 Appendix: Hybrid Calling Configuration Details

159 General Requirements UCM must run 10.5(2) SU3 or later If cloud services URIs are greater than 48 characters then you want to upgrade to a release (ES) which also has the fix for CSCux74780 Expressway-C connector must run X8.7.1 or later Codecs supported by Collaboration Cloud: Audio: G.711u, AAC-LD, Opus VideoH.264 URI routing configured on UCM All domains used in enterprise URIs need to verified and registered on Cisco Collaboration Cloud org Expressway-E certificate: signed by public CA SAN for all Expressway-E hosts SANs need to belong to the domains registered on the Cisco Collaboration Cloud organization BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 159

160 Connector Configuration UCM clusters Each UCM cluster needs to be provisioned on call connector User needs to be an application user with: Standard AXL API Access Standard CTI Allow Control of All Devices Standard CTI Enabled Standard CTI Allow Control of Phones supporting Connected Xfer and conf Standard CTI Allow Control of Phones supporting Rollover Mode On each UCM cluster the CFQDN has to be set to a unique value (see preloaded header discussion later) If multiple CFQDNs are configured then the 1 st is considered; no wildcards allowed BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 160

161 Call Service Connect End-to-End Enterprise Settings A single SIP URI Domain name is defined per Organization DNS zone SIP URI Domain has to be unique (validated) This is used to build the Spark SIP address for each user Traversal zone Domain can only be defined ONCE Suffix call.ciscospark.com for all Spark SIP addresses Example SIP URI Domain Name: example Host portion of Spark SIP addresses: example.call.ciscospark.com UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 161

162 Call Service Connect End-to-End Enable Users for Call Service Users must be entitled for Call Service Aware Cloud Collaboration Management Portal is used to change user entitlements Call connector for all enabled users populates enterprise URI and Spark SIP address DNS zone Traversal zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 162

163 Call Service Connect End-to-End Spark to Expressway SIP Destination per Org is configured in Cloud Collaboration Management Configured destination can be IP, host, or DNS SRV Expressway-E certificate must match configured host/srv Mutual TLS (MTLS) authentication is required for CSC MTLS can not be used on port 5061 if Expressway-E is used for MRA Use different port instead (5062) DNS zone Traversal zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 163

164 Call Service Connect End-to-End MTLS on Expressway-E If Expressway-E is dedicated to CSC then default port 5061 can be configured for MTLS Dedicated DNS zone If also used for MRA then enable MTLS on dedicated port (5062) Mutual TLS mode = On : enable additional MTLS port Shared Traversal zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 164

165 Call Service Connect End-to-End Neighbor Zone to Spark Challenges: Peer definition based on IP addresses not suitable for cloud solution DNS zone (prior to X8.6.1) allows flexible outbound routing, but we also need to be able to validate inbound connections Solution: Starting with X8.6.1 allows to configure mutual TLS authentication Classification of inbound connections based on TLS peer certificate DNS Zone selected based on identity in TLS certificate Enables: Dynamic outbound routing to cloud entities (DNS lookup) Inbound authentication of dynamic cloud entities (based on certificate) DNS zone Traversal zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 165

166 Call Service Connect End-to-End Neighbor Zone (DNS) to Spark Enable MTLS classification TLS verify mode: On TLS verify subject name: populated TLS verify inbound mapping: On Both of the above flags need to be set to on to enable inbound classification against the zone DNS zone Traversal zone TLS verify subject name needs to match the peer certificate presented by Spark during TLS setup fixed value: callservice.ciscospark.com Preloaded SIP routes support required for source based routing (discussed later) UCM neighbor zone Calls to Spark are bound to a fixed Domain DNS SRV requests for a fixed domain 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 166

167 Call Service Connect End-to-End Home Cluster Routing Multiple UCM clusters inside an enterprise Bob: ucm-eu.example.com Alice: ucm-us.example.com DNS zone Challenge: send incoming forked CSC session to correct UCM cluster (calling user s cluster) Solution: call connector populates home clusters CFQDN in Spark per user CSC calls have a SIP route header carrying this attribute ucm-eu.example.com? Expressway-C routes to home cluster based on this Preloaded SIP Route By default Expressway rejects calls with preloaded SIP Routes Preloaded SIP Routes need to be enabled on DNS zone and traversal zones for CSC ucm-us.example.com UCM neighbor zone Source based routing based on SIP route header not possible on SME BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 167

168 Call Service Connect End-to-End Traversal Server on Expressway-E Taversal zone for CSC can be dedicated or shared Dedicated allows for differentiated call treatment If addtl. port on firewall is a problem then existing traversal zone can be reused; impact on search rule configuration Preloaded SIP routes support required for home cluster routing DNS zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 168

169 Call Service Connect End-to-End Traversal Client on Expressway-C Preloaded SIP routes support required for Home Cluster Routing DNS zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 169

170 Call Service Connect End-to-End Search Rules on Expressway-E To UCM: Route everything from the MTLS authenticated DNS zone to the traversal zone No further matching required DNS zone From UCM: With dedicated CSC traversal zone route everything from traversal zone to DNS zone UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 170

171 Call Service Connect End-to-End Search Rules on Expressway-E To UCM: Route everything from the MTLS authenticated DNS zone to the traversal zone No further matching required DNS zone From UCM: With dedicated CSC traversal zone route everything from traversal zone to DNS zone Shared traversal zone requires more specific UCM neighbor zone 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 171

172 Call Service Connect End-to-End Differentiated CoS per User For calls anchored on a Spark RD the Spark RD device CSS and line CSS are used to route the call This makes sure that for all CSC calls originating from CSC enabled users (caller ID is cloud services URI) per user CoS is enforced DNS zone Traversal zone alice bob bigboss X UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 172

173 Call Service Connect End-to-End UCM neighbor zones/ucm trunks Multiple inbound trunks on UCM require multiple UCM neighbor zones on Expressway-C Dedicated zones for CSC per UCM Don t re-use zones defined for B2B (see CoS discussion) DNS zone Traversal zone Use listening port numbers on UCM to multiplex trunks Listening port on UCM defined by SIP Security profile UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 173

174 Call Service Connect End-to-End Expressway-C Search Rules To UCM One search rule per UCM cluster Match on CFQDN in SIP route header (CFQDN pushed into cloud by call connector) DNS zone Traversal zone From UCM With dedicated Spark traversal zone create Spark specific search rule Else calls to spark are subset of B2B rule on Expressway-C UCM neighbor zone BRKUCC Cisco and/or its affiliates. All rights reserved. Cisco Public 174