Session Manager instances are configured through Interaction Administrator. These settings enable management of the existence of each Session Manager instance, identity, and regionalization settings.
Once a Session Manager instance has had its certificate trusted and then successfully connected to the CIC server, Interaction Administrator automatically displays that Session Manager in the Session Managers >
Servers container. The list in that container serves as a roster of the available Session Managers, which informs IceLib-based applications about available Session Manager instances for connections.
If a trusted Session Manager instance is down, Interaction Administrator still displays its entry. This approach enables an IceLib-based application to cache the exact roster of available Session Managers, even if an off-server Session Manager was down for maintenance at the time that the IceLib-based application last
connected. One advantage is that IceLib can trust the exact roster it receives and replace its old cache, rather than being forced to merge the roster into the cache—as it did in CIC 3.0—to remember offline off-server Session Manager instances.
7.1.1 Retiring a Session Manager Instance
To permanently retire a Session Manager instance, do the following steps:
1. Ensure that the off-server Session Manager is off by stopping the following services on its host:
ININ Windows Service Monitor
IC Session Manager Service
2. Open Interaction Administrator and log on with CIC administrator credentials.
3. In the left pane of the Interaction Administrator window, select System Configuration > Session Managers > Servers.
The right pane displays the current list of Session Manager instances.
4. In the right pane, right-click a Session Manager instance that you want to delete and select Delete from the resulting context menu.
7.1.2 Setting Session Manager Identity
When the roster of available Session Manager instances is returned to IceLib-based applications, each Session Manager is identified with the exact network name for IceLib to use in its connection attempts. This Session Manager identifier defaults to the Fully Qualified Domain Name (FQDN) that the Session Manager instance had for itself; however, you can override it through the Interaction Administrator entry for that Session Manager instance and specify whatever value is most appropriate for a given installation. The FQDN must be accessible from all domains from which IceLib-based applications are used to connect.
7.1.3 Use Regionalization with Selection Rules
You can associate Session Manager instances with a Location entry in Interaction Administrator to support regionalization. This configuration enables connections for users/stations associated with a particular Location entry to prefer Session Manager instances associated with Location entries based on Selection Rules. The IceLib-based application gives preference to the Location entry associated with the Station being used to connect (if any), and then to the Location entry associated with the CIC user. Then, the Default Location entry is used as a fallback. IceLib-based applications use the Selection Rule configured for the
The application uses the Selection Rule configured for the Location entry as a guide to prioritize the best Session Manager instances. If the prioritized ones were not available, and the Selection Rule allows for connecting to Session Managers in any other locations, then connections to instances in non-prioritized locations will not be prevented.
By default, the off-server Session Manager server uses the Location of the CIC server.
For more information about how clients select Session Manager instances, see Section 2.3.1 Client Application Selection with Regionalization and Selection Rules.
The Session Manager instances that are associated with a given Location appear in the configuration for that Location in the Regionalization > Locations container in Interaction Administrator.
7.1.4 Specify Switchover Behavior
In a switchover environment, off-server Session Manager instances also have an option for whether they always connect to the current primary CIC server, or if they stay pinned to a particular CIC server.
Interactive Intelligence recommends that you leave this setting as the default value, which is to configure the off-server Session Manager instances to switch and stay connected to the current primary CIC server.
The option for always connecting to the particular CIC server specified at installation is much less common and is left available for backward compatible behavior for some WAN-switchover sites. Interactive Intelligence does not recommend the “no-switch” mode for recent CIC releases.
7.1.5 Configure Session Manager Selection Rules
In Interaction Administrator, you can configure Locations to have Session Manager Selection Rules. These Selection Rules can be used to prioritize the Location of Session Managers to which a user in that Location would connect. For more information on configuring Session Manager Selection Rules, see Section 2.3.1, Client Application Selection with Regionalization and Selection Rules.
You can add or edit a Selection Rule in Interaction Administrator under the Regionalization > Selection Rules container.
Each Selection Rule can have a list of Prioritized Locations and a list of Excluded Locations.
Use the Add Locations dialog box to add existing Locations to the Prioritized Locations list group box.
CIC processes Locations in the Prioritized Locations list group box from top to bottom.
The Add Locations dialog box contains unassigned Locations and special Location variables that are unique to Selection Rules:
Table 6 – Session Manager Selection Rule Variables Selection Rules Location variable Description
<This Location> This variable represents the location to which the Selection Rule is applied. For example, if you configure a Session Manager Selection Rule on Location1, then instances of <This Location> in that Selection Rule return Location1.
<CIC Server Location> The Location of the CIC server.
<Other Locations in Audio Path> Session Manager does not use this Location variable in its Selection Rules. Session Manager ignores any instance of this Location variable in its Selection Rules.
You can group multiple locations using the Group selected button so as to give Session Manager instances in those Locations the same priority level and cause CIC to select one Session Manager instance from the Locations within that group.
The Excluded Locations list group enables you to specify the following Selection Rules behavior:
Do not use any other Locations – This option specifies that the CIC server can consider and connect to only Session Manager instances in the Prioritized Locations list group box.
Use any Location, except the following – This options specifies that the CIC server can consider and connect to any Session Manager instance, in any location, except for those Locations specified in the list box.
For more information about Selection Rules, see Section 2.3.1 Client Application Selection with Regionalization and Selection Rules.
Once you have configured a Selection Rule, you can apply it to a Location as its Session Manager Selection Rule. To do so, edit a Location in the Regionalization > Locations container in Interaction Administrator, and then select a Selection Rule in the Session Manager list box located in the Selection Rules section.
By default, a Location uses the <Default Session Manager Selection Rule> for its Session Manager Selection Rule. <Default Session Manager Selection Rule> consists of only <This Location> as the top priority Location, and then includes all other Locations after that with no excluded Locations.
7.1.6 Configure a Session Manager’s Accept Connections Status
Using Interaction Administrator, you can configure a Session Manager instance to accept client connections with the Connections option buttons:
The Connections options are as follows:
Use default behavior - This setting has a different meaning depending on whether the Session Manager is an on-server Session Manager or an off-server Session Manager.
On-server Session Manager - The default behavior depends on if there are available off-server Session Managers or not:
Available - Session Managers do not accept connections.
Not available – Session Managers accept connections.
Off-server Session Manager - The default behavior is to accept connections.
Accept all connections - With this setting, Session Manager accepts connections regardless of whether it was an on- or off-server Session Manager and if any off-server Session Managers are available.
Do not accept new connections (Maintenance Mode) - With this setting, Session Manager stops accepting new connections. If there are existing connections to the Session Manager instance, those will remain live until either those clients disconnect themselves or the Session Manager instance is restarted to remove those connections.