Release 3.1 and Later Releases: Configuring Cisco StadiumVision Director for External Triggers

Table Of Contents

Configuring Cisco StadiumVision Director for External Triggers

Contents

Prerequisites for Cisco StadiumVision Director for External Triggers

Restrictions for Cisco StadiumVision Director for External Triggers

Information About External Triggers in Cisco StadiumVision Director

Overview of External Triggers

Multiple Venues

Input Trigger Support

Output Trigger Support

HTTP Methods and URLs for External Triggers

Input Trigger HTTP Methods and URLs

Output Trigger HTTP Methods and URLs

Authentication for External Triggers

Input Trigger Authentication

Output Trigger Authentication

External Trigger Actions

Input Trigger Actions

Output Trigger Actions

Use Cases for External Triggers

Moment of Exclusivity Use Case for Input Triggers

Moment of Exclusivity Use Case for Input and Output Triggers

Management Dashboard Registry Settings

Management Dashboard Registry Settings for Input Triggers

Management Dashboard Registry Settings for Output Triggers

How to Configure Cisco StadiumVision Director for External Triggers

How to Configure Input Triggers

Defining an Input Trigger

Configuring the HTTP Method for Input Triggers

Configuring Authentication for Input Triggers

Configuring Actions for a Received Trigger

How to Configure Output Triggers

Defining an Output Trigger

Configuring Actions for an Output Trigger

Enabling and Disabling an External Trigger

How to Monitor External Trigger History

How to Configure Advanced External Trigger Settings in the Registry

Feature Information for Cisco StadiumVision Director External Triggers

Configuring Cisco StadiumVision Director for External Triggers

---

First Published: May 29, 2012

Revised: March 8, 2013

This document is intended for Cisco StadiumVision Director administrators who are responsible for working with third-party developers and system integrators to establish connectivity for external input triggers to initiate certain actions by the Cisco StadiumVision Director software, such as to start an event script to control display of content for a desired "moment of exclusivity" or make an emergency notification at a venue.

Beginning in Cisco StadiumVision Director Release 3.1, output triggers also can be configured by the administrator to send a Hypertext Transfer Protocol (HTTP) request to notify external systems of a script event and trigger an action externally. This functionality can be used with the Cisco StadiumVision Mobile Streamer to trigger actions on mobile devices, such as for ad insertion.

Contents

•Prerequisites for Cisco StadiumVision Director for External Triggers

•Restrictions for Cisco StadiumVision Director for External Triggers

•Information About External Triggers in Cisco StadiumVision Director

•How to Configure Cisco StadiumVision Director for External Triggers

•How to Monitor External Trigger History

•How to Configure Advanced External Trigger Settings in the Registry

•Feature Information for Cisco StadiumVision Director External Triggers

Prerequisites for Cisco StadiumVision Director for External Triggers

Before you configure Cisco StadiumVision Director for External Triggers, be sure that the following requirements are met:

•Your backend devices that support contact closure, such as the Crestron QM-RMC Room Media Controller, are installed and properly configured by a qualified system integrator for your third-party devices.

•If you are going to support contact-closure triggers coming inbound from hardware, then the physical signal must be converted to an IP-based HTTP request by some conversion device, such as a General-Purpose Input/Output (GPIO) gateway.

•If you want to support output triggers from Cisco StadiumVision Director to a GPIO-controlled device or system, then you will need to convert the HTTP request to a GPIO signal using a device to make that signal conversion.

•For input triggers, the Cisco StadiumVision Director server is reachable by the contact closure application or device on the Internet Protocol (IP) network. For output triggers, the GPIO device or external HTTP server should be reachable by Cisco StadiumVision Director.

Restrictions for Cisco StadiumVision Director for External Triggers

Before you configure Cisco StadiumVision Director for External Triggers, consider the following restrictions:

•The Triggers interface is not venue aware, which means that you cannot apply venue-specific scope of control using the venue selector. All triggers have a global scope in Cisco StadiumVision Director.

•The Event Trigger Application Programming Interface (API) calls are one-way.

•The script duration, proof of play, and staging registry settings are global and cannot be configured on a per-action basis.

•Both HTTP and HTTPS protocols are automatically available and unable to be individually disabled.

