Emits CONFERENCE_FAILED in response to CONNECTION_FAILED event which then triggers JitsiConference.leave() through the middleware processing. Also base/conference state will be adjusted. It is to have a consistent redux state in which both connection and conference are failed. It could happen that in a buggy environment the XMPP connection is dropped, but the media is still flowing which would result in weird user experience.master
|
|
||
| 199 |
|
199 |
|
| 200 |
|
200 |
|
| 201 |
|
201 |
|
| 202 |
|
|
|
|
202 |
|
|
|
203 |
|
|
| 203 |
|
204 |
|
| 204 |
|
205 |
|
| 205 |
|
206 |
|
|
|
||
| 7 |
|
7 |
|
| 8 |
|
8 |
|
| 9 |
|
9 |
|
| 10 |
|
|
|
|
10 |
|
|
| 11 |
|
11 |
|
| 12 |
|
12 |
|
| 13 |
|
13 |
|
|
|
||
| 20 |
|
20 |
|
| 21 |
|
21 |
|
| 22 |
|
22 |
|
|
23 |
|
|
| 23 |
|
24 |
|
| 24 |
|
25 |
|
| 25 |
|
26 |
|
|
|
||
| 62 |
|
63 |
|
| 63 |
|
64 |
|
| 64 |
|
65 |
|
|
66 |
|
|
|
67 |
|
|
|
68 |
|
|
| 65 |
|
69 |
|
| 66 |
|
70 |
|
| 67 |
|
71 |
|
|
|
||
| 168 |
|
172 |
|
| 169 |
|
173 |
|
| 170 |
|
174 |
|
|
175 |
|
|
|
176 |
|
|
|
177 |
|
|
|
178 |
|
|
|
179 |
|
|
|
180 |
|
|
|
181 |
|
|
|
182 |
|
|
|
183 |
|
|
|
184 |
|
|
|
185 |
|
|
|
186 |
|
|
|
187 |
|
|
|
188 |
|
|
|
189 |
|
|
|
190 |
|
|
|
191 |
|
|
|
192 |
|
|
|
193 |
|
|
|
194 |
|
|
|
195 |
|
|
|
196 |
|
|
|
197 |
|
|
|
198 |
|
|
|
199 |
|
|
|
200 |
|
|
|
201 |
|
|
|
202 |
|
|
|
203 |
|
|
|
204 |
|
|
|
205 |
|
|
|
206 |
|
|
|
207 |
|
|
|
208 |
|
|
|
209 |
|
|
|
210 |
|
|
|
211 |
|
|
|
212 |
|
|
|
213 |
|
|
|
214 |
|
|
|
215 |
|
|
|
216 |
|
|
|
217 |
|
|
|
218 |
|
|
|
219 |
|
|
|
220 |
|
|
|
221 |
|
|
|
222 |
|
|
|
223 |
|
|
|
224 |
|
|
|
225 |
|
|
|
226 |
|
|
|
227 |
|
|
|
228 |
|
|
|
229 |
|
|
|
230 |
|
|
| 171 |
|
231 |
|
| 172 |
|
232 |
|
| 173 |
|
233 |
|