Cisco Cisco Agent Desktop 8.5 Referências técnicas
Cisco CAD VoIP Monitoring and Recording Guide
42
November 26, 2013
In the configuration shown in
, the same SPAN configuration would work for
1, 4, or 48 phones connected to the switch.
When you look at this example, you might note that, by capturing both ingress and
egress packets on both the voice gateway and the Unified CM port, duplicate streams
will be captured. The monitoring software, however, is only looking for packets whose
MAC address or IP address and port are shown as the source or destination of the
packet. If the Unified CM is mixing the streams and sending them out, the source
MAC/IP/port does not match the agent's device, so they are ignored by the software.
The result is that we process the streams between the agent phone and the
Unified CM during the conference.
egress packets on both the voice gateway and the Unified CM port, duplicate streams
will be captured. The monitoring software, however, is only looking for packets whose
MAC address or IP address and port are shown as the source or destination of the
packet. If the Unified CM is mixing the streams and sending them out, the source
MAC/IP/port does not match the agent's device, so they are ignored by the software.
The result is that we process the streams between the agent phone and the
Unified CM during the conference.
Trunk Port Monitoring
Using VLAN filters for SPAN source ports that are trunk ports can reduce traffic to the
VoIP server.
VoIP server.
In some installations, it might be necessary to include a trunk port as a source port for
a SPAN configuration. A trunk port is a port configured to connect two switch devices
directly. Trunk ports are different from normal device ports in that they carry all
VLANs. A trunk port cannot be a member of a VLAN, which is a method of restricting
network traffic on a port. Because of this, if a SPAN configuration includes a trunk port
as one of the source ports, all traffic from all VLANs that traverse the port are copied
to the SPAN destination port. This might not be desired if that traffic includes
non-audio traffic that is of no interest to the VoIP service. It might also reduce the
capacity of the VoIP service due to the amount of unnecessary traffic being processed
by the service.
a SPAN configuration. A trunk port is a port configured to connect two switch devices
directly. Trunk ports are different from normal device ports in that they carry all
VLANs. A trunk port cannot be a member of a VLAN, which is a method of restricting
network traffic on a port. Because of this, if a SPAN configuration includes a trunk port
as one of the source ports, all traffic from all VLANs that traverse the port are copied
to the SPAN destination port. This might not be desired if that traffic includes
non-audio traffic that is of no interest to the VoIP service. It might also reduce the
capacity of the VoIP service due to the amount of unnecessary traffic being processed
by the service.
When a trunk port is used as a SPAN configuration source port, some switches allow
VLAN filtering on the port. This means that the trunk port is indicated as a SPAN
source and only network traffic over the VLAN IDs indicated in the filter are copied and
sent to the SPAN configuration destination port. The restriction to this is that you must
use ports for SPAN sources when a VLAN filter is used. You cannot use any VLAN IDs
as sources of the SPAN. Conversely, if you use a VLAN to indicate the source of a SPAN
configuration, you cannot use VLAN filtering. The switches that support VLAN filtering
are shown in
VLAN filtering on the port. This means that the trunk port is indicated as a SPAN
source and only network traffic over the VLAN IDs indicated in the filter are copied and
sent to the SPAN configuration destination port. The restriction to this is that you must
use ports for SPAN sources when a VLAN filter is used. You cannot use any VLAN IDs
as sources of the SPAN. Conversely, if you use a VLAN to indicate the source of a SPAN
configuration, you cannot use VLAN filtering. The switches that support VLAN filtering
are shown in
.
MAC Address Changes Due to Layer 2 Routing
Devices
Devices
Issue: Monitoring and recording do not work when Layer 2 routing devices are
between the packet capture software and the IP phone.
between the packet capture software and the IP phone.
This issue affects audio capture methods where MAC address filtering is used and
there exists a Layer 2 routing device between the IP phone and the software that is
capturing audio packets
there exists a Layer 2 routing device between the IP phone and the software that is
capturing audio packets