Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Description of the Maintenance section in MikoPBX
The Maintenance section of MikoPBX is an interface for managing the technical aspects of the system and ensuring its stable operation. Here, administrators can perform tasks on data backup and recovery, software updates, system status monitoring, and event log management. This section helps maintain the functionality of the telephone system, promptly detect and eliminate possible problems.
The "PBX update" section in MikoPBX is an interface for managing system software updates. Here, administrators can check for new versions, install updates, and view the change history. Regular use of this section ensures that MikoPBX is up-to-date, secure, and stable.
The "System log entries" section in MikoPBX is a tool for monitoring and analyzing the status of the telephone system. Here, administrators can view event logs, check the status of various services and system components, and test connections and calls. Using this section helps to promptly detect and eliminate technical problems, ensuring stable and efficient operation of MikoPBX.
The "Reboot" section in MikoPBX is an interface for securely managing the state of the telephone system via the web interface. Here, administrators can reboot the system to apply new settings or shut it down gracefully for maintenance. Using this section prevents possible errors and ensures stable operation of MikoPBX. In addition, the possibility of rebooting via the console will be discussed.
This article contains step-by-step instructions for updating MikoPBX to a newer version.
Before updating, be sure to back up your PBX settings using the backup module.
Update option from MikoPBX console
Below is an example of a PBX installed on a VirtualBOX virtual machine, updated from version 2023.1.223 to version 2023.2.206. Download the iso image of the required PBX version from the repository.
In VirtualBOX, open the settings of the virtual machine where the PBX is installed. Go to the Storage section. Select the virtual optical drive. Click the icon in the Attributes group, and click Choose Disk File. Select the downloaded PBX iso image. Start the machine.
The console will display the line "The system loaded in Recovery mode".
Select Install / Repair (or press the number 8 on the keyboard) and press Enter.
You need the command "Update to version ****.*.**". Press the number 2 on the keyboard, then press Enter. The update installation will begin. When it is complete, the PBX will reboot.
After the PBX reboots, the message "The system loaded in Recovery mode" will no longer appear, indicating that the PBX has booted from the hard disk and not from the virtual optical drive. The installed update version will be displayed in green at the top.
Description of section functions
The "System Diagnostics" section in MikoPBX is a tool for monitoring and analyzing the status of the telephone system. Using this section helps to promptly detect and eliminate technical problems, ensuring stable and efficient operation of MikoPBX.
Section location: "Maintenance" -> "System log entries"
Contains 3 tabs: Show log, System information, Capturing network packets.
This section allows you to view log files for detailed analysis of PBX operations.
To start, select a file.
Set the lines for the number of lines to fetch.
Set the offset value to shift the selection.
Set the filter by entering a string to be included in the selection.
The following options are available:
Suppose you need to analyze an outgoing call to the number 74952293042.
Select the log file asterisk/verbose.
Set the phone number 74952293042 as the filter.
Set the limit to a sufficient value, such as 2000, to ensure all log entries are included.
In the last line of the log selection, find the identifier:
In this example, the ID = C-0000000f.
Repeat the log query but use the filter C-0000000f this time.
You will receive the entire log of the dialplan process.
The obtained data can be sent to technical support for further assistance.
The tab displays the following information:
Network settings
CPU load
RAM usage
iptables settings
This section allows you to perform a detailed analysis of errors in PBX operation.
You can start capturing network packets passing through the network interface.
To start the process, press the Start button.
Reproduce your issue: make a call or perform an action that causes the error or failure.
Press the Stop and Download button.
The network packets will automatically be saved in the archive MikoPBXLogs_log-tcpdump-XXXXXXXXXX. They should also automatically save in your browser's Downloads folder.
If you cannot find the archive in the Downloads folder, you can connect to the PBX via WinSCP and download it from the /storage/usbdisk1/mikopbx/tmp directory - the file will be log-tcpdump-XXXXXXXXXX.zip.
You can use the search function in WinSCP by entering "log-tcpdump*" in the file name field and specifying the search directory as "/storage"
You can download all system logs accumulated on the PBX. To do this, click the Download All System Logs button.
The system logs will automatically be saved in the archive MikoPBXLogs_log-sys-XXXXXXXXXX.zip. The logs should also automatically save in your browser's Downloads folder. You can also obtain this log archive from the /storage/usbdisk1/mikopbx/tmp directory by connecting to the PBX using WinSCP. The file will be log-sys-XXXXXXXXXX.zip.
Be careful! If there are many calls or heavy network "load" on the PBX, logs can take up a significant amount of disk space.
Other ways to collect logs:
Using an SSH client
Using the Wireshark utility
Using the tcpdump application
Upgrade option for MikoPBX in Docker container
To update the MikoPBX container to the latest version, you can follow these steps in the command line. These steps include stopping the current container, downloading the new version of the image, and running the container with the updated image.
First, you need to properly stop the running container. After stopping the container, you can safely remove it
To launch a new container using the latest image version with the same settings as before, use the following commands:
First, you need to properly stop the running container. After stopping the container, you can safely remove it
The next step is to download the latest MikoPBX image:
An example of the docker-compose.yml file that can be used to update your MikoPBX container through Docker Compose:
Save the contents to a file named docker-compose.yml, make the necessary adjustments, and run the command:
Data: Since data is stored in Docker volumes (mikopbx_cf and mikopbx_storage), it remains untouched during the update, preserving settings and user data.
Environment Variables: Ensure that all necessary environment variables are correctly passed.
Safety: Always create backups of your data before updating.
These steps will help ensure a smooth and safe update of your MikoPBX container.
Update option from the web interface
In some sections of the interface (e.g., Extensions), the current version of MikoPBX is displayed in the lower right corner.
In the PBX web interface, go to Maintenance → PBX update.
If there are newer versions of the PBX available, they will be displayed in the Online updates available table, with the version number in the first field and the list of changes in the second.
We recommend performing updates sequentially without skipping releases.
There are two update options: online update and update using a downloaded img file.
A warning window will appear. Click Upgrade.
The PBX will download and apply the updates, and then reboot.
Please note that this method can also be used to roll back to a previous version.
The img file will start downloading. Wait for the download to complete.
Then click Apply the update, and in the warning window, click Upgrade.
The updates will be applied, and the PBX will reboot upon completion.
Description of section functions
The system shutdown/reboot menu can be found in MikoPBX by clicking on "Reboot" in the "Maintenance" section.
When you open the page, a list of active calls to the PBX will be displayed. The start date of the call is displayed, from whom and to whom the call.
As long as there are active calls, the reboot and shutdown will not be available via the web interface.
Restart the PBX - the command starts restarting the station.
Turn off PBX - completes all processes and disconnects the station.
You can restart the station via the console menu. To do this, select the section "[3] Reboot the system"
If you want to restart the station: press "[1] Reboot MikoPBX"
If you want to turn off the station: press "[2] Shutdown"
The system will reboot.
In case of an emergency restart of the PBX (for example, power outage), it may be necessary to check the disk for errors.
In the PBX console menu, enter the command "[9] Console(Shell)" and press Enter.
System launch the MikoPBX console.
Enter the command reboot. Press Enter.
The system will reboot with a disk check.
Download the selected log as a file .
Refresh the log .
Auto-refresh the log .
Be cautious! If the system is installed on the same disk where call recordings are stored, there may be difficulties with the update.
Updates are downloaded to the PBX and applied immediately. To update this way, click the button for the desired version.
To update using this method, click the button for the desired version.
Then click the button and select the downloaded img file.
