/on turns packet capture on, /off turns packet capture off. The default is off; you should turn it on.
-i <ifname>: Specifies interface name to capture on.
-w <filename>: Captures directly to file in pcap format, file can be opened with Wireshark
or with other tools.
-C <file_size>: Specifies the maximum size of a capture file. The units of file_size are millions of bytes (1,000,000 bytes, not 1,048,576 bytes).
-W <filecount>: Specifies the number of files created. The capture files are overwritten from the beginning, thus creating a rotating buffer. Capture files after the first capture file have the name specified with the -w flag, with a number after it, starting at 1 and continuing upward.
-tt : Prints an unformatted timestamp on each dump line.
-s : Snarfssnaplen bytes of data from each packet rather than the default of 68 . Setting snaplen to 0 means use the required length to catch whole packets.
/type 1 captures SIP packets only or /type 2 captures the entire data payload on the Dialer host machine.
Captures network packets on interface 3 with capture files: capture1 – capture20. The maximum number of capture files stored is 20. After 20 files are created, the oldest capture file is overwritten with the new data. Maximum file size is 20 MB.
Import Unified CCE Data Collector Set Template
In the Performance Monitor, use the template file, CCE.xml, to create a Data Collector Set to capture the standard set of performance counters for the Unified CCE components. On any machine where a Unified CCE component is installed, the template file is installed in the icm\serviceability\perfmondirectory. After you created a Data Collector set, you can schedule or manually start to capture Unified CCE performance counter.
Follow these steps to import the template file and create the Data Collector set:
Step 1. Start the 32-bit Windows Performance Monitor tool by using the shortcut called Performance Monitor. This shortcut is available in the Cisco Unified CCE Tools folder. Alternatively, you can also launch the 32-bit utility by running the command mmc /32 perfmon.msc.
Step 2. In the panel on the left, expand Data Collector Sets.
Step 3. Right click User Defined and select New > Data Collector Set. The Data Collector Set wizard opens.
Step 4. Provide a name for the Data Collector Set and select Create from a template. Click Next.
Step 5. Click Browse. Go to icm\serviceability\perfmon and select the file CCE.xml. Click Next.
Step 6. Specify the location where you want to collect the performance counter log. Click Next
Step 7. Select Save and Close and click Finish.
The Performance Monitor creates the Data Collector Set by importing the XML file. You can edit the Data Collector Set to modify the component monitoring. For example to change the sampling interval or add or remove counters. For more information, see "Creating Data Collector Sets" in the Performance Monitor online help.
The Dialer is a multithreaded process that communicates between threads using inter thread messaging. This indicates how many messages are currently queued up for the main dispatch thread. By default, the Dialer process restarts when this value exceeds 10,000 messages.
Average Queue Time
The Dialer is a multithreaded process that communicates between threads using messaging. There is one main dispatch thread that is involved in most processing. This shows what is the average time spent in queue.
For an agent campaign, the Dialer replaces calls to customers and transfers those customers to agents. This counter indicates how many agents are currently talking in the monitored campaign skill group.
Busy Port (Customer) Count
The port is the unit on the Dialer that places calls to reserve agents and to contact customers. This counter tracks how many ports are currently busy trying to contact customers. This includes ports that are actively dialing and those that have been allocated but are not yet dialing a customer.
Ports Actively Dialing Customer Count
The port is the unit on the Dialer that places calls to reserve agents and to contact customers. This counter tracks ports that are currently actively dialing customers.
Busy Port (Reservation) Count
The port is the unit on the Dialer that places calls to reserve agents and to contact customers. This counter tracks how many ports are currently busy reserving agents only for normal records.
Agent Reservation Port Count
The port is the unit on the Dialer that places calls to reserve agents and to contact customers. This counter tracks how many ports are currently being used for reserving agents for both normal and callback records.
Port Utilization Percent
The port is the unit on the Dialer that places calls to reserve agents and to contact customers. This counter tracks the percent of total dialer ports in use for all outbound calls.
Idle Port Count
The port is the unit on the Dialer that places calls to reserve agents and to contact customers. This counter tracks how many ports are currently idle.
PCB Records Cached
The Dialer caches the PCB records received from campaign manager. This counter tracks the total number of PCB records cached.
Idle PCB Records Cached
This counter tracks the number of the cached PCB records that are in the idle state, waiting to be dialed out from the dialer.
Idle Not-Ready PCB Records Cached
This counter tracks the number of cached PCB records in the idle state where Agent is in Not-Ready state. These records will be retried until the agent is ready or the PCB call time expires.
Call Attempt Count
The Dialer attempts to contact customers and transfer them to reserved agents or an available IVR. This counter tracks how many customer attempts were placed today. It does not include preview calls that were rejected or skipped.
Abandoned Call Count
When a customer is contacted and an agent is not available to take the call, the call can be dropped or sent to the IVR for prompting and queuing. When either of these conditions occurs, the all is counted as abandoned. In a transfer to IVR campaign, a call is dropped and counted as abandoned if the configured IVR port limit is exceeded.
Reservation Call Count
The Dialer places calls to agents to reserve them for use while attempting to contact available customers. This counter tracks how many reservation calls were placed today.
Answering Machine Call Count
A campaign can be enabled to differentiate between live voice and answering machines. This counter tracks how many answering machines were detected today.
Customer Answered Call Count
A campaign can be enabled to differentiate between live voice and answering machines. If answering machine detection (AMD) is enabled for a campaign this counter increments when live voice is detected. If AMD is disabled, then all connected calls that are not FAX are identified as live voice. Direct Preview calls are identified as voice or AMD by the agent. This counter is reset daily at midnight.
Customer Not Answered Call Count
The Dialer attempts to contact customers. This counter tracks how many attempts resulted in no answer condition. This counter is reset daily.
Error Call Count
The Dialer attempts to contact customers. This counter tracks how many attempts resulted in a network error condition which includes no ring-back, no dial tone, and call disconnected from the network before ring no answer time out was exceeded.
Number of attempted calls per second
This counter tracks how many calls per second the Dialer is placing rounded to the nearest integer. If the dialing rate is too high, it can result in network congestion on the voice network that can result in inefficient dialing.