Summary:	ASTERISK-26394: Strange warning messages in JabberSendGroup function
Reporter:	Marcelo Terres (mhterres)	Labels:
Date Opened:	2016-09-20 08:06:56	Date Closed:	2016-09-20 08:36:39
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_xmpp
Versions:	14.0.0-rc1	Frequency of Occurrence	Constant
Related Issues:
Environment:	Ubuntu 14.04.5 LTS - Linux rtc 4.5.5-x86_64-linode69 #3 SMP Fri May 20 15:25:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux	Attachments:
Description:	After my update to Asterisk 14 (not sure if it starts just in rc1), I started to receive strange warning messages. My sample dialplan is: exten => 2222,1,NoOp(Earlier callerd identification - send message to MUC) same => n,JabberJoin(${XMPPRESOURCE},site@conference.jabber.mundoopensource.com.br,Asterisk) same => n,JabberSendGroup(${XMPPRESOURCE},site@conference.jabber.mundoopensource.com.br,Call from ${CALLERID(all)},Asterisk) same => n,Answer() same => n,Wait(1) same => n,Playback(thanks_for_call) same => n,Dial(SIP/1000,10) same => n,Hangup When I call extension 2222, I'm getting this messages: [Sep 20 10:03:29] WARNING[10395]: res_xmpp.c:3325 xmpp_pak_presence: Received presence information about 'site@conference.jabber.mundoopensource.com.br' despite not having them in roster on client 'asterisk' [Sep 20 10:03:29] WARNING[10395]: res_xmpp.c:3325 xmpp_pak_presence: Received presence information about 'site@conference.jabber.mundoopensource.com.br' despite not having them in roster on client 'asterisk' [Sep 20 10:03:29] WARNING[10395]: res_xmpp.c:3325 xmpp_pak_presence: Received presence information about 'site@conference.jabber.mundoopensource.com.br' despite not having them in roster on client 'asterisk' [Sep 20 10:03:29] WARNING[10361][C-00000003]: pbx.c:8558 pbx_parseable_goto: Goto requires an argument ([[context,]extension,]priority) The first 3 messages are clear to me, but the last message doesn't make sense, because it happens in the JabberSendGroup function. In despite of this error, the message is being correctly delivered in my MUC room.
Comments:	By: Asterisk Team (asteriskteam) 2016-09-20 08:06:56.673-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2016-09-20 08:17:21.302-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Marcelo Terres (mhterres) 2016-09-20 08:31:32.884-0500 Looks like I'm still sleeping and need to drink more coffee. Forget this issue too. :-( Thanks.