As a result, the product suite includes multiple possibilities to accomplish certain tasks. Some decisions are based on changes in real-world infrastructure; others are based on the future development plans for certain product features.
These designs provide you with a set of common models for contact centers. You can simplify the design and acceptance processes by basing your deployment on these designs.
The designs also help insulate your deployment against future problems by avoiding technology that is nearing its EOL. The Packaged CCE product is its own model. It includes a prebuilt set of VM templates for deploying a contact center that supports up to agents. If this predefined contact center can answer your business needs, it greatly simplifies deploying a new contact center.
The distributed environment offers flexibility to design deployments for a range of performance, capacity, and network topology requirements. Unified CCE—4, Agents. Unified CCE—12, Agents. Large Unified CCE. There are no agents at this layer. The following list details some of the components, options, and configurations that the Unified CCE Reference Designs do not support:.
Simplex configurations for components that are normally deployed in redundant pairs. HCS for CC does support this integration with limits. Unified Communications Manager software-based conference bridges and Unified Communications Manager software-based transcoder as media resources. A two-tiered deployment that supports traffic volumes beyond the capacity of the Unified CCE —12, Agents model.
Use Contact Director as the self-service layer. The following tables list configuration limits and scalability constraints for various Unified CCE deployments.
Includes setup, configuration, and scripting users. Each Distributor can support up to 64 users. This number represents the maximum number of save operations across all ADS in the solution in a 1-hour period.
For the cceadmin gadget and associated APIs, each reskilling operation can include up to changes. The maximum indicated is independent from the number of ECC and user variables used, with each representing approximately bytes extra storage per record. The maximum includes both persistent and nonpersistent variables. Configuration of precision queues creates a skill group per agent PG which counts toward the supported number of skill groups on each PG.
Configuration of precision queues creates a skill group for each agent PG which counts toward the supported number of skill groups on each system.
A two-tiered deployment that supports traffic volumes beyond the capacity of the Unified CCE — 12, Agents model. Most of these system parameters or combinations of these system parameters form contribution factors that affect system capacity.
When you design your contact center, ensure your design is deployed within these limits. See the comments in the following table for more information. Consult Cisco if you have special configuration requirements that might exceed specific parameters. This infornmation serves as a quick reference. The compatibility matrix specifies all supported configurations and versions for Cisco Unified Contact Center Enterprise Release The information in the compatibility matrix supersedes compatibility information in any other Cisco Unified Contact Center Enterprise documentation.
If a configuration or version is not stated in the compatibility matrix, that configuration or version is not supported. See the notes at the end of this table. Deployments close to the maximum number of configured agents on a system can show performance degradation and failed call routing, especially if contending capacity limitations also approach maximum thresholds. Expert assistance from partner or professional services is generally necessary for capacity-related system planning.
Parameters that most impact performance with large numbers of configured agents include total number of system peripherals, routes, number of active agents, and overall call load. The points at highest risk for degradation are busy hours and the half-hour update period, during which the PG sends report data to the Central Controller. System administrators can lessen the impact of these issues by purging unused configured agents, retiring inactive peripherals, and maintaining systems at current maintenance release levels.
You can deploy only so many Administration and Data Servers for each Logger. The following table lists the limits for the types of active Administration and Data Server users.
Do not run more than ten concurrent reports on any client machine. This is a combined limit for reports that run on the Unified Intelligence Center User Interface, Permalinks, and Dashboards on the client machine.
However, you cannot run ten concurrent reports for the maximum reporting users on each node. Our capacity testing shows that reporting users can each have the following running reports:. If you have fewer reporting users on a node, they can run proportionally more reports. But, no client machine can exceed the ten report limit. Many variables affect system capacity, but Cisco chose values for a representative subset.
The sizing limitations in this table are based on that subset of variables. Does not include default skill group; assumes 17 statistics for each skill group enabled.
You can increase the number of monitor mode connections to 5 by reducing the All-Event clients by an equal amount. You can reduce the number of All-Event clients to support more monitor mode connections. The following list gives the minimum system requirements for agent and administrator workstations:. Graphics card —Support for x x 64 K color or better. The limits on how many of each you can have are linked.
If you use more of one, you can have less of the other. A combined maximum of nine All-Event clients and monitor-mode connections. Your design must trade off one for the other to stay within the combined maximum of 9. On each Agent PG, you can have the following:.
The number of All-Event Clients does not limit the number of monitor-mode connections that you can have on the large VMs. You can use the maximum amount of each type, if your system can support the load. If your deployment uses the CTI OS server, it begins with two monitor-mode connections on each side of the redundant pair.
However, you cannot configure those connections to fail over to the other side in a failure. Those extra connections would push Side B past the combined maximum of nine. Unified CCE negotiates the audio codec when a call first connects between two points. For example, the codec is negotiated when:. A call arrives in the system and media is established between the ingress gateway and a VXML browser.
A call in the queue connects to an agent and media is established between the ingress gateway and the agent phone. An agent conferences a call and media is established between all the parties and a conference resource. Codec selection can change on each leg of the call, depending on what codecs each component supports. This conversion enabled the voice traffic inside the contact center to run on G.
Unified Communications Manager allows configuring codec preferences at the region level; so you can advertise both A-Law and muLaw. CVP has default prompts for both mu-law and A-Law. You can only use one of the codecs in your deployment. Mobile Agent can advertise either G. But, Mobile Agent can only advertise one codec at a time.
All the Mobile Agents on a peripheral must use the same codec. The Unified Communications Manager must insert a transcoder in order to send a Mobile Agent a call in a different codec.
This table lists the availability of certain components and features in various deployment types. Congestion Control provides protection to the Central Control Router from overload conditions caused by high call rates. When faced with extreme overload, congestion control keeps the system running close to its rated capacity. Congestion Control provides satisfactory service during an overloaded condition to a smaller percentage of calls, rather than a highly degraded service to all calls.
The feature keeps the system within its capacity by rejecting calls by the Routing Clients at the call entry point. Throttling the capacities ensures the service of the routed calls is successful without timeouts. This throttling prevents overloading the Router and ensures the designed call processing throughput under overload conditions.
The following table lists the supported deployment types with the maximum supported calls per second CPS. This table lists some of these impacts. Unified CCE does not directly control the phones of mobile agents. The two delivery modes, Call-by-Call and Nailed Connection, use resources differently.
These formulas indicate platform capacity; they do not indicate how many agents can be kept busy by the number of dialer ports in the deployment. A quick, but inexact, estimate is that you require two ports for each outbound agent.
Your outbound resources can vary based on hit rate, abandon limit, and talk time for the campaigns. Use the sizing tool to determine outbound resources required for your campaigns. On the Router and Logger, the feature increases route requests made which effectively decreases the maximum call rate by about one third.
As the average number of precision queues or skill groups for each agent increases, the maximum concurrent agents for each PG and for the whole system decreases. The capacity impact varies based on ECC configuration, which requires professional guidance on a case-by-case basis. The Silent Monitor Server is a stand-alone server that provides silent monitor functionality for a set of mobile agents.
You can also configure the silent monitor service to provide silent monitor functionality for a single Unified CCE agent. Each of the deployment models described in this section assumes the possibility of an n-sided server configuration that replicates data between sites. WAN —Allocate a dedicated link of at least 1. Use a dedicated load balancer, rather than using Windows built-in functionality. Any load balancing solution must support sticky connections to maintain the web session information between requests.
A single-server system can only support the smallest deployments. Unified CCE supports E. For contact centers that advertise the agent extension outside of the contact center, these considerations apply:. To route incoming calls addressed to an E. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book Updated: October 13, Chapter: System Requirements and Constraints.
Model Description. Configured agents. Configured dialed numbers. Configured labels. Use agent targeting rules. Concurrent agents.
Concurrent agents on each UCM cluster. Active Administrators Users. Real-Time Only Distributors for configuration only. Concurrent Outbound Option agents. Sizing is required. Maximum number of clusters. Provisioning operations on each hour. Maximum agents tracked in Agent State Trace. Number of Peripheral Variables Call Variables. Peripheral Variable length characters. Maximum PGs. See system limits. Maximum VRU ports. Unified ICM does not support Finesse.
PIMs on each system total. C series. B series. Maximum outbound agents. Maximum dialer ports on each SIP dialer. Dialer ports on each system total. Dialers on each system total. Android has supported VP9 since version 4. Parts of the format are covered by patents held by Google. The company grants free usage of its own related patents based on reciprocity, i. DivX 10 DivX 10 is an advanced codec which enables you to convert and play almost any video file; it also allows high quality DivX HEVC video creation and video streaming.
Download VP9 Video Extension. Write a review or just post a comment about VP9 Video Extension. Let other people know about your opinion or experience with this software. Write a review. VP9 Video Extension 1. Updated: 15 Oct Be the first to review it!
0コメント