Sofia Server, Network, and Software Requirements

Be sure to review the server requirements and configuration to support sofia operation.


  • Sofia can be scaled out or scaled up. Each solution will require a study of the number of tags, platforms, redundancy requirements, performance expectations, business rule applications, and type of configuration (POC/Single Site/Enterprise).  
  • To view, download, or print a PDF version of the sofia prerequisites, click the link at the bottom of the article.
  • For trouble-free sofia installation and tag activation, either uninstall your antivirus/application firewall software or add the sofia installation and tag activator directories to the exceptions list.
  • If the sofia installation fails, manually delete the installation directory before attempting a re-install. If the sofia configuration utility itself fails, contact AiRISTA support for assistance, +1 (844) 816-7127.
Server Requirements
Minimum Hardware

2 Servers for POC  

    • Windows App Server / Windows DB Server
    • Quad Core Xeon 2.4ghz+
    • 16GB Ram
    • 100GB SSD storage)

2 Servers for a production environment*

    • 1 Windows App Server for (Quad Core Xeon 2.4ghz+/16GB Ram/10GB SSD storage)
    • 1 Microsoft SQL DB Server (Base Requirements for SQL/200GB for DB)

* For a large scale installation, as instructed by your AiRISTA representative, you will need a third server (Dual Core/100GB HD/8GB RAM) with Ubuntu Linux to host the Kafka message broker. (Optionally, the third server can run on Windows Application Server.)

Minimum Operating System

    • Windows Server 2016/2019 or newer recommended (2 servers for production)
    • Ubuntu Linux OS 20.04 or newer—only if using Kafka
Required Windows User Accounts

Windows Accounts

    • Account Name: AirAppUser
    • Account Rights:
      • Local rights to run services within windows:
      • Initial system admin rights to SQL server during the installation process
      • Subsequent SQL admin rights on created Databases
    • Account Role:
      • All sofia services will run using this account
      • Administrative activities within the Data Base(s) created by the install
      • Manage IIS functionality
    • Database Server:
      • Temporary SA access to execute sofia installation
      • Optional database installation with scripts (to be provided)
      • Post installation SA access to sofia database
Database Server Requirements

Microsoft SQL Server 2017/2019 or newer
Consult with your Microsoft Professional to acquire this software and to research its licensing requirements.

  • Windows Authentication enabled
  • SQL Management Studio is accessible during the installation


  • Windows SQL Server Express
  • Postgres
OS Requirements for Application Server

Microsoft Roles and Features Add-Ons

  • Microsoft Internet Information Server 7.0 or higher – Windows Role
  • Microsoft .NET Framework 3.5.1 – Windows Feature
  • Microsoft .NET Framework 4.6.1 or newer – Windows Feature

These are the options you should check for the Windows Server Manager roles and features to meet above requirements.


Unsupported OS

  • Windows (non-server version)
  • Mac OS
  • Unix (except as required by Kafka)
Software Requirements for Application Server

Microsoft Downloadable Software

MQTT Requirement: Mosquitto 

MQTT serves as an internal way to send messages and is our recommended solution for single server solutions. Sofia requires the Mosquitto message broker. Download it and install it before starting your sofia installation:


In the rare cases when a multiple-server cluster is necessary to accommodate a larger message load, you will need to install Kafka. Do not need to install Kafka unless it is specifically requested. Your AiRISTA sales engineer will let you know if it is ever necessary. 

Load Balancing and Redundancy

If required, the following guidelines are suggested when implementing sofia as a redundant system.

    • Redundant SQL servers
    • Redundant Kafka servers (not required if running Kafka on App server)
    • Redundant SSRS (if desired)
    • Redundant sofia Application Servers
    • Redundant Hardware load balancers (Examples: Citrix ADC, F5, Radware Alteon)
Request for Sofia License

AiRISTA will create custom licenses for you based on the specific hardware and software characteristics of the server where you plan to install sofia. These characteristics are collectively known as the server profile. You will need to run AiRISTA's downloadable executable, XpertLicenseInfo, to gather the necessary information from your server. 

