Cisco HCS Dial Plan Model for Generic Leaf Cluster

Transcription

1 Cisco HCS Dial Plan Model for Generic Leaf Cluster Generic Leaf Cluster, page 1 Model Basics, page 3 Model Worksheets, page 4 Base Data, page 5 Unified Communications Manager Model, page 11 Additional Features, page 11 Transactional Model, page 25 Generic Leaf Cluster The generic leaf cluster workbook is used to provision the Unified Communications Manager. The workbook consists of the following worksheets. Note Worksheet numbering (CCM 6.1.x) in the following table refers to the earliest Cisco Unified Communications Domain Manager model that the worksheets were supported in; the numbering is fixed and has no significance for Cisco HCS or the Cisco Unified Communications Manager being provisioned. Table 1: Generic Leaf Cluster Worksheets Worksheet Notes The Notes tab is used to capture Revision History. CCM 6.1.x* - Clear Models This worksheet is used to clear all the existing models before loading a new Dial Plan Model. CCM 6.1.x* - Time Periods The generic Cisco HCS model supports two time periods: AllDay (Monday to Sunday: 00:00 to 24:00) StandardHours (Monday to Friday: 07:00 to 18:00). 1

2 Generic Leaf Cluster Cisco HCS Dial Plan Model for Generic Leaf Cluster Worksheet CCM 6.1.x* - Time Schedules CCM 6.1.x* - TP to TS Mappings CCM 6.1.x* - Partitions CCM 6.1.x* - CSS CCM 6.1.x* - Partition-CSS Map CCM 6.1.x* - COS-CSS Mappings CCM 6.1.x* - Route Patterns CCM 6.1.x* - Translate Patterns CCM 6.1.x* Transform Patterns CCM 6.1.x* Called Xformations CCM 6.1.x* CTI Route Points The generic Cisco HCS model supports two time schedules: AllDay and StandardHours. This worksheet is used to map Time Periods to Time Schedules. Time Period AllDay is mapped to Time Schedule AllDay. Time Period StandardHours is mapped to Time Schedule StandardHours. This worksheet is used to create partitions on the Unified Communications Manager. The partitions may be cluster-wide or per location. This worksheet is used to create calling search spaces on the Unified Communications Manager. The CSSs may be cluster-wide or per location. This worksheet is used to define mappings between CSSs and Partitions defined earlier. The Unified Communications Domain Manager GUI does not expose CSSs to users, but rather exposes Class of Service to users. This worksheet is used to map class of service to a CSS. This worksheet is used to create route patterns on the Unified Communications Manager. The country-specific route patterns are captured in the Country Dial Plans directory, while the feature-related route patterns are captured in the Addon directory. This worksheet is used to create translation patterns on the Unified Communications Manager. The country-specific Translation patterns are captured in the Country Dial Plans directory, while the feature-related translation patterns are captured in the Addon directory. This worksheet is used to define Calling Party Number (CgPN) Transformation for: Incoming PSTN Calls that are forwarded back to PSTN through aggregation where CgPN consists + Incoming PSTN Calls that are forwarded back to PSTN using LBO where CgPN consists + CgPN Transformation for non-cisco-emergency-responder-based calls. This worksheet is used to define Called Party Number (CdPN) Transformation. None is defined for Cisco HCS. This worksheet is used to define CTI Route Points. None are defined for Cisco HCS. 2

3 Cisco HCS Dial Plan Model for Generic Leaf Cluster Model Basics Worksheet CCM 6.1.x* H.323 Trunks CCM 6.1.x* SIP Trunks CCM 6.1.x* Route Lists CCM 6.1.x* Route Groups CCM 6.1.x* RL-RG Mappings CCM 6.1.x* RG-H.323 Trunk Maps CCM 6.1.x* RG-SIP Trunk Maps CCM 6.1.x* Regions CCM 6.1.x* Global Settings CCM 6.1.x* Network Locales CCM 6.1.x* Country Details CCM 6.1.x* Device Pools CCM 6.1.x* CTI Ports CCM 6.1.x* Call Park CCM 6.1.x* AAR Groups This worksheet is used to define H.323 Trunk to unmanaged PBX. This worksheet is used to define Intercluster SIP trunks and SIP trunk to unmanaged PBX. This worksheet is used to define route lists toward aggregation local gateway other clusters unmanaged PBX This worksheet is used to define route groups toward aggregation (Manual) local gateway other clusters unmanaged PBX. This worksheet is used to map route groups to routelists. This worksheet is used to map route group to Intercluster H.323 Trunk to unmanaged PBX. This worksheet is used to map route groups to SIP trunks. Not used This worksheet is used to define Global Settings. For more information, see worksheet. This worksheet is used to define Network Locale Name, CCM Network Locale, and Language Locale (optional) for each country. Not used Not used Not used Not used Not used * Supports Cisco Unified Communications Manager 6.1 or later Model Basics The Dial Plan Model is detailed by configurable Microsoft Excel workbooks. Each spreadsheet in a Cisco HCS model workbook corresponds to the configurations of different elements within the target product 3