•No payload in an HTTP POST can be passed to the external system in an output trigger.

•You can configure an output trigger to loop back to Cisco StadiumVision Director using an input trigger, but no verification is made to prevent a loop.

•If you are saving a trigger in the enabled state, at least one HTTP action must be configured. Otherwise, you will get an error while attempting to save the trigger.

Information About External Triggers in Cisco StadiumVision Director

This section includes the following topics:

•Overview of External Triggers

•HTTP Methods and URLs for External Triggers

•Authentication for External Triggers

•External Trigger Actions

•Use Cases for External Triggers

•Management Dashboard Registry Settings

Overview of External Triggers

This section describes the input and output trigger support in Cisco StadiumVision Director.

Multiple Venues

The Triggers interface in the Setup area of the Cisco StadiumVision Director Control Panel is not venue aware. All defined triggers in Cisco StadiumVision Director are global in scope in a centralized Cisco StadiumVision Director server configuration with multiple venues. However, triggers can be applied to venue-associated scripts.

Input Trigger Support

Cisco StadiumVision Director Release 3.0 and later supports an HTTP-based API that a software or hardware contact closure source can use to trigger one or more actions by the Cisco StadiumVision Director software.

Cisco StadiumVision Director has 16 default (with a configurable maximum of 256) input trigger IDs that serve as placeholders for a Cisco StadiumVision Director administrator to define and enable for your system. The user interface options are defined in Extensible Markup Language (XML) code that can be accessed by an application using the Event Trigger API.

---

Note If you want to control external triggers from a software application, you can contact your Cisco Systems representative to obtain the Event Trigger API that is made available by special agreement. "TriggerSVD" is an example of a third-party demo application for the Event Trigger API on iOS (supporting Apple iTouch, iPhone, and iPad products) and is available as a free download from the iTunes store.

---

Building management and life safety systems as well as the broadcast control room in a stadium typically allow external integration by using dry contact closure and/or GPIO devices. It is expected that networked surveillance cameras, video routers, and other broadcast equipment already have these input/output (I/O) modules built into the hardware.

Figure 1 shows the different sources of contact closure that can be used as external input triggers to an event script on the Cisco StadiumVision Director server.

•The virtual contact closure option represents a software application that can initiate an HTTP request directly and also use the Event Trigger API for retrieval of input trigger configuration from Cisco StadiumVision Director. You can obtain a free sample third-party software application called "TriggerSVD" on the Apple iTunes site.

•The physical contact closure option represents a hardware device, such as those used for life safety or building management systems, which produce an electrical signal that requires another device to convert the signal to an IP-based HTTP request. Figure 1 Option B shows this conversion being done by a GPIO gateway to initiate the HTTP request after receiving the trigger from the physical contact closure device. The Crestron QM-RMC is an example of a third-party hardware device that accepts two-wire signals and sends commands to Cisco StadiumVision Director.

Figure 1 Input Sources of Contact Closure to Cisco StadiumVision Director

Output Trigger Support

Beginning in Cisco StadiumVision Director Release 3.1, the External Triggers feature supports output triggers which allow a script event to trigger notification to external systems. Cisco StadiumVision Director has 64 default output trigger IDs, with a configurable maximum of 256. These are initially disabled and serve as placeholders for a Cisco StadiumVision Director administrator to define and enable for your system.

Each output trigger is identified or addressed by its trigger ID, numbered sequentially similar to the pins on a GPIO device. An output trigger defines a script event that will be used to trigger one or more outbound actions using an HTTP GET or POST request.

Cisco StadiumVision Director maintains a history of what actions were taken and the responses. An HTTP output request is considered successful when HTTP code 200 (success status) is received.

Figure 2 shows the different methods that can be used as external output triggers from an event script on the Cisco StadiumVision Director server. Just as with input triggers, the supported methods include an HTTP call (like a software-based, virtual contact closure) with a 3rd party application, or a standard contact closure.

In addition, the Cisco StadiumVision Mobile Streamer can be used with the HTTP call method to initiate actions on mobile devices.

Figure 2 Output Trigger Methods From Cisco StadiumVision Director

HTTP Methods and URLs for External Triggers