After running XpertLicenseInfo, you will give the resulting file, XpertLicenseInfo.LIC, to AiRISTA. In turn, AiRISTA will return your custom license files.


Network and Security Requirements
IP Requirements

When creating DHCP scopes for your new devices (tags and gateways), coordinate with your network administrator. In most cases you will have to allocate one IP address per device.

Location enhancement devices, such as BLE Beacons, BGUs, and G3s require IP assignments routable to the sofia application server through Wi-Fi or over ethernet with or without power over ethernet (POE). 

Ports for Cloud-Based Installations

These ports are required to be opened to outbound connections to the cloud-based servers for users and hardware to be able to communicate with the Sofia Application Suite, which includes Hospitality, Contact Tracing, and Staff Safety subscriptions. 

Source Port Protocol  Device Type 
User 80/443 HTTP/S Sofia Web Application
User 82/83 (secure) HTTP/S Staff Safety Portal
User 82/83 (secure) HTTP/S Social Distance/Contact
Tracing Portal
User/Server 2012,
2013 (secure)
TCP Updates to Web Clients/Integrations/Real Time Streaming
Tag 8550, 8660 TCP Tag Firmware Updates
Tag 8552 UDP Tag Location Updates 
Tag 8553 UDP Tag Maintenance 
Software 24099 TCP AiRISTA RTLS Model Acceptor
Hardware 24200 TCP BGU (Beaconing Gateway Unit) BLE messages
Hardware 24889 TCP AoA Reader

UDP/TCP Ports should be OPEN to send and receive communications.

Ports for a Locally Installed Sofia Application Server

These ports are required for the users, hardware, and any installed software to be able to interact with locally installed sofia, including the Hospitality, Contact Tracing, and Staff Safety subscriptions. It is assumed that the firewalls on the applications server are disabled. If they are not, then assume all connections to the server are coming from a remote network and open ports as indicated below on the server or firewalls between the Users, Tags, Hardware, and the Applications server.

Source Port Protocol  Device Type 
User 80/443 HTTP/S Sofia Web Application
User 82/83 HTTP/S Staff Safety Portal (custom)
User 82/83  HTTP/S Social Distance/Contact
Tracing Portal (custom)
Tag 8550 TCP Firmware Updates
Tag 8552 UDP Location Updates
Tag 8553 UDP Maintenance
User/Server 2012, 2013 (secure) TCP Updates to Web Clients and Integrations
Hardware 5084 TCP Passive RFID Reader LLRP Protocol
Hardware 24200 TCP BGU (Beaconing Gateway Unit) BLE messages
Hardware 24889 TCP AoA Reader
Wi-Fi Requirements

Here are the minimal Wi-Fi network requirements to support sofia infrastructure and devices (tags).

In General

  • Wi-Fi frequency – 2.4 GHz, exclusively
  • Wi-Fi specification – IEEE 802.11 b/g/n
  • Security:
    • Preferred: WPA2-AES (Wi-Fi Protected Access 2, Advanced Encryption Standard)
    • Allowed: Unsecured Wi-Fi


  • For security levels beyond WPA2-AES, consult with your AiRISTA representative.
  • Network access requiring web authentication is incompatible with AiRISTA infrastructure and tags. 
Tag Activation

Activating the tracking devices (tags) typically happens after installing sofia. This ensures that sofia can send and receive data to and from the devices. Depending on your arrangements with AiRISTA, you may receive a set of previously activated tags. But if your tags still need activation, you must have these items in place:

  • A router such as the TP-Link AC750 to serve as the tag activator.
  • A computer that allows you to:
    • Set the network type to private.
    • Set a static IP.
    • Disable or uninstall application firewall software.
    • Disable the Windows firewall.
    • Install software. You will need Tag Activator 5, which you may get from your AiRISTA representative.
    • Set a static IP for Tag Activator 5 and the computer hosting it.


To allow for remote assistance, as preferred by AiRISTA, ensure your computer has internet access and the ability for simultaneous Wi-Fi and ethernet connections.  For trouble-free tag activation, either uninstall your antivirus/application firewall software, or add the Tag Activator 5 installation directory to the exceptions list.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.