# Cellular Modems for SMS Notifications **URL:** \ **Category:** Ignition\ **Created:** [October 18, 2023, 11:15pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673 "2023-10-18T23:15:51Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Zayne\_Luker](https://avatars.discourse-cdn.com/v4/letter/z/74df32/32.png) [@Zayne\_Luker](https://forum.inductiveautomation.com/u/Zayne_Luker)\ **Post date:** [October 18, 2023, 11:15pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/1 "2023-10-18T23:15:51Z")
Hello all, I have been troubleshooting the Twilio service that handles SMS notifications. After spending much of the day working on this the customer would now like to switch to using a cellular modem rather than using Twilio. I have been researching the user manual for information on how to move forward on this transition. I saw that Inductive Automation officially supports three Airlink devices, the RV50/RV50X, RV55, and LX40. All these devices are Sierra Wireless devices. Is there something that makes these modems so special? The customer I am working with already has Cradlepoints and I would like to know if these could be used instead. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 18, 2023, 11:19pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/2 "2023-10-18T23:19:42Z")
> [@Zayne\_Luker](#): > > Is there something that makes these modems so special? The customer I am working with already has Cradlepoints and I would like to know if these could be used instead. Yes, Ignition's SMS module isn't for use with generic SMS modems, it's for a proprietary API supported by the Sierra Wireless modems. I would try to convince your customer to stick with Twilio if you can. The days where Joe Schmoe can buy a cellular modem and blast out SMS indiscriminately are quickly coming to an end. In 5 years or less I'd bet that's just not a thing any more. It'll be a quaint memory, like how you could run your own email server a decade or two ago and actually expect it to work. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 18, 2023, 11:56pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/3 "2023-10-18T23:56:57Z")
> [@Kevin.Herron](#): > > like how you could run your own email server a decade or two ago and actually expect it to work. I still run two email servers. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 19, 2023, 12:00am UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/4 "2023-10-19T00:00:23Z")
I absolutely knew you ran at least one email server and was thinking about it when I wrote that. I almost tagged you. But running your own mail server makes you an anachronism at this point. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 19, 2023, 12:08am UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/5 "2023-10-19T00:08:37Z")
> [@Kevin.Herron](#): > > makes you an anachronism at this point Yes, to some extent. Which is just sad. There is plenty of activity from us little people on SMTP/IMAP-focused mailing lists, and the recipes to have a mail server play nicely in the modern world are well documented (locked-down relaying, then SPF and DKIM, most importantly). It isn't trivial, but it is not rocket science. Anyone who can set up their own cloud server with DNS and reverse DNS should grok the email requirements in DNS, too. Setting up for private/internal use **IS** trivial. Enterprises that don't do so for their automation requirements make me scratch my head. ---
**Author:** ![Tim\_Carlton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim_carlton/32/52835_2.png) [@Tim\_Carlton](https://forum.inductiveautomation.com/u/Tim_Carlton)\ **Post date:** [October 19, 2023, 1:02pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/6 "2023-10-19T13:02:43Z")
The only thing I didn't like about OS/2 was that I had to run a mail server when all I wanted was a mail client. ---
**Author:** ![jay](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@jay](https://forum.inductiveautomation.com/u/jay)\ **Post date:** [October 19, 2023, 4:13pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/7 "2023-10-19T16:13:52Z")
Kevin, I am confused by your prediction. I am using the Sierra Wireless SMS alarming on several projects and don't want that to stop working. How is an RV50 connected to Ignition's SMS alarming module any different from the cellular provider's perspective than Joe Schmoe with a smart phone? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 19, 2023, 4:25pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/8 "2023-10-19T16:25:37Z")
Because Joe and his smart phone can't realistically set up a spam operation. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 19, 2023, 4:26pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/9 "2023-10-19T16:26:40Z")
My prediction is not an indicator that IA is going to stop supporting these modules/hardware or do anything to make it stop working... just my prediction on where the celluar/telco industry is heading... If nothing else, there will be more regulatory hoops to jump through. We already saw this with Twilio 10DLC registration. ---
**Author:** ![Nebul0us](https://avatars.discourse-cdn.com/v4/letter/n/82dd89/32.png) [@Nebul0us](https://forum.inductiveautomation.com/u/Nebul0us)\ **Post date:** [May 9, 2025, 9:00pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/10 "2025-05-09T21:00:07Z")
I am currently debating between Twilio and an Airlink RV50. I don't really follow what you are saying. In fact, you listed a reason to NOT go with Twilio (10DLC registration) but have not pointed to any specific reason to NOT go with the Airlink device. Can you elaborate? Any new information to share in the last year and a half? ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [May 9, 2025, 10:06pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/11 "2025-05-09T22:06:16Z")
The Sierra modems are a massive security risk. They can’t be configured with a gateway address, so you have to have them on the same subnet as the ignition servers. That is a no go for most IT departments as the normal rule is that server subnets should never leave the datacenter/server room for physical access security. Also the modems themselves are just not great and terrible to set up, even with the IA guide. Twilio is a pain, lots of hoops to jump through to prevent spam in most countries, and they are geared as a company to bulk campaign SMS, not low volume, high reliability. This means they are not worried about downtime for their services as most of their customers don’t care much about a couple hours of delay for the messages. Here in Aus we have a lot of downtime from twilio and customers get disillusioned very fast. ---
**Author:** ![Nebul0us](https://avatars.discourse-cdn.com/v4/letter/n/82dd89/32.png) [@Nebul0us](https://forum.inductiveautomation.com/u/Nebul0us)\ **Post date:** [May 9, 2025, 10:18pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/12 "2025-05-09T22:18:35Z")
Well that doesn't leave many options...thanks for your input! ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [May 9, 2025, 10:38pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/13 "2025-05-09T22:38:59Z")
> [@HOW-TO: Use a Teltonika 4G Modem as an SMS Dialler](https://forum.inductiveautomation.com/t/how-to-use-a-teltonika-4g-modem-as-an-sms-dialler/99613): > > There has been some complaints about the SMS capability of the SMS Notifications module that I have seen recently. Most of these centre around how the Sierra Wireless SMS modems have no feedback on whether an SMS has been sent or if the modem is even connected. I personally have a couple of issues with the module: The Sierra dialler uses UDP, so there is no confirmation a packet ever made it to the unit. The dialler cannot have a gateway address configured on it, so it MUST be on the same su… I have actually made a module for this manufacturer, just haven't finished proper testing on it. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 10, 2025, 12:18pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/14 "2025-05-10T12:18:59Z")
> [@David\_Stone](#): > > That is a no go for most IT departments as the normal rule is that server subnets should never leave the datacenter/server room for physical access security. Which directly contradicts network segmentation and server placement guidelines from DHS/NIST/CISA. "Most IT departments" are **wrong**. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [May 10, 2025, 10:24pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/15 "2025-05-10T22:24:51Z")
I’m interested in a source on this one. Those acronyms you mention are US ones and I see no references to sharing server networks outside administrative zones without firewalls in the research I have done. The world uses IEC 62443 for manufacturing network security standards. Again I can’t find backup for this approach being wrong. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 11, 2025, 1:31am UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/16 "2025-05-11T01:31:40Z")
CISA has presented at ICC in the past and handed out non-re-distributable material. But most is public. They key is that SCADA servers and their databases belong **on** the plant network with the devices, and the innermost firewall is between that plant network and the rest of the world. (This is one of the reasons that I consider Windows unsuitable as either gateway's or DB's OS--it is not safe to run Windows in production on the same LAN as poorly-secured (or unsecured) manufacturing equipment. (Unsuitable ==\> "Engineering Malpractice") ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [May 11, 2025, 2:10am UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/17 "2025-05-11T02:10:20Z")
> [@pturmel](#): > > and the innermost firewall is between that plant network and the rest of the world. This bit here still supports my notion that a 4G device should be outside that inner firewall, wherever your servers are located inside that zone. > [@pturmel](#): > > They key is that SCADA servers and their databases belong **on** the plant network with the devices This may be true, but there is no reason the VLAN/subnet with the servers on it needs to be on a network physically outside the plant network server room, that’s what the plant network routers exist for. This forms your Layer 2 ACL boundary that protects the server from broadcast traffic, bad ip configurations and nefarious actors that have plant level network port access. The entire CPwE design uses VLANs and routing for logical separation of all devices on the floor that are unrelated, this is just the extension of that. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 11, 2025, 2:01pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/18 "2025-05-11T14:01:27Z")
If you are routing between your plant automation devices and your SCADA, you have to put forwarding gateway addresses in them. While that's fine for certain well-defended technologies, the vast majority of small devices are too vulnerable to be trusted with routing. That's why the SCADA server belongs in the same **subnet**. (It doesn't need to be a different subnet to apply layer 2 filtering.) If you are requiring layer 3 routing between plant devices and Ignition, you are screwing up. IMNSHO. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [May 11, 2025, 8:37pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/19 "2025-05-11T20:37:41Z")
Most factories have more than 200 Ethernet devices on the floor, so you run out of addresses on a single subnet, coupled with most small devices not coping with broadcast traffic, if you set up a network like this you will have significant issues long term. This also does not match the industry standard models for networking a plant. Devices only need a gateway set up if they need external network access by themselves. The SCADA server can be comfortably source NAT added to a subnet and none of the devices need gateways configured at all. ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [May 11, 2025, 9:04pm UTC](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673/20 "2025-05-11T21:04:38Z")
> [@David\_Stone](#): > > so you run out of addresses on a single subnet Expand the subnet! e.g., 192.168.0.0/23, for 512 addresses (192.168.0.0 to 192.168.1.255), etc. [Next page](https://forum.inductiveautomation.com/t/cellular-modems-for-sms-notifications/80673.md?page=2)