BT Looping Dial Plan

Overview
Paul Clilverd
Cisco AS Connected Experience COE
15th June 2015
Agenda
• Looping Dial Plan Overview
• PSTN Country Dial Plans
• Feature Processing
• Leaf Cluster & Country Models
• Looping Dial Plan Walkthrough
• Troubleshooting
Looping Dial Plan
Overview
Overview of Looping Dial Plan
The new looping dial plan can be implemented for customers using CUCM 10.x,
on either a CUCDM 10 or CUCDM 8.1.4 ERx platform.
It utilises two new features which are available within CUCM 10.x:
• CSS Hierarchy
• Named Local Route Groups (Device Based Routing)
• Based on Call Type rather than just dialled number
This presentation will focus on the implementation of the new looping dial plan
within BT’s CUCDM 8.1.4 ER2 solution and later 8.1.X releases.
Overview of Looping Dial Plan

The principles of the looping dial plan utilises the following stages:
• Dial Plan determination (Internal or PSTN Dial Plan)
• Country Dial Plan (PDD, Normalisation)
• Feature Processing (Class of Service, Time of Day, CLIR/CLIP)
• Routing
Overview of Looping Dial Plan
Overview of Looping Dial Plan
The looping dial plan is therefore implemented, as detailed below:
PSTN Country Dial Plans
PSTN Country Dial Plans
Each country deployed for the looping dial plan, now consists of a single
partition, configured in the “All Day” time schedule, that contains all the
patterns responsible for dialling within that respective country.
Should the country dial plan also have local dialling capabilities, a
second local dialling partition is also created. This local dialling
capability is still configured for each individual location.
Country Dial Plan Objectives
The main objectives of the each country’s translation patterns are:
• Eliminate Post Dial Delay (PDD)
• Normalise the Called Party Number
• Prefix the first feature code for call processing

This is also the same for local dialling, as a local call will be handled in
exactly the same way as any other PSTN outbound call.
Feature Processing
Feature Processing
The concept of feature processing within the looping dial plan, is to link
together a number of separate features, so that these features form a
feature chain which can be processed in a sequential manner.
A feature within this change must adhere to certain criteria when being
implemented, examples of these are:
• The translation pattern matched within the country dial plan, must
prefix the first feature code.
• Any translation patterns used by a feature must strip the incoming
feature code, and prefix the next feature code in the chain except for
the last feature used.
• The last feature in the chain will normalise the call details call routing
Feature Processing
Within the current BT looping dial plan leaf cluster models, the following
features are in use:
• Feature 1 = Forced On-Net
• Feature 2 = Class of Service
• Feature 3 = Time of Day Routing & CLIP / CLIR CLI Presentation
• Feature 4 = Forced Authorisation Codes
• Feature 5 = Client Matter Codes
• Feature 6 = Routing
Feature Processing Examples
Feature 1 – Forced On-Net
The following diagram describes how the forced on-net call processing feature is used within the BT looping dial plan.

The forced on-net feature must first de-classify its prefix, and then reclassify again thereafter to handle this particular
feature.
Feature Processing Examples
Feature 2 – Class of Service
The following diagram describes how a class of service is now
implemented as a feature, rather than from the country dial plan
translation patterns.
Feature Processing Examples
Feature 2 – Class of Service
The following diagram details some examples of the class of services
that are introduced by the looping dial plan.
Intl24HrsEnh-CSS CLIRIntl24HrsEnh- Natl24HrsEnh-CSS NatlExtHrsStd-CSS
CSS
E164Lookup E164Lookup E164Lookup E164Lookup
LOCLDP4-#ISO#-PT LOCLDP4-#ISO#-PT LOCLDP4-#ISO#-PT LOCLDP4-#ISO#-PT
CTRYDP4-#ISO#-PT CTRYDP4-#ISO#-PT CTRYDP4-#ISO#-PT CTRYDP4-#ISO#-PT

FONet-PT FONet-PT FONet-PT FONet-PT Feature 1 - FON

