Bridge Communications

Saturday, February 20, 2016

BOC Call Recorder - New Features

This week we have added a bunch of new features to the BOC Call Recorder.  Today's blog will discuss them in detail, including how to configure Group Policy settings.

Minimize to System Tray
























With this option you can hide the main screen completely from view, and from the taskbar, leaving almost no footprint of the application.  A left click will show this popup where you can see the activity status, and shortcuts to the main operations.  A right click will display a context menu with shortcuts to record, stop, settings, view application, and exit.

Optional Notifications

You can now receive optional Windows system notifications when auto recording stops and starts.  These can be controlled on the settings page and will look something like this.


Other New Settings

Settings Page















Some of the new settings not mentioned above are the options to start the program minimized, or keep the program on top of all other running programs.

Group Policy Settings Override

With version 1.0.15 and above BOC Call Recorder has the option to read settings pushed out via group policy.  If the registry key HKLM\Software\Policies\Bridge Communications\BOC Call Recorder exists the program will read it's settings there, and make the settings page view only.  If it does not exist the program will use it's normal HKCU\Software\Bridge Communications\BOC Call Recorder settings, and the settings screen will function like normal.  The key to be pushed out will mirror the local keys and look like this.


AlwaysTop 0 = no, 1 = yes
AutoRecord 0 =no, 1 = yes
Folder = The default folder to save files with a \ at the end
InputDevice = The Windows System name of the Microphone (note this is a contains search to if you get the first unique part of it, it should work)
Minimized - Auto start minimized 0 = no, 1 = yes
MinSpace - Number of GB free at which the recorder stops recording, and a warning is displayed.
OutputDevice - Same as input, but the playback device instead of recording device.
RecAlerts - Receive Windows System notifications when recording stops and starts. 0 = no, 1 = yes
ShowMin - Show alert when program is minimized so the user can find it. 0 = no, 1 = yes



Doug Routledge, C# Lync, Skype for Business, SQL, Exchange, UC Developer  BridgeOC
Twitter - @droutledge @ndbridge


6 comments:

  1. Trying to change the path for recordings to %SYSTEMROOT%\%USERPROFILE%\Documents\Recording\ MyDocs is redirected via GPO to a Network share.

    Does BOC Recording software recognise system variables and or network share paths?

    ReplyDelete
    Replies
    1. It stores the value in registry as a string, so you can either browse using the folder browser, or set the users programatically using group policy. It could be that c# doesn't recognize the special characters.

      Delete
    2. Thanks Doug think it's the latter, reset it to default location, and confirmed working. Then changed path via registry to %LOCALAPPDATA% var with the remainder of the path and it stopped recording again. Also wont work If I set path to My Docs which is redirected via gpo to a network share, anyone had any success in getting it to work to a network share?
      Thanks guys.

      Delete
    3. I believe unicode characters 1-31 are not allowed in c# file paths. % is 25. You can use a UNC path, mapped network drive, or something like C:\users\him\appdata\local\folder either would be fine. Basically is you use the utility to browse for the folder you should be fine.
      https://msdn.microsoft.com/en-us/library/system.io.path.invalidpathchars(v=vs.110).aspx

      Delete
  2. Hi Doug. I have asked a few of our users to evaluate BOC Call Recorder. Everything seems good but the ability to auto record calls stops working almost immediately. Is there a setting that we can use that locks to program to auto record all S4B conversations or force this functionality on? Many thanks Rod

    ReplyDelete
  3. There is the auto record setting in the settings, nothing else should be required. Are there any errors in the windows event viewer application log around the time it stops working?

    ReplyDelete