SIP Server stopped - segfault

[vrelk]

So, I was having issues with my older 3CX install with phones connecting to it. I generally use an SBC even though I don't really need it, which is why I didn't notice the issue for some time. The SIP server was stopped, and after some fiddling with apt purge and install, I gave up and did a fresh install using PBX Express to AWS.
I then did a restore and updated the system packages (3CX was not one of them). I got a support log after seeing services were still stopped, but didn't see anything useful. (If someone from 3CX sees this and wants it, I can send it).

● 3CXPhoneSystem01.service - 3CX PhoneSystem 01 SIP Server
   Loaded: loaded (/lib/systemd/system/3CXPhoneSystem01.service; enabled; vendor preset: enabled)
   Active: failed (Result: core-dump) since Tue 2020-03-17 20:46:31 EDT; 18min ago
  Process: 1760 ExecStopPost=/bin/rm -f /var/run/phonesystem/3CXPhoneSystem01.pid (code=exited, status=0/SUCCESS)
  Process: 1749 ExecStart=/usr/sbin/3CXPhoneSystem -p /var/run/phonesystem/3CXPhoneSystem01.pid /var/lib/3cxpbx/Bin/3CXPhoneSystem.ini (code=dumped, signal=SEGV)
Main PID: 1749 (code=dumped, signal=SEGV)

Mar 17 20:46:31 ip-172-26-12-162 systemd[1]: Starting 3CX PhoneSystem 01 SIP Server...
Mar 17 20:46:31 ip-172-26-12-162 systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=dumped, status=11/SEGV
Mar 17 20:46:31 ip-172-26-12-162 systemd[1]: Failed to start 3CX PhoneSystem 01 SIP Server.
Mar 17 20:46:31 ip-172-26-12-162 systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
Mar 17 20:46:31 ip-172-26-12-162 systemd[1]: 3CXPhoneSystem01.service: Failed with result 'core-dump'.

-- Subject: Unit 3CXPhoneSystem01.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit 3CXPhoneSystem01.service has begun starting up.
Mar 17 21:09:02 ip-172-26-12-162 kernel: 3CXPhoneSystem[3238]: segfault at 0 ip 0000560afa3fe253 sp 00007ffddcc5c790 error 4 in 3CXPhoneSystem[560afa28f000+45c000]
Mar 17 21:09:03 ip-172-26-12-162 systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=dumped, status=11/SEGV
Mar 17 21:09:03 ip-172-26-12-162 systemd[1]: Failed to start 3CX PhoneSystem 01 SIP Server.
-- Subject: Unit 3CXPhoneSystem01.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit 3CXPhoneSystem01.service has failed.
--
-- The result is failed.
Mar 17 21:09:03 ip-172-26-12-162 systemd[1]: 3CXPhoneSystem01.service: Unit entered failed state.
Mar 17 21:09:03 ip-172-26-12-162 systemd[1]: 3CXPhoneSystem01.service: Failed with result 'core-dump'.

 

[vrelk]

So, after another fresh install and doing a manual import of settings I think I narrowed it down to one final problem (must have been a different issue that started this whole thing because the issue started before I did this).

https://imgur.com/lIdlTTw

Anyways, it would seem that the wireguard tunnel I tried to setup so my AWS hosted 3CX install could be routed locally was causing the SIP server to crash. As soon as I disconnected it (also removes the interface) it started working again.

As for the issue that started this whole thing. Remote phones fail to register using UDP, but will register using TLS. Problem here is, it takes about 12 seconds for it connect to a local extension (IVR for my test).
If I use an SBC, it works perfectly using UDP or TLS and connects calls instantly.

This instance was setup using PBX Express, so it has all the firewall rules it should.