Hello,
PBX version 18.0.237 hosted on Linux in Azure, calls taken on the 18.3.33 Windows softphone.
We are seeing occasional problems when queue calls drop the moment they are connected to agents. I'm seeing this in the logs, which if I'm interpreting correctly, shows that the client at extension 1050 is connected to the call at 12:25:46 as normal, but at the same moment hangs up, sending the BYE at the same timestamp.
We've also had reports that sometimes the calls drop mid-conversation, and possibly only when the preceding call had been transferred, but I haven't been able to verify that.
What could be causing this situation? We're not seeing it on other agents in the same queue, and we do see it even when this agent is working with a different PC and headset.
I appreciate any insight you can offer, thank you!
PBX version 18.0.237 hosted on Linux in Azure, calls taken on the 18.3.33 Windows softphone.
We are seeing occasional problems when queue calls drop the moment they are connected to agents. I'm seeing this in the logs, which if I'm interpreting correctly, shows that the client at extension 1050 is connected to the call at 12:25:46 as normal, but at the same moment hangs up, sending the BYE at the same timestamp.
Code:
25/10/2021 12:25:46 - Leg L:4609.1[Line:10000<<+4477[xxx]543] is terminated: Cause: BYE from local
25/10/2021 12:25:46 - [CM503008]: Call(C:4609): Call is terminated
25/10/2021 12:25:46 - Leg L:4609.4[Extn:1050] is terminated: Cause: BYE from local
25/10/2021 12:25:46 - Leg L:4609.3[Queue:8022] is terminated: Cause: BYE from local
25/10/2021 12:25:46 - [CM503007]: Call(C:4609): Extn:1050 has joined, contact <sip:[email protected]:5063/UDP>
25/10/2021 12:25:35 - Leg L:4609.2[Ivr:8016] is terminated: Cause: BYE from 127.0.0.1:5483
25/10/2021 12:25:35 - [CM503007]: Call(C:4609): Queue:8022 has joined, contact <sip:[email protected]:5483/UDP>We've also had reports that sometimes the calls drop mid-conversation, and possibly only when the preceding call had been transferred, but I haven't been able to verify that.
What could be causing this situation? We're not seeing it on other agents in the same queue, and we do see it even when this agent is working with a different PC and headset.
I appreciate any insight you can offer, thank you!
