| Html |
|---|
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script> |
...
| Info |
|---|
The List of custom config parameters that allow changing various settings in config files. Created: August 2018 Updated: October 2021 Permalink: https://confluence.wildix.com/x/0AiIAQ |
| Table of Contents |
|---|
To make any changes to config files, access them via SSH as root:
...
| Note |
|---|
|
Collaboration
Disable file transfer in Collaboration chat messages
...
| Code Block |
|---|
COLLABORATION_FILE_TRANSFER_ALLOW=false |
Disable Chat and Post-It functionality in Collaboration
| Note |
|---|
The support starts from WMS 5.03. |
This feature disables access to Chat and Post-It functionality throughout Collaboration. It removes the Chat tab and disables Chat and Post-It options in Colleagues, Fn keys, History tabs, as well as in Search and via Add button. With disabled chats, users also don't receive Kite chat requests.
...
| Code Block |
|---|
COLLABORATION_CHAT_ALLOW=false |
| Note |
|---|
Use case: This feature is useful for teams4Wildix integration, as long as Microsoft Teams offers its own chat. Disabling chat functionality in Collaboration helps users to avoid confusion between these two systems and use one chat instead of two. |
Enable Call Control mode for the second opened Collaboration tab Anchor callcontrolmode callcontrolmode
| callcontrolmode | |
| callcontrolmode |
| Note |
|---|
The support starts from WMS 5.03. |
...
By default, only 1 active Collaboration session is permitted. However, there is an option to allow the second Collaboration tab – in Call Control mode. This can be used, for example, for media devices when connecting via remote desktop. . The option is particularly practical for teams4Wildix integration.
To activate this feature, add the following line to the file/rw2/etc/env.custom.ini:
...
Once the feature is activated, an additional option appears on the Collaboration login window – Call Control only. Tick this checkbox off to log into Collaboration in Call Control mode.
| Note |
|---|
Use Use case: User can set "Call control only" mode to be automatically enabled by adding a parameter in the URI (useful when it is needed to share the link among all employees or bookmark the page) How-to: add ?sip=no to PBX domain name ->https://pbxname.wildixin.com/collaboration/?sip=no |
| Note |
Note: Starting from WMS Beta v. 5.04.20211026.2, for users running Collaboration inside MS Teams, Call Control mode is enabled by default, without the need to edit the /rw2/etc/env.custom.ini file. |
Devices
Modify devices sync
...
| Note |
|---|
Supported devices:
|
...
The option allows setting a specific GSM gateway for SMS sending for each separate user:
Edit the config file /etc/wildix/smsd-route.conf by specifying user extension and MAC address of GSM gateway, for example:
Code Block 101,9c7533014b00 102,9c7533014b00 103,9c7533014b00 104,9c7533014b01
...
Create a new config file template.conf including GTM ID in the file /rw2/etc/pbx/, for example, use the command:
Code Block echo 'gtm=GTM-12345678' > template.conf
where 123445678 is Google Tag Manager ID.
...