Advanced Dial Plan Design For Ip Telephony Networks

Advanced Dial Plan
Design
BRKUCT-3012
Luc Bouchard
BRKUCT-3012 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1
HOUSEKEEPING
We value your feedback, don’t forget to complete your online session
evaluations after each session and complete the Overall Conference
Evaluation which will be available online from Friday.
Visit the World of Solutions on Level -01!
Please remember this is a ‘No Smoking’ venue!
Please switch off your mobile phones!

Please remember to wear your badge at all times including the Party!
Do you have a question? Feel free to ask them during the Q&A section or
write your question on the Question form given to you and hand it to the
Room Monitor when you see them holding up the Q&A sign.
Session Scope and Objectives
• To explore the various architectural challenges
of planning an IP-based telephony network
because it can do more than a traditional
telephony system, because it breaks all the
common boundaries (few, if any, PBX’s have
hundreds of sites)
• To explore the design and implementation

possibilities of Cisco’s IP telephony system
Design based on Cisco CallManager 4.X and
5.0
• Aspects we will cover:

• Dial plan elements
(Call routing logic, partitions and calling
search spaces...)
• Design guidelines
(Classes of service, multisite deployments,
extension mobility...)
Overall Agenda
Planning Considerations
Dial Plan Elements
Design Guidelines
Conclusions
Planning
Considerations
The Fundamentals
A Few Things We All Like in a Good
Dial Plan:
Not reprinting business cards (i.e.: not changing
numbers because we change phone systems)
Having abbreviated dialing within a site
(e.g.: five digit dialing)
Having a simple, direct correspondence between
someone’s DID number (i.e.: business card) and
their internal extension
Keeping it simple, where even the new guy can use
the phone system (i.e.: dial “9” for an outside line,
or five digits to reach colleagues)
The Fundamentals (Cont.)
A few things we all like in a good dial plan:

Keeping it simple, where even the new system administrator
can maintain the phone system
(an area code split would not destroy the plan)
Future proofing, such that when the new office
opens, we do not have to redo it all
Have a good user experience (e.g.: not having to
wait for interdigit timeout when calling the guy
in the next cube over)
Remember: the best tool to start with is this:
Uniform Dial Plans Are Simple
Q: Could this system use a uniform 3 digit dial plan?
A: No! Marseille and Brest DID ranges overlap in the
last 3 digits.
Q: Ok, how about 4 digit uniform dial plan?

A: No! overlaps again!
Because each time you call extensions 1120 Paris

through 1129 in Brest, you get the emergency 01450718XX
service (by calling 112)
Lyon Marseille Lille Brest

04785575XX 04911291XX 03203754XX 02985311XX
Uniform Dial Plans Are Simple (2)
Q: Fine! How about a 5 digit uniform dial plan?
A: Currently, yes! No overlap in the current ranges
of DID numbers assigned.
Q: Great! How about that new office we want to get

in Nice? Room for it in our dial plan?
A: Sure. Well, maybe: it cannot use a DID range
where the fourth digit after the prefix is 0, and Paris
cannot overlap with 575XX, 291XX, 754XX, 01450718XX
311XX, or 718XX…
Lyon Marseille Lille Brest Nice

04785575XX 04911291XX 03203754XX 02985311XX 0493??????
Uniform Dial Plans Are Simple (3)
Q: If all I could get from the Telco in Nice is a DID
range of 04935754XX, could I not dial 6 digits to
reach a Nice phone, and 5 digits anywhere else?
That way, I avoid the overlap between Nice and
Lille.
A: No! Because calls to Lyon (e.g.: 57540) will
sometimes overlap with calls to Nice’s phones
(e.g.: 575403), forcing the inter-digit timeout to
occur before the call is routed. Paris
01450718XX
Q: What do I do now? Go to 6 digits?
A: No: the Paris site has a 0 in the 6th position.
Overlaps with the PSTN access code…
Q: 7 digits?
A: No: Marseille starts with 112!

04785575XX 04911291XX 03203754XX 02985311XX 04935754XX
Uniform Dial Plans Are Simple (or so we hoped)
Q: 8 digits?
A: ok for now... not really abbreviated dialing
anymore though…
Paris
01450718XX

04785575XX 04911291XX 03203754XX 02985311XX 04935754XX
What if I have many, many more sites? More users?
Q: I have 250 branches, with over 90 with 100+ users,
and a dozen with more than 1000 users, and a
headquarter with 12000 users. Can I still use 8 + 5
digits for on-net, inter-site calls?
A: No!
You essentially have the following to play with:
2XXXX, 3XXXX, 4XXXX, 5XXXX, 6XXXX, 7XXXX, Paris
9XXXX 014455XXXX
250 DID ranges, the need for more than a whole 5 014507XXXX
digit range for a single site, and dividing the rest
into 250 un-equal parts. Future planning,
numbering plan changes, etc…
Toulouse Clermont-Ferrand Strasbourg Metz Bordeaux

056155XXXX 04736651XX 0388775XXX 0387442XXX 05569954XX
What if I have many, many more sites? More users? (2)
Q: What to do?
A: Site codes are a good idea.
0 = outside line, all combinations
8 + site code (3 digits would work up to 1000
sites),
followed by a 4 digit extension Paris
[2-79]XXX: on-net, intra-site dialing 014455XXXX
014507XXXX
Site code 123
(and 124)
Toulouse Clermont-Ferrand Strasbourg Metz Bordeaux

056155XXXX 04736651XX 0388775XXX 0387441XXX 05569954XX
Site code 012 Site code 345 Site code 256 Site code 390 Site code 822
Dial Plan
Elements
Dial Plan Elements Agenda
Cisco CallManager Call Routing Logic

External/Internal Routes in Cisco CallManager
Partitions and Calling Search Spaces
Alternate Routing
Other Tools
Defining External Routes
Commonly Used Route Pattern Wildcards
Delimiter (Does Not Match Any Digits)—Used for Discarding

Range of Digits (between one and six)
Single Digit Between Zero and Nine
0.0[1-6]XXXXXXXX
One or More Occurrences of Digits between Zero and Nine
The “#” Digit—Used to Avoid Inter-Digit Timeout
0.00! #
A Macro that enters an entire national numbering
plan into Cisco Unified CallManager (Hundreds
0. @ of individual Route Patterns). NANP by default. Others
available at: http://www.cisco.com/cgi-bin/tablebuild.pl/IDP
Basic Principle
Route Patterns
User Dials
“1200” 1XXX
12XX
User Dials Directory Numbers
“1234” 1234
1234
Cisco CallManager matches the most specific pattern

(longest-match logic)
An IP phone directory number is a special case
of route pattern that matches a single number

Alternate Routing
Other Tools
Dial Plan: The “IP Routing” of IP
Telephony
Route
Pattern 00.1408XXXXXXX Gatekeeper
Cisco Remote
CallManager GK Cisco
1000 IP WAN CallManager
Router/GW PSTN
1001 +1 408 5264000
Cisco CallManager Routes Two Basic Call Types:

On-Cluster Calls: Destination Directory Number (DN) is registered with Cisco CallManager.
DNs are considered “internal” routes.
Off-Cluster Calls: External Route Patterns Must Be Configured on Cisco CallManager
Alternate routes: Allow On-Cluster and Off-Cluster calls to attempt alternate paths to
destination (e.g.: IP WAN not available, go through PSTN)
External Routes in Cisco CallManager
Overall Structure
Route Pattern Route
• Matches dialed number for external calls Pattern
• Performs digit manipulation (optional)
• Points to a route list for routing
Configuration Order
Route
Route List List
• Chooses path for call routing
• Points to prioritized route groups 1st Choice 2nd Choice
Route Route
Group Group
Route Group 1st 2nd
• Performs digit manipulation Choice Choice
• Points to the actual devices
GK
Devices IP WAN PSTN
• Gateways (H.323, MGCP)
• Gatekeeper
• Trunk (H.225, ICT, SIP)
Defining External Routes
Route Group Device Types
Route
Group
GK
MGCP H.323 Gateways Inter-Cluster Trunk GK-Controlled SIP Trunk

Gateways (H.225) (Non-GK Controlled) Trunk
• Cisco IOS • Other Cisco

• Cat 6K T1/E1 • All Cisco IOS • Other Cisco CallManager
gatekeeper
• Cisco IOS Gateways CallManager clusters or
Gateways clusters SIP Network
Delegates Ext.
• VG series “Base” Dial Plan
IP WAN Routing
Configured
to the GK
in Cisco IOS
Dial Plan Config.
Cisco CallManager
Internal Routes in CallManager
IP Phones Voice messaging

On-cluster destinations
Call park
Software phone Auto-attendant

Translation
patterns
Analog phones
(FXS ports) IVR
911 (Emergency
Responder)
endpoints applications Non-media

with media services

Alternate Routing
Other Tools
Building Classes of Service
PartitionA
CSS1 2002 Lines
Phones PartitionA 2001 (Directory Numbers)
PartitionB 2000
Translation
7 [Transform Mask: 2001] Patterns
“Dialable” Patterns
112
“Dialing” Devices
CSS2 Route
PartitionB
0.0[1-6]XXXXXXXX Patterns
Lines
0.08XXXXXXXX
PartitionB
CSS3 Application Numbers
Gateways PartitionB 5000 (CTI Route Points, CTI Ports)
PartitionA 900X Special numbers
99XX (MeetMe, CallPickup...)
8001 Voice Mail Ports

CSS4 8000
Applications PartitionA Route
0.00! Patterns
Q3: Quick Quiz Question
What Is Needed for Phone A to Be Able to Call
Phone B and Vice Versa?
Phone A Phone B
Line 1000 Line 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
Impact of Partition Order in a CSS
Calling Search Space Most specific patterns

are chosen
User dials irrespective
Partition 1
“2345” of partition order
1XXX
Partition order is only
23XX used as a tie-breaker
in case of equal
matches
Partition 2
Device
12XX
User dials 23XX

“1234”
Device CSS-Line CSS Interaction
Line CSS
Partition L1
Partition L2 Resulting CSS
Partition L3 Partition L1
Line
Partition L2
Partition L3
Partition D1
Partition D2
Device CSS
Partition D3
Partition D1
Partition D2 The resulting CSS is
the concatenation of
Partition D3
the Line CSS with the
Device
Device CSS. The
<none> CSS is always
implied at the end.
Typical Use and Default Values
Calling Search
Spaces Partitions
Calling
Search
Space All IP phones,
assigned Voice Mail,
to Device Media
Based on InternalOnly Internal Resources,
Policy 911 Route
Pattern
LocalOnly
Local Local
Route Patterns
Unrestricted Long Distance
Long Distance Route Patterns
Default Default
CSS <None> <None> Partition

Alternate Routing
Other Tools
Alternate Routing
Multiple mechanisms to allow CUCM to route a call through an
alternate path if the preferred path is not available
e.g.: IP path not usable, then overflow the call through the PSTN
External routes can use Route Lists / Route Groups
Internal routes can use:
Automated Alternate Routing for calls to on-net 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 External routes
The route list/route group construct
Route Pattern 1
User calls Route pattern match
“8-11-3445” “811.XXXX” No digit manipulation
2
London (UK) Route List Select Route Group
“LON-OUT” based on priority
1st 2nd
Choice Choice
3a 3b
Discard “811”
Discard Access Code “8” Route Group Route Group Prefix “0039011819”
Point to remote CM via “IP-WAN” “LON-PSTN” Point to local PSTN
Inter-cluster Trunk + GK Gateway
4b
4a “00390118193445”
GK
“11-3445” sent over IP sent over PSTN to
IP WAN PSTN
WAN to Turin CallManager Turin
5
Note: Turin CUCM must +39 011 8193445
adapt incoming call’s digits x3445
to match DN on phone
BRKUCT-3012 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential
Turin (Italy) 33
Alternate Routing for internal routes
CAC denial without AAR
Request: Call from 2345: Region SF; Location SF
2345 to 1234? 1234: Region NY; Location NY
Codec SF-NY: G.729, ergo 24k
DO NOT PLACE Location SF: 24k: OK!
THAT CALL!!! Location NY: 1k Left: NO!!!
User Dials 1234
IP WAN BW Not
Available!!!
SF_GW
Phone A Phone B
2345 1234
San Francisco
PSTN
New York
Location: SF Location: NY
Region: SF Region: NY
AAR Situation with CallManager 4.0, 4.1 & 5.X
Call is automatically re-routed using number configured

in External Phone Number Mask when bandwidth is not
sufficient (call admission control denial)
AAR decision tree in CallManager 4.0, 4.1 & 5.X:
YES YES AAR Group YES Prefix digits from

AAR External Mask
On Destination? Table Group Table to
Configured? Configured? the External mask(1)
NO
NO NO Route the Call using

Drop the call the Calling device’s
AAR CSS
(1)
Mask is combined with the digits dialed originally
AAR Group Assigned to DN
DNs are assigned to

an AAR group
But, the CSS used for
AAR calls is on the
device (see next slide)
AAR Calling Search Space Assigned to Device
Be mindful of this for

extension mobility
This is how an AAR-
specific route can
be chosen
GW typically needs to be
co-located (since un-
availability of WAN
bandwidth is what triggers
the AAR mechanism)
AAR configuration Details
Called DN’s External Party Phone Number Mask: 212555XXXX
AAR Groups Tell Me to Prefix 91, So New Destination Is: 912125551234
AAR CSS of Originating Device Contains R.P. 91[2-9]XX[2-9]XX XXXX
Pointing to SF_GW
Let’s Request a Call from 2345 to SF_GW
User Dials 1234
IP WAN BW Not
Available!!!
SF_GW
Phone A Phone B
2345 AAR CSS 1234
San Francisco
on Device PSTN
DN’s AAR DN’s External Mask: New York
Location: SF Location: NY
Group: US 212 555 XXXX
Region: SF Region: NY
AAR Group: US
AAR Rerouting the Call
Request: Call from 2345: Region SF; Location SF
2345 to SF_GW? SF_GW: Region SF; Location SF
Go Ahead!!! Codec SF-SF: G.711, ergo 80k
Same Location: CAC OK!
GO!
User Dials 1234
IP WAN BW Not
Available!!! 34
2
51
Phone A
SF_GW 1
21 55
25 New Call Phone B
2345 55 1234
12 in NY
34 PSTN
San Francisco New York
Location: SF Place Location: NY
Region: SF
Call in SF Region: NY
AAR decision Tree with CallManager 4.2
YES YES
Voicemail
Box Checked?
New
NO
YES
AAR Destination
Mask Set?
NO
AAR Group YES Prefix digits from

AAR YES YES
External Mask Table Group Table to
Configured? On Destination? Configured? the External mask
NO
NO NO Route the Call using

Drop the call the Calling device’s
AAR CSS
Without Call Forward Unregistered (CFUR)
Request: Call from 1234: un-registered
2345 to 1234? CFB: 5000 (vmail)
CFB CSS: Internal
Send call to 5000
through the
Internal CSS!
Voice
Mail
(5000) SRST
User Dials 1234
IP WAN
SF_GW
Phone A Phone B
2345 1234
San Francisco
PSTN
New York
CFB: 5000 (vmail pilot)
CFB CSS: Internal
With Call Forward Unregistered (CFUR)
2345 to 1234? CFUR: 912125551234
CFUR CSS: Cent_GW
Send call to
912125551234
through the
Cent_GW CSS! Voice
Mail
(5000) SRST
User Dials 1234
12125551234
IP WAN
SF_GW 34
Phone A 12
5 55 Phone B
2345 1234
San Francisco
PSTN
New York
CFUR: 912125551234
CFUR CSS: Cent_GW
Reroutes calls to unregistered DN’s using number specified in “Call

Forward Unregistered” (CFUR) field
Destination number same irrespective of calling phone’s PSTN
dialing requirements: previous example a problem for say, a site in
Europe where the dialed number should be 0 00 1 212 555 1234
CFUR CSS same irrespective of calling phone’s dial plan: not able
to use different GW based on calling site
If CFUR CSS is left to <none>, calling phone’s CSS is used. NOT A
PROTECTED FEATURE!!!!
Calling phone’s class of service must allow call
Number in CFUR field needs to include PSTN access codes
What happens if phone is “merely” un-registered?
Beware of loops: GWs should not be allowed to place calls to
number ranges that deliver calls to the GW itself. Next page has
illustration: we will be looking at what happens after the first CFUR
attempt
GW to 1234? CFUR: 912125551234
CFUR CSS: Cent_GW
Send call to
912125551234
through the
GW wants to
Cent_GW CSS! Voice
reach 1234
Mail
(5000)
User Dials 1234
12125551234
IP WAN
SF_GW 34
Phone A 12
5 55 Phone B
2345 1234
Phone down
San Francisco
PSTN Site not in SRST!
New York
CFUR: 912125551234
CFUR CSS: Cent_GW
CFUR CSS cannot be expected to be able to

avoid loops in this situation.
CFUR is invoked whenever DN is unregistered,
including when EM is logged out or the phone is
unplugged
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

Alternate Routing
Other Tools
Other Tools
Translation Patterns: The Basics
Calling Search
Spaces Partitions
Translation Pattern
Translations Transforms “0” in
OperatorCSS 0 [Transform Mask: 2001] 2001 and Forces
Second Lookup
Dials “0”
Delivers “2001”
to Reach
Operator AllPhones
InternalCSS All IP Phones
Looks like a route pattern, allows digit manipulation

Instead of sending calls outside via a route list, forces
second lookup in Cisco CallManager, 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.
Other Tools
SIP Dial Rules (Cisco Call Manager 5.X)
SIP phones, used with SIP Dial Rules, can place the
function of “pattern recognition” in the phone
Dial Rules perform “local matching” of dialed digits;
sends digit “enbloc” to Call Manager
Applicable only for SIP Phones
SIP phones can be configured with, or without SIP dial
rules
Basic patterns: Digits, Period (Any digit), Comma
(Secondary Dial tone)
Other Tools
SIP dial rules – pattern recognition triggering SIP
invite No dial rule on the phone Dial rule on the phone
En-bloc SIP invite (dial rule match)

Single-digit KPML keypad events
Single-digit SCCP keypad events
En-bloc SIP invite (dial key)
Dial rule:
Match: 1…
1234 1234 1234 1234 Timeout: 0
e.g.: SCCP 7960 e.g.: SIP 7970 e.g.: SIP 7960 e.g.: SIP 7960
Dialing 1234 Dialing 1234 Dialing 1234 <dial> Dialing 1234
Other Tools
SIP dial rules – pattern recognition triggering SIP
invite
Sample Dial rule: “match 1… immediately”
More information in the dial plan chapter of the Cisco Unified

Communications SRND Based on Cisco Unified CallManager 5.0.
www.cisco.com/go/srnd
Other Tools
Time of the day Routing
RTP Call Manager
Cluster
SJC Hunt Pilot 2 Hunt Pilot 1 RTP

Partition DN 8000 DN 8000 Partition
Call coming in Call coming in

Time Period Hunt List Hunt List Time Period
at 9 am PST on 9.00 to 17.00 8.00 to 12.00 at 9 am EST on
Saturday for 8000 Mon-Fri Mon-Fri Sunday for 8000
distributed to Time Period Time Period distributed to
SJC Phones 8.00 to 17.00 Line Group Line Group 8.00 to 17.00 RTP Phones
Sat Sun
Time Period Time Period

No Business No Business
Jul 4th Jul 4th
San Jose (GMT-8) RTP IP Phones RTP (GMT-5)

Time Schedule Time Schedule
Call Manager routes the call IP WAN

based on time of the day
Time Schedule assigned to

