vicidial.org

Hi

I kept on experiencing this when I have patched the asterisk to use with sangoma.

Disconnected from Asterisk server

/usr/sbin/safe_asterisk: line 57: 1565 Segmentation fault (core dumped) ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} </dev/${TTY}

Asterisk ended with exit status 139

Asterisk exited on signal 11.

I was quite bummed by this. I used 1.2.31 to patch it with sangoma and it kept on crashing so I reverted it back to 1.2.30.2 with the sangoma patch thinking 1.2.31.1 sucks and still crashes

*note even sangoma call analyzer on a quad core/win2003 server kept on crashing but im talking with them about it.

Why are you using safe_asterisk?

I believe the patch was written for 1.2.30.2 and the 1.4 patch was written for 1.4.21.2

I think somebody set it as a service in case it disconnects.

as before I was so used to issuing asterisk -g when something breaks.

anyhow I found the culprit on why the hell it is crashing or so I though so.

It is because I am using the gsm gcc 4.2 patch and my gcc is just 4.1 lol

Its just one of those weeks that everything seems to suck big hairy balls.

I hate it when that happens

Now we are trying it again and it worked for a whole shift then when second shift began

I saw this and made me close my eyes

(11 headers 10 lines) ---
Found RTP audio format 0
Found RTP audio format 101
Peer audio RTP is at port 208.64.4.21:21600
Found description format PCMU
Found description format telephone-event
Capabilities: us - 0x104 (ulaw|g729), peer - audio=0x4 (ulaw)/video=0x0 (nothing), combined - 0x4 (ulaw)
Non-codec capabilities: us - 0x1 (telephone-event), peer - 0x1 (telephone-event), combined - 0x1 (telephone-event)
Segmentation fault (core dumped)


I keep seeing this too.

May 12 13:45:39 WARNING[27915]: channel.c:2290 ast_write: Thread 63052688 Blocki ng 'IAX2/Asterisk1-1502', already blocked by thread 18971536 in procedure ast_wa itfor_nandfds
May 12 13:45:39 WARNING[27915]: channel.c:2290 ast_write: Thread 63052688 Blocki ng 'Local/58600055@default-c388,2', already blocked by thread 31247248 in proced ure ast_waitfor_nandfds

Wow, a segfault, that's a new one, although we only ever ran it on Ulaw.

As for the WARNING blocking issue, how ofter do you see that?

Are you doing recording?

Are people pressing DTMF keys much?

for the warning I see it every time now. more so because we are using 8368 which means we are load balancing

yes we are recording all the calls.

pressing dtmf have an impact on asterisk as well? I guess we are calling businesses so maybe sometimes if the sangoma doesnt detected the ivr they are pressing dtmf.


Ill post more if I encountered anything.

have you checked your core to find your dump reason?

Ok

I removed the sangoma patch.

This is my step on installing asterisk

wget http://downloads.digium.com/pub/asteris ... 0.2.tar.gz
gunzip asterisk-1.2.30.2.tar.gz
tar xvf asterisk-1.2.30.2.tar
cd asterisk-1.2.30.2
cd apps
wget http://www.eflo.net/files/app_amd2.c
mv app_amd2.c app_amd.c

nano Makefile
add app_amd.so when you see this line
app_mixmonitor.so app_stack.so

wget http://www.eflo.net/files/meetme_DTMF_p ... 2.23.patch
patch -p1 < meetme_DTMF_passthru-1.2.23.patch
wget http://www.eflo.net/files/meetme_volume ... 2.16.patch
patch -p1 < ./meetme_volume_control_1.2.16.patch
- File to patch: app_meetme.c
cd ../
wget http://www.eflo.net/files/cli_chan_conc ... iter.patch
patch -p1 < ./cli_chan_concise_delimiter.patch
- File to patch: cli.c
wget http://download.vicidial.com/asterisk-p ... rsilence.c
mv -f app_waitforsilence.c apps/app_waitforsilence.c

make clean
make
make install

so anyway, asterisk is not crashing after that

I really wanted sangoma cpa work on that installation. I have seen the gains on having this working with vicidial and performance is really there.

I better contact sangoma about it also.

We haven't had these problems at all with the CPA patch. Have you tried 1.4.21.2 at all?

now that's an interesting thing. Do i really need to compile 1.4 now?

I better contact mike now for help on that matter.

We have instructions for 1.4.21.2 in the REQUIRED_APPS.txt file.