Use cases

Selected use cases on how Radiator can be used – check out more from our blog


The authentication proxy in Radiator GBA/BSF Pack is used to authenticate and proxy the Ut interface which is used for supplementary services configuration with VoLTE devices. Gregory Wille

Proximus Belgium

Radiator two-factor authentication

Modern services all around the internet offer different two-factor authentication solutions. They provide stronger security than using only username and password. Two-factor authentication requires a combination of something the user knows and something the user possesses. One common combination is the username and PIN or password with a physical token, such as a specific device, smart card, or mobile phone. The two-factor secured service may range from a web service to a network device to a remote VPN (Virtual Private Network) access – wherever stronger security is needed. The VPN devices can authenticate remote employees, the network devices can authorise administrators, and the web services can identify the users with secure two-factor authentication.

All you need is Radiator-based two-factor AAA service and a free mobile phone app, such as Google Authenticator, Microsoft Authenticator, or some other OTP/TOTP/HOTP app. The authenticator app is paired with Radiator two-factor AAA service and particular user credentials, and two-factor authentication are ready to be used. Radiator can combine complementary AAA information and functions from Active Directory, LDAP, and even 3rd party two-factor services, such as RSA SecurID, YubiKey, Duo Security, and Vasco Digipass. It can check existence and validity of a user from Active Directory, retrieve a proper VPN group, perform two-factor authentication using TOTP (Time-based One-time Password Algorithm), and then combine the results to a RADIUS authentication and authorisation response, which is sent back to a Cisco ASA VPN device.

More details in our blog

Hotel management systems

One of the widely seen use cases for Radiator is interoperating with different hotel property management systems (PMS). Radiator is used between the hotel’s PMS and the network equipment that controls internet access in hotel rooms. One of the commonly used systems is Micros Opera that is used by both independent hotels and hotel chains. Many hotels require guests to log in with their name and room number. Radiator then gives access based on customer information it has received from Opera. However, Radiator support is not limited to Opera: it supports any PMS that provides a FIAS interface.

In addition to simply offering unpoliced, complimentary internet access, Radiator provides you more advanced options for revenue generating services. Radiator can, for example, give policy instructions, such as the speed given to the customer – based on the price customer is willing to pay for the internet access. Also, Radiator can pass information to network equipment (such as Mikrotik controllers) about how long the customer can use the internet with their current login without having go through the login process again.

More details in our blog


Radiator Software’s experts have contributed to eduroam* development since 2002. In Finland, Radiator Software provides federation top-level RADIUS service for CSC and Funet since 2003. Radiator Software currently serves over 50% of the top 250 universities in the world, many of them members of eduroam.

Most of the major universities in Finland are Radiator Software’s customers that have Radiator-based eduroam RADIUS solution.  We in Radiator Software deliver both products and services for turn-key deployment of eduroam – like we have provided for many customers since 2003.

*) eduroam (education roaming) is the secure, world-wide roaming access service developed for the international research and education community.

VoWiFi (Voice over Wi-Fi)

Since Wi-Fi calling (VoWiFi) has been introduced into the market, operators have been increasing their indoor coverage to provide better voice coverage to their subscribers and offer new voice models both domestic and roaming. With the new generation devices and automatic SIM authentication, end users will not have to consider if they are connected to a LTE or a Wi-Fi network. In addition to better indoor coverage, VoWiFi brings also other benefits to operators. These benefits include getting back the revenues and control of the calls from the OTT players. Wi-Fi is also a low-cost solution to enhance voice service coverage and at the same time offload traffic from the core network.

Radiator products provide the essential components for the VoWifi authentication. For our customers, VoWiFi authentication is done with our Radiator SIM Pack that includes 3GPP AAA Server – providing all the interfaces for 3GPP and non-3GPP authentication. When combined with Radiator Telco Pack Diameter support for policy control and authentication, your network will be ready for Wi-Fi calling. Radiator integrates with all your evolved packet core and Wi-Fi network elements via 3GPP interfaces.

More details in our blog

Going cloud native with Radiator VNF

Nowadays many telcos target their packet core architecture at a cloud-native implementation, which is deployed in their own virtual infrastructure environment. In this environment, all different network functions, such as AAA, are virtualised. This infrastructure supports all services (data, voice, IoT, and so on) and all wireless access technologies including WiFi, LTE, and 5G. Also the data plan and control plan are fully separated. They are likely to follow different deployment models, such as centralised control plan and session management or distributed data plan. Radiator VNF is an ideal solution for this kind of approach and migration to cloud-native infrastructure.

Radiator VNF components and virtual hosts are configured automatically through a centralised configuration system. In addition to this, all VNF components interact using the redundant message queue. Cloud-native approach is also seen in load balancers to ensure that you always have the right amount of AAA capacity in your cloud-native network. For transition to Radiator VNF from a AAA solution, it can be run on a cloud-native infrastructure, such as Openstack. The other alternative is to run Radiator VNF with a static configuration on VMs. In that case, all the components can be implemented, such as load balancers developed for Radiator VNF, but options in scaling and automatic configuration are more limited. They emerge when the infrastructure is transformed to be cloud-native. Our licensing options and Radiator deployments support both approaches.

More details in our blog