A New Approach to Call Routing and Dial Plans Based on the Service Advertisement Framework (SAF) BRKUCC-2003

Transcription

1 A New Approach to Call Routing and Dial Plans Based on the Service Advertisement Framework (SAF) BRKUCC-2003

2 Introduction Prerequisites This Session Assumes Basic Knowledge of: Routing Protocols Dial Plans Cisco Unified Communications Manager Cisco Unified Communications Call Processing Deployment Models 2

3 Introduction Session Agenda and Scope Introduction Call Control Discovery (CCD) Scope and Objectives Features and Functionality Configuration Examples Service Advertisement Framework (SAF) The SAF Network The SAF Client-Network Interface Conclusions 3

4 Introduction Problem Statement and Goals Advanced network services and applications are often deployed as overlays Can the network leverage dynamic properties of routing to help these services communicate? Goals: Provide a network foundation for service awareness Enable applications 4

5 Introduction The Service Advertisement Framework (SAF) Vision A network-based, scalable, bandwidth-efficient, real-time approach to service advertisement and discovery Is based on EIGRP technology, but is independent of IP routing protocol (works with OSPF, BGP,...) Supports dark nets (non-saf nodes) for phased roll-outs and heterogeneous deployments Will allow administrators to control scope of each service through domains, filtering, VRFs,... 5

6 Introduction Problem Statements Specific to Unified Communications Call Control Services Presence Services Policy Services Unified Communications requires a large number of devices, services and applications Gateway Services VM / UM Services Collaboration Services Need to reduce complexity Need to simplify provisioning to accelerate absorption Need to simplify operations and reduce TCO Location Services Conferencing Services The Network Media Services Routing between call agents relies mainly on static configuration Complexity, operational cost, availability 6

7 Introduction Limitations of Current Call Routing Approaches Configuration complexity, speed of deployment High operational cost, TCO Availability, business continuity IP Network IP Network Proxy / GK / Session Manager 7

8 Introduction Call Control Discovery (CCD): a SAF Service CCD SAF-enabled IP Network Call agents discover each other through the SAF network by: Advertising their reachability information along with the DN ranges they own Requesting to learn about other call agents in the network Call agents dynamically route calls to remote destinations based on received advertisements 8

9 Introduction SAF+CCD Compared to TRIP, ENUM, DUNDi,... Peering between call agents vs. peering with the network Detection and reaction to connectivity changes Creating overlay topology vs. using existing network topology Configuration complexity Centralized approach vs. distributed approach Availability, TCO Point solution vs. generic framework Reuse same infrastructure to advertise other services 9

10 Introduction SAF Terms and Definitions SAF Header CCD SAF Service Data SAF Client: any application wishing to advertise a service to the network or request a service from the network or both SAF Forwarder: router feature provides relationship between client and framework, stores service information and propagates it to other forwarders Service: any information that a SAF client wishes to advertise and consume (e.g., dial plans for CCD) SAF Advertisement: carries service information, consists of SAF header and service data Non-SAF Node: any router that does not run the SAF protocols 10

11 Introduction SAF Architecture Cisco Unified CM CCD CUBE Cisco IOS GW CCD CCD CCD CUCME SRST Cisco Unified CM Session Management Edition CCD SAF Client SAF Client Protocol SAF Forwarder SAF Client Protocol SAF-unaware Router 11

12 Call Control Discovery (CCD) Scope and Objectives Features and Functionality Configuration Examples (Unified CM and IOS) Integration with Static Routing 12

13 Call Control Discovery (CCD) Scope and Objectives Cisco Unified CM CCD CUBE Cisco IOS GW CCD CCD CCD CUCME SRST Cisco Unified CM CCD Enable call agents to exchange dial plan, signaling protocol and reachability information through SAF Extend call control logic to incorporate dynamic routing based on information learned through SAF Focus on enterprise-owned Directory Numbers (DNs), rather than PSTN egress points Include information on DID translation rules in advertisements to simplify PSTN failover 13

