Today we’re announcing the next chapter for Auron Software.
In this article we’ll explain what is changing and what that means for existing customers.
Auron SMS Server is now Auron Omni
For the last decade our flagship product has been the Auron SMS Server. In the last five years, it has been joined by the Auron Workflow and Integration Server (WISe).
While Auron SMS Server focused on instant messaging integration, WISe provided a robust message bus for industrial environments.
Over time, both products increasingly overlapped in practice.
Auron Omni brings both platforms together into a single unified solution for messaging, workflow automation, and systems integration.
New license tiers
With the introduction of Auron Omni we’re also simplifying our licensing model.
Existing SMS Server and WISe licenses map to the following Auron Omni tiers:
- Auron SMS Server Standard -> Auron Omni Starter
For smaller companies doing low message volumes. - Auron SMS Server Professional -> Auron Omni Scale
For smaller companies doing higher message volumes. - Auron SMS Server SMS Center -> Auron Omni Professional
Processing high volumes with exceptional reliability. - Auron WISe -> Auron Omni Enterprise
Exceptional reliability with full customisation options.
Moving from perpetual to subscription licenses
Auron Omni is now offered exclusively through subscription licensing.
We believe modern infrastructure software should continuously improve through regular updates, security improvements, and ongoing support.
Moving to a subscription model allows us to:
- Deliver updates more frequently
- Respond faster to customer feedback
- Improve long-term reliability
- Sustainably invest in the platform
A new generation model
Alongside Auron Omni, we’re also introducing a new generation-based versioning model.
Previous Auron releases used year-based version numbers such as 2024R2. Going forward, Auron Omni releases will instead be grouped by platform generation, beginning with Auron Omni G1.
G1 represents the foundation of the unified Auron Omni platform and the next generation of Auron messaging and integration software.
Within a generation, customers can expect continuous improvements, feature updates, and reliability enhancements delivered through regular releases.
Existing SMS Server customers
Customers with active maintenance may upgrade to Omni at any time.
The upgrade process is designed to be seamless and compatible with existing SMS Server configurations.
Please note that Auron Omni uses subscription licensing. Unlike perpetual SMS Server licenses, continued operation requires an active Auron Omni subscription.
In addition, existing SMS Server customers may renew their maintenance for one additional year, through May 2027. Beyond this, existing customers with active maintenance will receive transitional pricing options for Auron Omni during the migration period.
Existing WISe customers
Existing WISe customers will benefit from lower renewal pricing under the new Auron Omni licensing model.
Please contact our team to schedule an in-place upgrade to Auron Omni.
SMS and Email Components
We’re also changing our focus regarding the standalone Auron SMS and Email Components.
Over time we’ve seen most customers move away from low-level libraries in favor of more integrated server-based solutions. Because of that, we will no longer actively market these standalone components to new customers.
Existing customers will continue to receive support, maintenance, and updates.
In addition, both components will remain part of the Auron Omni platform for the foreseeable future.
Looking ahead
Auron Omni represents a major step forward for our platform.
By bringing messaging, workflow automation, and integration together into a single product, we can deliver a more unified experience and continue building the tools our customers rely on every day.
Over the coming years we’ll continue investing in the platform with a strong focus on reliability, modern integration capabilities and usability.
We’re excited about what comes next, and we’re grateful to all of our customers who helped shape this direction!
This month marks 10 years since Auron Software was founded. Over that time, Auron SMS Server has become a stable and widely used framework for SMS and WhatsApp communication, while Auron WISe has evolved as a complementary solution for advanced workflow and integration scenarios.
We are now taking the next step.
We are actively developing the next generation of our platform, designed to unify these capabilities into a single, modern, and scalable system.
This new platform, Auron Omni, will serve as the successor to both Auron SMS Server and Auron WISe, consolidating their core functionality into one integrated platform while maintaining compatibility with existing implementations.
In all cases we’ll ensure that migration is possible without requiring changes to existing applications.
Our goal is straightforward:
to ensure long-term stability for existing users while providing a clearer and more future-ready foundation for new deployments.
In the coming period, we will share more details about the transition path, migration approach, and availability for existing customers.
If you are currently using Auron SMS Server or the Auron WISe in production, no immediate action is required. Your system remains fully supported.
We will guide all customers through the transition in a structured and predictable way.
Auron Software announces Auron E-Mail Component 6.4, a powerful API that helps developers add e-mail features quickly. This release improves Unicode support, enhances examples, and more.
First, version 6.4 adds full Unicode support for the To, From, CC, and BCC headers. International characters now display correctly in all e-mails. BCC headers are stored in MIME files but excluded when sending, preventing accidental recipient disclosure.
In addition, we’ve fixed sporadic OAuth2 token refresh problems, improving reliability with modern e-mail services. All C# and VB examples for IMAP, SMTP, and POP3 are updated to show real-world usage. API documentation now includes PowerShell and C# examples throughout, making it easier to implement e-mail features on multiple platforms.
All tooling is verified for Windows 2025, ensuring smooth operation on the latest platform. Find out more in the release notes.
All Auron Email Component examples are available on GitHub:
https://github.com/Auron-Software/AxEmail-Examples
You can download the trial version of the Auron Email Component from the Auron Software website in the download section:
https://www.auronsoftware.com/download/
The trial is also available via NuGet for easy integration into your projects:
https://www.nuget.org/packages/AxEmail
Version 6.4 makes building Email solutions even simpler and more reliable. Please don’t hesitate to contact us with any questions.
SMS is a core building block in many business processes. Companies use it for alerts and notifications. For two-factor authentication and verification. For system monitoring, status updates, and simple machine-to-person messaging. The Auron SMS Component is designed to handle these scenarios reliably, whether you connect through a GSM modem, an Android device, or an SMPP or HTTPS gateway.
Today we release Auron SMS Component version 7.3.
This release focuses on usability, tooling, and platform support. The most notable improvement is the update of our freeware tools SendSMS and SendSMSGui. Both tools now support the Auron SMS Agent for Android, making it easier than ever to send SMS messages through an Android device or phone.
SendSMSGui and SendSMS are closely related. SendSMSGui is an interactive testing tool. You use it to send an SMS through a modem or Android device. It helps you verify settings, connections, and message delivery. At the same time, SendSMSGui automatically generates the correct command line for the SendSMS command-line tool. You can simply copy and paste this command into your Command Prompt or PowerShell script. This makes it easy to move from testing to automation.
In addition to the tooling updates, version 7.3 includes several bug fixes. The example code is modernized and aligned with current development practices. All tooling is verified for Windows 2025, ensuring smooth operation on the latest platform. Find out more in the release notes.
All Auron SMS Component examples are available on GitHub:
https://github.com/Auron-Software/AxSms-Examples
You can download the trial version of the Auron SMS Component from the Auron Software website in the download section:
https://www.auronsoftware.com/download/
The trial is also available via NuGet for easy integration into your projects:
https://www.nuget.org/packages/AxSms
Version 7.3 makes building SMS solutions even simpler and more reliable. Please don’t hesitate to contact us with any questions.
The Auron WISe (Workflow and Integration Server) is our MES middleware solution for industrial automation. Its primary role is to serve as a messaging backbone within MES environments.
Typical applications include:
- Tracking and tracing the flow of goods and raw materials
- Order explosion. customer orders from the ERP system are ‘exploded’ into sub-orders for different batch-areas or machines in your plant.
- Integrations with ERP, LIMS, WMS or other third party systems.
- OT-to-cloud data pipelines, push factory-floor telemetry into your cloud-based data lake.
The WISe is suitable for any type of application that would benefit from:
- An advanced low-code message bus
- Zero downtime when adding or change functionality
- Fully traceable, synchronized, and reproducible operations.
The WISe is built on the proven messaging engine of the Auron SMS Server, already a well-known name in telecom and communications.
One of the key differences between WISe and the Auron SMS Server is WISe’s ability to define custom channel types and custom message types, providing a greater flexibility to complex industrial environments.
Custom channel types
The primary concepts in WISe are, like in the Auron SMS Server, channels, messages and triggers. Channels connect WISe to the outside world by sending and receiving messages. Triggers filter these messages and process any that match their conditions.
The ability to create custom channels is one of WISe’s most powerful features. It supports the core WISe philosophy of giving engineers the flexibility to adapt integrations to any environment. Instead of forcing a predefined approach, WISe provides the tools to implement exactly what your processes require.
WISe includes a range of general-purpose channels out of the box, such as HTTP API, file, and database integration channels, among others. However, every plant has machines, situations, or concepts that are unique, often with their own business logic or proprietary protocols. In these cases, you need the ability to create your own custom channel.
A custom channel doesn’t have to be just a custom definition, it can also have a custom user interface to setup and configure the channel and a custom process that holds all your business logic.
Custom Message Types
A message in WISe can also be viewed as an event, since both the ‘to’ and ‘from’ addresses are optional and fully customizable.
Custom message types can include any number of fields, as well as binary attachments. The WISe Manager allows you to create, inspect, and manage these custom messages. Additionally, you can develop a custom interface to edit and send your message types, tailored to your specific needs.
This flexibility enables WISe to handle a wide variety of messaging scenarios, from simple notifications to complex data exchanges between machines, systems, and applications. By defining your own message structures, you ensure that WISe fits seamlessly into your unique automation environment.
Examples
Custom message and channel types in the WISe are plugins and you can find complete, working examples of how to configure and build these in the Auron Software Github repository.
Trying the Auron WISe
If you’re interested in getting some hands-on experience with the Auron WISe please reach out to us. We’re happy to setup a demonstration or a location trial version so you can see for yourself.
You need a custom solution but you don’t want to spend the time to re-invent the wheel. That’s exactly why the Auron SMS Server gives you the ability to automate the Auron SMS Server with JavaScript.
It’s more than just a way to send SMS, WhatsApp and other instant messages. Unlock its scripting capabilities, and it becomes your complete solution.
Why script my SMS automation?
There are many situations when you need custom behavior. To name just a few:
- Immediate acknowledgement: Customers report a more positive support experience if they know right away that their request is well received.
- Personalized response: You can reply to an existing customer using their full name or you can reference their existing query.
- FAQ and self-service: Automatically reply with predefined answers, like store hours or product details to reduce your support load.
- Feedback requests: After a purchase, send a message asking for a review or survey response.
And many more like this. In fact, chances are that, if you’re reading this, you may already have your own use case in mind.
The Auron SMS Server offers multiple ways to customize its behavior. Most notably you can use either a script language, like JavaScript or SQL Server or you can use a compiled language like C# or VB.Net.
A couple of advantages of using JavaScript:
- JavaScript familiarity: Many developers already have a familiarity with JavaScript.
- Code in place: Your changes are immediately effective. You can tweak and test immediately on the test server and export/import directly on the production server.
- Rich Ecosystem: With JavaScript on windows you’ll have access to many built-in windows APIs. Find some of the in our scripting guide.
- Built-in examples: The Auron SMS Server includes a lot of builtin example triggers. Also, the API reference in the knowledge base has JavaScript examples for most properties and methods.
Triggers and automatic message handling
By using triggers you’ll be able to automatically process incoming messages. But not just incoming messages but failed messages and succeeded messages as well. You can find a full overview of which message states are available for scripting here.
Triggers are especially useful for setting up things such as automatic replies and automatic forwards. The Auron SMS Server has a large number of prebuild scripts as well. All of these are available in JavaScript.
Some key use cases include:
- Automatic replies: Respond instantly to incoming SMS, such as a receipt confirmation (e.g. “Thank you for your message!”).
- Automatic forwards: Redirect message to another channel. Like forwarding an SMS to an e-mail or an e-mail to an SMS.
- Status based actions: Process failed messages by retrying them or retrying them on a different channel.
Creating a simple example trigger
To see how triggers work we can setup a simple example trigger. Let’s use the auto reply example. You can create a trigger by opening the Auron SMS Server manager, going to the ‘Triggers’ node in the left tree-view and selecting ‘New Trigger’.
This will open a dialog with a list of all available trigger templates. Select the ‘Reply Trigger Template.’ The icon indicates that this template is available in JavaScript.
In the next couple of steps, you’ll walk through the auto reply wizard, which helps you set up a trigger. First you’ll enter a name for the trigger and select which message channel it should listen to and lastly you’ll setup the reply body.
In the wizard you can use placeholders to shape the reply body. The placeholders that are available depend on the message type. For an SMS or WhatsApp message you’ll have the body and phone number but for an e-mail message you’ll also have the CC and BCC addresses etc.
If this is exactly what you had in mind then you can just click finish, enable the trigger and you’re done. If you need to do some more customizing or if you’re curious to know how the trigger works you can edit it by clicking the pencil on the right side of the trigger.
Inspecting your new trigger
On this first page you’ll find the trigger condition. This is a summary of what causes the trigger to run. Which message type it’s going to trigger for, on which status it’s going to trigger and which condition applies. The condition itself is a SQL expression. In this case it only runs for message that come in on the channel with ID ‘SMPP1’. If you remove that expression the trigger runs for every message. You can also expand the expression to narrow it down further.
The ‘JavaScript’ tab is where the magic happens. That’s where you’ll find the reference to the trigger script. This is also where you can specify some common files to include. By default the Auron SMS Server includes a ‘Common.js’ file which you can expand to add JavaScript function that you’ll need to share between triggers.
The JavaScript structure
Click on edit next to the script file to edit or inspect the actual trigger script. The script can look a little intimidating if you’re not familiar with JavaScript, but if you look closely you’ll see that it’s actually very easy to understand.
The ‘ProcessMessageEx’ function at the top of the script is the main entry point for the trigger. From there it calls the ‘Reply’ function. The reply function, in turn, creates a new SMS message object, which uses the incoming message (objMessageIn) to setup the new message (objMessageOut).
You can see that this is where the target channel is set for the reply message. Also, you’ll notice the ReplacePlaceholders function, where the placeholder replacement from the wizard is done.
You’re completely free to change and update this script in any way you see fit. The only thing this script needs is the entry function ‘ProcessMessageEx’. Other than that you can change everything.
STR_DEBUGFILE = "C:\\ProgramData\\Auron\\Auron SMS Server\\Log\\TRIGGER1.txt"
B_ENABLE_DEBUG = true
// ========================================================================
// Function: ProcessMessageEx
// ------------------------------------------------------------------------
// ProcessMessageEx trigger function to process incoming messages
// ========================================================================
function ProcessMessageEx(objMessageIn, objMessageDB, dctContext)
{
Log(">> ProcessMessageEx")
Reply(objMessageIn, objMessageDB)
Log("<< ProcessMessageEx")
}
// ========================================================================
// Reply
// ------------------------------------------------------------------------
// Automatically reply this message
// ========================================================================
function Reply(objMessageIn, objMessageDB)
{
Log(">> Reply")
// reply to SMS message
objMessageOut = objMessageDB.Create("SMS")
objMessageOut.AddTrace("Reply to message from channel: [" + objMessageIn.ChannelID + "]")
objMessageOut.ChannelID = "SMPP1"
objMessageOut.ToAddress = objMessageIn.FromAddress
objMessageOut.ToAddressTon = objMessageIn.FromAddressTon
objMessageOut.ToAddressNpi = objMessageIn.FromAddressNpi
objMessageOut.DataCoding = objMessageIn.DataCoding // in case of Unicode messages
objMessageOut.Body = ReplacePlaceholders("Automatically generated reply.\r\n%BODY%",
objMessageIn.FromAddress, objMessageIn.ToAddress, objMessageIn.Body)
// save the message into the database
objMessageDB.Save(objMessageOut)
if (objMessageDB.LastError != 0)
{
sErrorDescription = objMessageDB.GetErrorDescription(objMessageDB.LastError)
objMessageOut.AddTrace("Error replying to this message: [" + sErrorDescription + "]")
objMessageOut.StatusID = "FAILED"
Log("Error: Could not reply to this message: [" + sErrorDescription + "]")
}
Log("<< Reply")
}
// ========================================================================
// ReplacePlaceholders
// ------------------------------------------------------------------------
// Replace placeholder values
// ========================================================================
function ReplacePlaceholders(sFormat, sFromAddress, sToAddress, sBody)
{
Log(">> ReplacePlaceholders")
sResult = sFormat
sResult = sResult.replace("%FROMADDRESS%", sFromAddress)
sResult = sResult.replace("%TOADDRESS%", sToAddress)
sResult = sResult.replace("%BODY%", sBody)
Log("<< ReplacePlaceholders")
return sResult
}JavaScript around the Auron SMS Server
So far, we've setup a new trigger and looked at the script that it produces. But that's not all that we can do to automate the Auron SMS Server with JavaScript.
The same API that's used inside triggers can also be used outside of the Auron SMS Server, for example, to script behavior from the Windows Task scheduler.
For example, let's setup a simple JavaScript that will send an e-mail message every day containing a report of the number of failed message in the last 24 hours. This is the script:
// File: FailedMessageReport.js
// Purpose: Check Auron SMS Server MSSQL database for failed messages using AxMmServer.MessageDB Count() and save a summary message for an admin
// Create Auron SMS Server MessageDB object
var objMessageDB = WScript.CreateObject("AxMmServer.MessageDB");
// Count failed messages from the last 24 hours using MSSQL syntax
var sFilter = "StatusID = 'FAILED' AND LastUpdate >= DATEADD(HOUR, -24, GETDATE())";
var nFailedCount = objMessageDB.Count(sFilter);
if (objMessageDB.LastError != 0)
{
WScript.Echo("Count failed: " + objMessageDB.GetErrorDescription(objMessageDB.LastError));
WScript.Quit(1);
}
// Create and save a summary message to admin
var objNewMessage = objMessageDB.CreateMessage("SMS"); // Create an SMS message
objNewMessage.ToAddress = "+1234567890"; // Admin phone number
objNewMessage.Body = "Daily Report: " + nFailedCount + " messages failed in the last 24 hours.";
objMessageDB.Save(objNewMessage);
if (objMessageDB.LastError == 0)
WScript.Echo("Summary SMS saved successfully.");
else
WScript.Echo("Failed to save summary: " + objMessageDB.GetErrorDescription(objMessageDB.LastError));To run this script every day we'll setup the script in the Windows Task Scheduler by following these steps:
- Save the script: For example, use FailedMessageReport.js in C:\Scripts
- Open the Windows Task Scheduler
- Create task: Set the name to 'SMS Failed Report'
- Create trigger: In the Triggers tab click -New -> Action: "Start a program"
- Setup program: Name: "cscript.exe" Arguments: "C:\Scripts\FailedMessageReport.js"
- Condition: Check 'Run whether the user is logged on or not' and store the credentials
That's it. You can run the task manually to verify that it works. You now know exactly how to automate the Auron SMS Server with JavaScript.
Try it for yourself
You can get started with the Auron SMS Server right away by downloading the trial here. The trial is fully functional for 30days.
If you need any help setting things up or if you have any other questions you can always contact us.
Did you know how easy it is to send messages to WhatsApp groups with the Auron SMS Server? In this article, we’ll dive deeper into the how and why of WhatsApp integration.
As of this writing, WhatsApp is the dominant messaging platform for business messaging, so it makes sense to integrate with it. However, setting up an integration with your business can be challenging. With the Auron SMS Server and the WhatsMate platform, you can set up a simple test case in minutes!
Why send to a WhatsApp group?
WhatsApp is the go-to platform for delivering targeted, real-time messages. Here are some practical use cases where WhatsApp group integration makes sense:
1. Operational alerts
When it’s critical to stay on top of your production, you’ll want to set up a WhatsApp group for your support team. Many of our customers use real-time messaging to receive alerts from their machine or server infrastructure. With a single message to your WhatsApp group of specialists, you can ensure business continuity.
2. Steamlined customer support
If you already have a WhatsApp business account, you may organize customers into groups based on region, for example. This is effective because it’s a great way to provide immediate updates and notifications to a group of customers when it matters.
3. Events and announcements
Some groups are temporary but still invaluable. If you’re organizing an event and want to keep track of what everyone is doing, for instance, during a festival or a webinar, it makes sense to have a single point of communication where you can guide members on what is happening or where they need to be.
4. Boost marketing campaigns
Marketing your product greatly benefits from having a strong community and an accessible brand. You don’t need to add all your leads, but you could organize giveaways or set up a VIP group for your most loyal customers to offer weekly deals and discounts.
How does WhatsMate integrate with the Auron SMS Server?
WhatsMate provides an HTTP-based API for sending messages to WhatsApp and Telegram groups or individuals, and the Auron SMS Server provides an HTTP channel.
For example, to send a message to a WhatsApp group using WhatsMate, you need the following URL:
POST https://api.whatsmate.net/v3/whatsapp/group/text/message/{instance_number}The instance number is a number you’ll receive from WhatsMate. You can then send the following JSON payload to send a message:
{ "group_name": "%TOADDRESS%", "group_admin": "%FROMADDRESS%", "message": "%BODY%"}You can do this in the Auron SMS Server by creating a new HTTP SMS channel.
On the next page of the wizard, you can set up your client ID and secret as provided by WhatsMate.
Finally, parse the response from WhatsMate to confirm if the message was sent and to receive an ID from the WhatsMate service.
And that’s all you need to do to start sending messages to WhatsApp groups with the Auron SMS Server!
Get started today
You can set all of this up yourself today in just a couple of steps:
- Download the Auron SMS Server from the download page to start a fully functional 30-day trial
- Start a trial with WhatsMate.
- Setup your HTTP SMS channel.
If you need any help setting things up or if you have any other questions you can always contact us.
Version 2024R2 Released
Auron Software has launched a major update to its Auron SMS Server, introducing High Availability (HA) as the key feature. This update is a significant advancement for businesses that rely on SMS and messaging, improving system reliability and uptime.
With the introduction of High Availability, the Auron SMS Server can now remain operational even during system failures. Previously, a single server setup posed risks for critical messaging applications. However, with HA, businesses can now deploy a two server setup where a secondary server actively monitors the primary server. As a result, this enables automatic failover if any issues arise, ensuring minimal downtime. This is especially important for industries such as finance, healthcare, and logistics, where uninterrupted communication is crucial.
Auron SMS Server
The Auron SMS Server is a Windows server application that helps businesses integrate instant messaging and email into their business processes. The Auron SMS Server is commonly used to set up OTP systems, send appointment reminders, or send alerts. Additionally, because the Auron SMS Server can automatically process and reply to incoming messages, it is also commonly used for remote control applications or applications where customer confirmation is required.
Upgrading
For customers with a valid maintenance license, this update is available as a free upgrade. Auron Software also provides detailed guides to help users set up and use the new HA feature.
This update sets a new standard for operational reliability, making Auron SMS Server a vital tool for businesses looking to improve their messaging infrastructure.
For a full list of changes and upgrade instructions, please refer to the release notes. Detailed steps for setting up High Availability are available in the configuration section of the knowledge base.
The update is fully backward compatible with version 2024. You can test it by downloading a fully functional, 30-day free trial of Auron SMS Server 2024R2 here.
The Auron SMS Server 2024 is the next major version update of the Auron SMS Server. The Auron SMS Server is a Windows server application to help you integrate instant messaging and E-mail into your applications. Use it to connect to multiple SMS providers and send alerts, notification or mass mailings.
Our typical customers are banks, hospitals as well as customer support departments. The software is most commonly used for:
- Sending out transaction confirmations
- As middleware for 2FA or MFA applications
- Send automated notifications to customers or staff
- Interact with your customers or staff
- Various M2M applications
- Etc..
Improvements in version 2024
This release has seen a lot of important improvements across the board. The most important improvements are:
- Transitioned from the SQL Native Client driver to the MSOLEDBSQL, ensuring compliance with Microsoft’s updated security standards.
- Updated dependencies, including moving LocalDB to version 2022 for trial users.
- We’ve added examples that demonstrate how to use the internal message broker system that makes the Auron SMS Server responsive. With these examples connect into the notification system and setup custom notifications to make your own application more responsive.
- As well as many other improvements. Find a complete list in the release notes.
HTTP SMS and WhatsApp channels
Many providers are using HTTP to send and receive instant messages through their service. This is a list of providers that work well with the Auron SMS Server.
Setting up a new HTTP channel can sometimes be challenging as it requires a lot of technical knowledge since each provider has their own API.
Back in version 2022 we made the first big improvements by providing a streamlined setup for larger providers such as Twilio and InfoBip. With this release we’ve done even more to streamline the setup of completely new or unknown HTTP providers.
Try or upgrade
To try this version simply download the setup file here. After installation you can start a 30 day fully functional trial. The trial is in no way limited and will give you an excellent idea of the Auron SMS Server.
Upgrading is easy as well. Just download the same setup file, run it, and follow the instructions. The setup automatically upgrades your configuration.
Make sure that any existing C#, VB.Net or other compiled code that uses the Auron SMS Server API is recompiled after the upgrade. Also, always be sure to make a backup of your server and database before the upgrade.
Today we’re releasing another big update: The Auron SMS Component 7.2. In this version we’ve had the focus on improving the Auron SMS Agent for Android in addition to the component itself.
Auron SMS Component
The Auron SMS Component is an easy to use programming and scripting library for Microsoft Windows. You can use it for SMS as well as WhatsApp and a lot more.
Here are some common usages:
- Integrate SMS notifications from your Powershell or VBScript automations
- Setup SMPP client or server connections for high performance / high volume SMS sending
- Setup your own portable HTTP server to receive incoming WhatsApp messages or delivery reports from HTTP enabled SMS providers
- Quickly setup your own HTTP enabled API for your customers
Find the full documentation in our knowledge base. Find many programming and scripting examples on our GitHub page.
Auron SMS Agent for Android
With the Auron SMS Agent for Android you can send SMS from your PC using your Android phone. The Android SMS Agent is a small and easy to use application that runs on your phone and uses your WIFI connection to connect with the SMS Component.
It makes a lot of sense to use your Android phone for sending SMS. It’s a lot faster than most GSM modems and very reliable as well.
Find a full description on the Auron SMS Agent for Android page.
Improvements in SMS Component 7.2
In version 7.2 the Auron SMS Agent for Android has been greatly improved. It was already the fastest way to send SMS without using SMPP or HTTP. In version 7.2 you can have the application run in the background as well.
In addition we’ve taking another look at the Auron SMPP Simulator. The Auron SMPP Simulator is included with the Auron SMS Component and is a great way to performance or reliability test your SMPP client.
With the Auron SMPP Simulator you can now setup secure SMPP connections using TLS 1.2 or 1.3. You can select a security certificate from either your local machine or local user store.
Find the full list of changes in the release notes.
Download and try
Try the Auron SMS Component 7.2 today by downloading and installing the fully functional 30-day trial version.
You can also add the Auron SMS Component directly to your project by installing the nuget package from Visual Studio.