Before you get eager - this is not a simple problem - I've been racking my brains for a good chunk of time - even Rovo is frowning at me.
The situation:
We have an Phone Line setup with Twilio (not a fan - we'd like to have other options you know).
Apparently some time back in September Twilio blocked forwarding - so the phone worked - but by the time Operations got the ping - and forwarded the phone call to on-call - it would fire back an error in the activity log
System:
Couldn't Dial <NUMBER>; reason: code[21216]: Account not allowed to call <NUMBER>
And as per Operations configuration - dumps the call into voice mail.
As far as our SECOPS team was concerned - nothing was wrong as it would close out and quietly do its thing - and the Twilio account holder likely only got one tiny email that got buried in thousands being the platform owner of our very large org. (5-6000 users - 15-20 sites - 5000 Jira spaces in one site - we're a little busy here)
I'd like to see if there's a way to trap this by rerouting an alarm/page out to notify us Org Admins "its broken" as opposed to waiting for someone to notice there's an issue.
In the mean time I suggested they test their phone line once a week until we find a way to automate it cleanly.
TLDR - we need a way to notify us of a "internal system error" that falls back to voicemail without it falling back to voicemail but instead notifying the org administrators "this is broken."
Natively - no marketplace apps please. (so don't advertise)
I fear we'll be forced to manually test for a good chunk of time. One can hope someone clever out there who knows how to deal with this.
Much thanks!
EDIT: Forgot to mention - we got the phone line back up and running - turned out it was a "paperwork" error - ha ha ha ha. But still would be nice to know sooner rather than later there was a problem.