14 Call Control Discovery (CCD) Schema Schema based on XML 1.0 with UTF-8 encoding All CCD information is in the hosted-dn object trunk-route provides signaling protocol information dn-pattern contains advertised DN patterns along with strip/prefix rules to obtain DID SAF Header: Service ID 101:2 SAF Service Data: CCD Object <?xml version="1.0" encoding="utf-8"?> <service-description xmlns=" xmlns:xsi=" xsi:schemalocation=" saf-ucv0.95.xsd" schemaversion="1.0" id="1.0"> <hosted-dn> <description> <product>ucm</product> <version> </version> <enterprisename>clusterb</enterprisename> <location>sw068b-cmb2</location> </description> <trunk-route> <protocol><sip/></protocol> <tunneled-signaling><qsig-iso/></tunneled-signaling> </trunk-route> <dn-pattern version="1"> <p d= 1: ">2XXX</p> <p d= 4: "> [136]</p> <p d="0:"> xxx</p> </dn-pattern> </hosted-dn> </service-description> 14

15 Call Control Discovery (CCD) Advertising DN Ranges Service Advertisement IP address: Protocol: SIP DN Patterns: 8408XXXX [4: ], 8415XXXX [4: ], 8949XXXX [4: ] New York CME Routing Table DN Pattern to DID rule IP address Protocol 8408XXXX 4: SIP 8415XXXX 4: SIP 8949XXXX 4: SIP 8408XXXX PSTN 8212XXXX San Jose New York 8415XXXX San Francisco 8949XXXX Irvine SAF-Enabled IP Network 15

16 Call Control Discovery (CCD) Learning DN Ranges San Jose CUCM Routing Table DN Pattern to DID rule IP address Protocol 8212XXXX 4: SIP Service Advertisement IP address: Protocol: SIP DN Patterns: 8212XXXX [4: ] 8408XXXX PSTN 8212XXXX San Jose New York 8415XXXX San Francisco 8949XXXX Irvine SAF-Enabled IP Network 16

17 Call Control Discovery (CCD) Dynamic Routing San Jose CUCM Routing Table DN Pattern to DID rule IP address Protocol 8212XXXX 4: / SIP 8442XXXX 4: H.323 New York CME Routing Table DN Pattern to DID rule IP address Protocol 8408XXXX 4: / SIP 8415XXXX 4: / SIP 8949XXXX 4: / SIP 8442XXXX 4: H XXXX PSTN 8212XXXX San Jose New York 8415XXXX 8949XXXX SAF-Enabled IP Network 8442XXXX San Francisco Irvine Call London 17

18 Call Control Discovery (CCD) Automatic PSTN Failover San Jose CUCM Routing Table DN Pattern to DID rule IP address Protocol 8212XXXX 4: SIP 8442XXXX 4: H.323 New York CME Routing Table DN Pattern to DID rule IP address Protocol 8408XXXX 4: SIP 8415XXXX 4: SIP 8949XXXX 4: SIP 8442XXXX 4: H XXXX Translate to PSTN 8212XXXX San Jose New York 8415XXXX 8949XXXX SAF-Enabled IP Network 8442XXXX San Francisco Irvine Call London 18

19 Call Control Discovery (CCD) Automatic Rerouting for SRST SRST subscribes to CCD service but does not publish any patterns During WAN failures, SRST uses learned patterns to transparently re-route calls over the PSTN New York SRST Routing Table DN Pattern to DID rule IP address Protocol 8408XXXX 4: SIP 8415XXXX 4: SIP 8949XXXX 4: SIP 8408XXXX PSTN 8212XXXX San Jose New York 8415XXXX 8949XXXX SAF-Enabled IP Network Call San Francisco Irvine 19

