Virtual Office configuration issues

Last Updated : Oct 24, 2019 |
Prolog information
Metadata
Keywords:

Condition

Virtual Office Login Allowed (VOLA) attributes are set, but virtual key does not appear during configuration.
The cause for the Virtual Office configuration issue can be one of the following:
  • VOLA attributes are in the second line of features in Communication Manager endpoint configuration.
  • Key maps take a long time to update.

Solution

  1. Check Avaya Breeze® platform for the latest version.
  2. Move VOLA attributes to the first line of features in Communication Manager endpoint configuration.
  3. If moving VOLA attributes to the first line of features in Communication Manager endpoint configuration fails, then reboot the UNIStim endpoint and retry.
  4. If rebooting of UNIStim endpoint fails, then collect DSA (syslogLevelSet dsa tDSA 7) and TPS (syslogLevelSet tps tSET 7) DEBUG logs during registration to analyze and fix the issue.