Cisco Cisco Computer Telephony Integration OS 8.5 開発者ガイド
4-53
CTI OS Developer’s Guide for Cisco Unified Contact Center Enterprise
Release 8.5(3)
Chapter 4 Building Your Application
Enabling Silent Monitor in Your Application
•
AvgInternalCallsHeldTimeToHalf = InternalCallsHeldTimeToHalf/InternalCallsHeldToHalf
•
AvgCallsQTimeHalf = CallsQTimeHalf/CallsQHalf
•
AvgAgentOutCallsTalkTimeToday = AgentOutCallsTalkTimeToday/AgentOutCallsToday
•
AvgAgentOutCallsTimeToday = AgentOutCallsTimeToday/AgentOutCallsToday
•
AvgAgentOutCallsHeldTimeToday = AgentOutCallsHeldTimeToday/AgentOutCallsHeldToday
•
AvgHandledCallsTalkTimeToday = HandledCallsTalkTimeToday/HandledCallsToday
•
AvgHandledCallsAfterCallTimeToday = HandledCallsAfterCallTimeToday/HandledCallsToday
•
AvgHandledCallsTimeToday = HandledCallsTimeToday/HandledCallsToday
•
AvgIncomingCallsHeldTimeToday = IncomingCallsHeldTimeToday/IncomingCallsHeldToday
•
AvgInternalCallsRcvdTimeToday = InternalCallsRcvdTimeToday/InternalCallsRcvdToday
•
AvgInternalCallsHeldTimeToday = InternalCallsHeldTimeToday/InternalCallsHeldToday
•
AvgCallsQTimeToday = CallsQTimeToday/CallsQToday
Enabling Silent Monitor in Your Application
There are two (mutually exclusive) silent monitoring methods:
•
CTI OS based silent monitoring
•
Cisco Unified Communications Manager (Unified CM) based silent monitoring
Refer to the “Silent Monitoring” section of the CTI OS System Manager's Guide for Cisco Unified
ICM/Contact Center Enterprise & Hosted for additional information on each. For information concerning
how to enable silent monitor in your application, refer to
ICM/Contact Center Enterprise & Hosted for additional information on each. For information concerning
how to enable silent monitor in your application, refer to
, as
applicable.
Enabling CTI OS Based Silent Monitoring in Your Application
Note
CTI OS Silent Monitor functionality is only available in the C++ and COM CILs.
The silent monitor manager object is responsible for establishing and maintaining the state of a silent
monitor session.
monitor session.
The first thing a client application should do is to create a silent monitor object instance. The application
should then set this object instance as the current manager in the session object. The CIL provides the
interface to this functionality. A client application can work in one of two possible modes:
should then set this object instance as the current manager in the session object. The CIL provides the
interface to this functionality. A client application can work in one of two possible modes:
•
Monitoring mode. The client receives audio from a remote monitored target (device/agent).
•
Monitored mode. The client sends audio to a remote monitoring client.
Note
Silent Monitor does not work until you set the session mode using on of the following function calls:
Session.SetAgent() for an Agent mode application
Session.SetMessageFilters() for a Monitor mode application
Session.SetMessageFilters() for a Monitor mode application