4 Model Worksheets Cisco HCS Dial Plan Model for Generic Leaf Cluster (Unified Communications Manager, Cisco vpgw Softswitch, and so on), such as Unified Communications Manager partitions or Unified Communications Manager calling search spaces. Generally, all the configuration elements detailed in the model worksheets correspond to a transaction that occurs during the provisioning workflow. Therefore you always see a transaction name associated with the elements that you are configuring to tell the system when to provision those elements. A transaction is defined as a singular element during the provisioning life cycle for a customer or can occur multiple times, for example, when locations are added to that customer. Model Worksheets The Cisco HCS consists of the following standard model files. The files and directories are loaded to Cisco Unified Communications Domain Manager in the listed order. Because there are multiple files for the Cisco HCS Dial Plan Model, there is a model configurator tool that allows the service provider or your Cisco representative to select the countries from the country dial plan and features from the Addon directory. The configurator tool then combines all the selected files in to one Excel spreadsheet. Table 2: Model Files and Directories Node Base Data Unified Communications Manager IOS SME Cisco PGW mml Cisco PGW x10 Filenames Dial Plan Specific Platform Specific Generic Leaf Cluster Country DP Generic IOS Generic SME Generic Cisco PGWmml Generic Cisco PGWx10 These files are released along with the Dial Plan Model. They are loaded to Cisco Unified Communications Domain Manager using the Bulk Loader. The Dial Plan Model for Unified Communications Manager is split into several directories. The base DP model is specified in the generic leaf cluster spreadsheet. The country-specific Dial Plans are specified in the Country DP Directory. The Dial Plan Model for Cisco IOS gateways is defined in the Generic IOS spreadsheet. The Dial Plan Model for SME is defined in the Generic SME spreadsheet. The Dial Plan Model for Cisco PGW is defined in the Generic Cisco PGWmml spreadsheet. The Dial Plan Model for Cisco PGW Times Ten Database is defined in the Generic Cisco PGW Times Ten Database spreadsheet. The preceding directories and files are described in the following sections. 4

5 Cisco HCS Dial Plan Model for Generic Leaf Cluster Base Data Base Data The Base Data directory consists of two files: Dial Plan Specific Base Data Platform Specific Base Data The Base Data files are loaded using the Bulk Loader in Unified Communications Domain Manager. Note Be sure that you are using the latest Bulk Loader files. Download the base data from software.cisco.com/download/navigator.html?mdfid. To locate the latest files for this release, navigate as follows: Downloads Home > Cisco Products > Unified Communications > Call Control > Hosted Collaboration > Cisco Hosted Collaboration Solution (HCS) > Cisco Hosted Collaboration Solution Version 10.0 > Unified Communications Domain Manager (CUCDM) Bulk Loaders>. When you load new base data, existing base data is not overwritten. Platform Specific Base Data The Platform Specific Base Data workbook consists of the following worksheets: Table 3: Platform Specific Base Data Worksheets Worksheet Notes Add Brands Add Phone Types Add Expansion Module Types Associate Phone Expansion Set System Preferences This worksheet is used to specify revision history and changes made to the workbook. This worksheet is used to define all brands that are supported by the Cisco HCS deployment. This worksheet is used to define all the phone types that are supported by the Cisco HCS deployment. This worksheet is used to define all the expansion modules that are supported by the Cisco HCS deployment. This worksheet is used to associate phone types with the expansion modules that are supported by the Cisco HCS deployment. This worksheet is used to define Cisco Unified Communications Domain Manager level preferences such as time zone, auditing, banners, and so on. 5

6 Dial Plan Specific Base Data Cisco HCS Dial Plan Model for Generic Leaf Cluster Worksheet Add Hardware Sets This worksheet is used to define the hardware set that is used in a Cisco HCS deployment. The generic hardware set (Cisco HCS-Basic) consists of: Unified Communications Manager Cisco36xx Series Router (CUBE) IOS Device (local gateways) ISC interface Technician (Legacy PBX) Cisco Unity (voic ) Cisco Emergency Responder Session Management Edition Cisco PGW and Cisco PGW TimesTen database Associate Hardware Sets Add Feature Display Policies Raw Data-Security Profiles Prev FDPolicies This worksheet is used to associate the hardware set to a dial plan. The generic hardware set Cisco HCS-Basic is linked to Cisco HCS Dial Plan Cisco HCS-G1. This worksheet is used to define Feature Display Policies. Not used Not used Dial Plan Specific Base Data The Dial Plan Specific Base Data workbook consists of the following worksheets: Table 4: Dial Plan Specific Base Data Worksheets Worksheet Notes Add Service Types This worksheet is used to specify revision history and changes made to the workbook. This worksheet is used to define service types (Classes of Service) that can be assigned to end users. The service types are used to define outbound and call forwarding restrictions. 6

7 Cisco HCS Dial Plan Model for Generic Leaf Cluster Predefined Telephone Class of Service Types Worksheet Add Number Construction Set Dial plan Preferences Add Countries This worksheet is used to define the Dial Plan name (Cisco HCS-G1) and number construction rules for both Unified Communications Manager and internal use for Unified Communications Domain Manager. These rules are applied globally to all the enterprises. This worksheet is used to define preferences for both the Internal and PSTN published numbers. This worksheet is used to define all the countries supported by the Cisco HCS. Predefined Telephone Class of Service Types Table 5: Class of Service Types Cisco Unified Communications Domain Manager uses class of service to assign calling restrictions to an end user. The class of service is mapped by Dial Plan Model to a calling search space and partitions that are understood by Unified Communications Manager. The classes of service in the following table are used in Unified Communications Domain Manager. These class of service types are loaded without loading the AddOn features (described later in this guide in Additional Features, on page 11). Class of Service TempOutOfService International24Hrs-Enhanced International24Hrs-Standard Calling Search Space TempOutOfService-CSS Intl24HrsEnh-CSS Intl24HrsStd-CSS Temporary Out of Service Class of Service - Only allows emergency dialing International 24 hours Enhanced - No restrictions International 24 hours Standard - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls InternationalWrkHrs-Enhanced InternationalWrkHrs-Standard IntlWrkHrsEnh-CSS IntlWrkHrsStd-CSS International Working Hours Enhanced - No restrictions during standard working hours International Working Hours Standard - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls 7

