Rameshkumar Posted July 13, 2018 Report Share Posted July 13, 2018 Hi, I am using Vodia version 60. Sometimes call stuck in Active calls while actually it has been disconnected. This cause problem if user is the part of agent group, it considered it busy and can not take calls. How can I kill the process like this without restarting the service? Quote Link to comment Share on other sites More sharing options...
Support Posted July 13, 2018 Report Share Posted July 13, 2018 Hi, Press the left most button you see on this webpage. Quote Link to comment Share on other sites More sharing options...
Rameshkumar Posted July 13, 2018 Author Report Share Posted July 13, 2018 I know it use to cancel/kill the process, but it's not working. If I click on it it does not do anything and call still appear in active calls. Quote Link to comment Share on other sites More sharing options...
Support Posted July 13, 2018 Report Share Posted July 13, 2018 Try logging out and logging back in for that agent, if not, reboot the extension (which might not help, but worth a try). Lastly, unfortunaltely you might have to reboot the service if nothing works. Quote Link to comment Share on other sites More sharing options...
Rameshkumar Posted July 13, 2018 Author Report Share Posted July 13, 2018 Already tried all those options but noting worked. But this should have a solution. For one user we can't restart whole server. Also after how much time that process will be killed? Quote Link to comment Share on other sites More sharing options...
Support Posted July 13, 2018 Report Share Posted July 13, 2018 Hi, The time for the process to end cannot be determined. Your only option left is to reboot the server. Which OS is your PBX running on? We have a new 61.0 out, so if you are restarting the service, you might as well upgrade, as these issues are better handled there. Quote Link to comment Share on other sites More sharing options...
jackgrylls Posted December 29, 2018 Report Share Posted December 29, 2018 Hi ThereJust to add i have also noticed this behaviour on some systems with call pick up *20* and also barge in.Have not found a solution other than restarting all services.Cheers Quote Link to comment Share on other sites More sharing options...
Support Posted December 31, 2018 Report Share Posted December 31, 2018 If you're on the latest version which is 62.0.1, this issue disappears after a certain amount of time. It still has to be fixed though, but it does disappear in a few hours. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.