Configuring Virtual Office support for Device Adapter UNIStim endpoint

Last Updated : Oct 08, 2020 |
Prolog information
Metadata
Keywords:
Before you begin
Device Adapter requires the following class of service attributes to configure Virtual Office feature:
  • Virtual Office Login Allowed (VOLA)
  • Virtual Office User Allowed (VOUA)
  1. Do one of the following:
    • Configure the CS1K-IP station in Communication Manager. For more information, see Communication Manager documentation.
    • Do the following to configure the CS1K-IP station in System Manager:
      1. Log in to System Manager by using the appropriate administrative credentials.
      2. Click Users User Management Manage Users.
      3. Select the user, and then click Edit.
      4. On the User Profile: Edit: <user name> page, click Communication Profile tab and then click Session Manager Profile.
      5. In the SIP Registration area, in the Max. Simultaneous Devices field, click 1.
      6. Clear the Block New Registration When Maximum Registrations Active check box.
      7. Click Commit.
  2. Configure the applicable CoS from VOLA/VOUA for the Device Adapter. For more information, see CS 1000 CoS and Avaya Aura feature field mapping.
  3. Do the following to configure the Idle time interval for DVLA set field for the DVLA phones:
    1. In the Idle time interval for DVLA set field, enter a time interval which defines maximum time for DVLA phones.
      ADDITIONAL INFORMATION:
      This attribute can be set to values ranging from 1 to 1440 minutes in one of the following formats:
      • Minutes. For example, 5 or 5m.
      • Hours and minutes. For example, 5h 5m.
      • Hours. For example, 5h.
      ADDITIONAL INFORMATION:
      By default, the value is 0 because this function is considered to be turned off.
      The following error message is displayed when a user tries to set any other non-numeric value:
      "Service Globals : The attribute Idle time interval for DVLA set does not contain a valid value based on the attribute type. Please correct the entry.".
      There are no additional logs for tracking incorrectly entered data, as this happens on the Session Manager side and when entering incorrect data, no messages are sent to the Device Adapter side.
    2. Click Commit.