8 Predefined Telephone Class of Service Types Cisco HCS Dial Plan Model for Generic Leaf Cluster Class of Service National24Hrs-Enhanced Calling Search Space Natl24HrsEnh-CSS National 24 Hours Enhanced - Following calls are blocked: International calls National24Hrs-Standard Natl24HrsStd-CSS National 24 Hours Standard - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls International calls National24Hrs-Restricted Natl24HrsRst-CSS National 24 hours Restricted - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls International calls Mobile calls NationalWrkHrs-Enhanced NatlWrkHrsEnh-CSS National Working Hours Enhanced - Following calls are blocked during standard working hours: International calls NationalWrkHrs-Standard NatlWrkHrsStd-CSS National Working hours Standard - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls International calls NationalWrkHrs-Restricted NatlWrkHrsRst-CSS National Working hours Restricted - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls International calls Mobile calls 8

9 Cisco HCS Dial Plan Model for Generic Leaf Cluster Predefined Telephone Class of Service Types Class of Service Local24Hrs-Enhanced Calling Search Space Local24HrsEnh-CSS Local 24 hours Enhanced - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls International calls Mobile calls National calls Internal Only Internal CLIR CLIRInternational24Hrs-Enhanced CLIRInternational24Hrs-Standard CLIRInternationalWrkHrs-Enhanced CLIRInternationalWrkHrs-Standard CLIRIntl24Hrs-FAC CLIRNational24Hrs-Enhanced Internal-CSS InternalCLIR-CSS CLIRIntl24HrsEnh-CSS CLIRIntl24HrsStd-CSS CLIRIntlWrkHrsEnh-CSS CLIRIntlWrkHrsStd-CSS CLIRIntl24HrsFAC-CSS CLIRNatl24HrsEnh-CSS Internal - Only on-net calls are allowed Internal Calls with CLIR - Caller ID is not sent International 24 hours Enhanced - No restrictions Caller ID is not sent International 24 hours Standard - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls Caller ID is not sent International Working Hours Enhanced - No restrictions during standard working hours Caller ID is not sent International Working Hours Standard - Following calls are blocked during standard working hours: Caller ID is not sent International 24 Hours Standard - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls Caller ID is not sent and Forced Authorization Code is required National 24 Hours Enhanced - Following calls are blocked: International calls Caller ID is not sent 9

10 Predefined Telephone Class of Service Types Cisco HCS Dial Plan Model for Generic Leaf Cluster Class of Service CLIRNational24Hrs-Restricted CLIRNational24Hrs-Standard CLIRNationalWrkHrs-Enhanced CLIRNationalWrkHrs-Restricted CLIRNationalWrkHrs-Standard Calling Search Space CLIRNatl24HrsRst-CSS CLIRNatl24HrsStd-CSS CLIRNatlWrkHrsEnh-CSS CLIRNatlWrkHrsRst-CSS CLIRNatlWrkHrsStd-CSS National 24 hours Restricted - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls International calls Mobile calls Caller ID is not sent National 24 Hours Standard - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls International calls Caller ID is not sent National Working Hours Enhanced - Following calls are blocked during standard working hours: International calls Caller ID is not sent National Working hours Restricted - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls International calls Mobile calls Caller ID is not sent National Working hours Standard - Following calls are blocked during standard working hours: Premium Rate calls Personal Communication Service (PCS) calls International calls Caller ID is not sent 10

11 Cisco HCS Dial Plan Model for Generic Leaf Cluster Unified Communications Manager Model Class of Service CLIRNatl24Hrs-FAC Calling Search Space CLIRNatl24Hrs-FAC National 24 Hours - Following calls are blocked: Premium Rate calls Personal Communication Service (PCS) calls International calls Caller ID is not sent and Forced Authorization Code is required These classes of service map to partitions, calling service spaces, and time periods defined in an Excel spreadsheet. Unified Communications Manager Model The Unified Communications Manager of the leaf cluster model consists of several files and directories: Generic Leaf Cluster Country Dial Plans AddOn Features Additional Features These features are not optional, but are classified as Additional because the features are available in the release but can be decoupled from the generic model, or the features are selectable as part of a deployed Dial Plan. The following features are classified as Additional features: Analog Line class of service (referred to as EmergencyCallsSupport for Analog Gateways) Cisco Emergency Responder Calling Line Identification Restriction (CLIR) Forced Authorization Codes (FAC) Cisco Unified Contact Center Enterprise (Unified CCE) Redirecting, Connected, Called and Calling Transformation Support (RCC-Transformation) Extension Mobility Cross Cluster (EMCC) Generic SIP Trunk (GSIP-Trunk) Forced On-Net Cisco IP Manager Assistant (IPMA) This document does not cover provisioning but describes the role of the feature in the Dial Plan Model. 11

12 Analog Line Class of Service Cisco HCS Dial Plan Model for Generic Leaf Cluster Analog Line Class of Service This feature enables analog ports on H.323 and SIP gateways to be configured with a per-port calling search space when the gateway is activated. The ALineCOS directory contains all the definitions that are required to support this feature; provisioning of this feature is out of scope of this document. The ALineCOS AddOn contains the following definitions to support this feature: A global definition, AnalogGWCSS, in the Add Service Types of the Base Data Bulk Loader file. Assign this service type as the calling search space of the Inbound Calls of the gateway. For each location, create a new partition, AnalogLineCOS-PT and associate it to the new calling search space, AnalogGWCSS. (This calling search space must be the same name as the service type and is hard coded as AnalogGWCSS.) Map the calling search space to the service type with the same name. In the COS-CSS mappings worksheet, add a new column, where a class of service code is assigned to each existing COS-CSS mapping the feature uses. A new translation pattern, #COSCODE#.!, is added to the Translate Pattern Worksheet. Create this translation pattern in Cisco Unified Communications Manager when a user (analog line) is associated to a class of service defined above. The variable is replaced with the Analog Class Of Service Code value that is associated to the class of service and the calling search space is replaced with what is defined in the COS-CSS mapping worksheet. Part of this feature is to support emergency dialing through analog line. For each location within a country, add the following translation pattern to the AnalogLineCOS-PT partition: XX.<Country Emergency Number> XX#EXT#.<CountryEmergencyNumber> Where XX and XX#EXT# is replaced with +02<CountryCode> and the Calling Party Number is prefixed with '*#LRID#' before the translation pattern goes to the emergency routing calling search space. In the case where Cisco Emergency Responder is used, remove only XX and XX.#EXT# before the translation pattern goes to E#ISO#CSS. H.323 and SIP IOS gateway model contains the following new transactions and definitions: [Add/Del]COSRule To add or delete class of service code that is supported on the Gateway. [App/Unapply]COSRule To assign or unassign a class of service to the Analog port/line. 12

