Cisco HCS Dial Plan Model with Enhanced Number Translation

Transcription

1 Cisco HCS Dial Plan Model with Enhanced Number 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 Translations Enhanced Number Translations (ENTs) allow you to load and customize Route Patterns and Translation Patterns for individual customer foundation HCS-G1 and HCS-G2 dial plans. ENTs support a number of customer-specific requirements such as Allowing and Blocking number ranges, supporting short-code dialing 1

2 Extension Dialing Template Cisco HCS Dial Plan Model with Enhanced Number Translation both at the Customer and Location level, routing calls to inter-cluster trunks, and routing calls to a third-party PBX. Before ENTs are loaded, ENT Feature Configuration Templates (FCTs) must first be loaded at the Customer level. 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 that use these FCT templates. Note ENT translation patterns can load either Route Patterns or Translation Patterns. The FCT templates define whether the pattern creates a route pattern or a translation pattern. 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 Unified Communications 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 Translation Pattern Elements. Then load the "Add Customer Number Translation Pattern" and "Add Location Number Translation Pattern" worksheet. (Unhash required FCTs and ENTs as required.) Extension Dialing Template In order to support extension dialing with or without a prefix, the intrasite translation pattern is removed from the Cisco HCS Dial Plan Model. When a new location (or site) is added for a customer, an ENT-based translation pattern is provisioned for that location based on the extension dialing template. The template consists of the following columns (only nonblank columns are shown). Table 1: Extension Dialing Templates Provider Name Reseller Name Customer Name Feature Configuration Template Name Translation Pattern Name Translation Pattern Partition Name Calling Search Space Name Value HCSArcLab HCSArcReseller HCSArcCustomer IntraSite_G1_Template Extension #PRETRANSLATEDNUM# AllowInternal IncomingToSite-CSS Service provider name. Reseller name. Customer name. ENT template name. Translation pattern name. Pretranslated number. This value is taken from the GUI. The partition name to be used for extension dialing. It is created by the model. Next CSS to be used in the call routing. This CSS is created by the model. 2

3 Cisco HCS Dial Plan Model with Enhanced Number Translation Extension Dialing with Prefix Template Route Action Calling Mask Calling Line Presentation Calling Name Presentation Called Mask Value Route #SITECODE##SITEMASK# Default Default #SITECODE##SITEMASK# The route action is to route the call. The calling mask in the template is defined as SLC+Extension. Calling line presentation number is taken from the GUI. Calling name presentation is taken from the GUI. The SLC is prefixed to the posttranslated number taken from the GUI. Extension Dialing with Prefix Template Table 2: Extension Dialing with Prefix Template The following table shows the template you use for a customer or a customer location. Extension Dialing with Extension Prefix ENT_G1_IntraSite_ExtPfx_Template In this use case, a prefix is used for extension dialing. The extension prefix is provisioned as a pretranslated number. The calling party DN is displayed as a calling party number. Extension Dialing with a Prefix Number Translations Provisioning Guideline 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

4 Intrasite Dialing Template Cisco HCS Dial Plan Model with Enhanced Number Translation Intrasite Dialing Template This 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 Extension Dialing CLIR Extension Dialing CLIR Extension Dialing ENT_G1_IntraSite_Templatev# (where # is the template version number) IntraSite_G1_Template IntraSiteLnkChild_G1_Template IntraSiteCLIR_Unres_G1_Template IntraSiteCLIRLnkChild_Unres_G1_Template IntraSiteCLIR_Res_G1_Template IntraSiteCLIRLnkChild_Res_G1_Template This is the current capability provided by the G1 Dial Plan Model. The Calling Party DN is displayed as the Calling Party Number. Use these templates if internal calls dialed as extensions are to be displayed (not restricted). Use these templates only if internal calls dialed as extensions are to be displayed as restricted. 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

5 Cisco HCS Dial Plan Model with Enhanced Number Translation InterCluster Call Routing Templates Target Select All Locations Feature Configuration Template for example, IntraSite_G1_Template InterCluster Call Routing Templates Table 4: InterCluster Call Routing Templates The following table shows the templates to use for a customer or a customer location. In the table, x is any Dial Plan (G1, G2, or G3) and # is the template version number. InterCluster Call Routing InterCluster Call Routing ENT_Gx_InterClusterTrunk_RP_Templatev# ENT_Gx_InterClusterTrunk_Unmanaged_RP_Templatev# This template is used create InterCluster route patterns. Use any one of the locations in the cluster to provision the RP. This template includes three template options and can be used to create RPs to an unmanaged MGCP, H323, or SIP PBX. Use any one of the locations in the cluster to provision the RP. 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 into the system $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 100s as in 234XXXX, then provision RP as 234XXXX. For individual extension, provision RP as an Extension Example: Posttranslated Number Number of X's contained in the RP (optional) 5

