Specifications

5-46
Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions
OL-14010-09
Chapter 5 Configuring System Components
Managing Triggers
This type of trigger can only be used if an IVR license has been purchased and installed on the system.
For details on how to configure and use HTTP triggers, see the Cisco Unity Express Interactive Voice
Response CLI Administrator Guide.
Configuring Multiple Triggers for an Application
Your network may require multiple triggers for one or more Cisco Unity Express applications. For
example, the following are some scenarios where multiple triggers for the same application are useful:
• Multiple language support—You have an auto-attendant application which you want to deploy in
two different languages. One way to achieve this would be to have two different triggers (call-in
numbers) pointing to the same application, but with different values for the locale parameter.
For example, assume that you have call-in numbers 6700 and 6900 (both pointing to the same
auto-attendant application), the locale for the trigger 6700 is configured to be xx_XX, and the locale
for the trigger 6900 is configured to be yy_YY. If the callers dial 6700, they will hear the
auto-attendant greetings in the language xx_XX. If the callers dial 6900, they will hear the
auto-attendant greetings in the language yy_YY.
• Different call treatment for internal and external callers—You have an auto-attendant application,
and you want to provide slightly different Menu options for internal and external callers. In other
words, you want to provide an option to the internal callers to transfer to the inventory department,
but you do not want to present this option to the external callers. One way to achieve this would be
to have two different triggers (call-in numbers) pointing to the same application, and by making a
branching decision in your script by checking the called number using the “Get Call Contact Info”
step.
Repeat the procedure described in the “Configuring SIP Triggers for the Applications” section on
page 39 and the “Configuring JTAPI Triggers for the Applications (Cisco Unified
Communications Manager Only)” section on page 43 (depending on your deployment mode) to create
multiple triggers for an application.
Sharing Ports Among Applications and Triggers
Accessing an Application
The maximum number of callers that can access an application concurrently is determined by two
parameters:
• The maxsessions value configured for the triggers invoking the application.
• The maxsessions value configured for the application itself.
If more calls than the trigger's configured maxsession value are received, callers hear a busy tone.
If more calls than the application's configured maxsession value are received, Cisco Unity Express plays
an error prompt to the callers.
The following example shows how the maxsessions values for applications and triggers play a role in
how many active calls can be made to an application. In this example:
• Your module has 8 ports.
• You assigned the auto-attendant application a maxsessions value of 5.
• You configured 2 triggers both invoking the same auto-attendant application.