Cisco Cisco Agent Desktop 8.5 Guia De Configuração Rápida

Página de 102
Issues
November 2013
73
Issues
The VoIP Monitor service explicitly specifies what NIC adapter to use for capturing 
audio packets, but it does not specify which NIC should be used when sending out 
packets. These outgoing packets would be going to either the Cisco Recording & 
Playback Service or a supervisor’s desktop that is live-monitoring an agent’s call. 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 steams 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 tables so that 
normal traffic does not go through the sniffing NIC. Contact your network 
administrators for details.
An alternative solution is to give the sniffing NIC and 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.
In addition to these steps, the NIC that is used by the VoIP Monitor service must not 
be the first NIC in the network binding order. By default, the first NIC adapter in the 
binding order will be used by applications to send traffic out to the network. Contact 
your network administrator for details.
Uninstalling and installing NICs can cause the binding order of the systems network 
adapters to change. Whenever these kinds of changes are made, the binding order 
might need to be changed manually.