Bugs item #3539687, was opened at 2012-07-03 04:51 Message generated for change (Settings changed) made by franzzieris You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=843359&aid=3539687&group_id=167540
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Communication Group: 12.7.6.TESTING >Status: Open >Resolution: Fixed Priority: 7 Private: No Submitted By: Franz Zieris (franzzieris) Assigned to: Franz Zieris (franzzieris) Summary: Default chat server denies room creation Initial Comment: The default chat server (conference.jabber.ccc.de) denies room creation, which is necessary for the Multi User Chat. >From the ErrorLogs: WARN 2012-07-03 13:18:20,684 (SubscriptionManager.java:106) Received error presence package from saros696314...@conference.jabber.ccc.de/fzie...@saros-con.imp.fu-berlin.de/Saros, condition: forbidden, message: Room creation is denied by service policy This leads to a non-working chat: the instructions how to start a Saros session remain even if a session is already running (but that's another bug). The default usage of "conference.saros-con.imp.fu-berlin.de" would be a sufficient solution for this bug. We use this server for our STF tests anyway (and that's the reason this bug is seldom sighted by developers). ---------------------------------------------------------------------- Comment By: Franz Zieris (franzzieris) Date: 2012-07-03 10:49 Message: The "other bug" has number #3539830, click here https://sourceforge.net/tracker/?func=detail&aid=3539830&group_id=167540&atid=843359 ---------------------------------------------------------------------- Comment By: Franz Zieris (franzzieris) Date: 2012-07-03 09:30 Message: And I will create the "other bug". I simply had no time to create it yet. >From my point of view the behavior described above *is* a bug: We deliver a version of Saros that does not support chatting out of the box. Even if the "other bug" is fixed, the user only gets an information, but has to find a solution himself. I see no point in classifying this as a "configuration issue" instead of "bug", since it does not change the way we have to handle it. ---------------------------------------------------------------------- Comment By: Stefan Rossbach (kargor) Date: 2012-07-03 08:08 Message: Dear Franz, this is a configuration issue and not a bug. Using Saros in a company intranet may procude the same issue as long as the chat server is not manually changed. You already described the real bug, not reporting this issue to the user. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=843359&aid=3539687&group_id=167540 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dpp-robot mailing list Dpp-robot@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-robot
