Policy-based Assignment of Users to Session Managers Overview

Last Updated : Mar 04, 2021 |

The policy-based assignment feature provides dynamic assignment of Session Managers based on a defined policy. A policy-based model indicates that the system selects the Session Manager servers based on a defined policy. The dynamic assignment occurs when the user logs in to their device. If a user logs in through multiple devices, the system applies the policy for each device login. Therefore, all devices of a user are assigned to the same set of Session Managers at a time.

When a user is assigned a Session Manager(s) dynamically, the system stores these assignments details in the Cassandra database. All Session Managers can access this data from Cassandra database. If the Session Manager server restarts, the system continues to perform the dynamic assignment of Session Managers.

The following policies can be applied to a user’s communication profile:

  • Fixed

  • Fixed-region

  • Location-region

To administer the policy-based assignment feature, select the Enable Policy Based Assignment of Session Managers option on the Elements > Session Manager > Global Settings page.

Note:

Before you enable the Policy-based Assignment of Users to Session Managers feature and pair Session Managers to Avaya Aura® Device Services, ensure that Avaya Aura® Device Services is on Release 8.1.4.

Fixed policy

This policy provides a fixed set of Session Managers to be assigned to a user. This policy is in line with the current practice of manual Session Manager assignment to a user and is maintained for backward compatibility. You can now assign up to 4 Session Managers to a user's profile with this policy. The additional two Session Managers allow both local and geo-redundancy simultaneously for added reliability.

Fixed-region policy

This policy dynamically assigns Session Managers to a user based on fixed administered regions. These regions are administered with the required Session Managers that eliminates the need to administer specific Session Managers to a user. The user is assigned to the Session Manager group or regions, and the policy selects the least loaded Session Managers within the regions and assigns it to the user.

Whenever a region assignment in a user’s communication profile is changed, the updates to the user’s Session Manager profile occurs immediately. If Session Manager assignment within the region is changed, then the system reflects the changes for the user’s Session Manager profile within 24 hours. A region group requires a minimum of one Session Manager and a minimum of two Session Managers if the same region is assigned to a communication profile more than once (for example: primary and secondary region). If the region is not referenced in a Location To Region Mapping or in a user's Session Manager profile, you can delete regions with Session Managers assigned.

Location-region policy

This policy determines the Session Managers assigned to the user based on the location of the last device login. A user’s location is mapped to regions on the Session Manager Groups page. When a user’s communication profile is assigned with the location-region policy, the least loaded Session Managers are selected from the regions mapped to the user’s location. The location-region policy helps to spread the load evenly across given regions.