BRKVVT-2008_c2© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 1 Enterprise Dial-Plan Fundamentals BRKVVT-2008.

BRKVVT-2008_c2 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 1

Enterprise Dial-Plan Fundamentals

BRKVVT-2008

© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKVVT-2008_c2 2

BRKVVT-2008 Abstract

This session explains the various Cisco Unified Communications Manager (Unified CM) fundamental elements used to construct a dial plan; attendees learn how closest match routing works in Cisco Unified CM, how partitions and calling search spaces function as well as the various constructs available to route on-net and off-net calls

Other concepts such as Class of Service, Class of Service for Cisco Unified SRST, Internal and External Alternate routing, calling- and called-party translations are also covered; this session provides a comprehensive understanding of the fundamental elements involved in an Enterprise Dial-Plan design and is a prerequisite for the Advanced Dial-Plan session


Enterprise Dial Plan FundamentalsParts List


Agenda

Call Routing Basics

Calling Search Spaces and Partitions

Building Class of Service

Building Class of Service Unified SRST (COR)

Alternate Routing

Tail-End Hop-Off (TEHO)

Other Tools


Cisco Unified CM

Router/GW

Ext.1000

Ext.1001

Gatekeeper

Dial PlanThe “IP Routing” of IP Telephony

+1 408 5264000

Cisco Unified CM Routes Two Basic Call Types:

On-Cluster Calls: Destination Directory Number (DN) is registered with Cisco Unified CM. DNs are considered “internal” routes.

Off-Cluster Calls: Destination Number is not registered with Cisco Unified CM. Route Patterns are configured to allow for “external” routes.

Alternate routes: Allow On-Cluster and Off-Cluster calls to attempt alternate paths to destination (e.g. IP WAN not available, go through PSTN)

9.1408XXXXXXXRoute

Pattern

GKRemoteCisco

Unified CM

PSTN

IP WAN


Cisco Unified CM Call Routing LogicCommonly Used Wildcards

Delimiter (Does Not Match Any Digits)—Used for Discarding

Range of Digits (Between 2 and 9)

Single Digit Between 0 and 9

One or More Occurrences of Digits Between 0 and 9

The “#” Digit—Used to Avoid InterDigit Timeout

A Macro That Enters the Whole North AmericanNumbering Plan into Cisco Unified CM (or a Different Country’s Numbering Plan if Using the International Dial Plan Tool)

9 . [2-9] XXXXXX

9.011! #

9. @


Cisco Unified CM Call Routing LogicPatterns

Pattern Description0, 1, 2, 3, 4, 5, 6, 7, 8, 9, *, #

Match Exactly One Keypad Button

X Any Single Digit in the Range 0–9

[xy*z] Exactly One of Any of the Keypad Buttons in the Brackets

[x-y] Exactly One of Any Digit Between x and y Inclusively

[^x-y] Any Digit That Is Not Between x and y Inclusively

! One or More Digits in the Range 0–9

wildcard? Zero or More Occurrences of the Previous Wildcard

wildcard+ One or More Occurrences of the Previous Wildcard

@ Numbering Plan Macro—More Later

<blank> Immediately Route Call with No Digits


Matches Numbers Between 1200 and 1299

Matches 1326, 1356, 1366, 1376, 1386

Matches Any Number That Begins with 13, Is Followed by One or More Digits, and Ends with #;135# and 13579# Are Example Matches

Matches 1111

Matches *1*1

Matches 1306, 1316, 1326, 13*6, 13#6

1111

*1*1

12XX

13[25-8]6

13!#

13[^3-9]6

Cisco Unified CM Call Routing LogicMatching Patterns


Cisco Unified CM Call Routing LogicNumbering Plans

@ wildcard is a macro for patterns in Numbering Plan files; groups dialed digits and assigns name tags; default is North American Numbering Plan (NANP); NANP definition is included on Cisco Unified CM in the text file

@ wildcard is 166 very specific route patterns

In 4.x, can see patterns here:

C:\Program Files\Cisco\DialPlan\NANP

In 5.x/6.x, it is not accessible

International dial plans available

http://www.cisco.com/cgi-bin/tablebuild.pl/IDP


Actual Routes in Cisco Unified CM:9.[2-9]119.[2-9]XX XXXX

Cisco Unified CM Call Routing LogicRoute Filters – The Basics

The “@” wildcard represents all the routes defined in the national numbering plan

Cisco Unified CM identifies tags in each number:

INTERNATIONAL-ACCESS

AREA-CODE

OFFICE-NUMBER ...

Route filters are logical expressions that operate on these tags

Useful for blocking 900, pay-per-call, international...

Route Pattern

“9.@”

North American Numbering Plan:9.[2-9]119.[2-9]XX XXXX9.1 [2-9]XX [2-9]XX XXXX9.011 !

“INTERNATIONAL-ACCESS”DOES-NOT-EXIST

AND“AREA-CODE”

DOES-NOT-EXIST


Cisco Unified CM Call Routing Logic Route Filters – Configuration

LIMITATION: Entire Route Filter Can Containup to 1024 Characters (Excludes“NOT-SELECTED” Fields)


Route Patterns

Cisco Unified CM Call Routing LogicBasic Principle

Cisco Unified CM matches the most specific pattern (longest-match logic)

For call routing, an IP phone directory number acts as a ‘route pattern’ that matches a single number

1XXX

Cisco Unified CM Call Routing Logic

User Dials“1200”

User Dials“1234” 1234

Directory Numbers

1234

12XX


Cisco Unified CM Call Routing LogicExample (1)

Cisco Unified CM Actions:

Configured Route Patterns

1111

1211

1[23]XX

131

13!

1[0-4]XX

User’s Dial String:



1111

1211

1[23]XX

131

13!

1[0-4]XX

Might Match

Might Match

Might Match

Might Match

Might Match

Might Match

Provide Dial Tone Wait


<Off Hook>


