[asterisk-bugs] [JIRA] (ASTERISK-27384) DNS related segfault using pjsip and multiple DNS SRV records

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-27384:
----------------------------------------

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines



> DNS related segfault using pjsip and multiple DNS SRV records
> -------------------------------------------------------------
>
>                 Key: ASTERISK-27384
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27384
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.17.2
>         Environment: CentOS 6 64bit
>            Reporter: Michael Maier
>            Assignee: Joshua Colp
>         Attachments: core.myfw-2017-10-27T07-22-22+0200-brief.txt, core.myfw-2017-10-27T07-22-22+0200-full.txt, core.myfw-2017-10-27T07-22-22+0200-locks.txt, core.myfw-2017-10-27T07-22-22+0200-thread1.txt
>
>
> I encountered a segfault during normal usage. At the time the segfault appeared, no call has been processed. Asterisk was idle.
> All in all there are 5 trunks defined, using bundled pjsip. Three of them are Telekom trunks, using DNS SRV records:
> # nslookup -type=srv _sip._udp.tel.t-online.de
> Server:         192.168.x.y
> Address:        192.168.x.y#53
> Non-authoritative answer:
> _sip._udp.tel.t-online.de       service = 1 5 5060 d-epp-102.isp.t-ipnet.de.
> _sip._udp.tel.t-online.de       service = 0 5 5060 n-epp-102.isp.t-ipnet.de.
> Authoritative answers can be found from:
> d-epp-102.isp.t-ipnet.de        internet address = 217.0.28.101
> n-epp-102.isp.t-ipnet.de        internet address = 217.0.23.229
> There have been issues fixed like this? fixed some time ago: see ASTERISK-26738
> Unfortunately, I don't have any more information about this segfault as there was no log entry in the asterisk log nor in messages. I didn't run tcpdump at the time of the segfault, too.



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