AES Release 4.1 includes Call Control service enhancements for DMCC (CSTA Phase III) applications.

Do the "Monitor Start" and "Monitor Stop" services allow the DeviceID to be a VDN extension in a CM system ? And if a VDN can be monitored does the set of Event reports that result from such a monitor request include all the normal Events available in a TSAPI application, e.g. Call Offerred, Call Queued, Call Alerting, and Call Connected.

In other words does the DMCC Call Control services now include the functionality equivalent to the TSAPI function call cstaMonitorCallsviaDevice() ?

If DMCC Call Control services do not support VDN monitoring now, is there a plan to add this capability ?

Hi Peter,

Good question. Monitoring a VDN extension is not supported in 4.1. However, we plan to support this capability in 5.0 which we plan to Beta later this year.

Carla,
Can you clarify the current situation regarding monitoring splits (aka ACD and Hunt Group Extensions)?

Thanks.

John,
Sure. When a monitor is started for an ACD split extension, agent events (i.e. agent logged off and agent logged on) are sent for that monitor, call events are not sent on that monitor.