Migrating Netrix Voice Recorder Configuration from BT Trade 9.3

SUID

In 9.3 by default Netrix sent “firstname space lastname” as the SUID to the Voice Recorder.

Since “firstname space lastname” is not unique, in 9.4 the default was changed to send the “userID”

To revert  to the 9.3 behaviour, one of the following must be set to true;

•the turret boot setting ‘application.global.recorder.userNameInSUID’

•the user profile setting ‘profile.setting.recording.userNameInSUID’

Note that for Veba, if it doesn’t’ recognise the SUID, it replies with a destination (“IN”) address for the RTP as 0.0.0.0. Netrix sees this destination address as invalid, and hence closes the connection to the VR – and displays the red banner (and after a short period retries to connect)