Cisco HCS Dial Plan Model with Enhanced Number Translation · Cisco HCS Dial Plan Model with Enhanced Number Translation ... Extension Dialing Template ... TEHO_LBO_#LOCATION-ID#_RP_Template

Cisco HCS Dial Plan Model with EnhancedNumber Translation

• Bulk-Loading Enhanced Number Translations, page 1

• Extension Dialing Template, page 2

• Extension Dialing with Prefix Template, page 3

• Intrasite Dialing Template, page 4

• InterCluster Call Routing Templates, page 5

• Intersite Dialing with or Without an ISP Template , page 6

• Intersite Call to Unmanaged Location in vPGW, page 8

• Local Calling Template, page 9

• Short Code Dialing Template, page 10

• Short Code Voice Mail Dialing Template, page 10

• Blacklist or Call Blocking Template, page 11

• Calling Party Screening Template, page 12

• Allow Call Template, page 13

• Tail End Hop Off Template, page 14

• InterCluster Voice Mail Route Pattern Template, page 16

• Small Contact Center Route Pattern Template, page 17

• Country-Specific ENT Templates, page 18

Bulk-Loading Enhanced Number TranslationsEnhanced Number Translations (ENTs) allow you to load and customize Route Patterns and TranslationPatterns for individual customer foundation HCS-G1 and HCS-G2 dial plans. ENTs support a number ofcustomer-specific requirements such as Allowing and Blocking number ranges, supporting short-code dialing

Cisco Hosted Collaboration Solution, Release 10.6(1) Dial Plan Management for Cisco Unified CommunicationsDomain Manager, Release 8.1(x)

1

both at the Customer and Location level, routing calls to inter-cluster trunks, and routing calls to a third-partyPBX.

Before ENTs are loaded, ENT Feature Configuration Templates (FCTs) must first be loaded at the Customerlevel. ENTs can then be loaded at the Customer or Location level making use of these FCT templates.

The VS-P1 reference loader provides a set of FCT template examples together with translation patterns thatuse these FCT templates.

ENT translation patterns can load either Route Patterns or Translation Patterns. The FCT templates definewhether the pattern creates a route pattern or a translation pattern.

Note

Review and adjust the reference bulk loader as required(C4-CUCDM81x-VS-P1-HCS901v11-FCT-ENT-Loader-Set-vyVS Corp, where x is the Cisco UnifiedCommunications Domain Manager version number, and y is the worksheet version number).

It is recommended that the FCTs are loaded first in combination with Route Pattern Element and TranslationPattern Elements. Then load the "Add Customer Number Translation Pattern" and "Add Location NumberTranslation Pattern" worksheet. (Unhash required FCTs and ENTs as required.)

Extension Dialing TemplateIn order to support extension dialing with or without a prefix, the intrasite translation pattern is removed fromthe Cisco HCS Dial Plan Model. When a new location (or site) is added for a customer, an ENT-basedtranslation pattern is provisioned for that location based on the extension dialing template. The templateconsists of the following columns (only nonblank columns are shown).

Table 1: Extension Dialing Templates

DescriptionValueTemplate Name

Service provider name.HCSArcLabProvider Name

Reseller name.HCSArcResellerReseller Name

Customer name.HCSArcCustomerCustomer Name

ENT template name.IntraSite_G1_TemplateFeature Configuration TemplateName

Translation pattern name.ExtensionTranslation Pattern Name

Pretranslated number. This value is takenfrom the GUI.

#PRETRANSLATEDNUM#Translation Pattern

The partition name to be used for extensiondialing. It is created by the model.

AllowInternalPartition Name

Next CSS to be used in the call routing.This CSS is created by the model.

IncomingToSite-CSSCalling Search Space Name


2

Cisco HCS Dial Plan Model with Enhanced Number TranslationExtension Dialing Template

DescriptionValueTemplate Name

The route action is to route the call.RouteRoute Action

The calling mask in the template is definedas SLC+Extension.

#SITECODE##SITEMASK#Calling Mask

Calling line presentation number is takenfrom the GUI.

DefaultCalling Line Presentation

