UPINGET

We received a request recently to develop a CTI call control program to clear an agent’s call if the call is not being recorded. Since there are many recording methods, it is hard to determine if the call is being recorded without integration with the voice logger system. The only way that we can check if an agent is being recorded is to assume the recording method is using DMCC SingleStepConference method because a dummy device is used for the recording.

A Compliance Manager is developed in this way, it monitors the agent extensions and checks if a dummy device is in the call. The program will cut the call if a dummy device is not in the agent’s call. More call control scenarios can be developed if you let us know the detailed requirements. If you are interested, please contact us.

ctiSVR 1.4.0 just released, this version has the following updates:

1. Filter SILENT/ACTIVE monitoring call events. For example, DMCC recording.
2. Add parameter tg_telnetbindip to bind the telnet port to a specific IP address. For example, 127.0.0.1
3. Supports multiline commands by the tcpgate console.
4. Add tcpgate command execsql and execsqlfile commands for the configuration database.
5. Sends ASCII data using the AES built-in UUI data field if the length is within the limit.
6. Add parameter ivr_primarytlink to set primary tlink and auto fallback the primary tlink when it is resumed.
7. Supports Service Observe APIs introduced in private data version 17.
8. Add parameter ivr_filterv7failedevent to filter ASAI v7 failed event introduced by ASAI link 7 or above.