[asterisk-bugs] [JIRA] (ASTERISK-26746) pjsip: Repeated segfaults with not responding nameserver

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Jan 24 06:26:10 CST 2017


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

Asterisk Team commented on ASTERISK-26746:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> pjsip: Repeated segfaults with not responding nameserver
> --------------------------------------------------------
>
>                 Key: ASTERISK-26746
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26746
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.13.1
>         Environment: Centos 6
> dual core processor
> FreePBX 13.0.190.7
>            Reporter: Michael Maier
>
> Asterisk was started while DNS was not functional: local named (configured in /etc/resolv.conf) was reachable, but named couldn't resolve any hostnames, because of broken INPUT iptables rules (the answer of the provider DNS was never seen by named). Therefore request timed out.
> There have been trunks configured using SRV and not SRV entries. I can't say, which of both types (or even both) caused the segfaults. Unfortunately, no debug was activated at the time the crashes appeared.



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



More information about the asterisk-bugs mailing list