UPINGET

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.