IPv4 address on my windows 3cx system stays at detecting (red)

[feestbeestzaandam]

Product Standard Yearly
Version Number 18.0 (Build 908)
Windows 10 PC


As shown below, IPv4 remains on detection. (red)
But the 3cx server works fine.
My ip address has not (yet) changed, so luckily everything is still going well.
I also replaced the stun servers with non-default servers for testing, but it made no difference.
The firewall test shows green, so I don't know where the problem is.
I read something about a new activation server, but my server was activated a long time ago.
Does anyone know where I'm doing something wrong?



Productstandaard Jaarlijks
Versienummer 18.0 (build 908)
Windows 10 pc

Zoals hieronder te zien is, blijft IPv4 bij detectie. (rood)
Maar de 3cx-server werkt prima.
Mijn ip adres is (nog) niet veranderd, dus gelukkig gaat alles nog goed.
Ik heb ook de stun-servers vervangen door niet-standaardservers om te testen, maar dat maakte geen verschil.
De firewalltest geeft groen weer, dus ik weet niet waar het probleem zit.
Ik heb iets gelezen over een nieuwe activeerserver, maar mijn server is lang geleden geactiveerd.
Weet iemand waar ik iets fout doe?

 

[Alphabetic]

Are you on static WAN or DHCP?

What are your network settings in mgmt console?

 

[AWS2P]

Did you disable IPV4 to be replaced with IPV6 only ?

 

[feestbeestzaandam]

My isp gives me a random ip adres so it is DHCP but the last 3 months it was/is the same so its semi static.
I hope you wanted to know this settings?
I have in my network on every pc IPv4 ip adresses and sometimes also IPv6 if the divices supports it

 

[feestbeestzaandam]

• STUN server 77.72.169.213:3478 could not be reached (time out three times). It could be that the STUN server you are using is down or a network problem is preventing STUN resolutions. This might cause problems if you use VoIP Providers.
  
• 3CX Phone System Management Console ID: 30031 02/15/2023 5:35:47 PMSTUN server 77.72.169.213:3478 could not be reached (time out three times). It could be that the STUN server you are using is down or a network problem is preventing STUN resolutions. This might cause problems if you use VoIP Providers.
  

 

[feestbeestzaandam]

With a test from the windows machine where 3cx is working i did a test wit winstun.
and it works great, see picture.So it must be a fault in 3cx?

 

[SnakeRiverWebDevelopment]

As can be seen below, IPv4 remains at detection. (red)

Your IP is DHCP, it will always show red. Only static IP's show black.

 

[feestbeestzaandam]

Uw IP is DHCP, het zal altijd rood zijn. Alleen statische IP's tonen zwart.

I don't know why but it seems my picture from my first post has disappeared.
So I'll post it here (again).

If it stays red that's not a problem, but it stays detecting and doesn't show an ip address. I got the message:

"STUN server 77.72.169.213:3478 could not be reached (timed out three times). The STUN server you are using may be unavailable or a network problem is preventing STUN resolutions. This can cause problems if you VoIP providers used".

So I think something is wrong.

 

[JosIPVG]

Have you tried setting up a static ip4 adress for the machine?
If you run the firewall checker now does it still pass full marks?

 

[feestbeestzaandam]

I tried it and yes the firewall report is all green.

 

[feestbeestzaandam]

This way it looks on a new other 3cx server so ther is still something wrong on my old server and i like to repair it.