STUN Timeouts

Discussion in '3CX Phone System - General' started by Kinjutsu, Jul 2, 2008.

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

    Joined:
    May 20, 2008
    Messages:
    7
    Likes Received:
    0
    Hi guys. I have seen a few topics on this but haven't really seen any definite answer. So here is my situation.

    When I start the Phone Server, the first STUN request that is sent actually resolves, and everything works fine. (see log below)

    Code:
    10:29:32.534  	StunClient::process  	[CM506002]: Resolved SIP external IP:port (205.151.63.89:10060) on Transport 192.168.0.103:5060
    10:29:32.441 	StunClient::onInitTests 	[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.0.103:5060
    I've set the STUN server options so that it rechecks external IP every 1200 seconds. What happens next is that after 1200 seconds, it sends another request that never resolves, I get like 100 lines in a row that state the request has timed out. So my question is, why does the first request on start up (StunClient::eek:nInitTests) resolve, but the following requests (StunClient::eek:nTestOut) do not? I've checked my router settings and everything is set up properly, in fact everything works, I can place and receive calls, except that the STUN requests keep timing out.
     
  2. Kinjutsu

    Joined:
    May 20, 2008
    Messages:
    7
    Likes Received:
    0
    Figured it out.
     
Thread Status:
Not open for further replies.