VICIDIAL Asterisk Crash when call gets connected

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

VICIDIAL Asterisk Crash when call gets connected

Postby bobby » Thu Aug 09, 2007 7:30 am

Hi

I have asterisk running and h/w is an Intel Dual Core 2 with SATA Harddisk, 2GB RAM. My OS is Ubuntu. Asterisk version 1.2.18 and AstGuiClient version 2.0.3. Codecs used are g729 and ulaw. Only using VOIP.

Got VICIDial running around 20 days back. Been working more or less smoothly until today. I had calls getting stuck with the dialer not dialing but thanks to this forum I was able to clear the table in mysql and get the PD working again.

Since the last 2 days whenever the call gets connected the asterisk server crashes with a core dump. It was irregular initially but now it crashes on almost every instance when the call gets connected.

The messages are given below. The error occurs consistently each time whenever the call is connected to the agent. No sure where else to look. If any other log info is needed pl ask (and maybe tell me where to look also). Appreciate any help urgently. Thanks.

This is the messages i get on screen when the crash occurs:
Aug 8 08:09:30 NOTICE[6218]: member.c:415 member_exec: [ $Revision: 1.9 $ ] begin processing member thread, channel => SIP/abcdefgh-out0-007f3250
Aug 8 08:09:30 NOTICE[6218]: member.c:742 create_member: attempting to parse passed params, stringp => 8600052
Aug 8 08:09:30 NOTICE[6218]: member.c:793 create_member: parsed data params, id => 8600052, flags => , priority => 0, vad_prob_start => 0.050000, vad_prob_continue => 0.020000
Aug 8 08:09:30 NOTICE[6218]: member.c:1077 create_member: created member, type => S, priority => 0, readformat => 64
Aug 8 08:09:30 NOTICE[6218]: member.c:451 member_exec: CHANNEL INFO, CHANNEL => SIP/abcdefgh-out0-007f3250, DNID => (null), CALLER_ID => (null), ANI => xxxxxxxxxx
Aug 8 08:09:30 NOTICE[6218]: member.c:454 member_exec: CHANNEL CODECS, CHANNEL => SIP/abcdefgh-out0-007f3250, NATIVE => 256, READ => 256, WRITE => 256
Aug 8 08:09:30 NOTICE[6218]: conference.c:504 start_conference: attempting to find requested conference
Aug 8 08:09:30 NOTICE[6218]: conference.c:563 find_conf: found conference in conflist, name => 8600052
Aug 8 08:09:30 NOTICE[6218]: conference.c:796 add_member: member added to conference, name => 8600052
Aug 8 08:09:30 NOTICE[6218]: member.c:514 member_exec: begin member event loop, channel => SIP/abcdefgh-out0-007f3250
Aug 8 08:09:30 NOTICE[6218]: member.c:532 member_exec: Conference Members: 2
Aug 8 08:09:30 NOTICE[6218]: member.c:538 member_exec: Quiet debug 0 - 0
Aug 8 08:09:30 NOTICE[6218]: member.c:688 basic_play_sound: playing conference message enter
Aug 8 08:09:30 NOTICE[6218]: member.c:688 basic_play_sound: playing conference message enter
Aug 8 08:09:30 NOTICE[6218]: member.c:351 process_outgoing: unanticipated delivery time, delivery_diff => 1167596727, delivery.tv_usec => 423039
*** glibc detected *** asterisk: malloc(): memory corruption: 0x00000000007eb8e0 ***
======= Backtrace: =========
/lib/libc.so.6[0x2ba7c67e01d1]
/lib/libc.so.6(__libc_calloc+0x96)[0x2ba7c67e1636]
/usr/lib/asterisk/modules/app_conference.so(create_slinear_frame+0x1b)[0x2aaaaeefd8f3]
/usr/lib/asterisk/modules/app_conference.so(mix_multiple_speakers+0x2ce)[0x2aaaaeefd3a3]
/usr/lib/asterisk/modules/app_conference.so(mix_frames+0x4c)[0x2aaaaeefcf04]
/usr/lib/asterisk/modules/app_conference.so(conference_exec+0x8ad)[0x2aaaaeef7ead]
/lib/libpthread.so.0[0x2ba7c5c1f2a5]
/lib/libc.so.6(clone+0x6d)[0x2ba7c683f61d]
======= Memory map: ========
00400000-004e5000 r-xp 00000000 08:06 60902 /usr/sbin/asterisk
006e5000-006ee000 rw-p 000e5000 08:06 60902 /usr/sbin/asterisk
006ee000-008a0000 rw-p 006ee000 00:00 0 [heap]
40000000-40001000 ---p 40000000 00:00 0
40001000-40041000 rwxp 40001000 00:00 0
40041000-40042000 ---p 40041000 00:00 0
40042000-40082000 rwxp 40042000 00:00 0
40082000-40083000 ---p 40082000 00:00 0
40083000-400c3000 rwxp 40083000 00:00 0
400c3000-400c4000 ---p 400c3000 00:00 0
400c4000-40104000 rwxp 400c4000 00:00 0
40104000-40105000 ---p 40104000 00:00 0
40105000-40145000 rwxp 40105000 00:00 0
40145000-40146000 ---p 40145000 00:00 0
40146000-40186000 rwxp 40146000 00:00 0
40186000-40187000 ---p 40186000 00:00 0
40187000-401c7000 rwxp 40187000 00:00 0
401c7000-401c8000 ---p 401c7000 00:00 0
401c8000-40208000 rwxp 401c8000 00:00 0
40208000-40209000 ---p 40208000 00:00 0
40209000-40249000 rwxp 40209000 00:00 0
40249000-4024a000 ---p 40249000 00:00 0
4024a000-4028a000 rwxp 4024a000 00:00 0
4028a000-4028b000 ---p 4028a000 00:00 0
4028b000-402cb000 rwxp 4028b000 00:00 0
402cb000-402cc000 ---p 402cb000 00:00 0
402cc000-4030c000 rwxp 402cc000 00:00 0
4030c000-4030d000 ---p 4030c000 00:00 0
4030d000-4034d000 rwxp 4030d000 00:00 0
4034d000-4034e000 ---p 4034d000 00:00 0
4034e000-4038e000 rwxp 4034e000 00:00 0
4038e000-4038f000 ---p 4038e000 00:00 0
4038f000-403cf000 rwxp 4038f000 00:00 0
403cf000-403d0000 ---p 403cf000 00:00 0
403d0000-40410000 rwxp 403d0000 00:00 0
40410000-40411000 ---p 40410000 00:00 0
40411000-40451000 rwxp 40411000 00:00 0
40451000-40452000 ---p 40451000 00:00 0
40452000-40492000 rwxp 40452000 00:00 0
40492000-40493000 ---p 40492000 00:00 0
40493000-404d3000 rwxp 40493000 00:00 0
404d3000-404d4000 ---p 404d3000 00:00 0
404d4000-40514000 rwxp 404d4000 00:00 0
40514000-40515000 ---p 40514000 00:00 0
40515000-40555000 rwxp 40515000 00:00 0
40555000-40556000 ---p 40555000 00:00 0
40556000-40596000 rwxp 40556000 00:00 0
40596000-40597000 ---p 40596000 00:00 0
40597000-405d7000 rwxp 40597000 00:00 0
405d7000-405d8000 ---p 405d7000 00:00 0
405d8000-40618000 rwxp 405d8000 00:00 0
40618000-40619000 ---p 40618000 00:00 0
40619000-40659000 rwxp 40619000 00:00 0
40659000-4065a000 ---p 40659000 00:00 0
4065a000-40e5a000 rwxp 4065a000 00:00 0
40e5a000-40e5b000 ---p 40e5a000 00:00 0
40e5b000-40e9b000 rwxp 40e5b000 00:00 0
40e9b000-40e9c000 ---p 40e9b000 00:00 0
40e9c000-40edc000 rwxp 40e9c000 00:00 0
40edc000-40edd000 ---p 40edc000 00:00 0
40edd000-40f1d000 rwxp 40edd000 00:00 0
40f1d000-40f1e000 ---p 40f1d000 00:00 0
40f1e000-4171e000 rwxp 40f1e000 00:00 0
4171e000-4171f000 ---p 4171e000 00:00 0
4171f000-4175f000 rwxp 4171f000 00:00 0
2aaaaaaac000-2aaaaaaaf000 rw-p 2aaaaaaac000 00:00 0
2aaaaaaaf000-2aaaaaab6000 r-xp 00000000 08:06 60999 /usr/lib/asterisk/modules/res_musiconhold.so
2aaaaaab6000-2aaaaacb6000 ---p 00007000 08:06 60999 /usr/lib/asterisk/modules/res_musiconhold.so
2aaaaacb6000-2aaaaacb7000 rw-p 00007000 08:06 60999 /usr/lib/asterisk/modules/res_musiconhold.so
2aaaaacb7000-2aaaaacbb000 r-xp 00000000 08:06 60993 /usr/lib/asterisk/modules/res_indications.so
2aaaaacbb000-2aaaaaeba000 ---p 00004000 08Aborted (core dumped)
bobby
 