6 Intersite Dialing with or Without an ISP Template Cisco HCS Dial Plan Model with Enhanced Number Translation Target Location specific (Use any one location to provision the RP) Feature Configuration Template 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 = X Figure 1: InterCluster Call Routing Template Example Intersite Dialing with or Without an ISP Template This template defines translation patterns for Intersite Call routing. Since ISP is included in the Site Location Code (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 the calling line and calling name presentation are set to default instead of <blank>. 6

7 Cisco HCS Dial Plan Model with Enhanced Number Translation Intersite Dialing with or Without an ISP Template Table 5: Intersite Dialing Templates Intersite Dialing (with an ISP) Intersite Dialing (without an ISP) Intersite Dialing (CLIR) ENT_G1_InterSite_Templatev# (where # is the template version number) InterSite_G1_Template InterSite_G1_Template InterSiteLnkChild_G1_Template InterSiteCLIR_G1_Template The ISP is included in the SLC. This is a special case of Intersite Dialing (with an ISP). The only difference is that the first digit of the SLC is not an ISP. You do not use any variables; the same template can be used for this use case. Note For Intrasite dialing, the extension prefix template is used in order to avoid a conflict. This template is used to provision Calling Line Identification Restriction translation patterns. Intersite Dialing Number Translations Provisioning Guideline Pretranslated Number X (value taken from the template) Posttranslated Number X (value taken from the template) Target Select All Locations Feature Configuration Template for example, InterSite_G1_Template 7

8 Intersite Call to Unmanaged Location in vpgw Cisco HCS Dial Plan Model with Enhanced Number Translation Intersite Call to Unmanaged Location in vpgw The 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 the vpgw. 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 InterSite Call to Unmanaged Location in the vpgw vpgw_unmanaged_location_rp_template This template is to be used to create RPs to an unmanaged Location/PBX on the vpgw. Note The Route List to the vpgw name must be RL_to_VPGW. 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 and PostTranslateNumber=X Posttranslated Number X (see example above) Target Customer Feature Configuration Template vpgw_unmanaged_location_rp_template 8

9 Cisco HCS Dial Plan Model with Enhanced Number Translation Local Calling Template Local Calling Template The following table shows the template to use for a customer or a customer location. Table 7: Local Calling Template Local Call ENT_Gx_Local_Calling_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is a template version number). This template includes: Local_Call24Hr_Template Local_CallStd_Template Local_CallLLBO24Hr_Template Local_CallLLBOStd_Template There are several countries that have variable length local dialing. For example, in India and Mexico, the length of the area code + local number is fixed at 10, but they have variable length area codes from two to four digits. So if the length of the area code is two digits, then the length of the local number is eight digits. The local template can be used to customize translation patterns per location. Note There are four templates to provision local call (one for each partition). Ensure that the translation patterns for all four templates are provisioned. 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

10 Short Code Dialing Template Cisco HCS Dial Plan Model with Enhanced Number Translation Short Code Dialing Template Table 8: Short Code Dialing Template Use the following table to determine which templates to use for a customer or a customer location. Short Code Dialing ENT_Gx_ShortCode_Dialing_Templatev# (where x = any Dial Plan, G1, G2, or G3, and # = template version number). This template includes: This template provides an ability to create short codes for commonly-used services such as help, operator, maintenance, and voice mail. Note Only intracompany short code dialing is supported. Short code patterns are location specific or applied to all locations. The translation pattern is assigned to the AllowInternal<site> partition. Short Code Dialing Number Translations Provisioning Guideline Pretranslated Number Short code (Example: #1) Posttranslated Number Expanded number (Example: ) 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 Template The 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 voic access code to a voic number. 10