Calling name presentation is taken from theGUI.

DefaultCalling Name Presentation

The SLC is prefixed to the posttranslatednumber taken from the GUI.

#SITECODE##SITEMASK#Called Mask

Extension Dialing with Prefix TemplateThe following table shows the template you use for a customer or a customer location.

Table 2: Extension Dialing with Prefix Template

DescriptionTemplate NameUse Case

In this use case, a prefix is used for extensiondialing. The extension prefix is provisioned as apretranslated number. The calling party DN isdisplayed as a calling party number.

ENT_G1_IntraSite_ExtPfx_TemplateExtension Dialing withExtension Prefix

In the template, use the first sheet in the workbook to fill in the variables for provider, reseller, and customername. This auto-fills the remaining template sheets with the correct data. Load the template into the systemand use either another bulk loader or the GUI to add the translation pattern.

• $ProviderName—VS-P1-HCS

• $ResellerName—VS-Ops

• $CustomerName—GenCorp

Extension Dialing with a Prefix Number Translations Provisioning Guideline

Enter the following number translation patterns from the bulk loader or in the Number Translation GUI:

• Pretranslated Number—Provision translation pattern to be allowed

• Posttranslated Number—Provision the extension prefix, such as 7

• Target—Select appropriate Location or all locations if the extension prefix is same across all locations

• Feature Configuration Template—ENT_G1_IntraSite_ExtPfx_Template


3

Cisco HCS Dial Plan Model with Enhanced Number TranslationExtension Dialing with Prefix Template

• Apply To—Leave as IPPBX

• Calling Line Presentation—Select anything except NA

• Calling Name Presentation—Select anything except NA

Intrasite Dialing TemplateThis template defines translation patterns for Intrasite Call routing for customers or customer locations.

• Extension Dialing

• Calling Line Identification Restriction (CLIR) Extension Dialing (not restricted)

• Calling Line Identification Restriction (CLIR) Extension Dialing (restricted)

Table 3: Intrasite Dialing Templates


This is the current capability provided by theG1 Dial Plan Model. The Calling Party DN isdisplayed as the Calling Party Number.

ENT_G1_IntraSite_Templatev# (where # is thetemplate version number)

IntraSite_G1_Template

IntraSiteLnkChild_G1_Template

Extension Dialing

Use these templates if internal calls dialed asextensions are to be displayed (not restricted).

IntraSiteCLIR_Unres_G1_Template

IntraSiteCLIRLnkChild_Unres_G1_Template

CLIR Extension Dialing

Use these templates only if internal calls dialedas extensions are to be displayed as restricted.

IntraSiteCLIR_Res_G1_Template

IntraSiteCLIRLnkChild_Res_G1_Template

CLIR Extension Dialing

The Calling Party Number Display is DN by default.





Intrasite Dialing Number Translations Provisioning Guideline


• Pretranslated Number—X (value taken from the template)

• Posttranslated Number—X (value taken from the template)


4

Cisco HCS Dial Plan Model with Enhanced Number TranslationIntrasite Dialing Template

• Target—Select All Locations

• Feature Configuration Template—for example, IntraSite_G1_Template




InterCluster Call Routing TemplatesThe following table shows the templates to use for a customer or a customer location. In the table, x is anyDial Plan (G1, G2, or G3) and # is the template version number.

Table 4: InterCluster Call Routing Templates


This template is used create InterClusterroute patterns. Use any one of the locationsin the cluster to provision the RP.

ENT_Gx_InterClusterTrunk_RP_Templatev#InterCluster CallRouting

This template includes three templateoptions and can be used to create RPs toan unmanaged MGCP, H323, or SIP PBX.Use any one of the locations in the clusterto provision the RP.

ENT_Gx_InterClusterTrunk_Unmanaged_RP_Templatev#InterCluster CallRouting

In the template, use the first sheet in the workbook to fill in the variables for provider, reseller, customer name,and route list ID. This auto-fills the remaining template sheets with the correct data. Load the template intothe system and use either another bulk loader or the GUI to add the translation pattern.