“Partition”; partitions remain
active only during particular SJ IP Phones San Jose Site
time configured
Other Tools
Hunt Options
Hunt Pilot
• Matches dialed number for Hunt
call coverage
• Performs digit manipulation Pilot
• Points to Hunt List for routing
Hunt List
Configuration Order
• Chooses path for call routing Hunt
• Points to prioritized Line List
Groups
First Second
Choice Choice
Line Group Line Line
• Performs Digit manipulation
• Points to actual extensions Group I Group II
Endpoints
• IP Phones
• Voicemail Ports
IP Phones Voicemail
Other Tools
Route Filters: The Basics
North American
Numbering Plan:
Route Pattern
9.[2-9]11 The “@” wildcard represents
“9.@” 9.[2-9]XX XXXX all the routes defined in the
9.1 [2-9]XX [2-9]XX XXXX
9.011 !
national numbering plan
Cisco CallManager identifies
tags in each number:
INTERNATIONAL-ACCESS
AREA-CODE
“INTERNATIONAL-ACCESS” OFFICE-NUMBER ...
DOES-NOT-EXIST
AND Route filters are logical
“AREA-CODE” expressions that operate
DOES-NOT-EXIST
on these tags
Useful for blocking 900, pay-
Actual Routes in Cisco CallManager:
9.[2-9]11 per-call, international...
9.[2-9]XX XXXX
Other Tools
Route Filters: Configuration
LIMITATION:
Entire Route Filter Can Contain
up to 1024 Characters (Excludes
“NOT-SELECTED” Fields)
Other Tools
DNA and IDP
Dialed Number Analyzer Tool

Dial plan troubleshooting tool: simulate calls from specific IP
phones/gateways/trunks or from a certain CSS and
observe routing behavior
(Ships as a plugin with CCM 3.3(4), 4.0(1) and later)
International Dial Plan downloads

Allows to create country-specific numbering plans and import
them into CCM to enable use of the
“@” macro
http://www.cisco.com/cgi-bin/tablebuild.pl/IDP
Design Guidelines
Design Best Practices Agenda

Traditional CSS Approach
Line/Device CSS Approach
Multisite Deployments
Mobility Considerations
Example of Composite View - France
Calling Search Route Route
Calling Spaces Partitions Lists Groups Devices
Search
Space Internal
Assigned All IP Phones
to IP Phone Route
Based on 112
Internal Only Patterns
Policy 0.112
Local
Local 0.04XXXXXXXX
National PSTN PSTN PSTN

0.0[1-356]XX
RL RG
National
XXXXXX
International
International 0.00!
0.00!#
<none>
<none>
Example of Composite View – North America
Calling Spaces Partitions Lists Groups Devices
Search
Space Internal
Assigned All IP Phones
to IP Phone Route
Based on 911
Internal Only Patterns
Policy 9.911
Local
Local 9.[2-9]XXXXXX
National PSTN PSTN PSTN

9.1[2-9]XX[2-9]XX
RL RG
National
XXXX
International
International 9.011!
9.011!#
<none>
<none>
Scalability for Centralized Deployments
Partitions
Spaces Lists Groups
SJ911 Route
911
9.911 Patterns
SJ Devices
SJInternal
SJPSTN
9.[2-9]XXXXXX SJ RG
Device CSS 9.1[2-9]XX[2-9]XXXXXX SJ
Dictates: 9.011! RL
SJUnrestricted 9.011!#
• Class of Service SJ Gateways
• Path Selection OnCluster
All IP Phone DNs
NY911
NY Devices
NYInternal
911
9.911
NY RG
NY
# CSS = N x C RL
NYPSTN
NYUnrestricted 9.[2-9]XXXXXX
N = # of Sites NY Gateways
9.1[2-9]XX[2-9]XXXXXX
C = # of Classes 9.011!
of Service 9.011!#

Line/Device CSS Approach
The Line/Device CSS Approach
Line CSS Vs. Device CSS
The Line CSS Has an
Effect on Calls Made
Line CSS from That Line Only
Partition L1
Partition L2 Resulting CSS
Partition L3 Partition L1
Line
Partition L2
Partition L3
Partition D1
Partition D2
Device CSS
Partition D3
Partition D1
<none> partition
Partition D2 omitted for clarity
The Device CSS Has an
Partition D3
Effect on All Calls Made
Device from That Phone
Key Idea
Line CSS “Blocked” Translation Pattern

Line CSS
Selectively Blocks
Block Int’l Partition
Undesired Routes
(According to 0.00!
Resulting CSS
Class of Service)
Line Block Int’l Partition
0.00!
PSTN Partition
...
0.00!
Device CSS
Device CSS
Allows Access to PSTN Partition
All External Routes 0.04XXXXXXXX <none> partition

0.0[1-356]XXXXXXXX omitted for clarity
0.00!
Device “Routed” Route Patterns
Scalability for Centralized Deployments
CSS’s Partitions Route Lists Route Groups
Line CSS BlockedPSTN “Blocked”
Dictates: Internal 9.[2-9]XXXXXX Translation
• Class of Service 9.1[2-9]XX[2-9]XXXXXX Patterns
9.011!
All Lines
9.011!#
Unrestricted OnCluster
All IP Phone DNs
(No Blocks)
Device CSS
Dictates: SJPSTN
SJ Devices
911
• Path Selection 9.911 SJ RG
SJ
SJDevices 9.[2-9]XXXXXX
9.1[2-9]XX[2-9]XXXXXX RL
9.011!
9.011!# SJ Gateways
# CSS = N + C NYPSTN
NY Devices
911
9.911 NY RG
N = # of sites NY
NYDevices 9.[2-9]XXXXXX
C = # of classes 9.1[2-9]XX[2-9]XXXXXX RL
of service 9.011!
9.011!# NY Gateways
Comparison of the Two Methods
CSS’s
it ional Partitions CSS’s
New
Partitions
Trad OnCluster OnCluster
Shared Shared
Site1Internal Site1Emergency Internal BlockPSTN
Site1Local Site1Local Local LocalOnlyPSTN
1 Site1National Site1National National NoInt’lPSTN
Site1International Site1International International NoBlocks
Site2Internal Site2Emergency Site1Devices Site1PSTN

Site2Local
1
Site2Local
2 Site2National Site2National 2 Site2Devices Site2PSTN
Site2International Site2International Site3Devices Site3PSTN

3
…
…
SiteNInternal SiteNEmergency
SiteNLocal SiteNLocal
N SiteNNational SiteNNational
SiteNInternational SiteNInternational N SiteNDevices SiteNPSTN
(N*4) CSS’s ((N*4) + 2) Partitions (N + 4) CSS’s (N + 6) Partitions

CallForward Caveats
Forwarded calls use the CallFwdxxx CSS’s only; these values are
not concatenated with Line or Device CSS
If forwarded calls must have unrestricted
privileges, set the CallFwdxxx CSS’s to
the site-specific Device CSS
If forwarded calls must be restricted to internal numbers only, set
the CallFwdxxx CSS’s to a single, global CSS with only internal
partitions
If forwarded calls must have some intermediate restriction (e.g., no
international calls), this approach may loose efficiency, as
additional site-specific CSS’s will be needed
In CUCM 5.X, a new CSS [Secondary Calling Search Space for
New
CallForwardAll] has been added, allowing for CFA to have all the
classes of service afforded by the line/device approach
Other 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 Softphone (not
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)

Choosing a Dial Plan Approach
Uniform On-Net Dialing
Variable-Length On-Net Dialing with Partitioned Addressing
Variable-Length On-Net Dialing with Flat Addressing
Voice
Cisco Mail Dialing within a site and across
CallManager sites with same number of
Cluster
digits (e.g., 5)
5-Digit Dialing Between Sites
Extensions are globally unique
DN 2XXXX
Easy to design and configure
Limited scalability of
IP WAN the addressing method
Site 1 Site N (number of sites, number
of extensions)
...
DN 3XXXX DN 4XXXX
5-Digit Dialing Within Site
Variable-Length On-Net Dialing (VLOD)
Voice
Cisco Mail Abbreviated dialing within a
E.164 or ‘Site Code’ Dialing Between Sites
CallManager site (four or five digits)

Cluster
Identical extensions (e.g.,
1000) may appear at different
sites
DN 1000
Intersite calls use an “escape
code”
IP WAN (e.g., “9 + full E.164”, or
Site 1 Site N
“8 + site code + extension”)
...
Easier scalability for large
numbers of extensions
and sites
DN 1000 DN 1000
4-Digit Dialing Within Site
Addressing Methods for VLOD
Partitioned Addressing Flat Addressing
Translations_pt
8212.1XXX [Discard PreDot] SJC_Translations_pt NYC_Translations_pt
1XXX [Prefix 8408] ... 1XXX [Prefix 8212]
8408.1XXX [Discard PreDot]
...
IntraSite Intersite IntraSite
IntraSite IntraSite Calls Calls Calls
Calls Intersite Calls
Calls
Internal_pt
SJCPhones_pt NYCPhones_pt
84081XXX 82121XXX
1XXX 1XXX
... ...
• Phone DN’s in different partitions • Phone DN’s in same global partition

• Global Xlations for intersite calls • Per-site translations for intrasite calls
Preliminary Design Questions
How many sites are going to be part of the system?

What are the calling patterns between sites?
What do users dial within a site and to reach another
site?
What transport network is going to be used for intersite
calls (PSTN or IP WAN)?
What (if any) CTI applications are being used?
Is there a desire for a standardized on-net dialing
structure (e.g., using site codes)?

MultiSite Deployments
Use this Model if...
DID ranges do not overlap (based on chosen quantity

of digits for internal calls)
Number of sites is relatively small
Number of sites is not expected to grow significantly in
the future
Composite View
Partitions Lists Groups Devices
Spaces
Site1PSTN_pt
Route
911 Patterns
9.911
9.[2-9]XXXXXX S1 S1
9.1[2-9]XX[2-9]XXXXXX PSTN PSTN PSTN
Site1_css 9.011! RL RL
9.011!#
Site 1
Site 1 Phones Gateways
Extensions: Internal_pt All On-Net DN’s:
10000 This Is Where No
1XXXX 10001
20000 Overlap Can Take
Place!!!
...
Site2PSTN_pt
Site2_css 911 S2 S2
9.911 PSTN PSTN PSTN
Site 2 Phones 9.[2-9]XXXXXX RL RL
9.1[2-9]XX[2-9]XXXXXX Site 2
Extensions:
9.011! Gateways
2XXXX
9.011!#

