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

Recall management #7149

Open
Amygos opened this issue Nov 15, 2024 · 0 comments
Open

Recall management #7149

Amygos opened this issue Nov 15, 2024 · 0 comments
Labels
nethvoice Bug or features releted to the NethVoice project
Milestone

Comments

@Amygos
Copy link
Member

Amygos commented Nov 15, 2024

We can think, with the functionality activated (I imagine a global activation or for incoming route) to behave like this automatically.

At most we can, when the external numbering calls back, communicate who appears to have searched for it and whether they want to speak directly with him or continue normally, or for example tell him that Tizio searched for it but Tizio is currently busy, so we also avoid having to manage failures by anticipating them.

I agree with limiting the functionality in time, 12 hours seems like a reasonable amount of time to me, we can make it modifiable.

https://partner.nethesis.it/t/richiamata-su-occupato-ma-al-contrario/8630/11

@Amygos Amygos converted this from a draft issue Nov 15, 2024
@Amygos Amygos removed this from NethServer Nov 15, 2024
@Amygos Amygos added this to the NethVoice 1.5 milestone Nov 15, 2024
@andrea-marchionni andrea-marchionni added the nethvoice Bug or features releted to the NethVoice project label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nethvoice Bug or features releted to the NethVoice project
Projects
Status: Todo
Development

No branches or pull requests

2 participants