Технические ссылки для Cisco Cisco Agent Desktop 8.5
VoIP Monitor Service Deployment Strategies
20
of
34
November 26, 2003
6.0 VoIP Monitor Service Deployment Strategies
This section describes, in general terms, the different sniffing configurations
that can be used in successful VoIP Monitor service installations. The primary
goal of these scenarios is to limit the amount of network traffic the VoIP Monitor
service must sniff in order to serve the needs of the customer.
that can be used in successful VoIP Monitor service installations. The primary
goal of these scenarios is to limit the amount of network traffic the VoIP Monitor
service must sniff in order to serve the needs of the customer.
Sniffing excessive network traffic incurs loads on the VoIP Monitor service
machine, the switch(es), and the network. Using the correct sniffing strategies
that match the customer’s needs allows the system to work most efficiently.
Using an invalid sniffing scenario negatively affects the VoIP Monitor service
and the system as well.
machine, the switch(es), and the network. Using the correct sniffing strategies
that match the customer’s needs allows the system to work most efficiently.
Using an invalid sniffing scenario negatively affects the VoIP Monitor service
and the system as well.
VoIP sniffing can be done at several locations in the system:
•
Voice VLANs
•
IP Phone/CAD switch ports
•
Voice gateway and CallManager ports
In this context, sniffing means to set up a SPAN or RSPAN to monitor one or
more ports and/or VLANs. The sources used by the SPAN each have issues
that affect VoIP monitoring, and need to be understood.
more ports and/or VLANs. The sources used by the SPAN each have issues
that affect VoIP monitoring, and need to be understood.
6.1 Voice VLANs
Sniffing voice VLANs is the preferred sniffing method for two primary reasons:
•
Voice and data network traffic are separated
•
SPAN configuration and maintenance are easier
It is strongly recommended that voice and data network traffic be separated by
VLANs, and that the VoIP Monitor service sniffs only the voice VLAN. The less
network traffic the VoIP Monitor service needs to process, the more capacity it
has.
VLANs, and that the VoIP Monitor service sniffs only the voice VLAN. The less
network traffic the VoIP Monitor service needs to process, the more capacity it
has.
6.2 IP Phone Switch Ports
If VLANs or VSPAN are not supported on the switch, SPAN must use individual
ports as source ports rather than a VLAN. This is less desirable than VLAN
sniffing because the VoIP Monitor service is exposed to both voice and data
traffic. This additional traffic reduces the capacity of the service.
ports as source ports rather than a VLAN. This is less desirable than VLAN
sniffing because the VoIP Monitor service is exposed to both voice and data
traffic. This additional traffic reduces the capacity of the service.
6.3 Voice Gateway and CallManager Ports
If agent-to-agent call monitoring/recording is not required, it is possible to set
up SPAN to monitor only the voice gateway port(s) and the CallManager port.
up SPAN to monitor only the voice gateway port(s) and the CallManager port.