# Starlink Service for SMS and SIP-VOIP Notifications

**URL:** <https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 5, 2025, 8:49pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932 "2025-02-05T20:49:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![yiotis](https://avatars.discourse-cdn.com/v4/letter/y/e99b99/32.png) [@yiotis](https://forum.inductiveautomation.com/u/yiotis)\
**Post date:** [February 5, 2025, 8:49pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/1 "2025-02-05T20:49:39Z")

</div>

Has anyone used Starlink Business services for SMS (SMS Module)? I wanted to know how well this works, is it reliable? Also what web based service are you using for VOIP (Voice Module) ? I would like some recommendations for the SIP-Voice service rather than blindly picking any online service provider. Thank You.

---

<div class="post-metadata">

**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:** [February 5, 2025, 8:53pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/2 "2025-02-05T20:53:11Z")

</div>

I don't use Ignition's voice module myself, but I **do** run a VOIP client for Asterisk into my office through StarLink (in a tunnel). I would not expect Starlink itself to cause you any trouble.

---

<div class="post-metadata">

**Author:** ![yiotis](https://avatars.discourse-cdn.com/v4/letter/y/e99b99/32.png) [@yiotis](https://forum.inductiveautomation.com/u/yiotis)\
**Post date:** [February 5, 2025, 9:10pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/3 "2025-02-05T21:10:07Z")

</div>

Thanks for your feedback. I haven't heard of Asterisk. I am assuming you are referring to [SIP Trunking ⋆ Asterisk](https://www.asterisk.org/products/sip-trunk/)

---

<div class="post-metadata">

**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:** [February 5, 2025, 9:11pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/4 "2025-02-05T21:11:16Z")

</div>

Yes, I run Asterisk for my office phones, in the cloud. So the trunk isn't over Starlink, but the SIP connection from desk phone to my phone server.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 5, 2025, 9:47pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/5 "2025-02-05T21:47:44Z")

</div>

Note that, although we don't make this _super_ clear, our generic "SMS module" is actually **extremely specific** to a few types of SMS modems from Airlink:

> **[SMS Notification Profile | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/alarm-notification/notification-profile-types/sms-notification-profile#device-configuration)**
>
> SMS Notification Module

It is **not** a general purpose "send alarm notifications over SMS using any provider" option.

We also have a [Twilio based](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/alarm-notification/notification-profile-types/twilio-sms-notification) SMS module, and there's going to be a Twilio based voice option first-party in 8.3.

But any integration with Starlink _as a modem_ is not going to be possible first party. The best experience would have be with a custom module [ex working from our notification profile example module](https://github.com/inductiveautomation/ignition-sdk-examples/tree/master/slack-alarm-notification), but you could achieve _one way_ notification relatively easily with a scripted pipeline block if Starlink provides you with an API that you can call from scripting.

---

<div class="post-metadata">

**Author:** ![yiotis](https://avatars.discourse-cdn.com/v4/letter/y/e99b99/32.png) [@yiotis](https://forum.inductiveautomation.com/u/yiotis)\
**Post date:** [February 8, 2025, 4:25pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/6 "2025-02-08T16:25:15Z")

</div>

Thank You. Essentially what you are saying is we can run SMS via the Twilio SMS module and we were able to get Voice to work over AWS Chime. Phil T. above also suggested voice via Asterisk. Essentially both utilizing a 3rd party service over Starlinks internet.

---

<div class="post-metadata">

**Author:** ![delgadobrentsq](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@delgadobrentsq](https://forum.inductiveautomation.com/u/delgadobrentsq)\
**Post date:** [September 12, 2025, 11:45am UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/7 "2025-09-12T11:45:08Z")

</div>

i’ve had better luck triggering sms and sip notification reliably after tweaking buffer sizes and adding a small delay between sends.

---

<div class="post-metadata">

**Author:** ![delgadobrentsq](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@delgadobrentsq](https://forum.inductiveautomation.com/u/delgadobrentsq)\
**Post date:** [October 16, 2025, 10:42pm UTC](https://forum.inductiveautomation.com/t/starlink-service-for-sms-and-sip-voip-notifications/101932/8 "2025-10-16T22:42:35Z")

</div>

I’ve been running a similar setup and had a few hiccups at first too. The key for me was using a [sip provider](https://telxi.com) that allowed adjusting port settings and had decent support for NAT traversal. I had to tweak some firewall rules and SIP ALG settings on the router to get reliable two-way audio. Latency wasn’t a big issue, but packet loss was until I fine-tuned the QoS settings.
