Monitor Handlers page

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.

Caution: CIC cannot differentiate between primary and monitor handlers in the Manage Handlers Notebook. This is why the lists of inactive handlers are identical on the Primary Handlers and Monitor Handlers page. Make sure you don't activate a primary handler on the Monitor Handlers page, or vice versa.

Note: You must have manage handler rights (configured in Interaction Administrator) to activate and deactivate handlers.

Inactive Handlers

Handlers in this list are registered on the server but not active.

To activate a monitor handler:

• Double-click on the inactive monitor handler's name.

or

• Select the inactive monitor handler and click the Add button.

Active Handlers

Handlers in this list are registered with the Interaction Processor and currently active (monitoring events in the Interaction Processor).

To deactivate a monitor handler:

• Double-click the active monitor handler name.

or

• Select the active monitor handler and click Remove.