• $Route List ID for MGCP—RL-UNMANPBX-MGCP-#LOCATION-ID#

• $Route List ID for H323—RL-UNMANPBX-H323-#LOCATION-RICPID#

• $Route List ID for SIP—RL-UNMANPBX-SIP-#RICPID#

InterCluster Call Routing Translations Provisioning Guideline


• Pretranslated Number—Provision RP toward unmanaged PBX. If the extension range is in 10s or 100sas in 234XXXX, then provision RP as 234XXXX. For individual extension, provision RP as an ExtensionExample: 2343983

• Posttranslated Number—Number of X's contained in the RP (optional)


5

Cisco HCS Dial Plan Model with Enhanced Number TranslationInterCluster Call Routing Templates

• Target—Location specific (Use any one location to provision the RP)

• FeatureConfigurationTemplate—for example, ENT_Gx_InterClusterTrunk_Unmanaged_RP_Templatev#




Example of InterCluster Call Routing Template Use

To route calls from CL1 to CL2, create RPs at CL1 using an InterCluster Call Routing template. RP1 =234XXXX, RP2 = 367222X

Figure 1: InterCluster Call Routing Template Example

Intersite Dialing with or Without an ISP TemplateThis template defines translation patterns for Intersite Call routing. Since ISP is included in the Site LocationCode (SLC), this template can be used for the following:

• Intersite Dialing with an ISP

• Intersite Dialing without an ISP

• Intersite Dialing with Calling Line Identification Restriction (CLIR)

The following translation patterns replace the translation pattern in the Dial Plan 8.6(2) Model except that thecalling line and calling name presentation are set to default instead of <blank>.


6

Cisco HCS Dial Plan Model with Enhanced Number TranslationIntersite Dialing with or Without an ISP Template

Table 5: Intersite Dialing Templates


The ISP is included in the SLC.ENT_G1_InterSite_Templatev# (where# is the template version number)

InterSite_G1_Template

Intersite Dialing (with anISP)

This is a special case of IntersiteDialing (with an ISP). The onlydifference is that the first digit of theSLC is not an ISP. You do not use anyvariables; the same template can beused for this use case.

For Intrasite dialing, theextension prefix template isused in order to avoid aconflict.

Note

InterSite_G1_Template

InterSiteLnkChild_G1_Template

Intersite Dialing (withoutan ISP)

This template is used to provisionCalling Line Identification Restrictiontranslation patterns.

InterSiteCLIR_G1_TemplateIntersite Dialing (CLIR)





Intersite Dialing Number Translations Provisioning Guideline


• Pretranslated Number—X (value taken from the template)

• Posttranslated Number—X (value taken from the template)


• Feature Configuration Template—for example, InterSite_G1_Template





7

Cisco HCS Dial Plan Model with Enhanced Number TranslationIntersite Dialing with or Without an ISP Template

Intersite Call to Unmanaged Location in vPGWThe ENT_Gx_vPGW_Unmanaged_Location_RP_Templatev# (where x is any Dial Plan G1, G2, or G3, and# is the template version number) is used to create route patterns to an unmanaged location or PBX on thevPGW. The assumption is that unmanaged locations do not dial ISP to get to a managed location.

Table 6: Intrasite Call to Unmanaged Location in vPGW Template


This template is to be used to create RPs to anunmanaged Location/PBX on the vPGW.

vPGW_Unmanaged_Location_RP_TemplateInterSiteCall toUnmanagedLocation inthe vPGW

The Route List to the vPGW name must be RL_to_VPGW.Note





Intrasite Call to Unmanaged Location in vPGW Translations Provisioning Guideline


• Pretranslated Number—route pattern toward unmanaged location/pbx on vPGW. If ISP=8,UnManagedLocation SLC=234 and Extension Length=4 then PreTranslateNumber=8.234XXXX andPostTranslateNumber=X

• Posttranslated Number—X (see example above)

• Target—Customer

• Feature Configuration Template—vPGW_Unmanaged_Location_RP_Template





8

Cisco HCS Dial Plan Model with Enhanced Number TranslationIntersite Call to Unmanaged Location in vPGW