This section describes the HTTP methods and URLs used to support input and output triggers in Cisco StadiumVision Director.

Input Trigger HTTP Methods and URLs

The HTTP method used by the trigger device can be a GET or POST, depending on the device requirements. You can configure the inbound HTTP method per input trigger in Cisco StadiumVision Director. The default is GET.

---

Note The payload of a POST is ignored by Cisco StadiumVision Director.

---

Each time an external system sends an HTTP request to Cisco StadiumVision Director as an input trigger, the set of actions associated with that input trigger are taken. There is a registry key (ExternalTrigger.input.minInterval) that specifies how much time to elapse before Cisco StadiumVision Director processes any succeeding HTTP request to the same input trigger. For more information, see the "Management Dashboard Registry Settings for Input Triggers" section and the "How to Configure Advanced External Trigger Settings in the Registry" section.

Cisco StadiumVision supports both HTTP and HTTPS API calls using the following sample URLs, where svd-server-ip is the IP address of your Cisco StadiumVision Director server, and id is the number of the input trigger:

•http://svd-server-ip:8080/StadiumVision/ws/rest/trigger/input/id

•https://svd-server-ip/StadiumVision/ws/rest/trigger/input/id

---

Note To further protect access using these URLs, you can configure authentication by both password and IP address. For more information, see the "Authentication for External Triggers" section.

---

Consider the following when using HTTPS:

•Cisco StadiumVision Director uses self-signed certificates. Depending on how the API consumer application is designed, it might require automatic acceptance of the certificate.

•The standard HTTPS port 443 is used.

Output Trigger HTTP Methods and URLs

Just as with input triggers, the HTTP method used by output triggers in Cisco StadiumVision Director can be a GET or POST, depending on the external device or application requirements. You can configure the outbound HTTP method per output trigger in Cisco StadiumVision Director.

---

Note Cisco StadiumVision Director cannot send any payload in a POST request.

---

The URL that Cisco StadiumVision Director specifies in its output HTTP request is determined by the target application or hardware device consuming the trigger event. However, the URL to the target external system must be configured in the output trigger when you define the HTTP action.

Sample Output Trigger URL to GPIO Device

The following is a sample URL when sending an output trigger to a hardware GPIO device:

•http://gpio-server-ip/state.xml?relayXState=n

where:

–gpio-server-ip—Specifies the IP address of the GPIO device.

–X—Specifies the relay number that you want to trigger (1 or 2).

–n—Specifies the numeric value that corresponds to the state that you want to assign to the relay (for example, 0 is off, 1 is on, and 2 pulses the relay on for a default of 1 second, then off).

Sample Output Trigger URL to Cisco StadiumVision Mobile Streamer

The following is a sample URL when sending an output trigger to Cisco StadiumVision Mobile Streamer with a configured data channel and optionally using a third-party client application to process a message string:

•http://svm-streamer-ip/streamer/svd.php?channel=channel-name&message=string1+string2&src_url=http://xyz.com

where:

–svm-streamer-ip—(Required) Specifies the IP address of the Cisco StadiumVision Mobile Streamer.

–channel-name—(Required) Specifies the data channel that is configured in the Cisco StadiumVision Mobile Streamer for your trigger.

For example, a data channel named "d41 - 1.2" would be specified as "channel=d41+-+1.2".

–message=string1+string2—(Optional) Specifies a message string to be sent, where spaces are replaced by "+" symbol.

For example, a message string of "hello world" would be specified as "message=hello+world".

–src_url=http://url—(Optional) Specifies the URL of the third-party application to consume the HTTP request.

For example, a source URL of "stats.com" would be specified as "src_url=http://stats.com".

---

Note For more information about Cisco StadiumVision Mobile Streamer data channel configuration, see the

---

Authentication for External Triggers

Cisco StadiumVision Director supports Basic Authorization for both input and output triggers. This section describes the methods supported to secure the use of input and output triggers in Cisco StadiumVision Director.

Input Trigger Authentication

Cisco StadiumVision Director supports two forms of authentication that you can configure per input trigger:

•Username and password

•IP address list

For added security, both forms of authentication can be enabled.

Output Trigger Authentication

Cisco StadiumVision Director supports a username and password authentication that you can configure per output trigger as part of the HTTP action definition.