VLOD with Partitioned Addressing
A global on-net numbering plan using site codes is not

desired (or possible)
Policy restrictions must be applied to on-net intersite
calls (that is, some or all users are not allowed to dial
other sites on-net)
Intersite calls are always routed over the PSTN
CTI applications are not used across sites
Hypothetical Customer Example
GK
US EU
GK GK CCM Cluster
CCM Cluster
GK GK
Gatekeeper
Cluster
San Jose London

+1 408 5551XXX +44 20 77881XXX
... ...
New York Dallas Paris Milan
+1 212 555 1XXX +1 972 555 1XXX +33 1 44551XXX +39 02 66771XXX
OnCluster_pt
Partitions
SJC_Phones_pt NYC_Phones_pt DFW_Phones_pt
Calling
Search
SJC_Internal_css
SJC_Local_css
SJC_LD_css
NYC_Internal_css
NYC_Local_css
NYC_LD_css
... DFW_Internal_css
DFW_Local_css
DFW_LD_css
Spaces
SJC_Intl_css NYC_Intl_css DFW_Intl_css
...
SJC NYC DFW
* Note: If Using the Line/Device CSS Approach, the

Number of CSS’s Can Be Reduced
Line Configuration
2125551000
1000
Intersite Calls Within a Cluster
One Translation
Calling Search Pattern Per Site
Partitions for Intersite Calls
Spaces
Delivers 1XXX
NYCPhones_pt
1000
1000
1001
NYC_Internal
Translations_pt
New York 91212555.1XXX [Discard PreDot][CSS:NYC_Internal]
Extensions: 1XXX
91408555.1XXX [Discard PreDot][CSS:SJC_Internal]
DID’s: (212) 555-1XXX
91972555.1XXX [Discard PreDot][CSS:DFW_Internal]
1000
To D
SJC_Internal SJCPhones_pt
FW_
1000
Inte
1001
rna
San Jose
Extensions: 1XXX
l
Delivers 1XXX
DID’s: (408) 555-1XXX

VLOD with Flat Addressing
Branches interact often

Users dial a ‘site code’ for intersite calls
Intersite calls go over IP WAN
CTI applications are used across sites
International deployment
A global on-net dial plan is needed
Site Code Assignment
GK
US EU
GK GK CCM Cluster
CCM Cluster
GK GK
Gatekeeper
Cluster
San Jose London

408 442
... ...
New York Dallas Paris Milan
212 972 331 392
Internal_pt (contains all the phones)

Partitions
SJC_Xlations_pt NYC_Xlations_pt DFW_Xlations_pt
Calling
Search
SJC_Internal_css
SJC_Local_css
SJC_LD_css
NYC_Internal_css
NYC_Local_css
NYC_LD_css
... DFW_Internal_css
DFW_Local_css
DFW_LD_css
Spaces
SJC_Intl_css NYC_Intl_css DFW_Intl_css
...
SJC NYC DFW
* Note: If Using the Line/Device CSS Approach, the

Number of CSS’s Can Be Reduced
Line Configuration
2125551000
1000
*Note: Line Text Label Is

Not Preserved in SRST Mode
Outgoing inter-cluster WAN/PSTN Calls
Option 1: Eight digit only
Simple, easy to maintain
No automatic PSTN failover (manual redial)
Option 2: Eight digit + E.164 with centralized
PSTN failover
A little more configuration and maintenance
Automatic PSTN failover using central gateway
(SJC in our example)
Possibility to place calls on-net even when dialed
as PSTN
Option 3: Eight digit + E.164 with distributed
PSTN failover
A lot more configuration and maintenance
Automatic PSTN failover using local gateway
Outgoing PSTN/IP WAN Calls: Option 1
Spaces
...
Intercluster_pt
IPWAN IPWAN IP
SJC_Internal_css 8.XXXXXXX RL RG GK WAN
SJC_Local_pt
SJC_Local_css
9.[2-9]XXXXXX
SJC_LD_pt SJC SJC

SJC_LD_css PSTN PSTN PSTN
9.1 [2-9]XX
RL RG
[2-9]XX XXXX
SJC_Intl_css SJC_Intl_pt
9.011!
9.011!#
Calling Search Partitions Route Route
Lists Groups Devices
...
Spaces
Internal_pt
Intercluster_pt
NYC_css
8442.XXXX
8331.XXXX
8392.XXXX
8 011 44 1234 5678 Delivers 8 plus E.164

SJC SJC
SJC_PSTN_pt PSTN PSTN PSTN
SJC_css RL RG
9.[2-9]XXXXXX
9.1 [2-9]XX 2nd
[2-9]XX XXXX Choice
9.011! SJC
Device CSS IPWAN IP
9.011!# IPWAN RG WAN
for San Jose Site RL GK
8.011!
(Line/Device Approach) 1st
Choice
Calling Search Spaces Partitions Route Lists Route Groups Devices
SJC_Intercluster_pt
...
8442.XXXX
8331.XXXX SJC SJC
SJC_Internal_css 8392.XXXX PSTN PSTN PSTN
8 011 44 1234 5678 RL RG
Delivers 8 plusE.164
SJC_Local_css
SJC_Local_pt SJC Gateway
9.[2-9]XXXXXX 2nd Choice
SJC_LD_pt
SJC_LD_css 9.1[2-9]XX SJC st
[2-9]XXXXXX IPWAN 1 Choice
SJC_Intl_pt RL
SJC_Intl_css 9.011! IPWAN IP
8.011! RG GK WAN
NYC_Intrclstr_pt NYC st
8442.XXXX IPWAN 1 Choice GK-Controlled
8331.XXXX RL Intercluster Trunk
NYC_Internal_css
8392.XXXX
8 011 44 1234 5678 2nd Choice
Delivers 8 plus E.164
NYC_Local_css
NYC_Local_pt NYC NYC
9.[2-9]XXXXXX PSTN PSTN PSTN
RL RG
NYC_LD_pt
NYC_LD_css 9.1[2-9]XX NYC Gateway
[2-9]XXXXXX
NYC_Intl_pt
NYC_Intl_css 8.011!
9.011!
Intra/Inter-site Calls Within a Cluster
Calling Search
Spaces Partitions
Delivers 82121XXX
NYC_Translations_pt One Translation

Pattern per Site
1XXX [Prefix 8212]
82121000 for “Local”
Four Digit Dialing
NYC_Internal_css
Internal_pt
82121000
New York 82121001
Site code: 212 Phone DN’s Are
Extensions: 1XXX 84081000 Directly Reachable
84081001
...
84081000
SJC_Internal_css SJC_Translations_pt
1XXX [Prefix 8408]
San Jose
Site code: 408 Delivers 84081XXX
Extensions: 1XXX
Incoming PSTN/IP WAN Calls
Calling Search
Spaces Partitions
One Translation
E164_Translate_pt Pattern
per Site
Incoming_css 212555.1XXX [Disc. PreDot, prefix 8212]
PSTN
408555.1XXX [Disc. PreDot, prefix 8408]
Translation pattern must represent the 972555.1XXX [Disc. PreDot, prefix 8972]
called number as delivered by LEC into GW
Delivers 8sssxxxx
Internal_pt
82121000
82121001
SJC_Internal_css
84081000
84081001
...
Incoming PSTN/ IP WAN Calls (Alternative)
Configure GW to
Strip and Prefix
Relevant Digits
Gatekeeper Configuration
gatekeeper
zone local US cisco.com 10.9.11.1
zone local EU cisco.com 10.20.1.1 ! Replace E.164’s with 8-digit
no zone subnet US default enable ! numbers for Option 1
no zone subnet EU default enable !
zone subnet US 10.9.11.2/32 enable zone prefix US 84081...
zone subnet US 10.9.11.3/32 enable zone prefix US 82121...
zone subnet EU 10.20.1.2/32 enable zone prefix US 89721...
zone subnet EU 10.20.1.3/32 enable zone prefix EU 84421...
zone prefix US 14085551... zone prefix EU 83311...
zone prefix US 12125551... zone prefix EU 83921...
zone prefix US 19725551... !
zone prefix EU 442077881...
gw-type-prefix 1#* default-technology
bandwidth interzone zone US 256
bandwidth interzone zone EU 256
arq reject-unknown-prefix
no shutdown
Voice Mail Integration
Voice
Mail Each eight digit extension is
Cisco
CallManager unique it can be used to
Cluster identify a voicemail box
No need to use masks in
voicemail profile
No translations necessary for
1. VM Access
2. MWI MWI
IP WAN
Site 1 Site N
...
DN 81001234 DN 82001234

Extension Mobility Consideration
Device Mobility Consideration
Extension Mobility Considerations
Requirements
HQ
IP WAN
Device
Profile
PSTN
Call Logged-out Call
PSTN San Jose New York PSTN
Allow users to log in at different sites with a single device

profile
Restrict PSTN calls when logged out
Always route emergency calls via local gateway
Optional: route all PSTN calls via local gateway
Traditional Dial Plan Approach
Per-Site CSS/ Global CSS/ Spaces Partitions Lists Groups
Partition Partition
EM User Line NYPSTN_pt

CSS Contains 9.[2-9]XXXXXX
NY_EM_css 9.1[2-9]XX[2-9]XXXXXX
Internal DNs + 9.011!
PSTN Patterns 9.011!#
Logged-Out NY RG
Line CSS OnCluster NY
Logout_css All IP Phone DNs RL
Only Contains
Internal DN’s NY Gateways
Device CSS NY911_pt

Only Contains NY911_css 911
Emergency 9.911
Patterns
Traditional Dial Plan Approach: Behavior
HQ
EM CSS’s
CFAll: Internal
CFAll: SJ-Nat’l
CFAll: Internal
Line: Internal Line: Internal

Line: SJ-Int’l IP WAN
Device: SJ-911 Device: NY-911
CSS’s CSS’s
Device
Profile
PSTN
Speed Dial: Speed Dial:
San Jose New York 95551234
95551234
Emergency calls routed via local gateway

