Problems with Stun and Reboots

Discussion in '3CX Phone System - General' started by blabla, Apr 11, 2008.

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

    Joined:
    Jan 20, 2008
    Messages:
    32
    Likes Received:
    0
    Problem 1:
    Server is beeing rebooted, Server provides Internet Access through a PPPOE connection and runs 3CX.
    Result: Provider Lines are not registered until you manualy restart of force a register.
    3CX logs that it can not lookup the DNS entries for the STUN server (quite logicaly, since the connection is not up at this point in time) then gives up and does not try again.

    Problem 2: Server is also running VPN connections through RRAS. Every 5 seconds 3CX is logging [CM506004]: STUN request to STUN server 64.69.76.23 has timed out; used Transport: 192.168.X.X.5060 ... the Transport beeing the internal VPN Interface number (private IP adress space).

    Version: Latest Version
     
  2. h2009

    h2009 Member

    Joined:
    Mar 15, 2008
    Messages:
    447
    Likes Received:
    0
    The fix to problem two:
    Is you need to put in stun server address in both addresses, use this one for both, or google public stun server to find more - that will fix that problem

    stunserver.org
    stunserver.org

    Problem one
    not to sure what the problem is? can you clarify what you mean please.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. blabla

    Joined:
    Jan 20, 2008
    Messages:
    32
    Likes Received:
    0
    This does not fix Problem 2.
    The Problem is that 3CX tries to STUN resolve an internal address that is not routable and there is no NAT available, hence the lockup fails (the server has its own external IP on a RRAS interface).
    This would be no problem, but 3CX is trying and logging this every 2 seconds an is therby spamming the log.

    Regarding 1: What more can I say, the internet connection is not yet available when 3CX starts, DNS Lookup of the STUN servers fails and after that, 3CX is not trying again without intervention.
     
Thread Status:
Not open for further replies.