I get from backtrace: Thread 168 (Thread 0x7fb5122be700 (LWP 1411)): #0 0x00007fb57e0cdf0d in poll () from /lib64/libc.so.6 #1 0x00000000004b245c in ast_waitfor_nandfds (c=0x7fb554081db8, n=1, fds=0x7fb554081e50, nfds=1, exception=0x0, outfd=0x7fb5122b6c50, ms=0x7fb5122b6c54) at channel.c:3170 #2 0x0000000000484b87 in bridge_channel_wait (bridge_channel=0x7fb554081d80) at bridge_channel.c:2602 #3 0x00000000004853b1 in bridge_channel_internal_join (bridge_channel=0x7fb554081d80) at bridge_channel.c:2768 #4 0x000000000046b949 in ast_bridge_join (bridge=0x7fb554080590, chan=0x7fb560285300, swap=0x0, features=0x7fb5122b6dc0, tech_args=0x0, flags=(AST_BRIDGE_JOIN_PASS_REFERENCE | AST_BRIDGE_JOIN_INHIBIT_JOIN_COLP)) at bridge.c:1713 #5 0x000000000050a610 in ast_bridge_call_with_flags (chan=0x7fb560285300, peer=0x7fb554045c90, config=0x7fb5122b7e90, flags=0) at features.c:671 #6 0x000000000050a6e2 in ast_bridge_call (chan=0x7fb560285300, peer=0x7fb554045c90, config=0x7fb5122b7e90) at features.c:710 #7 0x00007fb535b8b4b7 in dial_exec_full (chan=0x7fb560285300, data=0x7fb5122b85d0 "SIP/CC-MOVEL-TDM-FT/33105587988477247,60,L(764234560:61000:30000)", peerflags=0x7fb5122bb290, continue_exec=0x0) at app_mbilling.c:2752 #8 0x00007fb535b90a5c in mbilling_exec (chan=0x7fb560285300, data=0x652b69 "") at app_mbilling.c:3959 #9 0x0000000000582bb1 in pbx_exec (c=0x7fb560285300, app=0x7fb57001f950, data=0x7fb5122bb4f0 "") at pbx_app.c:494 #10 0x000000000056ff34 in pbx_extension_helper (c=0x7fb560285300, con=0x0, context=0x7fb560285cb8 "billing", exten=0x7fb560285d08 "087988477247", priority=1, label=0x0, callerid=0x7fb56019b080 "4330152780", action=E_SPAWN, found=0x7fb5122bdba4, combined_find_spawn=1) at pbx.c:2886 #11 0x00000000005735ad in ast_spawn_extension (c=0x7fb560285300, context=0x7fb560285cb8 "billing", exten=0x7fb560285d08 "087988477247", priority=1, callerid=0x7fb56019b080 "4330152780", found=0x7fb5122bdba4, combined_find_spawn=1) at pbx.c:4111 #12 0x0000000000574288 in __ast_pbx_run (c=0x7fb560285300, args=0x0) at pbx.c:4288 #13 0x0000000000575a58 in pbx_thread (data=0x7fb560285300) at pbx.c:4610 #14 0x00000000005f9ba9 in dummy_start (data=0x7fb5604b20a0) at utils.c:1239 #15 0x00007fb57edfae25 in start_thread () from /lib64/libpthread.so.0 #16 0x00007fb57e0d8bad in clone () from /lib64/libc.so.6
My code: line 2752: res = ast_bridge_call(chan, peer, &config); memset(&peerflags, 0, sizeof(peerflags)); snprintf(dialcommand, sizeof(dialcommand), "SIP/%s/%s%s",trunkcode,trunkdestination,dialparams); ast_channel_data_set(chan, dialcommand); line 3959: dial_exec_full(chan, dialcommand, &peerflags, NULL); Have any method to use function from another app? for example, the function dial_exec_full. I rewrite all function inside my app. Exist any method to use from app_dial.c? Best regards > On 12 Sep 2018, at 20:10, i...@magnussolution.com wrote: > > thanks for you help. > > > I try use backtrace. But I no a expert. > > I using cents 7 64x > > gdb -se "asterisk" -ex "bt full" -ex "thread apply all bt" --batch -c > core.13414 > /tmp/backtrace.txt > > warning: exec file is newer than core file. > Missing separate debuginfo for /usr/lib64/libmyodbc5.so > > > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > Missing separate debuginfo for /usr/lib64/libmyodbc5.so > Core was generated by `asterisk -vvvvvvvg'. > Program terminated with signal 11, Segmentation fault. > #0 ast_odbc_release_obj (obj=0x0) at res_odbc.c:712 > 712 struct odbc_class *class = obj->parent; > > > to use ODBC on centos7 and mariaDB 10 I install it > > yum -y remove mysql-connector-odbc > yum -y localinstall --nogpgcheck > http://dev.mysql.com/get/Downloads/Connector-ODBC/5.3/mysql-connector-odbc-5.3.11-1.el7.x86_64.rpm > > <http://dev.mysql.com/get/Downloads/Connector-ODBC/5.3/mysql-connector-odbc-5.3.11-1.el7.x86_64.rpm> > ln -s /usr/lib64/libmyodbc5w.so /usr/lib64/libmyodbc5.so > > > >> On 12 Sep 2018, at 19:28, Alex Villacís Lasso <a_villa...@palosanto.com >> <mailto:a_villa...@palosanto.com>> wrote: >> >> El 12/9/18 a las 14:33, i...@magnussolution.com >> <mailto:i...@magnussolution.com> escribió: >>> that’s correct. I wrote a ael context with func_odbc and this work very >>> well. >>> >>> But, using my app_mbilling.c work more faster than ael and func_odbc. >>> >>> example: >>> agi 15 CPS >>> ael-func_odbc 30 CPS >>> native application 50 CPS >> >> Have you tried yet FastAGI? Ordinary AGI is slowed down by the spawning of >> an entire process per call. FastAGI just requires a daemon that listens to >> requests on a TCP/IP port. This is way less invasive than writing a whole >> new Asterisk application in C. Any bottlenecks would now be located in the >> FastAGI server and could be tuned without touching the Asterisk core. >> >> As an aside, just a wild guess, but I think the crashes could be due to one >> or more race conditions, and the proper locking required to solve them would >> slow down your C application to the ael-func_odbc level. >> >> >> -- >> _____________________________________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com >> <http://www.api-digital.com/> -- >> >> Astricon is coming up October 9-11! Signup is available at: >> https://www.asterisk.org/community/astricon-user-conference >> <https://www.asterisk.org/community/astricon-user-conference> >> >> asterisk-dev mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-dev >> <http://lists.digium.com/mailman/listinfo/asterisk-dev> > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Astricon is coming up October 9-11! Signup is available at: > https://www.asterisk.org/community/astricon-user-conference > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Astricon is coming up October 9-11! Signup is available at: https://www.asterisk.org/community/astricon-user-conference asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev