Recent Webex issues (Was: Meetecho for interim meetings)

Jay Daley <jay@ietf.org> Mon, 26 April 2021 19:35 UTC

Return-Path: <jay@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59703A2421 for <wgchairs@ietfa.amsl.com>; Mon, 26 Apr 2021 12:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ABIQPE-6aOP; Mon, 26 Apr 2021 12:35:21 -0700 (PDT)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 63E403A241D; Mon, 26 Apr 2021 12:35:20 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Recent Webex issues (Was: Meetecho for interim meetings)
From: Jay Daley <jay@ietf.org>
In-Reply-To: <ab5bff35-bd78-9166-8802-7d591973f398@sit.fraunhofer.de>
Date: Tue, 27 Apr 2021 07:35:13 +1200
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, Working Chairs <wgchairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3957ADFF-311C-41CC-9D66-1E8DA9FE232C@ietf.org>
References: <39B62FF8-3DC1-4FBE-93B2-8FB1A3A82555@amsl.com> <5c90a50b-a5ab-9cbb-abe5-f563891de0f7@sandelman.ca> <FB33625D-F0EE-476D-940E-D24BF75634B2@tzi.org> <f37f4ae4-bdf7-cda0-7162-f32fcfcb41ed@sit.fraunhofer.de> <CAKKJt-f4LZBABEUOwj-ggsaX6_TtKmN_0kzZz2U+8k++w38R1A@mail.gmail.com> <4ddc1c68-8d51-6254-3c3e-6e7a96789538@sit.fraunhofer.de> <7cb83f8c-2aa2-4c63-2649-1da48d3d622d@sit.fraunhofer.de> <0A5A1BA7-8A3F-4AC3-8BF1-B04D040E74D7@ietf.org> <ab5bff35-bd78-9166-8802-7d591973f398@sit.fraunhofer.de>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/dnUXeTKQRcvZqkDsYujNvT8YEms>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 19:35:27 -0000

Hi Henk

We’ve looked at this this and there are indeed three options as below:

1. "Webex Meeting Pro 200"
This is the default and the only one that should be used.  If used this will allow full connectivity including WebRTC.

2.  "Webex Meetings 107 Virtual"
This was an experiment and has now been deleted.

3.  "Webex Personal Conference"
This is auto-created by Webex and sets up an audio only conference.  We believe the issue recently was that this was used not option 1 above but we cannot get stats on the usage of this so we are going to take a risk and disable it to precent this happening again and we will see if anyone complains.

Jay


> On 23/04/2021, at 6:43 PM, Henk Birkholz <henk.birkholz@sit.fraunhofer.de> wrote:
> 
> Thanks Jay! That is very appreciated.
> 
> On 22.04.21 21:59, Jay Daley wrote:
>>> On 23/04/2021, at 3:28 AM, Henk Birkholz <henk.birkholz@sit.fraunhofer.de <mailto:henk.birkholz@sit.fraunhofer.de>> wrote:
>>> 
>>> Hi all,
>>> 
>>> quickly running though a series of tests with Michael, we were able to to recreate the issue and also schedule meetings that do not exhibit the issue.
>>> 
>>> You can select a "Meeting type", when you schedule a meeting. You should select "Webex Meeting Pro 200" there.
>>> 
>>> As you might have guessed, I did not. Selecting "Webex Personal Conference" instead comes with the issue we experienced at the iotops interim.
>>> 
>>> So, it is pretty easy to circumvent that issue by selecting the "correct" type. Now, I am left wondering, why I have three options to choose from. My options are:
>>> 
>>> "Webex Meetings 107 Virutal"
>>> "Webex Meeting Pro 200"
>>> "WebEx Personal Conference"
>>> 
>>> Are these options the same for everyone else? Do we need anything else than "Webex Meeting Pro 200"?
>> I will pickup and see what it happening with this.
>> Jay
>>> 
>>> Viele Grüße,
>>> 
>>> Henk
>>> 
>>> On 21.04.21 10:51, Henk Birkholz wrote:
>>>> Hi Spencer,
>>>> I personally know of four individuals that were not able to join. Two of them presenters, three of them using Linux and one of them using a Mac.
>>>> I joined in testing another reoccurring IETF webex instance afterwards and that worked fine.
>>>> From my point of view, it might have something to do with the individual session I set up and the issue is maybe limited to "non-app" users.
>>>> Viele Grüße,
>>>> Henk
>>>> On 20.04.21 23:57, Spencer Dawkins at IETF wrote:
>>>>> To the survivors of the IOTOPS meeting ...
>>>>> 
>>>>> On Tue, Apr 20, 2021 at 1:50 PM Henk Birkholz <henk.birkholz@sit.fraunhofer.de <mailto:henk.birkholz@sit.fraunhofer.de> <mailto:henk.birkholz@sit.fraunhofer.de>> wrote:
>>>>> 
>>>>>     Hi all,
>>>>> 
>>>>>     while I was able to join the IOTOPS webex, I understand that quite a
>>>>>     few
>>>>>     people where blocked from joining.
>>>>> 
>>>>> 
>>>>> Did I understand correctly that
>>>>> 
>>>>>   * a number of participants who were blocked were using Linux systems, but
>>>>>   * some number of participants said they WERE able to join using Linux
>>>>>     systems?
>>>>> 
>>>>> I could have gotten that wrong, because I was just listening to the general background banter, but that's what I thought I heard.
>>>>> 
>>>>> Best,
>>>>> 
>>>>> Spencer
>>>>> 
>>>>> p.s. Michael Richardson and I co-chair Cellar, which doesn't use WebEx for our meetings, but I can't imagine trying to run one of our meetings from a cell phone - you'll be shocked to learn that we each have a screen open for the video. a screen open in Github, and another screen open for CodiMD, at a minimum.
>>>>> 
>>>>>     Maybe something broke when I set this up. Although there is some chance
>>>>>     that the issue sneaked in with some default setting (as I am not aware
>>>>>     of a deviation from defaults).
>>>>> 
>>>>>     Whatever happened, I actually hope it was me. If anyone can shed a bit
>>>>>     more light on this - or speak from a similar experience - that would of
>>>>>     course be great.
>>>>> 
>>>>>     Viele Grüße,
>>>>> 
>>>>>     Henk
>>>>> 
>>>>>     On 20.04.21 20:37, Carsten Bormann wrote:
>>>>>      > On 20. Apr 2021, at 18:11, Michael Richardson
>>>>>     <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca> <mailto:mcr%2Bietf@sandelman.ca>> wrote:
>>>>>      >>
>>>>>      >> Today, IOTOPS chairs and speakers found that webex had stopped
>>>>>     working a few minutes before the meeting.  Some of us are suffering
>>>>>     with a smartphone with a tiny screen.
>>>>>      >
>>>>>      > Amazingly, all other Webex links (IETF or not) that I tried today
>>>>>     properly offer the WebRTC link (“Join via Browser”).
>>>>>      > Just
>>>>> https://ietf.webex.com/ietf/j.php?MTID=m633bd0ec88130283104fb7cd84156f3e
>>>>>     doesn’t.
>>>>>      >
>>>>>      > Iotops Is a relatively young WG.  Maybe something broke when
>>>>>     setting this up?
>>>>>      >
>>>>>      > Grüße, Carsten
>>>>>      >
>>>>> 
>>> 
>> -- 
>> Jay Daley
>> IETF Executive Director
>> jay@ietf.org <mailto:jay@ietf.org>
> 

-- 
Jay Daley
IETF Executive Director
jay@ietf.org