- Joined
- Jan 3, 2018
- Messages
- 34
- Reaction score
- 4
Hi to all,
I'm a sysadmin in a company where we are evaluating 3CX as PBX replacement.
Two users were on an internal call when there was a brief Internet outage (3CX is on a AWS instance)
When connection resumed, everybody was available again except the two users, which were stuck as busy.
These users could place calls, but couldn't be called - they were diverted to voicemail.
I checked Activity log and reason for diverting to voicemail was that the called extension was busy.
I asked to reboot and reprovision the phone to no avail.
Finally, I restarted 3CX SIP server and in a matter of seconds the problem solved.
Unfortunately the relevant activity log seems to be lost with the restart.
Why this happens? Is there a more graceful way of fixing or preventing this than restarting server?
This is very similar to what is described on this 10 years old post https://www.3cx.com/community/threads/what-to-do-when-an-extension-is-stuck.3792/
Thank you
Nick
I'm a sysadmin in a company where we are evaluating 3CX as PBX replacement.
Two users were on an internal call when there was a brief Internet outage (3CX is on a AWS instance)
When connection resumed, everybody was available again except the two users, which were stuck as busy.
These users could place calls, but couldn't be called - they were diverted to voicemail.
I checked Activity log and reason for diverting to voicemail was that the called extension was busy.
I asked to reboot and reprovision the phone to no avail.
Finally, I restarted 3CX SIP server and in a matter of seconds the problem solved.
Unfortunately the relevant activity log seems to be lost with the restart.
Why this happens? Is there a more graceful way of fixing or preventing this than restarting server?
This is very similar to what is described on this 10 years old post https://www.3cx.com/community/threads/what-to-do-when-an-extension-is-stuck.3792/
Thank you
Nick