Release Note SourceTech Presence Service — 24 januari, 2018

Release Note SourceTech Presence Service

presence-serviceIt has come to our attention that in major upgrades for Windows 10 the Product Key ID is changed. This ID is a part of the algorithm used for generating the Installation ID, that is then used when generating a licenses for our products. Due to this, a major upgrade for Windows 10 will result in the license to be invalid (since the Installation ID which the license is generated with differs from the Installation ID of the machine).

As a consequence to this we have removed the use of the Product Key ID when generating the Installation ID.

SourceTech Presence Service >= validates license both with and without the Product ID. With this change a license generated for <= (found in a existing installation) will still be considered to be valid until the Product ID is changed again.
A license that is generated based on the Installation ID in Presence Service >= will not be affected by future changes of the Product Key ID, since this is removed from the algorithm.

We recommend that licenses is regenerated when upgrading to SourceTech Presence Service =>

Important information regarding new release — 12 december, 2017

Important information regarding new release

SourceTech JeraFor release of Tellus PAM, Tellus WebApps, TellusVoice and Cloud Services

Some changes has been made in Tellus Hub, this in the client part of the application. The Hub client are used by every application that connects to the Hub server. For Tellus to have the expected functionality, all applications must use the new Hub client.

This means that if one or some of the application should be upgraded in a Tellus system*, all of the application mentioned above should be upgraded to latest version.

* We recommend all to upgrade Tellus WebApps if Tellus Voice is installed and the system is currently running the faulting version of Tellus WebApps Read the release note for Tellus WebApps here.

Problems with Tellus Web — 20 oktober, 2017

Problems with Tellus Web


This is some important information regarding SourceTech Tellus WebApps, our latest released Tellus Web.

We have found a problem in this version, that is only affected when SourceTech Tellus is used with SourceTech Tellus Voice.

When Tellus Web makes a request for Tellus Voice and it’s settings Tellus API makes a lot of request. This results in TellusVoiceAPIAppPool to increases it’s use of memory, and using a lot more memory then it should.  If the machine dosen’t have sufficient memory the server becomes slow.
This can have major effects to the Tellus system, resulting in problems for applications/functions to work as expected.

The problem dosen’t have to occur at a customer just becuase they are running the faulting version, it depends on the machine amount of memory accordingly to the size of the Tellus system. If you have any questions feel free to contact us.

We are currently investigating the problem and will fix it as soon as possible. The version is removed from Downloads and we don’t recommend an upgrade to this version.



Important information regarding Tellus Voice and packages for Spoken Absence and Polling — 22 juni, 2017

Important information regarding Tellus Voice and packages for Spoken Absence and Polling


We have some important information regarding Tellus Voice and the packages for Tellus Voice compatible with the version
!This should be read and taking into account before installing at customer site!

When TellusVoice DB is created and the database migration has been applied, a pre-set with the vxml script that Tellus Voice uses is installed in the database. When the package Tellus Voice – Spoken Absence and Tellus Voice – Polling is downloaded and installed by Cloud Services, all scripts that are considered to be system scripts will be updated with the new scripts.tellus-cloud

If a scripts is set as a none system script this will not be updated.

An early problem with Tellus Voice was that the scripts installed in the database (with the database migrations) was not set as system scripts. This has resulted in a problem where scripts, that infact, are system scripts hasn’t been updated.
What we have done in Tellus Voice and the packages Tellus Voice – Spoken Absence and Tellus Voice – Polling is to change, temporarily, the behaviour of scripts.

When installing the new packages for Spoken Absence and Polling all scripts in the database will be overwritten, regardless if they are system scripts or not. The new scripts are, as it should, marked as system scripts after the installation, which means that the problem of update of scripts will not exists in future versions.

This change will not cause any problem if the customer uses the default scripts and haven’t made any alterations in the scripts. If alterations has been made for the customer, some adjustments needs to be done when before installing. The altered scripts can be copied from TellusVoiceDB before installing and then be applied again after the installation. If there are any hesitation regarding what needs to be done, feel free to contact us.

We recommend that all customers upgrade to Tellus Voice and download the packages Tellus Voice – Spoken Absence, Tellus Voice – Polling and LangPacks for installed languages.

Release notes with information regarding version of packages and changes can be read here.