20 Call Control Discovery (CCD) 3 rd Party IP PBX Integration using CUBE San Jose CUCM Routing Table DN Pattern to DID rule IP address Protocol 8442XXXX 4: H XXXX 4: SIP 8408XXXX San Jose DN Pattern to DID rule IP address Protocol 8408XXXX 4: SIP 8415XXXX 4: SIP 8949XXXX 4: SIP 8442XXXX 4: H.323 PSTN IP address: Protocol: SIP DN Patterns: 8312XXXX [4: ] CUBE Chicago Chicago CUBE Routing Table Static dial peer for destination 8312XXXX 3 rd Party IP PBX XXXX 8415XXXX 8949XXXX SAF-Enabled IP Network Call XXXX San Francisco Irvine London 20

21 Call Control Discovery (CCD) 3 rd Party TDM PBX Integration San Jose CUCM Routing Table DN Pattern to DID rule IP address Protocol 8442XXXX 4: H XXXX 4: SIP 8408XXXX San Jose Boston Gateway Routing Table DN Pattern to DID rule IP address Protocol 8408XXXX 4: SIP 8415XXXX 4: SIP 8949XXXX 4: SIP 8442XXXX 4: H.323 PSTN Cisco IOS Gateway Boston TDM Static dial peer for destination 8617XXXX 3 rd Party TDM PBX XXX 8415XXXX 8949XXXX SAF-Enabled IP Network Call XXXX San Francisco Irvine London 21

22 Call Control Discovery (CCD) Cisco Unified CM Support Details Starting with release 8.0(1), ability to advertise and/or subscribe to the CCD service Learned DN patterns dynamically inserted in a specified partition Transparent PSTN failover when destination is unreachable Scalability: Up to 2,000 advertised DN patterns per cluster Up to 20,000 learned DN patterns per cluster DN patterns must be unique (if duplicates, warning can be issued) Ability to purge and block unwanted patterns (e.g., from rogue or mis-configured call agents) Extensive troubleshooting support through RTMT and traces 22

23 Call Control Discovery (CCD) Unified CM Configuration SIP Trunk 23

24 Call Control Discovery (CCD) Unified CM Configuration H.323 Trunk 24

25 Call Control Discovery (CCD) Unified CM Configuration Hosted DNs Applies the same todid rules to all DN Patterns in this group Used to advertise full E.164 ranges instead of internal numbers + todid rules 25

26 Call Control Discovery (CCD) Unified CM Configuration Hosted DNs (Cont.) Can bulk-import or export hosted DNs to/from a CSV file Hosted DN patterns to be advertised are configured by the administrator Allows flexibility in designing on-net dial plan and choosing which DN ranges to advertise to other call agents 26

27 Call Control Discovery (CCD) Unified CM Configuration Advertising Service Each hosted DN group can be associated with only one CCD advertising service SAF trunks can be re-used by different CCD advertising services and CCD requesting services The SAF trunks Unified CM groups determine on which nodes this service runs and which IP addresses are advertised through SAF 27

28 Call Control Discovery (CCD) Unified CM Configuration SAF Partition All CCD-learned patterns are inserted into the partition configured here This partition will not appear when you search for partitions in the Call Routing > Class of Control > Partitions menu. Can be added to a Calling Search Space like any other partition 28

29 Call Control Discovery (CCD) Unified CM Configuration Requesting Service Selected SAF trunks are used to originate outbound calls towards learned destinations 29

30 Nice Devices Paris Devices Call Control Discovery (CCD) Integration with Static Routing CSSs Partitions Route Lists Route Groups Intercept patterns learned through CCD SAF_Learned_Patterns_PT 8408XXXX [4: ] 8919XXXX [4: ] 8212XXXX [4: ] 8611XXXX [4: ] 8649XXXX [4: ] CCD selects SAF-enabled H.323/SIP trunks CCD OnNet_RG GK GK-controlled Trunk Paris_CSS OnCluster_PT All IP Phone DNs (833XXXXX) Intercluster_PT OnNet RL HQ_RG HQ GWs 8271XXXX 8971XXXX Paris_RG Nice_CSS 8200XXXX French_PSTN_PT XXXXXXXXXX +! French Intl RL French Loc RL 2 nd pref Local Route group Paris GWs Nice GWs Nice_RG 30

