© 2009 cisco systems, inc. all rights reserved. cisco public presentation_id 1 ccvp: implementing...
Post on 26-Mar-2015
230 Views
Preview:
TRANSCRIPT
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 1
CCVP: Implementing International Dial Plans Using Cisco Unified Communications Manager Version 7 BRKCRT-1962_c2
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 2
Agenda
Introduction
+ Dialing
New Digit Manipulation Features
Local Route Groups
Globalized Call Routing
Summary
Q & A
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 3
Introduction
Issues and Terminology
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 4
Issues of International Unified CM Deployments
Different representation of international numbers and different dial rules per country
Example US vs. Germany
PSTN access code: 9 vs. 0
National access code: 1 vs. 0
International access code: 011 vs. 00
Complex digit manipulation requirements in certain scenarios
AAR between countries
TEHO across countries
Device mobility across countries
SRST/CFUR across countries
Etc.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 5
Cisco Unified CM Terminology
Incoming PSTN call: Call from PSTN to internal phone
Outgoing PSTN call: Call from internal phone to PSTN
Call ingress: Incoming call leg; call received by Cisco Unified CM
Call egress: Outgoing call leg; call routed to destination by Cisco Unified CM
Number Normalization: The process of changing numbers to a well-defined (normalized) format (e.g. to E.164 with + prefix)
Number Globalization: The process of changing numbers to global E.164 format
Number Localization: The process of changing from normalized (in this case global) to local (shortest-possible) format
Localized E.164: PSTN number in partial (subscriber, national, international) E.164 format
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 6
Introduction
Overview of Globalized Call Routing
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 7
Call Routing Based On Globalized Numbers
Globalized format (E.164 with + prefix) is used for
All external destinations
All external sources
Internal sources when destination is external
Internal directory numbers are used for
All internal destinations
Internal sources when destination is internal
If sources of calls (users at phones, incoming PSTN calls at gateways, etc.) do not use globalized format natively, the localized call ingress is globalized before being routed
Applies to phones as well as gateways and trunks
Applies to called and calling party numbers
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 8
Localization At Call Egress
After call routing and path selection, globalized numbers can be changed to local format at the egress device
Applies to calling and called party number for all calls routed to gateways and trunks
Applies to calling party number for calls routed from gateways and trunks to phones
No localization is required for
Called party number of all calls routed to phones (must be in internal directory number format before call routing)
Calling party numbers for calls routed from internal to internal (are not globalized at call ingress)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 9
to External:Calling: DN
Called: according to local dial rules (PSTN
access codes, international access codes, etc.) or E.164 (click to dial, call lists,
etc.)
Globalized Call Routing: Number Formats
Globalized Call Routing
External to Internal:Calling: E.164
Called: DN
Internal/External to External:
Calling: E.164Called: E.164
Internal to Internal:Calling: DNCalled: DN
Call Ingress Call Egress
Calling: Localized E.164Called: Localized E.164
to Internal:Calling: DNCalled: DN
from External:Calling: Localized E.164
Called: DN
from Internal:Calling: DNCalled: DN
from Internal:Calling: Localized E.164Called: Localized E.164
from External:Calling: Localized E.164Called: Localized E.164
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 10
Components of Globalized Call Routing Introduced in Unified CM Version 7
+ Dialing
Support for + in call routing table entries (route patterns, translation patterns, etc.)
Support for + dialing from Cisco IP phones
Digit manipulation by
Non-urgent translation patterns
Incoming calling party prefixes
Called and calling party transformations
Local route groups
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 11
+ Dialing
Support in Cisco Unified Communications Manager
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 12
E.164 and + Prefix
Defines international public telecommunication numbering plan used in the PSTN and other networks
Also defines the format of telephone numbers
E.164 numbers can have a maximum of 15 digits
E.164 number starts with country code (no prefix)
International escape code + is usually prefixed to indicate that number is international (for example +49405055512)
International access codes can be used instead of +
International access codes differ per country (for example 01149405055512 or 0049405055512)
E.164 as an ITU-T recommendation for aninternational numbering plan:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 13
Support for + Dialing on Outgoing PSTN Calls
Cisco Unified CM call routing support for + dialing
+ is a dialable pattern
Can be matched in route patterns, translation patterns, etc.
Phones can place calls to international destinations using numbers in E.164 format with + prefix
From call lists (missed calls, received calls, etc.)
From directories (corporate directory, personal address book, etc.)
From speed dials
From applications (click to dial, etc.)
Not supported from phone keypad (manually entered by user)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 14
Outgoing Call With + Dialing: Called Number Localization at Call Egress
Phone uses + dialing (via call list, directory, or speed dial entry)
\+ route pattern is matched
Called number can be modified based on selected gateway
France
Germany
IP
Paris
Toronto
HQ408 555 4000
+1 408 555 40001 408 555 4000
00 1 408 555 4000
Canada
USA
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 15
Modifying Calling Party Numbers on Incoming PSTN Calls
Calling party globalization at call ingress (incoming PSTN call received from gateway)
Calling party numbers received at PSTN gateways are usually in non-E.164 format (type and length typically depend on location of caller)
Convert received calling party number to global E.164 format with + prefix
Calling party localization at call egress (incoming PSTN call sent to IP phone)
Display calling party number in shortest possible (localized) format at receiving phone (different per phone)
Retain calling party number in globalized format internally at receiving IP phone (for callbacks)
Incoming PSTN Calls:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 16
Modifying Calling Party Numbers on Incoming PSTN Calls (Cont.)
Callback number is not shown on display (only internally stored at phone)
Allows users to see simple (short) numbers but enables + dialing to be used for callbacks
PSTN
Incoming PSTN Call
Globalization at Call Ingress
Calling Party: 4085551234
San Jose 5551234
San Jose
Calling Party: +14085551234
San Jose
Calling Party:Display: 5551234
Callback: +14085551234
Localization at Call Egress
GermanyAtlanta
Calling Party:Display: 4085551234
Callback: +14085551234
Calling Party:Display: +14085551234
Callback: +14085551234
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 17
+ Dialing
Configuration
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 18
International Escape Character + Configuration Overview
+ sign in Cisco Unified Communications Manager:
+ sign used historically as a wildcard character in Cisco Unified Communications Manager route plans
Matches one or more occurrences of the preceding digit or wildcard value
For instance, 91X+ matches 910 through 919999999999999
International Escape Character configuration depends on field:
\+ is used in those fields where + wildcard is supported (in order to differentiate from + wildcard)
+ is used in those fields where + wildcard is not supported
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 19
Configuring International Escape Character Using \+
In these fields + configures the + wildcard
\+ has to be used for the International Escape Character
Configuration WindowFields that Support Entering \+ for
International Escape Character
Route Pattern, Hunt Pilot, and Translation Pattern
Route Pattern, Hunt Pilot, and Translation Pattern
Directory Number Directory Number
Intercom TranslationPattern Intercom TranslationPattern
Calling Party Transformation Pattern
Called Party Transformation Pattern
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 20
Configuring International Escape Character Using +
+ wildcard is not supported in these fields
+ is used for the International Escape Character
Configuration WindowFields that Support Entering + for International Escape Character
Device Pool Incoming Prefix fields
Service Parameter Incoming Prefix fields
Route Pattern, Hunt Pilot, Intercom Translation Pattern, and Translation Pattern
Calling Party Transform Mask, Called Party Transform Mask, and Prefix Digits
(Outgoing Calls)
Directory NumberExternal Phone Number Mask and all Call
Forwarding fields
Calling Party TransformationCalling Party Transform Mask and Prefix
Digits (Outgoing Calls)
Called Party TransformationCalled Party Transform Mask and Prefix
Digits
Voice Mail Port and Voice Mail Port Wizard
External Number Mask
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 21
Configuring International Escape Character Using + (Cont.)
Configuration WindowFields that Support Entering + for International Escape
Character
Message Waiting Message Waiting Number
Voice Mail Pilot Voice Mail Pilot Number
Gateway
Prefixes: Incoming Calling Party National Number, Incoming Calling Party International Number, Incoming Calling Party Unknown Number, and Incoming Calling Party Subscriber
Number; and Caller ID DN, Prefix DN
Trunk
Prefixes: Incoming Calling Party National Number, Incoming Calling Party International Number, Incoming Calling Party Unknown Number, and Incoming Calling Party Subscriber
Number; SIP trunk only supports the Incoming Calling Party Unknown Number Prefix; Caller ID DN and Prefix DN
Speed Dial and Abbreviated Dial
Number field
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 22
+ Dialing
Considerations
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 23
+ Dialing Support Considerations
Cisco Unified IP Phones (support depends on phone model)
+ dialing supported from call lists, speed dials, directories, and applications (not from keypad)
Support of localized calling party numbers (incoming calls)
Nokia Dual Mode Phones also support + to be entered from keypad
SIP trunks and MGCP gateways
Full support for + dialing
SIP trunks do not support number type
H.323 trunks and gateways
+ sign stripped off
Number type supported
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 24
New Digit Manipulation Features
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 25
New Digit Manipulation Features Introduced in Unified CM Version 7
Non-urgent Translation Patterns
Urgent priority can now be disabled at translation patterns
Incoming Calling Party Prefixes
Prefixes for the calling party number of incoming calls can be configured at individual gateways and trunks
Global Transformations
Called and calling party transformations can be applied at individual gateways and trunks
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 26
Characteristics of Incoming Calling Party Prefixes
Used for calling party globalization of calls received through trunks and gateways
Allows the configuration of prefixes based on number type (unknown, subscriber, national, international)
Can be configured at device, device pool, and as system parameter
Not applicable to calls received from phones
Use external phone number mask in E.164 format for globalization of phone numbers
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 27
Characteristics of Called and Calling Party Transformations
Used to localize called and/or calling party numbers at call egress
Implemented by globally configured transformation patterns
Transformation patterns are put into partitions
Devices are configured with called and calling party transformation CSS
Transformation CSS of device controls the transformation patterns visible to the device
Applied directly to phones, gateways and trunks or via device pool
Phones support calling party transformation only
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 28
Frankfurt area (69) Hamburg area (40)
Number Type Prefix
International +National +49 Subscriber +4940
69 3056412 4589555
1 408 555 5000
44 1234 567890
Calling Party Number
+1 408 555 5000+44 1234 567890+49 69 3056412+49 40 4589555
UK
US
Germany
Hamburg GatewayPSTN
Calling party number of calls received
through Hamburg gateway are normalized
(globalized to E.164 format)
Incoming Calling Party Prefix Example: Globalization of Calling Number
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 29
+49691234+14085551234+17035551234+13035551234
Called Party Transformation Example: Localization of Called Number
Globalized call routing is enabled
Localization of called number at egress gateway (after call routing) is shown
Herndon_GWarea code: 703
Called Party Transformation CSS: A,B
Boulder_GWarea code: 303
Called Party Transformation CSS:
B, C
49691234, international4085551234, national5551234, subscriber3035551234, national
49691234, international4085551234, national7035551234, national5551234, subscriber
\+1703XXXXXXX -> XXXXXXX, sub
\+1XXXXXXXXXX -> XXXXXXXXXX, ntl
\+.! -> PreDot DDI, intl
\+1303XXXXXXX -> XXXXXXX, sub
A
B
C
Called Party Transformation Patterns Partition
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 30
Calling Party Transformation Example: Localization of Calling Number
Globalized call routing is enabled
Localization of calling number at egress gateway (after call routing) is shown
Herndon_GWand Herndon phones:
area code: 703Calling Party
Transformation CSS: A, B
Boulder_GW and Boulder phones:area code: 303Calling Party
Transformation CSS: B, C
Call from Boulder Phone to PSTN via Herndon Gateway:
+13035551001 -> 3035551001, national
Call to Herndon Phone (from PSTN received through any gateway):
+49691234 -> +49691234+14085551234 -> 4085551234
+17035551234 -> 5551234
Call from Herndon Phone to PSTN via Herndon Gateway:+17035551002 -> 5551002,
subscriber
A
B
C
Called Party Transformation Patterns Partition
\+1703XXXXXXX -> XXXXXXX, sub
\+1XXXXXXXXXX -> XXXXXXXXXX, ntl
\+1303XXXXXXX -> XXXXXXX, sub
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 31
Considerations For Called And Calling Party Transformations
The pre-transformed called and calling party numbers (i.e. numbers before route pattern and route list digit manipulation settings are applied) are used to search for a matching transformation pattern
If a matching pattern is found, digit manipulation settings of route pattern and route list are ignored; the global transformation is performed based on the pre-transformed number
If no match is found, the route pattern and route list digit manipulation settings are applied
If additional transformations are required before searching for a matching transformation pattern, translation patterns have to be used
Transformations configured at translation patterns are always performed first; the resulting numbers are treated as pre-transformed numbers at the matching route pattern
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 32
Local Route Groups
Introduction
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 33
Local Route Groups
Allow dynamic selection of the egress gateway based on the source of the call
Decouple the selection of the PSTN gateway from the route patterns used to access the gateway
Reduce the complexity of dial plans
Configured by two configuration elements:
“Standard Local Route Group” entry in list of route groups that can be added to route lists
Local Route Group setting at device pools refers to any configured route group
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 34
Path Selection: Traditional Approach
Each site uses a local gateway for PSTN breakout
Per site a separate set of gateway, route group, device pool, route list, partition, route pattern, and CSS is configured
Gateway Devices
Route Groups
Route Lists
Partitions Route Patterns
GW-Bldr GW:
RG-Bldr
RG-Bldr RG:
RL-Bldr
GW-Bldr P-Bldr
Calling Search Spaces
GW-Hrdn GW:
RG-Hrdn
RG-Hrdn RG:
RL-Hrdn P-Hrdn
GW-RTP GW:
RG-RTP
RG-RTP RG:
RL-RTP P-RTP
GW-SJ GW:
RG-SJ
RG-SJ RG:
RL-SJ P-SJ
GW-Rch GW:
RG-Rch
RG-Rch RG:
RL-Rch P-Rch
Sites
Boulder, CO
Richardson, TX
Herndon, VA
RTP, NC
San Jose, CA
GW-Hrdn
GW-Rch
GW-RTP
GW-SJ
DP-Bldr
RL-Hrdn RL:
9.@ / P-Hrdn
RL-Bldr RL:
9.@ / P-Bldr
RL-Rch RL:
9.@ / P-Rch
RL-RTP RL:
9.@ / P-RTP
RL-SJ RL:
9.@ / P-SJ
P-Hrdn P:
CSS-Hrdn
P-Bldr P: CSS-Bldr
P-Rch P:
CSS-Rch
P-RTP P:
CSS-RTP
P-SJ P: CSS-SJ
DP-Hrdn
DP-Rch
DP-RTP
DP-SJ
Device Pools
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 35
Path Selection With Local Route Group
Only separate gateways, route groups, and device pools are configured per site
All sites share the same route list, partition, route pattern, and CSS
<Local> RG:
RL-Local P-System P-System P:
CSS-System
Route Lists
Partitions Route Patterns
Calling Search Spaces
Gateway Devices
Route Groups
GW-Bldr GW:
RG-Bldr
GW-Bldr
GW-Hrdn GW:
RG-Hrdn
GW-RTP GW:
RG-RTP
GW-SJ GW:
RG-SJ
GW-Rch GW:
RG-Rch
Sites
Boulder, CO
Richardson, TX
Herndon, VA
RTP, NC
San Jose, CA
GW-Hrdn
GW-Rch
GW-RTP
GW-SJ
RG-Bldr LRG : DP-Bldr
RL-Local RL:
9.@ / P-System
RG-Hrdn LRG : DP-Hrdn
RG-Rch LRG : DP-Rch
RG-RTP LRG : DP-RTP
RG-SJ LRG : DP-SJ
Device Pools
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 36
TEHO Example Without Local Route Groups
For each TEHO route pattern the first entry in the route list is the TEHO location, the second entry is the local gateway
For non-TEHO destinations there is only one entry (local gateway) in the route list
For N sites, N × N route patterns and route lists are required
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 37
TEHO Example Without Local Route Groups – Five Sites
Each site has a different route pattern and route list for each of the other sites
Each site has one additional route pattern and route list for generic PSTN access (to non-TEHO PSTN destinations)
RL-Rch-Local
9.@ / P-Rch
RL-Rch-Bldr RL:
9.1.303.XXX.XXXX / P-Rch
RL-Rch-Hrdn RL:
9.1.703.XXX.XXXX / P-Rch
RL-Rch-RTP RL:
9.1.919.XXX.XXXX / P-Rch
RL-Rch-SJ RL:
9.1.408.XXX.XXXX / P-Rch
RL-Hrdn-Bldr RL:
9.1.303.XXX.XXXX / P-Hrdn
RL-Hrdn-Local
9.@ / P-Hrdn
RL-Hrdn-Rch RL:
9.1.972.XXX.XXXX / P-Hrdn
RL-Hrdn-RTP RL:
9.1.919.XXX.XXXX / P-Hrdn
RL-Hrdn-SJ RL:
9.1.408.XXX.XXXX / P-Hrdn
RL-Bldr-Rch RL:
9.1.972.XXX.XXXX / P-Bldr
RL-Bldr-RTP RL:
9.1.919.XXX.XXXX / P-Bldr
RL-Bldr-SJ RL:
9.1.408.XXX.XXXX / P-Bldr
Route Lists
Route Patterns
Sites
Boulder, CO
Herndon, VA
RL-Bldr-Hrdn RL:
9.1.703.XXX.XXXX / P-Bldr RG-Hrdn RG-Bldr
RG: RL-Bldr-Hrdn
RG-Rch RG-Bldr
RG: RL-Bldr-Rch
RG-RTP RG-Bldr
RG: RL-Bldr-RTP
RG-SJ RG-Bldr
RG: RL-Bldr-SJ
RL-Bldr-Local
9.@ / P-Bldr RG-Bldr RG:
RL-Bldr-Local
RG-Bldr RG-Hrdn
RG: RL-Hrdn-Bldr
RG-Rch RG-Hrdn
RG: RL-Hrdn-Rch
RG-RTP RG-Hrdn
RG: RL-Hrdn-RTP
RG-SJ RG-Hrdn
RG: RL-Hrdn-SJ
RG-Hrdn RG: RL-Hrdn-Local
Richardson, TX RG-Bldr
RG-Rch RG:
RL-Rch-Bldr
RG-Hrdn RG-Rch
RG: RL-Rch-Hrdn
RG-RTP RG-Rch
RG: RL-Rch-RTP
RG-SJ RG-Rch
RG: RL-Rch-SJ
RG-Rch RG: RL-Rch-Local
Partitions Calling Search Spaces
P-Hrdn
P-Rch
P-Hrdn P:
CSS-Hrdn
P-Bldr P:
CSS-Bldr
P-Rch P: CSS-Rch
P-Bldr
RL-SJ-Local
9.@ / P-SJ
RL-SJ-Bldr RL:
9.1.303.XXX.XXXX / P-SJ
RL-SJ-Hrdn RL:
9.1.703.XXX.XXXX / P-SJ
RL-SJ-Rch RL:
9.1.972.XXX.XXXX / P-SJ
RL-SJ-RTP RL:
9.1.919.XXX.XXXX / P-SJ
RL-RTP-Local
9.@ / P-RTP
RL-RTP-Bldr RL:
9.1.303.XXX.XXXX / P-RTP
RL-RTP-Hrdn RL:
9.1.703.XXX.XXXX / P-RTP
RL-RTP-Rch RL:
9.1.972.XXX.XXXX / P-RTP
RL-RTP-SJ RL:
9.1.408.XXX.XXXX / P-RTP
Route Lists
Route Patterns
Sites
RTP, NC
San Jose, CA
RG-Bldr RG-RTP
RG: RL-RTP-Bldr
RG-Hrdn RG-RTP
RG: RL-RTP-Hrdn
RG-Rch RG-RTP
RG: RL-RTP-Rch
RG-SJ RG-RTP
RG: RL-RTP-SJ
RG-RTP RG: RL-RTP-Local
RG-Bldr RG-SJ
RG: RL-SJ-Bldr
RG-Hrdn RG-SJ
RG: RL-SJ-Hrdn
RG-Rch RG-SJ
RG: RL-SJ-Rch
RG-RTP RG-SJ
RG: RL-SJ-RTP
RG-SJ RG: RL-SJ-Local
Partitions
P-RTP
Calling Search Spaces
P-SJ P-SJ P:
CSS-SJ
P-RTP P:
CSS-RTP
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 38
TEHO Example With Local Route Groups – Five Sites
Route Lists
Route Patterns
Sites
Boulder, CO
Richardson, TX
RTP, NC
San Jose, CA
Partitions Calling Search Spaces
P-System P:
CSS-System P-System
RL-Local RL:
9.@ / P-System <Local> RG:
RL-Local
RL-RTP RL:
9.1.919.XXX.XXXX / P-System RG-RTP <Local>
RG: RL-RTP
RL-Rch RL:
9.1.972.XXX.XXXX / P-System RG-Rch <Local>
RG: RL-Rch
RL-Hrdn RL:
9.1.703.XXX.XXXX / P-System RG-Hrdn <Local>
RG: RL-Hrdn
RL-Bldr RL:
9.1.303.XXX.XXXX / P-System RG-Bldr <Local>
RG: RL-Bldr
Herndon, VA
RL-SJ RL:
9.1.408.XXX.XXXX / P-System RG-SJ <Local>
RG: RL-SJ
N2 N+1 reduction
N 1 reduction
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 39
TEHO Example With Local Route Groups – Five Sites (Cont.)
The number of route patterns and route lists for TEHO destinations is reduced from N × (N - 1) to N (20 to 5 in this example with 5 sites)
The number of route patterns and route lists for non-TEHO destinations is reduced from N to 1 (5 to 1 in this example)
The total number of route patterns and route lists is reduced from N × N to N + 1 (25 to 6 in this example)
The number of partitions and CSS is reduced from N to 1 (5 to 1 in this example)
The number of gateways, route groups, and device pools remains the same (N)
In this scenario, local route groups enable the following dial plan simplifications:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 40
Local Route Groups
Operation
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 41
Route Group: Boulder_RG
GW: Boulder_GW
Call From Boulder Phone To Herndon-TEHO Destination
Boulder_GW
Device Pool Boulder
Local Route Group:
Boulder_RG
Boulder Phones
Herndon Phones
Device Pool Herndon
Local Route Group:
Herndon_RG
Route Pattern: 9.1303[2-9]XXXXXX
Route List:TEHO-Boulder
Route Pattern: 9.1703[2-9]XXXXXX
Route List:TEHO-Herndon
Route Pattern: 9.@Route List: PSTN
Route List: PSTN
Route Groups: Standard LRG
Route List: TEHO-BoulderRoute Groups: Boulder_RG
Standard LRG
Route List: TEHO-HerndonRoute Groups: Herndon_RGStandard LRG
Route Group: Herndon_RG
GW: Herndon_GW Herndon_GW
Primary Path
Backup Path
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 42
Route Group: Boulder_RG
GW: Boulder_GW
Call From Boulder Phone To Non-TEHO Destination
Boulder_GW
Device Pool Boulder
Local Route Group:
Boulder_RG
Boulder Phones
Herndon Phones
Device Pool Herndon
Local Route Group:
Herndon_RG
Route Pattern: 9.1303[2-9]XXXXXX
Route List:TEHO-Boulder
Route Pattern: 9.1703[2-9]XXXXXX
Route List:TEHO-Herndon
Route Pattern: 9.@Route List: PSTN
Route List: PSTN
Route Groups: Standard LRG
Route List: TEHO-BoulderRoute Groups: Boulder_RG
Standard LRG
Route List: TEHO-HerndonRoute Groups: Herndon_RGStandard LRG
Route Group: Herndon_RG
GW: Herndon_GW Herndon_GW
Primary Path
Backup Path
No backup path!
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 43
Route Group: Boulder_RG
GW: Boulder_GW
Call From Herndon Phone To Non-TEHO Destination
Boulder_GW
Device Pool Boulder
Local Route Group:
Boulder_RG
Boulder Phones
Herndon Phones
Device Pool Herndon
Local Route Group:
Herndon_RG
Route Pattern: 9.1303[2-9]XXXXXX
Route List:TEHO-Boulder
Route Pattern: 9.1703[2-9]XXXXXX
Route List:TEHO-Herndon
Route Pattern: 9.@Route List: PSTN
Route List: PSTN
Route Groups: Standard LRG
Route List: TEHO-BoulderRoute Groups: Boulder_RG
Standard LRG
Route List: TEHO-HerndonRoute Groups: Herndon_RGStandard LRG
Route Group: Herndon_RG
GW: Herndon_GW Herndon_GW
Primary Path
Backup Path
No backup path!
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 44
Route Group: Boulder_RG
GW: Boulder_GW
Call From Herndon Phone To Boulder-TEHO Destination
Boulder_GW
Device Pool Boulder
Local Route Group:
Boulder_RG
Boulder Phones
Herndon Phones
Device Pool Herndon
Local Route Group:
Herndon_RG
Route Pattern: 9.1303[2-9]XXXXXX
Route List:TEHO-Boulder
Route Pattern: 9.1703[2-9]XXXXXX
Route List:TEHO-Herndon
Route Pattern: 9.@Route List: PSTN
Route List: PSTN
Route Groups: Standard LRG
Route List: TEHO-BoulderRoute Groups: Boulder_RG
Standard LRG
Route List: TEHO-HerndonRoute Groups: Herndon_RGStandard LRG
Route Group: Herndon_RG
GW: Herndon_GW Herndon_GW
Primary Path
Backup Path
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 45
Route Group: Boulder_RG
GW: Boulder_GW
Call From Herndon Phone To Herndon Destination
Boulder_GW
Device Pool Boulder
Local Route Group:
Boulder_RG
Boulder Phones
Herndon Phones
Device Pool Herndon
Local Route Group:
Herndon_RG
Route Pattern: 9.1303[2-9]XXXXXX
Route List:TEHO-Boulder
Route Pattern: 9.1703[2-9]XXXXXX
Route List:TEHO-Herndon
Route Pattern: 9.@Route List: PSTN
Route List: PSTN
Route Groups: Standard LRG
Route List: TEHO-BoulderRoute Groups: Boulder_RG
Standard LRG
Route List: TEHO-HerndonRoute Groups: Herndon_RGStandard LRG
Route Group: Herndon_RG
GW: Herndon_GW Herndon_GW
Primary Path
Backup Path
Primary and backup path are the same!
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 46
Local Route Groups
Interaction With CSS Implementation Models
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 47
Review Of Traditional CSS Implementation: Single Site Example
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 48
N
Review of Traditional CSS Implementation: Multisite Example
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 49
Review of Line/Device CSS Model
Partitions of line CSS and partitions of device CSS are combined (with priority to partitions of line CSS)
Usage guidelines:
Configure device CSS to provide call routing information (for example, which gateway to select for all PSTN calls)
Configure line CSS to provide class of service information (for example, which of the PSTN calls to block)
Significantly decreases the total number of partitions and CSS required:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 50
Review of Line/Device CSS Model: Concept
Device CSS contains only one partition with route patterns to all PSTN numbers using a specific PSTN gateway
For each PSTN gateway, route patterns exist once in a different partition
Line CSS contains a partition with a single route pattern that matches international numbers and has been configured as a blocked pattern
Regardless of the used gateway, this same partition can be used to block international calls
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 51
Empty
Review of Line/Device CSS Model: Multisite Example
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 52
Interaction Of Local Route Groups With CSS Implementation Models
The purpose of the line/device approach is to decouple gateway selection from CoS to reduce the number of route patterns, route lists, partitions and CSS:
When using local route groups, gateway selection is totally independent of the matched route pattern and referenced route list
Further dial plan simplification is possible:
No need for multiple device CSS because the route list refers to the Default Local Route Group (specified in the device pool of the calling phone)
CoS is still provided by different line CSS (which is independent of gateways anyway as all accessible patterns are blocked patterns)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 53
Interaction of Local Route Groups With CSS Implementation Models (Cont.)
Per class of service one (line) CSS is required which has access to the desired blocked patterns
The (gateway-independent) PSTN route pattern(s) have to be made available by granting access to the corresponding partition
Either by using one and the same device CSS at all phones or by adding the partition to the end of the line CSS
CSS requirements with traditional approach and no local route groups: number of classes of services × number of sites
CSS requirements with line/device approach and no local route groups: classes of service + number of sites
CSS requirements with local route groups: number of classes of service (+ 1, if partition of PSTN route patterns is placed into device CSS instead of the end of the line CSS)
The CSS requirements with local route groups are:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 54
Globalized Call Routing
Introduction
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 55
New Dial Plan Approach For International Deployments
Globalized call routing simplifies implementation of international multisite deployments with centralized call processing
Call routing is based on globalized (+ dialing) numbers (except for calls to internal destinations)
E.164 global format is used for all calling party numbers (except for calls from internal to internal)
If sources of calls (users at phones, incoming PSTN calls at gateways, etc.) do not use normalized format natively, their localized call ingress needs to be normalized before being routed
Applies to phones as well as gateways and trunks
Applies to called and calling party numbers
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 56
New Dial Plan Approach For International Deployments (Cont.)
Applies to calling and called party number for all calls routed to gateways and trunks
Applies to calling party number for calls routed from gateways and trunks to phones
Does not apply to called party number for all calls routed to phones (as internal directory numbers are the standard format for internal destinations)
Does not apply to calling party numbers for calls route from internal to internal (as internal directory numbers are the standard format in this case)
After the call is routed and path selection is performed, the destination device might need to change the normalized numbers to local format (localized call egress)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 57
Globalized Call Routing – Three Phases
Globalized Call Routing
Globalization of Localized Call Ingress
Localization at Call Egress
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 58
Globalized Call Routing
Globalization of Localized Call Ingress and Localized Call Egress
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 59
Globalized Call Routing: Number Formats
Unified CM Globalized Call Routing
Call Ingress Call Egress
to Internal:Calling: E.164
Called: DN
to External:Calling: E.164Called: E.164
to Internal:Calling: DNCalled: DN
to External:Calling: E.164Called: E.164
from External:Calling: Localized E.164
Called: DN
from Internal:Calling: DNCalled: DN
from Internal:Calling: Localized E.164Called: Localized E.164
from External:Calling: Localized E.164Called: Localized E.164
Calling: Localized E.164Called: Localized E.164
to Internal:Calling: DNCalled: DN
to External:Calling: DN
Called: according to local dial rules (PSTN
access codes, international access codes, etc.) or E.164 (click to dial, call lists,
etc.)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 60
Normalization of Localized Call Ingress on Gateways
to Internal:Calling: E.164
Called: DN
to External:Calling: E.164Called: E.164
Calling: Localized E.164Called: Localized E.164
Localized Call Ingress
Normalization
Calling number:Incoming Calling
Party Prefix(GW, DP, SP)
Called number for internal destinations:
Significant Digits (GW) or
Translation Patterns
Called number for external destinations:Translation Patterns
Example (gateway in San Jose):5551234, sub -> +14085551234303555333, ntl -> +1303555333496912345, intl -> +496912345
Examples (DID 4085551XXX at gateway in San Jose):
Significant Digits: 4
Unified CM Globalized Call Routing
GW: gateway, DP: device pool, SP: service parameter
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 61
Normalization of Localized Call Ingress from Phones
to External:Calling: E.164Called: E.164
to External:Calling: DN
Called: according to local dial rules (PSTN
access codes, international access
codes, etc.)
Localized Call Ingress
to Internal:Calling: DNCalled: DNto Internal:
Calling: DNCalled: DN
Normalization
Calling number for external destinations:
External Phone Number Mask
(Translation Pattern)
Called number for external destinations:Translation Patterns
Example (phones in San Jose):External Phone Number Mask:
+14085551XXX Example (phones in San Jose):9.1[2-9]XX[2-9]XXXXXX -> DDI
PreDot, Prefix +9.[2-9]XXXXXX -> DDI PreDot,
Prefix +14089011.! -> DDI PreDot, Prefix +
Example (phones in Hamburg):000.! -> DDI PreDot, Prefix +
00.! -> DDI PreDot, Prefix +490.! -> DDI PreDot, Prefix +4940
Unified CM Globalized Call Routing
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 62
Localized Call Egress at Gateways
External to External:
Calling: E.164Called: E.164
Internal to External:
Calling: E.164Called: E.164
Calling: Localized E.164Called: Localized E.164
Localized Call Egress
Calling number:Calling Party
Transformation CSS (GW, DP)
Called number:Called Party
Transformation CSS (GW, DP)
Example (Partition for San Jose gateway):
\+.! -> DDI PreDot, Prefix 011\+.1XXXXXXXXXX -> DDI Predot\+1408.XXXXXXX -> DDI Predot
Example (Partition for Hamburg gateway):
\+.! -> DDI PreDot, intl\+49.! -> DDI Predot, ntl
\+4940.! -> DDI Predot, subExample (Partition for San Jose gateway):
\+.! -> DDI PreDot, intl\+1.XXXXXXXXXX -> DDI Predot, ntl\+1408.XXXXXXX -> DDI Predot, sub
Example (Partition for Hamburg gateway):
\+.! -> DDI PreDot, intl\+49.! -> DDI Predot, ntl
\+4940.! -> DDI Predot, sub
Unified CM Globalized Call Routing
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 63
Localized Call Egress at Phones
External to Internal:
Calling: E.164Called: DN
Internal to Internal:
Calling: DNCalled: DN
from External:Calling: Localized E.164
Called: DN
Calling number:Calling Party
Transformation CSS (Phone, DP)
Note: Normalized format also kept for callback
from lists on supported phones
Localized Call Egress
Example (Partition for San Jose phones):
\+1.XXXXXXXXXX -> DDI Predot\+1408.XXXXXXX -> DDI Predot
Example (Partition for Hamburg phones):\+49.! -> DDI Predot, Prefix 0
\+4940.! -> DDI Predot
Unified CM Globalized Call Routing
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 64
Globalized Call Routing
Examples
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 65
Globalized Call Routing – Example: Emergency Dialing
Note local emergency numbers (e.g. 112 in EU, 999 in UK, 000 in Australia)
Introduce a corporate emergency number (e.g. 888) that can be used at all sites
Allow local emergency numbers in addition to corporate emergency number:
Per site: Only local emergency number is permitted (e.g. 112 can only be used in EU, 999 can only be used in UK, etc.)
Globally: All local emergency numbers are permitted at all sites (roaming users can use home emergency number)
Local emergency numbers are globalized to corporate emergency number (e.g. 888) at call ingress by translation patterns
Corporate emergency number is localized at egress gateway by called party transformation CSS (e.g. 888 is changed to 112 at EU gateway, to 999 at UK gateway, and to 000 at Australian gateway)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 66
3 Trans-lation
Patterns: 000, 112,
999
Called party trans-
formation mask: 888
Australia
000
112
999
Australian User in EU
EU User
UK User
888
Any User in UK
Route Pattern:
888
Route List: System
Route List: System
Route Group: Default
LRG
EU-GW
UK GW
Called partytransformation:
888 -> 112
Called partytransformation:
888 -> 999
Globalized Call Routing – Example: Emergency Dialing (Cont.)
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 67
Globalized Call Routing
Interaction With AAR
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 68
Interaction With AAR
AAR calls are placed to global number
No AAR prefixes required between AAR groups
Eliminates the need of multiple AAR groups
Single route pattern (\+.!) sufficient for all AAR calls
Route pattern refers to single route list
Route list includes only “Standard Local Route Group“
AAR CSS can be the same for all phones
AAR can benefit from globalized call routing when globalized number is used in external phone number mask:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 69
AAR Group:DE
AAR Example Without Globalized Call Routing
DN: 2001Ext. Phone Nr
Mask:5115552XXX
DN: 3001Ext. Phone Nr.
Mask: 69125XXXX
IP WANIP WAN
Site1 (+1):international dialing: 9.011
Site 2 (+49):international dialing: 0.00
PSTNPSTN
AAR Group:US
AAR Group Configuration:Prefix US to DE: 901149Prefix DE to US: 0001
RP: 9.@ RP: 0.!
Two route patterns in different partitions, two AAR CSS, two
AAR groups
Unified CM
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 70
AAR Group:System
AAR Example With Globalized Call Routing
DN: 2001Ext. Phone Nr
Mask:+15115552XXX
DN: 3001Ext. Phone Nr.
Mask: +4969125XXXX
Unified CM
IP WANIP WAN
PSTNPSTN
AAR Group:System
Single RP: \+.!
Single route pattern in one partition, single AAR CSS, single AAR group,
no prefixes within AAR group
Single RL:Default Local Route Group
RG: US RG: DE
Site1 Site 2
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 71
Globalized Call Routing
Interaction With CFUR
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 72
Interaction With CFUR
CFUR calls are placed to global number
Single route pattern (\+.!) sufficient for all CFUR calls
Same route pattern can be used for AAR and PSTN access (unless TEHO is used)
Route pattern refers to single route list
Route list includes only “Standard Local Route Group“
CFUR CSS can be the same for all phones
CFUR can benefit from globalized call routing when globalized number is used as CFUR destination number:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 73
Interaction With CFUR (Cont.)
Without using local route groups the CFUR CSS determines the gateway used for the CFUR call
The CFUR CSS is set at the phone that is unregistered (in SRST mode)
All callers use the same CFUR CSS to reach such an unregistered phone
If callers are at different sites, they all have to use the same gateway (typically the main site gateway is used)
With local route groups each spoke site can use its local gateway for CFUR calls
Optimized gateway selection with multiple sites when using local route groups:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 74
CFUR Example Without Local Route Groups
HQ
Site 1 Site 2
PSTNPSTNIPIP
PhoneCFUR: 915215553001CFUR CSS: HQ
521-555-3XXX
531-555-4XXX
511-555-2XXX
3001
Route Pattern9.@Partition: HQ
CFUR call from HQ phone to Site 1 phone uses HQ PSTN gatway
CFUR call from Site 2 phone to Site 1 phone uses HQ PSTN gateway instead of Site 2 PSTN gateway
Route ListRoute Group: HQ-GW
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 75
CFUR Example With Local Route Groups
HQ
Site 1 Site 2
PSTNPSTNIPIP
PhoneCFUR: 915215553001CFUR CSS: System
521-555-3XXX
531-555-4XXX
511-555-2XXX
3001
CFUR call from HQ phone to Site 1 phone uses HQ PSTN gatway
CFUR call from Site 2 phone to Site 1 phone uses Site 2 PSTN gateway
Route Pattern9.@Partition: System
Route ListRoute Group: Standard LRG
Device PoolLRG: HQ-GW
Device PoolLRG: Site2-GW
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 76
Globalized Call Routing
Interaction With TEHO
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 77
Interaction With TEHO
The number of route patterns and route lists required for TEHO with local backup is reduced from N × N to N + 1 (N is the number of sites)
The number of partitions and CSS is reduced from N to 1
The number of gateways, route groups, and device pools remains the same (N)
If combined with globalized dialing, TEHO can be used worldwide using this simple dial plan model (N + 1 route patterns and route lists) – regardless of different local dial rules
TEHO can be used across countries (if legally permitted)
When using globalized call routing and local route groups:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 78
Globalized Call Routing
Interaction With Device Mobility
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 79
Review of Cisco Unified Device Mobility
Roaming sensitive settings (location, region, SRST reference, MRGL, etc.) are always updated when roaming to different physical location
Device mobility related settings (device CSS, AAR CSS, and AAR group) are updated based on device mobility group
Different DMG
No update of device CSS, AAR CSS, and AAR group
No changes to dial rules, but use of home gateway
Same DMG
Update of device CSS, AAR CSS, and AAR group
Use of roaming gateway but changes to dial rules
Before Unified CM version 7 Cisco Unified Device Mobility was typically implemented as follows:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 80
Interaction With Cisco Unified Device Mobility
Updates of roaming sensitive settings still apply (no changes)
Combination of advantages of both Cisco Unified Device Mobility version 6 implementation types is possible
Roaming gateway can be used
Home dial rules can be used
No updates of device mobility related settings (device CSS, AAR CSS, and AAR group) required
Functionality of device level CSS (device/line approach) is replaced by local route group
Different AAR groups and AAR CSS not required
Eliminates need for device mobility groups
Cisco Unified Device Mobility benefits from globalized call routing and local route groups:
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 81
Cisco Unified Device Mobility Version 6 Example: Different DMG
HQ
Branch
PSTNPSTN
Route Pattern0.!Partition: HQ
Route ListRoute Group: HQ-GW
Route Pattern9.@Partition: Branch
Route ListRoute Group: BR-GW
Device Pool: HQPhysical Location: HQDevice Mobility Group: HQ(Device Mobility CSS: HQ)
Device Pool: BRPhysical Location: BRDevice Mobility Group: BR(Device Mobility CSS: BR)
BR Phone (roaming)Device CSS: BR
BR Phone (home)Device CSS: BR
HQ: EU numbering plan, BR: NANP; BR user roaming to HQ uses NANP dial rules and uses BR gateway
+1-521-555-3XXX
+49-40- 5552XXX
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 82
Cisco Unified Device Mobility Version 6 Example: Same DMG
HQ
Branch
PSTNPSTN
BR Phone (roaming)Device CSS: HQ
Route Pattern0.!Partition: HQ
Route ListRoute Group: HQ-GW
Route Pattern9.@Partition: Branch
Route ListRoute Group: BR-GW
BR Phone (home)Device CSS: BR
Device Pool: HQPhysical Location: HQDevice Mobility Group: WorldDevice Mobility CSS: HQ
Device Pool: BRPhysical Location: BRDevice Mobility Group: World(Device Moblity CSS: BR)
HQ: EU numbering plan, BR: NANP; BR user roaming to HQ has to use EU dial rules and uses HQ gateway
+1-521-555-3XXX
+49-40- 5552XXX
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 83
Single RL:Default Local Route Group
Cisco Unified Device Mobility Example Using Globalized Call Routing and LRG
HQ
Branch
PSTNPSTN
+1-521-555-3XXX
+49-40- 5552XXX
RG: BR
RG: HQ
Device Pool: HQPhysical Location: HQLocal Route Group: HQ
Device Pool: BRPhysical Location: BRCSS: BR)Local Route Group: BR
BR Phone (roaming)Line CSS: BR
BR Phone (home)Line CSS: BR
HQ: EU numbering plan, BR: NANP; Normalization of localized call ingress is in place; BR user roaming to HQ uses NANP dial rules and uses HQ gateway
BR Translation Patterns (Partition BR, CSS: System):
91.[2-9]XX[2-9]XXXXXX -> DDI PreDot, Prefix +1
9.[2-9]XXXXXX -> DDI PreDot, Prefix +1408
9011.! -> DDI PreDot, Prefix +
HQ Translation Patterns (Partition HQ, CSS: System:000.! -> DDI PreDot, Prefix +
00.! -> DDI PreDot, Prefix +490.! -> DDI PreDot, Prefix +4940
Route Pattern: \+!Partition: System
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 84
Summary
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 85
Summary
Cisco Unified Communications Manager version 7 introduces support for + dialing.
New digit manipulation features have been introduced.
Non-urgent translation patterns
Incoming calling party prefixes
Called and calling party transformations
Local route groups decouple gateways selection from matched route patterns.
Globalized call routing can be easily implemented using the new features and substantially simplifies dial plan configuration including AAR, CFUR, TEHO and device mobility.
Globalized call routing is based on three phases:
Globalization of localized call ingress
Call routing based on globalized numbers
Localization at call egress
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicPresentation_ID 86
Q & A
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 87
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.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco PublicBRKCRT-1962_c2 88
top related