We use 'kick' reason for kicking out participants from Jitsi Meet
conference. However there is no such reason defined in Jingle
specs. Because of that our Jitsi reason IQ provider throws an
exception and XMPP provider connection is killed after that.
There are few options of solving the issue:
1. do not let the exception "fly", but catch and log it. Then
provide NULL reason when parsing Reason IQ which will also mean that
the reason is invalid.
2. change reason to 'decline' or 'cancel' in Jitsi Meet
3. make reason not an enum, but a String that can handle any value
What do you think ? My bet is option 1 and I'm going to apply it on
Monday if no one objects until then.