Solved Exception of type 'TCX.PBXAPI.PBXIsNotConnected' was thrown.

[amarsin]

Hello, this happens on a Migration.
after Backup is loaded and all fine, this happens on SIP Trunks.

how to fix this?

 

[amarsin]

also i get errors on starting services:

Job for 3CXPhoneSystem01.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status 3CXPhoneSystem01.service" and "journalctl -xe" for details.
A dependency job for 3CXIVR01.service failed. See 'journalctl -xe' for details.
A dependency job for 3CXQueueManager01.service failed. See 'journalctl -xe' for details.
A dependency job for 3CXCallFlow01.service failed. See 'journalctl -xe' for details.

tryed now migrate from debian9 to debian9, same error
tyed from deb9 to deb10, same error

 

[ChrisC_3CX]

We might need a bit more information regarding the process to get a better understanding of what's going on:

1. What exact version of 3CX was the backup you are using taken form?
2. Is this new instance an on-prem machine?
3. How did you deploy the new machine, was it using the 3CX ISO?
4. Are you restoring the backup during installation or after the 3CX Installation has been completed?
5. You say this happens on SIP Trunks, do you mean that the backup is restored successfully without errors and that you get the error when you click on the "SIP Trunks" section in the Management Console?
6. You mention getting errors on starting services, are you saying not all services start up after the installation?
7. Does the new instance have enough resources? I'd make sure it's compliant with our hardware requirements and especially check the drive capacity.

 

[amarsin]

We might need a bit more information regarding the process to get a better understanding of what's going on:

1. What exact version of 3CX was the backup you are using taken form?
2. Is this new instance an on-prem machine?
3. How did you deploy the new machine, was it using the 3CX ISO?
4. Are you restoring the backup during installation or after the 3CX Installation has been completed?
5. You say this happens on SIP Trunks, do you mean that the backup is restored successfully without errors and that you get the error when you click on the "SIP Trunks" section in the Management Console?
6. You mention getting errors on starting services, are you saying not all services start up after the installation?
7. Does the new instance have enough resources? I'd make sure it's compliant with our hardware requirements and especially check the drive capacity.

1. it was latest v16
2. no, container > strato deb 10 or 9, tested both
3. no default debian installs, default 3cx install + vacuuming postgre. as useal
4. 3cx installation is going thru fine, no errors etc.
5. yes its restored, no error. i get the error not as i click on siptrunks, its not an UI failure.
6. correct.
7. yes it has 8vcpus + 32gbRam and also on nvme raid

Deployed alot 3cx's like that on my old work, we used promox, ceph and opensense as maingateway. no iswsues at all.

my guess:

Strato is not KVM compatible and using "bad" hardware virtualization.

 

[NickD_3CX]

my guess:

Strato is not KVM compatible and using "bad" hardware virtualization.

That is very likely. Try restoring it on supported hardware or a tested virtualization platform or Hosting Provider and see how it goes.

 

[amarsin]

allready did that like 2 weeks ago, not that big deal in the end. but ye seems strato su**.

thank you!