Local Calling TemplateThe following table shows the template to use for a customer or a customer location.

Table 7: Local Calling Template


There are several countries that have variable lengthlocal dialing. For example, in India and Mexico, thelength of the area code + local number is fixed at 10,but they have variable length area codes from twoto four digits. So if the length of the area code is twodigits, then the length of the local number is eightdigits. The local template can be used to customizetranslation patterns per location.

ENT_Gx_Local_Calling_Templatev#(where x is any Dial Plan, G1, G2 orG3, and # is a template versionnumber). This template includes:

Local_Call24Hr_Template

Local_CallStd_Template

Local_CallLLBO24Hr_Template

Local_CallLLBOStd_Template

Local Call

There are four templates to provision local call (one for each partition). Ensure that the translation patternsfor all four templates are provisioned.

Note





Local Call Number Translations Provisioning Guideline


• Pretranslated Number—9.[2-9]XXXXX

• Posttranslated Number—XXXXXX

• Target—Select appropriate location or indicate all locations if fixed number of digits apply to all locations

• Feature Configuration Template—Apply the same translation pattern to all four templates above





9

Cisco HCS Dial Plan Model with Enhanced Number TranslationLocal Calling Template

Short Code Dialing TemplateUse the following table to determine which templates to use for a customer or a customer location.

Table 8: Short Code Dialing Template


This template provides an ability to create shortcodes for commonly-used services such as help,operator, maintenance, and voice mail.

ENT_Gx_ShortCode_Dialing_Templatev#(where x = any Dial Plan, G1, G2, or G3, and #= template version number). This templateincludes:

Short Code Dialing

Only intracompany short code dialing is supported.Note

Short code patterns are location specific or applied to all locations. The translation pattern is assigned to theAllowInternal<site> partition.





Short Code Dialing Number Translations Provisioning Guideline


• Pretranslated Number—Short code (Example: #1)

• Posttranslated Number—Expanded number (Example: 81135050)

• Target—Select appropriate location or indicate all locations if short code applies to all locations

• Feature Configuration Template—SC_Dialing_Template




Short Code Voice Mail Dialing TemplateThe ENT_Gx_VM_ShortCode_Dialing_Templatev# (where x is any Dial Plan model G1, G2, or G3, and #is the template version number) is used to convert a voicemail access code to a voicemail number.


10

Cisco HCS Dial Plan Model with Enhanced Number TranslationShort Code Dialing Template

Table 9: Short Code Voice Mail Dialing Template


This template provides an ability to createshort codes for commonly-used services suchas help, operator, maintenance, and voicemail.

VM_Dialing_TemplateShort Code Dialing

The VM short code pattern is location-specific or can be applied to all locations. The translation pattern isassigned to the AllowInternal<site> partition.





Short Code Voice Mail Translations Provisioning Guideline


• Pretranslated Number—Short code (Example: #1)

• Posttranslated Number—Expanded number (Example: 81135050)

• Target—Select appropriate location or indicate all locations if short code applies to all locations

• Feature Configuration Template—VM_Dialing_Template




Blacklist or Call Blocking TemplateUse the ENT_Gx_Block_Call_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is a templateversion number) to define call-blocking translation patterns.

Table 10: Blacklist/Call Blocking Translation Pattern


You can add Blacklist or Blocking translation patterns foreach customer or location as required.

Block_Call_TemplateBlacklist or CallBlocking

Block National calls to pre-defined translation patterns.Block_Natl_Call_TemplateBlock National Calls


11

Cisco HCS Dial Plan Model with Enhanced Number TranslationBlacklist or Call Blocking Template


Block International calls to pre-defined translation patterns.Block_Intl_Call_TemplateBlock InternationalCalls





Provision the translation pattern to be blocked as pretranslated number. If the blocking pattern is for a PSTNNumber, please include the PSTN Prefix. Please use the Allow Partition to add blocking Translation Patterns.For example, to block National calls to a particular NPA, use the partition which allows National calls(AllowNatl24Hr-#COUNTRY#). To block Intl calls to a country, use the Allow Intl partition(AllowIntlStd-#COUNTRY#). Partitions for ENT-based DP Customization are done at the Customer Level.

Blacklist or Call-Blocking Number Translations Provisioning Guideline


• Pretranslated Number—Provision translation pattern to be blocked (Example: 9.1900)

• Posttranslated Number—X

• Target—Customer level

• Feature Configuration Template—for example, Block_Call_Template




Calling Party Screening TemplateUse the ENT_Gx_Calling_Pty_Screening_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is atemplate version number) to reject inbound calls from provisioned Calling Party Numbers.

Table 11: Calling Party Screening Template


You can add Blacklist or Blocking translation patterns for each customer.Calling_Pty_Screening_TemplateBlacklist or Call Blocking


12

Cisco HCS Dial Plan Model with Enhanced Number TranslationCalling Party Screening Template





Provision the translation pattern to be blocked as pretranslated number. If the blocking pattern is for a PSTNNumber, include the PSTN Prefix. Use the Allow Partition to add blocking Translation Patterns. For example,to block National calls to a particular NPA, use the partition which allows National calls. To block Internationalcalls to a country, use the Allow Intl partition.

For the Reject Calling Party Number use the CallingPartyScreeningPT.

Calling Party Screening Translations Provisioning Guideline


• Pretranslated Number—Provision the Calling Party Number to be rejected


• Target—Customer level

• Feature Configuration Template—for example, Calling_Pty_Screening_Template




Allow Call TemplateUse the ENT_Gx_Allow_Call_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is a templateversion number) as follows to define call-allowed translation patterns.

