Skip to main content

How can we help?

Frequently searched: Android devices, cloning, ADC Gallery, Glossary,...

CTNode-OLD

In this article

    CTNode 10.4.5

    Version 10.4.5.3 (20/04/2017)

    • Fixed problem in setups while comparing versions which could cause e.g. v10 to be considered older than v2.7. This fix applies to CTArchitect, CTNode, GlobalCCA and WebProd setups, and was first seen on MDAC prerequisite check.
    • Fixed wrong threshold value for FileCache syncing in logging: this was previously increased from 15MB to 50MB, but the logging still mentioned 15 MB.
    • Fixed automatic creation of registry key MaximumFileCacheSyncSizeMB, which was not created when it doesn't exist.
    • Fixed some problems with Microsoft Visual C++ Redistributable in setups:
      • When installing Microsoft Visual C++ Redistributable, in most cases multiple versions within the same track were installed. E.g. when installing Microsoft Visual C++ 2015 v14.0.24215, v14.0.24212 was also installed. This bug applies to Microsoft Visual C++ 2008 up till 2015. Except for the unneeded installation, there is no impact.
      • Updated version-check of Microsoft Visual C++ 2015 Redistributable (both 32-bit and 64-bit), according to a new recommendation of Microsoft. This fixes problems when running the installer on systems where Microsoft Visual C++ 2017 Redistributable (14.10.x) or some versions of TFS testing framework are already installed. An error message box is displayed (errorcode 0x666 or 0x80070666), after which the setup continuous.

    Version 10.4.5.2 (23/03/2017)

    • Updated behavior of the Emergency exit (red hand) to gracefully close the connection with CTArchitect, as happens with the Close (X) system button on the window title bar.
    • Fixed startup problems with CTWatch because the packaged Visual C++ runtime is 2015 (vc14) and CTWatch was built with Visual Studio 2013 (vc12). CTWatch is now also built with Visual Studio 2015 (vc14). This is a fake release of CTArchitect to allow identification of the new setup containing the updated CTWatch. CTArchitect 10.4.5.3 and 10.4.5.2 are identical.
    • Fixed problem during setup, resulting in missing icons (start menu, autostart user and autostart system) when upgrading from 5.3.x. Before 5.4.0, CTNode was called HWClient, and during the upgrade, the file HWClient.lnk was searched instead of Hardware Client.lnk.

    Version 10.4.5.1 (09/02/2017)

    • Added support for SIP Session timers (RFC 4028).

      • Session timers are an extension to SIP:

        • they prevent infinite calls (e.g. after a server is restarted without closing existing sessions first).
        • they keep firewall hole punching "open".

      • Current implementation:

        • the minimum expiration timeout is 90 seconds. Smaller expiration intervals are rejected with a response code 422 "Session Interval Too Small".
        • the proposed default expiration timeout is 1800 seconds.
        • the refreshing is done by sending re-INVITEs. For incoming requests, both UPDATEs and re-INVITEs are supported.
        • the refresher is choosen by the UAS (the party receiving the INVITE). When HMP is UAS, it chooses the refresher as the one proposed by the UAC (the party sending the INVITE), or himself if no refresher was proposed. When HMP is UAC, it is not proposing a refresher.

      • This feature is disabled by default, and can be enabled by setting this registry key to 1 (DWORD): HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\MI4C\CTArchitect\HMP1_SessionTimersEnabled

      • Even when remote side doesn't actively support Session Timers, this feature can be useful: when the remote side doesn't support Session Timers, the local side (HMP) will be the refresher, using the default expiration timeout. The remote party will respond to the re-INVITEs as specified by SIP (RFC 3261).

      • Possible future development is the configuration of: default refresh interval, minimum refresh interval, refresher selection preference, ...

      • Further details can be found in topic "SIP Session Timer" in HMP 3.0 Release Update .

    • Fixed continuous reboots of CTNode when no CTArchitect is connecting to the CTNode. By design, CTWatch is rebooting the machine when no CTNode is not connected with CTArchitect for more than 10 minutes after CTNode was succesfully connected with CTArchitect. Due to a bug, CTWatch could trigger a reboot shortly after startup if a time-change of more than 2 seconds happens (e.g. because mismatch between hypervisor & domain time). This message is seen in CTNode logging when this happens:
      WARNING: Notifying CTWatch disabled: More than 10 minutes no connection to Central CTArchitect anymore.

    • Fixed startup parameters of CTNode when starting as service (Setups).

    • Changed service display name from CTArchitect HWClient Service to CTArchitect CTNode Service. The service. The service name has been updated from HWClient to CTNode.

    • All fixes up to 10.4.4.1.