These are credentials required by the external system. For example, consider an external web server's REST API that can only be called by clients that provide credentials. Then, configure an input trigger (10) in Cisco StadiumVision Director to require authentication. If you wanted to loop an output trigger to that input trigger 10, the username/password for this output trigger must match what is set in input trigger 10.

External Trigger Actions

This section describes the trigger actions that are supported for input and output triggers. For input triggers, you define what script actions should happen when an inbound trigger is received. For output triggers, you define a URL to be sent from Cisco StadiumVision Director when a particular script action occurs.

Input Trigger Actions

Cisco StadiumVision Director can perform certain script actions or TV controls upon receipt of an input trigger. Each input trigger can be configured to have multiple actions.

You can configure the following script actions to occur upon receipt of an input trigger:

•Start a script.

•Stop a script.

•Change to an ad-hoc state.

•Leave the current ad-hoc state.

•Go to the next sequential state.

•Go to the previous sequential state.

You can configure the following TV control actions to occur upon receipt of an input trigger:

•Turn TVs off by group, zone, or device.

•Turn TVs on by group, zone or device.

Output Trigger Actions

Cisco StadiumVision Director supports configuration of a URL to be sent outbound when a designated script starts, stops, or changes to a specified state.

If a script is configured in an outbound trigger, and then you remove the script (or you remove a state, and the trigger refers to a state in the script), Cisco StadiumVision Director will auto-disable the trigger.

Use Cases for External Triggers

This section provides a high-level description of some specific use cases for input and output triggers in Cisco StadiumVision Director.

Moment of Exclusivity Use Case for Input Triggers

Figure 3 shows the use case of a single button that can be used when a goal occurs during the match that can trigger multiple display changes at once, including a Cisco StadiumVision Director event script change to an ad-hoc state that displays new content on multiple TVs in the venue.

Figure 3 Moment of Exclusivity for a Goal During Match with Input Trigger

Moment of Exclusivity Use Case for Input and Output Triggers

Figure 4 also shows the use case of a moment of exclusivity for a goal during a match. In this example, an input trigger occurs when a single button is used to identify a goal. Cisco StadiumVision Director responds to the input trigger action with an event script change to an ad-hoc state that displays new content on multiple TVs in the venue. In addition, an output trigger is defined that sends an output URL to the Cisco StadiumVision Mobile Streamer that displays a message on mobile devices.

Figure 4 Moment of Exclusivity for a Goal During Match with Input and Output Triggers

Management Dashboard Registry Settings

This section describes the registry keys in the Cisco StadiumVision Management Dashboard for input and output triggers. The registry values are global and apply to all input or output triggers.

Management Dashboard Registry Settings for Input Triggers

Table 1 describes the registry keys in the Management Dashboard that support input trigger configuration and operation.

Table 1 Default Registry Settings for Input Triggers 

Registry Key	Default	Description
ExternalTrigger.input.count	16	Number of allowable input triggers. The range is 1-256.
ExternalTrigger.input.history.days	7	Maximum number of days that the input trigger history is kept before it is purged.
ExternalTrigger.input.minInterval	5	Minimum length of time (in seconds) that must transpire between receipt of two input triggers of the same ID to avoid processing as a duplicate.
ExternalTrigger.input.script.duration	0	Script duration in seconds. The default is zero, which specifies that the script plays forever.
ExternalTrigger.input.script.pofp	true	Proof-of-play setting when a script starts due to an input trigger. The values are true or false. The default is true, which enables proof of play.
ExternalTrigger.input.script.staging	true	Content staging setting when a script starts due to an input trigger. The values are true or false. The default is true, which enable content staging.

Management Dashboard Registry Settings for Output Triggers

Table 2 describes the registry keys in the Management Dashboard that support output trigger configuration and operation.

Table 2 Default Registry Settings for Output Triggers 

Registry Key	Default	Description
ExternalTrigger.output.count	64	Number of allowable output triggers. The range is 1-256.
ExternalTrigger.output.history.days	7	Maximum number of days that the output trigger history is kept before it is purged.1
ExternalTrigger.output.initialDelay	0	Length of time (in seconds) to wait before processing the first configured trigger action. This registry is ignored if an output trigger is disabled.
ExternalTrigger.output.interActionDelay	0	Length of time (in seconds) to wait before processing the next configured action in the output trigger. This delay does not account for the time required to send an HTTP request to the external system. This registry is ignored if an output trigger is disabled.

