- Joined
- Aug 23, 2022
- Messages
- 2
- Reaction score
- 0
Hi,
I have noticed a problem with several 3CX instances I am managing, where a held call occasionally fails to be retrieved.
Strangely enough, the behavior differs depending on call direction (inbound/outbound).
Scenario 1: Inbound call is put on hold, and fails to retrieve properly.
In this case, retrieving the call appears to work just fine, but the call is silent.
Meanwhile, the other side appears to be stuck on hold with the hold music playing.
There is no way of recovering and the only thing you can do is to hang up, which also causes the call to end on the remote side.
Scenario 2: Outbound call is put on hold, and drops on retrieval.
In this case, retrieving the call just causes it to drop entirely.
Other interesting things to note are that I cannot seem to reproduce this issue with internal calls, and that the issue appears to happen on a 'per-call' basis, since it either happens on the first attempt of putting someone on hold, or not at all.
We're using 3CX v18.0 (Build 965)
I was able to reproduce the issue on several different hard- and soft phones, including Yealink T46s (v66.86.0.5), Snom D375 (v10.1.64.17), as well as the official web- and Android apps.
I also re-ran all firewall checks which completed with no issues.
Thanks,
Thomas
I have noticed a problem with several 3CX instances I am managing, where a held call occasionally fails to be retrieved.
Strangely enough, the behavior differs depending on call direction (inbound/outbound).
Scenario 1: Inbound call is put on hold, and fails to retrieve properly.
In this case, retrieving the call appears to work just fine, but the call is silent.
Meanwhile, the other side appears to be stuck on hold with the hold music playing.
There is no way of recovering and the only thing you can do is to hang up, which also causes the call to end on the remote side.
Scenario 2: Outbound call is put on hold, and drops on retrieval.
In this case, retrieving the call just causes it to drop entirely.
Other interesting things to note are that I cannot seem to reproduce this issue with internal calls, and that the issue appears to happen on a 'per-call' basis, since it either happens on the first attempt of putting someone on hold, or not at all.
We're using 3CX v18.0 (Build 965)
I was able to reproduce the issue on several different hard- and soft phones, including Yealink T46s (v66.86.0.5), Snom D375 (v10.1.64.17), as well as the official web- and Android apps.
I also re-ran all firewall checks which completed with no issues.
Thanks,
Thomas