cucm7-dial plan update

© 2008 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 1

허용준, 시스코 시스템즈 코리아

CUCM 7 New FeaturesDial Plan update


The new dial plan functions

Looking at the new features from the bottom up:

local route group

+ sign support

calling / called number transformations

GW incoming call prefixing based on numbering plan


Local route groupa scalability gem*and*an enabler of features


Local Route Groupwithout it – we can start from this, for 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!#

CSS’s Partitions Route Lists Route Groups

JFKPSTN

JFK

RL

All L

ines

JF

K D

evic

es

JFK RG

JFK Gateways

911

9.911

JFKDevices

“Blocked”

Translation

Patterns

(No Blocks)

9.[2-9]XXXXXX

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

9.011!

9.011!#

SFOPSTN

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!#

SFORL


Local Route Groupwith it – and end up with this, for 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!#


All L

ines

JF

K D

evic

es

JFK RG

JFK Gateways

JFKDevices

“Blocked”

Translation

Patterns

(No Blocks)

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!#

US LD

RL

US_pstn_part

Local

Route

group2nd

pref

HQ RG

HQ Gateways

US LOC

RL

Route group chosen as

per device pool of calling

device


Local Route Groupwith it – key take aways

We go from route patterns that are site-specific to patterns that are type-specific.

– e.g.: local, national, international

We now group by dial plan domains

–e.g.: US dialing habits of 9 plus seven, 9 plus ten, 91 plus ten, 9011 plus ???, 911, 9911). I could not add a French site to the preceding example without creating patterns for 112, 0112, 00[1-6]XXXXXXXX, 000!, 000!#

we get site-specific failover for “free” on long distance patterns

we now have much fewer things to configure per site


+ sign supportenabling globalised number routing

+ sign supportenabling globalised number routing


+ Sign Supportwhat it is: concept

E.164 support includes the use of + to “wildcard” international access codes.

+33144522919 is the E.164 (global) representation of City Hall in the 19th

arrondissement in Paris. It is accessed by different localised methods:

–In Paris, send 0144522919 to an “intra-France” gateway

– In London, send 0033144522919 to an international gateway in the UK

– In San Francisco, send 01133144522919 to an international gateway in the US

–From “anywhere”, by sending +33144522919, into a network that can digest it. E.g.: most mobile GSM carriers, and now, our UC system 7.0

Supporting the + sign allows UCM-based systems to:

–Route calls based on a directory’s entry using the E164 notation

•Either in a dual mode phone or click-to-dial from softclient

–Store numbers in a non-site specific form in Extension Mobility profiles

–Allows CallForwardAll destinations to use Local Route Groups

–Allows AAR destinations to be globalised, thereby simplifying AAR configuration

–… and many other things.

Phones do not support the + sign for keypad entry, but support the + sign in display and missed/received calls menus.

Let’s look at some screen shot examples.


+ Sign supportfrom the phones: allowing globalised AND localised TUI

Internal

OnCluster

All IP Phone DNs

French_loc2glob_part

0.112, pre-dot

00.XXXXXXXXX, pre-dot, prepend +33

000.!, pre-dot, prepend +

000.!#, pre-dot, prepend +,

strip trailing #


Fra

nce-w

ide

Nic

e D

evic

es

NCE RG

NCE Gateways

NCEDevices

“Blocked”

Translation

Patterns

Unrestricted(No Blocks)

Pari

s D

evic

es CDG RG

112

CDGDevices

+33XXXXXXXXXX

+!

French

LD RL

French_pstn_part

Local

Route

group

2nd

pref

HQ RG

HQ Gateways

French

LOC RL

French CoR blocked

00[1-6]XXXXXXXX

000!

00033[1-6]!

CDG Gateways

FrenchE164Routing

+33[1-6]!

+[0-4]!

+[5-9]!

Localy-significant translation patterns globalise the user

input


+ Sign supportfrom the phones: localised TUI may require extra effort

Internal

OnCluster

