Cisco Cisco E-Mail Manager Unity Integration Option

14

QoS allows customers to more easily prioritize traffic on their network.

QoS is now supported on the dedicated (‘private’) network between duplexed pairs of Routers and of 
PGs (respectively):

Replacing UDP heartbeats with TCP keep-alive messages 

Supporting layer 2 prioritization with 802.1p, a LAN QoS handling mechanism

Supporting layer 3 classification with DSCP 

See 

, for additional details.

The Logger now handles configuration and historical data separately, so that configuration changes are 
no longer slowed down by historical data transfers. Similarly, in the case that historical data transfer 
temporarily fails, propagation of configuration changes will remain unaffected. Note that this combined 
functionality is still part of a single Logger node; that is, the externally visible functionality of the 
Logger remains essentially unchanged.

When ICM uses the "translation route to VRU" method to route a call to a type2 SCI VRU, the VRU 
becomes the new routing client for the call. For Release 7.0(0) a new mechanism has been added in ICM 
to support a subsequent network transfer using that new VRU routing client. In an environment in which 
the original routing client is not capable of network transfer, all the pre-route calls can be transferred to 
CVP via Translation Route To VRU to take advantage of the network transfer feature.

This feature can be used in several scenarios:

To support Transfer to VRU with Outbound for Hosted IPCC where a shared Network VRU is used 
for providing announcements to targeted phones/answer machines.

To receive a call on an converged enterprise network after a carrier pre-route using CVP to control 
the call.

To use pre-routing for load balancing purposes before the call is sent to a CVP controlled network, 
with call context and cradle to grave reporting capabilities.

For new installations, Release 7.0(0) ICM/IPCC Setup requires the installation of Windows Server 2003 
SP1 (or later).

For Release 7.0(0) common ground upgrades (which are subject to a later update of the operating 
system), the SP4 requirement for Windows 2000 must be met. All components of Release 7.0(0), 
including CTI OS, have this common ground upgrade requirement.

Note that Windows 2000 Server is subject to end-of-life/end-of-support considerations as enforced by 
Microsoft.

Specific requirements, for new installations, technology refresh upgrades, and common ground 
upgrades, are found in the Cisco ICM/IPCC Enterprise and Hosted Edition Hardware and System 
Software Specification (Bill of Materials) and the ICM Upgrade Guide for Cisco ICM/IPCC Enterprise 
& Hosted Editions.