Configure Busylight settings with registry keys

The article details how to configure Busylight settings on Windows, including predefined color codes for presence states, and explains how to customize these via registry keys under HKCU\Software\Busylight. 

The article covers changing color values, distributing settings via group policies, and provides tables of all relevant registry keys and default values.

Predefined colors

Busylight has predefined color settings for presence states with the colors:

Color Description
Red Busy or On a call
Green Available
Purple Do not disturb
Blue Ringing or IM alert
Yellow In a meeting

Registry keys

The predefined color values and their dynamic behavior can be changed via registry keys. 

These keys are stored in the path HKCU\Software\Busylight and can be changed or added via registry keys, or centrally via group policies. 

  • Changes may also be applied after installation of the Busylight software.
  • After changing the values in the registry, Busylight has to be reset or restarted.
  • The easiest way is to click the Busylight icon in the Windows systray and choose “Reset Busylight“.
Tray app menu (left with Busylight only, right with Kuando Box and Busylight)

Figure: Tray app menu (left with Busylight only, right with Kuando Box and Busylight)

 

 

Example: Changing “Busy” from Red to Blue

The registry keys allow you to control the values of the Red, Green and Blue (RGB) colors in the Busylight LED light (the allowed range is 0-100 as a percentage in decimal).

Note

To open Registry Editor, run regedit in Windows.

To change the colour for Busy (see screenshot below):

  1. Insert two new DWORD values named “Red” and “Blue”.
  2. Set Red to 0 (to cancel the default value).
  3. Set Blue to e.g. 50 (percent).

 

 

You can also mix the basic colors to create new ones, e.g., Purple is a mix of Blue (value: 60), Green (value: 40) and Red (value: 1).

To get a unified color scheme within an organization, it is recommended to distribute the changes configuration via group policies.

 

Default color values

The following table contains all registry keys that are used by Busylight, along with the default values if the key does not exist:

Registry Key Data type Description Default Value (Decimal) New Default V 3.0
Away
Blue DWORD Blue value for "Away" 0 0
Green DWORD Green value for "Away" 18 100
Red DWORD Red value for "Away" 16 89
Busy
Blue DWORD Blue value for "Busy" 0 0
Green DWORD Green value for "Busy" 0 0
Red DWORD Red value for "Busy" 50 100
BusyInACallColor STRING "Pulse" or "Red" "Pulse" "Pulse"
BusyInCallSequence
Step1 DWORD Color intensity for "on the phone", Step 1 7 14
Step2 DWORD Color intensity for "on the phone", Step 2 21 42
Step3 DWORD Color intensity for "on the phone", Step 3 36 72
Step4 DWORD Color intensity for "on the phone", Step 4 50 100
Step5 DWORD Color intensity for "on the phone", Step 5 36 72
Step6 DWORD Color intensity for "on the phone", Step 6 21 42
Step7 DWORD Color intensity for "on the phone", Step 7 10 20
Red DWORD Red value for "on the phone" 50 100
Green DWORD Green value for "on the phone" 0 0
Blue DWORD Blue value for "on the phone" 0 0
Free
Blue DWORD Blue value for "Available" 0 0
Green DWORD Green value for "Available" 50 100
Red DWORD Red value for "Available" 0 0
DoNotDisturb
Blue DWORD Blue value for "Do not disturb" 60 100
Green DWORD Green value for "Do not disturb" 1 2
Red DWORD Red value for "Do not disturb" 40 67
Ringing
Blue DWORD Blue value for "Ringing" 100 100
Green DWORD Green value for "Ringing" 0 0
Red DWORD Red value for "Ringing" 0 0
Off
Blue DWORD Blue value for "Offline" 0 0
Green DWORD Green value for "Offline" 0 0
Red DWORD Red value for "Offline" 0 0
IMAlert
IMAlert DWORD Flag for IM alert (0 or 1) 1 1
Blue DWORD Blue value for "new IM"
Green DWORD Green value for "new IM"
Red DWORD Red value for "new IM"
Other settings
IMAlertWithSound DWORD Flag for IM alert with sound 0 0
IMVolume DWORD Overrides "Volume" for IM alerts n/a n/a
MissedCallNotification DWORD 0 (Default): off · 1: on, blue blinking signal on missed calls 0 0
SoundClip DWORD Index of ringtone for calls (1…8) 1 1
Volume DWORD Volume of ringtone for calls 75 75

 

 

Registry key used for Kuando Box and Omega

Version 3.0 includes support for Kuando Box and Busylight Omega (large Busylight). 

There are special registry keys for these models.

Registry Key Data type Description Default Value (Decimal)
KuandoboxFadeoutTime DWORD Stores selected value of Fadeout time (timeout after voice detection) in seconds (menu options: 4 (default), 10 or 20) 4
KuandoboxSensivity DWORD Voice sensitivity value of KuandoBox (for adaption to different handset voice levels).
0: Minimal sensitivity (default)
1: Medium sensitivity
2: Maximum sensitivity
0

 

Registry keys used for the Lync Tools plugin 

The following table contains all registry keys used for the Lync Tools plugin 

Select Lync Tools in the Busylight menu

Registry Key Data type Description Default Value (Decimal)
HotKeyDialOutMod DWORD Modifier for function key "Fast dialout" -
HotKeyDialOuKey DWORD Function key for "Fast dialout" -
HotKeyAcceptMod DWORD Modifier for function key "accept call" or "drop call", resp. -
HotKeyAcceptKey DWORD Function key for "accept call" or "drop call", resp. -
BusyOnBusy DWORD Flag for call forwarding on Busy 0
SwitchDisplayOn DWORD Flag for switch on display on incoming contact 1
NoWarnOnDoubleLync DWORD Warning message can be switched off when both Lync 2010 and 2013 clients are installed 0
FastDialoutWithCtrlC DWORD Fast Dial hotkey shall emulate Ctrl-C to copy mouse selection into clipboard. Set to "0" when conflicting with other applications. 1
FonComfortInvisible DWORD 0: Lync-Tools visible and changeable (default)
1: Lync-Tools invisible
2: Lync-Tools Read Only
0

 

Special registry keys

The following table contains special registry keys:

Registry Key Data type Description Default Value (Decimal)
FonComfortInvisible DWORD Visibility mode for Lync tools:
0: Lync tools visible and changeable
1: Lync tools invisible and deactivated
2: Lync tool configuration read-only
0
SDKLogLevel DWORD Log level for USB communication:
0: no messages
1: verbose logging
0

 


 

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.