on Openfire Version 4.6 i have the following problem:
Admin A kicks User B from a muc with:
<iq firstname.lastname@example.org/ressource' id='kick1' email@example.com' type='set'> <query xmlns='http://jabber.org/protocol/muc#admin'> <item nick='Usernick' role='none'> <reason>Kicked out Test</reason> </item> </query> </iq>
Then the user was kicked from channel but the Admin gets this presence back:
<presence from="firstname.lastname@example.org/Usernick" to="email@example.com/ressource" type="unavailable" xmlns="jabber:client"> <x xmlns="http://jabber.org/protocol/muc#user"> <item jid="firstname.lastname@example.org/ressource" affiliation="member" role="none"> <actor jid="email@example.com" nick="Admin"/> </item> <status code="307"/> <status code="110"/> </x> </presence>
Code 110 is totaly wrong here, because it is not a self-presence… the problem is now that 110 let the Admins’ client think he was kicked too, but that is not the case.
- Example 93. Service Informs Remaining Occupants AND
- Example 92. Service Informs Moderator of Success
should be send out by openfire
- it seems that Example 91. Service Removes Kicked Occupant was sent to Admin.
INFO: This only occurs on a kick not on a ban.