LogoLogo
www.mikopbx.comTelegram communityForum
English
English
  • MikoPBX Manual
    • Quick start
    • Getting to know MikoPBX
    • System requirements
  • Installation
    • Standalone Computer
    • Virtual Machine
      • VMware ESXi
      • VMware Fusion
      • VirtualBOX
      • VMware Workstation Pro
      • Hyper-V
      • Proxmox
    • Cloud
      • AWS
        • AWS deployment guide
        • AWS Marketplace
      • Microsoft Azure
      • Google Cloud
        • Google Cloud deployment guide
        • Google Cloud Marketplace
      • Hetzner cloud (In dev)
      • Digital Ocean
      • Alibaba Cloud
      • Vultr
    • Docker container
      • Docker installation and creating a user and directories
      • Running MikoPBX in a container
      • Running MikoPBX using docker compose
  • User manual
    • Telephony
      • Extensions
      • Call queues
      • IVR Menu
      • Conferences
      • Sound files
      • Call detail records (CDR)
    • Call Routing
      • Telephony providers
      • Incoming routing
      • Outbound routing
      • Night and Holiday Switch
    • Modules
      • Registration in the modules marketplace
      • Module management
      • Application dialplans
    • Maintenance
      • PBX update
        • Updating from the web interface
        • Updating from the MikoPBX console
        • Updating the docker
      • System log entries
      • Reboot
    • Network and Firewall
      • Network interface
      • Firewall
      • Anti brute force
    • System
      • General settings
      • Time Settings
      • Mail settings
        • Setting up E-mail notifications for the Gmail mail service
      • Asterisk Manager Interface(AMI)
      • System files customisation
  • FAQ
    • Setup
      • Installation on MDADM RAID1
      • Fine-tuning the firewall
      • Migrating MikoPBX to Another Server
        • Transfer Using Backup
        • Transfer using scheduled backup (SFTP)
        • Transfer using rsync
      • Reset to factory settings
      • Monitoring Providers on MikoPBX
    • Management
      • Change the login name
      • The extra disk space has run out, the disk size has increased
      • Storing Recordings in a Shared Windows Folder
      • Resetting WEB Interface Credentials
      • Backup Internet and Provider Re-Registration
    • Troubleshooting
      • Connecting to the PBX using SSH
        • Connecting to PBX using SSH client (Putty)
        • Connecting via SSH (Windows)
        • Connecting via SSH (Linux/MacOS)
      • Connecting to a PBX using WinSCP
      • Getting logs using the tcpdump application
      • Capturing Logs from PBX using Wireshark
      • Traffic Analysis Using Sngrep
      • Adjusting the volume
      • Troubleshooting sound problems
      • Jitter Configuration
    • Incoming Routing
      • Choosing a provider when redirecting to a mobile
      • Notification of Employment, Call Waiting
      • Black and white lists
      • Allow additional dialing of the internal number in the queue
      • Output of information about the did number
      • Setting individual non-working hours for a provider account
      • An example of the implementation of a typical route of incoming calls
      • Routing by DID Number
      • Normalization of incoming phone number
      • Basic IVR example
    • Outbound routing
      • Add P-Preferred-Identity and Remote-Party-ID header
      • Conference with a regular external subscriber
      • Outgoing with internal number dialing
      • Remove all special characters from the dialed number
      • Prohibiting calls via a backup route
      • Calls to emergency numbers
      • Number Templates
        • Uniform distribution of outgoing
        • Sample template: calls to another country
        • How to prohibit the replacement of "+" with 00
        • Changing the number prefix from "+345" to "347"
        • Changing the number prefix from "345, 347" to "+345"
        • Removing the area code from the number
        • Adding the prefix "1" to the number
      • Making Calls Through a Specific Provider
    • Scenarios and cases
      • Generate extensions by REST API
      • Missed Call Telegram Notifications
      • Call the company from your mobile and dial an extension to call a third-party company
      • Sending an incoming fax to email
      • Customer's assessment of the quality of service
      • Simulation of external calls
      • Disabling "off-hours" for VIP numbers
      • Registering multiple accounts from one provider
      • Setting up individual non-working hours for several providers on one host
      • Disable forwarding to mobile for internal calls
      • Unique background music for the queue
      • Pause for Queue agent
      • Dynamic Queue Agents
      • Setting up the "Paging" function
      • Limit the number of authorizations per SIP account
      • Call Monitoring (ChanSpy)
      • Conversion of Call History FreePBX -> MikoPBX
      • SSL Certificate for MikoPBX Web Interface from OPNSense
      • Hiding the Caller’s Number from Employees
    • Interconnections
      • Merging two MikoPBX
      • Integration of MikoPBX and Grandstream UCM6202
      • MikoPBX and FreePBX (PJSIP)
      • MikoPBX and FreePBX (IAX)
    • VoIP providers
      • Mango
      • Zadarma
    • Softphones
      • Bria Solo
      • Sessiontalk
      • MicroSIP
      • Groundwire
      • Zoiper
      • Jitsi
      • PhonerLite
      • Linphone (MacOS)
      • Telephone(MacOS)
      • Configuring webRTC client SIMPL5
      • Softphone.pro
      • 3CX Softphone
      • PortSIP
    • IP telefones
      • Snom D120
      • Yealink T19
    • VoIP gateways
      • GoIP4
      • Grandstream HT503
      • Using a Huawei E173 USB Modem for Calls (chan_dongle)
  • Modules
    • MIKO modules
      • for 1C:Enterprise
        • Панель телефонии 4.0 для 1С
        • Панель телефонии 1.0 для 1С
        • Модуль умной маршрутизации
      • Users groups
      • CRM Bitrix24 integration
      • Autoprovision
      • Let's Encrypt
      • Access control management
      • Module auto dialer
      • Backup
      • Synchronization with LDAP/AD
      • Callback module
  • other
    • Changelog
      • MikoPBX 2024.1
      • MikoPBX 2023.2
      • MikoPBX 2023.1.223
Powered by GitBook
On this page
  • Creating a resource group
  • Creating a storage account
  • Configuring the created storage account
  • Creating an image
  • Creating a virtual machine
  • Configuring ports for incoming connections
  • Starting MikoPBX

Was this helpful?

Edit on GitHub
Export as PDF
  1. Installation
  2. Cloud

Microsoft Azure

MikoPBX Installation Guide using Microsoft Azure

Last updated 1 year ago

Was this helpful?

First, log in to the Microsoft Azure portal

Let's proceed with the setup.

For quick and convenient searching on the Azure portal, use the search bar.

Creating a resource group

  1. Open Menu / All services / General / Resource groups

  2. In the Resource groups tab, select Create

  3. Enter the group name, for example MikoPBX_group

  4. Use default values for other fields

  5. After entering the values, click the Review + create button, then the Create button

Creating a storage account

  1. Open Menu / All services / Analyze and transform data / Storage accounts

  2. In the Storage accounts tab, select Create

  3. Specify the created resource group MikoPBX_group

  4. Enter the storage account name, for example pbximgs

  5. Use default values for other fields

  6. After entering the values, click the Review + create button, then the Create button

Configuring the created storage account

  1. Go to the card of the created storage account pbximgs

  2. In the opened tab, go to the Data storage / Containers

  3. Add a new container

  4. Enter the container name, for example imgs

  5. Click the Create button

  1. Open the created container imgs

  2. In the opened tab, select Upload

  3. Select a file from the MikoPBX distribution with the .vhd extension

  4. Click the Upload button

Creating an image

  1. Open Menu / All services / Compute / Images

  2. In the Images tab, select Create, let's create a new image based on the uploaded *.vhd file

  3. Specify the resource group MikoPBX_group

  4. Enter a unique name for the image, for example MikoPBX_Azure

  1. Specify the OS type - Linux

  2. Specify the generation of virtual machines - Gen 1

  3. Select the blob storage object by clicking Browse, Browse / pbximgs / imgs / *.vhd

  4. Specify the account type - Standard HDD

  5. Use default values for other fields

  6. After entering the values, click the Review + create button, then the Create button

Creating a virtual machine

  1. Open Menu / All services / Compute / Virtual machines

  2. In the Virtual machines tab, select Create / Azure virtual machine

  3. Specify the resource group MikoPBX_group

  4. Enter the virtual machine name, for example MikoPBX-vm

  1. Choose the previously created image, See all images / Other items / My images / MikoPBX_Azure

  2. Specify the machine size (combination of CPU / RAM to be at least 1GB / HDD parameters)

  1. Specify the username for the administrator account

If you have an SSH key, do the following

  1. Select the source of the SSH public key - Use existing public key

  2. Specify it in the SSH public key field

If you do not have an SSH key, do the following

  1. Select the source of the SSH public key - Generate new key pair

  2. Specify the key pair name, for example mikopbx_key

Continue with the following instructions:

  1. In the license type field, specify Other

  2. Use default values for the other fields

To deploy the PBX use two disks:

  • A 1 Gb disk for the main system

  • A 50+ Gb disk for storing call recordings

  1. Go to the Disks tab

  2. Specify the OS disk type

  3. Check the Delete with VM checkbox

  1. Create a new data disk

  2. Specify the disk size to be at least 50GB

  3. Use default values for the other fields, click OK

  1. After entering the values, click the Review + create button, then click Create

Configuring ports for incoming connections

  1. Open the virtual machine you created and go to Networking / Network settings / Rules

  2. In the tab, choose Create inbound port rule

  3. Specify the destination port ranges - 0 - 65535

  4. Choose the protocol TCP

  1. Specify a name, for example TCP

  2. Use default values for the other fields

  3. After entering the values, click the Add button

  1. Similarly, create a rule for UDP. Specify the destination port ranges - 0 - 65535, protocol UDP, and name

Make sure to configure the Firewall on the MikoPBX

Starting MikoPBX

  1. Open the virtual machine you created and go to the Connect section

  2. In the drop-down menu under More ways to connect, select Serial console

  1. Copy the external address of the created virtual machine and enter it in the browser's address bar

  2. For login use the login and password provided in Serial console

https://portal.azure.com/