31 Call Control Discovery (CCD) Integration with Static Routing PSTN Failover CSSs Partitions Route Lists Route Groups Call SAF_Learned_Patterns_PT 8408XXXX [4: ] 8919XXXX [4: ] SAF has notified CCD engine that 8408XXXX is unreachable via IP Call Paris_CSS 8212XXXX [4: ] 8611XXXX [4: ] 8649XXXX [4: ] CCD HQ_RG OnCluster_part All IP Phone DNs (833XXXXX) HQ GWs Paris Phone ParisAAR_CSS French_PSTN_part French Intl RL 2 nd pref Paris_RG XXXXXXXXXX +! French Loc RL Local Route group Paris GWs Nice GWs Nice_RG 31

32 Call Control Discovery (CCD) Monitoring and Troubleshooting for Unified CM RTMT is used to monitor learned routes and configured SAF Forwarders SAF/CCD tracing is included as part of the Unified CM SDI and SDL traces Learned Patterns are not included in the Route Plan Report in Unified CM Admin The Dialed Number Analyzer (DNA) tool will match CCD-learned patterns 32

33 Call Control Discovery (CCD) Unified CME, SRST, CUBE, Gateway Support Details Starting with Cisco IOS 15.0(1)M, Unified CME, CUBE and IOS Gateways can advertise CCD service, or request, or both Unified CME Unified CME CUBE Unified CME Recommended IOS 15.1(3)T Listen-only mode for SRST Transparent PSTN failover when destination is unreachable SAF Network Scalability: Up to 125 advertised DN patterns per CME/CUBE Up to 6,000 learned DN patterns per CME/CUBE/SRST (platform-dependent) Unified CME CUBE Unified CME Unified CME 33

34 Call Control Discovery (CCD) Unified CME or CUBE Configuration Example router eigrp SAF-fwdr service-family ipv4 autonomous-system 1 sf-interface Ethernet0/0 topology base voice service saf profile trunk-route 1 session protocol int Eth0/0 sip transport tcp port 5060 profile dn-block 1 pattern 1 extension 5xxx pattern 2 global xxx profile dn-block 2 alias strip 4 pattern 3 extension 8123xxx Co-resident SAF Forwarder Trunk route: signaling IP address, port, protocol DN blocks: patterns to be advertised and to DID transformation rules profile callcontrol 2 dn-service dn-block 1 dn-block 2 trunk-route 1 site-code 8333 exit dn-service exit-profile channel 1 vrouter SAF-fwdr asystem 1 publish callcontrol 2 subscribe callcontrol wildcarded dial-peer voice 100 voip destination-pattern.t session target saf CCD instance: integrates DN blocks and trunk route SAF client: publish and/or subscribe to services Enable call agent to look up routes learned through SAF 34

35 Call Control Discovery (CCD) Case Study chi-f2 chi-f1 lon-f2 lon-f1 hkg-f2 hkg-f1 US HQ Advertise 8312XXXX [4: ] MPLS VPN Chicago 8408XXXX [4: ] 8617XXXX [4: ] Request Any CCD instance Unified CM Europe HQ Advertise 8444XXXX [4: ] MPLS VPN London 8446XXXX [4: ] 8443XXXX [4: ] Request Any CCD instance Unified CM Asia HQ hkg-f3 Advertise Unified CM Hong Kong 8852XXXX [4: ] 8861XXXX [4: ] 8862XXXX [4: ] Request Any CCD instance SRST Request Any CCD instance San Jose Request SRST Any CCD instance CUBE Advertise 8334XXXX [4: ] Request Any CCD instance Advertise 8494XXXX [4: ] Request Any CCD instance Boston Nice Frankfurt IOS GW Unified CME Advertise 8822XXXX [4: ] Request Any CCD instance Seoul Unified CME Advertise 8651XXXX [4: ] Request Any CCD instance Singapore 35

36 Service Advertisement Framework (SAF) The SAF Network The SAF Client-Network Interface 36

37 The SAF Network Agenda What is a SAF advertisement How services are discovered and routed CCD CCD CCD CCD How to deploy SAF on an enterprise network CCD SAF Forwarder SAF-unaware Router 37

