Call events are an advanced feature provided by the TAPI Telephone System Integration plug-in for ContactsLaw. They allow users to set up actions which are automatically triggered in response to activity on the telephone line.
You can configure call events via the Options dialog for the plug-in, accessible from application settings, or on first use. Call events are always configured on an individual user basis, as they are tied to a specific telephone extension.
A call event has the following properties:
- Event - The type of event that triggers the rule. Choose from answered, ended, rejected, on hold and off hold.
- Direction - Whether the call is incoming, outgoing or whether the rule is triggered for all calls.
- Number filter - Applies the rule to a specific telephone number. Leave blank to trigger for all calls. You can also use PERL-style regular expressions (delimited by forwardslash characters) to match a range of numbers. Note: The format of the phone number is determined by the telephone system and may differ to what is shown in ContactsLaw.
- Action - The action to perform when the rule is triggered.
The following types of actions are available:
- Run program* - Runs an external program on the local computer. You can pass command-line arguments to facilitate automation.
- Open URL* - Opens a URL (web address or other resource) in the user's default browser.
- Answer automatically - Automatically answers the call as soon as it is detected. Use with caution.
- Send to voicemail - Sends the call to voicemail immediately. This is effectively the same as the DND function.
* You can include the following special symbols in the URL/arguments:
- %n - Telephone number
- %d - Direction (incoming/outgoing)
- %e - Event (answered/ended/etc)
Once configured call events will become active immediately and remain active as long as ContactsLaw is running. They are triggered after ContactsLaw receives the notification about each event.
See also
Telephone integration