When a user signs in through RCDevs OpenOTP, the one-time code is sent by SMS through SMSEagle, your own hardware SMS gateway. The request stays in your local network, with no cloud SMS provider.
OpenOTP’s SMS hub normally routes codes through a cloud SMSC. The SMSEagle plugin keeps the request on your local network and sends the code from your own device over the cellular network.
Cloud SMSC delivery needs outbound internet access from your OpenOTP server. SMSEagle sends messages on-premises over its own cellular connection, delivering OTP codes even in fully offline installations.
Cloud SMSC delivery is billed per message, often at premium authentication rates. SMSEagle sends over a standard SIM at local carrier rates – no per-message fees, no external contract.
A user authenticates against an application protected by RCDevs OpenOTP and requests an SMS one-time password.
OpenOTP’s SMS hub calls the SMSEagle plugin (Custom1) with the user’s phone number and the generated OTP code.
SMSEagle delivers the code over its own cellular connection, not through a third-party service, as an SMS to the user’s own phone.
Copy the SMSEagle script to OpenOTP and select it as the SMS gateway, and codes are sent by SMS.
An SMS code needs no app: people receive it on any mobile phone.
SMSEagle records every code it sends, together with its status, so you can check whether it was received.
Two SMSEagle devices can work as an HA cluster: if one fails, the other takes over sending codes.
Configure it with:
You also have to set SMS as the OTP token for every user in the MFA application:
SMSEagle is a hardware & software solution that guarantees a swift delivery of your messages to designated recipients, whether it’s for notifications, alerts, or important updates.
After registering to a demo you get a remote access to our physical device NXS-9750.