Table 12: Allow Call Template


Allow calls only to a limited number of dialing patterns.Allow_Call_TemplateList of Allowed Calls

Allow predefined National translation patterns when allNational Calls are blocked.

Allow_Natl_Call_TemplateAllow National Calls

Allow predefined International translation patterns whenall International Calls are blocked.

Allow_Intl_Call_TemplateAllow InternationalCalls


13

Cisco HCS Dial Plan Model with Enhanced Number TranslationAllow Call Template





Please provision the Translation Pattern to be allowed as Pre-Translated Number. If the allowed pattern is fora PSTN Number, please include the PSTN Prefix. The following Partitions are available for use in theTemplates. Please use the Blocking Partition to define the Allowed call Template since the Blocking Partitionwill be included in the COS assigned to the user. To allow exceptions for National Calls, useBlkNatl-#COUNTRY# Partition. To allow exceptions for International Calls, use BlkIntl-#COUNTRY#Partition.

Allow Call Number Translations Provisioning Guideline


• Pretranslated Number—Provision translation pattern to be allowed

• Posttranslated Number—Provision called party mask with the number of x's equal to the number length

• Target—Select all locations

• Feature Configuration Template—for example, Allow_Call_Template




Tail End Hop Off TemplateThe Tail End Hop Off (TEHO) feature is used to route PSTN calls through a local gateway at the remotelocation that is closest to the dialed number.

Route patterns are created for each destination code that requires TEHO. For example, If you have a localgateway in United Kingdom and want to deploy TEHO for calls to the United Kingdom, you need to build aroute pattern for +44 calls that point to a route list containing the gateway in United Kingdom as the primaryroute and to the standard local route group as a secondary route.

The TEHO feature requires that you create route lists consisting of the following:

• Gateway at a remote site as first choice

• Local Gateway as second choice (using standard local route group)

• Central Breakout as third choice

Create route patterns that point to the correct route list.


14

Cisco HCS Dial Plan Model with Enhanced Number TranslationTail End Hop Off Template

Currently, the Route Groups created by Cisco Unified Communications DomainManager when you add LocalGateways are not visible in the Generic SIP Support feature. In order to have Tail End Hop Off capability,TEHO Route Lists are created by the Dial Plan model as a default.

The ENT_Gx_TEHO_RP_Templatev# (where x is any Dial Plan G1, G2, or G3, and x is the template versionnumber) contains the templates shown in the following table. Use the ENT templates to provision each routepattern that requires TEHO.

Table 13: TEHO Route List


This template is to be used to create TEHOroute patterns

