Twilio SMS Ack Inbound Public Hostname


We would like to set up a Twilio account so that it sends our users SMS messages as well as acknowledges the alarm if one of our users acknowledge the alarm via SMS.

So far, the Twilio number does send users a message when an alarm is active. However, we can’t get the ack part to work. I know we are supposed to provide a public hostname in our Twilio account in the Gateway Config page (Config>Twilio>Accounts> Inbound/Public Hostname), but wasn’t sure where to get that information from.

Are we supposed to set up a publicly reachable server and configure it to forward the inbound requests to our ignition gateway? Or is this a piece of information that we can get from our Twilio page?

Thank you!
Is this

Yes. Either your Ignition instance needs to be reachable (not ideal unless you are hosting a public instance) or you need a reverse proxy server or something to forward inbound HTTP requests from Twilio.

Hi Kevin,

Is there something we need to do to make sure that a server forwards the inbound requests to the ignition gateway or should providing the public hostname in the Gateway take care of everything?

Thank you!

1 Like

@jlee - Were you able to resolve this issue? I am currently dealing with the same issue, have tried tweaking many settings within both Ignition & Twilio (not much to change within Twilio’s settings as it is defined from the Ignition module) but have not had any success with the acknowledgements.

Our Ignition server is publicly reachable via port forwarding (for the time being), is there some additional setup required for these SMS acknowledgements to reach the Ignition server? See pic #1 of the Twilio debugger which returns an ‘HTTP retrieval error’. The red highlights contain our WAN IP, where port 8088 is setup to port forward to our Ignition server LAN IP address:8088. Would it be as simple as setting up a ‘URL redirect’ of the “:PORT/system/twilio” address?

Currently, when you enter the URL shown in pic #1 (Twilio debugger URL shown), it returns with the error shown in pic #2.