1 The scheduled task named "ExternalTriggerHistoryCleanupTask" purges expired entries in the trigger history.

How to Configure Cisco StadiumVision Director for External Triggers

This section includes the following topics:

•How to Configure Input Triggers

•How to Configure Output Triggers

How to Configure Input Triggers

This section includes the following tasks:

•Defining an Input Trigger (required)

•Configuring the HTTP Method for Input Triggers (optional)

•Configuring Authentication for Input Triggers (optional)

•Configuring Actions for a Received Trigger (required)

Defining an Input Trigger

By default, Cisco StadiumVision Director supports 16 placeholder triggers that are undefined (unmapped) in the user interface. To support an external trigger, you need to define one of the unmapped triggers and enable it.

You can change this number of supported triggers in the Management Dashboard registry. For more information see the "How to Configure Advanced External Trigger Settings in the Registry" section.

To define an input trigger, complete the following steps:

---

Step 1 Log into the Cisco StadiumVision Director server as an administrator.

Step 2 From the main menu click Control Panel > Setup.

Step 3 Click Triggers.

Step 4 In the Input Triggers list, select a trigger number that is "Not Configured."

The trigger that you selected is highlighted and the trigger configuration is shown in the Basics panel on the right (Figure 5).

Figure 5 New Input Trigger Basics Panel

Step 5 In the Name box, type a name for the external trigger.

Step 6 (Optional) Configure the HTTP method.

For more information, see the "Configuring the HTTP Method for Input Triggers" section.

Step 7 (Optional) Configure authentication of the trigger source.

For more information, see the "Configuring Authentication for Input Triggers" section.

Step 8 Configure the actions for the trigger.

For more information, see the "Configuring Actions for a Received Trigger" section.

Step 9 To activate the trigger, click the Enable checkbox.

---

Tip You can only enable a trigger if actions are defined for it.

---

For more information, see the "Enabling and Disabling an External Trigger" section.

Step 10 Click Save.

---

Configuring the HTTP Method for Input Triggers

The default HTTP method is a GET operation in Cisco StadiumVision Director. A GET operation is also required for external devices that use the Event Trigger API to get the list of defined triggers.

Cisco StadiumVision Director ignores any payload updates that might be included in a POST operation. Therefore, you only need to configure the HTTP method if your device only supports the POST HTTP method, or if for some reason you prefer to support a POST.

To configure the HTTP method for input triggers, complete the following steps:

---

Step 1 From Control Panel > Setup > Triggers, select a trigger number in the Input Triggers list.

The configuration for the trigger that you selected appears in the Basics panel.

Step 2 In the Inbound HTTP Method drop-down box, click the arrow to display options and select GET or POST (Figure 6).

Figure 6 Inbound HTTP Method

Step 3 Click Save.

---

Configuring Authentication for Input Triggers

You can authenticate an external input trigger by user name and password, and/or IP address.

---

Note The trigger user name and password has no relationship to any Cisco StadiumVision Director user accounts. You can define any ASCII set of characters for an external trigger user name and password.

---

You can configure multiple IP addresses to be accepted using a semi-colon separator between addresses, and also using an asterisk (*) as a wildcard symbol to match any number that appears in the position where the asterisk is specified.

For example, 10.10.10.* accepts an external input trigger from any IP address in the range 10.10.10.0 through 10.10.10.255.

To configure authentication for input triggers, complete the following steps:

---

Step 1 From Control Panel > Setup > Triggers, select a trigger number in the trigger list.

The configuration for the trigger that you selected appears in the Basics panel.

Step 2 To authenticate the external trigger by username and password:

a. Select the Require Authentication checkbox (Figure 7).

b. In the User Name box, type the user name that you want to allow.

c. In the Password box, type the password for the specified user name.

Figure 7 Require Authentication for Input Triggers

Step 3 To authenticate the external trigger by IP address:

a. Select the Verify Inbound IP Addresses checkbox.

