[asterisk-bugs] [JIRA] Commented: (ASTERISK-20361) XMPP segfaults

[Noah Engelberth (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196912#comment-196912 ] 

Noah Engelberth commented on ASTERISK-20361:
--------------------------------------------

I think the (null) messages are sent by the chat client as part of what enables the "you're about to receive a message..." functionality that Pidgin and other clients have available as an option to turn on.  The messages don't evaluate true for ISNULL, and "${MESSAGE(body)}" does match the string "(null)" within the dialplan.

> XMPP segfaults
> --------------
>
>                 Key: ASTERISK-20361
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20361
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_xmpp
>    Affects Versions: SVN
>         Environment: CentOS 6.3.  XMPP clients including Pidgin 2.10.6 and Trillian.  OpenFire server, tried both versions 3.6.4 and 3.7.1
>            Reporter: Noah Engelberth
>            Severity: Critical
>         Attachments: extensions.conf, xmpp-backtrace.txt, xmpp.conf, xmpp-message.txt, xmpp-segfault-backtrace.txt
>
>
> Getting fairly frequent segfaults on my test box running Asterisk 11 SVN.  Trying to get res_xmpp working as an "interactive XMPP menu" for my internal users.  Both XMPP clients I've tested seem to send a message with a body of "(null)" when the XMPP client is starting a new message (but before the new message is actually sent).  I have my dialplan set up to filter these out and not fully receive them, but Asterisk is segfaulting somewhere in this filtering process.  Not 100% reproducible, but happens in long spurts when it does happen.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira