Cisco Cisco Agent Desktop 8.5 Guia Da Instalação
August 8, 2012
105
A
Using Multiple NICs with the VoIP
Monitor Service
Overview
The VoIP Monitor Service sniffs RTP traffic from the network and sends it to registered
clients. This requires support from the switch to which the service is connected.
clients. This requires support from the switch to which the service is connected.
The VoIP Monitor Service must be connected to the destination port of a configured
SPAN/RSPAN. Any traffic that crosses the SPAN/RSPAN source ports is copied to the
SPAN/RSPAN destination port and consequently is seen by the VoIP Monitor Service.
SPAN/RSPAN. Any traffic that crosses the SPAN/RSPAN source ports is copied to the
SPAN/RSPAN destination port and consequently is seen by the VoIP Monitor Service.
Not all Catalyst switches allow the VoIP Monitor Service to use the SPAN port for both
receiving and sending traffic. There are switches that do not allow normal network
traffic on a SPAN destination port. A solution to this problem is to use two NICs in the
machine running the VoIP Monitor Service:
receiving and sending traffic. There are switches that do not allow normal network
traffic on a SPAN destination port. A solution to this problem is to use two NICs in the
machine running the VoIP Monitor Service:
■
One NIC for sniffing the RTP streams, connected to the SPAN port
■
One NIC for sending/receiving normal traffic, such as requests from clients
and sniffed RTP streams, connected to a normal switch port not monitored by
the above-mentioned SPAN port.
and sniffed RTP streams, connected to a normal switch port not monitored by
the above-mentioned SPAN port.
Limitations
Since Cisco Unified Communications Manager (Unified CM) does not support two
NICs, using multiple NICs works only in configurations where Unified CM is not
co-resident with the VoIP Monitor Service.
NICs, using multiple NICs works only in configurations where Unified CM is not
co-resident with the VoIP Monitor Service.
SplkPCap 3.0, the packet sniffing library, works only with NICs that are bound to
TCP/IP. Make sure the sniffing card is bound to TCP/IP.
TCP/IP. Make sure the sniffing card is bound to TCP/IP.
Issues
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
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