Cisco Cisco E-Mail Manager Unity Integration Option Release Note
Cisco Unified ICM/Unified CC Enterprise & Hosted Editions, Releases 7.0(0) SR1 – SR4 and 7.1(x) Rev. 1.14
Hardware and System Software Specification
6BICM/IPCC Hardware and Software Requirements
©2008 Cisco Systems, Inc.
55
SQL Server 2000 licensing is required for any and all ICM/IPCC deployments. Customers must determine the appropriate licensing
methods based on the size of the deployment. It is not uncommon for a contact center environment to have more agent personnel
than stations so the most appropriate method of licensing in this case would be using device CALs versus user CALs. In large
installations, the cost of the total amount of user or device CALs required may surpass the cost of processor licensing so the latter
may be the appropriate licensing method. A processor license for each of the processors on the database servers would be required.
methods based on the size of the deployment. It is not uncommon for a contact center environment to have more agent personnel
than stations so the most appropriate method of licensing in this case would be using device CALs versus user CALs. In large
installations, the cost of the total amount of user or device CALs required may surpass the cost of processor licensing so the latter
may be the appropriate licensing method. A processor license for each of the processors on the database servers would be required.
Note: A license is required for every user of the system regardless of whether the deployment is distributed (for example, WebView
and HDS on separate nodes). For more information, see
and HDS on separate nodes). For more information, see
In deployment scenarios where Cisco IPCC Hosted Edition or ICM Hosted Edition is used by service providers, Microsoft’s Service
Provider License Agreement (SPLA) would apply in lieu of other licensing models. Under SPLA, SQL Server 2000 is licensed on a
monthly basis to end customers of the service providers. Service providers should consult with Microsoft to determine the
appropriate licensing model for their SQL Server 2000 deployments.
Provider License Agreement (SPLA) would apply in lieu of other licensing models. Under SPLA, SQL Server 2000 is licensed on a
monthly basis to end customers of the service providers. Service providers should consult with Microsoft to determine the
appropriate licensing model for their SQL Server 2000 deployments.
Cisco ICM or IPCC (Enterprise and Hosted) customers are encouraged to consult Microsoft documentation and other resources to
determine the licensing that best fits their specific ICM/IPCC deployment. In many cases, ICM/IPCC customers may already have
the necessary SQL Server licenses under an existing agreement with Microsoft. Consult your IT or Legal organization for more
information.
determine the licensing that best fits their specific ICM/IPCC deployment. In many cases, ICM/IPCC customers may already have
the necessary SQL Server licenses under an existing agreement with Microsoft. Consult your IT or Legal organization for more
information.
Microsoft Licensing terms are subject to change. Customers are ultimately responsible for ensuring their SQL Server licensing is in
compliance with Microsoft’s End User License Agreement (EULA).
compliance with Microsoft’s End User License Agreement (EULA).
The table below provides supplemental information.
Table 7.65: SQL Server Licensing Guide
Node
SQL Server Licensing
Model
Model
Note
Central Controllers
LoggerA (or RoggerA) or Central
Controller (System IPCC)
Controller (System IPCC)
Processor License
For dual-processor servers, it is more cost effective to
acquire a processor license for each physical processor than
it is to purchase individual CALs when the number of users
(incl. agents/supervisors) exceeds approximately 25 or fewer
users per processor for Standard Edition and 75 or fewer
users per processor for Enterprise Edition.
acquire a processor license for each physical processor than
it is to purchase individual CALs when the number of users
(incl. agents/supervisors) exceeds approximately 25 or fewer
users per processor for Standard Edition and 75 or fewer
users per processor for Enterprise Edition.
LoggerB (or RoggerB) or Central
Controller (System IPCC)
Controller (System IPCC)
Server License only
LoggerB is used for failover purposes and therefore does not
require a license as long as it has the same or fewer
processors than LoggerA (when per processor licensing is
used). Where Outbound Option is deployed, the same
recommendations apply.
require a license as long as it has the same or fewer
processors than LoggerA (when per processor licensing is
used). Where Outbound Option is deployed, the same
recommendations apply.
Router
None
While the Router node does not host a database it may act as
a client to a remote database using the dbworker or appgw
processes. Customers should follow vendor guidelines for
licensing those remote database servers.
a client to a remote database using the dbworker or appgw
processes. Customers should follow vendor guidelines for
licensing those remote database servers.
Distributors
AW Distributor (AWD) (Primary
and/or Secondary)
and/or Secondary)
Server License plus one User
CAL for each application
administrator and one Device
CAL for each Client AW
CAL for each application
administrator and one Device
CAL for each Client AW
Application administrators can be Script Editor or
Configuration Manager users. Each AW Distributor should
have a Device CAL allocated for each active Client AW
(standby connections do not require a license).
Configuration Manager users. Each AW Distributor should
have a Device CAL allocated for each active Client AW
(standby connections do not require a license).
AW Distributor (AWD) + Internet
Script Editor Option
Script Editor Option
Server License plus one User
CAL for each Internet Script
Editor user
CAL for each Internet Script
Editor user