Known Issues - Avaya IX Collaboration Unit CU360 Release Notes

Hide thumbs Also See for IX Collaboration Unit CU360:
Table of Contents

Advertisement

© 2019 Avaya Inc. All rights reserved

Known Issues

Avaya performs effective testing of each software version. Patch software may be available to fix
known issues of this software version. Please contact Avaya's Customer Support Service for
further information.
This section details the list of known issues for this version. Some issues are common to Avaya XT
Series.
Table 6:
List of known issues in this release
Category
System Setup
Date and Time
I/O Connections
IOT
Release Notes for Avaya IX Collaboration Unit CU360
Case Number/
Description of issue
Ticket ID
720p, 1080p HDMI or 4K
monitors are not correctly
recognized. The UX is displayed
with wrong proportions
The date and time are not
preserved after reboot when
1) the system has Internet time
disabled and Use Default NTP
Servers Disabled
Or
2) the system is configured for
geolocation (Internet Time) but
does not have internet access
Or
3) the system is configured to
use Default NTP Servers but the
DHCP server does not return
valid NTP servers or
4) the manually configured SNTP
servers are not reachable
USB Cameras are not supported
in this release
H.263 and H.263+ are not
supported.
When connected to an Equinox
Meeting hosted on Elite 6000, it
can happen in certain room
conditions that the transmission
of your local video freezes.
To allow @home CU360 or XT
Series devices units to register
with Avaya Aura or other SIP
Avaya SBCE
servers in your deployment,
configure SBC with the following
RegEx in System Parameters for
User Agents: .*RV/V.*
IP Office ( 10.1 or lower ) might
require Third Party license for
Avaya CU360 endpoints.
SR 1-11610561268
IP Office (10.0 or lower) might
require Third Party license for
Avaya XT4300, XT7100 and
XTE240.
When registered to IPO (sip
server), Avaya XT7100, XTE240
and XT4300 and Avaya CU360
endpoints might not receive
IPOFFICE-109632
presentation.
This happens if your IPO version
is outdated and does not
recognize the endpoint. See SR
1-11610561268 above.
Cisco SX80 TC7.2.0 is not able to
receive SIP TLS incoming calls if
Solution/Workaround
Turn off the system, unplug the monitor, turn on
the system and plug the monitor again.
Use one of the following workarounds:
1)
Assure that Internet Time is Yes and
assure that the System has internet
access.
2)
Assure that use default NTP servers is Yes
and assure that the DHCP server returns
NTP servers which are reachable
3)
Assure that the manually specified NTP
servers are reachable
If none of the above workarounds is applicable and
the date of the system is still wrong after the system
is kept turned off for several minutes, you need to
configure manually the date at each restart.
Try to set and remove Privacy.
Try to zoom in the camera or pass your hand in
front of the camera to change the camera shot.
Use a 3rd Party SIP License to register that endpoint
as a SIP device to an IP Office system.
Note: The endpoint cannot register as an H.323
device to IPO.
Configure IPO with "MediaSecurity=None" to the
extensions associated to those endpoints to enable
presentation towards them.
Disable AES256 on XT or place outgoing call from
Cisco to XT.
Known Issues 21

Advertisement

Table of Contents
loading

Table of Contents