The information in this document is based on these software and
hardware versions:

CTIOS Silent Monitor

Microsoft Windows NT 4.0, Windows 2000, and Windows
XP

The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.

The default filename is CTI OSClientLog. The convention
<TraceFileName>.mmdd.hhmmss.log is used to
create log files. The files are created in the current directory of the
executing program, for example the directory into which you have installed the
AgentDesktop. You can provide a fully qualified path for the TraceFileName if
you want to store the files in a different location. For example, set the value
to "c:\temp\CTI OSClientLog" to place the log
files in the directory "c:\temp" with the naming
convention of CTI OSClientLog.mmdd.hhmmss.log.
Client trace files are simple ASCII text, and you can open them with a
conventional text editor such as Notepad.

The CTIOS supervisor desktop fails to establish a session with the
CTIOS agent desktop through UDP port 8500. From the CTIOS supervisor desktop
log, the CTIOS agent desktop responds to the request and accepts to engage in
the session, as shown in this log:

Use Packet Analyzer to trace the traffic between CTIOS supervisor
desktop and agent desktop. In this instance, there is no traffic between the
CTIOS supervisor and the agent desktop through UDP port 8500.

There is a known driver issue for Intel Network Drivers to support
silent monitoring. By default, Intel adapters strip the VLAN tag, and then pass
the tag up the stack. If you need to see the tag, use one of these driver
versions (or later):