Digit analysis: match(fqcn="9195555644", cn="15644", pss="PA:Line1:Cisco:Local:Long Distance:International", dd=”")Digit analysis: potentialMatches=PotentialMatchesExist




1111

1211

1[23]XX

131

13!

1[0-4]XX

User’s Dial String: Might Match

Might Match

Might Match

Might Match

Might Match

Might Match

Break Dial Tone Wait


1


Digit analysis: match(fqcn="9195555644", cn="15644", pss="PA:Line1:Cisco:Local:Long Distance:International", dd=”1")Digit analysis: potentialMatches=PotentialMatchesExist



1111

1211

1[23]XX

131

13!

1[0-4]XX

User’s Dial String: Doesn’t Match

Doesn’t Match

Might Match

Might Match

Might Match

Might Match

Wait


13




1111

1211

1[23]XX

131

13!

1[0-4]XX


User’s Dial String: Doesn’t Match

Doesn’t Match

Might Match

Match!

Might Match

Match! and Might Match

Keep Waiting—More Digits Might Cause a Different Pattern to Match


131




1111

1211

1[23]XX

131

13!

1[0-4]XX


User’s Dial String: Doesn’t MatchDoesn’t Match

Doesn’t MatchDoesn’t Match

Match!


Match!

Match! and Might Match


1311



Keep Waiting—More Digits Might Cause a Different Pattern to Match



Can You Tell Which Route Pattern Is the Best Match in This Case?

Hint: We Are Being Crafty to Make Sure You Remember Forever


Extend Call to the Best Match


1311<timeout>


1111

1211

1[23]XX

131

13!

1[0-4]XX



Match!


Match!

Match!


Matches Digit Strings, but for the purposes of Closest Match Routing in this case, this matches 100 Digit Strings because you only consider the number of Potential Strings Given the Number of Digits Dialed



1311<Timeout>

Matches 200 Digit Strings

Matches 500 Digit Strings


1111

1211

1[23]XX

131

13!

1[0-4]XX



Match!


Match!

Match!


Agenda

Call Routing Basics




Alternate Routing


Other Tools


Partitions and Calling Search Spaces Analogy (1 of 4)

RitaDave

305 555 5000

Miami Yellow Pages

Dave 305 555 5000

Rita Wants to Call Dave

Dave Lists His Number in a Directory

To Do So, She Needs to Know Dave’s Number



Rita

Miami Yellow Pages

Dave 305 555 5000

To Look up Numbers, Rita Looks Through theDirectories She Owns

If She Doesn’t Havethe Right Directory…

Dallas White Pages

Outlook Address Book

Little Black Book

… She Can’t Place the Call

Rita’s List of Directories

Dave

305 555 5000



RitaDave

305 555 5000

Miami Yellow Pages

Dave 305 555 5000

But If She Has theDirectory Dave Has

Listed His Number in…

Dallas White Pages

Miami Yellow Pages

Little Black Book


… the Call Will Go Through

Miami Yellow Pages

Miami Yellow Pages



RitaDave

305 555 5000

Miami Yellow Pages

Dave 305 555 5000

Dallas White Pages

Miami Yellow Pages

Little Black Book


The Directory in Which Dave’s Number Is Listed Is His Number’s Partition

The List of Directories in Which Rita Looks up

Numbers Is HerCalling Search Space


Partitions and Calling Search Spaces Concepts

PartitionA

911

900X99XX

8001

PartitionB

9.[2-9]XXXXXX

9.[2-9]XX[2-9]XXXXXX

9.011!

7 [Transform Mask: 2001]

20022001

2000

5000

8000

Lines (Directory Numbers)

TranslationPatterns

RoutePatterns

Special numbers(MeetMe, CallPickup...)

Voice Mail Ports

Application Numbers(CTI Route Points, CTI Ports)

RoutePatterns

CSS1PartitionA

PartitionB

CSS2PartitionB

CSS3PartitionB

PartitionA

CSS4PartitionA

Phones

Lines

Gateways

Applications

“Dia

ling

” D

evic

es

“Dia

lab

le”

Pat

tern

s


Partitions and Calling Search SpacesImpact of the Partition Order in a CSS

Most specific patterns are chosen irrespectiveof partition order

Partition order is only used as a tie-breaker in case of equal matches

Calling Search Space Z

Partition A

23XX

1XXX

Partition B

23XX

12XXDevice

User dials“1234”

User dials“2345”


Partitions and Calling Search SpacesQ3: Quick Quiz Question

What Is Needed for Phone A to Be Able to Call Phone B and Vice Versa?

Phone ALine 1000

Phone BLine 2000

Line 1000 and Line 2000 Must Be in the Same Partition

Phone A and Phone B Must have same Calling Search Space

All of the above

None of the above

Phone A’s Calling Search Space Must Contain Line 2000’s Partition, and Phone B’s Calling Search Space Must Contain Line 1000’s Partition


Agenda

Call Routing Basics




Alternate Routing


Other Tools


UnifiedCM

Cluster

IP WANPSTN

...

CentralSite

RemoteSites

EmergencyCalls

Local Calls

International Calls

Lobby Phones

Office Phones

Exec Phones

Cisco Unified CM

Create “Dial-Plan Policy Groups”to Define Calling Restrictions

Instruct these Phones to Use Their Local Gateway for PSTN Access

Building Classes of ServiceRouting by User Class or Location

*


Calling SearchSpaces Partitions

Internal

Local

Long Distance

All IP Phones,Voice Mail,

MediaResources,911 Route

Pattern

LocalRoute Patterns

InternalOnly

LocalOnly

Unrestricted

<None>Default

CSS <None> DefaultPartition

Long DistanceRoute Patterns

Calling SearchSpace

Assignedto IP PhoneBased on

Policy

Building Classes of ServiceTypical Example of User Classes


Route Pattern Matches dialed number for external calls Points to a route list for routing Performs digit manipulation (optional)

Route List Points to prioritized route groups Performs digit manipulation (opt)

1st Choice 2nd Choice

PSTNIP WAN

Building Classes of ServiceExternal Route Construct

GK

RouteGroup 2

1st Choice

2nd Choice

Co

nfi

gu

rati

on

Ord

er

RoutePattern

RouteList

RouteGroup 1

Devices Gateways (MGCP, SCCP, H.323) Gatekeeper (H.323) Trunk (H.323, ICT, SIP)

Route Group Points to the actual devices Distribution algorithm


External Routes in Unified CMRoute Group Device Types

RouteGroup

Cat 6K T1/E1 Cisco IOS®

Gateways VG series

MGCPGateways

Dial Plan Config.Cisco Unified CM

All Cisco IOS Gateways

H.323 Gateways(H.225)

“Base” Dial Plan Configured

in Cisco IOS

Other Cisco Unified CM clusters

Inter-Cluster Trunk(Non-GK Controlled)

Cisco IOS gatekeeper

GK-ControlledTrunk

Delegates Ext.IP WAN Routing

to the GK

GKGK

Other CiscoUnified CMclusters or SIP Network

SIP Trunk

Local RouteGroup

New in 7.0!


International

National

Local

Internal

Building Classes of ServiceSingle Site Deployment Example: Composite Dial-Plan View

Internal Only

Local

National

International

All IP Phones


RouteLists

RouteGroups Devices

RoutePatterns

Calling SearchSpace


Policy

PSTNRL

PSTNRG

PSTN

<none>

9.011!#

9.1 [2-9]XX[2-9]XX XXXX

9119.911

9.[2-9]XXXXXX

9.011!

<none>


UnifiedCM

Cluster

IP WANPSTN

...

CentralSite

RemoteSites

Instruct these Phones to Use Their Local Gateway for PSTN Access

Building Classes of ServiceRouting by Location

*


Building Classes of ServiceCentralized Deployment Example: Composite Dial-Plan View

RTPPSTN

RTPPSTN

RTPInternal

RTPAllCalls

NYCInternal

NYCAllCalls

OnClusterAll IP Phones

RTP911911

9.911

RTP_PSTN9.[2–9]XXXXXX

9.1[2–9]XX[2-9]XXXXXX9.011!

9.011!#

PSTN


RouteLists

RouteGroups Devices

RoutePatterns

NYC911911

9.911

NYC_PSTN9.[2–9]XXXXXX

9.1[2–9]XX[2–9]XXXXXX9.011!

9.011!#

NYCPSTN

NYCPSTN

PSTN

RTPGateways

NYCGateways

RTPPhones

NYCPhones

Calling SearchSpace


Policy

Note that no IP trunks are shown, as only one cluster is considered.


Building Classes of ServiceDeployment Options

1. Traditional CSS Approach


Building Classes of ServiceTraditional CSS Approach for Centralized Deployments

RTPRL

RTP RGRTPinternal

RTPunrestricted

NYCinternal

NYCunrestricted

OnClusterAll IP Phone DNs

RTP911911

9.911

RTP_PSTN9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX9.011!

9.011!#

Calling SearchSpaces

PartitionsRouteLists

RouteGroups

RoutePatterns

NYC911911

9.911

NYC_PSTN9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX9.011!

9.011!#

NYCRL

RTP Gateways

NY

C D

evic

es

NYC RG

NYC Gateways

Device CSS Dictates: Class of Service Path Selection

# CSS = N x C

N = # of SitesC = # of Classes of Service

RT

P D

evic

es




2. Line/Device CSS Approach


Line

Line CSS

Partition L1

Partition L2

Partition L3

Device CSS

Partition D1

Partition D2

Partition D3Device

Resulting CSS

Partition L1

Partition L2

Partition L3

Partition D1

Partition D2

Partition D3

The resulting CSS is the concatenation of the Line CSS with the Device CSS. The <none> CSS is always implied at the end.

Building Classes of ServiceLine/Device CSS Interaction


Line Configuration

DeviceConfiguration

Building Classes of ServiceLine/Device CSS Interaction


Building Classes of ServiceLine/Device CSS Approach: Key Concept

Resulting CSS

9.011!...

Block Int’l Partition

PSTN Partition

9.011!

Line

Line CSS

Block Int’l Partition

9.011!

“Blocked” Translation PatternLine CSSSelectively BlocksUndesired Routes

(According toClass of Service)

Device CSS

Device

PSTN Partition

9.1[2-9]XX[2-9]XXXXXX

9.[2-9]XXXXXX

9.011!“Routed” Route Patterns

Device CSSAllows Access to

All External Routes


Building Classes of ServiceLine/Device CSS Approach: Translation Pattern Config


Building Classes of ServiceLine/Device CSS Approach for Centralized Deployments

Internal

Unrestricted OnClusterAll IP Phone DNs

BlockedPSTN9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX9.011!

9.011!#

CSS’s Partitions Route Lists Route Groups

NYC_PSTN

9.[2-9]XXXXXX9.1[2-9]XX[2-9]XXXXXX

9.011!9.011!#

NYCRL

All

Lin

esN

YC

Dev

ices

NYC RG

NYC Gateways

9119.911

RTPDevices

RTP_PSTN

9.[2-9]XXXXXX9.1[2-9]XX[2-9]XXXXXX

9.011!9.011!#

RTPRL

RT

P D

evic

es

RTP RG

RTP Gateways

9119.911

NYCDevices

“Blocked”Translation

Patterns

Device CSS Dictates: Path Selection

Line CSS Dictates: Class of Service

# CSS = N + C

N = # of sitesC = # of classes of service

(No Blocks)


Building Classes of ServiceComparison of the Two Methods

Site1Internal

Site1Local

Site1National

Site1International

CSS’s Partitions

Site1International

Site1National

Site1Local

OnCluster

Site1Emergency

Shared

Site2Internal

Site2Local

Site2National

Site2International Site2International

Site2National

Site2Local

Site2Emergency

SiteNInternal

SiteNLocal

SiteNNational

SiteNInternational SiteNInternational

SiteNNational

SiteNLocal

SiteNEmergency

…

1

2

N

(N*4) CSS’s ((N*4) + 2) Partitions

Traditional

Internal

Local

National

International

CSS’s Partitions

NoBlocks

LocalOnlyPSTN

OnCluster

BlockPSTN

Shared

Site1Devices Site1PSTN

…

1

(N + 4) CSS’s (N + 6) Partitions

Site2Devices Site2PSTN2Site3Devices Site3PSTN3

SiteNDevices SiteNPSTNN

NoInt’lPSTN

Line/Device


The Line/Device CSS ApproachCallForward Caveats (1 of 2)

Forwarded calls use the CallFwdxxx CSSs only; these values are not concatenated with Line or Device CSS

If forwarded calls must have unrestricted privileges, set the CallFwdxxx CSSs to the site-specific unrestricted Device CSS

If forwarded calls must be restricted to internal numbers only, set the CallFwdxxx CSSs to a single, global CSS with access only to internal partitions

If forwarded calls must have some intermediate restriction (e.g., no international calls), this approach may lose efficiency, as additional site-specific CSSs will be needed

In Unified CM 5.x and 6.x, a new CSS [Secondary Calling Search Space for CallForwardAll] has been added, allowing for CFA to have all the classes of service afforded by the line/device approach(primary CFA CSS ~ Line; secondary CFA CSS ~ Device)


The Line/Device CSS ApproachCallForward Caveats (2 of 2)

CallFwdAll CSS Activation Policy (6.x only)

1. With Configured CSS

The configured CFAll and Secondary CSS for CFAll are used

2. With Activating Device/Line CSS

The CallFwdAll Primary and Secondary CSS for Forward All automatically gets populated with the Directory Number CSS and Device CSS, respectively, for the activating device

3. Use System Default

The CFA CSS Activation Policy cluster-wide service parameter determines which Forward All Calling Search space will be used


The Line/Device CSS ApproachCall Forward All 6.x Configuration


The Line/Device CSS ApproachOther Caveats

Blocking translation patterns configured within the Line CSS must be at least as specific as the route patterns configured within the Device CSS

(Watch for the “@” wildcard, as its patterns are very specific)

AAR uses a different CSS for rerouted calls; in most cases, this CSS can be the same as the unrestricted site-specific Device CSS

Priority order between line and device is reversed for CTI route points and CTI ports; therefore, the Line/Device CSS approach cannot be directly applied to CTI devices, such as original Cisco Softphone (not IP Communicator)

In this case, it is viable only if blocked patterns are more specific than the routed ones (i.e. not relying on order of the partitions)




2. Line/Device CSS Approach

a. Optional new feature with Unified CM 7.0 which reduces number of Route Patterns configured in the system:

LOCAL ROUTE GROUP


Local Route GroupWhat It Is: Concept

Allow the site-specificity of call routing to be established by the calling device’s location (as derived from device pool)

Different endpoints in different sites would be associated with different local route groups: they can all call the same set of Route Patterns, yet the calls will be routed differently, based on the caller’s currently associated local route group

In practical terms, route patterns (i.e. patterns to off-cluster destinations) can serve all phones in the cluster, and the PATH SELECTION will be determined by the phones’ configuration.


Local Route GroupWithout It: Scalability for Centralized Deployments, Two Sites

Internal

Unrestricted OnCluster

All IP Phone DNs

BlockedPSTN

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#


JFKPSTN

JFKRL

All

Lin

esJF

K D

evic

es

JFK RG

JFK Gateways

911

9.911

JFKDevices


Patterns

(No Blocks)

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

SFOPSTN

SFORL

SF

O D

evic

es

SFO RG

SFO Gateways

911

9.911

SFODevices 9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#


Local Route GroupWithout It: Scalability for Centralized Deployments, Four Sites

Internal


All IP Phone DNs

OnCluster

All IP Phone DNs

BlockedPSTN

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#


JFKPSTN

JFKRL

All

Lin

esJ

FK

De

vice

s

JFK RG

JFK Gateways

911

9.911

JFKDevices


Patterns

(No Blocks)

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

SFOPSTN

SFORL

SF

O D

evic

es

SFO RG

SFO Gateways

911

9.911


9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

YVRPSTN

YVRRL

YV

R D

evic

es

YVR RG

YVR Gateways

911

9.911

YVRDevices 9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

YOWPSTN

YOWRL

YO

W D

evi

ces

YOW RG

YOW Gateways

911

9.911

YOWDevices 9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#


Local Route GroupWithout It: Scalability for Centralized Deployments, 1000 Sites


Local Route GroupWith It: GW Chosen by Association to Calling Device

DFWDevices


DF

W d

evic

esD

P:

DF

W_D

P

JFK RG

JFK Gateways

JFKDevices

SFO RG

SFO Gateways

SFODevices 9.1[2-9]XX[2-9]XXXXXX

US_pstn_part LocalRoutegroup

US LOCRL

DFW RG

DFW Gateways

Choice of Local Route Group based on calling

device’s Device Pool configuration

SF

O d

evic

esD

P:

SF

O_D

PJF

K d

evic

esD

P:

JKF

_DP


Local Route GroupWhat It Is: Screen Shot

Device pool is site-specific

Local route group is associated with device pool

Local route group is thus associated with all devices using a given device pool: e.g. phones, gateways


Local Route GroupWhat It Is: Screen Shot

Route lists can now refer to Local Route Groups as well as regular route group

Allows for simple local failover

In this example, calls go to the centralized US GW (in site HQ), and fallback to the local route group


Local Route GroupWith It – We Can Start from This, for Two Sites

Internal


All IP Phone DNs

BlockedPSTN

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#


JFKPSTN

JFKRL

All

Lin

es

JFK RG

JFK Gateways

911

9.911

JFKDevices


Patterns

(No Blocks)

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

SFOPSTN

SFO RG

SFO Gateways

911

9.911


9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

SFORL

SF

O d

evic

esD

P:

SF

O_D

PJF

K d

evic

esD

P:

JKF

_DP


Local Route GroupWith It – and End up with This, for Two Sites

Internal


All IP Phone DNs

BlockedPSTN

9.[2-9]XXXXXX

9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#


All

Lin

es

JFK RG

JFK Gateways

JFKDevices


Patterns

(No Blocks)

SFO RG

SFO Gateways

911

9.911


9.1[2-9]XX[2-9]XXXXXX

9.011!

9.011!#

US LDRL

US_pstn_part

LocalRoutegroup

1st p

ref

2nd

pref

HQ RG

HQ Gateways

US LOCRL

SF

O d

evic

esD

P:

SF

O_D

PJF

K d

evic

esD

P:

JKF

_DP


Building Classes of ServiceComparison Line/Device With and Without LRG

Internal

Local

National

International

CSS’s Partitions

NoBlocks

LocalOnlyPSTN

OnCluster

BlockPSTN

Shared

Site1Devices Cluser-PSTN

…

1

(N + 4) CSS’s (1 + 6) Partitions

Site2Devices2Site3Devices3

SiteNDevicesN

NoInt’lPSTN

w/ LRG

Internal

Local

National

International

CSS’s Partitions

NoBlocks

LocalOnlyPSTN

OnCluster

BlockPSTN

Shared

Site1Devices Site1PSTN

…

1

(N + 4) CSS’s (N + 6) Partitions

Site2Devices Site2PSTN2Site3Devices Site3PSTN3

SiteNDevices SiteNPSTNN

NoInt’lPSTN

w/o LRG


Line/Device CSS Approach + LRGBenefits Summary

200 Sites; Four Classes of Service; Six Unique Route Patterns

Traditional Approach:

# of Part = 802

# of CSS = 800

# of RP = 1200

Line/Device Approach:

# of Part = 206

# of CSS = 204

# of RP = 1200

Line/Device with LRG:

# of Part = 7

# of CSS = 204

# of RP = 7


Agenda

Call Routing Basics



Building Class of Service SRST (COR)

Alternate Routing


Other Tools


Sydney

Classes of Service for Unified SRST (COR)Rationale

When WAN connection is lost, Cisco Unified CM classes of service are also lost all remote phones gain unrestricted PSTN access

Class of Restriction (COR) configuration on branch router allows preservation of classes of service in Unified SRST mode

CiscoUnified CM

Cluster

Central Site

IP WAN

PSTN

Unified SRST Router

Unrestricted

Internal

+ Local

InternalOnly

Class of Service

CORconfig


Classes of Service for Unified SRST (COR)COR Logic (1)

corlist incoming c1

Member A

Member B

Member C

dial-peer voice 2 pots

corlist outgoing c2

Member A

Member B


corlist outgoing c3

Member A

Member B

Member D

Call 100

Choose OutgoingDial-Peer Based onMatching Pattern

1Check All the “Locks” of the Outgoing Corlist Against the “Keys” of the Incoming Corlist

2

Incoming Corlist Has All the Needed “Keys”

(i.e., Outgoing Corlist Is a Subset of Incoming);

The Call Can Be Completed

3

dial-peer voice 1 voip

destination-pattern 1..



Classes of Service for Unified SRST (COR)COR Logic (2)

Call 200

Choose OutgoingDial-Peer Based onMatching Pattern

1

Incoming Corlist Is Missing Some “Keys” (i.e., Outgoing

Corlist Is Not a Subset of Incoming Corlist);

The Call Cannot Be Completed

3

STOPSTOP

?

corlist incoming c1

Member A

Member B

Member C


corlist outgoing c2

Member A

Member B


corlist outgoing c3

Member A

Member B

Member D

dial-peer voice 1 voip



Check All the “Locks” of the Outgoing Corlist Against the “Keys” of the Incoming Corlist

2


Classes of Service for Unified SRST (COR)How to Recreate “Partitions” and “CSSs”

call-manager-fallback

2001

2002

Outgoing COR Lists (“Partitions”)Incoming COR Lists (“CSSs”)

OtherPhones


corlist outgoing EmPt

Member Emergency

destination-patt 911


corlist outgoing LocalPt

Member Local

destination-patt 9[2-9]......


corlist outgoing IntlPt

Member Intl

destination-patt 9011T


corlist outgoing LDPt

Member LD

destination-patt 91[2-9]..[2-9].....

cor incoming InternalCSS default

Member Emergency

cor incoming 1 LocalCSS 2001

Member Emergency

Member Local

cor incoming 2 IntlCSS 2002

Member Emergency

Member Local

Member LD

Member Intl


Classes of Service for Unified SRST (COR)SRST COR Limitations

Maximum number of “cor incoming” statements under call-manager-fallback is 21 (including default) in Unified SRST v4.1 [Cisco IOS 12.4(15)T]

If “manager” phone DNs are not consecutive and the Unified SRST site is relatively large, this may become an obstacle to establishing appropriate classes of service

If the cor incoming ‘default’ command is not used, a device/ DN with no corlist assignment is essentially unrestricted

CME-as-SRST “cor incoming” statements configured under the ephone-dn; no ‘default’ command available

(CME = Call Manager Express)


Agenda

Call Routing Basics




Alternate Routing


Other Tools


Cisco Unified CM

Router/GW

Ext.1000

Ext.1001

Gatekeeper

Dial PlanThe “IP Routing” of IP Telephony

+1 408 5264000

Cisco Unified CM Routes Two Basic Call Types:

On-Cluster Calls: Destination Directory Number (DN) is registered with Cisco Unified CM. DNs are considered “internal” routes.

Off-Cluster Calls: Destination Number is not registered with Cisco Unified CM. Route Patterns are configured to allow for “external” routes.

Alternate routes: Allow On-Cluster and Off-Cluster calls to attempt alternate paths to destination (e.g.: IP WAN not available, go through PSTN)

9.1408XXXXXXXRoute

Pattern

GKRemoteCisco

Unified CM

PSTN

IP WAN


Alternate RoutingBasics

Mechanisms that allow Unified CM to route a call through an alternate path if the preferred path is not available

e.g. IP path not usable/not enough bandwidth/phone unregistered—then reroute the call through the PSTN

Alternate Routing is not triggered on events happening mid-call

Alternate Routing for on-cluster routes:

Automated Alternate Routing (AAR) for calls to on-cluster IP endpoints when there is not enough bandwidth

Call Forward Un-Registered (CFUR) for calls to IP endpoints when the destination is unreachable (e.g. a remote site in SRST)

Alternate Routing for off-cluster routes:

The Route List/Route Groups construct provides alternate routing for external routes


Alternate Routing for Internal RoutesInternal Routes in Unified CM

Endpoints Applicationswith Media

Non-mediaServices

IP Phones

911 (Emergency Responder)

Software Phone

Call Park

Analog Phones (FXS ports) IVR

Voice Messaging

TranslationPatterns

On

-clu

ster

des

tin

atio

ns

Auto-Attendant


Alternate Routing for Internal RoutesCall Admission Control (CAC) without AAR

San FranciscoLocation: SFRegion: SF

Phone ADN: 2222

PSTN

IP WAN

Phone BDN: 1111

New YorkLocation: NYRegion: NY

PhoneA: Region SF; Location SFPhoneB: Region NY; Location NYSF-NY Codec: G.729, ergo 24kSF Location Avail BW: 24k - OK!NY Location Avail BW: 1k - NO!

Call From: DN 2222Call To: DN 1111

CALL NOT ALLOWED!

Bandwidth Not Available!

SF_GW

User Dials 1111 Unified CMCluster

NY_GW




Alternate Routing for Internal RoutesAAR Components

Phone ADN: 2222

PSTN

IP WAN

Phone BDN: 1111

SF_GW

Unified CMCluster

NY_GW

2) AAR Destination Mask Or External Mask configured on DN (ex., 212 555 XXXX)3) AAR Group configured on Device Pool, Device, or DN (ex., USA)

