a new approach to call routing and dial plans based on the...

BRKUCC-2003

A New Approach to Call Routingand Dial Plans Based on the Service Advertisement Framework (SAF)

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKUCC-2003 2

IntroductionPrerequisites

This Session Assumes Basic Knowledge of:

Routing Protocols

Dial Plans

Cisco Unified Communications Manager

Cisco Unified Communications Call Processing Deployment Models


IntroductionSession 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


IntroductionProblem Statement and Goals

Advanced network services and applications are often deployed as overlays

Can the network leverage dynamicproperties of routing to help these services communicate?

Goals:

Provide a network foundation for service awareness

Enable applications


IntroductionThe 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, ...


IntroductionProblem Statements Specific to Unified Communications

Call ControlServices

PresenceServices

PolicyServices

ConferencingServices

GatewayServices

MediaServices

LocationServices

CollaborationServices

VM / UMServices

The Network

Unified Communications requires a large number of devices, services and applications

Need to reduce complexity

Need to simplify provisioning to accelerate absorption

Need to simplify operations and reduce TCO

Routing between call agents relies mainly on staticconfiguration

Complexity, operational cost, availability


IntroductionLimitations of Current Call Routing Approaches

Configuration complexity, speed of deployment

High operational cost, TCO

Availability, business continuity

Call Agent

Call AgentCall Agent

Call Agent

Call Agent

Call Agent

Call Agent

Call Agent Call Agent

Call Agent

Call Agent

Call Agent

Call Agent

Call Agent

Call Agent


Call Agent

Call Agent

Call Agent

Call Agent


Call Agent

Call Agent

Call Agent

Call Agent

Call Agent

IP Network

Proxy / GK /

Session Manager

IP Network


IntroductionCall Control Discovery (CCD): a SAF Service

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 dynamicallyroute calls to remote destinations based on received advertisements

CCD

Call Agent


Call Agent

Call Agent

Call Agent

Call Agent


Call Agent

Call Agent

Call Agent

Call Agent

Call Agent


IntroductionSAF+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


IntroductionSAF Terms and Definitions

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

CCD

SAFHeader

SAFService Data


IntroductionSAF Architecture

Cisco Unified CMSession

ManagementEdition

CiscoUnified CM

CUBE

Cisco

IOS GW

CUCMESRST

CCD CCD

SAFForwarder

SAFClient

SAF-unawareRouter

SAFClientProtocol

SAFClientProtocol

CCD CCD CCD


Call Control Discovery (CCD)

Scope and Objectives

Features and Functionality

Configuration Examples (Unified CM and IOS)

Integration with ―Static Routing‖


Call Control Discovery (CCD)Scope and Objectives

CiscoUnified CM

CiscoUnified CM

CUBE

Cisco

IOS GW

CUCMESRST

CCD CCDCCD CCD CCD

Enable call agents to exchange dial plan, signaling protocol and reachability information through SAF

Extend call control logic to incorporate dynamic routingbased 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

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="http://www.cisco.com/namespaces/saf-uc"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.cisco.com/namespaces/saf-uc saf-uc-

v0.95.xsd" schemaVersion="1.0" id="1.0">

<hosted-dn>

<description>

<product>UCM</product>

<version>8.5.1.10000-26</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">

2XXX

8123700[136]

+16505557XXX

</dn-pattern>

</hosted-dn>

</service-description>


New York

Call Control Discovery (CCD)Advertising DN Ranges

DN Pattern ―to DID‖ rule IP address Protocol

8408XXXX 4:+1408555 10.1.1.1 SIP

8415XXXX 4:+1415777 10.1.1.1 SIP

8949XXXX 4:+1949222 10.1.1.1 SIP

New York CME Routing Table

San Jose

San Francisco Irvine

SAF-EnabledIP Network

PSTN

8408XXXX

8415XXXX 8949XXXX

8212XXXX

10.1.1.110.2.2.2

IP address: 10.1.1.1

Protocol: SIP

DN Patterns:

8408XXXX [4:+1408555],

8415XXXX [4:+1415777],

8949XXXX [4:+1949222]

Service Advertisement


New York

Call Control Discovery (CCD)Learning DN Ranges


8212XXXX 4:+1212444 10.2.2.2 SIP

San Jose CUCM Routing Table

San Jose


PSTN

8408XXXX

8212XXXX

10.2.2.210.1.1.1


Protocol: SIP

DN Patterns:

8212XXXX [4:+1212444]

Service Advertisement


8415XXXX 8949XXXX



8415XXXX 8949XXXX

London

8442XXXX

