Customer has always had Sametime premium licenses although not using the meeting features at all. Now we want to do the same with Sametime 12.0.2.
Is there any way to enable premium chat functions (Send files, send screenshots) with the "non-Premium" installation?
Or do we need to use the complete premium install with all its overhead although only sametime chat is used?
Manually editing policies.user.xml and enabling im.3000.label does not help with Sametime 12.0.2 (these features are also greyed out in Sametime admin interface policy editor
ressources are not the issue. The issue is the "visibility" of all of the features to the user that should not be used:
- Default entry for hostname is meeting instead chat (customer has a paid Webex-plan for meetings)
- Possibility to directly start meetings from chat (embedded and webchat)
I know and understand that HCL of course would like the customer to use the complete experience, but this most probably will not happen here... but still they want to use the enhanced chat features
if you use the not-premium installer there are settings within the images (sametime.ini, etc.) that reduce the functionality to limited functions - even if you try to modify the policy with the im.3000.label yourself.
sametime.ini
ST_BRANDING_INFO=entry
IMOnly=1
Maybe you can try to change these parameters within the custom.env, but i am not sure if that works.
I would suggest to install sametime-premium and then you could change the docker-compose.yaml file to reduced container loading (e.g. not meeting or a/v). Maybe the best way is to backup your docker-compose.yaml, .env, custom.env file from a non-premium installation to compare later with the premium installation.
Hi @Alexander Novak , both suggestions sound interesting.
I already thought about reducing the services that are started in docker-compose.yaml, but I will probably have to reconfigure at least the nginx instances as in Premium the "entry point" seems to be served by "jibri-web" container and in standard it is served by the "chat-proxy"...
And as soon as you open the host url without anything you are redirected to meetings in Premium and to webchat in Standard... need to figure out where this happens...
EDIT: I used your second tip and successfully reduced the "Premium" installation to the features of the Standard-Editon by following these steps:
I compared docker-compose.yaml of the Premium with the one of the Standard installation and removed all the services from Premium that are not in Standard (after creating a backup of course
I copied the sametime-config/web/nginx/meet.conf from the "small" installation to the Premium installation to make sure, nginx starts with the correct homepage and only creates the rules for webchat and admin
These two simple steps lets me start Sametime Premium in a "minimalistic, chat only" setup but with premium features enabled.