BLUF: I am having issues creating a notification profile to use Twilio as the SIP Gateway.
To clarify, my question is not about the Twilio Module, I can send SMS using Twilio Module. My expected answer is to make Twilio work as the voice notification service for Ignition alarms. I would appreciate any experience shared to have this working.
Here is a bit more description of my progress so far:
I set SIP on Twilio side and I was able to call myself using console and python code on my Ubuntu desktop. Now, I am trying to set a notification profile on ignition gateway to do the same when there is an alarm.
The following is my VOIP Gateway Settings:
Gateway Address: {domainname}.sip.us1.twilio.com
Username/Account: {username}@{domainname}.sip.us1.twilio.com
Password: {Password}
Advanced Settings
Authorization Id: {AuthToken}
The rest remains as default.
The status shows registering for a while, then returns “Request Timeout [408]”
On Twilio dashboard, there is no debug notifications, which means, I believe, it does not make it to the Twilio servers.
Am I on the right path at all?
Can anyone who has successfully made it through help me set this up? Thanks.
I am a little confused about whether ignition can use Twilio directly as the SIP gateway or if it needs something in between as the gateway then this gateway uses Twilio SIP.
Update:
I have deleted the Authorization Id in the advanced settings because somewhere in twilio documentation user id/authorization id are used interchangeably, thus I believe it is not supposed to be auth_token. That resulted in the same “Request Timeout [408]”
If I remember correctly, Twilio provides SIP Trunk capabilities, but it isnt a PBX per say. Have you tried the Kymera Systems Twilio module? It supports bi directional sms and voice.
Thanks for bringing the Kymera twilio module to my attention. Your twilio module looks promising. I will provide more feedback after I try all of its features for a while.
Was there ever any update to this? I have tried using the AWS Chime as a Voice connector, but it seems to lose registration with Ignition, and I have to restart the registration process to get the Voice alarms to work.
Was looking at Twilio as an option, since I use it already for SMS messages for alarms. Did anyone ever get this working?
Are you able to view your logs in Twilio or Ignition to see where they are failing? In my experience, it's usually due to the access lists. You'll want to make sure that you have added your network's IP address range to your IP / CIDR Access Control Lists in your Twilio account. You'll also want to allow all of the Twilio IP address ranges on your firewall
I also never would've guessed this configuration is "correct", but surprisingly it's the same for the "official" AWS Chime setup.
It seems if the Twilio trunk is configured with origination URIs/credential lists, it expects to be getting an INVITE from a proxy (PBX or SBC) - thus the Proxy Authentication required [407] error.
Without those configured, it works a treat straight from Ignition. Of course the IP ACLs give a bit of security, and in AWS Chime's case, the gateway address is pseudo-anonymized (22 char string - at least on the free tier).
I suppose we can manually define a complex trunk address in Twilio as well.