b. In the Address List box, type one or more IP addresses separated by a semi-colon (;).

Figure 8 Verify Inbound IP Addresses

Step 4 Click Save.

---

Configuring Actions for a Received Trigger

Cisco StadiumVision Director can perform certain script actions or TV controls upon receipt of an input trigger. Each input trigger can be configured to have multiple actions.

The script and device controls available for selection are based on what is already configured in the Cisco StadiumVision Director Control Panel.

To configure the actions for a received trigger, complete the following steps:

---

Step 1 From Control Panel > Setup > Triggers, select a trigger number in the trigger list.

The configuration for the trigger that you selected appears in the Basics panel.

Step 2 Click Actions.

The Actions panel is displayed (Figure 9).

Figure 9 Input Trigger Actions Panel

Step 3 Click the plus (+) icon to add an action for the selected input trigger.

The Action dialog box opens.

Step 4 At the top of the dialog box, select the drop-down list and choose one of the following actions and associated sub-options shown in the figure below and described in Table 3:

Table 3 External Trigger Script Actions and Sub-Options 

Action Name	Sub-Options	Description
Change Script State	•Script—Select the script name for the action. •State—Select the state to which to change. Example:	Change to an ad-hoc state of a specified script.
Leave Script State	Script—Select the script name for the action. Example:	Leave the current ad-hoc state of a specified script.
Next Script State	Script—Select the script name for the action. (See Leave Script State example).	Go to the next sequential state of a specified script.
Previous Script State	Script—Select the script name for the action. (See Leave Script State example).	Go to the previous sequential state of a specified script.
Start Script or Stop Script	Script—Select the script name for the action. (See Leave Script State example).	Start or stop a specified script.
TV Off or TV On	•Target type—Select whether you want to specify Devices, Groups, or Zones. •Select—Choose one or more checkboxes beside devices, groups, or zones to which the action applies. Example:	Turn TVs off or on by device name, group, or zone.

Step 5 Click Ok.

The action that you added is shown under the Actions panel of the Input Triggers screen.

Step 6 Repeat from Step 2 to add multiple actions for the trigger.

Step 7 When you have finished adding actions, click Save.

---

How to Configure Output Triggers

This section includes the following tasks:

•Defining an Output Trigger (required)

•Configuring Actions for an Output Trigger (required)

•Enabling and Disabling an External Trigger (required)

Defining an Output Trigger

By default, Cisco StadiumVision Director supports 64 placeholder triggers that are undefined (unmapped) in the user interface for output triggers. To support an external trigger, you need to define one of the unmapped triggers and enable it.

You can change this number of supported triggers in the Management Dashboard registry. For more information see the "How to Configure Advanced External Trigger Settings in the Registry" section.

To define an output trigger, complete the following steps:

---

Step 1 Log into the Cisco StadiumVision Director server as an administrator.

Step 2 From the main menu click Control Panel > Setup.

Step 3 Click Triggers.

Step 4 Click Output Triggers.

Step 5 In the Output Triggers list, select a trigger number that is "Not Configured.

The trigger that you selected is highlighted and the trigger configuration is shown in the Basics panel on the right (Figure 10).

Figure 10 New Output Trigger Basics Panel

Step 6 In the Name box, type a name for the external trigger.

Step 7 Configure the Event Type, by completing the following steps:

a. In the Event Type drop-down box, choose the type of script event that will be used to initiate the output trigger actions.

–ChangeScriptState—Specifies that output trigger actions begin when a change to the specified state for the selected script occurs.

–StartScript—Specifies that output trigger actions begin when the specified script starts.

–StopScript—Specifies that output trigger actions begin when the specified script stops.

b. In the Script drop-down box, select the script name for the specified event type.

c. (ChangeScriptState only) In the State drop-down box, select the state of the specified script that will be used to initiate the output trigger actions.

Step 8 Configure the actions for the trigger.

For more information, see the "Configuring Actions for an Output Trigger" section.

Step 9 To activate the trigger, click the Enable checkbox.

---

Tip You can only enable a trigger if actions are defined for it.

---

For more information, see the "Enabling and Disabling an External Trigger" section.

Step 10 Click Save.

---

Configuring Actions for an Output Trigger

