Re: [vmeet] Meetecho sessions start/stop time

2016-04-11 Thread Dave Crocker
On 4/11/2016 2:44 AM, Dan York wrote: ... I've alway run a separate Jabber client connected into each working group chat when remote. That's a useful hack, but it's a hack. Helpful now, but should not be necessary, IMO. Meetecho's software needs to be much more reliable. This marks its (

Re: [vmeet] Meetecho sessions start/stop time

2016-04-11 Thread Dan York
John, While I think the "one minute to disconnection" warning the Meetecho team just suggested is a great addition... On Apr 10, 2016, at 2:04 PM, John C Klensin mailto:john-i...@jck.com>> wrote: I'd simply run a session with a separate Jabber client, but that introduces some extra synchroniza

Re: [vmeet] Meetecho sessions start/stop time

2016-04-11 Thread Meetecho IETF support
Il 10/04/2016 20:04, John C Klensin ha scritto: --On Sunday, April 10, 2016 19:33 +0200 Meetecho IETF support wrote: Folks, just to clarify that Meetecho sessions do start 5 minutes before the WG meeting scheduled start time, and never stops before the meeting has actually finished. Only w

Re: [vmeet] Meetecho sessions start/stop time

2016-04-10 Thread Paul Kyzivat
On 4/10/16 1:33 PM, Meetecho IETF support wrote: Folks, just to clarify that Meetecho sessions do start 5 minutes before the WG meeting scheduled start time, and never stops before the meeting has actually finished. Only when the previous meeting runs *very* long, we have to shift the start tim

Re: [vmeet] Meetecho sessions start/stop time

2016-04-10 Thread Dave Crocker
On 4/10/2016 11:04 AM, John C Klensin wrote: There were a couple of times when I was typing something into Jabber (via Meetecho) when the session ended. That resulted in the screen, and Jabber session, abruptly clearing, so I couldn't finish the message for the Jabber log, copy the partially-fin

Re: [vmeet] Meetecho sessions start/stop time

2016-04-10 Thread John C Klensin
--On Sunday, April 10, 2016 19:33 +0200 Meetecho IETF support wrote: > Folks, > > just to clarify that Meetecho sessions do start 5 minutes > before the WG meeting scheduled start time, and never stops > before the meeting has actually finished. > > Only when the previous meeting runs *very*

[vmeet] Meetecho sessions start/stop time

2016-04-10 Thread Meetecho IETF support
Folks, just to clarify that Meetecho sessions do start 5 minutes before the WG meeting scheduled start time, and never stops before the meeting has actually finished. Only when the previous meeting runs *very* long, we have to shift the start time of the following Meetecho session. This is n