11 Cisco HCS Dial Plan Model with Enhanced Number Translation Blacklist or Call Blocking Template Table 9: Short Code Voice Mail Dialing Template Short Code Dialing VM_Dialing_Template This template provides an ability to create short codes for commonly-used services such as help, operator, maintenance, and voice mail. The VM short code pattern is location-specific or can be applied to all locations. The translation pattern is assigned to the AllowInternal<site> partition. Short Code Voice Mail Translations Provisioning Guideline Pretranslated Number Short code (Example: #1) Posttranslated Number Expanded number (Example: ) 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 Template Use the ENT_Gx_Block_Call_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is a template version number) to define call-blocking translation patterns. Table 10: Blacklist/Call Blocking Translation Pattern Blacklist or Call Blocking Block National Calls Block_Call_Template Block_Natl_Call_Template You can add Blacklist or Blocking translation patterns for each customer or location as required. Block National calls to pre-defined translation patterns. 11

12 Calling Party Screening Template Cisco HCS Dial Plan Model with Enhanced Number Translation Block International Calls Block_Intl_Call_Template Block International calls to pre-defined translation patterns. Provision the translation pattern to be blocked as pretranslated number. If the blocking pattern is for a PSTN Number, 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: ) Posttranslated Number X Target Customer level Feature Configuration Template for example, Block_Call_Template Calling Party Screening Template Table 11: Calling Party Screening Template Use the ENT_Gx_Calling_Pty_Screening_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is a template version number) to reject inbound calls from provisioned Calling Party Numbers. Blacklist or Call Blocking Calling_Pty_Screening_Template You can add Blacklist or Blocking translation patterns for each customer. 12

13 Cisco HCS Dial Plan Model with Enhanced Number Translation Allow Call Template Provision the translation pattern to be blocked as pretranslated number. If the blocking pattern is for a PSTN Number, 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 International calls 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 Posttranslated Number X Target Customer level Feature Configuration Template for example, Calling_Pty_Screening_Template Allow Call Template Use the ENT_Gx_Allow_Call_Templatev# (where x is any Dial Plan, G1, G2 or G3, and # is a template version number) as follows to define call-allowed translation patterns. Table 12: Allow Call Template List of Allowed Calls Allow National Calls Allow International Calls Allow_Call_Template Allow_Natl_Call_Template Allow_Intl_Call_Template Allow calls only to a limited number of dialing patterns. Allow predefined National translation patterns when all National Calls are blocked. Allow predefined International translation patterns when all International Calls are blocked. 13

14 Tail End Hop Off Template Cisco HCS Dial Plan Model with Enhanced Number Translation Please provision the Translation Pattern to be allowed as Pre-Translated Number. If the allowed pattern is for a PSTN Number, please include the PSTN Prefix. The following Partitions are available for use in the Templates. Please use the Blocking Partition to define the Allowed call Template since the Blocking Partition will be included in the COS assigned to the user. To allow exceptions for National Calls, use BlkNatl-#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 Template The Tail End Hop Off (TEHO) feature is used to route PSTN calls through a local gateway at the remote location that is closest to the dialed number. Route patterns are created for each destination code that requires TEHO. For example, If you have a local gateway in United Kingdom and want to deploy TEHO for calls to the United Kingdom, you need to build a route pattern for +44 calls that point to a route list containing the gateway in United Kingdom as the primary route 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

15 Cisco HCS Dial Plan Model with Enhanced Number Translation Tail End Hop Off Template Table 13: TEHO Route List Currently, the Route Groups created by Cisco Unified Communications Domain Manager when you add Local Gateways 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 version number) contains the templates shown in the following table. Use the ENT templates to provision each route pattern that requires TEHO. Tail End Hop-Off (TEHO) TEHO_LBO_#LOCATION-ID#_RP_Template TEHO_AGGR_RP_Template#COUNTRY# This template is to be used to create TEHO route patterns This template is to be used to create TEHO RPs. Additionally this template has to be created per country. By default it uses the country associated with the customer. If multiple country support is required, a template per country has to be created and applied. The country specific partitions have to be used with each template. Note This template only works for one cluster. This template cannot be applied for multi-cluster deployments. In the templates, use the first sheet in the workbook to fill in the variables for provider, reseller, and customer $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

16 InterCluster Voice Mail Route Pattern Template Cisco HCS Dial Plan Model with Enhanced Number Translation For more information about TEHO, see uc8x.html InterCluster Voice Mail Route Pattern Template The ENT_Gx_InterClusterVM_RP_Templatev# (where x is any Dial Plan Model G1, G2, or G3, and # is the template version number) provides a template to create route patterns for voic access. This template is used at the Customer level. Table 14: InterCluster VM RP Template Tail End Hop-Off (TEHO) VM_RP_Template This template is used to create RPs for VM access. It cannot be used for MultiCluster deployments. 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 Target Customer Feature Configuration Template VM_RP_Template 16

