SmartCallMonitor Changelog

What is New in SmartCallMonitor?

Version 3.3

New license keys

  • SmartCallMonitor utilizes a new license management now. Starting with version 3.3 new license keys are in effect and replace the previously used license keys. The new keys can be found in the customer area (Professional only).

VoIP – Softphone

  • For the VoIP softphone, automatic redirection to another line can now be configured (Professional only).
  • For VoIP lines the status "Do not disturb" can now be activated (Professional only).
  • VoIP lines can now also be monitored on a remote SmartCallMonitor instance. So VoIP lines as well as TAPI lines can be centrally configured on a               SmartCallMonitor server installation and can be used by other SmartCallMonitor installations (Professional only).
  • VoIP calls now also work in an RDP session. So it is possible to use SmartCallMonitor in a remote desktop connection (Professional only).
  • Phone menus can now be controlled by the softphone (Professional only).
  • SmartCallMonitor can play the ringtone for incoming VoIP calls on a second audio device (Professional only)
  • Configuring SmartCallMonitor as a softphone for VoIP telephony is easier and more understandable (Professional only).
  • The audio device for VoIP calls can now be tested in the settings (Professional only).
  • Several errors when setting up a VoIP line are fixed (Professional only).

Other improvements

  • With the new "Line Status" permission, the line status can be shared with other users in the network without disclosing caller information (Professional only).
  • Managing user rights for a line is now more convenient (Professional only).
  • SmartCallMonitor now also displays anonymous calls
  • TAPI calls now support call redirecting by prior arrangement, too.
  • The line to be used can now be selected in the phone sidebar.
  • Redial is now accessible from the main window.
  • Some errors when using the setup wizard are fixed.
  • In certain cases, forwarding a call resulted in multiple entries in the call journal. This is now fixed.
  • The reverse search of is now queried correctly again.

8 October 2020