Software installation and launch

Software installation and launch

Hardware recommendations

Link does not support ARM processors, so it cannot be installed on Mac devices with M-series chips.

 

Software recommendations 

Oracle VM VirtualBox host compatibility:

  • Windows (64-bit): Windows 8.1 to Windows 10 (various builds), Windows Server 2012–2019;

  • macOS (Intel only): 10.13 High Sierra, 10.14 Mojave, 10.15 Catalina — Intel hardware is required;

  • Linux (64-bit): Ubuntu, Debian 9/10, Oracle Linux 6–8, CentOS/RHEL 6–8, Fedora 30/31, Gentoo, SUSE SLES 12/15, openSUSE Leap 15.1 — officially supported Linux distributions only;

  • Oracle Solaris (64-bit): Solaris 11 — with restrictions;

  • For remote installation, you can use SSH or PuTTY.

 

General information

Link runs as a web application and must be installed on a host computer to provide browser-based access.

You can deploy any of the server versions below using Docker (recommended) or Oracle VM VirtualBox.

Choose your Link server setup:

SIP Support

Web Proxy

Recommended For

Protocol

Notes

SIP Support

Web Proxy

Recommended For

Protocol

Notes

No

No

Local networks

HTTP

Basic setup

No

Yes

Public servers

HTTPS

Requires domain config

Yes

No

Linux servers only

HTTP

SIP-enabled (local use)

Yes

Yes

Linux + public

HTTPS

SIP + HTTPS (most advanced)

Basic version includes:

  • Messaging, announcements, polls

  • Remote device configuration

  • Identifier creation/management

  • Guest access

  • Partial elevator module functionality

For advanced features (mobile app, concierge dial service, built-in SIP server, branding, etc.), a license is required.

 

Required ports

  • 5060 TCP/UDP — SIP (unencrypted)

  • 5061 TCP — SIP over TLS

  • 80 TCP — HTTP

  • 443 TCP — HTTPS

  • 6001 TCP — WebSocket

  • 10000–20000 UDP — RTP (audio/video)

  • 1883 TCP — MQTT (unencrypted)

  • 8883 TCP — MQTT (encrypted)

  • 48080 TCP — SIP proxy management

  • 48081 TCP — SIP node management

  • 48089 TCPSIP settings

Ensure outbound access to:

registry-1.docker.io index.docker.io docker.io

 

Installation under Linux using Docker

  1. Install Docker for your distro. The example below uses the installation for Ubuntu.

    # Remove old versions sudo apt-get remove docker docker-engine docker.io containerd runc # Configure the repo ## Update apt index and install dependencies sudo apt-get update sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg \ lsb-release ## Add Docker GPG key curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg ## Add repo echo \ "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null # Install Docker sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io
  2. Install docker-compose for your distro:

    # Download docker-compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Grant execute permission for the file sudo chmod +x /usr/local/bin/docker-compose # Add symlink sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose
  3. Clone the necessary project from our GitHub with the help of command:

    git clone https://github.com/basip/link.git
  4. Create the necessary volumes in advance, with help of the command:    

    docker volume create name

    Name changes depending on the volume name to be created. The list of required volumes (with external: true values) you can find at the end of the docker-compose.yml file.

    install-20240114-224711.png


    So, according to the example, the following commands must be done:

    docker volume create app-data docker volume create app-storage docker volume create system-logs docker volume create app-ssl-certs docker volume create broker-data

     

If you are installing a version with a web proxy:

  1. Copy the env.example file and name this copy as .env.

  2. In the .env file you must enter the following data:

  • your Link server address, e.g. link.bas-ip.com for HTTPS_DOMAIN field;

  • production for HTTPS_MODE field;  

These parameters are required for correct encryption certificates to work.

 

  1. Go to the folder of the version you want to install. For example, for the version with SIP, the command is: 

cd link/with-sip

If you install version without SIP, the command is: 

cd link/without-sip
  1. Run the project.

docker-compose up -d

You can improve the productivity of extensive projects by doing the following Docker configuration: 

Change the userland-proxy attribute to false in the docker configuration /etc/docker/daemon.json file. If there is no such file, then create it with the content

{"userland-proxy": false} 

This completes the installation of the Link server. You have access to the web interface. You can learn more about it in the First authorization and the server initial setup section.

Always perform external backups before any server updates to prevent data loss and mitigate potential disruptions.