Summary:ASTERISK-21678: IPv6-configured sip channel transmits to (null) for IPv4 register= hosts
Reporter:Olle Johansson (oej)Labels:
Date Opened:2013-04-24 11:06:18Date Closed:
Versions: 11.23.1 13.11.2 Frequency of
Description:SIP.conf binds to a specific IPv6 address only.

One register= line refers to a host that only has IPv4 addresses.

The SIP channel is trying repeatedly to transmit to (null)

[Apr 24 18:04:51] WARNING[27634]: acl.c:590 resolve_first: Unable to lookup 'host.example.com'

is output, but the SIP channel tries to register anyway.
Comments:By: Olle Johansson (oej) 2013-04-25 02:46:28.930-0500

Rusty, I did not accept any assignment to me on this bug ;-)

By: Alexander Traud (traud) 2016-09-28 09:38:14.203-0500

Olle, I am browsing through the IPv6 issues currently. I am able to confirm your reported issue still today in Asterisk 13.11.2:{noformat}  ERROR: netsock2.c: ast_sockaddr_resolve: getaddrinfo("secure.dus.net", "(null)", ...): Name or service not known
WARNING:      acl.c:        resolve_first: Unable to lookup 'secure.dus.net'
WARNING: chan_sip.c:    transmit_register: Probably a DNS error for registration to user@secure.dus.net, trying REGISTER again (after 20 seconds)
NOTICE: chan_sip.c:      sip_reg_timeout:    -- Registration for 'user@secure.dus.net' timed out, trying again (Attempt #2){noformat}Asterisk is trying again and again waiting for that register statement to be removed (or the DNS entry of that server to be updated with a Dual Stack configuration). Therefore, please explain which behavior you expect instead and which issues the current behavior cause. Should Asterisk fail and not try again? Or should the time period be longer than 20 seconds?