BlkIntlCT-PT BlkIntlCT-PT
BlkIntlRstCT-PT Feature 2 - CoS
BlkPRSCT-PT
AllowPSTN-PT AllowPSTN-PT AllowPSTN-PT AllowPSTN-PT
24HrsCLIP-PT 24HrsCLIR-PT 24HrsCLIP-PT ExtHrsCLIP-PT
Feature 3 – CLIP/CLIR
noFAC-PT noFAC-PT noFAC-PT noFAC-PT Feature 4 - FAC
noCMC-PT noCMC-PT noCMC-PT noCMC-PT Feature 5 - CMC
LBORting-PT LBORting-PT LBORting-PT LBORting-PT
CBORting-#ISO#-PT CBORting-#ISO#-PT CBORting-#ISO#-PT CBORting-#ISO#-PT Feature 6 - Routing
CustSCode24Hrs-PT CustSCode24Hrs-PT CustSCode24Hrs-PT CustSCode24Hrs-PT
LocSCode24Hrs-PT LocSCode24Hrs-PT LocSCode24Hrs-PT LocSCode24Hrs-PT
AllowUCCEXferPT AllowUCCEXferPT AllowUCCEXferPT AllowUCCEXferPT
AllowVMCalls AllowVMCalls AllowVMCalls AllowVMCalls
AllowInternal AllowInternal AllowInternal AllowInternal
AllowCallFeatures AllowCallFeatures AllowCallFeatures AllowCallFeatures
InterSiteRoutingPT InterSiteRoutingPT InterSiteRoutingPT InterSiteRoutingPT
Site Site Site Site
Feature Processing Examples
Feature 2 – Class of Service
The table below highlights the call types that each class of service is able to
make, depending on the restrictions applied by a calling search space:
Names Personal
Operator
Emergency OnNet FreePhone Local National Mobile Comms International Premium Rate
Non Timed (Base) Services
Services
InternationalXXXHrs-
A A A A A A A A A A
Enhanced
InternationalXXXHrs-
A A A A A A A B A B
Standard
NationalXXXHrs-Enhanced A A A A A A A A B A
NationalXXXHrs-Standard A A A A A A A A B B
NationalXXXHrs-Restricted A A A A A B A B B B
LocalXXXHrs-Enhanced A A A A B B A B B A
LocalXXXHrs-Restricted A A B A B B A B B B
Call Forward
CF-International24Hrs-
B A A A A A A B A B
Standard
CF-National24Hrs-Standard B A A A A A A A B B
CF-Local24hrs-Enhanced B A A A B B A B B A
Key:
CF-Internal Only B A B B B B B B B B A = Call Type Allowed
CF-BlockAll B B B B B B B B B B B = Call Type Blocked
Feature Processing Examples
Feature 3 – Time Of Day & CLIP / CLIR
The following diagram describes how the time of day feature is
implemented as the 3rd feature within the chain.
Feature Processing Examples
Feature 4 & 5 – Forced Authorisation Codes & Client Matter Codes
The FMC codes are used in conjunction with the CMC, to ensure the call is
routed to the correct route patterns.
The CMC feature is similar to FAC, except for each call type two translation
patterns are needed to cater for the two possible values of the FAC extension
digit.
The first digit is used for LBO and is set to one. The second digit value is used
to indicate the following combination of FAC and CMC requirement for routing.
EXTENSION FAC AND CMC INDICATOR
VALUE
0 No FAC and No CMC
1 FAC and no CMC
2 CMC and no FAC
3 CMC and FAC
Feature Processing Examples
Feature 4 & 5 – Forced Authorisation Codes & Client Matter Codes
At present only the FAC Calling Search spaces contain the required FMC
partition for FAC call processing. However no Calling search spaces currently
include the CMC partitions within the BT model.
This means that all calls will not use the CMC facility, but this feature has been
left in the BT models should it be required in the future.
Feature Processing Examples
Feature 6 – Routing
Once all the features within the chain have been concluded, if the call is still
able to route, the last decision in the feature chain is routing the call.
The route that the call will take, is ultimately dependant on the configuration that
has been completed for that location the caller is dialling from.
Should the location be configured with a local gateway for LBO routing, then a
number of translation patterns are created in order to route the call out of the
IOS gateway.
However if the location is using the default SIP trunk for outbound routing, the
call will pass through call screening, and be changed back into a called number
that will match the configured country route patterns.
Feature Processing Examples
Feature 6 – Routing
The predominate check in the routing step, is the feature screening process to
ensure the call has not bypassed any previous feature steps.
After the call has passed the screening process, the call is passed to the
relevant route pattern in CUCM, and sent to the LBO gateway or SIP trunk for
processing.
Country
IP Phone Time Of Day /
Translation Forced On-Net Class of Service FAC CMC Routing
Line CSS CLIP or CLIR
Pattern

IP Phone Pre Routing Post Routing

