[cisco-voip] IPCC silent monitoring
Linsemier, Matthew
MLinsemier at apcapital.com
Fri Sep 15 09:28:26 EDT 2006
Wes,
I thought with IPCC Express 4.0 there was no need for SPAN or Remote
SPAN ports anymore for monitoring? Has something changed?
-Matt
________________________________
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: Friday, September 15, 2006 9:20 AM
To: GPate at kenttech.com
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] IPCC silent monitoring
Gary,
Make sure you span the voice vlan of the agent phones to the designated
NIC of the monitoring server. take a packet capture at that interface
to make sure you are seeing all the vlan traffic. Then make sure your
server NIC correctly passes dot1q tagged packets up to the OS. You can
verify both in 1 step by attempting a packet capture with network
monitor or ethereal on the Monitor server.
A good starting point:
http://www.cisco.com/en/US/products/sw/custcosw/ps1001/products_tech_not
e09186a008010e6ba.shtml
/Wes
Gary L. Pate wrote:
I have a client using IPCC 4.0 enhanced version, and they are able to
use all the enhanced features except the monitoring function. As I
understand it, this version does not require you to span the ports, but
their ports are spanned anyway because they are using a third party
recording device to record all conversations. Anyway, barge in,
intercept, etc. work, and when they do the monitoring, the applications
acts like its working, but they do not hear anything coming out of the
PC speakers even though its been confirmed that the speakers do work. Is
there anything special that the workstation needs to monitor?
________________________________
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--------------------------------------------------------------------------------
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may be
protected by one or more legal privileges. It is intended solely
for the use of the addressee identified above. If you are not
the intended recipient, any use, disclosure, copying or
distribution of this communication is UNAUTHORIZED. Neither this
information block, the typed name of the sender, nor anything
else in this message is intended to constitute an electronic
signature unless a specific statement to the contrary is
included in this message. If you have received this communication in
error, please immediately contact me and delete this communication from
your computer. Thank you.
--------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060915/b3a50b84/attachment.html
More information about the cisco-voip
mailing list