During your maintenance period, they are located at Downloads -> Older versions in the customer area, if you are logged in to your customer account.
You should be able to find the installation files and keys of the two last major versions there.
During your maintenance period, they are located at Downloads -> Older versions in the customer area, if you are logged in to your customer account.
You should be able to find the installation files and keys of the two last major versions there.
None of our applications depend on Java Spring or any other Java library and are thus not affected by this vulnerability.
All of our products are being developed in Delphi or C#. Although we use Spring4D(elphi) with some of the components, they are safe to use, because the reported vulnerability applies to Java Spring framework only.
This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.
When installing SmartCallMonitor, you can choose to register it for calling numbers that you click in the browser. The final installation page shows a checkbox for this and is enabled by default.
Check the event log of the Exchange Server Toolbox or the Windows Event Viewer under Windows Logs | Application for the following message:
"The request was aborted: Could not create SSL/TLS secure channel"
If this is present, you can fix the problem this way:
You can now copy the contents of the text box under Options | SSl Encryption Collections into a text document. Append the following keys at the end:
Follow the editing instructions in the right part of the window under "Help".
Then copy the text back into the text box and press "Apply" to save the settings. For the changes to be applied, you must restart the server.
All of our products are being developed in Delphi or C#. Although we use Log4Net with some of the components, they are safe to use, because the reported vulnerability applies to Log4J only.
None of our applications depend on Log4J or any other Java library and are thus not affected by this vulnerability.
This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.
You can register SmartCallMonitor as a phone with your Fritz!Box, and then make phone calls e.g. with a headset. Following steps are necessary:
If the line is not visible, please consider this article: https://knowledgebase.jam-software.com/7520
When SmartCallMonitor suddenly stops to monitor calls, it oftentimes helps to restart the SmartCallMonitor service. You can follow these steps to do so:
Most of the time the problem here is that the operating system does not load all required components fast enough. The following steps may resolve the issue:
Hint: If you want to start and receive calls in the software, refer to the following article instead: https://knowledgebase.jam-software.de/7519
If you want to use call monitoring with a Fritz!Box, follow these steps:
You did not find what you were looking for? Please contact us so we can provide an answer to your question.
Contact Form