How do I configure my AntiVirus software to work with Cisco TelePresence ConferenceMe? |
Some AntiVirus software blocks call signalling from ConferenceMe. In this case, you will see the message: "Call ended due to network errors". ConferenceMe uses port 80 for signalling. To solve this problem, you can either add the ConferenceMe application as an exception to the virus filter or you can add the IP address of the MCU as an exception to the filter. The table below details solutions to issues caused by various AntiVirus software:
|
TREND Micro OfficeScan Work around for Cisco ConferenceME
The place I got this running at was running Worry Free Business version 6 SP3. This should also be compatible with versions made after 6.
- Go to the server on which Trend is installed.
- Right Click Notepad and run as Administrator
- Open C:\Program Files\Trend Micro\Security Server\PCCSRV\ofcscan.ini
- Search for: [INI_SERVICE_MODEL_SECTION]
- On the line above: [INI_SERVICE_MODEL_SECTION] type this information in:
You will now need to restart your Trend Master Service on the same server. Right Click “Computer” and Click “Manage”
Find “Configuration” – “Services” – and Then right click “Trend Micro Security Server Master Service” and click “Restart”.
Now log into your your Trend web app and go to “Preferences” – “System” – Click “Verify now” under Connections Verification.
This will push the new settings out to the clients. It seems like it takes a while for things to propagate to the clients. I found rebooting the clients 2x’s was the easiest way for forcing the clients to get the settings ASAP. If you want to double check that the settings have actually been applied to the system you can verify it in the Registry.
HKLM – Software – TrendMicro – NSC – TmProxy
You will notice if the settings were successfully pushed through if there are keys created that match the items that were entered in the ini file.
There should be some subkeys created as well.
Eternal-student says
Thanks for the post. My heart sank when I saw the Tandberg site that said there was no known work around.
One thing though, isn’t there a more straight forward way to whitelist a program through the web interface on the administration server?