NethVoice recall on busy doesn't recognize an extension status change.
For this reason, it is not generated at the call when the monitored extension is free.
To reproduce the problem it is necessary to engage a user in a conversation by activating the callback on busy from another user.
When the first user is free, the second user must be called to start the call to the monitored user but this does not happen
NethVoice recall on busy doesn't recognize an extension status change.
For this reason, it is not generated at the call when the monitored extension is free.
To reproduce the problem it is necessary to engage a user in a conversation by activating the callback on busy from another user.
When the first user is free, the second user must be called to start the call to the monitored user but this does not happen