[asterisk-bugs] [JIRA] (ASTERISK-28123) stun keeps revaluating

Asterisk Team (JIRA) noreply at issues.asterisk.org
Sat Oct 20 14:27:47 CDT 2018


    [ https://issues.asterisk.org/jira/browse/ASTERISK-28123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245215#comment-245215 ] 

Asterisk Team commented on ASTERISK-28123:
------------------------------------------

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].

> stun keeps revaluating
> ----------------------
>
>                 Key: ASTERISK-28123
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28123
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stun_monitor
>    Affects Versions: 13.23.1
>         Environment: fedora 28
>            Reporter: Sean Darcy
>            Severity: Minor
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list