Avaya CU360 Release Notes page 132

© 2021 Avaya Inc. All rights reserved
Category
Spaces Meeting
with "Spaces"
App as personal
device
Spaces Meeting
with CU360 App
Release Notes for Avaya Collaboration Unit CU360
Case Number/
Description of issue
Ticket ID
device before the meeting is
started. For example, if the
Bluetooth device volume is set to
a low level before the call is
started it may not be possible to
increase the volume to an
acceptable level.
Media path will not recover
if encountering network
disruptions during a meeting.
You cannot initiate recording
from the Spaces Room app, you
Recording
can only determine that a call is
being recorded.
Camera zoom settings are not
Zoom+/-
persisted across calls.
AV Grabber/Wi-Fi
Sharing Display/Split&Share not
supported yet.
FW and NAT Outgoing ports to Spaces
Backend and Media Server must
be open in the local NAT/FW.
TLS traffic is used for both HTTPS
and WSS, any TLS-inspection
should support these protocols
or have an exception for Spaces'
hosts.
The Spaces Room App cannot
join members-only spaces,
Members-only
unless invited by authorized
(private) meetings
members joining the room via
QRCode or Pairing code
Whiteboard is not supported in
Whiteboard
Spaces Meetings
Mute state of a Bluetooth audio
BT
device is not synced with Spaces
app.
Sometimes BT is not selected
BT properly if changed during the
call
FW and NAT Outgoing ports to Spaces
Backend and Media Server must
be open in the local NAT/FW.
TLS traffic is used for both
HTTPS and WSS, any TLS-
inspection should support these
protocols or have an exception
for Spaces' hosts.
Video Video resolution is limited to
720p30fps
Redial It is not possible to redial into
meetings when invited through
QR code or pairing code or
calendar.
FW and NAT Outgoing ports to Spaces
Backend, SIP and Media Server
must be open in the local
NAT/FW if they are blocked. TLS
traffic is used for both HTTPS
and WSS, any TLS-inspection
should support these protocols
or have an exception for Spaces'
hosts.
Solution/Workaround
Hang-up and re-join the meeting when the network
is recovered.
Start recording from web front-end.
Use the remote-control zoom keys on every call.
Share from your desktop/laptop web front-end.
See also
https://content.avayacloud.com/Spaces/PDF/Avaya
_Spaces_Manual.pdf > Network Access
Requirements section
Invite the device by joining the room through paring
code or QRCode
Ensure both physical Bluetooth mute and Spaces
soft mute key are unmuted to enable speech path.
Ask to "raise hand" by using the CU360 remote-
control
Select BT audio, disconnect the call and join again
See also
https://content.avayacloud.com/Spaces/PDF/Avaya
_Spaces_Manual.pdf > Network Access
Requirements section
Save the original meeting URL as a favorite contact.
Check that a device inside the company can connect
to
spaces.avayacloud.com (HTTPS + WSS, TCP/TLS
80,443)
spaces.sip.mpaas.avayacloud.com (TCP/TLS 5061)
and that the DNS is properly configured.
*.avayacloud.com HTTPS + WSS, TCP/TLS 80,443)
*.mpaaservice.com HTTPS + WSS, TCP/TLS 443
UDP 3000-4999 for these addresses:
35.227.0.176/29
35.243.1.0/29
35.192.193.192/27
Known Issues 132