PBX ENGINE Stopped

Reporting an Issue VitalPBX 4
1

Hello dear team

2 Days ago, we faced a “PBX Engine Stopped” issue on our V4 Pbx.
We created ticket to ask help from VitalPBX support and we was kindley supported
But, we was told that it was due to multiple invalid WebSocket sessions (as one client is calling from his own developped webrtc client).

So bellow are the steps we followed:

  1. As we thinked that it was an issue with server capacity and many connexions, we managed to buy a new Dedicated server and installed again the V4 (see server specs attached)
    New VitalPBX server
    New VitalPBX server1595×428 28.5 KB
    .
  2. We disconnected all Tenant’s client so actually, bind, no connexion, nothing is on
  3. We configured all possible things on the new server

BUT, we just noticed that the “PBX ENGINE” went again down while there is no call, nothing and server is new.

Can you help to find solution please

1 Like
2

Same issue here. Did you find a solution?

3

You would need to look at the logs to understand why Asterisk has crashed.

4

While the PBX Engine shows as STOPPED , my Asterisk is still up and running…
Even if I refresh the web interface. It keeps showing STOPPED, and on the other hand, I’m in the Asterisk console, I can make / receive call, it’s working correctly. Something is not matching correctly.

5

I am afraid that VitalPBX for some reason cannot access your AMI credentials.

6

And this would be set where?
The documentation stipulates that AMI Users is for 3rd parties