Issue with virtualization of 3CX in Hyper-V using MPLS SIP

[dza]

Hi,

I have been having issues with the virtualization of my 3CX . The system runs fine one its own dedicated physical machine using two separate network cards. An on board card and an external card ( the second network card is used for connecting my MPLS SIP )

I followed all the steps listed here ( https://www.3cx.com/docs/installing-microsoft-hyper-v/ ) and I can verify everything is set up correctly. But the above article does not provide any details on how to set up the second network adapter on a VM for the MPLS SIP.

I have two separate network adapter on the VM with different Mac addresses. I duplicated all the settings including the IP address of MPLS SIP from the working physical machine onto the VM.

However, when i migrate everything over onto the VM, I'm unable to register my MPLS SIP.

Any help would really be appreciated.

 

[cobaltit]

What troubleshooting have you done? Can you ping the MPLS SIP endpoint? Traceroute? Wireshark results?

 

[Lee Cramman]

So you have 2 separate networks, one dedicated for MPLS SIP and the other for your LAN?

If so do the 2 virtual nics should point to 2 different virtual switches / networks which, in turn, should point to your 2 separate physical network adaptors. If they point to the same virtual switch / network or both virtual switches / networks are mapped to the same adaptor then that could be your issue.

Have you confirmed that the 2 nics in your VM are definitely functional and talking to the 2 separate (correct) networks rather than the same one?

I'm unclear what you mean by an external card. It would normally be an internal card or an external adaptor. Either way, there will need to be functioning drivers for both on the hyper-v host.

If you've used P2V conversion it can cause issues with software that was installed expecting to see one set of hardware and then later seeing another so a fresh install and restore from 3CX backup is the way to go.

Unfortunately, I don't normally deal with Microsoft Hyper-V so my terminology might not be exactly correct but the principles apply.

 

[simply7]

Do you have a persistent route statement for your traffic to use the correct route for your MPLS SIP?
Check the physical box by entering ROUTE PRINT at a command prompt. Below is an example of what you may need on your VM.

NIC 1
IP 10.0.0.2
Mask 255.255.255.0
GW 10.0.0.254

NIC 2
IP 123.123.123.2
MASK 255.255.255.252
GW 123.123.123.3

If the IP of the SIP Server is 122.122.122.1 you would need to run this at an elevated command prompt.
route add -p 122.122.122.1 MASK 255.255.255.255 123.123.123.3

Honestly this should be handled in a router and not on your SIP server.