TEHO_LBO_#LOCATION-ID#_RP_TemplateTail End Hop-Off (TEHO)

This template is to be used to create TEHORPs.Additionally this template has to be createdper country. By default it uses the countryassociated with the customer. If multiplecountry support is required, a template percountry has to be created and applied. Thecountry specific partitions have to be usedwith each template.

This template only works for onecluster. This template cannot beapplied for multi-clusterdeployments.

Note

TEHO_AGGR_RP_Template#COUNTRY#

In the templates, use the first sheet in the workbook to fill in the variables for provider, reseller, and customername. This auto-fills the remaining template sheets with the correct data. Load the template into the systemand use either another bulk loader or the GUI to add the translation pattern.




• $Route List ID—TEHO-LBO-#LOCATION-ID#

TEHO Translation Provisioning Guideline


• Pretranslated Number—Provision route pattern requiring TEHO

• Posttranslated Number—Provision number of X's contained in the Route Pattern

• Target—Select all locations where TEHO is required

• Feature Configuration Template—for example, TEHO_LBO_#LOCATION-ID#_RP_Template




15

Cisco HCS Dial Plan Model with Enhanced Number TranslationTail End Hop Off Template


For more information about TEHO, see http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/uc8x.html

InterCluster Voice Mail Route Pattern TemplateThe ENT_Gx_InterClusterVM_RP_Templatev# (where x is any Dial Plan Model G1, G2, or G3, and # is thetemplate version number) provides a template to create route patterns for voicemail access. This template isused at the Customer level.

Table 14: InterCluster VM RP Template


This template is used to create RPs for VM access.It cannot be used for MultiCluster deployments.

VM_RP_TemplateTail EndHop-Off(TEHO)





The $Route List ID is RL-UNITY#VMCPID#.

InterCluster Voice Mail Route Pattern Translations Provisioning Guideline


• Pretranslated Number—Route Pattern for VM access

• Posttranslated Number—Number of X's contained in the Route Pattern


• Feature Configuration Template—VM_RP_Template





16

Cisco HCS Dial Plan Model with Enhanced Number TranslationInterCluster Voice Mail Route Pattern Template

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/uc8x.html

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/uc8x.html

Small Contact Center Route Pattern TemplateThe ENT_Gx_Small_CC_RP_Templatev# (where x is any Dial Plan Model G1, G2, or G3, and # is thetemplate version number) provides a template to create route patterns for a Small Contact Center. This templateis used for a customer or a customer location.

Table 15: Small Contact Center RP Template


This template is used to create RPs for Small ContactCenter. The ENT template overwrites the routepattern that has been created by the Dial Plan modelsand modifies the route pattern to prefix the CCCPIDbefore routing the call.

SCC_RP_TemplateSmallContactCenter


• $ProviderName—HCS-SCC

• $ResellerName—SCC-Reseller

• $CustomerName—Ent32_scc

• $CCCPID—1041

Small Contact Center Route Pattern Translations Provisioning Guideline


• PretranslatedNumber—Route Pattern toward Session Border Controller or Cisco Unified Border Element- SP Edition



• Feature Configuration Template—SCC_RP_Template





17

Cisco HCS Dial Plan Model with Enhanced Number TranslationSmall Contact Center Route Pattern Template

Country-Specific ENT Templates

Block Collect Calls Template (Brazil)Use the ENT_Gx_Brazil_Block_Collect_Calls_v# (where x is any Dial Plan, G1, G2 or G3, and # is a templateversion number) to define collect call related translation patterns for Brazil.

Table 16: Block Collect Calls Template (Brazil)


This template is used to Block Local andLong Distance Collect Calls in Brazil. ForMulti-Country customers, please useLocation specific templates

Block_Collect_Calls_24HrsLoc_Template

Block_Collect_Calls_WrkHrsLoc_Template

Block_Collect_Calls_24HrsLnkLoc_Template

Block_Collect_Calls_WrkHrsLnkLoc_Template

Block Collect Calls

This template is used to Block Local andLong Distance Collect Calls in Brazil. ForBrazil only customers, you can useCustomer Specific Templates.

