Managing Handlers

In the Handlers and Monitor Handlers pages of the Server Configuration page you can activate and deactivate primary and monitor handlers. All published handlers are listed on these pages. Once you publish a handler using Interaction Designer, the handler appears in the Inactive Handlers list, unless it is already an Actively running handler. CIC begins to use Activated handlers as soon as another event occurs for which the handler is registered. If Interaction Processor is currently running older versions of the handler, those threads finish before the new handler is used. Any threads running on handlers you deactivate continue until the thread is finished.

After installing CIC and publishing all handlers, you must activate the primary handlers on the Handlers page and the monitor handlers on the Monitor Handlers page. The fastest way to do this is:

1. On the Handlers page, select all of the handlers in the Inactive Handlers list (for example, use the Shift key and multi-select the entire list) and add them to the Active Handlers list.

2. Look carefully at each entry in the Active Handlers list and double-click on the handlers that end with or contain the word "'monitor"'. These are the monitor handlers. They should be in the Inactive Handlers list on this page.

3. On the Monitor Handlers page, only the monitor handlers should appear in the Inactive Handlers list. Select all of these handlers and click Add to move them to the Active Handlers list.

Note: You can also manage handlers the same way in Interaction Designer's Manage Handlers notebook, accessible from the Utilities menu.

Primary and Monitor Handlers

Primary handlers are generally handlers that act directly on objects such as calls within the system. Only one primary handler can be activated for a given initiator. For example, you cannot activate two primary handlers that both start with the Incoming Call initiator. Only one handler can act on the incoming call. This prevents two handlers from performing disparate actions on a single object. If you attempt to activate two handlers that start with the same initiator, CIC generates an error message in the event log.

Monitor handlers do not actively manipulate or modify objects in the system. Typically they retrieve call attributes and write that information to a database for reporting purposes, although they are not limited to reporting. CustomCallDisconnectMonitor determines if a call was recorded, and if so, where to send a copy of that recording. Since monitor handlers are not acting on objects, more than one monitor handler can use the same initiator. For example, CallDisconnectMonitor and CustomCallDisconnectMonitor both use the Call Monitor Initiator configured to start when a call disconnects.