Posts: 9
Joined: Sun Jul 15, 2007 5:51 am

Postby mflorell » Thu Aug 09, 2007 8:08 am

What are you using Music on hold for?
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby bobby » Thu Aug 09, 2007 8:14 am

Not using it for anything on the outbound calls.

Want to use it in future for some inbound campaigns.

Currently nothing.
bobby
 
Posts: 9
Joined: Sun Jul 15, 2007 5:51 am

Postby ramindia » Thu Aug 09, 2007 12:15 pm

Hi

what is the hardware config ( Brand)

If assembled Intel Board Chipset, RAM ( what speed)

try to pull one of the GB RAM and Try alternative. i have come across this problem some time back with memory.


If you are having CentOS CD with you, try running Memory test on bootup.


ram
Kindly post your feedback, if this solution works.
so its very usefull for others who join later as a NEWBIE.
ramindia
 
Posts: 688
Joined: Wed Oct 11, 2006 4:06 am
Location: India

Postby gardo » Thu Aug 09, 2007 12:43 pm

I suggest installing the latest asterisk (1.2.23). There was a bug in the previous versions where asterisk crashes when dialing some kind of phone numbers. Can't exactly remember the details.
http://goautodial.com
Empowering the next generation contact centers
gardo
 
Posts: 1926
Joined: Fri Sep 15, 2006 10:24 am
Location: Manila, 1004