10.3.3.3


8408XXXX +1408555 /4 10.1.1.1 SIP

8415XXXX +1415777 /4 10.1.1.1 SIP

8949XXXX +1949222 /4 10.1.1.1 SIP


8212XXXX +1212444 /4 10.2.2.2 SIP

New York

Call Control Discovery (CCD)Dynamic Routing



San Jose


PSTN

8408XXXX

8212XXXX

10.2.2.210.1.1.1

Call 84421000


8212XXXX 4:+1212444 10.2.2.2 SIP

8442XXXX 4:+442077111 10.3.3.3 H.323


8408XXXX 4:+1408555 10.1.1.1 SIP

8415XXXX 4:+1415777 10.1.1.1 SIP

8949XXXX 4:+1949222 10.1.1.1 SIP

8442XXXX 4:+442077111 10.3.3.3 H.323



8415XXXX 8949XXXX

New York

Call Control Discovery (CCD)Automatic PSTN Failover


8212XXXX 4:+1212444 10.2.2.2 SIP

8442XXXX 4:+442077111 10.3.3.3 H.323

San Jose CUCM Routing TableDN Pattern ―to DID‖ rule IP address Protocol

8408XXXX 4:+1408555 10.1.1.1 SIP

8415XXXX 4:+1415777 10.1.1.1 SIP

8949XXXX 4:+1949222 10.1.1.1 SIP

8442XXXX 4:+442077111 10.3.3.3 H.323


San Jose


London

PSTN

8408XXXX

8442XXXX

8212XXXX

10.2.2.2

10.3.3.3

10.1.1.1

8442XXXX

8442XXXX

Call 84421000

Translate to+4420771111000



8415XXXX 8949XXXX

New York

Call Control Discovery (CCD)Automatic Rerouting for SRST


8408XXXX 4:+1408555 10.1.1.1 SIP

8415XXXX 4:+1415777 10.1.1.1 SIP

8949XXXX 4:+1949222 10.1.1.1 SIP

New York SRST Routing Table

San Jose


PSTN

8408XXXX

8212XXXX

10.1.1.110.2.2.2

Call 89491000

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



8415XXXX 8949XXXX

London

8442XXXX

10.3.3.3

Chicago

Call Control Discovery (CCD)3rd Party IP PBX Integration using CUBE


Chicago CUBE

Routing Table

San Jose


PSTN

8408XXXX

8312XXXX

10.4.4.410.1.1.1


8408XXXX 4:+1408555 10.1.1.1 SIP

8415XXXX 4:+1415777 10.1.1.1 SIP

8949XXXX 4:+1949222 10.1.1.1 SIP

8442XXXX 4:+442077111 10.3.3.3 H.323DN Pattern ―to DID‖ rule IP address Protocol

8442XXXX 4:+442077111 10.3.3.3 H.323

8312XXXX 4:+1312888 10.4.4.4 SIP

3rd Party

IP PBX

Call 84156789

10.4.4.8CUBE


Protocol: SIP

DN Patterns:

8312XXXX [4:+1312888]

Static dial peerfor destination

8312XXXX



8415XXXX 8949XXXX

London

8442XXXX

10.3.3.3

Boston

Call Control Discovery (CCD)3rd Party TDM PBX Integration

San Jose CUCM Routing Table Boston Gateway Routing Table

San Jose


PSTN

8408XXXX

8617XXX

10.5.5.510.1.1.1


8408XXXX 4:+1408555 10.1.1.1 SIP

8415XXXX 4:+1415777 10.1.1.1 SIP

8949XXXX 4:+1949222 10.1.1.1 SIP

8442XXXX 4:+442077111 10.3.3.3 H.323


8442XXXX 4:+442077111 10.3.3.3 H.323

8617XXXX 4:+1617999 10.5.5.5 SIP

3rd Party

TDM PBX

TDM

Call 84156789

10.5.5.8

Cisco IOSGateway

Static dial peerfor destination

8617XXXX


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


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


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


Call Control Discovery (CCD)Unified CM Configuration—Hosted DNs

Used to advertise full E.164 ranges instead of internal numbers + ―toDID‖ rules

Applies the same ―toDID‖ rules to all DN Patterns in this group


Call Control Discovery (CCD)Unified CM Configuration—Hosted DNs (Cont.)

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

Can bulk-import or export hosted DNs to/from a CSV file


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


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


Call Control Discovery (CCD)Unified CM Configuration—Requesting Service

Selected SAF trunksare used to originate outbound calls towards learned destinations


Call Control Discovery (CCD)Integration with ―Static Routing‖

