Clicking on Event Configurations displays the list of events covered by the feature.
...
There are separate events defined for CIF1 and CIF2. Only items applicable to the current environment get deployed, so if only CIF1 (single-session app) flavor of Enreach Voice is in use then CIF2 doesn’t appear. it is possible to use both CIF2 and CIF2 in the same environment, in that case both CIF1 and CIF2 are present for the same event.
The system can listen to the following call events:
...
Is Built-in: Indicates if the event handler is a system one (deployed by Enreach’s deployment package) or is a custom one, (created manually by the customer or integrator partner).
Plugin: The plugin which is hooked up for this event. It can either be point to a system or a custom plugin.
Order: Plugins of a certain event are triggered in a row, one-by-one. This integer value specifies in which order the plugins have to be triggered.
To avoid conflicts and make room for new plugins to be deployed in a new release, built-in and custom plugins have reserved order spaces:First 50 of every 100 is reserved for custom plugins: 1-50, 101-150 … 1001-1050, etc.
Second 50 of every 100 is reserved for built-in plugins: 51-100, 151-200 … 1051-1100, etc.
Status: Indicates if the item is active or not. Inactive items are ignored by plugin engine and not triggered when the event is raised.
Certain built-in plugins (like Callback Attempt: set A-number to queue number plugin for Click-to-dial event) are by default deployed as inactive and must be enabled manually.
...