All IP Phone DNs

NANP_loc2glob

9.911, pre-dot

9.1[2-9]XX[2-9]XXXXXX, pre-dot, prepend +


9011.!#, pre-dot, prepend +


NA

NP

-wid

eO

tta

wa

De

vic

es

YOW RG

YOW Gateways

YOWDevices

“Blocked”

Translation

Patterns


Rim

ou

sk

i D

evic

es YXK RG

911

YXKDevices

+1XXXXXXXXXX

+!

NANP

LD RL

NANP_pstn_part

Local

Route

group

2nd

pref

HQ RG

HQ Gateways

NANP CoR blocked

9[2-9]XXXXXX

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

Watch precision of the match!!

91[2-9]XX[2-9]XXXXXX

YXK Gateways

NANPE164Routing

Depends on whether you want

to centralise egress for national

numbers

+1[2-9]XX[2-9]XXXXXX

+[0234]!

+[5-9]!

YXK_loc2glob

9.[2-9]XXXXXX, pre-dot, prepend +1418

YOW_loc2glob

9.613[2-9]XXXXXX, pre-dot, prepend +1

NANP

LOC RL

Localy-significant translation patterns globalise the user

input

Localy-significant translation patterns

for 7 and 10 digit local dialing


+ Sign supportfrom the phones: Tail End Hop Off is simple

Internal

OnCluster

All IP Phone DNs

NANP_loc2glob

9.911, pre-dot

9.1[2-9]XX[2-9]XXXXXX, pre-dot, prepend +


9011.!#, pre-dot, prepend +


NA

NP

-wid

eO

tta

wa

De

vic

es

YOW RG

YOW Gateways

YOWDevices

“Blocked”

Translation

Patterns


Rim

ou

sk

i D

evic

es

YXK RG

+55!

YXKDevices

+1XXXXXXXXXX

+!

NANP

LD RL

NANP_pstn_part

Local

Route

group

2nd

pref

HQ RG

HQ Gateways

NANP CoR blocked

9[2-9]XXXXXX

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

91[2-9]XX[2-9]XXXXXX

YXK Gateways

NANPE164Routing

+1[2-9]XX[2-9]XXXXXX

+[0234]!

+[5-9]!

YXK_loc2glob

9.[2-9]XXXXXX, pre-dot, prepend +1418

YOW_loc2glob

9.613[2-9]XXXXXX, pre-dot, prepend +1

NANP

LOC RL

BRZ

TEHO RL

BRZ RG

BRZ Gateways


calling / called number transformations:

bridging local and global forms


calling / called number transformationswhat it is: concept, slide 1 of 2

Calls presented to a phone or a gateway typically require the calling and the called party numbers be adapted to the local preferences/requirements of

–The user receiving the call

–The gateway through which the call is routed

–The network to which the call is routed

Calls received from an external network (e.g.: the PSTN) typically present calls in a localised flavor. We can now adapt the received call based on:

–The numbering plan presented by the network for a specific call

–The called/calling number delivered into the UC system by the gateway

–Combining the two elements above, we can globalise the number upon entry


calling / called number transformationswhat it is: concept, slide 2 of 2

The calling number may need to be:

–Left in the global form. E.g.: +1 408 902 3574. GSM networks may accept (or even require) this form

–Changed to the locally-significant on-net abbreviated form. E.g.: 23574 if the called party is co-located with me.

–Changed to an enterprise-significant form. E.g.: 89023574 if I call someone in say, RTP’s Cisco site, on-net.

–Changed to a nationally-significant form if I call a pizza shop in New York. E.g.: 408 902 3574

–Changed to a Brazilian-significant form if I call a shop in Rio: 0014089023574

The called number may need to be adapted to enter another network with the correct numbering type and the correct numbering form.

–If I call +33144522919 using a US Gateway, I may leave the number intact if the Gateway AND the carrier support the + sign.

–I may need to change the number to 011 33144522919 and set the numbering type to international

