How to Stop 3CX from trying to send STUN over VPN interface

[blabla]

How can I stop 3CX from doing this:

11:39:32.791 StunClient:nTestTout [CM506004]: STUN request to STUN server 64.69.76.23 has timed out; used Transport: 192.168.X.X:5060
11:39:31.588 StunClient:nTestTout [CM506004]: STUN request to STUN server 64.69.76.23 has timed out; used Transport: 192.168.X.X:5060
11:39:31.588 StunClient:nTestTout [CM506004]: STUN request to STUN server 64.69.76.23 has timed out; used Transport: 192.168.X.X:5060
11:39:31.478 StunClient:nTestTout [CM506004]: STUN request to STUN server 64.69.76.23 has timed out; used Transport: 192.168.X.X:5060
11:39:30.400 StunClient:nTestTout [CM506004]: STUN request to STUN server 64.69.76.23 has timed out; used Transport: 192.168.X.X:5060

The server is DIRECTLY (PPPOE) connected to the internet, STUN requests over the "real" internet interface work.
192.168.X.X is a internal VPN interface.

 

[slinc]

i am getting the same errors this morning.

 

[blabla]

I am getting them for months.

 

[Ecommerce]

I also have this problem...

Our server has two Nic's

1) - Outside World (Internet)
2) - Internal Office Network and Storage (Intranet)

I had to disable the second nic, because there was no way I could find to stop it from sending STUN request to just one network... and since the internal network does not touch the internet... all the logs were filled with stun errors...