Adding users

Last Updated : Aug 21, 2024 |

About this task

Use this procedure to add users in Session Manager. You can ignore any unnecessary input fields.

For information on other sections of the User Management page, see the System Manager online help.

Important:

When you create a user with a user provisioning rule, the system populates the user attributes values from the user provisioning rule. Do not modify the populated values.

Before you begin

For assigning Session Managers to a user based on a defined policy, select the Enable Policy Based Assignment of Session Managers option on the Global Settings page.

Procedure

  1. On the System Manager web console, click Users > User Management  > Manage Users.
  2. Click New.
  3. Verify that the Identity tab is selected.
  4. Optional In the User Provisioning Rule field, select a user provisioning rule.

    You can select only one user provisioning rule. For assigning user provisioning rules, see User provisioning rule.

  5. In the Identity section, enter the required information in the appropriate fields.
  6. Click the Communication Profile tab.
  7. In the Communication Password field, enter a password for the user. The user must enter this password to log in to the endpoint.
  8. For each SIP handle:
    1. If you are adding a non-SIP endpoint user, for example, a DCP endpoint user, verify the communication address of the user conforms to the Avaya E.164 type.
    2. In the Communication Address section, click New.
    3. In the Type field, select Avaya SIP from the menu.
    4. In the Fully Qualified Address field, enter the extension number.
    5. Click Add.
  9. In the PROFILES section, click the toggle button next to Session Manager Profile.

    System Manager enables Session Manager Profile and displays the fields of the Session Manager profile.

  10. If you do not select the Enable Policy Based Assignment of Session Managers option, perform the following:
    1. In the Primary Session Manager field, select the Session Manager to use as the home server for the currently displayed communication profile.
    2. In the Secondary Session Manager field, select the Session Manager to serve as secondary service provider if primary Session Manager fails.
  11. If you select the Enable Policy Based Assignment of Session Managers option, perform the following:
    1. In the Policy field, select the required policy for the Session Manager communication profile.

      Based on the policy selection, the system displays the relevant fields. The options are:

      • fixed: When you select this option, the system displays the Primary Session Manager, Secondary Session Manager, Third Session Manager, and Fourth Session Manager fields.

        The default value is fixed.

      • fixed-region: When you select this option, the system displays the Primary Region, Secondary Region, Third Region, and Fourth Region fields.

        The system assigns the primary, secondary, third, or fourth region to the Session Manager Communication profile.

      • location-region: When you select this option, the system does not display the Primary Session Manager and Secondary Session Manager fields and performs the dynamic assignment of Session Manager based on the mapping of locations to regions on the Elements > Session Manager > Session Manager Administration > Groups > Location to Region Mapping page.

    2. Based on the Policy selected, specify the Session Managers or regions required for the communication profile.
  12. Optional For survivability, in the Survivability Server field, specify a survivability server. For example, Branch Session Manager.
    Note:

    When you administer a user with a Survivability Server, the system verifies that valid SIP Entity links exist between the Branch Session Manager and the administered Primary and Secondary Session Manager servers.

  13. In the Max. Simultaneous Devices field, select the appropriate value from the menu.
  14. Optional Select the check box for Block New Registration When Maximum Registrations Active?.
  15. In the Origination Sequence field, select the origination application sequence from the menu.
  16. In the Termination Sequence field, select the termination application sequence from the menu.
  17. In the Emergency Calling Origination Sequence field, select the emergency calling origination sequence from the menu.
  18. In the Emergency Calling Termination Sequence field, select the emergency calling termination sequence from the menu.
  19. In the Home Location field, enter the location. This field is mandatory for mobile users.
  20. In the Conference Factory Set field, select the Conference Factory Set from the menu.
  21. Optional Select the check box for Enable Centralized Call History.
  22. Optional Select the required client for Enable Client.
  23. Optional Click Commit.
  24. Assign the user to a Communication Manager station:
    Note:

    You can assign a user to a Communication Manager station after the data synchronization is complete.

    1. Select the CM Endpoint Profile check box.
    2. From the System menu, select Communication Manager.
    3. If the station associated with the user already exists on Communication Manager, select the Use Existing Endpoints check box.
    4. In the Extension field, enter the extension administered on Communication Manager for the existing or new station.
    5. To change the Communication Manager station data, click Endpoint Editor and make the necessary changes.
    6. If the user is not associated with an existing Communication Manager station, in the Template field, select a phone template for the station of the user from the menu.
    7. In the Port field, enter the port associated with the extension.
    8. Optional Select the Delete Endpoint on Unassign of Endpoint from User or on Delete User box. This step applies if you want the system to delete the station when you delete the user or unassign the endpoint.
  25. Click Commit.
  26. Verify the order of the Session Manager servers.
Related information
User Profile | Add field descriptions
Verifying the Session Manager configuration sequence