Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Модуль возможно использовать начиная с MikoPBX 2019.04.134.
Разграничение прав доступа к исходящим маршрутам
Установка caller id для исходящего вызова
1. Выполните установку модуля в разделе Управление модулями.
2. Включите модуль и зайдите в его настройки.
3. На основной странице модуля отображается список существующих групп. Сейчас он пустой.
3. На вкладке Cотрудники отображается список всех сотрудников и то, к какой группе они принадлежат. Сейчас они сотрудники не принадлежат ни к какой группе, потому что самих групп еще не создано.
4. Для добавления новой группы нажмите Создать группу сотрудников.
5. На вкладке Настройки группы укажите ее имя и описание**.** Затем нажмите Сохранить.
6. Вы перейдете на вкладку Сотрудники группы. Добавьте в группу необходимых сотрудников.
7. Перейдите на вкладку Правила исходящей маршрутизации и активируйте разрешенные маршруты.
Если все маршруты будут запрещены - то будут позволены только внутренние вызовы.
1. Создайте новую группу Только внутренние (название группы может быть любым).
2. На вкладке Сотрудники группы заполните список сотрудников.
3. На вкладке Правила исходящей маршрутизации отключите все маршруты.
Настройка выполняется аналогично примеру Разрешить сотруднику только внутренние вызовы с тем лишь отличием, что следует запретить только международные маршруты.
Для каждого сотрудника создайте отдельную группу. Укажите разрешенный маршрут.
На вкладке Правила исходящей маршрутизации укажите CallerID для каждого маршрута.
Не каждый провайдер позволяет подменить CallerID. Обычно позволяют использовать только тот номер, который принадлежит организации.
Если необходимо использовать этот функционал, то в настройках провайдера потребуется отключить использование поля fromuser.
This feature allows for the isolation of a group of employees on the PBX:
Employees within the group can only call numbers within their own group
Employees from other groups will not be able to call the isolated group
Number templates related to the group. A group member will be able to call only these numbers
The templates may include digits from 1 to 9 and the symbol X (any digit 1-9)
A group member will be able to dial all numbers that match the template
Examples of templates:
2XX - numbers from 200 to 299
200001 - a specific internal number, such as a queue number
7XXXXXXXXXX - 11-digit numbers for Russia
The module for MikoPBX provides a REST API for creating campaigns for automatic dialing of external numbers:
If there is an available agent, the module dials a phone number from the campaign pool.
When the customer answers, a connection is established with the internal queue number or agent.
If the internal number is busy, the call is automatically terminated."
The module allows creating access groups with specific permissions and assigning these permissions to company employees.
Additionally, the module allows for authentication in MikoPBX using external LDAP/AD services or simply assigning a login and password to each employee.
The module also adds a new tab to the employee settings page, allowing for quick assignment of access groups or password changes directly from their profile card.
Let's consider a few common scenarios for MikoPBX access control:
Create an access group and enable the Group without access restrictions toggle.
Choose the home page that administrators will land on after authentication.
Next, navigate to the "Users" tab of the access group and select the employees who will be granted permission to administer the system.
Create an access group with restricted privileges that grants access only to IVR menu administration.
Next, go to the Setting permissions tab and select only the necessary rights to view and modify existing IVR menus.
Assign the access group to employees who will administer the IVR menus and save the access group.
Create an access group, disable full privileges, and grant access only to the call history section with user filtering.
When selecting this section, an additional tab appears in the module settings, allowing you to configure permissions for viewing and listening to call recordings on a per-employee basis.
You can select various filtering options and employees whose call recordings can be listened to by users within this access group.
The module allows users to be authenticated either with a simple login-password pair or by using an external LDAP authentication server. To configure the connection with the server, navigate to the "Domain Authorization Settings" tab.
Please provide the access parameters to your domain. If necessary, specify the parameters for the organizational unit and the filter for user accounts. Before saving, you can perform a connection data check and retrieve a list of users from the server.
At the end, you can enter user credentials to test the authorization and save the module settings.
Designed to simplify the process of obtaining an SSL certificate for HTTPS. System requirements:
The PBX must have a dedicated domain, for example, sip.test.ru.
The web interface of the PBX must be accessible on the internet (at the time of obtaining the SSL certificate).
The flag "This station is behind a NAT router" must be activated on the PBX.
The "External Host Name of Your Router" must be configured on the PBX. Refer to the network interface settings.
Disable the "Redirect to HTTPS" option in the general settings. The Lets Encrypt server verifies the resource by making an HTTP request to your PBX.
To obtain the certificate, follow these steps:
Go to the "Modules" -> "Extensions and plugins" tab.
Install and enable the "Lets Encrypt Get SSL" module.
Go to the module interface
Perform the "Get/update cert" action:
Note: In version 2020.2.XXX, the backup functionality has been moved to a separate module and is not included in the core package. The module can be installed via the Module Management section.
Go to the "Modules" -> "Marketplace of modules section" tab.
Make sure that the Backup Module is installed and enabled.
Go to the module settings.
Click on "Create backup copy".
Select the data that should be included in the backup:
PBX Settings - all configuration settings of MikoPBX made in the web interface.
Call History - saves the cdr.db database (location: /storage/usbdisk1/mikopbx/astlogs/asterisk/cdr.db). This setting does not save actual call recordings, only the information on the Telephony → Call History (Documentation) tab without playback/download functionality.
Call Recording Files - saves all call recordings in *.mp3 format.
Sound Files - saves sound files uploaded to the PBX in the Telephony → Sound Files (Documentation) section.
Click on "Create a backup".
Once the process is complete, the backup will appear in the list of backups:
In the backup list, you can perform the following actions:
Restore from a backup.
Download the backup archive.
Delete the backup.
The process of upgrading from Askozia 4, 5 ME to MikoPBX is described in this guide.
In the list of backups, select the desired one and click "Restore from backup".
Select the categories of data to restore.
Click on "Restore from a backup".
The restoration process will start, and once completed, the PBX will be rebooted.
The progress of data restoration will be displayed on the current page.
We recommend restoring the data in two stages:
Restore Sound Files, PBX Settings, and Call History.
Restore Call Recording Files - this is the longest stage.
FTP Mode - creates a ZIP archive. For this mode, an FTP server is required.
SFTP Mode - creates an IMG container. This mode only requires MikoPBX.
WebDav Mode - creates an IMG container.
The fastest backup options are SFTP and WebDav. FTP is outdated, and the ability to use this protocol will eventually be removed from the backup module.
Click the "Backup schedule" button to configure automatic backups.
To enable scheduled backups, activate the switch "Scheduled Backup."
Fill in the required information:
Server Address - IP address of MikoPBX or the address of the SFTP \ FTP server.
Port - for SFTP mode, the port is 22. Disabling the "SFTP Mode" switch activates FTP mode with port 21.
Username - the username for server authentication.
Password - the password for server authentication.
Server Path - the directory where the backups will be saved. Recommended directory on MikoPBX: /storage/usbdisk1/mikopbx/backup/.
When using WebDav, the directory in the "Server Path" field must be created manually in advance.
Schedule - specify the day and time for the backup operation.
Keep Last X Versions - specify how many backup versions should be retained.
PBX Settings - all configuration settings of MikoPBX made in the web interface.
Call History - saves the cdr.db database (location: /storage/usbdisk1/mikopbx/astlogs/asterisk/cdr.db). This does not save actual call recordings, only the information on the Telephony → Call History tab without playback/download functionality.
Call Recording Files - saves all call recordings in *.mp3 format.
Sound Files - saves sound files uploaded to the PBX in the Telephony → Sound Files section.
Click "Save."
This module is designed for bidirectional synchronization of employee account data with MikoPBX. The data source is either an Active Directory or LDAP server.
When a new employee is created in the domain, they will automatically be uploaded into MikoPBX, with an available internal number assigned to them. The information about the number will then be sent back to the domain and recorded in the employee's profile. The same will happen with their mobile phone number and photograph. As always, the setup is extremely straightforward.
For each AD/LDAP server, you can specify synchronization settings, departmental filters, or create a custom filter for complex filtering logic.
Next, you need to correctly configure the attributes for synchronizing account data.
During the initial synchronization, the system will match the existing MikoPBX account data with the data obtained from the domain. The following fields are used for matching:
Email address
Employee name
Mobile phone
Internal phone
Before enabling automatic synchronization, it is recommended to test the correctness of the specified attributes by clicking the Run request button.
If all parameters are correctly specified, you will see a list of employees with attributes from the domain. This is a safe request and will not result in changes to the system.
After testing, you can initiate manual or automatic data synchronization.
In the columns "status" and "updated", you can track the current synchronization process.
As of now, the removal of an employee from the domain will not lead to their automatic removal from MikoPBX. The account will be retained until manually deleted by a MikoPBX administrator. This is because there may be various complex call routing scenarios where it's not feasible to simply remove an employee from the call route without replacing them with someone else.