[asterisk-bugs] [JIRA] Closed: (ASTERISK-20118) When dnsmgr is enabled, the status of SIP trunks that use host names changes to UNKNOWN after sip reload

[Misha Vodsedalek (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Misha Vodsedalek closed ASTERISK-20118.
---------------------------------------

    Resolution: Not A Bug

The reported issue was due to an interaction introduced in an attempt to resolve another problem. Sorry about that.

> When dnsmgr is enabled, the status of SIP trunks that use host names changes to UNKNOWN after sip reload
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20118
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20118
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.14.0
>         Environment: Asterisk 1.8.14.0
> dnsmgr enabled
>            Reporter: Misha Vodsedalek
>
> We have a SIP trunk (voip.ms) that works properly when Asterisk is started. When we reload the configuration (either via "reload" or "sip reload"), the output of "sip show peers" changes for that trunk to
> Host               Status
> (Unspecified)      UNKNOWN
> The trunk is not operational after that and does not recover (even though "sip show registry" shows the trunk as registered).
> The problem does not occur when we use the IP address of the voip.ms location as the host.  The problem does not occur when we use the name as the host (e.g., houston.voip.ms) and when we disable dnsmgr.
> We tried another SIP trunk provider and the same issue was observed (i.e., the problem is not voip.ms specific).
> Testing exactly the same SIP trunk configuration on another system with Asterisk 1.6.2.24 with dnsmgr enabled did not exhibit this problem. Hence, it appears the problem has been introduced in Asterisk 1.8.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira