Running XP service Pack3 on the supervisor CTIOS 7.2.9X desktop. Agent phone has span to PC enabled. We click voice monitoring for an agent in talking state - but do not hear anything. Any specific things for checking the nic card of the lap top? The laptop is connected to the Phone. Thanks
connectivity on the default data VLAN, while being able to capture voice packets on a different VLAN (voice VLAN) simultaneously. Some NICs are able to accomplish this task while others MAY not. In
order to help with deployments, Cisco has tested the most common NICs with driver versions as listed in the table below. Be advised that there is a possibility for a specific NIC card to behave differently
with different driver versions or operating systems. If a combination of NIC / operating system / driver version is not specifically listed below, it is recommended to test them using instructions in the CTI OS
System Manager's Guide (see Appendix A, "Testing an Ethernet Card for Silent Monitor") for NIC testing information before deploying them with Silent Monitor."
You can find information about testing NIC cards in the CTIOS System Manager's Guide - Appendix A.
guys, i have installed the CTIOS server with silent monitoring. They are using two types of NIC one is Broad Com Extreme which i found in guide the cisco doesn't support for Silent Monitoring and the 2nd one is Broad Com Net Link which cisco supprts with some registry chnage which i have done also on agent machine. now when i press the silent monitoring button i got error code = 0x1000000C Silent Monitoring Session failed and causes may be Agent mahicne is not connected with hardphone or the NIC is not compatible while Agent PC is connected in a daisy chain pattern and NIC is compatible after having the required registry change.
So, I'm assuming you're using CTIOS based monitoring, correct? Also, your PC connected off the back of the phone? To be honest with me silent monitoring has always worked for me, but it just takes a lot of trail and error. Do the silent monitoring test before and after making the registry changes to ensure that you're actually seeing the correct packets.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...