Twilio Module - more

In the gateway configuration for your Twilio account, why does the port need to be 80 in
the Inbound section? It says it is the default, so you should be able to change to another port.

What if you are on a Windows Server and IIS is using port 80?

The inbound port is the port Twilio’s servers are going to use when they attempt to reach the gateway with an HTTP request. It’s 80 because:

  1. That’s the default port for HTTP.
  2. That’s Twilio’s default.
  3. It’s not the expected case that your gateway is actually reachable on the internet, but instead that you’ve configured a router or something on the edge of your network to forward requests to the Ignition gateway on your local network.

If your gateway is actually reachable on the internet then you should set the inbound port to be the same port you’ve configured Ignition to run on.

We are a hosting service, so our Ignition server is reachable from the internet.
If we are using the Ignition default port of 8088, should the inbound port be set
to 8088 in the Twilio account setup on the gateway? Edit: I see you have already
answered this.

Is there any configuration work to be done on the Twilio side, since 8088 is not the
default port for http?

[quote=“stan@tripaga.com”]
Is there any configuration work to be done on the Twilio side, since 8088 is not the
default port for http?[/quote]

No, the module takes the configured public hostname and port then configures Twilio with a callback URL using those settings.