17 Cisco HCS Dial Plan Model with Enhanced Number Translation Small Contact Center Route Pattern Template Small Contact Center Route Pattern Template The ENT_Gx_Small_CC_RP_Templatev# (where x is any Dial Plan Model G1, G2, or G3, and # is the template version number) provides a template to create route patterns for a Small Contact Center. This template is used for a customer or a customer location. Table 15: Small Contact Center RP Template Small Contact Center SCC_RP_Template This template is used to create RPs for Small Contact Center. The ENT template overwrites the route pattern that has been created by the Dial Plan models and modifies the route pattern to prefix the CCCPID before routing the call. $ProviderName HCS-SCC $ResellerName SCC-Reseller $CustomerName Ent32_scc $CCCPID 1041 Small Contact Center Route Pattern Translations Provisioning Guideline Pretranslated Number Route Pattern toward Session Border Controller or Cisco Unified Border Element - SP Edition Posttranslated Number X Target Customer Feature Configuration Template SCC_RP_Template 17

18 Country-Specific ENT Templates Cisco HCS Dial Plan Model with Enhanced Number Translation 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 template version number) to define collect call related translation patterns for Brazil. Table 16: Block Collect Calls Template (Brazil) Block Collect Calls Block_Collect_Calls_24HrsLoc_Template Block_Collect_Calls_WrkHrsLoc_Template Block_Collect_Calls_24HrsLnkLoc_Template Block_Collect_Calls_WrkHrsLnkLoc_Template Block_Collect_Calls_24HrsCust_Template Block_Collect_Calls_WrkHrsCust_Template This template is used to Block Local and Long Distance Collect Calls in Brazil. For Multi-Country customers, please use Location specific templates This template is used to Block Local and Long Distance Collect Calls in Brazil. For Brazil only customers, you can use Customer Specific Templates. $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 support Collect 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 XXXXXXXX or XXXXXXXX, etc. Posttranslated Number Leave it blank Target Location or Customer Feature Configuration Template Choose from one of the above 18

19 Cisco HCS Dial Plan Model with Enhanced Number Translation Forced Authorization Codes Template (USA) Forced Authorization Codes Template (USA) Use the ENT_G3_USA_Per_Location_FAC_Tmplatev# (where # is a template version number) to define Call Allowed Translation Patterns for the United States. This template applies to the Shared Instance Dial Plan (G3) only. Table 17: Forced Authorization Code (FAC) Template (USA) FAC provisioning for National Calls FAC provisioning for International Calls USA_Per_Loc_FAC_Natl_Call_Template USA_Per_Loc_FAC_Intl_Call_Template This template is used to define per location Forced Authorization Codes for National Calls. This template is used to define per location Forced Authorization Codes for International 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 to both National and International, then provision them for both templates. If the FAC code is only applicable to 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 Target Select All Locations Feature Configuration Template USA_Per_Loc_FAC_Natl_Call_Template USA_Per_Loc_FAC_Intl_Call_Template 19

20 Forced Authorization Codes Template (Turkey) Cisco HCS Dial Plan Model with Enhanced Number Translation Forced Authorization Codes Template (Turkey) Use the ENT_G3_TUR_Per_Location_FAC_Tmplatev# (where # is a template version number) to define Call Allowed Translation Patterns for Turkey. This template applies to the Shared Instance Dial Plan (G3) only. Table 18: Forced Authorization Code (FAC) Template (Turkey) FAC provisioning for National Calls FAC provisioning for International Calls FAC provisioning for Mobile Calls TUR_Per_Loc_FAC_Natl_Call_Template TUR_Per_Loc_FAC_Intl_Call_Template TUR_Per_Loc_FAC_Mobl_Call_Template This template is used to define per location Forced Authorization Codes for National Calls. This template is used to define per location Forced Authorization Codes for International Calls. This template is used to define per location Forced Authorization Codes for 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 to both National and International, then provision them for both templates. If the FAC code is only applicable to 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 Target Select All Locations Feature Configuration Template TUR_Per_Loc_FAC_Natl_Call_Template TUR_Per_Loc_FAC_Intl_Call_Template 20

21 Cisco HCS Dial Plan Model with Enhanced Number Translation Forced Authorization Codes Template (Turkey) 21

22 Forced Authorization Codes Template (Turkey) Cisco HCS Dial Plan Model with Enhanced Number Translation 22