[asterisk-bugs] [JIRA] (ASTERISK-26738) frequent segfaults since activation of DNS SRV

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26738:
------------------------------------------

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].

> frequent segfaults since activation of DNS SRV
> ----------------------------------------------
>
>                 Key: ASTERISK-26738
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26738
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.13.1
>         Environment: Centos 6 64bit
> FreePBX 13.0.190.7
> IPv4 and IPv6
> dual core processor
>            Reporter: Michael Maier
>            Severity: Critical
>
> After switching to DNS SRV w/ 5 parallel trunks I'm getting frequent segfaults like the attached one. Backtrace is built on base of patched Schmooze RPM source package:
> - Patch to get libasteriskpj.so.2 symbols
> - Patch from https://issues.asterisk.org/jira/browse/ASTERISK-26675
> Parallel running tcpdump shows, that REGISTER is sent at the time of the crash.
> In detail:
> - The DNS SRV entry has two hostnames (see https://issues.asterisk.org/jira/browse/ASTERISK-26735). All the time before the crash, ipaddress 217.0.23.108 is used for REGISTER.
> - At the moment of the crash, 2(!!) REGISTERS are sent nearly at the same time (0.01s difference) for the same trunk! The first to 217.0.23.140(!), the second to the usual 217.0.23.108. The answer from 217.0.23.108 comes first (200 ok), the answer from 217.0.23.140 comes 0.09s later and is 401 unauthorized. That's the end. Now the crash appears.



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