Administering Avaya Spaces

Administering Avaya Spaces© 2021, Avaya Inc. All Rights Reserved.
Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer “Documentation” means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or Documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. “Hosted Service” means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third Party Components “Third Party Components” mean certain software programs or portions thereof included in the Hosted Service may contain software (including open source software) distributed under third party agreements (“Third Party Components”), which contain terms regarding the rights to use certain portions of the software (“Third Party Terms”). The Third Party Terms that apply is available in the products, Documentation or on Avaya’s website at: https:// support.avaya.com/Copyright or such successor site as designated by Avaya. Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE H.264 CODEC OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP:// WWW.MPEGLA.COM. Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. Preventing Toll Fraud “Toll Fraud” is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: https://support.avaya.com or such successor site as designated by Avaya.
September 2021 Administering Avaya Spaces 4 Comments on this document? [email protected]
Programming command script examples for the Avaya Spaces Calling extension................. 42 General programming command script parameter descriptions........................................... 43 Dialing rule settings......................................................................................................... 46
Chapter 8: Slack integration configuration.......................................................................... 48 Configuring the Equinox Cloud Client application in your company profile.................................. 48 Integrating Avaya Assistant with your Slack workspace............................................................ 49
Chapter 9: Citrix environment configuration....................................................................... 50 Citrix client requirements........................................................................................................ 50 Citrix server requirements...................................................................................................... 50 Avaya Spaces limitations for Citrix environments..................................................................... 51 Configuration recommendations............................................................................................. 51 BCR configuration and usage................................................................................................. 52
Chapter 12: Resources........................................................................................................... 58 Documentation...................................................................................................................... 58
Purpose This document provides information about advanced administration tasks for Avaya Spaces. It is primarily intended for company, system, and network administrators.
This document includes information about the following:
• Configuring hosts and protocols in your network.
• Setting up the company and domain.
• Adding users to the company.
• Creating a login policy, which you can use to restrict the available login options.
• Using Admin Area to manage company settings, users, and subscription plans.
• Configuring the Avaya Spaces Calling extension in your company profile.
• Configuring Slack integration.
• Configuring Citrix environment integration.
This document does not include information about using Avaya Spaces. For general usage information, including information about using Avaya Spaces with other applications, see Using Avaya Spaces. You can also get quick reference information from the Avaya Spaces articles on the Avaya Documentation Center.
Change history
Issue Date Summary of changes Issue 3 September 21, 2021 • Added information about managing company-level permissions in the
Admin Area.
• Updated Feature comparison for each license type on page 33 with information about the new Essential license options and other minor clarifications.
Table continues…
advanced administration information.
Usage information for end users is now in a separate document called Using Avaya Spaces.
Change history
Avaya Spaces is a cloud-based solution designed for team collaboration. With Avaya Spaces, you can host meetings, send chat messages, and manage posts and tasks. Avaya Spaces can also be integrated with other extensions and applications. Before using Avaya Spaces, you must set up a company, domain, and users. Ensure that you also add the avayacloud.com domain to the white list for the company site. Avaya Spaces uses JWT and OAuth2 for authentication and authorization. You can configure the login policy of your company and restrict which authentication mechanisms are available. For example, you can choose to only allow Microsoft Office 365 Single Sign-On (SSO) authentication and disable all other login options. Many management functions are available through the Admin Area. You can manage:
• Company and domain settings • Users • Subscription plans and licensing
You can allocate the Business or Power licenses to company users. If you do not assign a license to a user, the free Essential license is automatically assigned.
Related links Editing your company details on page 24 Inviting users to your company on page 28 Managing your subscription plan on page 30 Allocating user licenses on page 31
Supported browsers and operating systems Supported operating systems for the desktop application The Avaya Spaces desktop application is available for the following operating systems:
• Windows 10 • Mac 10.15 and later
Supported browsers for the web interface The web version of Avaya Spaces supports the following web browsers:
• Firefox 77 and later
• Edge 83 and later
• Chrome 83 and later
• Firefox 77 and later
Avaya Spaces components Avaya Spaces is comprised of the following solution components:
Avaya accounts
Component Description Avaya accounts A Cloud-native licensing engine, which provides a correlation of licensed
users, companies, and applications, including Avaya Spaces. You can integrate this component with identity providers, such as Google or Office 365, for authentication and authorization.
Media Platform-as-a-Service (MPaaS)
Avaya Spaces provides audio, video, and web conferencing capabilities. The meetings are hosted on a common Avaya-owned service, which is based on MPaaS. This embedded component provides features for managing multimedia meetings, but it is decoupled from the adopting Avaya Spaces application.
Google Cloud Avaya Spaces is a cloud-native service that uses Google Cloud Platform services, such as the Google Compute Engine. As part of its service offering, Google Cloud provides networking, computation, storage, encryption, and resiliency capabilities.
PSTN phone Licensed users can schedule a conference within Avaya Spaces. If dial-in options are available, anyone can join the conference using a PSTN- connected phone if they have the space ID and password (if defined).
Avaya Spaces application Avaya Spaces is a front-end application that delivers collaboration features to end users.
Table continues…
WebRTC-enabled browser. Mobile application The Avaya Spaces mobile application is supported on Android and iOS
mobile devices. Download the application from the Google Play or Apple App Store.
Role-based access control Avaya Spaces synchronizes with the data stored on Google Cloud. You cannot directly access the data on the Cloud. Avaya Spaces gathers and stores data from company administrators and end users.
Company administrator data Avaya Spaces gathers the following company administrator data:
• Company-specific information, such as users and associated licenses. • Account information, including user names, email addresses, photos, phone numbers, and
company details.
End user data Avaya Spaces gathers the following end user data:
• Account information, including user names, email addresses, photos, phone numbers, and company details.
• User preferences. • Content posted in a space, including text, files, and images.
Your role within a space affects what you can access. For more information about group space roles, see Using Avaya Spaces.
Data storage and encryption The Avaya Spaces application is built on Google Cloud. Data is stored on the cloud back-end application and in Avaya Spaces.
• Data required by the Cloud application is stored in an encrypted format through Google Cloud.
• Data required by the Avaya Spaces web interface is stored in the browser. Browser data can be stored in the cache or as cookies.
• Data required by the mobile application is stored on the mobile application container service provided by the device operating system.
Administration overview
Personal data encryption When data is transmitted over a network, it is encrypted. Google Cloud stores personally identifiable information. The REST encryption controls for data stored on Google Cloud are provided through Google storage services.
• All stored data is encrypted. • All client-server data connections are encrypted in transit with TLS 1.2 or higher. • When dialing into an audio conference through a PSTN phone, Avaya Spaces cannot ensure
the end-to-end encryption of the voice signaling path across global service provider networks.
Data storage and encryption
Chapter 3: Network access configuration
Use this chapter to configure Avaya Spaces from behind secure firewalls and proxies. This information is intended for network administrators.
When configuring your network, remember the following:
• Avoid whitelisting based on IP address. These addresses can change dynamically.
• Add the avayacloud.com domain to your network whitelist.
• Leave HTTP headers, such as Authorization, intact.
Required hosts and protocols Avaya Spaces uses the following transport protocols:
• HTTPS and WSS. • WebRTC, including ICE, STUN, and TURN protocols over DTLS-SRTP. • SIPS over TCP/TLS.
Use TLS traffic for HTTPS and WSS. TLS-inspection should support both or have an exception for Avaya Spaces hosts. For all Avaya Spaces features to function normally, ensure that the following settings are unrestricted. In the following table, the media host IP addresses for UDP are provided in the CIDR format.
spaces.sip.mpaas.avayaclo ud.com
5061 SIPS TCP/TLS For Avaya CU360 and Avaya XT Series Room System connectivity in SIP mode.
*.googleapis.com 80,443 HTTPS TCP/TLS For file sharing. *.esna.com 80,443 HTTPS TCP/TLS For mobile application
authentication. ASN of 15169 5228,5229,52
302 TCP TCP/TLS For push notifications.
accounts.google.com 80,443 HTTPS TCP/TLS For SSO. login.microsoftonline.com 80,443 HTTPS TCP/TLS For SSO. login.salesforce.com 80,443 HTTPS TCP/TLS For SSO. *.avaya.com 80,443 HTTPS TCP/TLS For SSO. *.gstatic.com 80,443 HTTPS TCP/TLS Content Delivery Network
(CDN). spacesip.net 5061 SIPS TCP/TLS Allows SIP connectivity. 155.184.0.0/20
155.184.16.0/22
3000-4999 SRTP/SRTCP UDP Secure low latency audio and video traffic.
This is the preferred transport protocol for media.
Dynamic 80 TURN TCP For media tunneling. These options are:
• Only used if preferred transport media fails.
Dynamic 443 TURN TCP/TLS
1 Includes spaces.avayacloud.com, spacesapis.avayacloud.com, spacesapis-socket.avayacloud.com mpaas.avayacloud.com, us-central1-mpaas-production-230415.cloudfunctions.net, storage.googleapis.com, and lh3.googleusercontent.com.
2 If you cannot open these ports without IP address restrictions, add all of the goog.json addresses to the whitelist.
Required hosts and protocols
guests.
Media transport guidelines UDP is the preferred media protocol because it results in the best user experience. Tunneling media over TCP or TLS is available for highly restrictive firewalls, but avoid using it as the primary method for accessing Avaya Spaces. To ensure that media traverses your network firewall securely, configure an address-restricted dynamic cone NAT or a port-restricted dynamic cone NAT for the specified UDP port range. All major firewall vendors support this configuration. Avoid using a symmetric NAT because it can result in sub-optimal tunneling of audio or video and connection failures. Since media is sensitive to latency, connect to the internet through the shortest path possible to reduce round trip times and improve the quality of service. You can use the media host IP addresses for UDP to program software-defined network infrastructure to recognize media traffic and route to the internet seamlessly. This configuration is recommended for large enterprises with multiple sites and a centralized network data center architecture.
Network access configuration
Avaya Spaces supports personal and company accounts. To manage users and allocate licenses for a company, first configure your company.
Use this chapter to:
• Add users one at a time or in bulk
• Manage the users you add
You can perform additional management tasks from the Admin Area in Avaya Spaces.
Related links Admin Area management on page 23
Adding a company and domain About this task Adding a company and domain is an essential prerequisite for all other administration tasks in this document. Set up your company to add users, manage login and message retention policies, allocate licenses, and configure integration with other applications. If required, you can add more than one domain for a company. After adding a domain name, you must verify it unless the account you are using has site permissions.
Procedure 1. In your browser, navigate to https://accounts.avayacloud.com and log in with your
administrator credentials.
Alternatively, to access this web page, you can navigate to Profile & Account in Avaya Spaces when you are logged in with your administrator credentials.
2. To add a company, do one of the following:
• At the top of the screen, click the arrow next to your profile picture and click Add Company.
3. On the General tab, type a company name and description.
4. Click Save.
6. Enter the domain name.
You can find the domain in your company email address. For example, if your email address is [email protected], then xyzenterprises.com is the domain name.
7. Next to the domain name, click Verify to verify the domain name.
If the account has site permissions, you do not need to verify the domain.
8. Follow the on-screen instructions to verify the domain on your DNS server.
9. Click Verify.
If you cannot complete the verification independently, click Manual verify to have Avaya personnel complete the verification process. This process could take several business days to complete.
Next steps Add users to your company.
Related links Pairing domains on page 38 Adding a company and domain (video)
Company and user configuration
Options for adding users After adding your company and domain, add users. Each user's email address must be within the configured domain. For example, if your domain is xyzenterprises.com, the user email address must end with @xyzenterprises.com. You can do one of the following:
• Add one user at a time • Import users in bulk using a CSV file
After adding users, you can edit or delete them. You can also manage users from the Admin Area in Avaya Spaces. The company policies you set apply to all users you add to your company. You can allocate the Business or Power licenses to company users from the Admin Area. The assigned license affects which features users can access.
Related links Admin Area management on page 23 Allocating user licenses on page 31 Feature comparison for each license type on page 33
Adding one user at a time About this task You can invite company users one at a time. If you only need to add a few users, this is the easiest way to do it. If you need to add many users, see Importing users in bulk on page 18.
Before you begin • Add your company and domain. You must also verify the domain. • The users you add must have an email address within the configured domain.
Procedure 1. From https://accounts.avayacloud.com, click Manage Companies and click your company
name.
3. Enter the user's first and last name.
4. Enter the user's email address.
If the domain is xyzenterprises.com, then [email protected] is an example of a valid email address.
5. Click Save.
6. (Optional) Repeat this procedure to add another user.
Result The users you add receive an invitation email, which they must accept to become active users. You can click Invites Waiting Confirmation to view the list of pending users who have not yet accepted the invitation. To view or manage active users, click Active.
Related links Adding a company and domain on page 15 Managing pending user invitations on page 20 Editing an active user on page 21 Deleting a user on page 21 Adding company users (video)
Importing users in bulk About this task You can invite users to your company in bulk using a CSV file. This option enables you to import multiple users simultaneously. Create the CSV file using a simple text editor, such as Notepad.
Before you begin • Add your company and domain. You must also verify the domain.
name.
2. On the Manage Users tab, navigate to Tools > Import From CSV.
3. From Separator, select one of the following options to define how data is separated:
• Comma: The data items are separated by commas. Each comma-separated item is displayed in a separate cell in the CSV file.
• Tab: Press the Tab key to separate each data item. Each item is displayed in a separate cell.
4. From Quotechar, select one of the following:
• Single Quote: Use single quotes (') to split the text into two lines within the same cell. This option does not separate the text into different cells.
• Double Quote: Use double quotes (") to separate data into columns.
In the following example image, Id is the first column, Name is the second column, and Address is the last column:
5. (Optional) In Tip, click the examples to download sample files with the correct formatting.
Use the samples as a guide for creating your file.
Options for adding users
The following example shows a simple CSV file for importing users with only their email addresses:
6. In File, click Choose file and locate the CSV file with the user data to attach.
7. Click Import.
When the import is completed successfully, the number of invited users is displayed.
8. (Optional) To return to the Manage Users page, click Back to Manage Users.
Result The users you add receive an invitation email, which they must accept to become active users. You can click Invites Waiting Confirmation to view the list of pending users who have not yet accepted the invitation. To view or manage active users, click Active.
Related links Adding a company and domain on page 15 Managing pending user invitations on page 20 Editing an active user on page 21 Deleting a user on page 21 Importing company users to Avaya Spaces (video)
Managing pending user invitations About this task When you add users, they receive an invitation email, which they must accept to become active users. You can view the list of pending users who have not yet accepted the invitation.
name.
2. On the Manage Users tab, click Invites Waiting Confirmation.
3. (Optional) To resend the invitation, click Resend Verification next to the user's name.
4. (Optional) To remove the previous invitation, click and click OK to confirm.
Editing an active user About this task When users you add accept the invitation, they become active users. You can edit the name and email address of an active user anytime.
name.
2. On the Manage Users tab, find the user and click Edit. 3. (Optional) Update the user's first and last name.
4. (Optional) Update the user's email address.
5. Click Save.
6. (Optional) To return to the Manage Users page, click Back to Manage Users.
Deleting a user About this task You can delete an active user that you added accidentally or that no longer works for your company. If you want to delete more than one user, repeat this procedure.
name.
3. Click OK to confirm.
Chapter 5: Admin Area management
After adding your company, you can perform management functions from the Admin Area. You must be a company administrator to access the Admin Area. Other company employees cannot access it. This chapter describes how to use the Admin Area. The following tabs are available in the Admin Area:
Tab Purpose Settings To manage your company settings. You can add domains, configure a
company-wide message retention policy, and enable Avaya Spaces Calling for company users.
Users To invite and manage users. Plans To manage your company's subscription plan. You can purchase Business
and Power licenses and allocate these licenses to users.
Accessing the Admin Area About this task After the initial company setup is complete, you can access the Admin Area. Use the Admin Area to manage company settings, users, and licenses.
Before you begin Navigate to https://accounts.avayacloud.com and set up your company.
Procedure To open the Admin Area, do one of the following:
• In your browser, navigate to https://spaces.avayacloud.com/admin and log in with your administrator credentials.
• In Avaya Spaces, click the arrow next to your profile picture at the top of the screen and then click Admin Area.
Related links Adding a company and domain on page 15 Signing in to the administration portal (video)
Working with the Settings tab From the Admin Area Settings tab, you can manage your company configuration. You can change the company name and description, add domains, and set up a message retention policy. You can also enable the Avaya Spaces Calling feature.
Editing your company details About this task Use the Admin Area Settings tab to manage your company. In the General area, you can update your company name and description.
Procedure 1. In the Admin Area, click the Settings tab and navigate to the General area.
2. In the Company Name field, type a new name for your company.
3. In the Description field, type a company description.
4. Click Save to apply the changes.
Admin Area management
Related links Adding a company and domain on page 15
Adding a domain from the Admin Area About this task When you first set up your company, you must add and verify the company domain. You can use the Admin Area to add another domain. When you add users, they must have an email address within one of the configured domains.
Procedure 1. In the Admin Area, click the Settings tab and navigate to the Domains area.
2. Click Add Domain.
3. Enter the domain name and click OK.
You can find the domain in your company email address. For example, if your email address is [email protected], xyzenterprises.com is the domain name.
4. From https://accounts.avayacloud.com, click the Domains tab and verify the domain.
Related links Adding a company and domain on page 15
Deleting a domain About this task You can use the Admin Area to delete a company domain that you no longer require.
Procedure 1. In the Admin Area, click the Settings tab and navigate to the General area.
2. Click next to the domain name.
3. Click OK to confirm.
Working with the Settings tab
Procedure 1. In the Admin Area, click the Settings tab.
2. Under Message Retention, select one of the following options to specify when data is deleted:
• Use system policy: Select this option to use the system default value of 730 days. To use this option, you and the space admin must select it. Data is automatically deleted after this time.
• Delete messages after: All data is deleted after the number of days you specify. A space admin can set a lower value for a specific space.
There is a delay of approximately 24 hours before data is deleted. If you set the wrong value by mistake, you have some time to fix it before the data is permanently removed.
• Keep messages forever: Data is never deleted.
3. Click Save.
Enabling the Avaya Spaces Calling feature About this task When Avaya Spaces Calling is enabled, company users can make audio calls through a soft phone or using the Avaya Spaces Calling extension in the Google Chrome or Microsoft Edge web browser. The Avaya Spaces Calling feature is automatically enabled in some countries. If it is not enabled, you can enable it manually from the Admin Area.
Important: If you enable the Avaya Spaces Calling extension, ensure that you also configure the extension in your company profile. You can do this from the Apps tab at https:// accounts.avayacloud.com. For more information, see Avaya Spaces Calling extension configuration on page 40.
2. Under Avaya Spaces Calling, enable the Enable Avaya Spaces Calling switch.
3. Select one or more of the following options:
• Avaya Spaces Calling Chrome Extension: To use the Avaya Spaces Calling extension in the Google Chrome or Microsoft Edge browser with a Windows or Mac desktop. To use this extension, you must have an operational Avaya Aura® or IP Office WebRTC infrastructure. You must also enable the extension in your company profile.
• Avaya Workplace Client: To make audio calls through Avaya Workplace Client. This option requires an Avaya SIP infrastructure.
For information about using Avaya Workplace Client, see Using Avaya Workplace Client for Android, iOS, Mac, and Windows.
• Any dialing application (Tel URI): To make audio calls using a non-Avaya soft phone.
4. Click Save.
Related links Administering Avaya Spaces Calling (video)
Managing company policy permissions About this task From the Admin Area, you can set company-level permissions that apply to all spaces. At the company level, you can manage which users can create content in a space and whether users can upload files. Content creation affects all content in a space, including chat messages, posts, and tasks. In the web interface or desktop application, a space admin can manage permissions for members or guests within a specific space. The company-level permissions you configure in the Admin Area affect the permissions that the space admin can set for a specific space. For example, if you disable Attachment Upload in the Admin Area, the space admin cannot manage file upload permissions within the space.
2. Navigate to Company Policy to manage company-level permissions.
3. In the Space User Role Policy area, do the following:
a. For users to create content within a space, ensure that the Content Creation check box is selected.
b. Select which user roles can create content.
For example, if you do not want guests to create content in a space, clear the Guest check box. Only select Admin and Member.
Working with the Settings tab
4. In the User Role Policy area, ensure that Attachment Upload is selected to allow company users to attach files within a space.
This setting applies to all company users. If you disable the Attachment Upload option, users cannot upload files in any space.
5. Click Save Policy Settings to save your changes.
Working with the Users tab You can add and manage users at https://accounts.avayacloud.com. Many of these user management functions are also available from the Users tab in the Admin Area.
Inviting users to your company About this task From the Users tab in the Admin Area, you can invite a user with their email address or import users in bulk using a CSV file.
Procedure 1. In the Admin Area, click the Users tab.
2. Click Invite New User. 3. Do one of the following:
• To invite a single user, type the user's email address and click Invite.
• To add users in bulk using a CSV file, click Import From CSV.
Related links Adding one user at a time on page 17 Importing users in bulk on page 18
Viewing active and pending users About this task When you add users, they must accept the invitation to become active users. In the Admin Area, you can view active users and pending users who have not yet accepted the invitation.
2. (Optional) To view and manage pending users who have not yet accepted the invitation, select List Pending Users Invites.
3. (Optional) To view and manage active users, select List Active Users.
The license allocated to each active user is also displayed.
Deleting a pending user invitation About this task You can delete a pending user invitation from the Admin Area. For example, this option is useful if you sent an invitation by accident and want to rescind it. You can also manage pending user invitations from https://accounts.avayacloud.com.
2. Select List Pending Users Invites.
3. From the list of pending user invites, locate the user invitation to delete.
4. Next to the user's name, click .
5. When prompted, click OK to confirm.
Related links Managing pending user invitations on page 20
Deleting an active user from your company About this task You can delete an active user from the Admin Area. For example, you can delete an active user that you added accidentally or that no longer works for your company. You can edit an active user from https://accounts.avayacloud.com. However, you cannot edit a user from the Admin Area.
2. From the list of active users, locate the user you want to delete.
3. Next to the user's name, click .
4. When prompted, click OK to confirm.
Related links Editing an active user on page 21
Working with the Users tab
Deleting a user on page 21
Working with the Plans tab You can use the Admin Area Plans tab to purchase licenses and manage how licenses are allocated to users.
Managing your subscription plan About this task Use the Admin Area to manage your company's subscription plan. You can modify the number of users in your company and select a contract duration for your licensing plan. You can purchase Business or Power licenses.
Procedure 1. In the Admin Area, click Plans.
The Admin Area displays your current plan details.
2. Do one of the following:
• If you have not yet purchased licenses for your company, click Purchase.
• To update your existing license plan, click Upgrade.
The Admin Area redirects you to https://www.avaya.com/en/products/ucaas/spaces- pricing/.
3. Based on the number of users in your company, select a range.
You can use the slider or the drop-down menu to select a user range. For example, if your company has 2500 users, select 2000-3999.
4. Select the contract duration.
For example, you can select a 3-year contract.
Related links Feature comparison for each license type on page 33
Allocating user licenses About this task After purchasing Business and Power licenses for your company, you can allocate licenses to users. Only one license can be assigned to each user. You can allocate a license to one or more users at a time. You can change the license allocation anytime. If you do not allocate a license to a user, the free Essential license is automatically assigned.
Working with the Plans tab
2. Click Manage.
3. In the Unallocated Users list, select the check box next to the users to whom you want to allocate a license.
You can allocate licenses to one or more users at a time.
4. At the top of the screen, click the Actions button.
5. Select one of the following:
• Allocate to Spaces Business: To allocate the Business license.
• Allocate to Spaces Power: To allocate the Power license.
The users are moved to the Allocated Users list.
Related links Allocating licenses to company users (video)
Deallocating user licenses About this task You can deallocate user licenses and then assign new licenses to those users. If you do not assign a new license to a user, the free Essential license is automatically assigned.
Procedure 1. In the Admin Area, click the Plans tab.
2. Click Manage.
3. In the Allocated Users list, select the check box next to the users whose licenses you want to deallocate.
You can deallocate licenses from one or more users at a time.
4. Click Deallocate.
Related links Allocating user licenses on page 31
Feature comparison for each license type The following license types are available:
• Essential: This is the basic license, which is free of charge. • Business: This is the mid-tier license. This license provides additional features that are not
available with the Essential license, including video conferencing and unlimited storage. • Power: This is the advanced license. This license provides features that are not available
with the Essential and Business licenses. You can purchase Business and Power licenses and allocate them to users. If you do not allocate a license to a user, the free Essential license is automatically assigned. The following table summarizes the features available for each license type:

Up to 100 participants

Table continues…
3 Enable large meetings for a space before hosting meetings with more than 250 participants.

Unlimited storage. Each file can be a maximum of 2 GB.
Group task management

API access
Fair use policy Avaya Spaces is a shared resource, so your usage can affect others. Avaya Spaces uses a Fair Use Policy (FUP) for monitoring and controlling usage to ensure that everyone has fair access to the available capacity and resources. The FUP is used to monitor, notify, and restrict anyone who crosses the following simultaneous usage thresholds. The following table indicates the number of meetings or calls you can have at the same time:
Power Business Essential
Simultaneous group meetings or conference calls hosted by the space creator
5 3 1
5 3 0
Avaya Spaces Calling
Avaya Aura® or IP Office PBX calls, excluding calls answered by another endpoint
5 3 0
Related links Allocating user licenses on page 31 Deallocating user licenses on page 32 Understanding user licensing (video)
By default, Avaya Spaces supports the following login options: • Native login using standard Avaya Spaces account credentials • Google SSO using your Google account credentials • Microsoft Office 365 SSO using your Microsoft account credentials • Salesforce SSO using your Salesforce account credentials • Avaya SSO using your Avaya credentials • Enterprise SSO using the SSO credentials of your company
To restrict the available login options, you can create a login policy. The login policy affects all company users within the configured domain.
Domain pairing options If different login options are set for different domains, you can choose to pair the domains for users to log in using the login options enabled for either domain. The following image illustrates a domain pairing scenario:
Domain A Domain B
For example, [email protected] must log in using Google
Only allows Salesforce SSO login For example, [email protected] must log in using Salesforce
Google and Salesforce enabled
[email protected] and [email protected] can log in using Google and Salesforce
Important: If you choose to pair domains, avoid separating them. Separating paired domains can cause complications because users from both domains have new email addresses created for the disconnected domain.
Restricting the available login options About this task You can configure a login policy to restrict the login options available to company users.
name.
2. On the Policies tab, click Login Options.
The Allow All check box is selected by default indicating all login methods are available. To restrict the available options, you must clear the Allow All check box.
3. Ensure that only the login methods to allow are selected.
At least one login method must always be selected.
4. If your company has multiple domains, select the domains for which you want this login policy to apply.
You can select Allow All if you want the login policy to apply to all configured company domains.
5. Click Save.
6. When prompted, click Save to confirm.
Result When company users enter their email address on the Avaya Spaces Login screen, they see the available login options based on the login policy you set. For example, if you disable the native login option, they cannot see the Password field or Sign In button. Company users can only log in using the login options you enable.
Related links Configuring your company's login security policy (video)
Restricting the available login options
Pairing domains About this task If different login options are set for different domains, you can choose to pair the domains for users to log in using the login options enabled for either domain. If one domain allows all login methods, all login methods are available for both paired domains. One domain can be paired with any number of others. Each pairing is a one-to-one relationship that does not affect any other pairing involving either domain.
Important: If you choose to pair domains, avoid separating them. Separating paired domains can cause complications because users from both domains have new email addresses created for the disconnected domain.
name.
2. On the Policies tab, click Login Options.
3. Clear Allow All under the “Allowed emails with the following domains” section.
4. In Enter a valid domain to white list, enter the domain to pair with and click Add.
5. When prompted, click Add to confirm.
Login policy administration
6. Click Save.
7. Ensure that the administrator for the other domain repeats this procedure.
If the administrators for both domains do not follow this procedure, then the pairing is unsuccessful. Both domains must accept the pairing.
Pairing domains
Chapter 7: Avaya Spaces Calling extension configuration
Install the Avaya Spaces Calling extension from the Google Chrome web store and use it to make audio calls from your Avaya telephone system. If Avaya Spaces Calling is not already enabled, you can enable it from the Settings tab in the Admin Area. Before company users can use the Avaya Spaces Calling extension, you must configure it in your company profile.
This chapter describes how to configure the extension in your company profile.
Related links Enabling the Avaya Spaces Calling feature on page 26
Avaya Aura® and IP Office component configuration To use the Avaya Spaces Calling extension, you must have an operational Avaya Aura® or IP Office WebRTC configuration.
Avaya Aura® configuration If you have an Avaya Aura® infrastructure, ensure that you configure Avaya Aura® Web Gateway and Avaya Aura® Device Services. When you configure your company profile to support the Avaya Spaces Calling extension, point Avaya Spaces to your Avaya Aura® Web Gateway FQDN. For more information about Avaya Aura® Web Gateway and Avaya Aura® Device Services, see the following documents:
• Deploying the Avaya Aura® Web Gateway • Administering the Avaya Aura® Web Gateway • Deploying Avaya Aura® Device Services • Administering Avaya Aura® Device Services
These documents are available on the Avaya Support and Avaya Documentation Center websites.
IP Office configuration If you have an IP Office infrastructure, ensure that you configure Avaya one-X® Portal for IP Office. When you configure your company profile to support the Avaya Spaces Calling extension, point Avaya Spaces to your IP Office FQDN.
For more information about IP Office configuration and administration, see the following documents:
• IP Office SIP Telephone Installation Notes • Installing and Maintaining an IP Office Application Server • IP Office SIP Phones with ASBCE • IP Office Resilience Overview
Configuring the Avaya Spaces Calling extension in your company profile
About this task Before company users can use the Avaya Spaces Calling extension, you must configure it in your company profile. As part of this configuration process, you must configure a script pointing to your Avaya Aura® Web Gateway or IP Office FQDN.
name.
2. On the Apps tab, do the following to add Avaya Spaces Calling Extension if it is not already present:
a. Click Configure New App.
b. From the drop-down list, select Avaya Spaces Calling Extension.
3. In the Avaya Spaces Calling Extension Application Settings window, enter the appropriate programming command script for your environment.
4. Click Save.
The new profile settings are used the next time company users log in to the extension.
Related links Programming command script examples for the Avaya Spaces Calling extension on page 42 General programming command script parameter descriptions on page 43
Programming command script examples for the Avaya Spaces Calling extension
When configuring the Avaya Spaces Calling extension in your company profile, you must enter a JSON script that is appropriate for your Avaya Aura® or IP Office environment. The script settings are case sensitive. Change the Name parameter in the script to a suitable description for your environment.
Avaya Aura® script example The following example includes two profiles in a single script: { "Aura_Web_Gateway_Server_Profile": [{ "Name": "Alpha Aura", "Address": "alpha.example.com", "AccountsToken": true, "LogDownload": true, "DialRule": false }, { "Name": "Beta Aura", "Address": "beta.example.com" "AccountsToken": true,
Avaya Spaces Calling extension configuration
General programming command script parameter descriptions The following table describes the parameters in the Avaya Spaces Calling extension programming command script. It also indicates whether the parameters are applicable for Avaya Aura®, IP Office, or both.
JSON parameter Applicable for Avaya Aura® or IP Office?
Description Values and examples
Name Both Enter a name for the profile. This is a mandatory parameter.
If there are multiple Avaya Aura® or IP Office profiles, you will see the name when logging in to the extension.
Example name: IPO Gamma
environment, enter your Avaya Aura® Web Gateway FQDN.
If you are using an IP Office environment, enter your Avaya one-X®
Portal FQDN.
To access the service from the public internet, the public DNS must resolve the address you specify to the public IP address on Avaya Session Border Controller for Enterprise (Avaya SBCE).
Example address: onexserver.example .com
AadsAddress Avaya Aura® only Enter the Avaya Aura®
Device Services FQDN. This is an optional parameter.
If this parameter is set, the Avaya Spaces Calling extension searches for contacts and retrieves dialing rule configuration information from Avaya Aura®Device Services. In this case, the DialRule parameter setting is ignored.
Avaya Aura® Device Services does not currently support Avaya Spaces SSO. Therefore, the AccountsToken parameter is always treated as false.
Example aads.example.com
Table continues…
AccountsToken Both This optional parameter is for Avaya Spaces SSO. Set this parameter to true if your environment has SSO enabled. The default value is false.
Set to true or false
LogDownload Both Set this optional parameter to true to enable users to download logs from the Avaya Spaces Calling extension interface.
The default value is true.
DialRule Both This is an optional parameter.
When set to true, an administrator must set global dialing rules.
When set to false, end users can configure local dialing rules through the Avaya Spaces Calling extension interface.
The default value is false.
STUNHost IP Office only This is an optional parameter.
To enable service access from internal and public networks, this FQDN must be set to the Avaya SBCE public address on a public DNS and the Avaya SBCE private address on an internal DNS.
Example: stunserver.example .com
The standard STUN port is 3478.
Example: 3478
Table continues…
AutoFailover IP Office only Set this optional parameter to true if redundant WebRTC or Avaya one-X® Portal gateways are available.
When this parameter is set to true, if the primary server goes down, the application tries to automatically connect to the secondary server.
When this parameter is set to false, the interface displays an error when the primary server goes down because connectivity with a secondary server cannot be established.
The default value is false.
VoiceMail IP Office only This is an optional parameter.
Match this value to the IP Office voicemail short code. If not specified, the default value of *17 is used.
Example: *17
Dialing rule settings When DialRule is set to true, you must configure the following global dialing rule parameters in the JSON script for both Avaya Aura® and IP Office:
JSON parameter Description Values and examples OutsidePrefix The prefix used on the telephone
system for placing external calls.
For example, in some cases, you must enter 9 before you can make an external call outside of your company.
9
JSON parameter Description Values and examples CountryCode The country code. For example,
the country code is 1 in the United States and 44 in the United Kingdom.
1
CityCode The area code. To include multiple area codes, use a comma-separated list.
555 Example with multiple area codes: 555,613,777
PbxPrefix Specify if the telephone system has its own prefix within a network.
538
LongDistancePrefix The prefix for making external calls to national, non-local phone numbers.
For example, 1 is the long distance prefix in North America.
1
InternationalPrefix The prefix used for external calls to international phone numbers.
For example, the international calls prefix in North America is 011.
011
ExtensionLength The length of internal extension numbers. To specify multiple values, use a comma-separated list.
4 Example with multiple extension length values: 3,4
NationalLength The length of national phone numbers, including the area code. For example, a national number in North America has 10 digits.
To specify multiple values, use a comma-separated list.
10 Example with multiple values: 10,12
RemoveAreaCode In some areas, you can make local calls without entering an area code.
Set this parameter to true to remove the area code. By default, this parameter is set to false.
ApplytoPlusNumber The default value is true, which means that the dialing rules are applied to phone numbers that use the + format.
Chapter 8: Slack integration configuration
Integrate Avaya Assistant with Slack and configure it to work with your Avaya Spaces environment. When the integration is complete, Avaya Spaces company users can send an invitation to their Avaya Spaces meeting room from a Slack channel. The Slack channel members can also launch the Avaya Spaces meeting from Slack.
Configuring the Equinox Cloud Client application in your company profile
About this task You must configure Equinox Cloud Client settings on the Apps tab of your company profile. The programming command script that you enter during this configuration process requires you to point Avaya Assistant to your Avaya Equinox® Conferencing portal URL. The script values are case-sensitive. The values you enter do not affect any other applications. This configuration is not required if you are using Avaya Equinox® Meetings Online.
Important: Any settings that you configure through the Conferencing application override the settings you configure here. To clear the changes made through the application interface, you must remove the application and resinstall it, so the values you configure in this procedure are used instead.
name.
2. On the Apps tab, do the following to the add Equinox Cloud Client if it is not already present:
a. Click Configure New App.
b. From the drop-down menu, select Equinox Cloud Client. 3. In the Equinox Cloud Client Settings window, enter the following programming command
script: { "Meeting_Portal_Settings": [ {
"Meeting_Portal_Name": "Equinox Meetings", "Meeting_Portal_Url": "https://<yourportalURL>" } ] }
In this script, <yourportalURL> is the URL for the Avaya Equinox® Conferencing Portal.
You can optionally include the port number in the Conferencing portal URL.
For multi-tenant installations, add /portal/tenants/<tenant-id>/ to the end of the string. For example, https://yourportal.com:1234/portal/tenants/ toronto100/.
4. Click Save.
The new profile settings are used the next time company users log in to the application.
Integrating Avaya Assistant with your Slack workspace About this task Use Avaya Assistant to complete the integration with Slack.
Procedure 1. In your browser, navigate to https://assistant.apps.avaya.com/slack.
2. Click Add to Slack.
Avaya Assistant redirects you to the Slack platform.
3. In the Sign in to your workspace window, enter your Slack workspace URL.
For example, xyzenterprisesgroup.slack.com.
4. Click Continue.
5. Enter your Slack email and password, and then click Sign In.
6. To allow Avaya Assistant to access your Slack workspace, click Allow.
A confirmation message is displayed indicating that Avaya Assistant is successfully installed in your Slack workspace.
Result After completing this integration process, company users can use their Slack channel to start meetings in their Avaya Spaces meeting room. For more information about starting an Avaya Spaces meeting from Slack, see Using Avaya Spaces.
Related links Integrating Slack with Avaya Spaces (video)
Integrating Avaya Assistant with your Slack workspace
Chapter 9: Citrix environment configuration
To join Avaya Spaces meetings from a Citrix virtual desktop, follow the instructions in this chapter. You must configure the Citrix client and server. For optimal audio and video quality, ensure that you also configure Browser Content Redirection (BCR).
You can also use your Citrix virtual desktop environment with the Avaya Spaces Calling extension.
Citrix client requirements The Citrix client requires the following:
• Microsoft Windows 10 operating system • Google Chrome web browser with the Sites can send pop-ups and use redirects setting
enabled • Citrix Workspace application
Avaya recommends using Citrix Workspace application version 2002 or later for BCR and screen sharing. If you are using an earlier version, you can see content that others are sharing, but you cannot share your screen.
Related links Avaya Spaces limitations for Citrix environments on page 51
Citrix server requirements The Citrix server requires the following:
• Citrix Virtual Apps and Desktops 7, version 1811 or later • Virtual Delivery Agent operating system: Windows 10 (minimum version 1607) or Windows
Server 2016 • Virtual Delivery Agent web browser: Google Chrome version 72 or later
Related links Avaya Spaces limitations for Citrix environments on page 51
Avaya Spaces limitations for Citrix environments • BCR does not work with Citrix Receiver. You must install the Citrix Workspace application on
the client. • Citrix BCR supports Microsoft Windows 10 and Windows Server 2016. BCR does not support
other operating systems. • When using BCR, you cannot share your browser tab in an Avaya Spaces meeting. You can
still share an application or your entire screen. • Citrix BCR does not support push notifications, so Avaya Spaces does not display chat and
other message notifications. • BCR does not work with the Citrix Workspace application for Windows version 1912 Long
Term Service Release (LTSR) because of the removal of the embedded browser. For more information, see https://support.citrix.com/article/CTX270599. Avaya recommends using Citrix Application version 2002 Current Release (CR) or later.
• Citrix Workspace application version 2002 or later is required for screen sharing in an Avaya Spaces meeting. If you are using an earlier version, you can see content that others are sharing but you cannot share your screen.
• The Citrix server requires Citrix Virtual Delivery Agent version 1811.1 or later to support Google Chrome.
• With Citrix Workspace version 1905 and earlier, websites that use Integrated Window Authentication (IWA) might not work because BCR cannot interpret the Windows Security dialog box. This does not affect Avaya Spaces, but SSO websites used for authentication that employ IWA do not work.
• Google Chrome console logging is not supported.
Configuration recommendations Follow these recommendations to optimize your Avaya Spaces experience with a Citrix virtual desktop environment:
• On the Windows display settings, set the Scale and layout value to 100% or less. Avaya Spaces does not work correctly if the Windows display scale is larger than 100%.
• Configure the Citrix client to use high DPI for the best resolution and performance. Set this using Advanced Preferences on the Citrix Workspace taskbar.
• Enable BCR for the Citrix client and server.
Avaya Spaces limitations for Citrix environments
BCR policies in Citrix Studio The following table summarizes the available Citrix Studio BCR policy options:
Policy name Value Description Browser Content Redirection Allowed or Prohibited Enables or disables the BCR
feature.
Browser Content Redirection ACL Configuration
List of URLs Defines which websites to redirect to the local client. Wildcards are permitted but not as part of the protocol or domain.
Browser Content Redirection Authentication Sites
List of URLs Defines which websites can be used to authenticate the users on the sites listed under the Browser Content Redirection ACL Configuration policy.
Configuring BCR on the Citrix server About this task As an administrator, you must set up each Citrix server to make Client Fetch and Client Rendering work for BCR.
Before you begin • On the Citrix server, install Citrix Virtual Apps and Desktops 7. • On a Citrix client, install the Citrix Workspace application. Do not install Citrix Receiver. • Verify that Citrix Virtual Delivery Agent version 1811.1 or later is installed, because earlier
versions do not support Google Chrome.
Procedure 1. Open the Chrome browser on the Citrix server, go to https://chrome.google.com/webstore
and enter Browser Redirection Extension in the Search field. Install the extension.
Citrix environment configuration
2. Navigate to Citrix Studio on the Citrix server.
3. In the Policies settings, edit the Browser Content Redirection policy and click Allowed.
4. Add the following entries to the Browser Content Redirection ACL Configuration > Policies list: https://spaces.avayacloud.com/* https://accounts.avayacloud.com/* https://accounts.google.com/* https://login.microsoftonline.com/* https://login.live.com/*
This ACL configuration list defines which websites to redirect to the local client.
You can use wildcards in the list entries, but only after the protocol and domain. For example, after https://spaces.avayacloud.com/.
5. Add the following entries to the Browser Content Redirection Authentication Sites > Policies list. https://spaces.avayacloud.com/* https://accounts.avayacloud.com/* https://accounts.google.com/* https://login.microsoftonline.com/* https://login.live.com/*
Configure the list of URLs that support authentication using third-party websites, such as Google or Microsoft Office 365. These are the URLs for which BCR remains active (redirected) when navigating away from a URL in the ACL configuration list.
You must add any website used for SSO to the authentication sites list. A single website can have multiple URL entries in the list.
Related links BCR policies in Citrix Studio on page 52
Configuring BCR on a Citrix client About this task Work with virtual desktop users to ensure that BCR is configured on their Citrix clients. You can install the BCR extension from the Chrome web store. This extension redirects web pages in Citrix environments where BCR is enabled.
Before you begin On the Citrix client, install the Citrix Workspace application. Do not install Citrix Receiver.
Procedure 1. On the Citrix client, use the Google Chrome web browser to log in to the Citrix server.
You do not need to log in to the Citrix Workspace application.
2. Connect any devices, such as a microphone or camera, to the local client.
BCR configuration and usage
The Citrix Workspace application accesses these devices directly through the local client.
3. On the Citrix server virtual desktop, click Preferences and then click the Select Connections tab.
4. Under Microphone and webcams, set Session Settings to Do not connect. 5. Open the Chrome browser on the Citrix server, go to https://chrome.google.com/webstore
and enter Browser Redirection Extension in the Search field. Install the extension.
6. Use Chrome on the Citrix server to join an Avaya Spaces meeting.
When you browse to a website, the color of the BCR extension logo indicates the BCR status:
Green The connection is successful.
Grey The connection is not active or is idle.
The site URL is not allowed or not configured to use the BCR feature.
Red The site cannot connect to the Citrix server or the Citrix Workspace application on the client.
Verifying the Citrix configuration About this task After configuring BCR on the Citrix client and server, you must verify that both Client Fetch and Client Render are working.
Procedure 1. Using a local Windows client, connect to the Citrix Virtual Delivery Agent server.
2. Launch the Chrome browser on the Citrix Virtual Delivery Agent server and join an Avaya Spaces meeting.
3. Ensure that you can send and receive audio and video and that screen sharing is working properly.
Citrix environment configuration
Chapter 10: Third-party room system administration settings
You can join an Avaya Spaces meeting from the following third-party Poly room systems: • Poly Studio, Studio X30, and Studio X50 • Poly Group Series 310, 500, and 700
Generate a third-party room system URI in Avaya Spaces. You can then use that URI to make a call to Avaya Spaces from your Poly device. For more information about obtaining the URI in Avaya Spaces, see Using Avaya Spaces.
Important: Ensure that the spacesip.net protocol is unrestricted. For more information about protocols, see Required hosts and protocols on page 12.
Before making a call to Avaya Spaces, you must configure a few settings in your Poly web administration interface. The following procedure describes these settings at a high level.
Updating Poly administration settings About this task This high-level procedure summarizes the settings you must update in your Poly web administration interface before you can make a call to Avaya Spaces. The layout of the web administration interface varies depending on which Poly device you are using. For more information about Poly devices, see the following resources:
• For Poly Studio, see https://www.poly.com/us/en/products/video-conferencing/studio • For the Poly Group Series, see https://www.poly.com/us/en/products/video-conferencing/
group
Procedure 1. On the Poly web administration interface, navigate to one of the following paths depending
on the Poly system you are using:
• For Poly Group Series, navigate to Admin Settings > Network > IP Network.
• For Studio X30 or Studio X50, navigate to Call Configuration > SIP.
3. In Transport Protocol, select TLS.
4. Click Save to save your changes.
5. Navigate to one of the following paths on the Poly web administration interface:
• For Poly Group Series, navigate to Admin Settings > Security > Global Security > Encryption.
• For Studio X30 or Studio X50, navigate to Call Configuration > Call Settings.
6. In Require AES Encryption for Calls, select Required for All Calls.
Perform the following additional steps for the Poly Group Series.
8. On the Poly Group Series administration interface, navigate to Admin Settings > General Settings > System Settings > Call Settings.
9. Ensure that you select the Display System Name Instead of SIP Address check box to send the system name in the SIP invite.
Third-party room system administration settings
Chapter 11: Troubleshooting
Avaya Spaces does not work properly due to firewall or proxy server settings
Condition Avaya Spaces does not work as expected. Avaya Spaces might time out unexpectedly or the space might be greyed out. Users cannot join meetings or access other content in the space.
Cause This issue can occur if firewall port settings are not correctly configured.
Solution Review the “Network access configuration” chapter. Configure your network firewall settings using the table in Required hosts and protocols on page 12.
Related links Network access configuration on page 12
Documentation Avaya Spaces customer documentation, articles, and videos are available on the Avaya Documentation Center. You can also find Avaya Spaces documentation on the Avaya Support website.
Title Use this document to: Audience Using Using Avaya Spaces Understand how to use Avaya Spaces
features on the mobile and desktop applications. This document provides detailed navigation and usage information, including information about:
• Using My Meeting Room, group spaces, and direct messaging spaces
• Working with meetings, recordings, chat, posts, and tasks
• Making one-on-one digital calls through Avaya Spaces
• Making audio calls through the Avaya Spaces Calling extension or Avaya Workplace Client
• Using meeting scheduling add-ons for Google Chrome and Microsoft Outlook
End users
Videos Avaya Spaces Videos Watch short videos on how to navigate
through Avaya Spaces, use Avaya Spaces features, and perform administration tasks.
End users and administrators
Articles Logging in to and out of Avaya Spaces
Access Avaya Spaces, create an account if you do not have one, and log in. This article also describes how to log out of Avaya Spaces.
End users
Table continues…
group spaces, and direct messaging spaces. This article also provides high-level information about making and managing a call.
End users
Working with the Avaya Spaces Dashboard
Use the Avaya Spaces Dashboard on the web interface and desktop application.
End users
Working with group spaces Set up and manage group spaces. End users Joining and managing an Avaya Spaces meeting
Manage meetings in Avaya Spaces. This article also describes the features that are available in an Avaya Spaces meeting.
End users
Access and work with meeting recordings in Avaya Spaces.
End users
Working with posts in Avaya Spaces Create and manage posts in Avaya Spaces.
End users
Create and work with tasks in Avaya Spaces.
End users
Working with chat in Avaya Spaces Work with chat messages in Avaya Spaces. This article also describes how to start a direct messaging chat conversation.
End users
Avaya Spaces license types Learn about Avaya Spaces licensing. This article includes a comparison of the features you can access with different license types.
All users, with a focus on end users
Using the Avaya Spaces scheduling add-ons for Google Chrome and Microsoft Outlook
Set up and use Avaya Agenda Chrome Extension and Avaya Meeting Scheduler for Microsoft Outlook. Use these add-ons to schedule meetings.
End users
1. Go to https://support.avaya.com.
2. At the top of the screen, type your username and password and click Login.
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the list.
Documentation
5. In Choose Release, select the appropriate release number.
The Choose Release field is not available if there is only one release for the product.
6. In the Content Type filter, click a document type, or click Select All to see a list of all available documents.
For example, for user guides, click User Guides in the Content Type filter. The list only displays the documents for the selected category.
7. Click Enter.
Avaya Documentation Center navigation For some programs, the latest customer documentation is now available on the Avaya Documentation Center website at https://documentation.avaya.com.
Important:
For documents that are not available on Avaya Documentation Center, click More Sites > Support on the top menu to open https://support.avaya.com.
Using the Avaya Documentation Center, you can:
• Search for keywords.
To filter by product, click Filters and select a product.
• Search for documents.
From Products & Solutions, select a solution category and product, and then select the appropriate document from the list.
• Sort documents on the search results page.
• Click Languages ( ) to change the display language and view localized documents.
• Publish a PDF of the current section in a document, the section and its subsections, or the entire document.
• Add content to your collection using My Docs ( ).
Navigate to the Manage Content > My Docs menu, and do any of the following:
- Create, rename, and delete a collection.
- Add topics from various documents to a collection.
- Save a PDF of the selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive collection that others have shared with you.
• Add yourself as a watcher using the Watch icon ( ).
Resources
- Enable Include in email notification to receive email alerts.
- Unwatch selected content, all content in a document, or all content on the Watch list page.
As a watcher, you are notified when content is updated or deleted from a document, or the document is removed from the website.
• Share a section on social media platforms, such as Facebook, LinkedIn, and Twitter.
• Send feedback on a section and rate the content.
Note:
Some functionality is only available when you log in to the website. The available functionality depends on your role.
Support Go to the Avaya Support website at https://support.avaya.com for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise.
Using the Avaya InSite Knowledge Base The Avaya InSite Knowledge Base is a web-based search engine that provides:
• Up-to-date troubleshooting procedures and technical tips
• Information about service packs
• Links to other pertinent information
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you can access the Knowledge Base without extra cost. You must have a login account and a valid Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
1. Go to http://www.avaya.com/support. 2. Log on to the Avaya website with a valid Avaya user ID and password.
The system displays the Avaya Support page. 3. Click Support by Product > Product-specific Support.
Support
4. In Enter Product Name, enter the product, and press Enter.
5. Select the product from the list, and select a release. 6. Click the Technical Solutions tab to see articles. 7. Select relevant articles.
Resources
browser content redirection
Browser Content Redirection (BCR) on a Citrix virtual desktop infrastructure provides optimized audio and video quality. When BCR is enabled, media travels between the Citrix client and the Avaya Spaces back-end cloud infrastructure, providing optimized transmission.
CDN A Content Delivery Network (CDN) is a geographically distributed network of proxy servers and their data centers. A CDN minimizes loading delays and increases content availability.
STUN Session Traversal Utilities for NAT (STUN) is a standard set of methods and transport protocol that allows a phone to discover its public IP address and ports.
whitelist An explicit list of permitted domains or addresses for your network.
Avaya Aura configuration ..............................................40 company profile ............................................................ 41 IP Office configuration .................................................. 40 programming command script ...................................... 42 script ............................................................................. 42
Avaya Spaces components ................................................... 9 Avaya support website .........................................................61
B Browser Content Redirection (BCR)
Citrix benefits ................................................................52 policies ..........................................................................52 recommendation ...........................................................51 verification .................................................................... 54
Citrix Studio policies ..........................................................................52
Avaya Spaces Calling extension .................................. 41 components ........................................................................... 9 configuration
Avaya Aura ................................................................... 40 Avaya Spaces Calling extension .................................. 40 Citrix ............................................................................. 50 initial company ........................................................12, 15 IP Office ........................................................................40 users .......................................................................12, 15
configuring Equinox Cloud Client .................................................... 48 message retention policy ..............................................26
configuring Avaya Spaces Calling extension company profile ............................................................ 41
content publishing PDF output .................................................. 60 searching ...................................................................... 60 sharing ..........................................................................60 sort by last updated ...................................................... 60 watching for updates .................................................... 60
D data encryption .................................................................... 10 data storage .........................................................................10 deallocating
domain adding ...........................................................................15 adding from Admin Area ...............................................25 deleting ......................................................................... 25
G global dialing rules ............................................................... 46
I importing
L legal notices
Citrix ............................................................................. 51 login options
pairing domains ............................................................ 38 restricting login options .................................................37
M managing
P pairing
examples ...................................................................... 42 paramaters ................................................................... 43
R related documentation ......................................................... 58 required hosts ...................................................................... 12 required protocols ................................................................ 12 restricting
login options ................................................................. 37 role-based access control ....................................................10
S script descriptions ................................................................ 43 script examples ....................................................................42 script parameters ................................................................. 43 searching for content .................

Date post:	16-Oct-2021
Category:	Documents
Author:	others
View:	0 times
Download:	0 times

Administering Avaya Spaces

Documents

Avaya on Avaya: Why Avaya UC/CC and Avaya Networking are Better Together

Administering Avaya Aura™ System Platform

Avaya Ethernet Routing Switch 3500 Series ...badgercommunications.com/pdf/avaya/avaya-ethernet...Avaya Ethernet Routing Switch 3500 Series The Avaya Ethernet Routing Switch (ERS) 3500

ADMINISTERING MEDICATION Presentation on ADMINISTERING MEDICATION.

Administering Avaya IP Office Platform with · PDF fileSupport. Support ™ Platform with Manager . Administering Avaya IP Office™ ™ Platform with Manager . Administering Avaya

Avaya Spaces Manual - 國立臺灣大學teach.cc.ntu.edu.tw/course/video conferencing/Avaya...Avaya Spaces User Manual Avaya Inc. 3 Avaya Spaces is not just any collaboration tool.

Administering Avaya Contact Center Select

Administering Network Connectivity on Avaya Aura ......Administering Network Connectivity on Avaya Aura™ Communication Manager 555-233-504 Issue 14 May 2009

Administering Avaya Communicator on IP Office · Avaya Communicator for IP Office is an application that works with the IP Office suite. Using this product, you can access enterprise

Administering Voicemail Pro - Avaya

Administering Avaya One-XMobilefor IPOfficeen-us

Administering Avaya one-X® Mobile for IP Office

Administering Avaya one-X® Communicator · PDF fileConfiguration Checklist ..... 16 Chapter 4: Integrations

Administering Avaya Aura® Call Center EliteAdministering Avaya Aura ® Call Center Elite Release 7.0.x Issue 1 May 2016

Avaya Session Manager · Installing and Administering Avaya Aura™ Session Manager 03-603324 Issue 1.1 Release 1.1 June 2009

ContactPro for Avaya Oceana, Avaya Elite & Skype for Business · ContactPro for Avaya Oceana, Avaya Elite & Skype for Business CCT ContactPro for Avaya Oceana, Avaya Elite & Skype

Administering Avaya Aura™ Communication Manager

Maintenance for the Avaya G250 and Avaya G350 …...Avaya Inc. Maintenance for the Avaya G250 and Avaya G350 Media Gateways, 03-300438.