Article 70031: How TASKE Handles Unmonitored Devices for the Communication Manager with Application Enablement Services (AES)

Print

Summary

This article outlines the impact of unmonitored devices to TASKE applications.

Best Practices

• Monitor all vector directory numbers as they do not require a TSAPI license.
• All inbound calls should flow through a monitored vector directory number.
• Monitor all front end auto-attendant ports and voice mail ports.
• To monitor an ACD hunt group, monitor the group itself and monitor all extensions that may answer for that group.
• To monitor a non-ACD hunt group, monitor all extensions that answer for that group. The group ID itself cannot be monitored.
• Monitor all extensions that you wish to report outbound call information on.
• If you want to track calls that are answered by voice mail you must monitor the device that sends the call to voice mail.

Reporting from Unmonitored Devices

In certain situations TASKE can still report on unmonitored devices, refer to the following for more details:

• If an inbound call goes to a monitored front end, then answered by an unmonitored extension, TAKSE will report on this call.
• If an inbound call goes to a monitored front end, then abandons on an unmonitored extension, Visualizer will report on this call.
• If an unmonitored device calls a monitored device, TASKE will report on this call.
• If an unmonitored device calls another unmonitored device TASKE will not receive any events for this call.
• If an unmonitored device makes an outbound call TASKE will not receive any events for this call.