Solved email-test-since-new-public-static-ip 5.7.0 Denied

[iam-user99]

Hello,

I think here is something wrong with the FQDN. What do you think might be the cause?



problem: 3cx-Email test say
5.7.0 Denied
since new primary WAN /new static IP
no other problems observed so far
Watchguard is manageing the two WAN LINES, but only XXX.XXX.XXX.165 should be the primary one.

details

a)
static IP was changed in 3cx-webadmin + reboot

a)
if I ping (from home)
contoso.my3cx.de
this IP
XXX.XXX.XXX.194 (thats now secondary WAN, but will retire)
replies.

b)
in putty:
echo $(wget -qO - https://api.ipify.org)
it shows
XXX.XXX.XXX.165 (thats new primary wan)

c) licence say:
Unable to reach 3CX License Activation Server. Confirm that your Primary DNS Server is able to resolve activation.3cx.com

e)
in putty
systemd-resolve --status
DNS is the local Domaincontroller on premises

f)
XXX.XXX.XXX.165 was listed in 2003 at sorbs/spamhaus, but should be clean now afaik.

g)
switch to dynamic, reboot, wait 3 hours, switch back to static ip was done -no effect.

h)
firewall-test= green

i)
Port 2528 outbound is open


• 3CX Version, e.g. Standard Annual 16.0.8.9
• Debian 9
• On-premises
• IP Phone YEALINK
• Provisioning Method: Local / VPN / STUN / SBC ? > Local
• Trunk Provider or VoIP Gateway Make/Model, e.g. >QSC-PLUSNET
• Has the Firewall Checker passed: YES / NO ? >YES
• Are custom Phone Templates being used: YES / NO ? >NO

 

[ChrisC_3CX]

This will happen if the PBXs internet traffic IP does not match the IP the PBX's FQDN resolves to. That said, make absolutely sure ALL of the PBXs traffic is permanently routed out of only one of the WANs and then go to "Settings >> Network >> Select static IP and enter the correct IP address" then go to "Dashboard >> Services" and restart the 3CX System service. Once the DNS updates you should be good to go.

 

[ChrisC_3CX]

Hey @iam-user99,

As mentioned via PM, it seems the FQDN IP and the IP the PBX contacts our activation servers from are in fact the same. That said, the PBX version you're running is no longer capable of activating so what you must do now is upgrade the PBX to v16.0.8.16 or better yet to v18.0.3.461.

If you do not have the option to upgrade via the "Management Console >> Updates" section, I recommend simply taking backup and redeploying the PBX using the latest 3CX ISO: https://www.3cx.com/docs/manual/installing-debian-linux-pbx/

 

[iam-user99]

Hello Chris,

thx a lot - solved.

The solution was your statement: it seems the FQDN IP and the IP the PBX contacts our activation servers from are in fact the same. That said, the PBX version you're running is no longer capable of activating so what you must do now is upgrade the PBX to v16.0.8.16

 

[ChrisC_3CX]

Brilliant! Happy to see you got this sorted in no time!

Do start a new thread if you need anything else!