Is anyone running 3CX on hyper-v. I think there were some issues a couple years back but not sure if they've been worked out in v12? I have been running 3CX on a physical for 2 years but would like to virtualize it.
Running a 3CX Phone System installation in a virtualized environment is something very common and as long as the System Requirements are met (don't forget to calculate +10% in the requirements) you shouldn't have an issue. Note that you must install the Integrated Services if you choose to go Hyper-V.
However what issues are you referring to and what version of 3CX where they present on?
I think it may have been version 10 I heard there were some issues of increased jitter. It could have been anything tbh. It appears if I follow the instructions in the doc it will work just fine. I think I am going to try this this weekend.
Go for it.
I got tired of that AMD desktop on top of the UPS in our rack.. first threw it on the File/Print/DC box running 2012 R2.. finally went with it's own VM instead. Been pretty much flawless. My problems have been firewalls tanking or crapping out from RTP streams (really?... you're going to choke on a friggin' pair of streams for a phone call?...) so I multi-homed my PBX machine by dropping another vNIC onto the config with VLAN 666 or the external WAN.. and majiggered some port-based VLAN for the switch to the WAN circuit.. my hypervisor is has a team to the switch.
Short version.. it works fine. Just watch out for dynamic MAC.. your license activations will hate you eventually (I think five..).
I tried to switch over 3CX from a physical to a hyper v yesterday and wasn't able to get it working. I have something incorrectly configured in the network adapter. Calls would hit the 3CX (they would momentarily show up in the ports/trunk status) but then they would disappear and I would get a 3CX recording 'your call could not be completed'. In the 3CX logs I could see that there were references to the ip address on the host adapter on the hyper v host machine which is NOT the ip address of the 3cx vm. The 3cx vm has a different static IP address configured.
My guess is there is some routing or DNS issue somewhere. The only way 3CX would know about the IP address of the network adapter on the host machine is if it was looking up the IP of the 3CX server via the mac address of the host adapter (which is the statically configured mac address of the virtual adapter).
I followed the instructions in the hyper-v/3cx doc. Maybe I missed something or overconfigured something?
I had a new hyper v server ready with the current 3cx version installed. I backed up the current instance, then restored to the hyper v. 3CX itself looks good on the hyper v, but there is a network issue with the configuration.
I think both; calls both internal and external hit the 3cx for a second, then drop. My guess is this: calls hit the 3CX server then cannot reach any extensions and they do not get forwarded to voicemail. BUT the message I get 'this call cannot be completed' is from the 3CX server.
Go to settings, advanced, custom parameters and then in the search box type in the OLD lan ip and see if it shows up anywhere. If it does replace it with the new ip address.
I will try this. Somehow the 3CX is picking up the ip address of the host network adapter and it may see that somehow on startup. BTW the current 3CX and the new vm I tried to deploy were the same IP address. (but it still may have gotten confused somehow).