Avaya XT Series - Configuring Fqdns

Name Description
Automatic Join to Important Meeting Select Yes to enable the XT Series endpoint to
automatically join the meeting when it starts if it is
marked with High Importance (exclamation mark) in
Microsoft Outlook. No manual user intervention is
required.
Select No to disable automatic entry to meetings of
High Importance. If another meeting is already in
place when the important meeting starts, the current
call will not be automatically dropped.
FQDN list Each entry represents a mapping between the Fully
Qualified Domain Name (FQDN) of a meeting
location and a number to dial in a SIP or H.323 call
in order to join the virtual meeting room. By default,
the list contains two entries which you can edit. You
can also add additional mappings. Each mapping
represents a dialling rule for an XT Series endpoint
to a specific cloud service that supports h323 or sip
calls. For more information, see
Configuring
FQDNs on page 223.
Button Description
Save From the web interface only, select Save to retain
your updates.
Configuring FQDNs
About this task
If you define a Fully Qualified Domain Name (FQDN) mapping, your users can join a meeting from
the XT Series endpoint GUI with a single click on the calendar item displayed on the endpoint GUI
or Web interface. The XT Series endpoint applies the mapping rules to automatically generate the
number to dial from the meeting location contained in the calendar entry. The meeting location for
Avaya Meetings Server is usually in the format:
https://<Meeting FQDN>/portal/tenants/default/?ID=<MeetingID>
The list of FQDNs contains a number of dial mappings for several videoconferencing cloud
services.
Procedure
1. Access the FQDN settings. From the XT Series web interface, select Administrator
Settings > Calendar > General. From the endpoint, select Configure > Advanced >
Calendar.
2. Click New FQDN.
Alternatively, you can click Edit to edit an existing FQDN.
Calendar integration
August 2020 Deployment Guide for Avaya XT Series 223
Comments on this document? infodev@avaya.com