38 The SAF Network What Is a SAF Advertisement? SAF Header SAF Service Data Service ID IP Address Port Length Metrics Client Data Identifies service type and unique instance Used by forwarders to propagate advertisements Metrics used to avoid loops and for future client use Service-specific information Meaningful only to clients of the given service Transparent to forwarders 38

39 The SAF Network The SAF Forwarder Protocol (SAF-FP) Non-SAF Cloud First implementation of service routing Leverages EIGRP reliable transport (IP protocol 88) Uses DUAL algorithm to prevent loops Works on top of any IP routing protocol (OSPF, BGP, static,...) No periodic broadcasts Incremental updates only when changes occur e.g., Service publication, service withdrawal, service update, connectivity loss, new forwarder comes online Supports IPv4 and IPv6* (no IPv6 clients yet) 39

40 The SAF Network Forwarder Neighbor Establishment L2-Adjacent Dynamic Discovery Multicast Occurs automatically on all enabled interfaces Static Configuration Unicast Prevents dynamic discovery on the same interface Not configured 40

41 The SAF Network Forwarder Neighbor Establishment Non-Adjacent Static Configuration Unicast Configured between each pair of forwarders Non-SAF-enabled Network Dynamic Discovery Requires multicast routing Forwarders join a common peer group New in 15.2(1)T Non-SAF-enabled Network 41

42 The SAF Network Forwarder Neighbor Establishment Non-Adjacent Static/Dynamic Configuration Unicast One Forwarder configured as a dynamic unicast neighbor Other forwarder configured as a static neighbor New in 15.2(1)T Non-SAF-enabled Network 42

43 The SAF Network Forwarder Configuration L2- Adjacent fwdr1 Eth0/0 Eth0/1 fwdr2 interface Ethernet0/0 ip address router eigrp SAF-fwdr service-family ipv4 autonomous-system 1 topology-base interface Ethernet0/1 ip address router eigrp SAF-fwdr service-family ipv4 autonomous-system 1 topology-base Non- Adjacent fwdr3 Loop0 Dark Net fwdr4 Loop1 interface Loopback0 ip address router eigrp SAF-fwdr service-family ipv4 autonomous-system 1 neighbor loopback0 remote 16 topology-base interface Loopback1 ip address router eigrp SAF-fwdr service-family ipv4 autonomous-system 1 neighbor loopback1 remote 16 topology-base 43

44 The SAF Network How Advertisements Propagate When a SAF forwarder receives an advertisement: 1) It stores it in memory 2) It sends it out through all the other SAF-enabled interfaces fwdr1 fwdr2 fwdr3 EIGRP-style metrics and the DUAL algorithm are used to avoid loops and to provide fast convergence fwdr1 fwdr3 fwdr2 fwdr4 fwdr5 44

45 The SAF Network Quiz Hub-and-spoke forwarder topology Forwarder 1 sends an advertisement to the HQ forwarder Q: Will the HQ forwarder propagate it to Forwarder 2 and Forwarder 3? router eigrp SAF-fwdr service-family ipv4 auton 1 sf-interface loopback0 no split-horizon topology-base neighbor Loop0 Dark Net HQ Fwdr A: Only if split horizon is disabled on the interface! Loop1 Fwdr1 Loop1 Fwdr2 Loop1 Fwdr3 45

46 The SAF Network Other Aspects of SAF-FP Stub forwarder Learn services normally from other forwarders Advertise only locally published services, or no services at all Improve scalability and network stability Neighbor authentication MD5 or native algorithm Avoid malicious service injection or manipulation of services Many other features inherited from EIGRP Bandwidth-percent, hello-interval, hold-time, split-horizon, maximum-hops, metric weights, etc. 46

47 The SAF Network SAF Forwarder Platform and Release Support ISR, ISR G2, 7200 Series IOS 15.0(1)M 7600 Series 12.2(33)SRE ASR 1000 Series IOS 12.2XE (RLS5) Catalyst 6500 Series 12.2(33)SXI4 Catalyst 4500 Series 15.1(1)SG Q4CY11 Catalyst 3000 Series under consideration Nexus 7000 Series under consideration 47

