3CX PhoneSystem 01 SIP Server service stops constantly

[rafael.quintero]

Hi All

I have several PBXs with v18 where the 3CX PhoneSystem 01 SIP Server Service constantly stops.

PBX configuration is On Premise and hosted on Debian OS using the 3cx ISO

Regards

 

[ChrisC_3CX]

We might need a bit more information to hopefully figure out what's going on:

1. What exact version of 3CX are you running? You might want to consider updating to the latest version v18.0.2.307 which was just released today if you haven't already.

2. Are all affected PBX's compliant with our hardware specs? Regardless I recommend monitoring resource usage to see if it might be related.

3. Provided these are VM's, what virtualization platform is being used?

4. To check if this is perhaps call routing related, you could run a Call Report and check the call flow activity right before the crash to see if there's anything strange happening right before the incident such as a call loop, etc.

5. You could also take a look at the following log to see if you can gather a bit more information on what might be causing this. Take a look at the log entries right before the crash:

/var/log/syslog

 

[rafael.quintero]

We might need a bit more information to hopefully figure out what's going on:

1. What exact version of 3CX are you running? You might want to consider updating to the latest version v18.0.2.307 which was just released today if you haven't already.

2. Are all affected PBX's compliant with our hardware specs? Regardless I recommend monitoring resource usage to see if it might be related.

3. Provided these are VM's, what virtualization platform is being used?

4. To check if this is perhaps call routing related, you could run a Call Report and check the call flow activity right before the crash to see if there's anything strange happening right before the incident such as a call loop, etc.

5. You could also take a look at the following log to see if you can gather a bit more information on what might be causing this. Take a look at the log entries right before the crash:

Hi Chris

1. Version: 18.0.1.237

2. Yes, all the specs are compliant.

3. The virtualization platform is VMWare.

When it happens again, logs will be attached.

We have an open case with the number 800102 in case you like to review more information.

Regards

 

[NickD_3CX]

As this is not a constant issue, I would highly recommend upgrading to V18 Update 2 now because all troubleshooting from now on will need U2, I am pretty sure our Support Team has already informed you of this.
If not though, I can tell you that is 99% what they will be telling you.

So, my advice:

1. Upgrade to V18 U2 asap
2. Recheck that the logging has been re-enabled as per your support ticket
3. Then start monitoring again if the crash re-occurs

This can go 2 ways:
- Either the issue won't happen again, which is what we all hope for, as the stability improvements of U2 may kick in
- The issue happens again in which case you will already be on the latest stable release at the time (V18 U2) and the logs you provide support will be able to be used.

 

[per.eriksson_1]

I have the same issue after upgrading yesterday.

Less than 14h after the reboot after the upgrade.

Same setup with VMWare 6.7 and 3cx Debian

 

[ChrisC_3CX]

@per.eriksson_1

Could you perhaps also provide the information mentioned here?

Also, what IP Phones are you using if any(brand/model)?

 

[per.eriksson_1]

Things has stabilized...why I don't know. Since Wednesday no more issues....

What we have:

1. One single 3cx Debian (3cx packaged) server v18.0 (Build 314) just upgraded with the normal upgrade process
2. VMWare 6.7 U3 or 7.0.U2 depending on vCenter moves. 4 cores, 8Gb RAM
3. The system has 4 Linux SBC's where all desk phones comes in through
4. One single trunk to VoipTiger (non-"approved" provider)
5. The server is located in Germany while all clients are in Somalia
6. Hardware phones GrandStream 2130 and Yealink T23G only.
7. We have about 200 desk phones, 200 Smartphones and then of course all windows and web clients as well.
8. The system is in decent use but we will never ever come up to what we have licenses for.

BR
Per

 

[ChrisC_3CX]

Have you happened to check the Call Reports too, do you see any "suspicious" activity?

If this last occurred within the last 7 days, looking through /var/log/syslog for that specific instance might also be a good idea.

 

[joshuao3]

And now I'm having the same issue. Every 15 minutes or so the service called "3CX PhoneSystem 01 SIP Server" crashes. The Windows Logs says it's originating in ntdll.dll. I've attempted the fixes found here:

https://softwaretested.com/windows/how-to-fix-ntdll-dll-crash-error-on-windows-10/

DISM and SFC show no errors.

There were no windows updates in the last week or so and I have plenty of resoursed on the VM. None of the other hosted machines are having any problems.

Here's the Windows Log:
Faulting application name: 3CXPhoneSystem.exe, version: 15.5.9880.0, time stamp: 0x5ab27178
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x15c0
Faulting application start time: 0x01d803f639e6e891
Faulting application path: C:\Program Files\3CX Phone System\Instance1\Bin\3CXPhoneSystem.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 71959904-900b-46c7-8943-11bca197931e
Faulting package full name:
Faulting package-relative application ID:

Any help would be appreciated.

 

[ChrisC_3CX]

Is this one of the instances you've mentioned previously or a different machine? If a different one, what version of 3CX is it running?

Could you perhaps provide a screenshot from

"Properties >> Details"

tab of

"C:\Program Files\3CX Phone System\Bin\3CXPhoneSystem.exe"