| Summary: | ASTERISK-13542: crash when setting an incoming call via SIP | ||
| Reporter: | Eldad Ran (eldadran) | Labels: | |
| Date Opened: | 2009-02-09 09:43:13.000-0600 | Date Closed: | 2011-06-07 14:00:29 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) console.txt ( 1) core_dump.txt | |
| Description: | The system crash while settingup a call. This is a brand new system, it not in production yet. while doing a single test call, the system crash on me. I'll attach the core dump and the consoledump while in full debug mode ****** ADDITIONAL INFORMATION ****** Ver 1.4.23.1 | ||
| Comments: | By: Joshua C. Colp (jcolp) 2009-02-09 14:32:57.000-0600 Can you please attach the dialplan this is executing and complete console output? The error 127 is actually for a symbol resolution issue, meaning something tried to use a function that could not be resolved. By: Eldad Ran (eldadran) 2009-02-09 15:03:24.000-0600 As per your request the relevant dialplan, as for the console, this is all I got, I was set full debug (core set debug 10; core set verbose 10; sip set debug) [bezeqint_inbound] exten => 039370000,1,NoOp(Start) exten => 039370000,n,Ringing() exten => 039370000,n,Goto(forward,s,1) [forward] exten => s,1,NoOp('Forward ${EXTEN} to ${TC_FRWDNAME} with ${accountcode} - ${DNID}') exten => s,n,SIPAddHeader(X-TC-accountcode: ${accountcode}) exten => s,n,SIPAddHeader(X-TC-API: 'WS') exten => s,n,SIPAddHeader(X-TC-FRWD: 1) exten => s,n,Progress() exten => s,n,Dial(SIP/039370000@tc014-146) exten => h,1,DeadAGI(frwd_clean.php) ; Call hangup termination exten => h,n,Hangup exten => t,1,DeadAGI(frwd_clean.php) ; Call absulote timeout termination exten => t,n,Hangup exten => T,1,DeadAGI(frwd_clean.php) ; Call timeout termination exten => T,n,Hangup exten => i,1,DeadAGI(frwd_clean.php) ; Invalid exten => i,n,Hangup(34) By: Eldad Ran (eldadran) 2009-02-09 15:06:43.000-0600 I just found out that the core dump is an old one, from the 4th of February, while the today crash had not generated any core dump, it just crash. How do I force it to generate one? By: Joshua C. Colp (jcolp) 2009-02-09 15:20:07.000-0600 It's not a crash. It's trying to find a function and failing, so it exits. Can you please start Asterisk from the console instead of a script, place a call, and attach that? I think it will say what symbol it is looking for. By: Eldad Ran (eldadran) 2009-02-09 15:25:43.000-0600 I ran asterisk directly from the terminal and not via safe_asterisk and I get this error: *CLI> asterisk: symbol lookup error: /usr/lib/asterisk/modules/chan_sip.so: undefined symbol: ast_pickup_ext I had a look and it looks like res_features.so was not loaded on my machine, loading it fixed the crash, is there any dependence mechanism that should kick in log it to a file and warn the user? By: Joshua C. Colp (jcolp) 2009-02-10 13:15:46.000-0600 Closed since this was a module not being loaded issue. As for a dependence mechanism there isn't one in 1.4, but in later versions things have been changed around so that it exists in the core (thus not as a module). | ||