Getting error on incoming call routing with correct Twilio Credentials and Number

[ankit_pandey]

I am getting the above error prompt when trying to integrate Twilio based incoming call routing with OpsGenie.

The Twilio credentials and phone number are correct and verified.

Can someone suggest what am I doing wrong ?

[Howard Nedd]

Hi @ankit_pandey ,

I had the same issue.

Prior to taking steps provided by Wei make sure to check your API keys in Twilio. I created it all but then forgot to click on the save button below. This way your create API key and SID info will not be generated. So the data that you copy and paste will be none existing for Twilio and thus Opsgenie.

Go to your API keys and see if the API key actually exists. If this is not the case create a new one and make sure to click on safe.

Let me know if that works.

Regards,
Howard

[Wei Wung]

Hi @ankit_pandey 

How are you doing?  Thank you for reaching out!

Per our Incoming Call integration document, your custom Twilio number must first be purchased from Twilio's US Region 1 and the API keys created in the same US Region 1.  Please check if that is the case for your setup.

To check the number, go to your Twilio Console  > Develop tab > # Phone Numbers > Manage > Active numbers > click into your number > scroll down to Voice & Fax to see its Routing region.

To check the Region for your API key, in your Twilio account, go to Account > API key & tokens > click on the API key used in the incoming call configuration and you will be able to see its Region.

Hope the above helps.

[Pamela Barone]

What a joke. There's nothing about this in the integration setup so I just wasted two hours and $20 setting it up in Twilio only to find out it won't work outside of the US!

Sure would be helpful to include this on the setup page.

[Trent Lawson]

It definitely works now, I am using it in Australia