VD_app_conference Error

[austin.rock9]

Is there anybody who has used app_conference. I m gettting the below error in the asterisk cli. And when the LIVE call is connected my asterisk stop automatically. Please is there anybody who can help me.

> Channel SIP/1111-2800 was answered.
-- Executing Conference("SIP/1111-2800", "8600052") in new stack
Jul 17 13:49:05 NOTICE[6064]: member.c:415 member_exec: [ $Revision: 1.9 $ ] begin processing member thread, channel => SIP/1111-2800
Jul 17 13:49:05 NOTICE[6064]: member.c:742 create_member: attempting to parse passed params, stringp => 8600052
Jul 17 13:49:05 NOTICE[6064]: member.c:793 create_member: parsed data params, id => 8600052, flags => , priority => 0, vad_prob_start => 0.050000, vad_prob_continue => 0.020000
Jul 17 13:49:05 NOTICE[6064]: member.c:1077 create_member: created member, type => S, priority => 0, readformat => 256
Jul 17 13:49:05 NOTICE[6064]: member.c:451 member_exec: CHANNEL INFO, CHANNEL => SIP/1111-2800, DNID => (null), CALLER_ID => (null), ANI => (null)
Jul 17 13:49:05 NOTICE[6064]: member.c:454 member_exec: CHANNEL CODECS, CHANNEL => SIP/1111-2800, NATIVE => 256, READ => 256, WRITE => 256
Jul 17 13:49:05 NOTICE[6064]: conference.c:504 start_conference: attempting to find requested conference
Jul 17 13:49:05 NOTICE[6064]: conference.c:548 find_conf: conflist has not yet been initialized, name => 8600052
Jul 17 13:49:05 NOTICE[6064]: conference.c:511 start_conference: attempting to create requested conference
Jul 17 13:49:05 NOTICE[6064]: conference.c:583 create_conf: entered create_conf, name => 8600052
Jul 17 13:49:05 WARNING[6064]: translate.c:116 ast_translator_build_path: No translator path from unknown to unknown
Jul 17 13:49:05 WARNING[6064]: translate.c:116 ast_translator_build_path: No translator path from unknown to unknown
Jul 17 13:49:05 WARNING[6064]: translate.c:116 ast_translator_build_path: No translator path from unknown to unknown
Jul 17 13:49:05 WARNING[6064]: translate.c:116 ast_translator_build_path: No translator path from unknown to unknown
Jul 17 13:49:05 WARNING[6064]: translate.c:116 ast_translator_build_path: No translator path from unknown to unknown
Jul 17 13:49:05 WARNING[6064]: translate.c:116 ast_translator_build_path: No translator path from unknown to unknown
Jul 17 13:49:05 NOTICE[6064]: conference.c:796 add_member: member added to conference, name => 8600052
Jul 17 13:49:05 NOTICE[6064]: conference.c:646 create_conf: added new conference to conflist, name => 8600052
Jul 17 13:49:05 NOTICE[6064]: conference.c:663 create_conf: started conference thread for conference, name => 8600052
Jul 17 13:49:05 NOTICE[6064]: member.c:514 member_exec: begin member event loop, channel => SIP/1111-2800
Jul 17 13:49:05 NOTICE[6064]: member.c:532 member_exec: Conference Members: 1
Jul 17 13:49:05 NOTICE[6064]: member.c:538 member_exec: Quiet debug 0 - 0
Jul 17 13:49:05 NOTICE[6064]: member.c:546 member_exec: skipping entry message on SIP/1111-2800
Jul 17 13:49:05 NOTICE[6064]: member.c:688 basic_play_sound: playing conference message conf-onlyperson
Jul 17 13:49:05 NOTICE[6066]: conference.c:53 conference_exec: [ $Revision: 1.7 $ ] entered conference_exec, name => 8600052
Jul 17 13:49:06 NOTICE[6064]: member.c:351 process_outgoing: unanticipated delivery time, delivery_diff => 2073110658, delivery.tv_usec => 986928
== Manager 'sendcron' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'updatecron' logged on from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing Monitor("Local/919179695254@default-df00,2", "gsm|20060717-134909_0000000000_919179695254") in new stack
-- Executing Dial("Local/919179695254@default-df00,2", "SIP/0109#0019179695254@221.135.102.100||tTo") in new stack
-- Called 0109#0019179695254@221.135.102.100
-- SIP/221.135.102.100-37ce is making progress passing it to Local/919179695254@default-df00,2

[mflorell]

There were no ERRORs in the log you posted, only NOTICEs and WARNINGs. Where does your Asterisk session crash? I see no crash in these logs. And if there is a crash you need to do a full backtrace through gdb.

Remember that app_conference is experimental. The developers are working on the memory issues and it isn't proven as stable in production as meetme is.