Scroll export button | ||||||||
---|---|---|---|---|---|---|---|---|
|
Info |
---|
The List of custom config parameters that allow changing various settings in config files. Created: August 2018 Updated: March 2024 Permalink: https://wildix.atlassian.net/wiki/x/Fh3OAQ |
Table of Contents |
---|
To make any changes to config files, access them via SSH as root:
...
The option allows overriding of Global Call groups settings (see the chapter below) and saving custom parameters after each system upgrade.
...
Note |
---|
|
Collaboration
Disable file transfer in Collaboration chat messages
...
Change the default Departments tree separator Anchordepartmentsastree departmentsastree
departmentsastree | |
departmentsastree |
Starting from WMS 5.04.20220309.1, the Colleagues tab in Collaboration shows only the list of Departments and there is possibility to create a multilevel hierarchy of Departments and display them in a tree view.
...
Note |
---|
The support starts from WMS 5.04.20220309.1 |
By default, only people added to rosterare shown on the Colleagues tab. To display all users registered on the PBX, add the following line to the /rw2/etc/env.custom.ini file:
...
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
...
Note |
---|
Note: Starting from WMS 6.04.20231020.2, it is possible to manage location-based MFA via WMS -> PBX -> Features. Documentation: WMS Settings Menu - Admin Guide |
Dialplan
Exit code 0 from voicemail
...
Note |
---|
Note: Starting from WMS 5.04.20220309.1, in case you have several streams, modify the parameter [radio] to [radio1], [radio2], etc. in the config file and choose the corresponding option ("radio1", "radio2") when setting music on hold in the Dialplan. |
...
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.
...
Create a directory /etc/systemd/system/pbx-data-engine.service.d
Code Block # mkdir /etc/systemd/system/pbx-data-engine.service.d
Create a file /etc/systemd/system/pbx-data-engine.service.d/override.conf and add the following lines
Code Block # vi /etc/systemd/system/pbx-data-engine.service.d/override.conf [Service] ExecStart= ExecStart=/usr/sbin/pbx_data_engine.py --daemon --mode calls presence -cr
Reload systemd and restart the service to apply the changes
Code Block # systemctl daemon-reload # systemctl restart pbx-data-engine
Run the following command to check what events are sent to Analytics
Code Block echo mode | socat - UNIX-CONNECT:/var/run/data_engine/data_engine.sock
...
Note |
---|
Note: The support starts from WMS 5.04.20220309.1. |
ECM is enabled by default. To disable it, add the following line in /etc/callweaver/res_fax_custom.conf:
...
Note |
---|
Note: The support starts from WMS 5.04.20220309.1. |
Maximum transmission speed
...
Prevent obsolete repeaters from upgrade
Starting from W-AIR firmware v.07.30.xx.xx and higher, old Wildix repeaters are no longer supported and need additional configuration to stay on previous firmwares to continue working. For old repeaters to work, you need to add the following parameter to the /rw2/etc/provision.conf file:
Code Block |
---|
SupportObsoleteRepeater = yes |
The default value is “no”. When the parameter is enabled, the base stations automatically switch to the previous firmware on which the obsolete repeaters are supported (v. 06.xx.xx.xx)
Note |
---|
Note: To differentiate between obsolete and supported repeaters, check out the document How to Identify Obsolete Wildix Repeaters |
...