Configuring Edge Policies

Use Edge Policies to create event-based actions that are stored and executed on specific controllers. These policies can trigger URL Actions that perform tasks in external devices. For example, when a user swipes their badge at a reader device, a URL action can be sent to the Cisco VSM system to start recording surveillance video for that location.

Differences Between Edge Policies and Global I/O Triggered URL Actions

·         Edge Policies are stored on the Controller, and are triggered immediately when an event occurs, even if network communication with the ICPAM server is delayed or lost.

·         Global I/O rules might not execute immediately due to network delays, rules processing, communication between ICPAM and the controllers, or other factors.

·         Global I/O rules, however, offer additional options for automation rule triggers and subsequent actions. In addition, URL Actions for an Edge Policy are limited to the subset of events that can be triggered by the controller.

See Configuring Global I/O Automated Rules instructions to create global automation rules.

Procedure

Complete the following instructions to create or modify edge policies:

Note     This example assumes that the controllers, readers, doors, personnel accounts, and other components are installed, configured, and working properly. For instructions, see the other chapters in this guide, including Creating a phone service in UCM and System Configuration Settings .

Step 1            Enable the Edge Policy menu.

a.  Select System Configuration from the Admin menu.

b.  Select the Advanced Setting tab.

c.  Select the check box for the Enable “Edge Policies” Module option.

d. Click Save.

e.  Log out (select Logout from the Options menu), then log back in to the ICPAM application to activate the changes.

Step 2            Select Doors > Edge Policies > Edge Policy.

Step 3            Click Add, or select an existing rule and click Edit.

edge_policy_list.png

Step 4            Enter a name and description for the rule.

add_edge_policy.png

Tip           Select or de-select Enabled to activate or deactivate the policy.

Step 5           Define the Trigger type.

The trigger defines the event (such as Door Grant Access) and the devices (such as a controller) for the trigger. When the specified event occurs on the specified device, the Edge Policy action is triggered.

Release 1.3 and later support event triggers.

a.  Match – Select Any trigger.

b. Type – Select Event.

Step 6            Define the Trigger.

The trigger defines an event that occurs on a device. When this triggers occurs, the action for the Edge Policy is invoked.

a.  Click Add New to select the event and device(s) used to trigger the rule.

Tip   You can also use the Add available button to choose a previously defined trigger (condition).

To create, edit or delete the saved triggers, select Doors > Edge Policies > Conditions.

b. Enter the General properties:

§        Name—enter a meaningful name. For example, Access Lobby Door.

§        Description—enter the trigger description. For example, Access door event at lobby door.

c.  Switch to the Event page and select the event for the trigger.

§        Select an event from the left column then move it to the right column by clicking the top button.

d.  Switch to the Devices page and select the devices that the event must occur on.

§        Filter by—select the device. For example, Gateway.

§        Device Type—shows the available device types. For example, Door.

§        Select—highlight a device in the Available column, and click the arrow to move it to the Selected column.

§        Device(s)—click Choose and select an available device (such as a Door) and move it to the Selected field.

e.  Verify that the selected device name appears in the Devices field.

f.  Click Save and Close.

11_auto_tasks00267.jpg

Step 7         Back in the Add Edge Policy window, switch to the Action page, and specify the action that will be performed when the trigger condition(s) are met.

·         URL Action—select a URL Action that will occur when the conditions are met. See the Configuring URL Actions . The URL action must be an Edge action type.

Note       For Cisco VSM video recording, use create a soft trigger event in VSM to generate the URL used to record video. Enter that URL in the URL action.

Step 8          Click Save and Close to save the changes. The new or revised policy is displayed in the main window.

Step 9          Right click on the affected controller, and choose the Apply Configuration Changes command from the pop-up menu to activate the rule.

See Applying Configuration Changes for more information.

Note   The controllers must be in the Up state, signified by a green triangle in the icon. A dark green triangle means there are configuration changes that have not been applied.

 

See also:

Configuring Automated Tasks

Configuring Device I/O Rules