OnCluster_PT

All IP Phone DNs (833XXXXX)

CSSs Partitions Route Lists Route Groups

Nic

e D

evic

es

Nice_RG

Nice GWs

“Intercept” patterns

learned through CCD

Pa

ris D

evic

es

Paris_RG

French_PSTN_PT Local

Route

group

2nd

pref

HQ_RG

HQ GWs

SAF_Learned_Patterns_PT

Paris GWs

Intercluster_PT

OnNet_RG

GK

GK-controlled TrunkCCD

Nice_CSS

Paris_CSS

112

+33XXXXXXXXXX

+!

8271XXXX

8971XXXX

8200XXXX

8408XXXX [4:+1408555]

8919XXXX [4:+1919392]

8212XXXX [4:+1212666]

8611XXXX [4:+6123456]

8649XXXX [4:+6498765]

OnNet

RL

French

Intl RL

French

Loc RL

CCD selects

SAF-enabled

H.323/SIP trunks


Call Control Discovery (CCD)Integration with ―Static Routing‖—PSTN Failover

OnCluster_part

All IP Phone DNs (833XXXXX)

CSSs Partitions Route Lists Route Groups

Nice_RG

Nice GWs

Paris_RG

French_PSTN_part

Local

Route

group

2nd

pref

HQ_RG

HQ GWs

SAF_Learned_Patterns_PT

Paris GWs

CCD

ParisAAR_CSS

Paris_CSS

112

+33XXXXXXXXXX

+!

French

Intl RL

French

Loc RL

ParisPhone

8919XXXX [4:+1919392]

8212XXXX [4:+1212666]

8611XXXX [4:+6123456]

8649XXXX [4:+6498765]

8408XXXX [4:+1408555]

Call +14085551234

Call

84081234

SAF has notified

CCD engine that

8408XXXX is

unreachable via IP


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

Call Control Discovery (CCD)Monitoring and Troubleshooting for Unified CM


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

Recommended IOS 15.1(3)T

Listen-only mode for SRST

Transparent PSTN failover when destination is unreachable

Scalability:

Up to 125 advertised DN patterns per CME/CUBE

Up to 6,000 learned DN patterns per CME/CUBE/SRST (platform-dependent)

SAF Network

CUBE

UnifiedCME

UnifiedCME

UnifiedCME

UnifiedCME

UnifiedCME

UnifiedCME

CUBE


Call Control Discovery (CCD)Unified CME or CUBE Configuration Example

router eigrp SAF-fwdrservice-family ipv4 autonomous-system 1 sf-interface Ethernet0/0topology base

voice service safprofile trunk-route 1 session protocol int Eth0/0 sip transport tcp port 5060

profile dn-block 1pattern 1 extension 5xxxpattern 2 global 1408555xxx

profile dn-block 2 alias 14085258 strip 4pattern 3 extension 8123xxx

profile callcontrol 2 dn-servicedn-block 1dn-block 2trunk-route 1 site-code 8333

exit dn-serviceexit-profile

channel 1 vrouter SAF-fwdr asystem 1publish callcontrol 2subscribe callcontrol wildcarded

dial-peer voice 100 voipdestination-pattern .Tsession target saf

Co-resident SAF Forwarder

Trunk route: signaling IPaddress, port, protocol

DN blocks: patterns to beadvertised and ―to DID‖transformation rules

CCD instance: integratesDN blocks and trunk route

SAF client: publish and/orsubscribe to services

Enable call agent to look uproutes learned through SAF


Call Control Discovery (CCD)Case Study

Europe HQ

San Jose

US HQ

Boston Nice Frankfurt

Chicago London

MPLSVPN

Asia HQ

Hong Kong

Seoul Singapore

chi-f1

chi-f2

lon-f1

lon-f2

hkg-f3

hkg-f2

hkg-f1

MPLSVPN

UnifiedCM

UnifiedCM

Unified CM

SRSTSRST

CUBEIOS GW

UnifiedCME

UnifiedCME

Advertise

8334XXXX

[4:+3349988]

Request

Any CCD instance

Advertise

8494XXXX

[4:+49402233]

Request

Any CCD instance

Advertise

8651XXXX

[4:+6512345]

Request

Any CCD instance

Advertise

8822XXXX

[4:+8226666]

Request

Any CCD instance

Request

Any CCD instanceRequest

Any CCD instance

Advertise

8312XXXX [4:+1312777]

8408XXXX [4:+1408555]

8617XXXX [4:+1617333]

Request

Any CCD instance

Advertise

8444XXXX [4:+44201111]

