3CX SIP Service becomes unresponsive or crashes

[elec]

Hello,

We have a ticket open with 3CX support and according to them the reason our PBX is becoming unresponsive and requires a restart of the SIP service is due to invalid SRTP packets.

They are saying its because we are using unsupported phones, has anyone has found this issue and figured out a way out of this that doesnt involve replacing the phones? We are looking to buy more phones but it will take some time to order and get them installed and would like a workaround meanwhile.

• 3CX Version, Pro Annual 16.0.9
• Server OS, e.g. Debian 9
• Is the 3CX Server Hosted and where? VMWare on prem
• Provisioning Method: Local / VPN / 3cx APP and Web clients

 

[cobaltit]

Well you didn't mention what phones but 3CX is solid across all of our installed base, although our use of unsupported phones is very minimal. That being said, I'm surprised 3CX is crashing due to that. I would consider that a bug of sorts as that's almost like a DoS attack.

You could try using v18A4 as there were a number of crash scenarios addressed. v18A4 is reasonably stable, and given you are already crashing, wouldn't hurt to try.

 

[elec]

We are using a mix of Zycoo D60 and Grandstream 1630. Yes I agree it should be a bug, no matter what data a phone sends to a PBX it shouldnt cause to crash.

Thanks we will look into V18A4.

 

[NickD_3CX]

Regarding the crash, although I am not familiar with the specific ticket you have with 3CX Support, I can confirm that in V18, among other things of course, there has been some additional hardening added to the Media Server that counters/ignores invalid RTCP/SRTCP that did cause certain issues under circumstances.

This fix is included for sure in V18 Alpha 4 (maybe even Alpha 3, but not sure...).