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

[Alex Hermann (JIRA)]

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

Alex Hermann commented on ASTERISK-27384:
-----------------------------------------

I don't know if it is the cause of the problems, but your SRV records are invalid. The target of an SRV record MUST NOT be an alias (rfc2782).

$ host -t srv _sip._udp.tel.t-online.de
_sip._udp.tel.t-online.de has SRV record 1 5 5060 ims002.voip.t-ipnet.de.
_sip._udp.tel.t-online.de has SRV record 0 5 5060 ims001.voip.t-ipnet.de.

$ host ims001.voip.t-ipnet.de.
ims001.voip.t-ipnet.de is an alias for b-epp-001.isp.t-ipnet.de.

$ host ims002.voip.t-ipnet.de.
ims002.voip.t-ipnet.de is an alias for h-epp-001.isp.t-ipnet.de.


> 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: Michael Maier
>         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)