4) AAR Group configured on Device Pool, Device, or DN (ex., USA)6) AAR CSS configured on Device or DN

1) AAR Enabled for Cluster5) AAR Group ‘Dial Prefixes’ configured (ex., 91)


Alternate Routing for Internal RoutesAAR Decision Tree

External MaskOn Destination

Set?

AARConfigured?

AAR Group Configured?

Prefix digits from AAR Group

Table to AAR destination

Deny the call

NO

YESYES

Route the Call using the Calling device’s

AAR CSS

AAR DestinationMask Set?

AAR VoicemailBox Checked?

YES

NO NO

YES

NO

NO

YES

YES




Alternate Routing for Internal RoutesCall Admission Control (CAC) with AAR

Phone ADN: 2222

PSTN

IP WAN

Phone BDN: 1111

PhoneA: Region SF; Location SFPhoneB: Region NY; Location NYSF-NY Codec: G.729, ergo 24kSF Location Avail BW: 24k - OK!NY Location Avail BW: 1k - NO!

Call From: DN 2222Call To: DN 1111

CALL NOT ALLOWED!


SF_GW

User Dials 1111 Unified CMCluster

NY_GW

WAIT! AAR IS ENABLED!





Phone ADN: 2222

PSTN

IP WAN

Phone BDN: 1111


