[asterisk-bugs] [JIRA] (ASTERISK-29210) res_pjsip: Crash when examining transport

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-29210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-29210:
-------------------------------------

    Target Release Version/s: 18.2.0

> res_pjsip: Crash when examining transport
> -----------------------------------------
>
>                 Key: ASTERISK-29210
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29210
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 18.1.0
>         Environment: Debian 10( buster) on armv7l, dual core, 1400Mhz CPU, single SIP line.
>            Reporter: N GM 
>            Assignee: Unassigned
>            Severity: Minor
>      Target Release: 18.2.0
>
>         Attachments: backtrace.txt, debug_log_12_11_20, gdb.txt, pjsip.conf
>
>
> When starting Asterisk in daemon mode, using /usr/sbin/asterisk or /etc/init.d/asterisk start, daemon starts with no errors, but within a few second, ps shows that the daemon has crashed and that the process /usr/sbin/asterisk is no longer present. When started with -g option, produces a core dump. When started with /usr/sbin/safe_asterisk, produces continuous core dumps in /tmp.
> Interestingly, when started in CLI mode in foreground with /usr/sbin/asterisk -cvvvv, so far it has remained stable with no auto-shutdown or no core dump. SIP connection to SIP provider is established and voice calls work. More testing is perhaps needed to see if core dumps can be replicated in foreground.
> /var/log/asterisk/messages does not show any errors/warnings at the point of daemon crash/core dump.
> All testing is currently at halt and rollout to production status is on hold, due to these continuous core dumps.



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