We had the same issue in our Remote Hub for 6lo.
Also, in the regops important meeting out of the agenda, the problem
was the same: around the expected end time of the meeting, the
session was automatically closed for us.
Best regards, Nicolas.
El 23/07/15 a las 06:29, Laurent
Ciavaglia escibió:
Dear Lorenzo,
Thanks for the feedback (and indeed the stream remains active for
some minutes).
I hope these situations (overtime) will stay exceptional cases.
Best regards, Laurent.
On 22/07/2015 20:14, Lorenzo Miniero
wrote:
On Wed, 22 Jul 2015 19:59:19 +0200
Laurent Ciavaglia <Laurent.Ciavaglia@xxxxxxxxxxxxxxxxxx> wrote:
Dear IETF community, Meetecho team,
Please apology if the problem is solved, but I have been confronted
two times today with WG sessions finishing beyond the schedule with
important decision points at the end.
I am participating remotely. The issue is that the Meetecho stream
closes few minutes after the scheduled session end time.
As a proposal (if no other solution is already in place), I would
suggest that the WG chairs / Meetecho operator could "extend" the
Meetecho session by 5-minutes time slots on a per need basis to cover
for the overtime.
Thanks.
Hi Laurent,
what we close is just the access, that is new participants can't join
after the end time triggers. We don't interrupt ongoing sessions for
participants that are still in, though, and we don't hangup the media
streams unless the overtime reaches 10 minutes. In that case, we do
have to interrupt the session, as preparations for the following
meeting need to be made and cannot unfortunately be delayed.
Lorenzo
|