Summary: | ASTERISK-14142: Segmentation fault with incoming calls | ||
Reporter: | fishticky (fishticky) | Labels: | |
Date Opened: | 2009-05-15 16:35:34 | Date Closed: | 2009-05-29 12:50:36 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Addons/chan_mobile |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | For this issue, my chan_mobile version is 1.6.2, and my asterisk version is 1.6.2(beta2) Having had problems with dtmf being accepted for incoming calls using chan_mobile v. 1.6.1 and asterisk v. 1.6.1, I upgraded both to version 1.6.2. However, now 90% of the time any incoming call is received, asterisk immediately shuts down, and a segmentation fault occurs (however, in the 10% of the time that it works, everything works perfectly during the duration of the call, including dtmf) My extensions.conf file is as follows: [my-phone] exten => s,1,Answer() exten => s,n,Wait(1) exten => s,n,Authenticate(1234) exten => s,n,Background(vm-enter-num-to-call) exten => s,n,Wait(1) exten => s,n,Hangup() Using gdb, here is the backtrace of the core that is saved after the segfault: #0 0x00272c4d in __i686.get_pc_thunk.bx () from /usr/lib/asterisk/modules/chan_mobile.so #1 0x00000010 in ?? () #2 0x004ce391 in pthread_mutex_lock () from /lib/libpthread.so.0 #3 0x080971d1 in ast_raw_answer (chan=0x9af2d20, cdr_answer=1) at channel.c:1771 #4 0x0809a764 in __ast_answer (chan=0x9af2d20, delay=0, cdr_answer=1) at channel.c:1789 ASTERISK-1 0x080fd066 in handle_set_extenpatternmatchnew (e=0x9af2d20, cmd=160475728, a=0x493180) at pbx.c:6263 ASTERISK-2 0x080fc19f in device_state_cb (event=0x9af2d20, unused=0x9900150) at pbx.c:9218 ASTERISK-3 0x08108f9d in pbx_extension_helper (c=0x9af2d20, con=0x0, context=<value optimized out>, exten=0x9af2fe0 "s", priority=1, label=0x0, callerid=0x990a848 "5109192759", action=E_SPAWN, found=0xb756b338, combined_find_spawn=1) at pbx.c:3730 ASTERISK-4 0x0810b5d4 in manager_show_dialplan_helper (s=0xc, m=0x3b9bb0, actionidtext=0x0, context=0x9af2820 "pbx_thread", ' ' <repeats 11 times>, "started at [ 4541] pbx.c ast_pbx_start()", exten=0x0, dpc=0xb756b3b8, rinclude=0x814dcdb) at pbx.c:5973 ASTERISK-5 0x0810d190 in __ast_pbx_run (c=0x0, args=0x0) at pbx.c:4296 ASTERISK-6 0x0814dcdb in dummy_start (data=0x990aac8) at utils.c:949 ASTERISK-7 0x004cc45b in start_thread () from /lib/libpthread.so.0 ASTERISK-8 0x00423e5e in clone () from /lib/libc.so.6 | ||
Comments: | By: fishticky (fishticky) 2009-05-15 16:50:54 I forgot to add, the phone model is a samsung sgh-x820 By: Matthew Nicholson (mnicholson) 2009-05-15 16:55:32 Try the latest SVN from addons branch 1.6.2. There were some fixes from trunk that I neglected to merge. By: fishticky (fishticky) 2009-05-28 13:39:58 Ok, I will try that soon. One thing I should mention, is that this problem ONLY happens on the samsung sgh-x820. I tried this on three other cell phones (all Nokia), and this issue did not occur again. By: fishticky (fishticky) 2009-05-29 12:46:26 Yup, it seems that the new asterisk-addons branch did fix the segmentation faults resulting from the sgh-x820 phone. As far as I'm concerned, this issue is resolved... |