Summary:	ASTERISK-19580: chan_gtalk crash Asterisk on outgoing calls
Reporter:	tootai (tootai)	Labels:
Date Opened:	2012-03-23 05:37:59	Date Closed:	2015-02-26 09:27:18.000-0600
Priority:	Major	Regression?	Yes
Status:	Closed/Complete	Components:	Channels/chan_gtalk
Versions:	1.8.10.1 10.2.1	Frequency of Occurrence	Constant
Related Issues:
Environment:	kvm virtual machine, Debian Stable 6.3	Attachments:	( 0) backtrace.txt ( 1) gdb.txt
Description:	Asterisk crash without any core file.    -- Executing [312@OFFICE-Numbers:1] Macro("Local/312@OFFICE-Numbers-3087;2", "dialGTALK,my.user@gmail.com") in new stack    -- Executing [s@macro-dialGTALK:1] Set("Local/312@OFFICE-Numbers-3087;2", "CALLERID(name)=TOOTAi") in new stack    -- Executing [s@macro-dialGTALK:2] Set("Local/312@OFFICE-Numbers-3087;2", "CALLERID(number)=0033123456789") in new stack    -- Executing [s@macro-dialGTALK:3] NoOp("Local/312@OFFICE-Numbers-3087;2", "Outgoing call to GTALK - "TOOTAi" <0033123456789>") in new stack    -- Executing [s@macro-dialGTALK:4] Dial("Local/312@OFFICE-Numbers-3087;2", "gtalk/asterisk/my.user@gmail.com,,rt") in new stack zone-s*CLI> Disconnected from Asterisk server Executing last minute cleanups That's all.
Comments:	By: Paul Belanger (pabelanger) 2012-03-23 08:28:50.636-0500 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Matt Jordan (mjordan) 2012-03-23 09:02:25.338-0500 Did you run Asterisk with the '-g' option? In order to move this forward, we'll need a backtrace generated from a core file.  Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: tootai (tootai) 2012-03-23 09:37:56.912-0500 Backtrace from core file. By: Richard Mudgett (rmudgett) 2012-03-23 11:38:56.365-0500 FYI You need to send the issue back when you are done supplying feedback.  If you don't do this, the issue may languish because it appears to still be waiting for you to respond. By: tootai (tootai) 2012-03-23 11:51:55.257-0500 Sorry, I was thinking that the comment underlying the attached files would generate the SendBack By: Matt Jordan (mjordan) 2012-03-23 15:08:01.045-0500 I've acknowledged this issue and assigned it to the maintainer of chan_gtalk.  Please keep in mind that chan_gtalk is an extended support module [1], and response times may reflect that. https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States By: Malcolm Davenport (mdavenport) 2015-02-26 09:27:18.398-0600 Unfortunately, this issue wasn't addressed during the bug-fix lifetime of Asterisk 1.8 or 10.  The good news is that Asterisk 11 and greater have chan_motif and res_xmpp, which are a rewrite of XMPP support within Asterisk, and are supported. We'd encourage you to try that out instead and see if that clears things up for you.