I doubt the generation of hyper v machines can be an issue. But SIP Server is crashing. Sip server is a network service so it depends 100% on network. If you have a stack that is problematic or the hypervisor is not configured correctly, the guest suffers and the sip server will act like this.
However in this case, I would like to change my analysis here.
libdum-1.10.so is a library which is used deep inside the core of the sip engine. It is at the top layers of the core and this is responsible to build the internal structure of how the dialogs should be sent / built. It calls DUM thread - Dialog usage manager and it is this guy that creates and builds the sip packets in a nutshell.
Get me that core dump. Maybe we can see something from it. I think a call or a specific type of call or a race condition is causing the server to crash.
Hello here is the log dump for the crash just moments ago.
Jul 6 06:25:02 WestRec-3CX rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="455" x-info="
http://www.rsyslog.com"] rsyslogd was HUPed
Jul 6 07:17:01 WestRec-3CX CRON[59608]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 08:17:01 WestRec-3CX CRON[61028]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 09:17:01 WestRec-3CX CRON[62513]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 10:17:02 WestRec-3CX CRON[63982]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 11:17:01 WestRec-3CX CRON[65407]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 11:33:17 WestRec-3CX systemd[1]: Starting Cleanup of Temporary Directories...
Jul 6 11:33:17 WestRec-3CX systemd[1]: Started Cleanup of Temporary Directories.
Jul 6 12:17:01 WestRec-3CX CRON[1778]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 13:17:01 WestRec-3CX CRON[3233]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 13:44:56 WestRec-3CX kernel: [181663.818896] iptables[DOS]: IN=eth0 OUT= MAC=00:15:5d:03:1c:05:ac:5f:3e:a6:91:5c:08:00 SRC=192.168.4.20 DST=192.168.4.3 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=63942 DF PROTO=TCP SPT=45427 DPT=7 WINDOW=65535 RES=0x00 SYN URGP=0
Jul 6 13:44:57 WestRec-3CX kernel: [181664.818029] iptables[DOS]: IN=eth0 OUT= MAC=00:15:5d:03:1c:05:ac:5f:3e:a6:91:5c:08:00 SRC=192.168.4.20 DST=192.168.4.3 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=63943 DF PROTO=TCP SPT=45427 DPT=7 WINDOW=65535 RES=0x00 SYN URGP=0
Jul 6 14:17:01 WestRec-3CX CRON[4742]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 15:17:01 WestRec-3CX CRON[6200]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 16:17:01 WestRec-3CX CRON[7691]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 6 16:53:38 WestRec-3CX kernel: [192985.460953] traps: 3CXPhoneSystem[8322] general protection ip:7fb87d3b7e20 sp:7fb8713e5530 error:0 in libdum-1.10.so[7fb87d306000+13c000]
Jul 6 16:53:38 WestRec-3CX systemd[1]: 3CXPhoneSystem01.service: main process exited, code=killed, status=11/SEGV
Jul 6 16:53:38 WestRec-3CX systemd[1]: Unit 3CXPhoneSystem01.service entered failed state.
Jul 6 17:00:26 WestRec-3CX systemd[1]: Starting 3CX PhoneSystem 01 SIP Server...
Jul 6 17:00:26 WestRec-3CX systemd[1]: Started 3CX PhoneSystem 01 SIP Server.