Step 15. Configure Access To Client Applications - Nortel Contact Center Multimedia Installation And Maintenance Manual

October 2007
Step 15. Configure access to client
applications
The Contact Center Agent Desktop and Outbound Campaign Management Tool
applications are based on Microsoft .NET technology. The .NET deployment
model is based on clients pulling the latest version of an application from a Web
server. This .NET deployment provides the benefit of deploying a thick client
using thin-client technology and the ability to automatically update the
applications based on updates and patches on the server.
Accessing the Web server introduces the potential for a client to download
malicious code. The following information provides the procedures to set the
security and to deploy the Contact Center Agent Desktop and Outbound
Campaign Management Tool with minimal risk.
The Nortel Multimedia security policy file, CCMM_Security_Policy.msi
(Microsoft Installer), contains a policy level for the client to download and run
assemblies with a particular strong name. A strong name consists of the
assembly identity (name, version number, private key) and a public key. The
Outbound Campaign Management Tool and the Contact Center Agent Desktop
assemblies are digitally signed with a strong name based on the private key.
After it is installed, the CCMM_Security_Policy.msi file instructs the clients to
trust the assemblies with the strong name assigned to the Outbound Campaign
Management Tool and the Contact Center Agent Desktop. You can install the
CCMM_Security_Policy.msi file while you are logged on to the server as the
local administrator.
Installing the CCMM_Security_Policy.msi file
You must install the current Nortel CCMM_Security_Policy.msi file that is
included in the latest service update. For more information about the latest
service update, visit www.nortel.com.
There are three methods to install the security policy:
a manual installation, recommended to test the client applications on one or
two clients
Installation and Maintenance Guide
Migrating Contact Center 6.0 to a new server
737