[Home]

Summary:ASTERISK-27256: Segfault while sending unsolicited MWI
Reporter:Ross Beer (rossbeer)Labels:pjsip
Date Opened:2017-09-06 07:43:04Date Closed:2019-02-07 04:54:18.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip_mwi
Versions:13.17.1 13.21.0 GIT Frequency of
Occurrence
Frequent
Related
Issues:
is duplicated byASTERISK-27302 Segfault grp_lock_acquire while processing endpoint event
is duplicated byASTERISK-28054 Asterisk Core dumping on regular basis 13.21.1
Environment:Fedora 23 and CentOS 7Attachments:( 0) core-asterisk-103187-1506506276-thread1.txt
( 1) core-asterisk-151140-thread1.txt
( 2) core-asterisk-97004.txt
( 3) TimerCrash_01.txt
Description:Segfault when generating out of dialog unsolicited MWI:

{noformat}
0  0x00007f901a2d21e0 in pop_freelist (ht=0x1a821d0) at ../src/pj/timer.c:149
       new_id = -1313818704
#1  0x00007f901a2d29d2 in schedule_entry (ht=0x1a821d0, entry=0x7f8cb9411948, future_time=0x7f8d624293f0) at ../src/pj/timer.c:312
#2  0x00007f901a2d2e82 in schedule_w_grp_lock (ht=0x1a821d0, entry=0x7f8cb9411948, delay=0x7f901a5256c0 <t1_timer_val>, set_id=1, id_val=1, grp_lock=0x7f8ca8d16e68) at ../src/pj/timer.c:514
       status = 0
       expires = {sec = 16946142, msec = 855}
#3  0x00007f901a2d2f51 in pj_timer_heap_schedule_w_grp_lock (ht=0x1a821d0, entry=0x7f8cb9411948, delay=0x7f901a5256c0 <t1_timer_val>, id_val=1, grp_lock=0x7f8ca8d16e68) at ../src/pj/timer.c:567
#4  0x00007f901a241325 in tsx_schedule_timer (tsx=0x7f8cb94117c8, entry=0x7f8cb9411948, delay=0x7f901a5256c0 <t1_timer_val>, active_id=1) at ../src/pjsip/sip_transaction.c:981
       timer_heap = 0x1a821d0
       status = 0
#5  0x00007f901a243c90 in tsx_on_state_null (tsx=0x7f8cb94117c8, event=0x7f8d624294e0) at ../src/pjsip/sip_transaction.c:2459
       tdata = 0x7f8ed090be98
       status = 0
#6  0x00007f901a2429d7 in pjsip_tsx_send_msg (tsx=0x7f8cb94117c8, tdata=0x7f8ed090be98) at ../src/pjsip/sip_transaction.c:1789
       event = {prev = 0x10, next = 0x7f8cb94117a0, type = PJSIP_EVENT_TX_MSG, body = {timer = {entry = 0x7f8ed090be98}, tsx_state = {src = {rdata = 0x7f8ed090be98, tdata = 0x7f8ed090be98, timer = 0x7f8ed090be98, status = -795820392, data = 0x7f8ed090be98}, tsx = 0x7f8d62429530, prev_state = 439113248, type = 32656}, tx_msg = {tdata = 0x7f8ed090be98}, tx_error = {tdata = 0x7f8ed090be98, tsx = 0x7f8d62429530}, rx_msg = {rdata = 0x7f8ed090be98}, user = {user1 = 0x7f8ed090be98, user2 = 0x7f8d62429530, user3 = 0x7f901a2c5620 <pj_pool_alloc+39>, user4 = 0x10}}}
       status = 32652
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2017-09-06 07:43:06.217-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: Rusty Newton (rnewton) 2017-09-06 17:57:29.455-0500

Thanks for the report.

I'm guessing you were not able to get a debug log or reproduce it?

By: Asterisk Team (asteriskteam) 2017-09-21 12:00:04.435-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. 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

By: Ross Beer (rossbeer) 2017-09-27 05:51:12.466-0500

Another segfault just occurred while attempting to send unsolicited MWI with chan_pjsip. Please see the attached backtrace.

By: Richard Mudgett (rmudgett) 2017-09-27 10:50:24.923-0500

What is the version in use for the latest backtraces?

By: Ross Beer (rossbeer) 2017-09-27 15:40:27.604-0500

Latest backtrace was using GIT Asterisk GIT-13-13.15.0-rc1-351-gf75f7b7M

By: Ross Beer (rossbeer) 2018-06-25 04:15:25.646-0500

This issue is still occurring when sending unsolicited MWI

By: Ross Beer (rossbeer) 2018-07-12 10:16:37.449-0500

This issue is still occurring in the latest release

By: ADTopkek (ADTopkek) 2018-09-24 08:13:01.102-0500

My ticket just got closed and merged into this one: ASTERISK-28054

We had it happen to 15.5.0. We set all voicemails to Unsolicited because solicited caused the phones voicemails to flicker on and off randomly along with showing voicemails that didn't exist, driving people crazy.