Push all missed calls created in Exotel as tasks in Avni
Notes
APIs on both sides are available
Auth is based on a static API key and token
There is some mapping we will need based on the called number (each number is mapped to a state and program). This logic will stay within the integration software.
DB Migration for the module to setup the metadata - 0.25
2.5 Setup sync status
Improve our background scheduler to run integration of multiple projects - 0.5
Error handling - 2
Duplicate tasks should not be created if there is an open task for a call (Good to have) - (Task GET based on status and metadata observations. This might require standardization of numbers before creating tasks) - 1
Happy path (actually create the task) - 2
Metadata migration - 2 endpoints (1 to get metadata, another to store metadata. This will be async. Add uuid column) - 3
Training implementer to add metadata - 0.5
Analysis
Define meta structure for mapping data
Limitation
0801928303 and 91801928303 are 2 different numbers
Objective
Push all missed calls created in Exotel as tasks in Avni
Notes
Tasks
Analysis
Limitation 0801928303 and 91801928303 are 2 different numbers