[asterisk-bugs] [JIRA] (ASTERISK-17171) [patch] Each time a device sends a REGISTER, the error "No address associated with nodename" appears

[Sean Bright (JIRA)]

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

Sean Bright closed ASTERISK-17171.
----------------------------------

    Resolution: Cannot Reproduce

Modern versions of macOS (and FreeBSD) now return {{EAI_NONAME}} instead of {{EAI_NODATA}}, so this patch is no longer applicable.

> [patch] Each time a device sends a REGISTER, the error "No address associated with nodename" appears
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-17171
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17171
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/Netsock
>            Reporter: John Covert
>              Labels: patch
>         Attachments: addr.c, netsock2.c.2011-01-13.patch, netsock2.c.patch
>
>
> The following messages appear continuously:
> {noformat}
> sip_uri_domain_cmp sip.covert.org - sip.covert.org
> [Dec 28 10:59:23] ERROR[13395]: netsock2.c:205 ast_sockaddr_parse: getaddrinfo("sip.covert.org", "(null)", ...): No address associated with nodename
> [Dec 28 10:59:23] ERROR[13395]: netsock2.c:205 ast_sockaddr_parse: getaddrinfo("sip.covert.org", "(null)", ...): No address associated with nodename
> {noformat}
> This is because "If the AI_NUMERICHOST bit is set in the ai_flags member of the hints structure, then a non-NULL nodename string must be a numeric host address string. Otherwise an error of EAI_NONAME is returned. This flag prevents any type of name resolution service (e.g., the DNS) from being called."
> See http://www.manpages.info/macosx/getaddrinfo.3.html
> Patch supplied to eliminate the message on Darwin.
> ****** STEPS TO REPRODUCE ******
> simply allow devices to register which have specified a hostname.



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