INE VO DD WB Vol1 Mod10 GlobalizedDialPlan Tasks

Voice Deep Dive Workbook Version 3.5 Module 10

Copyright © 2011 Internetwork Expert www.INE.com - 1 -

Dial Plan: Globalization, Localization and

Mapping the Global # to the Local Variant ::

Tasks

Lab Instructions:

Prior to starting this lab, ensure that you have both read through the Voice Rack Rental Guide before beginning this lab, so that you are fully aware of how all equipment works and is accessed, and that you have loaded both the initial router/switch configs from INE’s members’ site, and that you have manually loaded the CUCM initial configs as described below.

Note

- Most Deep Dive lab scenarios require existing configuration before they can begin to be configured. Also, most lab scenarios use different pre-configuration from other Deep Dive labs. Therefore it is necessary to load the "Startup Configs" prior to beginning any of these lab scenarios.

- To load your router and switch configs, first log into your INE.com Members account, then navigate to the "Rack Rental" tab, and click on "Control Panel" >> "Click here to choose a configuration to be loaded on your Voice Rack", then choose the appropriately named selection for this module. This will only load your router and switch configs (pstn, r1, r2, r3, sw1, sw2).

- To load your CUCM server initial configs, please log into the CUCM Admin WebUI, and use the “Bulk Administration” tool to upload & import the appropriately named “DD-ModXX-CUCM-Startup.tar" file that was included in your Members account for this module. Here are two brief demonstration videos on how to successfully accomplish this upload and import into CUCM: Importing or Exporting Configurations in CSV file from CUCM (15 mins), and Fixing Any Issues That May Arise With Importing CSS and CdPTP & CngPTPs (8 mins).

http://ine.com/l/vo_rrag

http://members.ine.com/




http://ieclass.ine.com/p98538031/





Route Plan Description and Overall Guidelines

Phones in US locations use a prefix code of “9” to access a PSTN trunk. Phones at the NL location use a prefix code of “0” to access a PSTN trunk. Outside dial tone should be provided as soon as the prefixed PSTN Trunk Code has been dialed for each site respectively

Both the CorpHQ and Branch1 sites are located in the US and have the country code of “1”. CorpHQ is in the city of Seattle, WA and Branch1 is in Austin, TX.

Branch2 site is located in the Netherlands (NL) and has the country code of “31”. Branch2 is in the city of Amsterdam.

Users should be able to dial “911” from the US locations (CorpHQ and Branch1), and “112” from the Netherlands location (Branch2), to reach emergency services

Make sure the PSTN Trunk Code of “9” for US and "0" for NL are each stripped for all calls before going to PSTN (except for the “9” in “911”)

Local area (Subscriber) PSTN calls are placed from CorpHQ & Branch1 locations by dialing 10-digit numbers, and BR2 by dialing 7-digit numbers

Long-distance (National) PSTN calls placed from the CorpHQ and Branch1 locations are done so by dialing 11-digit numbers with the first number being the PSTN LD access code “1”, and at the Branch2 location by dialing 10 digit numbers with the first number being the PSTN National access code of “0” (this is in addition to the PSTN Trunk Code of 0 for Branch2)

International calls from the CorpHQ and Branch1 site should be prefixed using the PSTN International access code of “011” along with the country code and variable length number for the site/number you are trying to reach

International calls from the Branch2 site should be prefixed using the PSTN International access code of “00” along with the country code and variable length number for the site/number you are trying to reach (this is in addition to the PSTN Trunk Code of 0 for Branch2)

You should allow for any phone users to be able to terminate interdigit timeout on international number dialing using the “#” sign, in order to place the call immediately



Inbound Calling Party Transformation

10.1 Inbound Calling Party Globalization

Globalize all calls coming in from the PSTN to gateways at all sites using the proper Full E.164 numbering format (including preceding +) for each site

You are responsible for determining how calls are ringing into each site with regards to Numbering Type and Digit Length (note: not every call rings-in in the same fashion, so place multiple calls into each site and make notes to determine this)

The preceding “0” coming into the Branch2 Amsterdam site from the PSTN should not be included in the globalized format of the number - drop this "0" before doing anything else to the number

The new Globalized Calling number should display at any phone when the user at said phone presses either:

o DirectoriesCall HistoryMissed Calls

o DirectoriesCall HistoryReceived Calls

10.2 Inbound Calling Party Localization

Localize all calls that come in from the PSTN as they arrive at each IP phone

Local (Subscriber) Calls: o During inbound alerting, IP Phones in the US sites should display calling party

numbers that are local to each site as 10 digits o During inbound alerting, IP Phones in the NL site should display calling party

