[asterisk-bugs] [JIRA] Updated: (ASTERISK-20360) XMPP sendtodialplan hangs up after executing first priority (when using Hangup())

[Leif Madsen (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Madsen updated ASTERISK-20360:
-----------------------------------

    Component/s: Core/Channels
        Summary: XMPP sendtodialplan hangs up after executing first priority (when using Hangup())  (was: XMPP sendtodialplan hangs up after executing first priority)

> XMPP sendtodialplan hangs up after executing first priority (when using Hangup())
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20360
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20360
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Channels, Resources/res_xmpp
>    Affects Versions: SVN
>         Environment: CentOS 6.3 for Asterisk.  XMPP server running Openfire 3.6.4 on CentOS 5.8.  XMPP client sending messages to Asterisk is Pidgin 2.10.6
>            Reporter: Noah Engelberth
>            Severity: Minor
>         Attachments: xmpp-backtrace.txt, xmpp-debug.txt
>
>
> When using sendtodialplan=yes in xmpp.conf for res_xmpp.so and you have a Hangup() in the execution path for the inbound unsolicited XMPP messages, Asterisk will process the first inbound XMPP message as expected, and then all subsequent inbound XMPP messages will execute ONLY the first priority before hanging up the "call".  Restarting Asterisk causes the first XMPP message received after the restart to work, and then the hangup after first priority problem returns.  If no Hangup() ever executes during XMPP messages (instead relying on auto-fallthrough to hangup the message "calls"), XMPP messages will run as expected.  Once the Hangup() has executed, I cannot get Asterisk to resume receiving messages without restarting Asterisk.
> Regardless of how res_xmpp.so was loaded, trying to use "module reload res_xmpp.so" to get it to resume normal message handling results in a debug output of "xmpp.conf was unchanged", and Asterisk continues to hangup on incoming XMPP messages after executing a single priority.  
> If res_xmpp.so was noload'ed in modules.conf and manually loaded from asterisk -r, attempting to issue "module unload res_xmpp.so" crashes asterisk, with no debug output making it to the console prior to the crash.  I have attached the backtrace to this ticket.
> If res_xmpp.so was automatically loaded at Asterisk runtime, attempting to issue "module unload res_xmpp.so" causes the console to output the "Unregistered application" and "Unregistered function" lines, but the XMPP client remains logged in and will receive messages (though it still hangs up on them after the first priority).  If you then issue "module load res_xmpp.so" subsequent to the module unload command, the Asterisk console shows the normal output for loading res_xmpp.so, but my XMPP client can no longer send messages to Asterisk (even though the Asterisk XMPP client shows online in my buddy list and the server's status).

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