© 2021 Avaya Inc. All rights reserved
Release Notes for Avaya Collaboration Unit CU360
Known Issues 128
Category
Case
Number/
Ticket ID
Description of issue
Solution/Workaround
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.
Hang-up and re-join the meeting when the network
is recovered.
Recording
You cannot initiate recording
from the Spaces Room app, you
can only determine that a call is
being recorded.
Start recording from web front-end.
Zoom+/-
Camera zoom settings are not
persisted across calls.
Use the remote-control zoom keys on every call.
Sharing
AV Grabber/Wi-Fi
Display/Split&Share not
supported yet.
Share from your desktop/laptop web front-end.
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.
See also
https://content.avayacloud.com/Spaces/PDF/Avaya
_Spaces_Manual.pdf
> Network Access
Requirements section
Members-
only (private)
meetings
The Spaces Room App cannot
join members-only spaces,
unless invited by authorized
members joining the room via
QRCode or Pairing code
Invite the device by joining the room through paring
code or QRCode
Whiteboard
Whiteboard is not supported in
Spaces Meetings
Spaces Meeting with
“Spaces” App as
personal device
BT
Mute state of a Bluetooth audio
device is not synced with Spaces
app.
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
BT
Sometimes BT is not selected
properly if changed during the
call
Select BT audio, disconnect the call and join again
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.
See also
https://content.avayacloud.com/Spaces/PDF/Avaya
_Spaces_Manual.pdf
> Network Access
Requirements section
Spaces Meeting with
CU360 App
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.
Save the original meeting URL as a favorite contact.
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 ha
ve an exception for Spaces’
hosts.
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
34.90.202.88/29
34.90.54.64/27
35.240.211.240/29