[asterisk-bugs] [JIRA] (ASTERISK-26883) pjsip DNS SRV: missing auto generated match entry if DNS temporarily fails on startup

Rusty Newton (JIRA) noreply at issues.asterisk.org
Wed Mar 22 09:01:10 CDT 2017


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

Rusty Newton edited comment on ASTERISK-26883 at 3/22/17 9:00 AM:
------------------------------------------------------------------

Well, it's pretty trivial. Make a local DNS server to not respond (e.g. with iptables) and start asterisk:
{noformat}
[2017-03-18 07:53:58] ERROR[1967] netsock2.c: getaddrinfo("tel.t-online.de", "(null)", ...): Temporary failure in name resolution
[2017-03-18 07:53:58] ERROR[1967] res_pjsip_endpoint_identifier_ip.c: An error occurred when adding resolution results of 'tel.t-online.de' on 'telekomPJSIP'
[2017-03-18 07:53:58] ERROR[1967] res_sorcery_config.c: Could not create an object of type 'identify' with id 'telekomPJSIP' from configuration file 'pjsip.conf'
[2017-03-18 07:54:00] WARNING[2155] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:+4911111111111 at tel.t-online.de', retrying in '60'
[2017-03-18 07:54:08] ERROR[2155] res_pjsip.c: Error 320052 'DNS "Server failure" (PJLIB_UTIL_EDNS_SERVFAIL)' sending OPTIONS request to endpoint telekomPJSIP
{noformat}

About 2 or 3 minutes later, re enable the resolver again by removing the iptable rules and pjsip will register to the ISP successfully. But the auto generated match entries will stay empty.

I'm using bundled pjsip (see http://lists.digium.com/pipermail/asterisk-dev/2017-March/076202.html and http://lists.digium.com/pipermail/asterisk-dev/2017-March/076215.html)



was (Author: micha):
Well, it's pretty trivial. Make a local DNS server to not respond (e.g. with iptables) and start asterisk:

[2017-03-18 07:53:58] ERROR[1967] netsock2.c: getaddrinfo("tel.t-online.de", "(null)", ...): Temporary failure in name resolution
[2017-03-18 07:53:58] ERROR[1967] res_pjsip_endpoint_identifier_ip.c: An error occurred when adding resolution results of 'tel.t-online.de' on 'telekomPJSIP'
[2017-03-18 07:53:58] ERROR[1967] res_sorcery_config.c: Could not create an object of type 'identify' with id 'telekomPJSIP' from configuration file 'pjsip.conf'
[2017-03-18 07:54:00] WARNING[2155] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:+4911111111111 at tel.t-online.de', retrying in '60'
[2017-03-18 07:54:08] ERROR[2155] res_pjsip.c: Error 320052 'DNS "Server failure" (PJLIB_UTIL_EDNS_SERVFAIL)' sending OPTIONS request to endpoint telekomPJSIP

About 2 or 3 minutes later, re enable the resolver again by removing the iptable rules and pjsip will register to the ISP successfully. But the auto generated match entries will stay empty.

I'm using bundled pjsip (see http://lists.digium.com/pipermail/asterisk-dev/2017-March/076202.html and http://lists.digium.com/pipermail/asterisk-dev/2017-March/076215.html)


> pjsip DNS SRV: missing auto generated match entry if DNS temporarily fails on startup
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26883
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26883
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.14.0
>         Environment: CentOS 6, 64bit
>            Reporter: Michael Maier
>            Assignee: Unassigned
>
> If on startup of asterisk DNS temporarily fails, no match entry is generated, resulting in silently dropped inbound calls later on, because pjsip retries e.g. every 60s and establishes a working connection to ISP as soon DNS is working again.
> As I detected this problem about 3 hours after starting of asterisk, I'm assuming that changes of DNS lookups later on aren't recognized, too, resulting again in silently dropped inbound calls.
> Therefore, the requirement is to always be synchronous with the IP addresses used by pjsip.
> Make a local DNS server to not respond (e.g. with iptables) and start asterisk:
> {noformat}
> [2017-03-18 07:53:58] ERROR[1967] netsock2.c: getaddrinfo("tel.t-online.de", "(null)", ...): Temporary failure in name resolution
> [2017-03-18 07:53:58] ERROR[1967] res_pjsip_endpoint_identifier_ip.c: An error occurred when adding resolution results of 'tel.t-online.de' on 'telekomPJSIP'
> [2017-03-18 07:53:58] ERROR[1967] res_sorcery_config.c: Could not create an object of type 'identify' with id 'telekomPJSIP' from configuration file 'pjsip.conf'
> [2017-03-18 07:54:00] WARNING[2155] res_pjsip_outbound_registration.c: No response received from 'sip:tel.t-online.de' on registration attempt to 'sip:+4911111111111 at tel.t-online.de', retrying in '60'
> [2017-03-18 07:54:08] ERROR[2155] res_pjsip.c: Error 320052 'DNS "Server failure" (PJLIB_UTIL_EDNS_SERVFAIL)' sending OPTIONS request to endpoint telekomPJSIP
> {noformat}
> About 2 or 3 minutes later, re enable the resolver again by removing the iptable rules and pjsip will register to the ISP successfully. But the auto generated match entries will stay empty.
> I'm using bundled pjsip (see http://lists.digium.com/pipermail/asterisk-dev/2017-March/076202.html and http://lists.digium.com/pipermail/asterisk-dev/2017-March/076215.html)



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



More information about the asterisk-bugs mailing list