linkedin / linkedin/iris

Getting "Application error" voice message

Open
#363 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
845
Forks
146
PR merge metrics
No merged PRs in 30d

Description

Hi ,

We are trying IRIS & Oncall in our office environment. Whenever I create a test incident (Using Plans) with urgent priority, I get a call from iris. But the voice message says "application error". I expect the voice call to read the incident. It is not working. I have opened the externalip:16649 to the world, Below is my twilio config in IRIS,

vendors:

  • type: iris_twilio
    name: twilio_1
    account_sid: XXXXXXXXXXXXXXXXXXXXXXXXX
    auth_token: XXXXXXXXXXXXXXXXXXXXXXXXX
    twilio_number: +XXXXXXXXXXXXXXXXXXXXXX
    relay_base_url: http://External-IP:16649/

I get the following error,

web.1 | 54.158.131.187 - - [24/Jan/2018:05:24:26 +0000] "POST /api/v0/twilio/calls/gather?content=188.+test_call&source=Autoalerts&instruction=Press+2+to+claim.&message_id=188&loop=3 HTTP/1.1" 404 - "-" "TwilioProxy/1.1"
web.1 | 54.82.193.204 - - [24/Jan/2018:05:24:28 +0000] "POST /api/v0/twilio/status HTTP/1.1" 404 - "-" "TwilioProxy/1.1"
web.1 | 54.165.215.242 - - [24/Jan/2018:05:24:30 +0000] "POST /api/v0/twilio/status HTTP/1.1" 404 - "-" "TwilioProxy/1.1"

Please help me fix it.

Thanks,
Gani

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the urgent-priority call through the configured Twilio relay and inspect the logged POST requests to /api/v0/twilio/calls/gather and /api/v0/twilio/status. Trace why both endpoints return 404; done means the call returns the incident message and the Twilio callbacks no longer produce 404 responses.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.