Other PSTN calls routed via “home” gateway
User dialing habits and speed dials are automatically
preserved
Line/Device Dial Plan Approach
Partition Partition
EM User Line
Empty_pt
CSS Contains EM_css
An Empty
Partition
BlockedPSTN “Blocked”
Logged-out 9.[2-9]XXXXXX Translation
Line CSS Logout_css 9.1[2-9]XX[2-9]XXXXXX Patterns
“Blocks” 9.011!
9.011!#
PSTN Patterns
OnCluster
All IP Phone DNs
Device CSS
Contains All NYDevices_css
NYPSTN
Internal DNs + 911
NY RG
PSTN Patterns 9.911 NY
9.[2-9]XXXXXX RL
9.1[2-9]XX[2-9]XXXXXX
9.011!
9.011!# NY Gateways
Line/Device Dial Plan Approach: Behavior
HQ
PSTN Access Code: 0 PSTN Access Code: 9
EM CSS’s
CFAll:
CFAll:NoPSTN
PAR-all CFAll: NoPSTN
Line:
Line:NoPSTN
<empty> Line: NoPSTN
IP WAN
Device: PAR-all Device: LON-all
CSS’s CSS’s
Device
Profile
PSTN
Speed Dial:
Speed Dial: Paris London 00145678912
00145678912
All PSTN calls are routed via local gateway

User dialing habits and speed dials are not preserved across
different dialing “domains”
Forwarded calls are routed via “home” gateway
Line/Device Dial Plan Approach: Forwarded Calls
EM CSS’s IP WAN
CFAll:
CFAll:NoPSTN
SJ-all CFAll: NoPSTN
Line: NoPSTN
Line: <empty> Line: NoPSTN
Device: SJ-all 1010 1000 PSTN 2000 Device: NY-all

CSS’s CSS’s
Device
Profile
Cell Phone: CallFwdAll
San Jose 14085551234 New York to Cell phone
When a SJ User Logs in at NY Site and Forwards

His Phone to a PSTN Number:
Calls from SJ IP phones use SJ PSTN GW
Calls from PSTN users get hairpinned at the SJ PSTN GW
Calls from NY IP phones cross the WAN and use SJ PSTN GW
AAR Interaction
CAC Denied RTP
Call 914085551010
Call 1010
San Jose New York

IP WAN
Call 1010
Device
Profile PSTN
EM Config. Line Config. Line Config.
DN: 1010 DN: 1000 DN: 2000
Ext. Mask: 4085551010 Ext. Mask: 4085551000 Ext. Mask: 2125552000
AAR is inherently incompatible with EM users moving across branch sites

(regardless of approach)
When EM users log in at a different site, they cannot be reached via AAR
from other sites (DIDs don’t move!)
Ensure that GW CSS’s contain internal numbers only to prevent routing
loops

Extension Mobility Consideration
Device Mobility Considerations
High-level Behavior - CallManager 4.2 only!
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 site
Message displayed on phone screen for a few seconds
when it registers with CallManager:
Device in Home Location
Device in Roaming Location
Device Mobility
Device Pool Changes
Device Pool Common Profile (new)

CallManager Group Softkey Template
Auto-reg CSS Network Hold MoH Audio Source
User Hold MoH Audio Source
Roaming Sensitive Settings MLPP Indication
Date/Time Group MLPP Preemption
Impacts Region MLPP Domain
CAC, MRGL
Media Network Locale
Resource SRST Reference
& SRST
LocationTemplate
Softkey
PhysicalHold
Network Location
MoH Audio Source
Device
User Mobility
Hold GroupSource
MoH Audio
MLPP Indication
Device
MLPPMobility Related Information
Preemption
Impacts MLPP
DeviceDomain
CSS
Dial Plan AAR Group
AAR CSS
Device
Device Mobility
New Concepts
Device Mobility Device Pool Physical Device Mobility
Info Location Group
SJCV1_dmi
10.1.1.0/24
SJC-A_dp
(building A)
SJCD1_dmi
20.1.1.0/24
SJC-B1_dp SJC_phyloc
(building B) (SJC campus)
SJCD2_dmi
20.1.2.0/24
SJC-B2_dp
(building B) US_dmg
RTPV1_dmi
10.2.1.0/24
RTP_dp RTP_phyloc
RTPD1_dmi (RTP campus)
10.2.1.0/24
LONV1_dmi
10.42.1.0/24
LON_dp LON_phyloc EUR_dmg
LOND1_dmi (LON campus)
20.42.1.0/24
The big idea is to track phones based on Subnets
voice subnet: 10.1.1.0/24
data subnet: 20.1.1.0/24 voice subnet: 10.2.1.0/24 voice subnet: 10.42.1.0/24
data subnet: 20.1.2.0/24 data subnet: 20.2.1.0/24 data subnet: 20.42.1.0/24
1000 2000 3000
Note:
Note: When
When roaming
roaming from
from SJC
SJC
to LHR, we are crossing DMGs
to LHR, we are crossing DMGs
SJC RTP LHR Dial
Dial Plan-related
Plan-related information
information
does
does not
not change.
change.
Roaming Sensitive Settings

Change when roaming between physical
locations. DMG not a factor.
Device Mobility Related Information

Changes only when roaming within the
same DMG.
Requirements (Call Manager 4.2)
Denver
(303) PSTN call uses
555-1234 “roaming” gateway
Location CAC is
aware of the call
HQ PSTN WAN bandwidth not
consumed
Dials
9-1-303-
555-1234
RTP SJC
Traditional Dial Plan Approach
Partition Partition
RTPPSTN_pt
9.[2-9]XXXXXX
9.1[2-9]XX[2-9]XXXXXX
RTP_CSS 9.011!
9.011!#
RTP RG
RTP911_pt RTP
DM User Device 911 RL
CSS Contains 9.911
Internal DNs + RTP Gateways
PSTN Patterns OnCluster
+ Emergency All IP Phone DNs
Patterns
SJCPSTN_pt
SJC_CSS SJC RG
9.[2-9]XXXXXX SJC
9.1[2-9]XX[2-9]XXXXXX RL
9.011!
9.011!# SJC Gateways
SJC911_pt
911
9.911
RTP Mobile User at Home Location
RTP
RTP Mobile User at “SJC Roaming” Location
SJC
Traditional Dial Plan Approach: Behavior
Denver PSTN call uses
(303) “roaming” gateway
555-1234 Location CAC is
aware of the call
WAN bandwidth not
consumed
HQ PSTN Adopts the Dialing
Habits of “roaming”
site
Dials
9-1-303-
555-1234
RTP SJC
Traditional Dial Plan Approach (EM Approach)
Partition Partition
RTPPSTN_pt
EM User Line 9.[2-9]XXXXXX
9.1[2-9]XX[2-9]XXXXXX
CSS Contains 9.011!
Internal DNs + 9.011!#
RTP_Line_css RTP RG
PSTN Patterns RTP
RTP911_pt
911 RL
9.911
Device CSS RTP Gateways
RTP911_css
Only Contains OnCluster
Emergency All IP Phone DNs
Patterns
SJCPSTN_pt
9.[2-9]XXXXXX
9.1[2-9]XX[2-9]XXXXXX
SJC_Line_css 9.011! SJC RG
9.011!# SJC
RL
SJC911_pt
911
SJC911_css 9.911 RTP Gateways
Traditional Dial Plan (EM Approach): Behavior
Denver
(303) PSTN call uses
555-1234 “home” gateway
Location CAC is
aware of the call
G.729 CODEC
HQ PSTN uses more WAN
bandwidth
Preserves the
G.729 dialing habits
Dials
9-1-303-
555-1234
RTP SJC
Line/Device Dial Plan Approach
Partition Partition
BlockedPSTN “Blocked”
Line CSS 9.[2-9]XXXXXX Translation
“Blocks” SJC_css 9.1[2-9]XX[2-9]XXXXXX Patterns
PSTN Patterns 9.011!
9.011!#
OnCluster
All IP Phone DNs
Device CSS
Contains All SJCDevices_css
SJCPSTN
Internal DNs + 911
SJC RG
PSTN Patterns 9.911 SJC
9.[2-9]XXXXXX RL
9.1[2-9]XX[2-9]XXXXXX
9.011!
9.011!# NY Gateways
Line/Device Dial Plan Approach: Behavior
Denver PSTN call uses
(303) “roaming” gateway
555-1234 Location CAC is
aware of the call
WAN bandwidth not
consumed
HQ PSTN Adopts the Dialing
Habits of “roaming”
site
Dials
9-1-303-
555-1234
RTP SJC
Line/Device Dial Plan Approach: Forwarded Calls
IP WAN
CFAll: SJ-all
Line: <none>
Device: SJ-all 1000 PSTN 2000 Device: NY-

NY-all
CSS’s
Cell phone: CallFwdAll

CallFwdAll
San Jose 14085551234 New York to
to Cell
Cell phone
phone
When a SJ user moves to NY site and forwards his

phone to a PSTN number:
Calls from SJ IP phones use SJ PSTN GW
Calls from PSTN users get hairpinned at the SJ PSTN GW
Calls from NY IP phones cross the WAN and use SJ PSTN GW
AAR Interactions
CAC Denied RTP Call
Call 1010
1010
Call 914085551010
San Jose New York

IP WAN
Call
Call 1010
1010
PSTN
Line config. Line config. Line config.
DN: 1010 DN: 1000 DN: 2000
Ext. Mask: 4085551010 Ext. Mask: 4085551000 Ext. Mask: 2125552000
AAR is inherently incompatible with device mobility

across sites (same as for EM across sites)
When DM users move to different site, they cannot be
reached via AAR from other sites (DIDs don’t move!)
Ensure that GW CSS’s contain internal numbers only to
prevent routing loops
Conclusions
Conclusions
General Recommendations
KEEP IT SIMPLE!
Plan for future growth
Use Gatekeeper-controlled Intercluster Trunks when
more than two Cisco CallManager clusters are present
Normalize DNs to the full E.164 when using
Gatekeeper for dial plan resolution
Conclusions
Summary: What Did We Cover?
Planning an enterprise IP telephony dial