8446XXXX [4:+44161888]

8443XXXX [4:+44131777]

Request

Any CCD instance

Advertise

8852XXXX [4:+8524444]

8861XXXX [4:+8610999]

8862XXXX [4:+8621555]

Request

Any CCD instance


Service Advertisement Framework (SAF)

The SAF Network

The SAF Client-Network Interface


The SAF NetworkAgenda

CCD CCDCCD CCD CCD

SAFForwarder

SAF-unawareRouter

What is a SAF advertisement

How services are discovered and routed

How to deploy SAF on an enterprise network


The SAF NetworkWhat Is a SAF Advertisement?

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

SAF Header SAF Service Data

Service ID

Metrics

101 2 1.2.3.4

...

...

IP Address Port

Client Data

Length


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)

The SAF NetworkThe SAF Forwarder Protocol (SAF-FP)

Non-SAF Cloud


The SAF NetworkForwarder 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


The SAF NetworkForwarder Neighbor Establishment—Non-Adjacent

Static Configuration

Unicast

Configured between each pair of forwarders

Dynamic Discovery

Requires multicast routing

Forwarders join a common ―peer group‖

New in 15.2(1)T

Non-SAF-enabled

Network

Non-SAF-enabled

Network


The SAF NetworkForwarder 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


The SAF NetworkForwarder Configuration

interface Ethernet0/0

ip address 1.1.1.1 255.255.255.0

router eigrp SAF-fwdr

service-family ipv4 autonomous-system 1

topology-base

interface Ethernet0/1

ip address 1.1.1.2 255.255.255.0



topology-base

Eth0/0 Eth0/1

fwdr1 fwdr2

Loop0 Loop1

fwdr3 fwdr4Dark Net

interface Loopback0

ip address 3.3.3.1 255.255.255.0



neighbor 4.4.4.1 loopback0 remote 16

topology-base

interface Loopback1

ip address 4.4.4.1 255.255.255.0



neighbor 3.3.3.1 loopback1 remote 16

topology-base

L2-Adjacent

Non-Adjacent


The SAF NetworkHow 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

EIGRP-style metrics and the DUAL algorithm are used to avoid loops and to provide fast convergence

fwdr1

fwdr2

fwdr3

fwdr1

fwdr2

fwdr3 fwdr4

fwdr5



service-family ipv4 auton 1

sf-interface loopback0

no split-horizon

topology-base

neighbor ...

...

The SAF NetworkQuiz

―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?

A: Only if split horizon is disabled on the interface!

Dark

Net

Loop0

Loop1

Loop1Loop1

HQ Fwdr

Fwdr1Fwdr2

Fwdr3


The SAF NetworkOther 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.


The SAF NetworkSAF 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 2.5.0 (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


The SAF NetworkCase Study

Europe HQ

San Jose

US HQ


Chicago London

MPLSVPN

Asia HQ

Hong Kong

Seoul Singapore

chi-f1

chi-f2

bos-fsjc-f

lon-f1

lon-f2

sin-fseo-f

hkg-f3

hkg-f2

hkg-f1

fra-fnic-f

MPLSVPN

Dynamic DiscoveryNon-adjacent neighbors

Multicast peer-group*

Dynamic DiscoveryL2-adjacent neighbors

Multicast

Dynamic DiscoveryL2-adjacent neighbors

Multicast

Static ConfigurationNon-adjacent neighbors

Unicast peers

*Multicast Peer-Group Discovery and Dynamic Unicast Neighbors available in 15.2(1)T

Dynamic UnicastNon-adjacent neighbors

Dynamic Unicast peers*


The SAF Client-Network InterfaceAgenda

CCD CCD

SAFClient

CCD CCD CCD

SAF-CP SAF-CP

How SAF clients connect to the SAF network

How SAF clients publish services

How SAF clients request services


The SAF Client-Network InterfaceSAF 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

(Cisco Unified CM) (CUCME, SRST, CUBE...)

SAF-CP

SAF Network

InternalAPI

ExternalClients

InternalIOS Clients

SAF-FP

SAF-FP


The SAF Client-Network InterfaceThe 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


The SAF Client-Network InterfaceConnecting External Clients to a Forwarder

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

SAF-CP

router eigrp saf

!


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 ipv4 5050

external-client vnt-alpha basename

username vnt-saf

password ciscocisco

keepalive 10000


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.


The SAF Client-Network InterfaceCisco Unified CM as a SAF client

Unified CM

Cluster

PrimarySAF Fwdr

Secondary SAF Fwdr

Unified CM

Cluster

PrimarySAF Fwdr

Secondary SAF Fwdr

PrimarySAF Fwdr

Secondary SAF Fwdr

Single-Site Cluster Clustering over the WAN

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)


