[asterisk-bugs] [JIRA] (ASTERISK-23767) Dynamic IAX2 registration stops trying if ever not able to resolve
David Herselman (JIRA)
noreply at issues.asterisk.org
Thu May 22 07:18:43 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-23767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218376#comment-218376 ]
David Herselman commented on ASTERISK-23767:
--------------------------------------------
dnsmgr can be used to work around this issue but that also has it's own issue of setting the port as '0' once the name can again be resolved. This is however another separate issue from the one reported here...
is: This bug report deals with the issue that, should Asterisk ever not be able to resolve a DNS hostname for an IAX2 registration, it never tries again.
> Dynamic IAX2 registration stops trying if ever not able to resolve
> ------------------------------------------------------------------
>
> Key: ASTERISK-23767
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-23767
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_iax2
> Affects Versions: 11.9.0
> Environment: IAX2 registration to dynamic hostname
> Reporter: David Herselman
> Assignee: Rusty Newton
>
> Upgraded Asterisk from 10.7.1 to 11.9.0 on 55 hosts and are now experiencing an issue relating to IAX2 registrations, when the remote host is utilising a dynamic hostname.
> Alpha and Omega register with each other using IAX2 trunks. Both sides are set as 'host=dynamic' and rely on registrations to ascertain the remote point's IP address. This has been extremely reliable prior to our upgrade to 11.9.0.
>
>
> Problem: If DNS resolution is ever unavailable (Telco here kicks ADSL sessions off after 24 hours so that they reconnect) the registration gets set with a '(null)' host address and never retries the registration. Issuing a 'iax2 reload' doesn't help either, only completely unloading and reloading the chan_iax2 module works.
>
> Alpha has the following iax registration:
> {noformat}
> register=Alpha:*******@sip.crffac.golden-era.co.za{noformat}
>
>
> Alpha shows the host for the registration as being '(null)' although DNS resolution is currently operational (interruption was 6+ hours ago):
> {noformat}
> alpha*CLI> iax2 show registry
> Host dnsmgr Username Perceived Refresh State
> (null) N Alpha <Unregistered> 60 Unregistered
> 1 IAX2 registrations.
> alpha*CLI> iax2 show peers
> Name/Username Host Mask Port Status Description
> Omega/Alpha 165.145.109.36 (D) 255.255.255.255 4569 (T) OK (27 ms)
> 1 iax2 peers [1 online, 0 offline, 0 unmonitored]
> {noformat}
> Omega correctly shows the Alpha peer as being unavailable, as it hasn't registered:
> {noformat}
> omega*CLI> iax2 show registry
> Host dnsmgr Username Perceived Refresh State
> 196.15.196.130:4569 N Omega 165.145.109.36:4569 60 Registered
> 1 IAX2 registrations.
> omega*CLI> iax2 show peers
> Name/Username Host Mask Port Status Description
> Alpha/Omega (null) (D) 255.255.255.255 0 (T) UNKNOWN
> 1 iax2 peers [0 online, 1 offline, 0 unmonitored]
> {noformat}
>
>
> Issuing a 'reload iax2' does absolutely nothing, only completely unloading the chan_iax2 module and reloading it restores operation:
> {noformat}
> alpha*CLI> module unload chan_iax2.so
> Unloaded chan_iax2.so
> alpha*CLI> module load chan_iax2.so
> Loaded chan_iax2.so
> alpha*CLI> iax2 show registry
> Host dnsmgr Username Perceived Refresh State
> 165.145.109.36:4569 Y Alpha 196.15.196.130:4569 60 Registered
> 1 IAX2 registrations.
> omega*CLI> iax2 show peers
> Name/Username Host Mask Port Status Description
> Alpha/Omega 196.15.196.130 (D) 255.255.255.255 4569 (T) OK (27 ms)
> 1 iax2 peers [1 online, 0 offline, 0 unmonitored]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list