SF_GW

Unified CMCluster

NY_GW

DN 1111’s External Phone Number Mask = 212555XXXX=> New Destination = 2125551111

Within AAR Group ‘USA’, Prefix Dialing = 91=> New Destination = 912125551111

AAR CSS of PhoneA Contains RP 9.1[2-9]XX[2-9]XXXXXX which Points to SF_GW Call Is Now Attempted From 2222, To 912125551111, Via the SF_GW

DN’s External Mask: 212 555 XXXXAAR Group: USA

DN’s AAR Group: USADevice AAR CSS: Unrestricted





Phone ADN: 2222

PSTN

IP WAN

Phone BDN: 1111


SF_GW

Unified CMCluster

NY_GW

Call From: DN 2222Call To: RP 912125551111

User Originally Dialed 1111

PhoneA: Region SF; Location SFSF_GW: Region SF; Location SFSF-SF Codec: G.711, ergo 80kSame Location: CAC OK!PROCEED!

121255511115551111

Place Call in SF

New Call in NY


Alternate Routing for Internal RoutesWithout Call Forward Unregistered (CFUR)

IP WAN

PSTNDallas San Jose

Prior to CFUR, Call Forward Busy (CFB) used when phone’s unregistered

Issue: Phone is still able to receive calls via PSTN

HQ

Unified CM cluster

Call2000

1

Call fwded to5001 (vmail)

2

SRST Mode

CFB: 5001 (vmail)

DID: 4085262000

DN: 2000

CFB CSS: Internal

vmail

3


Alternate Routing for Internal RoutesWith CFUR (Unified CM 4.2 and 6.x)

Reroutes calls to unregistered DN’s using number specified in “Call Forward Unregistered” (CFUR) field

Number in CFUR field needs to include PSTN access codes

If leave CFUR CSS as <None>, calling party’s CSS is used(Calling phone’s class of service must allow call)

IP WAN

PSTN

HQ

Unified CM cluster

Call2000

1

Call fwded to914085262000

2

3CFUR: 914085262000

DID: 4085262000

DN: 2000

CFUR CSS: <None>CSS: Unrestricted

DN: 2000

SRST Mode

Dallas San Jose


Alternate Routing for Internal RoutesCFUR Caveats

CFUR Destination number same irrespective of calling phone’s PSTN dialing requirements based on calling site

An issue for previous example if say, calling phone was in Europe:the dialed number should be 0 00 1 408 526 2000

CFUR CSS same irrespective of calling phone’s dial plan; i.e., not able to use different GW based on calling site

As noted, if CFUR CSS is left to <none>, calling phone’s CSS is used and the Calling phone’s class of service must allow call

Not a Protected Feature!

Beware of Loops: What happens if phone is “merely” un-registered (site not in SRST-mode)?

GWs should not be allowed to place calls to number ranges that deliver calls to the GW itself; the next slide illustrates this issue



CFUR is invoked whenever DN is unregistered, including when EM is logged out or the phone is unplugged

CFUR CSS cannot be expected to be able to avoid loops in this situation

IP WAN

PSTN

HQ

Unified CM cluster

Call2000

1


2

CFUR: 914085262000

DID: 4085262000

DN: 2000

CFUR CSS: DAL_GW

Call for20004

3


5

Dallas San Jose



Set service parameter to 1 (or 2) to limit loops (value may need to be higher if forwarding “chains” are used for voicemail or other applications)

When looping call is dropped, caller hears fast-busy


Route Pattern Matches dialed number for external calls Points to a route list for routing Performs digit manipulation (optional)

Route List Points to prioritized route groups Performs digit manipulation (opt)


PSTNIP WAN

External Routes in Unified CMOverall Structure

GK

RouteGroup 2

1st Choice

2nd Choice

Co

nfi

gu

rati

on

Ord

er

RoutePattern

RouteList

RouteGroup 1

Devices Gateways (MGCP, SCCP, H.323) Gatekeeper (H.323) Trunk (H.323, ICT, SIP)

Route Group Points to the actual devices Distribution algorithm


Alternate Routing for External RoutesThe Route List/Route Group Construct

New York

User Calls“526-4000”


Route Pattern“52.XXXXX”

Route List“SJ”

Route Group“NY-PSTN”

Route Group“SJ-IPWAN”

Route Pattern Match No Digit Manipulation

1

Discard Pre-dot (“52”)Point to Remote CM viaInterCluster Trunk + GK

3a

“64000” Sent over IP WAN

to SJ Cisco Unified CM

4a

Prepend “1408” Point to LocalPSTN Gateway

3b

1 (408) 526-4000 Sent over PSTN

to San Jose

5b

Select Route Group Based on Priority

2

DID: (408) 526-4000DN: 64000

San Jose

PSTNIP WANGK

1st Choice

2nd

Choice

Select Gateway Based on Priority

4b


Agenda

Call Routing Basics




Alternate Routing


Other Tools


Tail-End Hop-Off (TEHO)What Is It?

San Jose

GK

Gatekeeper

CiscoUnified CMCluster 1

New York

CiscoUnified CMCluster 2

Seattle

IP WAN

San Jose PSTN

Seattle PSTN

New York PSTN

1 2

Calls to a Remote PSTN Number Use the IP WAN and Terminate at theGW Closest to the Destination

Within a Cisco Unified CM Cluster

Across Cisco Unified CM Clusters

1

2

Local Call Local Call

Calls9 1 408555123

4

(408) 555-1234 (646) 555-6789Calls

9 1 646

5556789


Tail-End Hop-Off (TEHO) Intracluster: Seattle to San Jose

Seattle

User Calls914085551234

1st Choice

2nd Choice

PSTN

Route Pattern91408[2-9]XXXXXX

Route ListSEA-1st-RL

LocalRoute Group

Route GroupSJ-RG

Route Pattern Match No Digit Manipulation

1

Route Through SJ GWAs a Result Call Is LocalUnified CM Strips off ‘9’

CAC May Reject Call

3a

SJ Gateway PresentsCall to PSTN in SJ

4a

Backup PathUse LRG

CAC Not Required

3b

GW Strips ‘9’Then Presents Call

to PSTN in SEA

4b

Select Route Group Based on Priority

2

(408) 555 1234San Jose

SJ GW Sea GW