13 Cisco HCS Dial Plan Model for Generic Leaf Cluster Cisco Emergency Responder The following call flow shows how class of service is supported for each analog port that is provisioned with this feature: Figure 1: Analog Line Class of Service Cisco Emergency Responder Cisco Emergency Responder is specified for United States deployment where Emergency Responder is used to support enhanced emergency call handling. The following definition is added to the model to support this feature: When a Cisco Emergency Responder server is connected: Partition EUS Calling search space EUSCSS Partition-CSS Map EUS and InterSiteRoutingPT partitions map to EUSCSS Route pattern to handle Default ERL and Default OnSite number in the EUS partition Route pattern to handle enhanced emergency calls with Calling Party Number set as the ELIN number in the EUS partition CTI Route Point to handle 911, 912, and 913, where 912 is for fallback if 911 is unavailable and 913 is to handle callback from the PSAP CTI Port for internal alerting 13

14 Calling Line Identification Restriction Cisco HCS Dial Plan Model for Generic Leaf Cluster When a location is added two translation patterns, 911 and #EXT#.911 are added to the AllowEmerCalls partition of that location and the handover calling search space is set to be EUSCSS. When a line is added to the ERL (for example ELIN) to handle callback from the PSAP through the ELIN number a translation pattern, +1<ELIN number>, is added to the E.164LookUp partition, and the handover calling search space is set to EUSCSS. Calling Line Identification Restriction The Calling Line Identification Restriction (CLIR) setting in the model is based on the system default. In Cisco HCS, the system default should be set to Allowed. This AddOn feature enables per line calling line identification presentation setting to be restricted. The following definition is included in the model to support this feature: Additional service types to set CLIR as the default for the line (for example CLIRInternational24Hrs-Enhanced, CLIRInternational24Hrs-Standard, CLIRNational24Hrs-Enhanced, CLIRNational24Hrs-Standard and also for Working Hours). Addition to the Cisco Unified Communications Manager model Partition, Calling Search Space, Partition-CSS Map, and COS-CSS mapping to support the preceding service type. The following translation patterns are added to the per-country translate pattern worksheet: Translation pattern to handle intrasite calls Translation pattern to handle intersite calls Translation pattern to handle all nonemergency PSTN numbers The preceding translation patterns basically set the calling line to Restricted and handed over to the standard calling search space with the similar name but without CLIR prefix. Example of a call flow for the United States: 14