48 chi-f2 chi-f1 US HQ The SAF Network Case Study Chicago lon-f2 lon-f1 Dynamic Discovery Non-adjacent neighbors Multicast peer-group* Europe HQ Dynamic Unicast Non-adjacent neighbors Dynamic Unicast peers* Dynamic Discovery L2-adjacent neighbors Multicast London Asia HQ hkg-f3 hkg-f2 hkg-f1 Hong Kong MPLS VPN Static Configuration Non-adjacent neighbors Unicast peers MPLS VPN Dynamic Discovery L2-adjacent neighbors Multicast sjc-f nic-f bos-f fra-f seo-f sin-f San Jose Boston Nice Frankfurt Seoul Singapore *Multicast Peer-Group Discovery and Dynamic Unicast Neighbors available in 15.2(1)T 48

49 The SAF Client-Network Interface Agenda CCD CCD CCD CCD CCD SAF Client SAF-CP SAF-CP How SAF clients connect to the SAF network How SAF clients publish services How SAF clients request services 49

50 The SAF Client-Network Interface SAF Client Types SAF clients perform three functions: Register to the network Publish services Subscribe to services External clients communicate to a SAF forwarder via the SAF Client Protocol (SAF-CP) Internal Cisco IOS clients communicate to a co-located SAF forwarder via internal API External Clients (Cisco Unified CM) SAF-CP SAF-FP SAF Network Internal IOS Clients (CUCME, SRST, CUBE...) SAF-FP Internal API 50

51 The SAF Client-Network Interface The SAF Client Protocol (SAF-CP) Simple TCP-based binary TLV protocol based on STUN (RFC-3489) Assumes client knows IP address of the SAF forwarder Security: digest authentication based on shared secret (user+pwd) Client can publish and subscribe to multiple services Forwarder notifies client of services matching subscriptions Forwarder sends updates only when there are service changes Client sends periodic Register as a keepalive 51

52 SAF-CP The SAF Client-Network Interface Connecting External Clients to a Forwarder router eigrp saf! service-family ipv4 autonomous-system 100 eigrp stub connected! sf-interface Loopback0 no split-horizon exit-sf-interface! topology base external-client vnt-alpha exit-sf-topology exit-service-family service-family external-client listen ipv external-client vnt-alpha basename username vnt-saf password ciscocisco keepalive Configure credentials for client authentication Multiple clients can share same credentials with basename keyword (e.g., nodes of the same Unified CM cluster) Up to 50 clients can connect to the same forwarder in the current release 52

53 SAF Forwarders in Unified CM Each Unified CM node can be configured to talk to a primary and secondary SAF Forwarder Each node in the cluster independently advertises Hosted DN patterns Advertisements include a Cluster ID to allow recipients to know the advertisements come from the same cluster Nodes that send advertisements are based on the Unified CM Group on the Device Pool of the SAF SIP Trunk. 53

54 The SAF Client-Network Interface Cisco Unified CM as a SAF client Supports SAF client authentication Process runs on every subscriber node in the cluster Two configuration modes: Basic all nodes use same primary/secondary SAF forwarders Advanced multiple sets of forwarders (for CoW deployments) Single-Site Cluster Clustering over the WAN Unified CM Cluster Unified CM Cluster Primary SAF Fwdr Secondary SAF Fwdr Primary SAF Fwdr Secondary SAF Fwdr Primary SAF Fwdr Secondary SAF Fwdr 54

55 The SAF Client-Network Interface Cisco Unified CM SAF Client Configuration Example 1. Configure SAF Security Profile 2. Configure SAF Forwarder IMPORTANT Make sure you put sign at the end of the client label 55

56 The SAF Client-Network Interface Case Study chi-f2 chi-f1 lon-f2 lon-f1 hkg-f2 hkg-f1 US HQ Chicago Unified CM Europe HQ London Unified CM Asia HQ hkg-f3 Unified CM Hong Kong MPLS VPN MPLS VPN SRST sjc-f CUBE SRST nic-f bos-f IOS GW fra-f Unified CME seo-f Unified CME sin-f San Jose Boston Nice Frankfurt Seoul Singapore 56