LBO Routing / CBO
Check Check Route Pattern
Line CSS <Country>Routing
(Is this fraud) (Not Fraud)
Route Next Hop by Calling Calling Number Modified
Number by Feature 1 (FON)
Leaf Cluster & Country
Models
Leaf Cluster & Country Models
The implementation of a dial plan is managed by CUCDM, using a combination of the leaf
cluster and the individual country dial plans.
By default when a customer is created on CUCDM, and the CUCM cluster is associated
to the customer, the following tables list the a general rule of thumb for the number of
translation patens that are created by both the looping dial plan and the non-looping dial
plans.
Looping Dial Plan Translation Patterns Non-Looping Dial Plan Translation Patterns
Leaf Cluster 97 Leaf Cluster 5
UK Country Dial Plan 400 UK Country Dial Plan 900
USA Country Dial Plan 380 USA Country Dial Plan 550
Germany Dial Plan 110 Germany Dial Plan N/A
Hungary Dial Plan 40 Hungary Dial Plan 420
Australia Dial Plan 130 Australia Dial Plan N/A
Leaf Cluster & Country Models
The country leaf cluster models have been greatly reduced in size, due to the implementation of the
looping dial plan being implemented at a higher hierarchical level then the previous dial plan.
The is ensures that the CUCM cluster uses less configuration, ultimately helping with resource
consumption for the servers.
The table below highlights the change in hierarchical configuration made between the dial plans and
the configuration that is implemented onto a CUCM cluster for the example countries.
Leaf Cluster & Country Models
The numbers of translation patterns will increase when other transactions are processed
for the customer or new locations, i.e. FNN Association, local breakout, EMCC and
Contact Centre Enterprise deployment transactions.
Another factor that will impact the number of translation patterns utilised on a customer
CUCM cluster, is the provider that the customer is placed under when configured.
The current configuration on CUCDM 8.1.x, is that customers will inherit all country dial
plans which have been assigned to each respective provider in CUCDM. This means that
a customer will have a country dial plan configured in CUCM, if that provider has a
country associated to it within CUCDM.
Leaf Cluster & Country Models
The diagram below details the current providers configured on BT’s CUCDM servers, as
well as the countries that are either assigned or could be assigned to each provider.
Looping Dial Plan
Walkthrough
Looping Dial Plan Walkthrough
The following examples detail the routing decisions that are made, when the following call
flows are processed within the looping dial plan.
Note: If required change the “Digit Analysis Complexity” Service parameter to see full trace output.
1) Inter-Site

2) IP Phone to IP Phone PSTN National (Forced On-Net)

3) IP Phone to PSTN National (Central Breakout, CLIP, CoS Allowed)

4) IP Phone to PSTN National (Central Breakout, CLIR, CoS Allowed)

5) IP Phone to PSTN National (Central Breakout, CLIP, CoS Block)

6) IP Phone to PSTN Emergency (Central Breakout, CLIR)

7) PSTN to IP Phone (Central Breakout)

8) IP Phone to PSTN National (Local Breakout, CLIP, CoS Allowed)

9) PSTN to IP Phone (Local Breakout)

Looping Dial Plan Walkthrough
The following example details the call flow for an Inter-site call.
Looping Dial Plan Walkthrough
The following example details the call flow for an IP Phone to a PSTN national number
(Central Breakout, CLIP, CoS Allowed)
Looping Dial Plan Walkthrough
The following example details the call flow for an IP Phone to a PSTN national number
(Central Breakout, CLIR, CoS Allowed)
Looping Dial Plan Walkthrough
The following example details the call flow for an IP Phone to a PSTN national number
(Central Breakout, CLIR, CoS Blocked)
Looping Dial Plan Walkthrough
The following example details the call flow for an IP Phone to an Emergency Number
Looping Dial Plan Walkthrough
The following example details the call flow for an PSTN inbound call to an IP Phone
Looping Dial Plan Walkthrough
The following example details the call flow for an IP Phone to a PSTN national number
(Local Breakout, CLIP, CoS Allowed)
Looping Dial Plan Walkthrough
The following example details the call flow for an Local Breakout PSTN inbound call to an
IP Phone
Troubleshooting
Troubleshooting
The predominate way in which to troubleshoot a call flow is to utilise the CUCM Dialled Number Analyser tool.

This tool will allow you to work through the call flow, to confirm the numbers that are presented through the feature
chain. However for Feature 1 and Feature 6, Forced On-Net and Routing, only the second step for these features will
provide the required output from DNA due to how these features are implmeneted.

1) On the DNA Analyser Tool, select the phone you require, and enter the dialled digits by the end device
Troubleshooting
Now that we can see the first amendment to the called party number, the next analyser
search's can be performed using these digits, as well as the 2nd and 3rd features within the
chain.
 Questions ????
Questions ????
Thank You