3CX call drops on 16.0.2.910

[Jim Canfield]

Hi Folks,

Over the past few weeks I've started getting calls from customers complaining about random call drops. At first I disregarded it as normal drop call issues, but the complaints have been consistent enough across all my installs that I'm looking into this more seriously. Is anyone else seeing this? All my trunking is with Twilio, which up to this point, has been bullet proof. Also hosting everything in AWS, so my install base is very consistent. SBC's are all Linux and I noticed they would not auto-update from 383 to 390 without manual intervention. Can't help but wonder if it's related to an SBC update.

Just thought I would check with the community before I start doing some real digging.

 

[leejor]

I would start by looking at the reported calls in the Activity Log for similarities. All outgoing/incomming, from certain sets, to certain numbers, Bye from provider, etc. Have users start to log log the time and date of the calls.

 

[Jim Canfield]

I would start by looking at the reported calls in the Activity Log for similarities. All outgoing/incomming, from certain sets, to certain numbers, Bye from provider, etc. Have users start to log log the time and date of the calls.

Yep - Already started a list. So far, nothing consistent.

 

[leejor]

Start comparing to the Activity Log to see which end dropped the call(s).

 

[Jim Canfield]

Start comparing to the Activity Log to see which end dropped the call(s).

Pulled the sip log from Twilio and it's showing a BYE from 3CX. I think it has to do with the SBC. I never rebooted the SBC's after upgrading to 390. I've updated a rebooted a couple of them to see if it makes any difference. Stay tuned...