Debian 9 SBC on Hyper-V HOST

[Lenin K]

Hey 3CX Community,
I ran into a very strange issue using 3CX in the cloud, connecting phones in office via Debian 9 3CX SBC VM on a HyperV Host. Currently, we have two clients setup this way & they both experienced the same exact issue below almost back to back.

The main 3CX server sits in the cloud and the SBCs are VM ona HyperV Host. We ran into an issue where the tunnel appeared to be disconnected (the same message was coming up on the phones) however, calls were still coming in, but no audio on either end. We tried rebooting both the SBC & the 3CX server in the cloud, however, the issue continued. I then created a new SBC on the HyperV host in an attempt to rule out the SBC, however, the same exact issue was happening on the new SBC, fresh install! At that point, we decided to reboot the HyperV Host and the issues were resolved. Same exact issue, two seperate clients.

Has any one running a similar setup experience this before? We have another office connected with an SBC using a Windows workstation & they never have any issues knock on wood.

Any community feedback or insight on this would be greatly appreciated. I was trying to find best practices to setup the Linux SBC on a HyperV VM, however, I did not see any.

 

[Rhys Haskell]

We have the same issue on a Raspberry PI. Sometimes clients will report all phones down, all the PI needs is a reboot and it will be back up in under 1 minute.

 

[cobaltit]

So the SBC on HyperV has the same requirements as 3CX on HyperV. Make sure you followed this guide:

https://www.3cx.com/docs/installing-microsoft-hyper-v/

And your specific issue sounds like when you don't have NTP installed.