plan—uniform vs. variable-length dialing
Enterprise IP telephony dial plan
elements—the tools and how to use them
Design recommendations in different areas
of dial plan:
Classes of service
Dialing architectures
Addressing methods
For More Information
More Details in: Chapter
10 of the IP Telephony
SRND for Cisco
CallManager 4.x and 5.0,
Available at:
http://www.cisco.com/go
/srnd/
Meet the Experts
Unified Communications Technologies
Janet Byron
Technical Leader
Jan-Willem Ruys
Consulting Engineer
Luc Bouchard
Technical Marketing Engineer
Mariano O'Kon
Consulting Systems Engineer
Paul Tindall
Consulting System Engineer
Richard Dodsworth
Meet the Experts
Unified Communications Technologies
TJ Schuler
Technical Marketing Engineer
Tobias Neumann
Tony Mulchrone
Technical Mktg Eng
Yves Torjman
Consulting System Engineer
Zorela Sora
Consulting Engineer
Recommended Reading
BRKUCT - 3012
Cisco
CallManager
Fundamentals
Cisco IP
Telephony:
Planning, Design,
Implementation,
Operation, and
Optimization
Available in the Cisco Company Store

Appendix
Reference material
follows
Appendix
Classes of Service for SRST (COR)

CallManager best match logic
Voice over PSTN
Tail End Hop Off
VLOD information
Trunks
Rationale
Class of Service SRST Router Cisco
CallManager
Cluster
COR
Unrestricted
config IP WAN
Internal
+ Local Central Site
PSTN Sydney
InternalOnly
When WAN connection is lost, Cisco CallManager

classes of service are also lost All remote phones
gain unrestricted PSTN access
COR configuration on branch router allows preservation
of classes of service in SRST mode
COR Logic (1)
2
Check All the “Locks”
of the Outgoing Corlist
1 Against the “Keys” of dial-peer voice 2 pots
Choose Outgoing
Dial-Peer Based on the Incoming Corlist destination-pattern 1..
Matching Pattern
corlist outgoing c2
Member A
dial-peer voice 1 voip Member B
corlist incoming c1
Call 100
Member A
Member B
Member C dial-peer voice 3 pots
destination-pattern 2..
corlist outgoing c3
Member A
3
Incoming Corlist Has All the Member B
Needed “Keys”
(i.e., Outgoing Corlist Is a Member D
Subset of Incoming);
The Call Can Be Completed
COR Logic (2)
2
Check All the “Locks”
1 of the Outgoing Corlist dial-peer voice 2 pots
Choose Outgoing
Against the “Keys” of
Dial-Peer Based on destination-pattern 1..
the Incoming Corlist
Matching Pattern
corlist outgoing c2
Member A
dial-peer voice 1 voip Member B
corlist incoming c1
Call 200
Member A
Member B
Member C dial-peer voice 3 pots
destination-pattern 2..
corlist outgoing c3
Member A
?
3 Member B
Incoming Corlist Is Missing
Some “Keys” (i.e., Outgoing Member D
Corlist Is Not a Subset of
Incoming Corlist); STOP
The Call Cannot Be Completed
How to Recreate “Partitions” and “CSS’s”
Incoming COR Lists (“CSS’s”) Outgoing COR Lists (“Partitions”)
Other dial-peer voice 1 pots

Phones destination-pattern 112
call-manager-fallback corlist outgoing EmPt
cor incoming InternalCSS default Member Emergency
Member Emergency
dial-peer voice 2 pots
destination-pattern 01........
corlist outgoing LocalPt
cor incoming 1 LocalCSS 2001
Member Local
Member Emergency
Member Local
2001 dial-peer voice 3 pots
destination-pattern 0[2-6]........
cor incoming 2 IntlCSS 2002 corlist outgoing LDPt
Member Emergency Member LD
Member Local
2002 Member LD dial-peer voice 4 pots

Member Intl destination-pattern 000T
corlist outgoing IntlPt
Member Intl
Step-by-Step Guidelines
Define meaningful tags (Emergency, VMail,

Local, LD, Intl)
Define “simple” COR lists (with only one tag as
a member) to be used as “partitions”
Assign the “partitions” as outgoing COR lists to
the appropriate POTS dial peers
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
COR: Cisco IOS Configuration Basics
STEP 1 STEP 2 STEP 3

dial-peer cor list c1 dial-peer voice 1 voip
dial-peer cor custom member A corlist incoming c1
name A member B session target ipv4:1.1.1.1
name B member C dtmf-relay h245-alpha
name C
name D dial-peer cor list c2 call-manager-fallback
member A cor incoming c2 default
member B cor incoming c3 1 2001
cor incoming c3 2 2004-2007
dial-peer cor list c3
member A dial-peer voice 2 pots
member B corlist outgoing c3
member D destination-pattern 1..
port 1/0:23
Define “Tags” for Create COR Lists with Associate Incoming and
COR List Members Various Combinations Outgoing COR Lists with
of Tags Voip/Pots Dial-Peers and
Cisco CallManager-Fallback
SRST COR Limitations
Maximum number of “cor incoming” statements under

call-manager-fallback is 5 (plus default) in SRST 2.1
(Cisco IOS 12.2(13)T14)
Maximum number of “cor incoming” statements under
call-manager-fallback is 20 (plus default) in SRST 3.0
(Cisco IOS 12.2(15)ZJ3)
If “manager” phone DN’s are not consecutive and the
SRST site is relatively large, this may become an
obstacle to establishing appropriate classes
of service
If a device/DN is has NO corlist assignment, it is
essentially unrestricted
Appendix

Voice over PSTN
Tail End Hop Off
VLOD information
Trunks
Example (1)
Configured Route Patterns
User’s Dial String: 1111
1211
1[23]XX
Cisco CallManager Actions: 131
1[0-4]XX
13!
Example (2)
User’s Dial String: 1111 Might Match
<Off Hook> 1211 Might Match
1[23]XX Might Match
Cisco CallManager Actions: 131 Might Match
Provide Dial Tone 1[0-4]XX Might Match

