Limitations

•The PC sign-on application (TurretLoginApp.exe) only supports Windows 10, Windows 11. 64bit OS versions

•When using the LDAP-based authentication from the turret (or soft-turret), the communications between the turret, the TSS and the LDAP directory must be secured using SSL (HTTPS and LDAPS).

•The PC sign-on application does not reflect the real sign-on state of the user on his IPTrade device. In other words, a sign-on or sign-off performed directly on the IPTrade device is not reflected on the application. As if a user is already connected to the target IPTrade device, the user will not be connected. On the other side, the PC sign-on application can't know the real sign-on state and display "Logged in.".

•Any error occurring during the turret authentication is not reflected neither.

•When a logout is requested, if the user currently logged on the turret is different than the requested user (from the PC's currently authenticated user), no logout is performed.

•The autostart at login feature is only set for the user who installed the PC sign-on application. The others users (on the same PC) must start PC sign-on application manually.

•Authenticating on the turret using the PC sign-on application will not work if the application is currently connected to a different TSS than the one the turret is connected to, even if database replication is enabled between the two. This can be caused by a previous failure that forces the turret to switch to the second TSS.

•The PC sign-on application (TurretLoginApp.exe) cannot be used in combination with the FlexPro (i.e. on the same physical machine).

•The PC sign-on application (TurretLoginApp.exe) cannot be used in combination with the FlexCom (i.e. on the same physical machine).

•When using Click to Dial, if the call fails to open or if no user is logged on the turret, the user won't be notified on the PC

•The Turret PC App can only communicate with Netrix using the TSS HTTP API.