UPINGET

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

1. Filter connected call and failed event is delivered after far end customer hangup the call. A parameter ivr_filterconnectedfailedevent is introduced.
2. Parameters ivr_filterdmccringerevent and ivr_filterdmcclampmodeevent are introduced for filtering of DMCC ringer and lampmode events.
3. Supports listreasoncode and listspeeddial API calls. Reason codes and Speed dial numbers can be defined by the CtiSVR and populates to the softphone applicaions such as calltoui.exe.
4. Add makeoutbouondcall API. The API will pick one phantom device to make outbound call, when the call is connected, it then makes a consulte call to an extension. The call is transferred to that extension once the extension is connected.
5. Register license to license.upignet.com.

1. Compile using the latest libary.
2. Package with the latest library.
3. Update the installation procedure, please reference the blog.

1. Add calltrace Splunk log for VDN calls. A new parameter ca_writecalltrace is introduced for this.
2. Update the ucid and origucid fields in the delivered, established, transfer and conference events.
3. Fine tune the object deletion sequence in program exit.
4. Supports PostgreSQL database.
5. Add lasthandledagent() API which search last handled agent in real-time records in memory and historical records from database. Parameters ca_dbreaderpoolsize and ca_maxlastagentquerytimerange are added for this API.
6. Apply locking for database writing and checking to prevent database disconnection when the two are executed in parallel. Add a parameter ca_dbtest to control database testing or not.
7. Add id_endtime to table tCallInfo, tCallInfoExt, tCallAban and tShortDuration tables.
8. Add callaban() api searching from the database.
9. Add parameter ca_checkstreaminterval to adjust the TSAPI stream checker interval.

AutoBridge 1.3.1 just released, this version has the following updates:

1. When the calling device is registered in the crisis alert map and a call with new call id is informed, the old registration is removed and activate the bridging again.
2. A scheduler procedure is added to check the crisis alert map and cleanup the mapping after the call is finished.
3. Crisis alert cancel event (by crisis-alert button auto pressing) and list emergency notification will be returned immediately.
4. If a new call’s state is in initiated, alerting and connected state, bridging can be started. Before that, only connected call will trigger the bridging. This maybe related to timing issue because the call can be notified before the call is connected.
5. OSSI interface can be integrated and the list emergency API can be used to trigger the bridging for specific tenant stations. New parameters ab_ossi and ab_cmtenant are introduced.
6. A new parameter called ab_crisisalertcancelbutton and ab_crisisalertcancelbuttonautopresss are introduced to press the crisis-alert button once bridging is started. This action is to cancel the crisis-alert.
7. No action to agent extension when the agent extension is not in bridging mode after receiving CONNECTION_CLEARED event.

AutoBridge 1.3.0 just released, this version has the following updates:

1. Integration with ctiSVR for DMCC support. A parameter called ab_ctisvr is introduced.
2. Supports auto bridge call for Crisis Alert extension. Parameters ab_crisisalertdevice, ab_crisisalertbridgedestination and ab_crisisalertbridgebackup are introduced.
3. Crisis alert events are sent to Splunk for centralized logging.
4. Crisis alert bridging is supported only when phantom device is available.
5. Fine tune the object deletion sequence for program exit.
6. Add database logging for crisis alert bridging.
7. Add email notification for Crisis Alert calls. The parameter ab_crisisalertemailnotify is added.

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

1. Add “setup” and “setup api” commands for program configuration.
2. Add API aya (Are you alive) to check the server status.
3. Compile with lastest version of CSchedulerEx for better handling of start stop internal scheduler.
4. Fine tune the object deletion sequence for program exit.
5. The API listextension add a parameter details=full for display more parameters.
6. Encode the password to XML format before sending to DMCC login.

The AvayaMonitor has enhanced to support integration with Avaya CM using the OSSI interface. Currently, the following CM objects can be monitored by AvayaMonitor. Also, the dashboard can be easily created using Nagios Monitoring tool. If you want to have a trial, please contact us.

• CM AE Svcs CTI Link
• CM Processor Channels

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).