Cisco StadiumVision Director can send an output URL based on a specified script event. Each output trigger can be configured to have multiple actions.

The scripts available for selection are based on what is already configured in the Cisco StadiumVision Director Control Panel.

To configure the actions for an output trigger, complete the following steps:

---

Step 1 From Control Panel > Setup > Triggers, select a trigger number in the trigger list.

The configuration for the trigger that you selected appears in the Basics panel.

Step 2 Click Actions.

The Actions panel is displayed (Figure 11).

Figure 11 Output Trigger Actions Panel

Step 3 Click the plus (+) icon to add an action for the selected output trigger.

The HTTP Action dialog box opens (Figure 12).

Figure 12 HTTP Action Dialog Box for Output Triggers

Step 4 In the HTTP Method drop-down box, click the arrow to display options and select GET or POST.

Step 5 To specify authentication for the outbound URL, click the Verify Credentials checkbox (Figure 13).

Figure 13 Verify Credentials for Output Triggers

a. In the User Name box, type the user name that you want to allow.

b. In the Password box, type the password for the specified user name.

Step 6 In the URL box, type the URL to be sent by the output trigger when the specified event type occurs.

---

Note Enter only a single URL in this box. Be careful if you are copying and pasting from another source to be sure that the entire URL appears correctly and as a single string.

---

Step 7 Click Ok.

The action that you added is shown in a list in the Actions panel of the Output Triggers screen.

Step 8 Repeat from Step 3 to add multiple actions for the trigger.

Step 9 When you have finished adding actions, click Save.

---

Enabling and Disabling an External Trigger

You can define external triggers in Cisco StadiumVision Director, but independently enable or disable them from operation. By default, external triggers are disabled.

Disabled triggers are indicated by a gray checkmark in the Status column of the corresponding trigger. When a trigger is enabled, the checkmark turns green in the Status column for the trigger name.

---

Note You can only enable a trigger if actions are defined for it.

---

To enable and disable an external trigger, complete the following steps:

---

Step 1 From Control Panel > Setup > Triggers, click Input Triggers or Output Triggers.

Step 2 Select a trigger number in the trigger list.

The configuration for the trigger that you selected appears in the Basics panel.

Step 3 In the Basics panel, do one of the following:

•To enable the external trigger configuration, select the Enabled checkbox.

A checkmark appears in the box when the option has been enabled.

•To disable the external trigger configuration, select the Enabled checkbox to clear the checkmark.

Step 4 Click Save.

---

How to Monitor External Trigger History

You can view a log of activity for a particular external trigger using the History feature. There is currently no way to see a global set of events that occurred.

To monitor external trigger history, complete the following steps:

---

Step 1 From Control Panel > Setup > Triggers, click Input Triggers or Output Triggers.

Step 2 Select a trigger number in the trigger list.

The configuration for the trigger that you selected appears in the Basics panel.

Step 3 Click History.

The logged messages and times for the selected trigger are displayed.

---

How to Configure Advanced External Trigger Settings in the Registry

You can change some of the default settings for external triggers in the Cisco StadiumVision Director registry. Be certain that you understand the purpose and impact of the registry values before changing.

Refer to Table 1 for a description of the registry keys and their default values.

To configure advanced external trigger options in the registry, complete the following steps:

---

Step 1 Log into Cisco StadiumVision Director server as an administrator.

Step 2 From the main menu, click Management Dashboard.

Step 3 Using the Management Dashboard drawers, go to Tools > Advanced > Registry.

Step 4 In the Registry Data box, find the keys that begin with "ExternalTrigger."

Step 5 In the Value box for the ExternalTrigger key that you want to change, type the new value that you want to apply.

Step 6 Click Apply.

Step 7 Click OK when the "Registry values saved (success)" message appears.

---

Feature Information for Cisco StadiumVision Director External Triggers

Table 4 lists the release history for this feature.

Table 4 Feature Information for Cisco StadiumVision Director External Triggers 

Date	Releases	Feature Information
March 8, 2013	Release 3.1.0-510	Output trigger support was added.
May 29, 2012	Release 3.0.0-247	Initial release for Cisco StadiumVision Director Release 3.0.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2013 Cisco Systems, Inc. All rights reserved.