When we receive kick presence it is both 110 and 307 status code, so we were triggering both conference_left and kicked event. Now when we receive kick we process as it is 110 to clean participants and room and then fire the kick event.

When only one participant is in the room and leaves(hangups) the only participant in members is focus.

Skips passing presence, cause it can reach the UI and there was a bug where we tried to pass the presence as an argument to the translation and ended in endless loop.

The places of the two arguments of the function createConnection were
switched in the function definition but the call to the function
remained unchanged.

Because the flag is required in the connection options anyway it will
be better to use it from one options set only to avoid redundancy.

The event is triggered when Jicofo sends 'session-terminate' and our
PeerConnection is closed.

Fix broken variable

If there is a problem with ssrc in successcallback of peerconnection create answer, no callback is called as a result of execution TraceablePeerConnection.createAnswer.

Do not flush the connection after 'session-accept'
is queued to avoid BOSH race condition issue.

This is an unrecoverable error and in current state of
the system reload in the client is the least complex
thing to do.

Moves render time calculations in the library.

Handles the case where we can receive the presence with the video type before we have received and created the remote track.

Fixes a problem where, sending that namespace on every presence will make the server think we are joining every time and will return us the message history for the muc.

If in the presence there is 110 and 307 status codes there was an error in processing. When kicked the other participants were not cleared from the conference. Firing an event for focus leaving the conference when we are kicked.