15 Cisco HCS Dial Plan Model for Generic Leaf Cluster Forced Authorization Code A phone line that is associated to CLIRInternational24Hrs-Enhanced services with the CLIRIntl24Hrs-Enh-CSS dial uses the 9011[^0]![0-9#] pattern (nonemergency PSTN number), has its Calling Line Restriction set to Restricted and call processing passed to Intl24Hrs-Enh-CSS. Figure 2: Calling Line Identification Restriction Forced Authorization Code This feature is used to enable Forced Authorization Code (FAC) in conjunction with route patterns to restrict access to long distance and international calls for certain groups of users. Note FAC is supported in deployments that use Shared Instance but the Forced Authorization Codes are global in nature, and not customer-specific. In the Cisco HCS, add the following to the generic model for this feature: Additional service types for FAC (for example, International24Hrs-FAC and National24Hrs-FAC) New partitions associated to Central and Local PSTN call handling When a provider country is added, create the following partitions to handle call handling through the aggregation: FACIntl24Hrs-<CC>, FACMobl24Hrs-<CC>, FACNatl24Hrs<CC>, and a FAC route selection partition FACRteSelPT-<CC>. When a local gateway is added to a location, create the following partitions: FACILBO24Hrs-<CC>, FACMLBO24Hrs-<CC>, FACNLBO24Hrs-<CC>, and a LBO route selection partition FACRetSelPT-LBO. Add the following partitions to support plus dialing: FACPlusIntl24Hrs-<CC> and FACPlusNatl24Hrs-<CC>. Two new FAC CSS (for example, Intl24HrsFAC-CSS and Natl24HrsFAC-CSS) are added and associated with the preceding item FAC service type. The FAC Calling Search Space contains the same partitions as its equivalent non-fac Calling Search Space except for the following: 15

16 Forced Authorization Code Cisco HCS Dial Plan Model for Generic Leaf Cluster For Handling of International Calls, use FACIntl24Hrs-<CC> instead of AllowIntl24Hrs-<CC> and FACILBO24Hrs-<CC> instead of AllowILBO24Hr-<CC>. For Handling of National Calls, use FACNatl24Hrs-<CC> instead of AllowNatl24Hrs-<CC> and FACNLBO24Hrs-<CC> instead of AllowNLBO24Hr-<CC>. For Handling of Mobile Calls, use FACMobl24Hrs-<CC> instead of AllowMobl24Hrs-<CC> and FACMLBO24Hrs-<CC> instead of AllowMLBO24Hr-<CC>. Add two additional calling search spaces to handle call routing, FACRteSelCSS-<CC> that contains the FACRteSelPT-<CC>, and FACRteSelCSS-LBO, that contains the FACRteSelPT-LBO. For each country added by the Provider Country transaction, add the same route patterns as those defined for non-fac, except that the FAC column is populated with the following: For International Calls routing pattern, set the FAC column to 2. For National Calls routing pattern, set the FAC column to 1. For Mobile Calls routing pattern, set the FAC column to 3. The same call handling is applied to the route pattern for Local Breakout through the Location LocalGateway. For each country that is added by the Provider Country transaction, add translation patterns to handle International, National, and Mobile calls to the appropriate FAC partitions. These translation patterns have the same characteristics as those defined for non-fac, except that the call is handled by 16

17 Cisco HCS Dial Plan Model for Generic Leaf Cluster Cisco Unified Contact Center Enterprise FACRteSelCSS-<CC>. The same is applied to the translation patterns that are added when Location LocalGateway is added. Figure 3: FAC International United States Call Flow Cisco Unified Contact Center Enterprise The dial plan AddOn supports Cisco Unified Contact Center Enterprise (Unified CCE) integration with the following functions: After Unified Communications Manager is added, a partition AllowUCCEXferPT is created. This partition contains the route patterns that are assigned to route calls to the Unified Contact Center server when one of the DNs that is assigned to the CTI route point is dialed. Class of service for Unified Contact Center Agent Line. Provide routing of ingress call based on the assigned Contact Center PSTN Pilot Number to Cisco Unified Border Element (Cisco UBE) from the Cisco PGW through a SBC. Only Cisco PGW routing is provisioned. Translate the Contact Center PSTN Pilot Number associated to a local gateway of a location to an internal Pilot Number (for example Contact Center Pilot DN). Provide routing of Internal Pilot Number (that is, Contact Center Pilot DN) to the Cisco UBE. 17

18 Cisco Unified Contact Center Enterprise Cisco HCS Dial Plan Model for Generic Leaf Cluster Provide routing of VRU number to the Cisco Unified Customer Voice Portal (Unified CVP) server. Handling incoming call from the Unified CVP server. Provide connection to the Unified CVP server and Cisco UBE from the Unified Communications Manager. This leverages the Generic SIP Trunk AddOn feature. All other integration needed to support the Unified Contact Center Enterprise is out of scope of this AddOn. For more information on Unified Contact Center Enterprise, see custcosw/ps1844/prod_installation_guides_list.html. Before the Contact Center is provisioned through Unified Communications Domain Manager, you must create the SIP Connection between the Unified CVP server and Cisco UBE with the Generic SIP Trunk feature (refer to the Generic SIP Trunk (GSIP) section). When the Contact Center Enterprise Server is connected to Unified Communications Manager by Unified Communications Domain Manager, the following dial plan is added: On the Cisco PGW, the AddCCCIP transaction is executed, which creates a dial plan similar to ConnectIPPX but associates it to the Unified Contact Center. The route list used by this dial plan is statically configured. On Unified Communications Manager, the following is created: Routing of VRU number that is returned from CC-UCCE-<CCCPID>-CSS, which contains UCCE-<CCCPID>-PT with the VRU number as the route pattern to route the call to the Unified CVP through the RL-UCCE-CVP-OR-CUBESP-#CCCPID# route list. This route list and its associated route group and trunk are created through the Generic SIP Trunk feature. Routing of VRU number dialed by the Agent AllowUCCEXferPT is populated with the VRU number as a route pattern to route the call to the Unified CVP through the RL-UCCE-CVP-OR-CUBESP-#CCCPID# route list. Figure 4: Call Flow for VRU 18

19 Cisco HCS Dial Plan Model for Generic Leaf Cluster Cisco Unified Contact Center Enterprise Routing of Call Transfer or Conference Call from the Agent AllowUCCEXferPT is populated with the Transfer pattern that was created by Unified Communications Domain Manager as a translation pattern with the handover calling search space set to UCCE-<CCCPID>-CSS. Routing of Transfer or Conference Call to Contact Center Enterprise Server through CTI Route Point A CTI Route Point with the Transfer Pattern (equate to DN and is created by the Unified Communications Domain Manager) and calling search space set to UCCE-<CCCPID>-CSS. Figure 5: Call Flow for Transfer and Conference When Contact Center Service is created by Unified Communications Domain Manager for Unified Communications Manager, an Internal CC Pilot Number Pattern is added to the InterSiteRoutingPT as a route pattern with route list set to RL-UCCE-CUBEE-OR-CUBESP-#CCCPID#. This is to route CC Pilot Number to the Cisco UBE. When a location is created, the following dial plan is added: Two classes of service for Agent Line support - National24Hrs-Standard-wCC and NationalWHrs-Standard-wCC. Calling search spaces - Natl24HrsStdwCC-CSS, and NatlWHrsStdwCC-CSS that contains the same partitions as Natl24HrsStd-CSS and NatlWrkHrsStd-CSS respectively, with the addition of the AllowUCCEXferPT. When Contact Center Internal Pilot number is associated with a PSTN Number, the following is added: On Times Ten Database Add an entry to map the PSTN number to the Unified Contact Center Enterprise server dial plan on the Cisco PGW. On Unified Communications Manager Add as a translation pattern, that transforms PSTN to DN with the handover calling search space set to InterSiteRoutingCSS. 19

20 RCC-Transformation Cisco HCS Dial Plan Model for Generic Leaf Cluster On IOS gateway (H.323 and SIP) Add as a rule in voice translation-rule 9121, 9122, and 802. Figure 6: Call Flow for Pilot Number RCC-Transformation The Redirecting Connected Called (RCC) AddOn feature enables you to perform a number transformation on the redirecting, called, and connected number. Unified Communications Domain Manager uses service type to associate transformation calling search space to the outbound trunk. The following service types are defined: ClusterW-Redirecting-Transformation ClusterW-Connected-Transformation ClusterW-Called-Transformation For ClusterW-Redirecting-Transformation and ClusterW-Connected-Transformation, the following are created: ClusterWDN2DDIMapping-CSS is associated to both service types and contains ClusterWDN2DDIMapping-PT. When a single DN or range of DNs is associated to the DDI, a calling number transformation pattern is added to the CLusterWDN2DDIMapping-PT. For Generic Dial Plan (G1) and Flat Dial Plan (G2) Models, when an outgoing call is made toward PSTN, the Calling Party DN is transformed to DDI. If there is no corresponding DDI number (DN without a DDI number), then 20

21 Cisco HCS Dial Plan Model for Generic Leaf Cluster RCC-Transformation For Generic Dial Plan (G1) Model Site Published Number is sent. For Flat Dial Plan (G2) Model External Mask of the Calling Line is sent. For Shared Instance Dial Plan (G3) Model, when an outgoing call is made toward PSTN, the external mask of the calling line is sent in all cases. For ClusterW-Called-Transformation, the following are created: ClusterWCalledTranf-CSS, which contains ClusterWCalledTranf-PT and FMCCalledTransf-PT. Currently FMC uses the Called Number Transformation. When Unified Communications Domain Manager executes AssociateFMC, a called number transformation pattern is added to the FMCCalledTransf-PT. The Redirecting, Calling, Called and Connected Party Transformation CSS for the Shared Instance Dial Plan (G3) is defined in the following table: Table 6: RCC Party Transformation for Shared Instance Dial Plan (G3) Calling Search Space Transformation Pattern Partition Calling Party Transformation CallingT2AggregCSS \+.! Multiple! CallingT4CFwdCallPT CallingT4EmerCallPT ClusterWDN2DDIMapping-PT The Transformation Pattern is defined to use External Mask. Called Party Transformation ClusterWCalledTransf-CSS NULL \+.#COUNTRY##MOBILE# ClusterWCalledTransf-PT FMCCalledTransf-PT There is no transformation defined for Called Party. Connected Party Transformation Redirecting Party Transformation ClusterWDN2DDIMapping-CSS ClusterWDN2DDIMapping-CSS!! ClusterWDN2DDiMapping-PT ClusterWDN2DDiMapping-PT The Transformation Pattern is defined to use External Mask. Note The external mask for each line is defined as the +E.164 number. Based on the Transformation Patterns defined in the preceding table: For Redirecting Party Transformation: Use External Mask For Calling Party Transformation: Use External Mask For Called Party Transformation: No Transformation 21

22 Extension Mobility Cross Cluster Cisco HCS Dial Plan Model for Generic Leaf Cluster For Connected Party Transformation: Use External Mask Extension Mobility Cross Cluster The EMCC model AddOn is a small part of Extension Mobility Cross Cluster (EMCC), to ensure that emergency calls egress from the originating country where the device resides. To achieve this, the following is added to the model: As a prerequisite, set the calling search space for PSTN Access SIP trunk to use phone's original Device Calling Search Space. When ActiveEMCC is executed, add the following to Unified Communications Manager: EMCC-CSS-<EMCC-CC> containing the EMCC-PT-<EMCC-CC>. Adjunct-CSS-<EMCC-CC> containing the Adjunct-PT-<EMCC-CC>. RL-EMCC, SLRG for route group and their associated RL-RG mapping. SIP trunk with no destination address. EMCC Country Emergency Number as a translation pattern in EMCC-PT-<EMCC-CC>, where EMCC Country is the home country. This translation pattern transforms the Called Emergency to a Global Generic Emergency Number, that is, The Global Generic Emergency Number as a route pattern in the EMCC-PT-<EMCC-CC> with route list set to RL-EMCC. Adjunct Country Emergency Number as a route pattern with Called Number Mask set to and route list set to RL-EMCC. An Adjunct Country is the Visiting Country. 22

23 Cisco HCS Dial Plan Model for Generic Leaf Cluster Interconnect Unified Communications Manager Clusters (Optional) Each country dial plan is enhanced to handle the Global Generic Emergency Number. Figure 7: Call Flow for Extension Mobility Cross Cluster Interconnect Unified Communications Manager Clusters (Optional) This procedure is only applicable where a customer has multiple clusters. Note This step can be added at a later date, when additional clusters are added. Cisco recommends that you conduct this step using the Cisco Unified Communications Domain Manager GUI. 23

24 Generic SIP Trunk Cisco HCS Dial Plan Model for Generic Leaf Cluster Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Go to Network > PBX Devices > CUCM ClusterName > Connectivity > PBX= > PBX for example select Connectivity for VSNetwork > PBX Devices > CUCM ClusterName > Connectivity > PBX= > PBX (For example) select Connectivity for VSC-CL1. Select required extra clusters, for example VSC-CL2. Select Connect IPPBX. Select Trunk Protocol = SIP, and Topology Type = Full Mesh or Star. Modify Trunk s, SIP Profile, Normalization Script and Script Parameters as required. Select Confirm. Monitor the Cisco Unified Communications Domain Manager Transaction logs and Device Logs and confirm that Cisco Unified Communications Domain Manager creates the required InterClusterSIP trunks, Route Groups and Route Lists on each cluster. For example, on VSC-CL1: ICT-SIP-1102, RG-IPPBX-SIP-1102, RL-IPPBX-1102 (where 1102 = CPID of VSC-CL2) on VSC-CL2: ICT-SIP-1101, RG-IPPBX-SIP-1101, RL-IPPBX-1101 (where 1101 = CPID of VSC-CL1). Note When adding connections to another cluster (if customer locations already exist), confirm that Cisco Unified Communications Domain Manager adds the required SLC Route Pattern routing in the remote clusters. Generic SIP Trunk The Generic SIP Trunk (GSIP) feature provides the ability to create, modify, or delete trunks, route groups, route lists and route patterns associated with a connection for SIP. Templates are provided to create elements within the connection (for example, trunks, RL-RG mapping, and route patterns). The naming convention for the template is as follows: AddConnection-<ProtocolType>-<TemplateName>. The only ProtocolType supported is SIP. Within the model the following templates are supported: Unified CCE support: ToCUBE for creating trunks and RL-RG Mappings connection to Cisco Unified Border Element (Cisco UBE). ToCVP for creating trunks and RL-RG Mapping connection to Unified CVP server. Cisco Unity Connection support: ToCisco Unity for creating trunks and RL-RG Mappings connection to Cisco Unity Connection. Generic Aggregation: ToAggregation for creating route pattern, trunks and RL-RG Mappings connection to the aggregation. Aggregation country specific: <ISO CC>_NATL_wPlus, <ISO CC>_INTL_wPlus and <ISO CC>_SVC_wPlus - for <ISO CC>, using a trunk that is created with the ToAggregation template, route pattern and RL-RG Mappings where the External Mask is a National Number and requires +44 to be the prefix to the Mask. 24

25 Cisco HCS Dial Plan Model for Generic Leaf Cluster Forced On-Net <ISO CC>_NATL_woPlus, <ISO CC>_INTL_woPlus and <ISO CC>_SVC_woPlus using a trunk that is created with the ToAggregation template, route pattern and RL-RG Mappings where the External Mask is in plus E.164 format. <ISO CC>_EMR for route pattern and RL-RG Mapping for Emergency call routing (where <ISO CC> is the ISO Country Code, for example GBR for Great Britain). Forced On-Net You can configure all gateways or trunks as Off-Net (external) or On-Net (internal) in Cisco Unified Communications Domain Manager. When an end user dials a PSTN number to another corporate location in the network, the Forced On-Net feature automatically routes the call on-net, maximizing savings by directing traffic over the customer's IP VPN and avoiding international toll charges. There is no transaction on Unified Communications Domain Manager to enable or disable this feature. Forced On-Net is enabled by adding the E.164LookUp partition to the routing calling search space, that is, RouteSelCSS-<CC>. When enabled, Forced On-Net is applicable to all the provider customers. Note On the Cisco PGW, the default setting is Forced On-Net. If you do not require Forced On-Net, on the Provider Country page of the Unified Communications Domain Manager you can configure a set of E.164 ranges to be Forced Off-Net. Note The Forced On-Net feature is not available to Shared Instance Dial Plan (G3) subscribers. IPMA (Model and Cisco Unified Communications Domain Manager) The Cisco IP Manager Assistant (IPMA) feature allows managers and their assistants to work together effectively. This feature comprises a call routing service that enhances the phone capabilities for the manager and the desktop interfaces for both the manager and the assistant. This service intercepts calls that are made to managers and routes them to selected assistants, managers, or other targets based on preconfigured call filters. The manager can change the call routing dynamically. For example, by pressing a soft key press on the phone, the manager can instruct the service to route all calls to the assistant and can receive status on these calls. IPMA can be provisioned in one of two ways: 1 Shared line mode 2 Proxy mode Transactional Model Cisco Unified Communications Domain Manager operates on a transactional model that is called on every user action whether through the web or bulk loading interface. These transactions occur at key steps of building 25

26 Transactional Model Cisco HCS Dial Plan Model for Generic Leaf Cluster the providers and services, and then with Cisco Unified Communications Manager individual activations of customers, locations, phones, and features. For example, when a provider adds a new Cisco Unified Communications Manager to the system, the transaction InitIPPBX must be called to load all the base configurations (namely partitions, calling search spaces, translation patterns, time schedules, so on) as defined in the Dial Plan Model. Administrators and users execute functions or operations on the Unified Communications Domain Manager to carry out certain tasks. For example, the task may be to add a new customer configuration into the network components or to add a new E.164 number range into the Unified Communications Domain Manager database. In Unified Communications Domain Manager, these functions or operations are named "Transactions." A transaction may be a single operation, to add a number into the database for example, or it may include many subtransactions that are executed with a single operation. Every operation, or transaction, is kept in the Unified Communications Domain Manager Transaction log and can be used for searching the status of previous transactions and to even stop or replay individual entries. To summarize, against every action that a user performs on Unified Communications Domain Manager, there is a transaction that runs as a result of this action. The details of the transactions are specified in the model. The model tells the Unified Communications Domain Manager what configuration needs to be executed against a specific transaction. Table 7: Commonly Used Transactions Transactions InitIPPBX AddProviderCountry AddLocation AssociateFNN(Range) ConnectIPPBXIPPBX AddLocationLocalGateway AddSNR Called at the initialization of the Unified Communications Manager by Unified Communications Domain Manager, either by the bulk loading spreadsheet or Static Load Config button on the GUI when adding a Unified Communications Manager. Called when a new country support is needed by the customer. Called when a new location is added. Called to associate Full National Number with internal DN. Called to connect one Unified Communications Manager Cluster with another. Called when local gateway is added to support local PSTN breakout. Called when Single Number Reach feature is added to a location. The dial plan also makes use of variables that are assigned at runtime during a transaction. Model Variables The model must use variables on certain occasions to get runtime information at the time of a transaction execution. A list of the most common variables that apply to Dial Plan follows. The complete list of model variables can be found in the Unified Communications Domain Manager product documentation. 26

27 Cisco HCS Dial Plan Model for Generic Leaf Cluster InitIPPBX Transaction Table 8: Model Variables Variable Name #COUNTRY# #CRID# #CUSTID# #EXT# #ICPID# #INT# #LOCATION-ID# #LRID# #NAT# #POSTTRANSLATEDNUM# #PRETRANSLATEDNUM# #SITE# #SITECODE# #SITEMASK# #TRANSID# #TRANSPARTITION# Country Code Customer Route ID The Customer ID as provisioned for the customer External line access prefix (from the Location) IPBX Call Processor ID The DN to contact the location The Location ID The Location Route ID National number prefix per country (for example, 0 for Great Britain before nationalcode) The posttranslated number as captured in the front-end The pretranslated number (shortcode) as captured in the front-end Location number within customer The Site Location Code (SLC), an enterprise-based site code The Site Extension Mask, a variable site translation mask to match the number of digits in the extensions of a location The incremented number for every number translation added The partition that is mapped to the descriptive name from the front-end InitIPPBX Transaction Cisco Unified Communications Domain Manager uses a once-only transaction called InitIPPBX to load static Cisco Unified Communications Manager configuration on each Cisco Unified Communications Manager cluster. Time Periods and Time Schedules The following time periods, time schedules, and their mapping is created during InitIPPBX transaction. 27

28 InitIPPBX Transaction Cisco HCS Dial Plan Model for Generic Leaf Cluster The generic Cisco HCS model supports two time periods: AllDay Monday to Sunday: 00:00 to 24:00 StandardHours Monday to Friday: 07:00 to 18:00 The generic Cisco HCS model supports two time schedules: AllDay StandardHours The generic Cisco HCS model maps Time Periods to Time Schedules as follows: Time Period AllDay is mapped to Time Schedule AllDay Time Period StandardHours is mapped to Time Schedule StandardHours Calling Search Spaces, Partitions, and Transformation Pattern Cluster-wide partitions are added during the InitIPPBX transaction. The translation patterns associated with these partitions are added while executing other transactions. Table 9: Partitions Partition E.164LookUp FMCLookUp CallingT4EmerCallPT CallingT4CFwdCallPT InterSiteRoutingPT NullPartition IncomingFromCisco Unity CustSC-RLSel-PT Partition containing translation patterns to convert incoming E.164 numbers to a directory number (DN) format Plus E.164 FMC to DN Partition to map calling party DN to DDI mapping for emergency calls Plus handling for call forward calls Handles intersite routing Not used For routing Incoming from Cisco Unity (not used) Route list Selection for Short Code Dialing The following cluster-wide calling search spaces are added, and mapped to above partitions during InitIPPBX transaction: Table 10: Calling Search Spaces CSS IncomingFromAggreg Partitions E.164LookUp 28

29 Cisco HCS Dial Plan Model for Generic Leaf Cluster Initialize the Unified Communications Manager Clusters (InitIPPBX) CSS FMCLookUp InterSiteRoutingCSS CallingT2AggregCSS CallingT2AggregCSS IncomingFromCisco Unity CustSC-RLSel-CSS Partitions E.164LookUp InterSiteRoutingPT CallingT4EmerCallPT CallingT4CFwdCallPT InterSiteRoutingPT CustSC-RLSel-PT CSS assigned to inbound trunk from aggregation layer Intersite routing calling search space Calling Party Transformation Calling Search Space for calls toward aggregation layer Calling search space assigned to incoming trunk from Cisco Unity Connection Route list selection for short code dialing The following transformation pattern is added to handle incoming PSTN number with + and to override route pattern Calling Party transformation when a call is forwarded toward aggregation: Table 11: Transformation Pattern Partition CallingT4CFwdCallPT Transformation Pattern PlusCGPNoverrideRP \+.! Remove + if it exists in the calling party number else do nothing and then prefix + to the calling party number. This is to avoid prefixing another + to the calling party number. Countries The InitIPPBX transaction applies to those countries that are already associated with the customer. Depending on what countries are added at the service provider level in Unified Communications Domain Manager the country relevant model elements are provisioned with the InitIPPBX transaction. Initialize the Unified Communications Manager Clusters (InitIPPBX) Complete this procedure to activate the InitIPPBX and AddProviderIPPBXCountry functions and push the cluster-wide and country-level dial plan models settings to the Cisco Unified Communications Manager cluster. The InitIPPBX step can be run using the Cisco Unified Communications Domain Manager GUI for each cluster. 29

30 Bulk-Load Extension Mobility Cross Cluster Settings (Optional) Cisco HCS Dial Plan Model for Generic Leaf Cluster Procedure Step 1 Step 2 Step 3 Browse to Network > PBX Devices > ClusterName. Scroll to the bottom of the CCM Cluster Management Page and select Load Static Configuration. Alternatively, configure the C1 CUCDM81x VS P1 NetworkElements vy(single Customer)(VSC CL1 CL2) loader sheet as follows (where x is the Cisco Unified Communications Domain Manager version, and y is the sheet version number): a) Hash columns A and B b) Unhash Column C (lines 8 and 9 as required). c) Click Save. d) Rerun the Network Elements loader. e) Confirm that the InitIPPBX load is successful. What to Do Next Review the InitIPPBX transaction device log or log in to the Unified Communications Manager cluster to verify that the cluster-wide and country-level dial plan has been loaded into the Unified Communications Manager cluster. Check for the addition of Partitions, CSSs, RPs, TPs, and so on. Successful completion of the InitIPPBX step is an important milestone in configuring a Cisco HCS Unified Communications Manager cluster, indicating the static configuration has been added correctly. Bulk-Load Extension Mobility Cross Cluster Settings (Optional) This is an optional procedure that is only required for the Extension Mobility Cross Cluster (EMCC) feature where a customer requires EMCC support across multiple clusters, for example between VSC-CL1 and VSC-CL2. Procedure Step 1 Step 2 Configure the C7 CUCDM81x VS P3 NetworkElements-MultiCustomerClusters-MCC-CL1-CL2-vy loader sheet as follows (where x is the Cisco Unified Communications Domain Manager version, and y is the sheet version number): a) Hash columns A, B, C, D, E, and F. b) Unhash column G (lines 8 and 9 as required). c) Click Save. d) Rerun the Network Elements loader. Monitor the Cisco Unified Communications Domain Manager Transaction logs and Device Logs and confirm the required EMCC settings have been added, for example: a) Addition of EMCC countries b) Addition of EMCC Remote Clusters c) Addition of GeoLocation Filters d) Addition of EMCC Feature Parameters 30