In earlier releases, each SIP user was assigned to a set of Session Managers (Primary, Secondary, and Tertiary) and administrators had to manually administer primary, secondary, and tertiary Session Managers to user's devices. In Release 8.1, Session Managers were assigned to a user based on the user's location from where they login. If a user registers in two or more devices from different locations with different Session Managers assigned to each location, the policy-based assignment of a user rearranges Session Managers so that all devices of a user registers to the same pair of Session Managers.

Though the new policy is dynamic, all devices of a user registers to the same pair of Session Managers. Session Managers are assigned based on the last registered location of a user.

From Release 10.1.2, Avaya Device Adapter supports the CSDK version update to support new policy-based assignment of users to Session Managers. The new policy ensures that a Session Manager supports local redundancy allowing a user to have more than two core Session Managers and a branch Session Manager. For customers that require local survivability as well as geographic redundancy, the two locally redundant Session Managers share a single IP address, so the presence of two Session Managers is hidden from endpoints and applications.

The CSDK version update in Avaya Device Adapter enables a user to register a maximum of four core Session Managers.