1 of 6

Setup

Monitoring Providers on MikoPBX

When working with telecom service providers, issues may occasionally arise. For example, the provider's server might become unresponsive or unavailable. This article provides a mechanism for notifying the system administrator via email.

To enable notifications, you will need to configure the SMTP client. See instructions in the section "Mail and Notifications".

Create a new "Dialplan Application".

Enter a name (e.g., Blacklist), a short number for the application (e.g., 99), and select "Code Type" - "PHP AGI Script".

Go to the "Program Code" tab:

Insert the following code:

<?php
use MikoPBX\Common\Models\PbxSettings;
use MikoPBX\Common\Models\LanInterfaces;
use MikoPBX\Core\System\Notifications;
use MikoPBX\PBXCoreREST\Lib\SIPStackProcessor;

require_once 'Globals.php';

$result = SIPStackProcessor::callBack(['action' => 'getRegistry']);
$adminMail = null;
$localIP = '';
$message = '';
foreach ($result->data as $provider) {
    if ($provider['state'] !== 'OFF' && $provider['state'] !== 'REGISTERED') {
        if ($adminMail === null) {
            $adminMail = PbxSettings::getValueByKey('SystemNotificationsEmail');
            $interfaces = LanInterfaces::find("disabled='0'");
            foreach ($interfaces as $interface) {
                if (!empty($interface->ipaddr)) {
                    $localIP = $interface->ipaddr;
                    break;
                }
            }
        }
        $message .= "Provider state: {$provider['state']}<br>" . "Url (local): ']} <br><br>";
    }
}

if (!empty($message) && !empty($adminMail)) {
    $notify = new Notifications();
    try {
        $notify->sendMail($adminMail, 'Provider invalid state...', $message);
    } catch (\Throwable $e) {
    }
}

Save the changes and copy the dialplan application identifier from the browser's address bar. It will look like "DIALPLAN-APP-CF967EE0".

Go to System → Customizing System Files and open the file /var/spool/cron/crontabs/root for editing.

Select the mode "Append to the end of the file", and in the black editing field at the bottom, insert the following code:

Adjust the file name according to your dialplan application identifier "DIALPLAN-APP-CF967EE0

*/5 * * * * /usr/bin/php -f /var/lib/asterisk/agi-bin/DIALPLAN-APP-9С060381.php start > /dev/null 2> /dev/null

Save the changes.

You're done!

Reset to factory settings

Method 1

Go to "General Settings" -> "Delete all system settings"

In the input field, paste the text "delete everything", click "Save settings"

Method 2

Open the MikoPBX console menu. Use the keyboard to enter 9 to go to the PBX console.

Enter two commands sequentially:

After executing these commands, MikoPBX will reboot. The login to the web interface takes place with the login (admin) and password (admin) by default.

Fine-tuning the firewall

When publishing a PBX on a public IP address, the task arises to protect the speaker from scanners, pests who are trying to pick up passwords to SIP PBX accounts. If a simple numeric password is set, it will be picked up very quickly, which will cause losses.

For basic protection against scanners, fail2ban must be enabled. Additionally, you can fine-tune the iptables rules.

Go to the "System file customization" section

Go to edit the /etc/firewall_additional file

Set the "Add to end of file" mode, insert the following code:

The added rule allows blocking all incoming requests over the UDP protocol that contain the substring "friendly-scanner"

A more complete example of a set of rules:

This will protect you from most scanners that I mention User-Agent when requesting.

Migrating MikoPBX to Another Server

Option №1

Perform a Backup of your current MikoPBX following .
Install MikoPBX on the new server. Follow the steps in this .
Upload the previously created MikoPBX backup to the new server following .

Option №2

If the data size is large, it's practical to save the backup directly on the target machine. Here's the process:

Install MikoPBX on the new machine.
On the original MikoPBX, set up .
Ensure the connection is via SFTP.
Username and password should be those used for .
Set the Path on the server to "/storage/usbdisk1/mikopbx/backup/".
Wait for the backup to complete.
Shut down the original machine.
On the target machine, perform a .

Option №3

Manual data migration script.

Installation on MDADM RAID1

Preparation

WARNING: All data on the disks will be erased.

Prepare a PC with two disks of the same size.
Boot the machine in LiveCD or LiveUSB mode.
Connect to the machine via SSH.

RAID 1 Assembly

Run the following command in the console to display disk names:

fdisk -l

The disk names will be displayed. In this example, the disk names are:

/dev/sda
/dev/sdb

Clear the superblocks on the disks:

bashCopy codemdadm --zero-superblock --force /dev/sd{b,a}

Clean the old metadata:

bashCopy codewipefs --all --force /dev/sd{b,a}

Create the RAID1 array:

bashCopy codemdadm --create --metadata=0.90 --verbose /dev/md0 -l 1 -n 2 /dev/sd{b,a}

When prompted with "Continue creating array?", confirm by entering "y".
You can now proceed with the installation as per the installation guide. When selecting the disk during installation, choose md0.

Grub

TODO: You may need to modify the grub.cfg file. Otherwise, there is no guarantee that the system will boot if one of the disks fails.