Cisco Cisco Agent Desktop 8.5 Referências técnicas
Cisco CAD VoIP Monitoring and Recording Guide
66
November 26, 2013
Test 5—Detect Promiscuous Traffic
This test uses the data captured in Test 3. It verifies if the NIC supports promiscuous
mode captures, and if valid RTP packets can be captured.
mode captures, and if valid RTP packets can be captured.
Successful Test Report Example
The following is an example of a successfully-run test. The system information is
omitted. The test results state whether the tests are passed and if the NICs will
support the packet sniffing solution used by CAD. If one or more tests fail, it might
indicate that a particular NIC is not supported. However, it might also indicate that the
configuration used in the test is not correct.
omitted. The test results state whether the tests are passed and if the NICs will
support the packet sniffing solution used by CAD. If one or more tests fail, it might
indicate that a particular NIC is not supported. However, it might also indicate that the
configuration used in the test is not correct.
---------------------------
Test 1: Check Driver Status
---------------------------
Driver is properly installed.
SPCD Driver service is running.
Test 1: SUCCESS
Test 1: Check Driver Status
---------------------------
Driver is properly installed.
SPCD Driver service is running.
Test 1: SUCCESS
----------------------------------------------
Test 2: Get the List of Valid Network Adapters
----------------------------------------------
Found 2 valid network interfaces:
Adapter 1:
Name: \Device\Splkpc_{1AF9AAEF-7AD0-4795-98EB-11AA0C59A106}
IP: 10.10.49.117
Adapter 2:
Name: \Device\Splkpc_{06FF0278-AA0F-44C0-933F-220AD13FDDC2}
Test 2: Get the List of Valid Network Adapters
----------------------------------------------
Found 2 valid network interfaces:
Adapter 1:
Name: \Device\Splkpc_{1AF9AAEF-7AD0-4795-98EB-11AA0C59A106}
IP: 10.10.49.117
Adapter 2:
Name: \Device\Splkpc_{06FF0278-AA0F-44C0-933F-220AD13FDDC2}
Test
Corrective Action if Test Fails
Check for
promiscuous
traffic
promiscuous
traffic
• Verify that a daisy-chained phone is configured to send
voice traffic out its second network port
• Ensure that the capture time is long enough. Use the -t
parameter to increase the time, if necessary.
• Ensure that there is promiscuous traffic available for the
NIC to capture. Some reasons for no traffic are: the phone
is not daisy-chained and there is no active call, or if using
SPAN and there is no call on any of the SPAN source ports.
is not daisy-chained and there is no active call, or if using
SPAN and there is no call on any of the SPAN source ports.
• Look for documented workarounds for this NIC to get it to
work correctly in promiscuous mode
• Update driver to the latest version and retest
Check for RTP
traffic
traffic
• Ensure that there is a phone call or simulated RTP traffic
exposed to the NIC being tested. Make a call to the IP
phone.
phone.
• Ensure that the phone uses the correct codec (G.711,
G.722, or G.729). Change the configuration in Unified CM
so that a supported codec is used.
so that a supported codec is used.