- Joined
- Jan 20, 2008
- Messages
- 32
- Reaction score
- 0
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.
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.