# Twilio SMS inbound configuration

**URL:** <https://forum.inductiveautomation.com/t/twilio-sms-inbound-configuration/113390>\
**Category:** Ignition\
**Created:** [January 19, 2026, 4:06pm UTC](https://forum.inductiveautomation.com/t/twilio-sms-inbound-configuration/113390 "2026-01-19T16:06:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Asjal\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@Asjal\_Ahmad](https://forum.inductiveautomation.com/u/Asjal_Ahmad)\
**Post date:** [January 19, 2026, 4:06pm UTC](https://forum.inductiveautomation.com/t/twilio-sms-inbound-configuration/113390/1 "2026-01-19T16:06:25Z")

</div>

Hi all,

I’m implementing SMS alarm acknowledgements in Ignition using the built-in Twilio notification profile, but I’m stuck on the ACK step.

Environment

- Ignition Gateway: 8.3.2

- Publicly accessible gateway host

- Gateway Web Server: HTTPS enabled on port 8043 (HTTP on 8088)

What I’m trying to do

- Use Ignition’s Twilio SMS notification profile with “Acknowledgement Allowed” enabled, so users can reply to the SMS with the acknowledgement code and Ignition will acknowledge the alarm.

Inbound webhook endpoint

- Twilio is configured to hit: https://:8043/system/twilio

- /system/twilio behavior from my machine:

Twilio / Ignition settings (current)  
Ignition Twilio account settings

- HTTPS Enabled: true

- Inbound Validation Enabled: false (see below)

Twilio configuration

- Phone Number:

- Messaging Service:

- TwiML App:

Observed behavior

- I receive alarm SMS notifications correctly.

- When I reply with the acknowledgement code, the alarm is NOT acknowledged in Ignition.

- When Inbound Validation Enabled = false:

- When I set Inbound Validation Enabled = true and test:

Questions

1. For Ignition’s Twilio SMS ACK flow, should the inbound webhook be ONLY configured in one place (Messaging Service vs TwiML App vs per-number), and can having both a Messaging Service and TwiML App assigned cause the inbound reply to bypass /system/twilio or be routed differently?

2. Is “Defer to sender’s webhook” appropriate for inbound ACK replies, or should the Messaging Service be explicitly set to “Send a webhook” to /system/twilio?

3. When Inbound Validation Enabled is enabled in Ignition, what determines the port Twilio ends up calling (why would it switch to 8088)?

4. Are there any specific Ignition log categories or settings I should enable to see Twilio inbound/ACK processing?

Any guidance on the correct Twilio + Ignition configuration for inbound SMS acknowledgement would be appreciated.

Thanks.

---

<div class="post-metadata">

**Author:** ![Asjal\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@Asjal\_Ahmad](https://forum.inductiveautomation.com/u/Asjal_Ahmad)\
**Post date:** [January 19, 2026, 5:47pm UTC](https://forum.inductiveautomation.com/t/twilio-sms-inbound-configuration/113390/2 "2026-01-19T17:47:24Z")

</div>

Setting Ignition loggers to Debug mode, I do get callbacks from Twilio in Ignition logs. However, they fail to validate. In Twilio, I keep getting 11220 - SSL/TLS Handshake Error because for some reason, it keeps trying to POST to `https://<gateway>:8088/system/twilio` even though I had the TwiML app set to 8043.

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0f10b2af535b9f2b95d7e80a843519bbe9b500b9.png)

---

<div class="post-metadata">

**Author:** ![Asjal\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@Asjal\_Ahmad](https://forum.inductiveautomation.com/u/Asjal_Ahmad)\
**Post date:** [January 22, 2026, 3:00pm UTC](https://forum.inductiveautomation.com/t/twilio-sms-inbound-configuration/113390/3 "2026-01-22T15:00:01Z")

</div>

Fixed the issue. I had to change the locale of the ec2 instance running the Ignition server and update the user in the user source by prepending their U.S. phone number with +1