User contributions for Gilbertas
From Kolmisoft Wiki
Jump to navigationJump to search
- 07:38, 17 November 2025 diff hist +1 How to change server time zone current
- 07:38, 17 November 2025 diff hist +123 How to change server time zone
- 14:00, 4 November 2025 diff hist +61 How to make several connections from one IP current
- 06:53, 9 October 2025 diff hist +1 MOR API users get current
- 06:52, 9 October 2025 diff hist +172 MOR API users get
- 06:43, 9 October 2025 diff hist −1 MOR API users get
- 06:42, 9 October 2025 diff hist −596 MOR API users get
- 06:42, 9 October 2025 diff hist +653 MOR API users get
- 08:13, 10 September 2025 diff hist 0 File:AccountantPermissions.png Gilbertas uploaded a new version of File:AccountantPermissions.png current
- 08:13, 10 September 2025 diff hist +2 Accountant permissions current
- 08:13, 10 September 2025 diff hist +190 Accountant permissions
- 08:31, 5 September 2025 diff hist +1 Fail2Ban on X18 current
- 08:31, 5 September 2025 diff hist +3 Fail2Ban on X18
- 08:29, 5 September 2025 diff hist +1 Fail2Ban on X18
- 08:29, 5 September 2025 diff hist +255 Fail2Ban on X18
- 08:11, 5 September 2025 diff hist −1,278 Fail2Ban on X18
- 08:10, 5 September 2025 diff hist +6,117 N Fail2Ban on X18 Created page with "=Description= In recent MOR X18 versions, Fail2ban has been reworked. Two main differences: * MOR jails are configured in jail.local, system's global jail.conf is left untouched * Fail2ban default chain changed to '''MOR-FAIL2BAN-JUMP'''. Now, Fail2ban adds chains to MOR-FAIL2BAN-JUMP, and not directly to the INPUT chain. <br><br> =How to modify MOR jails= * /etc/fail2ban/jail.conf contains global fail2ban configuration that is included in fail2ban package, we should..."
- 06:53, 5 September 2025 diff hist +2,178 MOR iptables Chains current
- 09:38, 25 August 2025 diff hist +89 Providers
- 09:35, 25 August 2025 diff hist +13 Providers
- 09:15, 25 August 2025 diff hist +3 M4 Iptables Chains current
- 09:12, 25 August 2025 diff hist +6 M4 Iptables Chains
- 09:11, 25 August 2025 diff hist +2 M4 Iptables Chains
- 09:11, 25 August 2025 diff hist +4 M4 Iptables Chains
- 09:10, 25 August 2025 diff hist +5,428 N M4 Iptables Chains Created page with "=Description= During the switch install/update, M4 automatically creates iptables chains to manage the security of the switch. <br><br> ==Whitelist Chains== There are two types of whitelist chains: Chains that only have ACCEPT statements, to make sure that IPs are always whitelisted. These chains are added at the very top of the INPUT chain, to make sure that IPs are whitelisted: * M2-CONNECT-POINTS-WHITELIST - this chain contains all IP authenticated connection points..."
- 12:54, 25 July 2025 diff hist +1 MOR iptables Chains
- 12:54, 25 July 2025 diff hist +4 MOR iptables Chains
- 12:53, 25 July 2025 diff hist +4 MOR iptables Chains
- 12:53, 25 July 2025 diff hist +2,809 N MOR iptables Chains Created page with "=Description= During the switch install/update, MOR automatically created iptables chains to manage the security of the switch <br><br> ==Whitelist Chains== There are two types of whitelist chains: Chains that only have ACCEPT statements, to make sure that IPs are always whitelisted. These chains are added at the very top of the INPUT chain, to make sure that IPs are whitelisted: * MOR-IPAUTH-WHITELIST - this chain contains all IP authenticated devices/providers from t..."
- 11:51, 30 June 2025 diff hist +11 M4 DID Management
- 11:50, 30 June 2025 diff hist +796 M4 DID Management
- 09:01, 29 May 2025 diff hist −42 M4 Emails
- 09:37, 28 May 2025 diff hist −20 Rate Notifications current
- 14:05, 20 May 2025 diff hist −4 Two SIP listening ports for single Asterisk current
- 12:58, 17 April 2025 diff hist 0 MOR forward Q.850 Reason header current
- 12:58, 17 April 2025 diff hist +41 MOR forward Q.850 Reason header
- 12:57, 17 April 2025 diff hist +1,253 N MOR forward Q.850 Reason header Created page with "= About = By default, MOR does not generate and/or forward Q.850 Reason header == How to enable == Add the following line in /etc/asterisk/sip.conf: use_q850_reason=yes Execute command (this does NOT interrupt calls): asterisk -rx 'sip reload keeprt' == Important == With this setting enabled: * If the Provider does not send Q.850 reason header, Asterisk (MOR) will add this header using internal Asterisk ISDN <--> SIP mapping. * If the Provider sends Q.850 reason h..."
- 09:58, 16 April 2025 diff hist +2 CDR Rerating current
- 09:57, 16 April 2025 diff hist +249 CDR Rerating
- 08:42, 7 March 2025 diff hist +387 M4 Aggregates current
- 13:29, 17 February 2025 diff hist +5 System.conf
- 13:27, 17 February 2025 diff hist +257 System.conf
- 13:09, 7 February 2025 diff hist −1 High Availability Configuration with Pacemaker and Corosync
- 13:07, 7 February 2025 diff hist +108 High Availability Configuration with Pacemaker and Corosync
- 13:04, 7 February 2025 diff hist +1 High Availability Configuration with Pacemaker and Corosync
- 13:04, 7 February 2025 diff hist +3,177 High Availability Configuration with Pacemaker and Corosync
- 12:12, 7 February 2025 diff hist −20 High Availability Configuration with Pacemaker and Corosync
- 12:11, 7 February 2025 diff hist +2 High Availability Configuration with Pacemaker and Corosync
- 12:10, 7 February 2025 diff hist +5 High Availability Configuration with Pacemaker and Corosync
- 12:09, 7 February 2025 diff hist +3,877 High Availability Configuration with Pacemaker and Corosync
