Cisco Cisco Agent Desktop 8.5 Guida All'Installazione

The VoIP Monitor service does not specify which NIC should be used when 
sending out packets. This is not a problem when using a single NIC for both 
sniffing and normal traffic. With two NICs, however, normal traffic should be 
restricted so that it does not go through the NIC used for sniffing. Otherwise, the 
sniffed RTP streams of a currently-monitored call might not reach the supervisor 
because the SPAN destination port does not allow outgoing traffic.

To resolve this, use the route command to customize the static routing table so 
that normal traffic does not go through the sniffing NIC. Contact your network 
administrator for details.

An alternative solution is to give the sniffing NIC an IP address that no other host 
on the network uses, and a subnet mask of “255.255.255.0”. Leave the default 
gateway field blank for this NIC’s TCP/IP binding. 

This procedure applies only to computers running Windows 2000.

1. Install the second NIC in the computer.

2. Start the computer.

3. Make sure that neither adapter is using dynamic host configuration 

protocol (DHCP) to get its IP address.

4. Give the adapters valid IP addresses.

5. Determine which of the two adapters is to be used for sniffing. 

6. Connect the sniffing adapter with the switch SPAN port.

7. Connect the second adapter with a normal switch port that is not 

monitored by the SPAN port.

8. Use the route command to customize the local routing table so that normal 

traffic does not go through the sniffing adapter.

9. Verify that the sniffing adapter is not registered with DNS and WINS by 

using the PING <local host name> command. This ensures that the local 
name always resolves to the normal traffic card IP address.