<< Click to Display Table of Contents >> Navigation: Settings > Telephony > TAPI settings |
Activate TAPI |
Activates call monitoring via TAPI. If this option is deactivated, SmartCallMonitor won't monitor any calls via TAPI. |
Call Prefixes
Remove prefix from incoming calls number |
Depending on the system configuration it may be necessary to remove a prefix (e.g. a leading zero) from the caller ID for incoming calls. |
Add prefix to outgoing calls from GUI |
Depending on the system configuration it may be necessary to add a prefix (e.g. a leading zero) to the caller ID for outgoing calls. |
Remove prefix from outgoing calls number |
Depending on the system configuration it may be necessary to remove a prefix (e.g. a leading zero) from the caller ID for outgoing calls. |
TAPI Initialization
Also use line names for identification of lines |
Some TAPI drivers reallocate the IDs of the lines after being restarted. Therefore SmartCallMonitor may have duplicate lines afterwards. This setting can prevent this problem. |
Delay TAPI initialization on startup by X s |
On computer boot the TAPI service may not be started yet, and problems may occur when SmartCallMonitor then tries to initialize TAPI already. This setting can prevent these problems. |
Delay TAPI initialization on startup |
Amount of seconds to delay TAPI initialization on program start. Useful to wait for possibly not yet loaded TAPI drivers on booting, because else the initialization fails. |
Reinitialize TAPI after x minutes of inactivity |
Due to problems with some TAPI service providers it may be necessary to reinitialize the TAPI service periodically. |
Wait when initializing x ms after each line |
Initializing TAPI lines in quick succession might cause problems with some TAPI service providers. |
Maximum Retry Count |
If a line can't be initialized, the application restarts the TAPI initialization as often as here given or as soon as all lines are initialized properly. |
Wait between Retries X ms |
Between reinitializing TAPI, the application wait the here given time. |
TAPI Call Handling
Ensure "0" prefix for every non-internal number |
With some telephone systems problems with the prefix of external numbers can occur. These send the phone number sometimes with and sometimes without prefix. This setting ensures, that a number always has a "0" prefix, if it is not an internal number. When using this setting please make sure that the setting "Maximum length of internal numbers" in the TAPI settings is configured correctly. |
Ensure custom prefix for non-internal numbers |
With some telephone systems problems with the prefix of external numbers can occur. This setting will force the entered prefix for external numbers. When using this setting please make sure that the setting "Maximum length of internal numbers" in the TAPI settings is configured correctly. |
Resolve phone number on initialization |
Sometimes it is necessary to resolve a phone number when initializing a TAPI call, because some TAPI drivers append special characters to the number. |
Use TAPI ID property for call identification |
If activated, the ID property of a TAPI call is used for its identification. |
Only consider TAPI calls with original handle |
If activated, only TAPI events are considered that use the object handle of the first TAPI event for a call. |
TAPI Logging
SmartCallMonitor logs the received TAPI messages to the service log file, which can be found in "%ProgramData%\Jam Software\SmartCallMonitor\ServiceLog.txt". This information can be very useful for debugging problems with specific TAPI systems.
Numbers |
Logs the phone numbers of the caller and the called. |
Names |
Logs the names of the caller and the called, if provided by the TAPI interface. |
Call state |
Logs the call states of TAPI calls. |
Call capabilities |
Logs the capabilities of the calls, i.e. which operations are possible for a given call. |
Redirection info |
Logs the redirection info of calls containing names and phone numbers of redirecting and redirection parties. |
Other |
Logs the call origin (inbound or outbound), the call reason and the related call id. |
Enable detailed TAPI initialization logging |
Enables logging of detailed TAPI initialization entries to a separate log file. The log file is located in "%ProgramData%\Jam Software\SmartCallMonitor\TapiLog.txt". |
Call types to process
Incoming |
Only incoming calls will be monitored by the SmartCallMonitor system |
Outgoing |
Only outgoing calls will be monitored by the SmartCallMonitor system |
Both |
Incoming and outgoing calls will be monitored by the SmartCallMonitor system |
Line for outgoing calls
Line for outgoing calls |
Defines on which line outgoing calls will be made. A line can also be selected dynamically in the switchboard view. |
Config |
Opens the settings for the selected line. |
Lines
Enabled |
Determines whether a line is used for monitoring. |
ID |
Shows the TAPI ID of a line. |
Name |
Shows the TAPI name of a line. |
Display Name |
Define a custom name for a line. |