Tail-End Hop-Off (TEHO) Intracluster: Route Patterns for Seattle

Route Pattern9.1 408 [2-9]XX XXXX

PSTN

Route List“SJ-1st-RL”

Route Group“SJ-RG”

San JoseGateway

PSTN

Route List“US-RL”

LocalRoute Group

SeattleGateway

Route Patterns911, 9.911

9.[2-9]XX XXXX9.1 [2-9]XX [2-9]XX XXXX

9.011!, 9.011!#

1st choice

2nd choice


SEA_International

SEA_National

SEA_Local

Tail-End Hop-Off (TEHO) Intracluster: Composite Dial Plan for Seattle

SEARL

SEARG

Internal_SEA

Local_SEA

National_SEA

International_SEA

9.[2-9]XXXXXX

9.011!

9.011!#

PSTN

CSS Assigned

to IP PhoneBased on Policy andGeography


RouteLists

RouteGroups Devices

SJ-SEARL

SJRG

PSTN

InternalIP Phones, VM

SEA_911911

9.911

9.1 408 [2-9]XX XXXX

1st Choice

2nd Choice

9.1 [2-9]XX [2-9]XX XXXX

San JoseGateway

SeattleGateway


Step 2

Tail-End Hop-Off (TEHO) Intercluster: San Jose to New York

GatekeeperSan JoseCisco

Unified CMCluster

New YorkCisco

Unified CMCluster

IP WAN

(646) 555-6789Calls9 1 646555678

9

San JoseGateway

New YorkGateway

GK

GK-ControlledTrunk

SJ Gateway

Route Pattern9.1 646 [2-9]XX XXXX

1st choice

2nd choice

Step 1

gatekeeper zone prefix NY 1646.......

Step 3

NY Gateway

Route Pattern1 646 [2-9]XX XXXX


SJ_International

SJ_National

SJ_Local

Tail-End Hop-Off (TEHO) Intercluster: Composite Dial Plan for San Jose

SJ-SJRL

SJ-RG

Internal_SJ

Local_SJ

National_SJ

International_SJ

9.[2-9]XXXXXX

9.011!

9.011!#

PSTN

CSS Assigned

to IP PhoneBased on Policy andGeography


RouteLists

RouteGroups Devices

SJ-WANRL

WAN-RG


SJ_911911

9.911

9.1 646 [2-9]XX XXXX

1st Choice

2nd Choice

9.1 [2-9]XX [2-9]XX XXXX

San JoseGateway

IP WANGK

Gatekeeper


NY_TEHO

Tail-End Hop-Off (TEHO) Intercluster: Dial Plan for New York

Note: To Avoid Routing Loops, Do Not Include Partitions That Contain IP WAN Routes in the “From_IP_WAN” Calling Search Space

NY-NYRL

NY-RG

From_IP_WAN

PSTN

IncomingCalls fromGatekeeper


RouteLists

RouteGroups Devices


9.1 646 [2-9]XX XXXX

New YorkGatewayGK


Agenda

Call Routing Basics




Alternate Routing


Other Tools


Other ToolsThe Options

In Unified CM, under the Call Routing menu, there are many advanced Dial-Plan features

Unified CM Administration Guide and Features and Services Guide can provide more details

http://cisco.com/en/US/partner/products/sw/voicesw/ps556/prod_maintenance_guides_list.html

We will go into some detail on:

Translation Patterns

Time of Day Routing

Hunt Groups

Call Coverage


Translation PatternsThe Basics

Looks like a route pattern, allows digit manipulation

Instead of sending calls outside via a route list, forces second lookup in Cisco Unified CM, using a (possibly different) calling search space

Translates “0” to2001 and forces a

second lookup

Translation Pattern

Ext. 2001

User dials“0” to reach

operator0 2001


Translation PatternsCall Flow

Looks like a route pattern, allows digit manipulation

Instead of sending calls outside via a route list, forces second lookup in Cisco Unified CM, using a (possibly different) calling search space

Translation Patterns are “Urgent Priority” by nature: as soon as they match, the inter-digit timer is aborted, and the best match pattern is selected to route the call

InternalCSS


Translation PatternTransforms “0” to2001 and ForcesSecond Lookup

Dials “0”to ReachOperator

OperatorCSSTranslations

0 [Transform Mask: 2001][ CSS: InternalCSS]

Delivers “2001”

AllPhones

All IP Phones


HuntPilot

HuntList

Hunt Pilot Matches dialed number for call coverage Performs digit manipulation Points to Hunt List for routing

Hunt List Chooses path for call routing Points to prioritized Line Groups

First Choice

SecondChoice

Line Group Performs Digit manipulation Points to actual extensions

LineGroup II

LineGroup I

Endpoints IP Phones Voicemail Ports

Co

nfig

ura

tion

Ord

er

IP Phones Voicemail

Call Coverage ExampleHunt Group Construct


Call Coverage ExampleTime of Day Partitions

1. Create hourly Time Periods that repeat ‘week from’ or ‘year on’

2. Create a Time Schedule to include selected Time Periods

3. Configure a Partition with the configured Time Schedule [default Time Schedule for partitions is <none>]

This partition (and the Internal Numbers assigned to this partition) will now only remain active during the Time of Day configured in the Time Schedule


OrlandoUnified CM

Cluster

IP WAN

SJC IP PhonesSan Jose Site

Hunt List

Line Group

MCO IP Phones

Hunt Pilot 1DN 8000

MCOPartition

Time Period0800 to 1400

Mon-Fri


Sat

Time PeriodNo Business

Jul 4th

MCO (EST)Time Schedule

Hunt List

Line Group

SJCPartition


Mon-Fri


Sun

Time PeriodNo Business

Jul 4th

Hunt Pilot 2DN 8000

SJC (PST)Time Schedule

Call Coverage ExampleCall Flow

Unified CM routes the callbased on time of the day

Unified CM routes the callbased on time of the day

Call coming in at 9 am PST onSunday for 8000distributed to SJC Phones

Call coming in at 9 AM EST onSaturday for 8000distributed to MCO Phones


Enterprise Dial Plan FundamentalsParts List


Enterprise Dial Plan FundamentalsGeneral Recommendations

Think Long Term!

Short, Standard naming conventions

Keep it simple

BRKVVT-3000: Advanced Dial Plan Design


Q and A


Recommended Reading

Continue your Cisco Live learning experience with further reading from Cisco Press®

Check the Recommended Reading flyer for suggested books

Available Onsite at the Cisco Company StoreSM


Complete Your Online Session Evaluation

Give us your feedback and you could win fabulous prizes. Winners announced daily.

