[Jaydeep] Spaces unable to detect Audio/Video or the Settings buttons. It only happens with Spaces. When user was setting up to do a live video demo for the PCC it happened on Tuesday (EST). Zoom to Avaya IX Workplace works but not Spaces.

[sync-by-unito[bot]]

Steps to reproduce or test this issue

• Use Avaya OCC hub device - (https://www.avaya.com/en/documents/fs-occ-hub-dv15409en.pdf)
• Connect microphone, camera and monitor devices to OCC hub device, have another USB 3.0 connection from OCC hub to PC/Laptop.
• This way mic/camera/display devices were not directly connected to PC/Laptop but through single USB 3.0 connection from OCC hub to PC/Laptop.
• If device drivers are not installed correctly, emulated mic device name for PC/Laptop causes exception in spaces app which in turn causes microphone device not detected properly and call results in collaboration only call.

Note that in interoperability section of Avaya OCC hub device, they mentioned that it supports Avaya IX Meetings Conferencing and not Avaya Spaces.

---

Got an issue with Spaces meeting room, buttons not visible, User informed: "Spaces refuses to see any of my video or audio tools. Maybe a Chrome problem but it only happens with Spaces. I was setting up to do a live video demo for the PCC when it happened on Tuesday. Zoom to Avaya IX Workplace works but not Spaces. Spaces product management believes I am in the unrecognized browser mod."

┆Attachments: Ronnie.jpg | spaces.avayacloud.com (2).har | spaces.avayacloud.com-1595008235403 (1).log

[sync-by-unito[bot]]

➤ Sudhansu Sekhar Sahoo commented:

Few more details on this issue from user's end:

1. Started Tuesday PM EST and continues today
2. Chat Works everything has been restarted and reset many times. Multiple IT Help Sessions. IT has so far refused to uninstall and re install Chrome. Problem is also with newly installed Firefox
3. Dial in Audio works. By following the screen pop up numbers
4. User has been attempted VPN and No VPN

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

Based on screenshots attached for the issue, It looks like spaces application is not able to find microphone device. If microphone device is not available, spaces switch to collaboration only call. That is happening here. For that machine we need to check available microphone devices as well as microphone device permission for Chrome browser.

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

Based on attached logs, camera and microphone device permissions were not granted in browser. The permission status for camera and microphone was 'Prompt' (Ask - default permission). Other than that when call was attempted, microphone device was not detected so it goes to collaboration only mode.

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

Updates from user who reported this issue: This issue goes away after installing updated drivers for camera and microphone. After a week with same drivers user again faces similar issue but it's intermittent.

[sync-by-unito[bot]]

➤ Jaydeep Bhalerao commented:

PR: https://github.com/esna/spaces-front/pull/3239

[sync-by-unito[bot]]

➤ Prashanth Muppalla commented:

@Ray Gerami ( https://app.asana.com/0/1154145881585295/calendar ), we can't test it from our end because we don't have access to the OCC hub.