Block_Collect_Calls_24HrsCust_Template

Block_Collect_Calls_WrkHrsCust_Template


• $ProviderName—HCSArcLab

• $ResellerName—HCSArcReseller

• $CustomerName—HCSArcCustomer

As a default, Collect Calls are supported by the Brazilian Dial Plan. If a customer does not wish to supportCollect Calls, they can be blocked by provisioning them using this ENT Template.

Block Collect Calls (Brazil) Number Translations Provisioning Guideline


• Pretranslated Number—0.90XXXXXXXXXX or 0.9090XXXXXXXX or 0.90909XXXXXXXX, etc.

• Posttranslated Number—Leave it blank

• Target—Location or Customer

• Feature Configuration Template—Choose from one of the above




18

Cisco HCS Dial Plan Model with Enhanced Number TranslationCountry-Specific ENT Templates


Forced Authorization Codes Template (USA)Use the ENT_G3_USA_Per_Location_FAC_Tmplatev# (where # is a template version number) to defineCall Allowed Translation Patterns for the United States. This template applies to the Shared Instance DialPlan (G3) only.

Table 17: Forced Authorization Code (FAC) Template (USA)


This template is used to define perlocation Forced Authorization Codesfor National Calls.

USA_Per_Loc_FAC_Natl_Call_TemplateFAC provisioningfor National Calls

This template is used to define perlocation Forced Authorization Codesfor International Calls.

USA_Per_Loc_FAC_Intl_Call_TemplateFAC provisioningfor InternationalCalls


• $ProviderName—SP-SHD

• $ResellerName—Reseller1

• $CustomerName—SMB101

Use these templates to provision FAC codes for National and International calls. If the FAC code applies toboth National and International, then provision them for both templates. If the FAC code is only applicableto one of the call types, then use the appropriate template.

FAC Codes (USA) Number Translations Provisioning Guideline


• Pretranslated Number—Provision Forced Authorization Code

• Posttranslated Number—NULL


• Feature Configuration Template—USA_Per_Loc_FAC_Natl_Call_TemplateUSA_Per_Loc_FAC_Intl_Call_Template





19

Cisco HCS Dial Plan Model with Enhanced Number TranslationForced Authorization Codes Template (USA)

Forced Authorization Codes Template (Turkey)Use the ENT_G3_TUR_Per_Location_FAC_Tmplatev# (where # is a template version number) to defineCall Allowed Translation Patterns for Turkey. This template applies to the Shared Instance Dial Plan (G3)only.

Table 18: Forced Authorization Code (FAC) Template (Turkey)


This template is used to define perlocation Forced Authorization Codesfor National Calls.

TUR_Per_Loc_FAC_Natl_Call_TemplateFAC provisioningfor National Calls

This template is used to define perlocation Forced Authorization Codesfor International Calls.

TUR_Per_Loc_FAC_Intl_Call_TemplateFAC provisioningfor InternationalCalls

This template is used to define perlocation Forced Authorization Codesfor Mobile Calls.

TUR_Per_Loc_FAC_Mobl_Call_TemplateFAC provisioningfor Mobile Calls


• $ProviderName—SP-SHD

• $ResellerName—Reseller1

• $CustomerName—SMB101

Use these templates to provision FAC codes for National and International calls. If the FAC code applies toboth National and International, then provision them for both templates. If the FAC code is only applicableto one of the call types, then use the appropriate template.

FAC Codes (Turkey) Number Translations Provisioning Guideline


• Pretranslated Number—Provision Forced Authorization Code

• Posttranslated Number—NULL


• Feature Configuration Template—TUR_Per_Loc_FAC_Natl_Call_TemplateTUR_Per_Loc_FAC_Intl_Call_Template




20

Cisco HCS Dial Plan Model with Enhanced Number TranslationForced Authorization Codes Template (Turkey)



21



22


Documents

Cisco HCS Dial Plan Model with Enhanced Number Translation · Cisco HCS Dial Plan Model with Enhanced Number Translation ... Extension Dialing Template ... TEHO_LBO_#LOCATION-ID#_RP_Template