Receive 20 Passport points for each session evaluation you complete.

Complete your session evaluation online now (open a browser through our wireless network to access our portal) or visit one of the Internet stations throughout the Convention Center.

Don’t forget to activate your Cisco Live Virtual account for access to all session material, communities, and on-demand and live activities throughout the year. Activate your account at the Cisco booth in the World of Solutions or visit www.ciscolive.com.



Backup Slides


Classes of Service for Unified SRST (COR)Step-by-Step Guidelines

Define meaningful tags (Emergency, Local, LD, Intl)

!dial-peer cor custom name EMERG name LOCAL name LD name INTL!

!dial-peer cor custom name EMERG name LOCAL name LD name INTL!




Define “simple” COR lists (with only one tag as a member) to be used as “partitions”

!dial-peer cor list EMERG member EMERG!dial-peer cor list LOCAL member LOCAL!dial-peer cor list LD member LD!dial-peer cor list INTL member INTL!

!dial-peer cor list EMERG member EMERG!dial-peer cor list LOCAL member LOCAL!dial-peer cor list LD member LD!dial-peer cor list INTL member INTL!





Assign the “partitions” as outgoing COR lists to the appropriate POTS dial peers

!dial-peer voice 911 pots corlist outgoing EMERG dest-patt 911 port x/x forward-digits 3!dial-peer voice 7 pots corlist outgoing LOCAL dest-patt 9[2-9]...... port x/x forward-digits 7!

!dial-peer voice 911 pots corlist outgoing EMERG dest-patt 911 port x/x forward-digits 3!dial-peer voice 7 pots corlist outgoing LOCAL dest-patt 9[2-9]...... port x/x forward-digits 7!






Define COR lists to be used as “CSS” (containing a subset of the tags as members)

!dial-peer cor list RESTR member EMERG!dial-peer cor list LOCALCSS member EMERG member LOCAL!dial-peer cor list UNRESTR member EMERG member LOCAL member LD member INTL!

!dial-peer cor list RESTR member EMERG!dial-peer cor list LOCALCSS member EMERG member LOCAL!dial-peer cor list UNRESTR member EMERG member LOCAL member LD member INTL!






Define COR lists to be used as “CSS” (containing a subset of the tags as members)

Assign the “CSS” as incoming COR lists to the different phone numbers under the SRST commands

!call-manager-fallback cor incoming RESTR default cor incoming LCLCSS 1 2101 - 2149 cor incoming UNRESTR 2 2150 - 2159!

!call-manager-fallback cor incoming RESTR default cor incoming LCLCSS 1 2101 - 2149 cor incoming UNRESTR 2 2150 - 2159!


Other ToolsCall Forward No Coverage

In the Hunt Pilot configuration settings, ‘Use Personal Preferences Destination’ fields are available to enable the Call Forward No Coverage (CFNC) settings for the original called number that forwarded the call to the hunt pilot

Example: A IP Phone with extension 1234 has call forwarded to HuntPilot 3456 and the hunt pilot members don't answer, then if the personal preferences box is checked on huntpilot then the call forwards to the no coverage number configured on the 1234 extension


Call Admission Control (CAC)Why Is It Needed?

IP WAN

Router/

Gateway

Unified CM

PSTN

Circuit-Switched Networks

Packet-Switched Networks

PBX

Physical

Trunks

STOP

IP WAN

Link

IP WAN link configured with Low Latency Queuing (LLQ)

Provisioned for 2 calls (equivalent to 2 “virtual” trunks)

Third Call

Rejected

No physical limitation on IP links so 3rd call can go through.

Voice quality of ALL calls will degrade.

Call Admission Control blocks 3rd call


Cisco Unified CM Static Locations Concept

Prevent WAN link over-subscription by limiting voice bandwidth

Assign bandwidth limit for voice per location

(G729 = 24Kbps, G711=80Kbps)

Location1 makes a G729 call over WAN to the Central Site

IP WANPSTN

CentralSite

Location 1 Location 2

<Hub_None>

Location

RemoteSites

1

Max BW = 24 kbpsAvail BW = 24 kbps



Cisco Unified CM Static Locations Concept

Prevent WAN link over-subscription by limiting voice bandwidth

Assign bandwidth limit for voice per location

(G729 = 24Kbps, G711=80Kbps)

Location1 makes a G729 call over WAN to the Central Site

Location 1 attempts a 2nd G729 call, but Locations-based CAC blocks the call

When resources are insufficient, user hears a fast-busy tone and a message is displayed on the phone

IP WANPSTN

Location 1 Location 2

<Hub_None>

Location

12



STOP

CentralSite

RemoteSites


Extension Mobility Functionality

Extension Mobility (EM) is an application that allows a user to temporarily take ownership of a phone

User-specific device profile is configured for each EM user and applied to the phone a user logs in to

User can log in to any phone within a Unified CM cluster that has been enabled for EM

Device Profile62796

62798

HomeSue Mobile

62796


HQ

RTP (home) SJC (visiting)

PSTN

Dials9-1-303-555-1234

Dials9-1-303-555-1234

Denver(303)

555-1234

Mobility and Mobility ApplicationsMobile User without Device Mobility Feature

PSTN call uses “home” gateway

Location CAC is unaware of the call

G.711 CODEC uses more WAN bandwidth

“Home” site’s Media Resources are selected (e.g. RTP conf bridge could be used)

AAR would be anchored on the home gateway

G.711


Mobility and Mobility ApplicationsDevice Mobility Feature (Unified CM 4.2 and 6.x)

Determines that the device has moved to new location based on the device’s IP subnet

Dynamically associates “roaming” device pool to devices that move to a different location

Determines the following parameters:

Location

Region

Device Calling Search Space

AAR configuration

SRST reference

MRGL


SJC

Mobility and Mobility Applications Device Mobility—User Gets New Information


HQ

RTP (home) SJC (visiting)

Dials9-1-303-555-1234

Dials9-1-303-555-1234

Denver(303)

555-1234

Mobility and Mobility Applications Device Mobility—Resolution

PSTN call uses “roaming” gateway

Location CAC is aware of the call

WAN bandwidth is not consumed

Proper Media Resources are selected

AAR outgoing calls would be sourced on the new site’s GW; incoming calls will fail (as they should)

PSTN

BRKVVT-2008_c2© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 1 Enterprise Dial-Plan Fundamentals BRKVVT-2008.

Documents

cisco systems

cisco public brkvvt

cisco unified srst

dial plan attendees

enterprise dialplan

international dial plan

tools slide

external alternate routing