Postby bobby » Fri Aug 10, 2007 4:01 am

Hi

Still not able to resolve the issue - I tried trimming the database down - noticed the server performance tables had a lot of records. But yet the issue persists. In fact I cleared up the entire db and had it setup from the beginning. Same result.

I am trying to get some CD to test the Memory. Will let you know as soon as I get the results. btw its a locally assembled system - no particular brand. Was running smoothly so far. Hardware has been used for more than 6 months. The Asterisk part without vicidial works smoothly even now - calls continue to get routed and work. Its only when vicidial makes the calls and connects that the error happens.

Meanwhile how do I upgrade the Asterisk to the latest version - is there a documented upgrade path that I can follow?

Here is the latest set of messages. Does that last message of "process_outgoing: unanticipated delivery time....." give us any clue? Is this a time related issue? This issue has broken confidence in our mostly smooth experience with Asterisk over 20 days. I am clueless right now. Appreciate any help. Thanks.

Aug 10 03:37:18 NOTICE[10466]: member.c:454 member_exec: CHANNEL CODECS, CHANNEL => SIP/abcdefgh-out0-0079ad50, NATIVE => 256, READ => 256, WRITE => 256
Aug 10 03:37:18 NOTICE[10466]: conference.c:504 start_conference: attempting to find requested conference
Aug 10 03:37:18 NOTICE[10466]: conference.c:563 find_conf: found conference in conflist, name => 8600051
Aug 10 03:37:18 NOTICE[10466]: conference.c:796 add_member: member added to conference, name => 8600051
Aug 10 03:37:18 NOTICE[10466]: member.c:514 member_exec: begin member event loop, channel => SIP/abcdefgh-out0-0079ad50
Aug 10 03:37:18 NOTICE[10466]: member.c:532 member_exec: Conference Members: 2
Aug 10 03:37:18 NOTICE[10466]: member.c:538 member_exec: Quiet debug 0 - 0
Aug 10 03:37:18 NOTICE[10466]: member.c:688 basic_play_sound: playing conference message enter
Aug 10 03:37:18 NOTICE[10466]: member.c:688 basic_play_sound: playing conference message enter
Aug 10 03:37:18 NOTICE[10466]: member.c:351 process_outgoing: unanticipated delivery time, delivery_diff => 1324064667, delivery.tv_usec => 363674
bobby
 
Posts: 9
Joined: Sun Jul 15, 2007 5:51 am

Postby mflorell » Fri Aug 10, 2007 8:27 am

Is there a reason you are using app_conference? It is unstable and currently unsupported. app_meetme is much more stable.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby bobby » Fri Aug 10, 2007 2:04 pm

Matt

don't have the zaptel hw so do you think i can still use the ztdummy for the Meetme?

thanks
bobby
 
Posts: 9
Joined: Sun Jul 15, 2007 5:51 am

Postby mflorell » Fri Aug 10, 2007 4:13 pm

If you keep the load low you should not have issues with meetme, If you experience problems I would recommend getting a hardware timer, there is a cheap X100P available for $10-$40 that does a very good job at that.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby ramindia » Fri Aug 10, 2007 11:54 pm

Hi

you can use any one depends on requirements

for high load recomended to use X100P as a zaptel source

ram
Kindly post your feedback, if this solution works.
so its very usefull for others who join later as a NEWBIE.
ramindia
 
Posts: 688
Joined: Wed Oct 11, 2006 4:06 am
Location: India


Return to Support

Who is online

Users browsing this forum: sofianemh and 139 guests