Russ Housley <[email protected]> wrote:
>> From: Michael Richardson <[email protected]>
>> Date: February 10, 2015 1:23:10 PM EST
>> To: Emil Ivov <[email protected]>, [email protected], Bernard Aboba 
>> <[email protected]>
>> Cc: Harald Alvestrand <[email protected]>, [email protected], Joe Hildebrand 
>> <[email protected]>, Ines Robles <[email protected]>

   I note that Russ received this almost by accident (from the iesg list).

>> Subject: report on use of JITSI for the ROLL virtual Interim meeting
>> 
>> The ROLL Virtual Interim meeting that occured today was done using the
>> JITSI.tools interface.

   I actually meant to try to attend, though I really had nothing to
offer but limited experience with JITSI. Alas, I needed to do two errands,
and shoveling the drive killed my enthusiasm. :^(

>> That we were going to do JITSI was announced with the original
>> announcement (4 weeks ago), but of course, many did not bother
>> testing their environment until the last moment.

   This is inevitable. I'm not even sure earlier testing is justifiable,
since so many of these tools change without warning. :^(

>>... We think that it is pretty important that the slides be out ahead of
>> time so people know what to expect, and that they go up in PDF, so that
>> people can read them on any platform.

   Absolutely!

>> I did try to the "Share Prezi" link in JITSI (which I had not seen before),
>> but I did not realize that Prezi is a cloud based slide creation system, and
>> that I could not just point at a PDF file somewhere...

   Perhaps this is documented somewhere; but I've never seen it documented.

>> A few people had to reload the page; and there was the usual "does my
>> microphone even work", and also "oops, I'm still muted" problems that occur
>> on all teleconference.

   We've become used to this. It's a flaw, IMHO; but nobody seems to want
to fix the audio problems which lead to this. :^(

>> Emil and I had previously set up a SIP bridge for audio,

   :^) :^)

>> and it did work at one point, but SIP spammers/attackers on my PBX
>> forced us to add some whitelist ACLs.

   :^(

>> Despite dropping those, the SIP bridge did not work again, and we
>> did not re-establish communication. The lack of an available audio
>> bridge was an issue for a number of participants.

   (Why does this always come as a surprise?)

>>...
>> We had between 10 and 12 participants in the conference, and I think that we
>> had the right set of people there. It worked well once we got going.

   :^) :^) :^)

>> Two participants were initially on Cisco VPNs, and they found they
>> had to turn off the VPN...

   Do we understand why this keeps happening?

>> I would like to encourage the IESG and IAB to hold a few calls a year on
>> JITSI, in order to make it clear to respective IT departments that this
>> technology is critically important.  Dog food.

   These would have to be _other_than_ their regular calls.

   The learning-curve is just too steep -- often driven by things which
seem trivial _after_ you understand them. Though WebEx has problems
almost every telechat, they're problems which seem familiar...

>> I want to say that today, that ietf.webex.com tells me again that I have a
>> completely unsupported platform and browser; it did this to me last week for
>> a day and then stopped. I can not even start the call which I could
>> previously do (and then use the PSTN to connect)...

   Indeed, that is a very common "Plan B"...

>> Joe and I have talked in the past about webex' lack of support for
>> common technical user platforms, and I wish the IETF would move to
>> formerly (formally?) abandon it.

   That's not going to happen.

   But if we can get enough "virtual interims" using an alternative like
JITSI, we might develop a critical-mass used to working with it...

>> It would also be nice if we had an official SIP bridge that could get audio
>> to the PSTN, ideally controlled from within JITSI.

   Hmm... Dunno what that would take.

>> {The 2013/2014 nomcom used G+ Hangouts, and we were able to use the Google
>> internal one which permitted >9 participants as we had a Google person who
>> had access to it.  The 2014/2015 Nomcom tried a call or two with JITSI, but
>> the audio bridge problem was more severe}

   I've had generally good experiences with G+ Hangouts -- though of course
the details change, seemingly every time I use it.

--
John Leslie <[email protected]>

_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet

Reply via email to