Summary:	ASTERISK-28123: stun keeps revaluating
Reporter:	Sean Darcy (seandarcy)	Labels:
Date Opened:	2018-10-20 14:27:23	Date Closed:	2018-10-22 08:09:46
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_stun_monitor
Versions:	13.23.1	Frequency of Occurrence	Constant
Related Issues:
Environment:	fedora 28	Attachments:
Description:	STUN is being reevaluated every  1 - 5 minutes: [Oct 20 14:57:38] WARNING[1175]: res_stun_monitor.c:140 stun_monitor_request: STUN poll got no response. Re-evaluating STUN server address. [Oct 20 14:57:59] NOTICE[1175]: res_stun_monitor.c:151 stun_monitor_request: Old external address/port <myipaddr>:56659 now seen as <myipaddr>:44335. IAX, got a network change message, renewing all IAX registrations. [Oct 20 14:58:38] WARNING[1175]: res_stun_monitor.c:140 stun_monitor_request: STUN poll got no response. Re-evaluating STUN server address. [Oct 20 14:58:59] NOTICE[1175]: res_stun_monitor.c:151 stun_monitor_request: Old external address/port <>:44335 now seen as <>:43465. IAX, got a network change message, renewing all IAX registrations. [Oct 20 14:59:38] WARNING[1175]: res_stun_monitor.c:140 stun_monitor_request: STUN poll got no response. Re-evaluating STUN server address. [Oct 20 14:59:59] NOTICE[1175]: res_stun_monitor.c:151 stun_monitor_request: Old external address/port <>:43465 now seen as <myipaddr>:59330. IAX, got a network change message, renewing all IAX registrations. cat res_stun_monitor.conf | grep -v ^\; [general] stunaddr = stun2.l.google.com:19302 I didn't change the default stunrefresh of 30. I've also tried xten , counterpath and numb.viagenie.ca servers. This is a NAT'd machine, of course. Firewall open for 19302 and 3478. But if it were a firewall issue, then the stun monitor would never find the address. Not a big deal, but really spams the logs.
Comments:	By: Asterisk Team (asteriskteam) 2018-10-20 14:27:24.265-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2018-10-22 08:09:47.037-0500 This appears to be working as expected. The module regularly sends out a STUN request and waits for a response. In your case it is sending out a request, and receiving no response. This could be because of the NAT involved or something else. You would need to do packet captures to see what is going on. When this occurs it opens a new local UDP port and sends a new request, which works in your case. This would force a fresh NAT mapping.