Tips For Configuring Your Email For Calendar Integration - Avaya XT Series Deployment Manual

Advanced Configuration of the XT Series
3. Configure the settings as described in
4. From the web interface only, select Save.
FQDN field descriptions
Name
Meeting FQDN
Dialing FQDN
Prefix
Call Protocol
Button
Save

Tips for configuring your email for calendar integration

Your XT Series can integrate with a Microsoft Outlook calendar using Microsoft Exchange Web
Services (EWS). There are three different modes of operation:
• Personal account mode: Use this mode to see your personal calendar on the XT Series
endpoint.
• Video endpoint account mode: Use this mode to create a standard email account for your
XT Series endpoint. You can invite the endpoint to the meeting as an attendee. You can use
these account details to see all meetings for which the endpoint is invited as an attendee.
This mode requires IT Administrator access to the Microsoft Exchange server to create a
standard email account for your endpoint.
August 2020
FQDN field descriptions
Description
Type the string that begins after the https:// and
before /portal.
https://<Meeting FQDN>/portal/tenants/
default/?ID=<MeetingID>
This example is for Avaya Meetings Server but you
can specify any mapping.
Type the FQDN of the SIP or H.323 Edge server
that is being used by the Avaya Workplace Client
solution.
You can leave this field as blank if the XT Series
endpoint is registered to a server (SIP or H.323)
that can place a call in this solution or in other
solutions by adding a prefix to the virtual room.
If your endpoint is external and not registered to this
solution, use the address specified in the invitation
details after the@ ("Room Device Access" section).
Type the relevant prefix if your endpoint is
registered to a SIP or H.323 Edge server that
requires a prefix to reach a virtual room in another
solution.
Select SIP or H.323.
Description
From the web interface only, select Save to retain
your updates.
Deployment Guide for Avaya XT Series
Comments on this document? infodev@avaya.com
on page 224.
224