numbers that are local to that site as 7 digits

Long Distance (National) Calls: o During inbound alerting, IP Phones in the US sites should display calling party

numbers as 11 digits if that call is from the same country, but a different geographic area (different Area Code)

o During inbound alerting, IP Phones in the NL site should display calling party numbers as 10 digits if that call is from the same country, but a different geographic area. This means that the calling party number should have the national access code of "0" added back to the front of the geographic code

International Calls: o During inbound alerting, IP Phones in the US sites should display calling party

numbers with all digits, including the country code and the preceding PSTN international access code of "011", if that call is from a different country

o During inbound alerting, IP Phones in the NL site should display calling party numbers with all digits, including the country code and the preceding PSTN international access code of "00", if that call is from a different country



Outbound Called and Calling Party Transformations

10.3 PSTN Patterns (Translation Patterns are the *New* Route Patterns)

The Route Patterns that you created in Module 9, have been re-created for you as basic Translation Patterns for the US and NL site(s)

Modify these Translation Patterns so that they Globalize every Called Party Number to a proper Full E.164 numbering format

o *NOTE: Emergency numbers need to be globalized to match the new Global Route Patterns - but will not be in "proper" E.164 format - this is OK)

Create new CSS's and PT's to allow calls made to these Translation Patterns to route to the appropriate (to be created) Global Route Patterns for each country

Create the necessary Global Route Patterns to match your globalized Translation (PSTN) Patterns, and to allow calls made from each country to route out the appropriate gateway(s) based on the (modified) information in the two tables below:

Table 10.3(1): Dialing from within US sites

Call Type PSTN Pattern Outbound Gateway

Emergency 911 Local

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

National/LD 1[2-9]XX[2-9]XXXXXX 1) CorpHQ 2) Local

International 011 + Variable length 1) CorpHQ 2) Local

Table 10.3(2): Dialing from within NL site

Call Type Pattern Outbound Gateway

Emergency 112 Local

Local [1-8]XXXXXX Local

National/LD 0[1-2]X[1-8]XXXXXX Local

International 00 + Variable length 1) CorpHQ 2) Local



10.4 Digit Manipulation: Calling & Called Party Transformations and IOS Voice Translation Rules & Dial Peers

Ensure that as calls leave for the PSTN, that all DINS digits are formatted properly so that the PSTN will route each call without error

*NOTE: Dial-Peers have been provisioned in IOS for both the CorpHQ-R1 and the Branch1-R2 GWs. You should take a look at both IOS GWs to ensure that you know how the dial-peers are configured so that you can send properly formatted DNIS digits to each GW without needing to modify any of the dial-peers

For Calling Party Numbers at all sites, the PSTN should see the calling party's number in the same format from Module 9, Task 5 (*NOTE: Nothing should need to be changed from yesterday to allow this task's bullet point to continue to function properly)

Mapping Global #s to their Local Variants

10.5 + Dialing and One-Button Missed Call DialBack

Ensure that any user at any IP Phone who presses either "Missed Calls" or "Received Calls" and sees the numbers in Full E.164 Globalized format, can simply press the "Dial" softkey, and the call will be properly routed - but only if that IP Phone has the proper CoR to be able to dial the Missed/Received number (e.g. Phone 2 at every site should not be able to return calls to a Local, National or International numbers)

10.6 Modify Class of Service (CoR)

Modify the CoR for IP Phone 2 at every site so that they now have access to dial Local numbers in addition to their exsting ability to dial Internal and Emergency numbers

Test not only Phone 2's ability to dial Local numbers from the keypad, but also its ability to return calls to a Local number, while still failing when trying to return calls from callers that came from National or International numbers



How To Dial Into a Site's GW Using the PSTN Phone Dialing Into the CorpHQ GW:

For Calling Party Type to show as "Subscriber" >> Select PSTN Line 1, and dial 10 digits (eg. 2065011001)

For Calling Party Type to show as "National" >> Select PSTN Line 2, and dial 1+10 digits (eg. 15126022002)

For Calling Party Type to show as "International" >> Select PSTN Line 3, and dial 00+1+10 digits (eg. 0012065011001)

For Calling Party Type to show as "Unknown" >> Select PSTN Line 6, and dial 10 digits (eg. 2065011001)

For Calling Party Type to show as "Private" >> Select Any PSTN Line, and dial *67+10 digits (eg. *672065011001)

Dialing Into the Branch1 GW:






Dialing Into the Branch2 GW:






Documents

INE VO DD WB Vol1 Mod10 GlobalizedDialPlan Tasks