Link to home
Start Free TrialLog in
Avatar of ROM
ROMFlag for United Kingdom of Great Britain and Northern Ireland

asked on

3cx move VM... not working.. no exts

3cx.. moved VM from one host to another and set static MAC. still no ext and cannot create TCP connection to activation.3cx.com
Avatar of Patrick Bogers
Patrick Bogers
Flag of Netherlands image

Hi

Sounds there is no connectivity at all on this VM or am i incorrect?
Can you e.g. ping a domain controller from that VM, or google.com? If yes then it is interesting what 3cx logs are showing.
(To my knowledge 3cx will startup quiet happily if basic connections are in place.)
Can it be the new host can not use a specific (voice) vlan that was accessable from the previous host?

Cheers
Avatar of ROM

ASKER

Yes I can ping activation.3cx.com... I can browse the web.

I can resolve from the web into the vm on the new host.

Checking my old server (spun it up again), it too has the issue cannot connect to activation.3cx.com.. so thats a red herring.

However.. I do not have any extensions in the new one :(

R
So outside communication is good but inside it is not.
If users can ping the 3cx server it means there is probably an ACL an the switch blocking voip traffic ( or not allowing it, however you like it.)
If users cant ping the new instance it probable has something to do with Vlan’s unless the new host is connected to the same switchport on the switch.

HTH
Download and install Fiddler and see the response you're getting from the activation IP
https://www.telerik.com/download/fiddler
Avatar of ROM

ASKER

Turned out I HAD to use the FQDN supplied by 3cx. It was not happy with anything I setup, even when the same.

Which is very odd as DNS entry for FQDN is the same IP as the 3cx one.

Closing as I resolved.
Thanks everyone

R
ASKER CERTIFIED SOLUTION
Avatar of ROM
ROM
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
1) If using 3CX FQDN, you mau need to "release" it and re-link it. 3CX will do this for you on request provided oyu can reach the activation servers.

2) to be sure you can reach the activation servers, run the 3CX "Firewall checker".  ONE problem with the actiavation servers is, the ports used are as for HTTP traffic, but it *isn't* HTTP traffic, and some smarter firewalls taht do packet content inspection will say "oh, this isn't HTTP traffic on this HTTP port - something fishy - I'll block it".