Overview

Application configuration occurs at the partition level. A partition is a configuration profile for an application. Applications can support multiple partitions, enabling you to create and execute multiple versions of the same application on a single Cisco Unified Application server.

Understanding Partitions

Partitions are flexible and can be useful in a variety of situations. For example, if an application is intended to serve end users located on distinct Cisco Unified Communications Manager clusters, it is often desirable for all call control and media streams to terminate to the network and telephony resources contained within each cluster. At the same time, it may be desirable to have another configurable protocol on the application, such as LDAP, which makes reference to the same central location, regardless of the partition.

Each partition is associated with a call route group and media resource group. By defining unique call route groups and media resource groups, you can identify the partitions that use individual media engines. For each partition, you can also determine which Cisco Unified Communications Manager cluster is used for making calls by specifying a call route group that corresponds to the particular telephony protocol and group.

Understanding Scripts and Triggers

Each application is also associated with scripts, which are partitioned along with the application. Because multiple scripts can execute actions through the same protocol, you must specify the conditions, or trigger, under which a partitioned script should initiate action.

These are examples of trigger parameters for the following event types:

•Value List —A trigger that activates when a call is received from more than one extension.

•Single Regular Expression—A trigger that activates when a call is received on any of several extensions in a range.

•Combined Method—A trigger that includes a single value trigger that activates when a single extension is called and a regular expression trigger that activates when a call is received from any of a range of extensions.

Note A regular expression is indicated by adding regex: before the expression. You cannot mix literal values and regular expressions in a list. Only a single regular expression can be used as a trigger parameter for a given partition. The syntax [0-9] in a regular expression is equivalent to the Cisco Unified Communications Manager X notation used in route patterns and CTI Route point line numbers.

Application Configuration Example

Assume that an application has one script and three partitions and activates on an IncomingCall trigger. The default partition has no triggering parameters and can act as a catch-all for events which do not match other partitions.

The application server determines the best match handler for a given event. Other partitions take effect if their trigger parameters are activated. For example, if Partition 2 specifies to=2000, then when a call comes in for extension 2000, partition 2 will activate. If no trigger matches, the default partition is active.

A partition is similar to a configuration template for a script and applies these rules:

•The application developer sets the event that triggers a script. The event applies to all partitions and cannot be changed.

•All installed script partitions across all applications are treated as equal.

•If any two partitions have identical triggering criteria, either one may trigger; therefore, it is important that all partitions have unique triggering criteria.

•The router will match the handler that best fits the events. For example, if partition A specifies to=2000 and partition B specifies to=2000 and from=1000, then a call from 1000 to 2000 triggers B.

Note Applications are automatically enabled after they are installed. However, applications created with the Cisco Unified Application Designer are in Running status and Etch-based applications are in Stopped status after install. Etch-based applications enter Running status once executed.

Step 6 Click Add. The partition is added and you return to the application details page.

Step 7 Under Configurations, enter the values as described in Table 5-8.

Note Configuration values are inherited from the default partition, and all unchanged configurations in the new partition remain linked to configurations in the default partition. These configuration values are updated in the new partition to match any changes made to them in the default partition.

Table 5-8 Configuration Details

Field

Description

Preferred Codec

Preferred media resource codec.

CallRoute GroupId

Call route group ID (used only when making outbound calls).

The protocol of the inbound call is determined by the configuration of the Cisco Unified Communications Manager. Specifically, its configuration determines which protocol is used when routing the call to the Cisco Unified Application Server device appearance.

Locale

Locale for this partition.

Note The supported locales listed can be different across applications. The list is dependent on which locales the application's developer has designated as supported.

EarlyMedia

Reserve media ports (for reduced set up time)

Enabled

Enabled when selected.

Media Resource Group

Cisco Unified Media Engine group closest to the IP endpoints using this application.