Wait
13! Might Match
Digit analysis: match(fqcn="9195555644", cn="15644",

pss="PA:Line1:Cisco:Local:Long Distance:International", dd=”")
Digit analysis: potentialMatches=PotentialMatchesExist
Example (3)
User’s Dial String: 1111 Might Match
1 1211 Might Match
1[23]XX Might Match
Break Dial Tone 1[0-4]XX Might Match

Wait
13! Might Match

pss="PA:Line1:Cisco:Local:Long Distance:International", dd=”1")
Example (4)
User’s Dial String: 1111 Doesn’t Match
13 1211 Doesn’t Match
1[23]XX Might Match
Wait 1[0-4]XX Might Match
13! Might Match

Example (5)
1[23]XX Might Match
Cisco CallManager Actions: 131 Match!
Keep Waiting; More 1[0-4]XX Might Match

Digits Might Cause a
Different Pattern to Match 13! Match! and Might Match

Example (6)
1[23]XX Match!
Cisco CallManager Actions: 131 Doesn’t Match
Keep Waiting; More 1[0-4]XX Match!

Digits Might Cause a
Different Pattern to Match 13! Match! and Might Match

Example (7)
1311<timeout> 1211 Doesn’t Match
1[23]XX Match!
Cisco CallManager Actions: 131 Doesn’t Match
Extend Call to the 1[0-4]XX Match!

Best Match
13! 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 ☺
Example (8)
1311<Timeout> 1211 Doesn’t Match
Matches 200 Digit Strings 1[23]XX Match!

Matches 500 Digit Strings 131 Doesn’t Match
Matches ∞ Digit Strings, However
1[0-4]XX Match!
for the Purposes of Closest Match
Routing in This Case, This 13! Match!
Matches 100 Digit Strings Because
You Only Consider the Number of
Potential Strings Given the
Number of Digits Dialed
Analogy
Rita Wants to Call Dave Miami Yellow Pages

Dave 305 555 5000
To Do So, She Needs to
Know Dave’s Number
Dave Lists His

Number in a Directory
Dave
Rita
305 555 5000
Analogy
To Look up Numbers,
Rita Looks Through the Miami Yellow Pages
Directories She Owns Dave 305 555 5000
If She Doesn’t Have

the Right Directory…
Rita’s List of Directories

Dallas White Pages
Outlook Address Book
Little Black Book
…She Can’t Place the Call

Dave
Rita
305 555 5000
Analogy
But If She Has the Miami Yellow Pages

Directory Dave Has Dave 305 555 5000
Listed His Number in…
Rita’s List of Directories

Dallas White Pages
Miami Yellow Pages
Little Black Book
…the Call Will Go Through

Dave
Rita
305 555 5000
Analogy
The Directory in Which Dave’s Number Miami Yellow Pages

Is Listed Is His Number’s Partition Dave 305 555 5000
Rita’s List of Directories The List of Directories in

Which Rita Looks up
Dallas White Pages Numbers Is Her Calling
Miami Yellow Pages Search Space
Little Black Book
Dave
Rita
305 555 5000
Appendix

Voice over PSTN
Tail End Hop Off
VLOD information
Trunks
What Is Voice over the PSTN (VoPSTN)?
A variation on the Centralized Call Processing

deployment model, where all intersite voice goes over
the PSTN (not the WAN)
We are not “promoting it”: merely setting requirements
and expectations.
We do see that it could serve as a “beach head” to win
over some customers
There are several, fundamental limitations
Relies on AAR configuration
VoPSTN Using AAR
Global Considerations
No Streaming of Audio to A Lot of Dial Plan Work Is
Central Site, Thus No: Required AAR Work + Each
• Centralized MoH SRST Router Needs to Know
• Centralized conferencing How to Reach All Other
• Centralized IVR Branches (Full Mesh)
• CTI apps
New York New York

WAN *Must* Be Location: NY1
QoS-Enabled, and Only Signaling Region: NY1
Highly Available Traffic Goes
(No Exceptions) over the WAN
Phone B
1234
IP WAN Does not
Work on
WAN
X Failure!!!
Phone A Phone C
2345 1235
Location: SF PSTN New York Location: NY2
Region: SF Region: NY2
VoPSTN Using AAR
Intersite Calls
This Is a New Missed Calls List Will Show CLID
Call; A Different of Calling Phone; All Intersite Calls
CDR Record Ring as External, Just Like Any
User Dials 1234. PSTN Call; Destination Phone
Will Be
String 9 1 212 555 1234 Is MUST Be DID Number
Generated.
Sent Through This
Calling/Called
Phone’s AAR Calling
Numbers Are New York New York
Search Space
the Only Links Location: NY1
AAR Calling Search
to the Original Region: NY1
Space Must Match a
Call
RP/RL/RG That Strips
User Sees the Off Net Access Phone B
“Network Code (i.e.: “9”) 1234
Congestion,
Rerouting” IP WAN
4
23
51
55
121
255
512
34
Phone A Phone C
2345 1235
Location: SF
Region: SF PSTN New York Location: NY2
Region: NY2
VoPSTN Using AAR
Non-Unity™ Centralized Voicemail
Note: RDNIS Required End to End for CFB, CFNA to a PSTN
Automated Mail Box Selection! Number (e.g.: 1 408 555 1000)
Note Hairpin of
Pilot Number: 408 555 1000 Call! Also Happens New York New York
on Transfers; Location: NY1
Affects Gateway Region: NY1
Sizing
Phone B
1234
0
00
IP WAN
555
51
55
1
08
000
User Dials
4
14
23
1234
51
55
51234
Phone A 55 Phone C
2345 1235
Location: SF
Region: NY2
VoPSTN Using AAR
Shared Lines Considerations
AAR Should Not Be DN 1234 Must Be in a
Used to Reach Site-Specific Partition,
User Dials 1234; Remote Shared Not Included in Off-Site
GW’s CSS Must
1234 Matches a TP in the Lines, as It Would Calling Search Spaces
Include Partition
Phone’s Dialing Plan, Launch Multiple
Containing the
Expanding to Parallel PSTN Calls
Shared Line,
912125551234 New York
Making Both 1234
Phone’s Calling Search Phones Ring
Space Must Match a 1234
RP/RL/RG That Strips
the Off Net Access New York
Code (i.e.: “9”) Location: NY1
IP WAN Region: NY1
4
23
51
55
121
255
512
34
Phone A Phone C
2345 1235
Location: SF
Region: NY2
VoPSTN Using AAR
Summary
Only accommodates Does not work during

SCCP destinations WAN interruption
RDNIS required for No centralized MoH
centralized VMAIL
No centralized conferencing
Extension mobility not possible
All transferred calls are hairpinned
No difference between PSTN and
All calls forwarded to outside locations
Interbranch calls (one ring type)
are hairpinned
Two CDR records for every call
If you tailor the WAN for signaling
(minimum); more if CallFwd invoked
only, no attendant console in remote
All intersite calls display Network sites, due to directory access BW
Congestion, rerouting
QoS is REQUIRED on the WAN
No shared line support
High availability is required on the
across branches
WAN: SRST does not make up for a
All destinations must be DID bad link, only a dead one
VoPSTN Using Dial Plan
Key Points
Cisco
CallManager
DN’s at each site are placed in
Cluster different partitions
Relies on PSTN route patterns
to call other sites
Central
Site Partition 1
For Cisco CallManager, all
Voice Media Signaling
calls are external calls
No “on-net” features across
PSTN IP WAN sites (e.g.: CallBack)
No easy migration to fullblown
Remote VoIP
Sites
NOTE: Abbreviated dialing
... possible with translation rules

on branch GW’s
Partition 2 Partition 3 Partition N
Appendix

Voice over PSTN
Tail End Hop Off
VLOD information
Trunks
Tail-End Hop-Off (TEHO)
What Is It?
Cisco Cisco
CallManager CallManager
(408) 555-1234 Cluster 1 (646) 555-6789
Cluster 2
Calls
9 1 646
5556789 Gatekeeper
GK
San Jose PSTN San Jose New York New York PSTN
Local Call 1 2 Local Call
IP WAN
Calls to a Remote PSTN Number
Use the IP WAN and Terminate at the
GW Closest to the Destination
Calls 1 Within a Cisco CallManager Cluster
9 1 408 Seattle
Seattle PSTN 5551234 2 Across Cisco CallManager Clusters
Intracluster: Seattle to San Jose
Route Pattern 1
User Calls Route Pattern Match
914085551234 91408[2-9]XXXXXX No Digit Manipulation
2
Seattle Route List Select Route Group
Based on Priority
SE-SJ-RL
1st 2nd
Choice Choice
3a 3b
Route Through SJ GW Backup Path
As a Result Call Is Local Route Group Route Group
Use SE GW
CCM Strips off ‘9’ SJ-RG SE-RG CAC Not Required
CAC May Reject Call
4b
4a GW Strips ‘9’
SJ Gateway Presents Then Presents Call
PSTN
Call to PSTN in SJ to PSTN in SE
(408) 555 1234

San Jose
Intracluster: Route Patterns for Seattle
Route Patterns Route Patterns

Route Pattern
9.011!, 9.011!# 911, 9.911
9.1 408 [2-9]XX XXXX
9.1 [2-9]XX [2-9]XX XXXX 9.[2-9]XX XXXX
Route List Route List

“SE-SJ-RL” “SE-SE-RL”
1st 2nd
choice choice
Route Group Route Group
“SJ-RG” “SE-RG”
San Jose Seattle

Gateway Gateway
PSTN PSTN
Intracluster: Composite Dial Plan for Seattle
Spaces
CSS
Assigned
Internal
to IP Phone
Based on
IP Phones, VM
Policy and
Geography SE_911
Internal_SE Seattle
911
Gateway
9.911
SE-SE
SE_Local SE-RG PSTN
Local_SE RL
9.[2-9]XXXXXX
2nd
SE_National Choice
National_SE 9.1 [2-9]XX [2-9]XX XXXX
9.1 408 [2-9]XX XXXX SE-SJ

SJ-RG PSTN
RL
International_SE SE_International 1st San Jose
Choice Gateway
9.011!
9.011!#
Intercluster: San Jose to New York
San Jose Gatekeeper New York

Calls Cisco Cisco (646) 555-6789
9 1 646 CallManager CallManager
5556789 GK
Cluster Cluster
IP WAN
San Jose New York
Gateway Gateway
Step 1 Step 2 Step 3

Route Pattern Route Pattern
9.1 646 [2-9]XX XXXX gatekeeper 1 646 [2-9]XX XXXX
1st 2nd zone prefix NY
choice choice 1646.......
Anonymous SJ NY
Device Gateway Gateway
Intercluster: Composite Dial Plan for San Jose
Spaces
CSS
Assigned Internal
to IP Phone IP Phones, VM
Based on
Policy and SJ_911
Geography Internal_SJ San Jose
911
Gateway
9.911
SJ-SJ
SJ_Local SJ-RG PSTN
Local_SJ RL
9.[2-9]XXXXXX
2nd
SJ_National Choice
National_SJ 9.1 [2-9]XX [2-9]XX XXXX
9.1 646 [2-9]XX XXXX SJ-WAN WAN- IP

RL RG GK WAN
International_SJ SJ_International 1st Anonymous
Choice Device
9.011!
(Gatekeeper)
9.011!#
Intercluster: Dial Plan for New York
Spaces
Incoming
Calls from
Anonymous
Device
Internal
(Gatekeeper)
IP Phones, VM
New York
GK
From_IP_WAN Gateway
NY_TEHO
NY-NY
9.1 646 [2-9]XX XXXX NY-RG PSTN
RL
Note: To Avoid Routing Loops, Do Not Include

Partitions That Contain IP WAN Routes in the
“From_IP_WAN” Calling Search Space
Appendix

Voice over PSTN
Tail End Hop Off
VLOD information
Trunks
View of Partitions/Calling Search Spaces
Calling Search
Spaces Partitions
Calling
Search
Space SJC
SJC_Phones_pt IP Phones
Assigned
to IP Phone
Based on On-Cluster
SJC_Internal_css OnCluster_pt
Policy Translations
Shared
Shared_pt Resources
SJC_Local_css (Voice Mail,
Media resources)
SJC_911_pt
SJC SJC_LD_css
SJC_Local_pt External
Route
Patterns
SJC_Intl_css SJC_LD_pt
SJC_Intl_pt
Outgoing PSTN/Gatekeeper Calls
1. Outgoing Calls
Route Patterns Route Route
Site 1 9.XXXYYYZZZ
Group
Route
9.XXXX List
9.YYYYYY Group
PSTN
IP
Site 2 GK WAN
On_Cluster Incoming
...
Translation Patterns Calling

9.XXXYYYZZZ [Discard]
9.XYZXYZXXXX [Discard] Search Space
Site N
Outgoing PSTN/Gatekeeper Calls
Calling Search Spaces Partitions Route Lists Route Groups Devices
SJC_Phones_pt
SJC IP Phones
SJC SJC
SJC_Internal_css 911
PSTN PSTN PSTN
911
RL RG
SJC_Local_pt SJC Gateway
SJC_Local_css 9.[2-9]XXXXXX 2nd Choice
SJC_LD_pt
SJC_LD_css 9.1[2-9]XX SJC
[2-9]XXXXXX IPWAN 1st Choice
San Jose SJC_Intl_css
SJC_Intl_pt RL
IP
9.011! IPWAN
RG GK WAN
NYC_Phones_pt
NYC IP Phones
NYC
IPWAN 1st Choice GK-controlled
NYC_Internal_css 911 Intercluster Trunk
911
RL
2nd Choice
NYC_Local_pt
NYC_Local_css 9.[2-9]XXXXXX NYC NYC
PSTN PSTN PSTN
NYC_LD_css
NYC_LD_pt
RL RG
9.1[2-9]XX
[2-9]XXXXXX NYC Gateway
New York NYC_Intl_css
NYC_Intl_pt
9.011!

Site 1 9.XXXYYYZZZ
Group
Route
9.XXXX List
9.YYYYYY Group
PSTN
2. Intersite
Calls IP
Site 2 GK WAN
On_Cluster Incoming
...

Site N
Calling Search
Spaces Partitions
Delivers 1XXX
NYCPhones_pt
1000
1000
1001
NYC_Internal_css
Translations_pt
New York 91212555.1XXX [Discard PreDot] One Translation
Extensions: 1XXX Pattern per Site
DID’s: (212) 555-1XXX for Intersite Calls
1000
SJC_Internal_css SJCPhones_pt
1000
1001
San Jose
Extensions: 1XXX Delivers 1XXX
DID’s: (408) 555-1XXX To DFW_Internal
Incoming PSTN/Gatekeeper Calls

Site 1 9.XXXYYYZZZ
Group
Route
9.XXXX List
9.YYYYYY Group
PSTN
IP
Site 2 GK WAN
On_Cluster Incoming
...

3. Incoming Calls
Site N
Incoming PSTN/Gatekeeper Calls
Calling Search
Prepend “9” to Match Spaces Partitions
Translation Patterns
PSTN
OnCluster_pt One Translation
Incoming_css 91408555.1XXX [Discard PreDot] Pattern per
IP Site’s E.164
WAN GK 91212555.1XXX [Discard PreDot] Address Range
SJC_Internal_css SJC_Phones_pt
SJC IP Phones
SJC
Delivers 1XXX
NYC_Phones_pt
NYC_Internal_css To
NYC IP Phones
DFW_Internal_css
NYC
Delivers 1XXX
Gatekeeper Configuration
gatekeeper
zone local US cisco.com 10.9.11.1
zone local EU cisco.com 10.20.1.1
no zone subnet US default enable
no zone subnet EU default enable
zone subnet US 10.9.11.2/32 enable
zone subnet US 10.9.11.3/32 enable
zone subnet EU 10.20.1.2/32 enable
zone subnet EU 10.20.1.3/32 enable
zone prefix US 14085551...
gw-type-prefix 1#* default-technology
bandwidth interzone zone US 256
bandwidth interzone zone EU 256
arq reject-unknown-prefix
no shutdown
Voice Mail Integration
Voice
Mail Both SCCP- (Unity) and SMDI-
Cisco
CallManager DN 8001 based Voice Mail systems can
Cluster be used
Voice mail boxes need a
unique DN
Need to “expand” DNs when
1. Digit
2. MWI accessing VM
Expansion
Translation
IP WAN MWI messages from VM
Site 1 Site N system need to be “translated”
to match appropriate
DN/partition
...
DN 1000 DN 1000
Voice Mail Integration: Digit Expansion
Use the “Voice Mail Box Mask” Field in Each Vm

Profile to Uniquely Identify the Voice Mail Boxes
(E.G., Using the Full E.164 Number)
Voice-Mail Integration: MWI Translation
Calling Search
Spaces Partitions
Prefix “91” to
VM_Xlate_pt the E.164 Number
VM_Xlate_css XXXXXXXXXX [Prefix 91] in Order to Reuse
the “OnCluster”
Voice Mail Translations
Ports Delivers “914085551000”
Incoming_css OnCluster_pt
PSTN
Need to Set the

SJC_Internal_css SJC_Phones_pt “MultiTenantMwiMode”
Service Parameter
SJC IP Phones
SJC to TRUE to
Enable MWI
Delivers “1000” Translation
Appendix

Voice over PSTN
Tail End Hop Off
VLOD information
Trunks
External Routes in Cisco Call Manager
Non-GK Controlled ICT
Inter-Cluster Trunk
San Backup 1
Jose 4 Backup New
3 6 York
HQ
2 5
Publisher Publisher
CM Group: SJC 1 CM Group: NYC 4

SJC 2 NYC 5
SJC 3 NYC 6
Redundancy is built into ICT (1 ICT needed instead of 3)

Non-GK Controlled ICT
Calls to a Non GK controlled inter-cluster trunk are load

shared in a round robin fashion among the configured
peer signaling addresses
For example, the first call is routed to peer transport
address one, next call to peer transport address two,
third call to transport address three, fourth call to
transport address one, and so forth
GK Controlled ICT
San GK controlled Inter-Cluster Trunk

Backup 1 GK GK
Jose
3
HQ
2
Publisher
GK GK
CM Group: SJC 1 GUP
Gatekeeper Cluster
SJC 2
SJC 3
Easier Administration and Scalable (up to 100 Clusters)
All Call Managers in CM Group register with GK, thus
providing redundancy and load balancing
Additional H.323 trunk defined for added redundancy when
GK is not unavailable at initial registration or during reset
GK-Controlled Trunks: Automatic Reroute
1st Gatekeeper
Choice GK
ACF gatekeeper
ARQ ACF zone local SJC cisco.com
ARQ zone local NYC cisco.com
zone prefix SJC 140855534..
Call Setup zone prefix SJC 14085557...
SJ NY zone prefix SJC 131055598..
[...]
2nd
zone prefix NYC 16465551...
ARJ Triggers CM to
Choice GK zone prefix NYC 131255568..
Use the Next Route
zone prefix NYC 120255524..
Group in the Route
ARQ ARJ List (PSTN Gateway) [...]
gw-type-prefix 1#* default-
technology
Call Setup bandwidth interzone zone SJC 480
SJ NY
PSTN
SJ Gateway NY Gateway
H.225 Trunks
Allows a mix- Cisco Applications
and-match of Cisco Call
Manager
CallManager clusters and Cluster Gatekeeper
H.323 gateways
GK
Auto discovers if remote
endpoint is H.323 gateway H.323
or Call Manager
IP PSTN
All calls across the WAN WAN
are controlled by the same H.323
gatekeeper Gateway
Facilitates migration
from toll-bypass
networks
Cisco CallManager PBX

BRKUCT-3012 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential Cluster 183
SIP Trunks
CallManager 4.x CallManager 5.0
SIP Trunk SIP Trunk
Early-media only and s/w MTP is required. Delay-media (h/w – s/w MTP) and early-
media (s/w MTP).
Only G.711 codec allowed.
MTP will be inserted dynamically if needed
RFC2833 only for OOB to 2833 conversion or early-
No Video Support, Subset of SIP media is used.
Messages RFC2833, KPML, Unsolicited-notify
SIP Trunks: Redundancy
Direct Integration
San SIP Trunk

Backup 1 4 Backup New
Jose
3 6 York
HQ
2 5
Publisher Publisher
CM Group: SJC 1 CM Group: NYC 4

SJC 2 NYC 5
SJC 3 NYC 6
NO Redundancy
built into SIP Trunk
Configuration
DNS SRV Records
Service (SRV) records allows:
Using several servers for single DNS domain
Designating some servers as primary and some as backups
Moving TCP/IP services from one host to other
DNS Integration
San Backup 1
Jose 4 Backup New
3 SIP Trunk SIP Trunk 6 York
HQ
2 5
Publisher DNS Publisher
FQDN: SJC-Cluster.com FQDN: NYC-Cluster.com
For any SRV query for

NYC-Cluster.com; DNS
returns a Host Name or
IP Address of Servers
H.323 Gateways with Centralized Processing
San
Jose .3 .1
HQ
.2
WAN
Publisher
Dial Peer Configuration

Be sure to configure a dial peer for each
CallManager server in the redundancy dial-peer voice 1 voip
group/device pool assigned to the destination-pattern 1...
preference 1
Gateway in CM session target ipv4:10.10.10.1
dial-peer voice 2 voip
Ensure that they match on both sides destination-pattern 1...
preference 2
session target ipv4:10.10.10.2
dial-peer voice 2 voip
destination-pattern 1...
preference 3
session target ipv4:10.10.10.3

Advanced Dial Plan Design For Ip Telephony Networks

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Advanced Dial Plan Design For Ip Telephony Networks

Загружено:

Авторское право:

Доступные форматы

Advanced Dial Plan

Visit the World of Solutions on Level -01!

Please remember this is a ‘No Smoking’ venue!

Please switch off your mobile phones!

• To explore the design and implementation

• Aspects we will cover:

Dial Plan Elements

A few things we all like in a good dial plan:

Remember: the best tool to start with is this:

Q: Ok, how about 4 digit uniform dial plan?

Because each time you call extensions 1120 Paris

Lyon Marseille Lille Brest

Q: Great! How about that new office we want to get

Lyon Marseille Lille Brest Nice

Lyon Marseille Lille Brest Nice

Lyon Marseille Lille Brest Nice

Toulouse Clermont-Ferrand Strasbourg Metz Bordeaux

Toulouse Clermont-Ferrand Strasbourg Metz Bordeaux

Cisco CallManager Call Routing Logic

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

Cisco CallManager matches the most specific pattern

Cisco CallManager Call Routing Logic

Cisco CallManager Routes Two Basic Call Types:

MGCP H.323 Gateways Inter-Cluster Trunk GK-Controlled SIP Trunk

• Cisco IOS • Other Cisco

IP Phones Voice messaging

Software phone Auto-attendant

endpoints applications Non-media

Cisco CallManager Call Routing Logic

8001 Voice Mail Ports

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

Calling Search Space Most specific patterns

User dials 23XX

Cisco CallManager Call Routing Logic

User Dials 1234

Call is automatically re-routed using number configured

YES YES AAR Group YES Prefix digits from

NO NO Route the Call using

DNs are assigned to

Be mindful of this for

User Dials 1234

User Dials 1234

AAR Group YES Prefix digits from

NO NO Route the Call using

Reroutes calls to unregistered DN’s using number specified in “Call

CFUR CSS cannot be expected to be able to

When looping call is dropped, caller hears fast-

Cisco CallManager Call Routing Logic

Looks like a route pattern, allows digit manipulation

En-bloc SIP invite (dial rule match)

En-bloc SIP invite (dial key)

More information in the dial plan chapter of the Cisco Unified

SJC Hunt Pilot 2 Hunt Pilot 1 RTP

Call coming in Call coming in

Time Period Time Period

San Jose (GMT-8) RTP IP Phones RTP (GMT-5)

Call Manager routes the call IP WAN

Time Schedule assigned to

Dialed Number Analyzer Tool

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