New : with Rainbow release v149, the Softphone user interface can now be forced through a user profile setting.
Behavior description
Before v149, a company administrator was able to allow the end user to activate or not the Softphone UI. He also had the possibility to force this Softphone mode during Desktop application installation using the parameter /ForceSoftphone.
From v149, the Softphone mode is fully controlled by a profile setting that can now be chosen between Allowed / Not Allowed / Forced
Desktop application installation parameter /ForceSoftphone becomes obsolete
Force the Softphone UI for my users already using it
You already have allowed the end user to activate or not the Softphone UI or you forced it with the Desktop application installation parameter. In both cases if the user has the softphone mode active then he will keep it with upgrade to v149.
But from v149 he will also be allowed to disable it even if you forced it with the Desktop application installation parameter. System profile Telephony or Telephony and Rainbow audio will have the profile settings "Use softphone mode" set to Allowed per default.
Therefore if you do not want that the user removes the softphone mode you'll have to create a new user profile where you set the setting Use Softphone mode to Forced. And apply this profile to the users.
Force the Softphone UI for new my users
For new users, simply create a new profile as described above and assign it to the users who should have softphone user interface and should not be allowed to change it.
Specific case Microsoft Teams users
Note: With v149 we have added a new system profile Microsoft Teams telephony only. In this profile the Softphone mode is set to Forced.
If you have Microsoft Teams user we strongly recommend to assign this new profile to these users .
Evolution planned for a future version of Rainbow
We plan to roll out the forced softphone mode in future versions of Rainbow for the Telephony and Telephony and Rainbow audio profiles. A specific announcement will be made when the target version for this change is known.
Stay tuned! follow the Announcements section.