The SAF Client-Network InterfaceCisco Unified CM—SAF Client Configuration Example

1. Configure SAF Security Profile 2. Configure SAF Forwarder

IMPORTANT

Make sure you put the @ sign

at the end of the client label


The SAF Client-Network InterfaceCase Study

Europe HQ

San Jose

US HQ


Chicago London

MPLSVPN

Asia HQ

Hong Kong

Seoul Singapore

chi-f1

chi-f2

bos-fsjc-f

lon-f1

lon-f2

sin-fseo-f

hkg-f3

hkg-f2

hkg-f1

fra-fnic-f

MPLSVPN

UnifiedCM

UnifiedCM

Unified CM

SRSTSRST

CUBEIOS GW

UnifiedCME

UnifiedCME


Typical SAF Networks


EMEA HQ

San Jose

US HQ


Chicago London

Asia HQ

Hong Kong

Seoul Singapore

chi-f1

chi-f2

lon-f1

lon-f2

Unified CM

SRSTSRST CUBE IOS GW UnifiedCME

UnifiedCME

Unified CM Unified CM

hkg-f1hkg-f3

hkg-f2

Publish &

Subscribe

Publish &

Subscribe

Publish &

Subscribe

Publish &

Subscribe

Publish &

Subscribe

Publish &

Subscribe

Publish &

Subscribe

Subscribe

Only

Subscribe

Only

SAF-Enabled Network


SAF Network

CCD and Session Management Edition (SME)

CUBE CUBE

SFO NYCDallas

SME

IP PSTNSME Learns Internal E.164 routes

from Leaf Clusters and advertises

patterns on behalf of 3rd party PBXs

and any Applications

PSTN PSTN PSTN

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 3rd party devices and Applications


SAF/CCD and Inter Cluster RSVPSIP Preconditions for RSVP over SIP Trunks

SAF Trunks support SIP Pre-Conditions for RSVP reservations between CUCM

clusters, between CUCMEs and CUCM and CUCME

IP WAN

Branch 2

Central Site 1

Branch 1

Media Stream

RSVPReservation

RSVP Agent

RSVPAgent

RSVP Agent

RSVP Agent

RSVP over SAF Enabled SIP Trunks

SCCP/SIP SCCP/SIP

Phone 1 Phone 2

Central Site 2


Conclusions


ConclusionsRecap 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


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


ConclusionsFuture and Feedback

SAF Client Protocol standardization

SAF Forwarder Protocol enhancements

Other SAF services

CCD enhancements


For More InformationSolution Reference Network Design

Cisco Unified Communications Solution Reference Network Design (SRND) for Cisco Unified Communications Manager release 8.x, available online at:

www.cisco.com/go/srnd

Cisco IOS SAF Configuration guide on Cisco.com:http://www.cisco.com/en/US/docs/ios/saf/configuration/guide/15_0/saf_15_0_book.html

Service Advertisement Framework Feature Guide on Cisco.com:http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/feature/guide/SAF_FeatureModule.html

SAF Support in Unified Communications – System Test Configurations:http://docwiki.cisco.com/wiki/Service_Advertisement_Framework_Support_in_Unified_Communications_-

_System_Test_Configuration

SAF Deployment Guide on Cisco.com:http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/ps10822/whitepaper_c11-

636604.html

http://www.cisco.com/go/srnd

http://www.cisco.com/en/US/docs/ios/saf/configuration/guide/15_0/saf_15_0_book.html

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/feature/guide/SAF_FeatureModule.html

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/feature/guide/SAF_FeatureModule.html

http://docwiki.cisco.com/wiki/Service_Advertisement_Framework_Support_in_Unified_Communications_-_System_Test_Configuration



http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/ps10822/whitepaper_c11-636604.html





BRKUCC-2003

Please browse on-site Cisco Store for suitable reading.

Recommended Reading


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 20th Anniversary t-shirt.

All surveys can be found on our onsite portal and mobile website: www.ciscoliveeurope.com/connect/mobi/login.ww

You can also access our mobile site and complete your evaluation from your mobile phone:

1. Scan the Access Code(See http://tinyurl.com/qrmelist for software,

alternatively type in the access URL)

2. Login

3. Complete and Submit the evaluation

Please complete your Session Survey

http://www.ciscoliveeurope.com/connect/mobi/login.ww

http://tinyurl.com/qrmelist

a new approach to call routing and dial plans based on the...

Documents