[Home]

Summary:ASTERISK-27384: DNS related segfault using pjsip and multiple DNS SRV records
Reporter:Michael Maier (micha)Labels:
Date Opened:2017-10-31 09:57:29Date Closed:2017-12-20 06:13:51.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:13.17.2 Frequency of
Occurrence		One Time
Related
Issues:
Environment:CentOS 6 64bitAttachments:( 0) core.myfw-2017-10-27T07-22-22+0200-brief.txt
( 1) core.myfw-2017-10-27T07-22-22+0200-full.txt
( 2) core.myfw-2017-10-27T07-22-22+0200-locks.txt
( 3) core.myfw-2017-10-27T07-22-22+0200-thread1.txt
Description: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.
Comments:By: Asterisk Team (asteriskteam) 2017-10-31 09:57:30.438-0500

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].
By: George Joseph (gjoseph) 2017-10-31 16:30:34.976-0500

Are you using bundled or external pjproject?
Was this a one-time crash or has it happened multiple times?  Not that one-time is any better, just trying to get a feel for what's going on.
Were there any DNS infrastructure issues at the time that you know about?

By: Michael Maier (micha) 2017-10-31 16:52:15.020-0500

Are you using bundled or external pjproject?
-> bundled

Was this a one-time crash or has it happened multiple times?
-> one-time

Were there any DNS infrastructure issues at the time that you know about?
-> Unfortunately, I don't know of any.
By: Alex Hermann (gaaf) 2017-12-01 10:14:09.008-0600

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.

By: Joshua C. Colp (jcolp) 2017-12-05 12:36:51.295-0600

The logs shows that the underlying transport may have been missing or invalid, the information provided doesn't explain why that would occur. We would also need to see the Asterisk log information with verbose and debug to explain what happened.
By: Joshua C. Colp (jcolp) 2017-12-20 06:13:37.682-0600

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