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

NethVoice: Recall on Busy isn't working #7010

Open
andrea-marchionni opened this issue Sep 9, 2024 · 1 comment
Open

NethVoice: Recall on Busy isn't working #7010

andrea-marchionni opened this issue Sep 9, 2024 · 1 comment
Labels
bug A defect of the software nethvoice Bug or features releted to the NethVoice project testing Packages are available from testing repositories

Comments

@andrea-marchionni
Copy link

It's possible to activate the recall busy service, it is correctly saved in the asterisk db

image

but then the daemon

root@voice2:/var/lib/asterisk# ps ax | grep recall
45 ? S 0:03 /usr/bin/python3 /usr/sbin/recallonbusy

That requires checking the settings and creating the calls when the recipient is free, which does not seem to work.

For this reason, the callback is never generated.

Check also that the default recall on busy parameter when creating extensions is active, it is not currently active.

image

The Recall on busy function is also missing in NethVoice CTI.

@andrea-marchionni andrea-marchionni added the bug A defect of the software label Sep 9, 2024
@edospadoni edospadoni added nethvoice Bug or features releted to the NethVoice project nethvoice-cti and removed nethvoice-cti labels Sep 9, 2024
@edospadoni edospadoni assigned tonyco97 and unassigned edospadoni Sep 12, 2024
@tonyco97 tonyco97 removed their assignment Sep 18, 2024
@andrea-marchionni andrea-marchionni assigned Stell0 and unassigned Amygos Sep 23, 2024
@Stell0
Copy link

Stell0 commented Oct 7, 2024

Test case:

  • update a nethvoice installation or install a new one

  • make a cal with an extension

  • try to call same extension from another one

  • book recall

  • hanghup first call

  • extension 2 should be called and when he answers a call to extension 1 starts

  • try different states for extension 2 (busy, in use, ...) when extension 1 hang up

  • try to use an extension that is not main extension for extension 1 and 2

  • try to use mobile app for extension 1 and 2

Stell0 added a commit to nethesis/ns8-nethvoice that referenced this issue Oct 8, 2024
NethServer/dev#7010

* freepbx: log recallonbusy using stdout and stderr

* Show reload button when recall on busy default is changed

* bump version to force database init

* Rewrite of recallonbusy to avoid using AMIClient python library

* make new recallonbusy executable

* enable recallonbusy by default

---------

Co-authored-by: Matteo Valentini <[email protected]>
@Stell0 Stell0 added the testing Packages are available from testing repositories label Oct 8, 2024
@Stell0 Stell0 removed their assignment Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect of the software nethvoice Bug or features releted to the NethVoice project testing Packages are available from testing repositories
Projects
Status: Testing
Development

No branches or pull requests

5 participants