Improving Performance for Communications Configurations

This topic is part of Guidelines for Session Communications Tuning.

When you deploy session communications, you create communications configurations, define employees as agents, and associate each agent with one or more configurations. How you do these things affects performance and scalability.

In a deployment supporting a large number of agents across multiple physical sites, you must determine criteria for grouping your agents within configurations.

For example, some dialing filters that you define, using the parameter DialingFilter.RuleN, might be appropriate for agents at a specific place, such as within the same country or area code. Other dialing filters might be suitable for a different set of agents.

In addition, some switch, teleset, or CTI middleware settings are reflected in your communications configuration, and can differ between physical locations.

It might be helpful to define a communications configuration to apply to users at a single location only. In addition to simplifying the process of defining communications configurations, telesets, or other elements, this approach can help you reduce demand on server resources such as Siebel Application Object Manager memory or CPU.

If call transfers or similar functions are to be supported between contact centers, then additional configuration issues apply.

For more information about defining communications configurations and agents, see Siebel CTI Administration Guide.