57 Typical SAF Networks 57

58 US HQ Unified CM EMEA HQ Unified CM Asia HQ Unified CM chi-f2 chi-f1 Chicago lon-f2 lon-f1 London hkg-f1 Hong Kong hkg-f3 hkg-f2 Publish & Subscribe Publish & Subscribe Publish & Subscribe SAF-Enabled Network Subscribe Only Subscribe Only Publish & Subscribe Publish & Subscribe Publish & Subscribe Publish & Subscribe SRST SRST CUBE IOS GW Unified CME Unified CME San Jose Boston Nice Frankfurt Seoul Singapore 58

59 CCD and Session Management Edition (SME) IP PSTN CUBE CUBE SME Learns Internal E.164 routes from Leaf Clusters and advertises patterns on behalf of 3 rd party PBXs and any Applications SME SAF Network PSTN PSTN PSTN SFO Dallas NYC Leaf Clusters Route Calls to each other Directly CCD allows Leaf Clusters to route calls amongst each other directly SME learns how to route calls to Leaf Clusters Dynamically SME Advertises Routes on behalf of 3 rd party devices and Applications 59

60 SAF/CCD and Inter Cluster RSVP SIP Preconditions for RSVP over SIP Trunks SAF Trunks support SIP Pre-Conditions for RSVP reservations between CUCM clusters, between CUCMEs and CUCM and CUCME RSVP over SAF Enabled SIP Trunks Central Site 1 Central Site 2 SCCP/SIP Phone 1 Branch 1 RSVP Agent RSVP Agent Media Stream IP WAN RSVP Reservation RSVP Agent RSVP Agent SCCP/SIP Phone 2 Branch 2 60

61 Conclusions 61

62 Conclusions Recap of Key Concepts SAF is a generic framework for service discovery Three main components: The network propagate service advertisements The client-network interface publish and subscribe to services The services e.g., Call Control Discovery Key differentiating aspects: Scalability, bandwidth efficiency, fast convergence In the network vs. overlay solution Service routing independent of IP routing Push-based model allows use for real-time applications Modular approach to maximize re-use 62

63 Conclusions Benefits of Call Control Discovery Reduce deployment time, realize quicker ROI Dial plan configuration complexity reduced from N² to N Allows optimal dial plan to be implemented quickly (i.e., on-net numbering plan with automatic PSTN failover) Reduce ongoing operational costs Complexity of adding/removing/changing a site drastically reduced No need to purchase, maintain, and configure dedicated gatekeepers Reduced reliance on static back-up configuration Improve business continuity Increased availability even during partial network failure thanks to dynamic awareness Implementable and maintainable mechanism for automatic PSTN rerouting Fast rerouting during failures 63

64 Conclusions Future and Feedback SAF Client Protocol standardization SAF Forwarder Protocol enhancements Other SAF services CCD enhancements 64

65 For More Information Solution Reference Network Design Cisco Unified Communications Solution Reference Network Design (SRND) for Cisco Unified Communications Manager release 8.x, available online at: SAF Deployment Guide on Cisco.com: Cisco IOS SAF Configuration guide on Cisco.com: Service Advertisement Framework Feature Guide on Cisco.com: SAF Support in Unified Communications System Test Configurations: _System_Test_Configuration 65

66 BRKUCC-2003 Recommended Reading Please browse on-site Cisco Store for suitable reading. 66

67 Please complete your Session Survey We value your feedback - don't forget to complete your online session evaluations after each session. Complete 4 session evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Networkers 20 th Anniversary t-shirt. All surveys can be found on our onsite portal and mobile website: You can also access our mobile site and complete your evaluation from your mobile phone: 1. Scan the Access Code (See for software, alternatively type in the access URL) 2. Login 3. Complete and Submit the evaluation 67

68 69

69