You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clean code, it is basically a POC right now with horrendous code.
Dial with a proper CallerID, this will be provided by the bouncer.
Implement proper storage, probably with redis or something so state is not lost if the app is reset.
Provide ringtone to the users which starts the call. If the call is allowed to go through it should be answered inmediatly and provide ringtone. Once the far end answers ringtone is cancelled and users bridged.
Provide the correct destination in the CDR. It should point to the endpoint's ID instead of the dialed extension.
Proper termination reasons when hanging up.
All ARI API related code should be inside a single package. It will live in this repository initially but if everything goes well we will need to reuse it in other repos, so it should be written with this in mind, AKA it can't depend on anything in this app, it should be self contained.
The text was updated successfully, but these errors were encountered:
Code is far cleaner, and all ARI code is in a single pkg.
Channel is now originated with correct caller ID.
You don't actually want to answer the call but instead set ringing on it. Once the other user answers, you stop ringing and mark the channel as answered.
It is not trivial to change the destination shown in CDR. Instead the endpoint (if available) is stored in userfield. This makes it possible to coalesce dst and userfield.
For the initial release we need to:
All ARI API related code should be inside a single package. It will live in this repository initially but if everything goes well we will need to reuse it in other repos, so it should be written with this in mind, AKA it can't depend on anything in this app, it should be self contained.
The text was updated successfully, but these errors were encountered: