Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper first release #1

Open
4 of 6 tasks
crazybolillo opened this issue Aug 4, 2024 · 2 comments
Open
4 of 6 tasks

Proper first release #1

crazybolillo opened this issue Aug 4, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@crazybolillo
Copy link
Owner

crazybolillo commented Aug 4, 2024

For the initial release we need to:

  • 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.

@crazybolillo
Copy link
Owner Author

  • 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.

@crazybolillo crazybolillo changed the title Initial release Proper first release Sep 14, 2024
@crazybolillo
Copy link
Owner Author

Ship now cry later. Points here are still good and should be covered someday but won't be in the first release.

@crazybolillo crazybolillo added the enhancement New feature or request label Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant