Solved Voice Mail Caller to PlayFile 23 hours and counting

[Matt Ross]

Hi All,
Just acquired 3CX - all running smoothly apart from 1 issue.
Having set voicemail - the Switcboard report is showing a Voice Mail caller to PlayFile Callee has run for 23 hours and counting!
Have used system both on webclient and app via Chrome - here's what we tried so far..
Delete and reinstall app
Sign out of web client and reboot device
Clear cookies
There is no option to force end the call - its greyed out

Any help much appreciated.
Thanks,
Matt

 

[Saqqara]

Try rebooting the server

 

[Matt Ross]

thanks Saqqara - that will be the next step - was hoping could achieved without disrupting service, but looking like this is the last option

 

[ChrisC_3CX]

Try dropping the call from "Management Console >> Dashboard >> Number of Calls in use", click the X icon on the right. If you can't see the call in the "Number of Calls in use" section, and you cannot drop it from within the Webclient Switchboard, you might very well need a reboot like @Saqqara mentioned.

You can just reboot the 3CX Services instead of restarting the whole server by going to "Dashboard >> Services" and only reboot the 3CX Database Server, this will force all other core 3CX services to restart along with it due to dependencies. Since this will render the 3CX PBX temporarily unavailable and also drop any active calls, I recommend performing this task during Out of Office hours to avoid downtime.

 

[Rhys Haskell]

Hi All,
Just acquired 3CX - all running smoothly apart from 1 issue.
Having set voicemail - the Switcboard report is showing a Voice Mail caller to PlayFile Callee has run for 23 hours and counting!
Have used system both on webclient and app via Chrome - here's what we tried so far..
Delete and reinstall app
Sign out of web client and reboot device
Clear cookies
There is no option to force end the call - its greyed out

Any help much appreciated.
Thanks,
Matt

You will need to restart the SIP server, this will kill any live calls but should resolve this issue.

 

[Matt Ross]

Many thanks @Saqqara and others for input - reboot solved the issue