–If I route the call through a French gateway, I may need to change the called number to 0144522919, and set the numbering type to National


Calling party transformations base scenario

UC

Johannes in Hamburg+4940691234567

FrankfurtCity Code: 69

HamburgCity Code: 40

GermanyCountry Code: 49

Service ProviderPOP in Hamburg

United FeestdomCountry Code: 693

gateway is physicallylocated in Hamburg

AB

CRaymondburgCity Code: 05

Tobias in Frankfurt+49691234567


Calling Party Transformations globalise on ingress – Incoming calling party settings

UCFrankfurt

City Code: 69Hamburg

City Code: 40





AB


Call A:Calling Number: 693056412Type: SubscriberCall B:Calling Number: 693056412Type: NationalCall C:Calling Number: 693056412Type: International

•We need rules applied to the gateway to globalise the calling number on ingress•There rules need to take into account:

•the digits received•the number type

•Next screen looks at sample rules for German gateways


For a Hamburg gateway (our case):

For a Frankfurt gateway (for the sake of argument):

These settings can be applied at the gateway, device pool or service parameter level, in order of precedence.




UCFrankfurt


City Code: 40





AB



•We need rules applied to the gateway to globalise the calling number on ingress•There rules need to take into account:

•the digits received•the number type

•Next screen looks at sample rules for German gateways



New in 7.1: Incoming calling party settings now allow for using Calling Party

Transformation Patterns to manipulate the calling party number when calls enter

the system from gateways. One CgPTP CSS is available for each numbering

type. Note: all calls are tagged with numbering type “Unknown” on SIP

Gateways and trunks. This allows digit manipulation to be based on regular

expressions, for more flexible matching.


Calling Party Transformations globalise on ingress

UCFrankfurt


City Code: 40





AB



•We now have globalisation rules for the Hamburg gateway•This allow us to process all calls on the presumption that the calling number is in a global format.

Call A:Calling Number: +4940693056412Type: internationalCall B:Calling Number: +49693056412Type: internationalCall C:Calling Number: +693056412Type: international


Calling Party Transformations When calls are presented to endpoints

UC

Johannes in Hamburg+4940691234567


If the caller is from Hamburg, show me the caller as a local incoming call. If from elsewhere in Germany, show me the caller as a National incoming call. If the caller is from another country, show me the call with the appropriate international prefix.

Tobias in Frankfurt+49691234567

Same for me, except I am in Frankfurt! So all the same rules apply, but a local call for me comes from Frankfurt, and a call from Hamburg is a National call.

•We need rules applied to the destination endpoints (e.g.: the phones)•There rules must assume some common starting point: a global format for any call•Next slides show sample config

Call A:Calling Number: +4940693056412Type: internationalCall B:Calling Number: +49693056412Type: internationalCall C:Calling Number: +693056412Type: international


Calling Party TransformationsCalling party transformation patterns for Hamburg

This one should be part of the calling party transformation pattern CSS of Hamburg devices only.


Calling Party TransformationsCalling party transformation patterns for Frankfurt

This one should be part of the calling party transformation pattern CSS of Frankfurt devices only.


Calling Party TransformationsCalling party transformation patterns for German sites

This one should be part of the calling party transformation pattern CSS of all German sites.


Key Takeaways

The Key Takeaways of this presentation are:

Dial Plans based on globalized routing of the called and calling numbers simplify configuration

7.X allows users to retain a localized user experience while benefiting from globalized (universal) routing

Even Canada/US-only deployments can benefit

7.X’s dial plan features support mobility better than ever

7.1 supports toll bypass avoidance mechanisms required by some countries, through logical partitioning


Additional Resources

You can find additional information about the topics and products covered in this session at the following links:

•www.cisco.com/go/srnd (for the latest UC SRNDs)

Contact presenter’s team at [email protected] for dial plan concerns with the UC system or with its SRND

LP references: EDCS-621754 and EDCS-621755.

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

mailto:[email protected]



cucm7-dial plan update

Documents