gather information to improve destination algorithm

[iameru]

concerns api endpoint for 46elks on_hangup

When a phone call is finished, either successful or unsuccessful, gather information for the Destination Algorithm.

Gather Basic Infos on:

• Which MEP was called.
• Was the call connected successful.
• Who was connected to the MEP (in hashed format, to not suggest the MEP again).
• How long was the connected call

also find a way to somewhat accurately tell, if an MEP is already in a call initiated by us. Easiest implementation would be a timestamp. In this case the algorithm doesn't rely on the backend to always correctly trigger a boolean in the database and can use sane values as a fallback, i.e. occupied for 8 minutes.

For metrics it might also be useful to gather information for prometheus on:

• how much did the call cost us
• which of our numbers made the call
• was the call successful

[iameru]

Personally I myself wouldn't be annoyed by getting suggested the same MEP twice in a row and would ask for another random one again in the rare case this happens. Thats why I'd prioritize this item less and focus on the more relevant data for the moment