DMCCLogger now supports real-time speech to text transcription. Currently, we have integrated with AWS and Azure. The integration is implemented directly using the RTP packets captured from the DMCC, therefore transcription process is close to real-time. The transcription text is sent to application by WebSocket or API interface in the format of JSON event.
We will support more vendors in the future, Google is planned in next minor release. If you want a trial, please contact us by email.
AutoBridge now supports bridging of 911 emergency calls with security officers immediately when user places a 911 call. The security officer can join the call or dispatch a team to assist the user if needed. AutoBridge uses DMCC to monitor a virtual station configured with Crisis Alert button. When user dials 911, the extension which dial the call is reported via the Crisis Alert button and the bridging process can be triggered automatically by the AutoBridge program. The AutoBridge can also use OSSI interface to get the caller who makes emergency call and trigger the process automatically.
The parameters that are specific for Crisis Alert are explained in more details as follows
ab_crisisalertdevice: The virtual station extension number that configured with crisis alert button
ab_crisisalertbridgedestination: The bridge destination after crisis alert is received. Normally, it is VDN or an extension of a security officer.
ab_crisisalertcancelbutton: The button number for the crisis alert. It is for cancellation of the crisis alert
ab_crisisalertcancelbuttonautopress: true or false to auto press the crisis alert button
ab_crisisalertringpattern: The ring pattern for crisis alert which is for determination if the virtual station is in crisis alert.
ab_ossilink: The OSSI link, you can setup by the tcpgate console “setup ossi”
ab_ossitrace: true or false to turn on the tracing.
ab_cmtenant: The CM tenant number to compare for the Auto-Bridging process.
upDialer 1.2.0 just released, this version has the following updates:
1. Add “setup”, “setup database”, “setup API” and “setup splunk” commands for program configuration.
2. Add “add dialeruser”, “delete dialeruser” and “disp dialeruser” commands. Before that, the users are defined in the tcpgate admin user database table.
3. A role is associated with each dialeruser. Four standard user roles are defined, they are agent, supervisor, manager and admin. Some functions are limited to supervisor privilege or above only.
4. Add cancelcallitems API to cancel call items of a job.
5. Add listcallcitems API to list call items of a job. The listing supports “active” or “all” call item listing.
6. Add WebSocket “call back start” and “call back cancel” events notification during dialer callback.
7. Support add call items with specific schedule calling time. The dialling will be started after the schedule time (UNIX time stamp).
clintSVR 2.2.1 just released, this version has the following updates.
1. Supports integration with bcmsSVR to provide number of ACD calls (whole day) of each agent for the API splitskillsla.
2. Change the clint “Exit” command to “logout” for faster logout of clint command.
3. Change the historical report time range from 00:00-23:30 to 00:00-23:59.
4. Add telnet “setup”, “setup database”, “setup api” and “setup aplunk” commands for clintSVR configuration.
5. Add custom historical report “uphisallsplitskillagentsummary” which provides a whole day agent summary data of all split skills. The number of ACD calls (whole day) of each agent for the API splitskillsla is supported.
6. Add custom real-time report “uprtallspskreport” which provides all real-time split skill report of a ACD. This version only provides the data via REST interface.
7. Add custom real-time report “uprtallagentstatus” which provides all real-time agent status of a ACD. This version only provides the data via REST interface.
8. Add a parameter “cs_hisreport_refreshstartpoint” for custom historical report “uphisallsplitskillagentsummary”. Before that start point, the cache result timestamp is updated to keep the cache alive.
9. Replace the parameter “cs_splitskillsla_freezingpoint” with “cs_hisreport_refreshstoppoint”. During the stop point, the cache result timestamp is updated to keep the cache alive.
Avaya CS1K CDR is now supported by AvayaCDR 1.7.0!
AvayaCDR can capture CS1K CDR from COM port or network network TCP streaming. This version has the following updates:
1. Supports capture CDR records from serial COM port. Supports generic and cs1klf (Avaya CS1000 with NEW format with line feed records) formats.
2. Supports TCP streaming of CDR from Avaya CS1000 with NEW format with line feed records, the paramcdr template called cs1klf is newly introduced.
3. Add new command rotate to rotate the remote database error log file.
CallAnalytics 2.2.0 just released, this version has the following updates.
1. Add “setup”, “setup api”, “setup database” and “setup splunk” commands for program configuration.
2. Fix the “disp tlink” and “disp activetserver” commanads.
3. Fix the Linux 64 bit version “setuserdata” API bug due to basic type size difference in Windows and Linux.
4. Able to set the telnet port by installation parameter -listenport.
AutoBridge 1.2.0 just released, this version has the following updates:
1. Add a new parameter to control the setup of outbound call bridging when the destination is in alert state. The bridging may fail when the trunk is not supported the conferencing of the called party during alert state. The parameter is called “ab_bridgingstartedbydelivered”.
2. Poll agent phone status regularly and release it to the available pool when no agent is engaging the phone.
3. Add tcpgate console commands “setup” and “setup api” for program configuration.
4. Add inbridge for inbound call bridging based on caller number.
5. Add outbridge fro outbound call bridging based on called number.
6. Add “disp tlink” and “disp activetlink” commands to check TSAPI tlink information.
AvayaECHI 1.2.2 just released, this version has the following updates:
1. Supports multiple instances on the same host machine.
2. Add “setup”, “setup database” and “setup splunk” commands for program configuration.
3. Add -telnetport as installation parameter to override the telnet port for Windows.
4. Add -telnetport as program argument to override the telnet port for Linux.
bcmsSVR 2.3.0 just released, this version has the following updates.
1. Fixed the totalPercentWithinServiceLevelDay value as -1(undefined) when the service level is zero but with abandoned calls.
2. Support multiple instances of bcmsSVR on the same machine.
3. Add AUX0-AUX9 for bcmsmonitorsplitagentstats API
4. Merge the APIs bcmsmonitorsplitsla and bcmsmonitorsplitagentstats, the final one is bcmsmonitorsplitsla. No modification for API bcmsmonitorsplitagentstats in the futurer.
5. Add bcmslistsummaryagentday fields for each agent in the API bcmsmonitorsplitsla.
6. Modify bcmsmonitorsplitstatus to handle CTI integration similar to API bcmsmonitorsplitsla.
7. Add “setup”, “setup database”, “setup api” and “setup splunk” commands for program configuration.
UPINGET 