Cisco Cisco Unified Contact Center Enterprise 9.0(1)
New and Changed Information
Release Notes for Cisco Unified Contact Center Enterprise Release 9.0(1)
Page | 12
North American Local Exchange NPA NXX DatabaseUpdate
For those that use Outbound Option, the region prefix has been updated for accuracy.
Obsolete Configurations
Beginning with Unified CCE Release 9.0(1), the following configuration types are obsolete:
Multi-NAM
4K Multi-CTI OS
Multi-Instance CTI OS
Multi-Instance SIP Dialer
QoS Implementation and Support
In Unified CCE Release 9.0(1), the Microsoft Packet Scheduler (for Router/Router, PG/Router, and PG/PG
connections) is no longer available. The ability to enable Packet Scheduler on the PG Setup was also
removed.
connections) is no longer available. The ability to enable Packet Scheduler on the PG Setup was also
removed.
For Microsoft Windows Server 2008, the Microsoft facility for DSCP packet markings (the IP_TOS socket
option) was removed. Subsequently, for Microsoft Windows Server 2008, packet markings are now made
with locally created QoS Policy entries. Note that the functional result for Microsoft Windows Server 2003
and 2008 installations is the same.
option) was removed. Subsequently, for Microsoft Windows Server 2008, packet markings are now made
with locally created QoS Policy entries. Note that the functional result for Microsoft Windows Server 2003
and 2008 installations is the same.
Note
Due to the removal of the IP_TOS socket option from Microsoft Windows Server 2008, applications
that include the Silent Monitor Server and the CTI OS servercan no longer set ToS markings for
outgoing packets.
that include the Silent Monitor Server and the CTI OS servercan no longer set ToS markings for
outgoing packets.
The CTI Client Interface Library (or CIL) also implemented QoS support with the IP_TOS socket option;
this functionality is supported under Windows XP, but not under Windows Vista or Windows 7. Therefore,
any CIL-based CTI Client on Microsoft Vista or Windows 7 cannot rely on the TOS (Type of Service)
parameters in the connection libraries to properly mark packets. A policy-based QoS arrangement (similar
to that taken on Unified CCE services) is not in the CIL because that approach relies on administrator or
elevated privilege, and Cisco cannot guarantee that client installation programs, or the client applications
themselves, will have the required privileges to add, delete, or modify a QoS Policy. Due to the large
number of CTI Clients in any installation, Cisco supportsan Active Directory administered QoS Group
Policy. An Active Directory administered QoS Group Policy will drive consistency across the client
installations. If a locally created QoS Policy is deemed necessary, use the IGroupPolicyInterface to
programmatically manage policies.
this functionality is supported under Windows XP, but not under Windows Vista or Windows 7. Therefore,
any CIL-based CTI Client on Microsoft Vista or Windows 7 cannot rely on the TOS (Type of Service)
parameters in the connection libraries to properly mark packets. A policy-based QoS arrangement (similar
to that taken on Unified CCE services) is not in the CIL because that approach relies on administrator or
elevated privilege, and Cisco cannot guarantee that client installation programs, or the client applications
themselves, will have the required privileges to add, delete, or modify a QoS Policy. Due to the large
number of CTI Clients in any installation, Cisco supportsan Active Directory administered QoS Group
Policy. An Active Directory administered QoS Group Policy will drive consistency across the client
installations. If a locally created QoS Policy is deemed necessary, use the IGroupPolicyInterface to
programmatically manage policies.
Virtualization: UCS Network Configuration and QoS