[asterisk-bugs] [JIRA] Commented: (ASTERISK-20395) CLI Originate to chan_gtalk causes memory corruption crash
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Sat Sep 15 17:01:27 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197123#comment-197123 ]
Rusty Newton commented on ASTERISK-20395:
-----------------------------------------
Private Name - falves11, please attach your gtalk.conf,jabber.conf (sanitized), plus any other relevant configs and an asterisk full log including VERBOSE and DEBUG messages of level 5 right up to the time of crash.
> CLI Originate to chan_gtalk causes memory corruption crash
> ----------------------------------------------------------
>
> Key: ASTERISK-20395
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20395
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_gtalk
> Affects Versions: 1.8.15.1
> Environment: centos 6.3
> Reporter: Private Name
> Assignee: Private Name
> Attachments: crash-10.txt, crash-1.txt, crash-2.txt, crash-3.txt, crash-4.txt, crash-5.txt, Untitled 5.txt, valgrind.txt
>
>
> It crashes every few minutes. I am uploading the trace.
> I originate calls from the cli with originate and then if answered it gets dropped on a context with music-on-hold. No more logic to it.
> It uses jabber and gtalk
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list