Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

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

Discussion in '3CX Phone System - General' started by blabla, May 7, 2008.

Thread Status:
Not open for further replies.
  1. blabla

    Joined:
    Jan 20, 2008
    Messages:
    32
    Likes Received:
    0
    How can I stop 3CX from doing this:

    11:39:32.791 StunClient::eek: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::eek: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::eek: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::eek: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::eek: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.
     
  2. slinc

    Joined:
    Aug 7, 2007
    Messages:
    37
    Likes Received:
    0
    i am getting the same errors this morning.
     
  3. blabla

    Joined:
    Jan 20, 2008
    Messages:
    32
    Likes Received:
    0
    I am getting them for months. ;)
     
  4. Ecommerce

    Joined:
    Apr 7, 2008
    Messages:
    8
    Likes Received:
    0
    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...
     
Thread Status:
Not open for further replies.