customer administration: configuration & provisioning ...€¦ · introduction intended...

Customer Administration:

Configuration & Provisioning Guide Version 4.6

February 9, 2019

Thursday, February 7, 2019 All Rights Reserved © 2019 Page: i

Notices

Copyright © 2019 AVI-SPL, Inc. All Rights Reserved.

Following are policies pertaining to proprietary rights and trademarks.

Proprietary Rights

The information contained in this document is proprietary and confidential to AVI-SPL, Inc., one

or more of its affiliated entities (collectively “AVI-SPL”), or both.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval

system, or translated into any language, in any form or by any means, electronic, mechanical,

photocopying, recording, or otherwise, without prior written permission from AVI-SPL.

All copyright, confidential information, patents, design rights, and all other intellectual property

rights of whatsoever nature contained herein are and shall remain the sole and exclusive

property of AVI-SPL.

Trademarks

The AVI-SPL name and the AVI-SPL logo are trademarks or registered trademarks of AVI-SPL,

Inc.

All third-party product and service names are trademarks or registered trademarks of their

respective owners.

Disclaimer

The information furnished herein is believed to be accurate and reliable. However, no

responsibility is assumed by AVI-SPL for its use or for any infringements of patents or other

rights of third parties resulting from its use.

Table of Contents

Symphony Administrator 4.6

Configuration and Provisioning © 2019 AVI-SPL, Inc. All Rights Reserved Page: ii

TABLE OF CONTENTS

1 Introduction 1

1.1 INTENDED AUDIENCE ................................................................................... 1

1.2 HOW TO USE THIS DOCUMENT ..................................................................... 1

1.2.1 Easy PDF Hyperlink Navigation ........................................................................... 1

1.2.2 Easy Word Hyperlink Navigation .......................................................................... 1

1.3 REFERENCES .............................................................................................. 1

1.4 TERMINOLOGY ............................................................................................. 2

1.5 WHAT'S NEW ............................................................................................... 7

2 Overview 8

2.1 GUIDE HIGHLIGHTS ...................................................................................... 8

3 Onboarding - Symphony Administration 9

3.1 ABOUT CONFIGURATION & SCOPE LEVELS .................................................... 9

3.1.1 Levels and Inheritance (Quick Ref) .................................................................... 11

3.2 TASK OUTLINE - ONBOARDING YOUR ACCOUNT .......................................... 12

3.2.1 Account Configuration Tasks .............................................................................. 12

3.2.2 Customizing Account (Overriding Default Configuration) ................................... 13

3.2.3 Provisioning Roles and Account Users .............................................................. 14

4 Administration Function 15

4.1 ACCOUNT USERS ...................................................................................... 15

4.1.1 List Users ............................................................................................................ 15

4.1.2 Toolbar Options .................................................................................................. 16

4.1.3 Managing User Account Registration Options ................................................... 16

4.1.4 Add a User, Update, or Delete (User Profile) ..................................................... 18

4.1.5 Manage Users (Change Password / Resend Welcome Email) .......................... 24

4.1.6 Mass Import Users.............................................................................................. 25

4.2 ACCOUNT LOCATIONS ................................................................................ 26

4.2.1 Edit Location ....................................................................................................... 27

Table of Contents


Configuration and Provisioning © 2019 AVI-SPL, Inc. All Rights Reserved Page: iii

4.3 ACCOUNT ROOMS ..................................................................................... 29

4.3.1 Edit Room ........................................................................................................... 30

4.4 ACCOUNT DEVICES .................................................................................... 34

4.4.1 Edit Device .......................................................................................................... 35

4.5 ACCOUNT CONFIGURATION FUNCTIONS ...................................................... 42

4.5.1 Account Configuration Definitions ...................................................................... 43

4.5.2 Account Monitoring ............................................................................................. 44

4.5.3 Account Scheduling ............................................................................................ 55

4.5.4 Account Calendar ............................................................................................... 57

4.5.5 Account Customization (Portal Logos, Email Logo and VMR Theme) ............... 58

4.5.6 Account LDAP .................................................................................................... 59

4.5.7 Account Entitlements .......................................................................................... 61

4.5.8 Account Tickets .................................................................................................. 62

4.5.9 Account User Registration (Policy, Licensing and Role Defaults) ...................... 64

4.5.10 Account Recording ........................................................................................... 66

4.5.11 Account VMR .................................................................................................... 67

Introduction

Intended Audience


Configuration and Provisioning © 2019 AVI-SPL, Inc. All Rights Reserved Page: 1

1 INTRODUCTION

This guide describes the configuration tasks for provisioning and handling your account using Symphony a Service (SYaaS). The tasks include onboarding accounts, provisioning locations, rooms, devices, and users for an account.

For a Quick Start, see Task Outline - Onboarding your account section.

1.1 INTENDED AUDIENCE

The guide is intended for SYaaS Account Administrators with all possible role permissions for Home Account Only Visibility.

1.2 HOW TO USE THIS DOCUMENT

This document is designed for both online and hardcopy consumption.

Please note hyperlinks may appear on a page which when clicked, reroute you to another topic, document or reference source. If you are reading a printed copy of the document, the underscored words are hyperlinks and should not be interpreted as items of emphasis.

Conventions used in this document for emphasis are bold and italic.

1.2.1 Easy PDF Hyperlink Navigation

You can use hyperlinks to jump to a place in the document. To Go Back/Return from whence you came, use ALT + Left Arrow.

NOTE The left arrow cannot be on the number pad. Use the regular keyboard cursor key, left arrow.

1.2.2 Easy Word Hyperlink Navigation

You can use hyperlinks to jump to a place in the document. To Go Back/Return from whence

you came; add the back button to your Quick Bar.

Navigate to File > Options > Quick Access Toolbar. Choose All commands from drop-down,

scroll and select the Back button, press Add. Press Save. The back button is now available on your Quick Bar for all word docs.

1.3 REFERENCES

This section aggregates customer-facing resources available for Administration and provides information regarding the Symphony platform.

Introduction

Terminology



References

Topic / Title Description

Symphony - User

Guide

This document describes the processes and procedures for end-users of

the Symphony Web Portal. The guide explains features available from the

User point of view, (e.g., Scheduling a Symphony meeting and Virtual

Meeting Room [VMR] services).

Symphony - Customer

Admin User Guide

This guide describes how customer Administrators can manage and

moderate meetings, provision/manage users, manage/monitor devices, set

alerts, work tickets and create reports using the Symphony platform.

Symphony - Release

Notes

This document summarizes and details the enhancements and other

modifications to Symphony for a release/version. You can use this

document to view What’s New.

Symphony – Crestron-

AMX Configuration

and Monitoring

Guidance

This guide describes the processes for partner’s when setting up

Symphony AMX/Crestron Controllers for Symphony. These processes are

discussed in this guide:

• Loading the Symphony program on the controller

• Onboarding Crestron-AMX Controller and Associated Devices

• Verifying the Controller and Device Monitoring

• FAQ

1.4 TERMINOLOGY

This section provides the terms and acronyms utilized in this document.

Glossary of Terms

Term or Acronym Description

Account Administrator The Administrator performs a variety of tasks for your Symphony

company account based on the permissions specified for the

Administration roles. For example, the Account Admin can

add/delete/activate users, monitor locations, rooms and devices as

permitted.

Symphony as a Service (SYaaS) enables your company

Administrators to configure and provision Locations, Rooms, Devices

and Users for their account(s). In addition, Admins can optionally

configure monitoring thresholds and other items that when violated

cause ticket generation

Account Configuration In Symphony, Account configuration refers to the setup of Symphony

specifics for your account in conjunction with Symphony as a Service.

CMS Cisco Meeting Server (CMS) is utilized for Virtual Meeting Rooms

(VMR) in Symphony. Also, see TMS (Cisco and Symphony) definition

and process

Device Configuration In Symphony, Device Configuration is the bottom level for

configuration. See About Configuration Scope & Levels.

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20User%20Guide%204_6.docx?Web=1

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20User%20Guide%204_6.docx?Web=1

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20Customer%20Admin%20User%20Guide%204_6.docx?Web=1

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20Customer%20Admin%20User%20Guide%204_6.docx?Web=1

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20Release%20Notes%204_6.docx?Web=1

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20Release%20Notes%204_6.docx?Web=1

https://thehub.avispl.com/services/rtd/techdocs/Documents/Symphony%20-%20Crestron-AMX%20Configuration%20and%20Monitoring%20Guidance.docx?Web=1




Introduction

Terminology



Glossary of Terms


Endpoint A communication endpoint is a type of communication network node.

It is an interface exposed by a communicating party or by a

communication channel. An example of the latter type of a

communication endpoint is a publish-subscribe topic or a group in

group communication systems.

Exchange

(Microsoft Exchange Server)

Microsoft Exchange Server is a mail server and calendar server

developed by Microsoft. It runs exclusively on Windows Server

operating systems.

Global Configuration (GC) In Symphony, the Global Configuration is the top-tier or level for

configuration also called default configuration. Global Configuration

is performed exclusively by AVI-SPL Personnel.

See About Configuration Scope & Levels for an overall description of

Configuration Tiers/Levels and their inheritance.

GSOC GSOC refers to the AVI-SPL Global Services Operations Center.

When you have purchased Managed Services Powered by

Symphony, the AVI-SPL GSOC supports your account.

The GSOC provides comprehensive remote, proactive monitoring

and management of a customer’s video conferencing environment,

including infrastructure and endpoints, as well as any virtual services

LDAP LDAP stands for Lightweight Directory Access Protocol. As the name

suggests, it is a lightweight client-server protocol for accessing

directory services, specifically X.500-based directory services. LDAP

runs over TCP/IP or other connection-oriented transfer services.

Location A location contains the unique physical location street address,

building, and city/state or country and identifies where a project or

service takes place.

Location Configuration In Symphony, Location Configuration is the tertiary level for

configuration. See About Configuration & Scope Levels..

MCU Multipoint Control Unit

Monitoring Thresholds Symphony can generate tickets for device or other issues that violate

the monitoring thresholds configured for at the Account, Location, or

Device levels based on your configuration. When a threshold is

violated, Symphony determines whether to generate a ticket to alert

you of the situation.

Read About Configuration & Scope Levels to understand threshold

inheritance.

You can customize thresholds as desired, see Account Monitoring

section.

Introduction

Terminology



Glossary of Terms


Monitoring Restrictions Symphony allows you to:

• Restrict monitoring schedules to disable monitoring as

necessary (e.g., for maintenance, moving, etc.) based on

your entire account or a location, room, device AND

• ALSO, you can customize if and when to generate tickets

based on the monitoring threshold violation conditions.

Read About Configuration & Scope Levels to understand threshold

inheritance.

You can customize thresholds as desired, see Account Monitoring

section.

OID An object identifier (OID) has a central utility in providing a traceable

source for the meaning of an identifier appearing in a cross-

system communication. The primary use of identifiers, either UUID

or OID, is in computer networks.

SNMP: An OID in Simple Management Network Protocol (SNMP) is

an "Object Identifier". It's an address used to identify devices and

their statuses. For example: “Want to know the status of a device at

one of your account room locations?”

Producer Please refer to Symphony Producers.

RMX MCU For Symphony purposes, RMX MCU refers to Polycom Real-time

Media eXecutive.

Room A Symphony Room is a physical or virtual location within a Location.

Room Configuration In Symphony, Room Configuration is the fourth level for

configuration. See About Configuration Scope & Levels)..

SNMP Simple Network Management Protocol (SNMP) is an internet

standard protocol for collecting and organizing information about

managed devices on IP networks and for modifying that information

to change device behavior.

Symphony as a Service

(SYaaS)

Symphony as a Service (SYaaS) enables you to access the

Symphony cloud and benefit from the capabilities of the Symphony

platform. The Symphony platform allows you to monitor and support

your AV, video, and unified communications and collaboration

systems.

Symphony Bridging

Services

When a customer has purchased Symphony Bridging Services, you

can automatically connect to a bridge when a scheduled meeting

starts. Symphony offers these types of bridging services:

• Hosted MCU Bridging Service

• Hosted Audio added to Bridging Call Service

Introduction

Terminology



Glossary of Terms


Symphony Conferencing

Services

For Managed Services Powered by AVI-SPL, Symphony

Conferencing Services entitles customers direct assistance from

AVI-SPL for scheduling meetings, producing meetings, and a variety

of services included at no extra charge to customer.

A Symphony meeting or conference is scheduled using the

Symphony portal and/or loads to the bridge.

Symphony Account

Producer (SYaaS)

Your account Producer role can serve as the point of contact for both

scheduled and unscheduled conference calls. More specifically your

account producers can connect and monitor video meetings, conduct

conference sweeps and monitor endpoints.

AVI-SPL configures the role for your account and services which

typically has the Can produce meetings permission and/or and Can

assign producers to meetings permission.

Symphony Recording

Services

When a you have purchased Symphony Recording Services, you can

define a meeting with recording capability.

Symphony Services Symphony Services refers to the various types of purchased services

provided to customer accounts such as Symphony Conferencing

Services, Bridging Services and Recording Services.

Telnet Protocol Telnet is a protocol that allows you to connect to remote computers

(called hosts) over a TCP/IP network (such as the internet). Using

telnet client software on your computer, you can make a connection

to a telnet server (i.e., the remote host).

Tickets Symphony tickets can be created via a conference call, alert, or

manually. Ticketing has with customizable configuration options to

manage your Symphony app devices and experience.

In addition, you can purchase the Ticket Adapter Library (TAL)

component to provide Symphony ticket synchronization to customer

third-party support applications (e.g. ServiceNow, Salesforce).

Introduction

Terminology



Glossary of Terms


TMS (Cisco) and Symphony At AVI-SPL, the Symphony product uses TelePresence®

Management Suite (Cisco TMS) for older Cisco MCUs and is

designed/configured as follows:

• TMS Agent – service running on the Symphony CommProxy

• TMS Server - If account is using Symphony as a Service

(SYaaS) methodology, the TMS device is configured in

Symphony. All other accounts (not using SYaaS) use Salesforce

for provisioning of their TMS.

• Also, the TMS device must be marked as active, as Symphony

accesses the device and makes API calls to retrieve / save /

update / delete conferences.

The room associated with the device must be marked as In

Service, and Managed.

• CommProxy must be configured. AVI-SPL sets ups and

configures this server device to monitor the account.

• Rooms are profiled in Symphony with their resource TMS ID, and

the respective device must be marked as active, and the room

associated with the device must be marked as In Service, and

Managed.

TMS Sync and direction must be configured in Symphony for the

account. Administrators with the proper access can setup the sync

direction under:

Administration > Configuration > Calendar

How it works?

• Service wakes up every 30 secs

• Symphony (SY) to TMS: Obtain all the meetings from SY since

the last sync (time stamp), convert meetings to the TMS format

and send the data to TMS.

• TMS to SY: Obtain all the meetings from TMS since the last sync

(transactions), convert meetings to the Symphony format and add

meetings to Symphony.

Limitations

• TMS has a limit of 100 occurrences to a recurrent meeting.

VMR A Virtual Meeting Room (VMR) is a self-service, cloud-based video

conferencing service and meeting room that is always available and

always accessible for ad hoc or scheduled meetings. Symphony

VMR Services are provided using Cisco Meeting Server (CMS).

Introduction

What's New



1.5 WHAT'S NEW

This section describes the Symphony - Customer Administration User Guide enhancements for the current Symphony release. The features exposed depend on your company’s services and permissions. For a complete list of release features, see the Symphony - Release Notes

What's New

Release 4.6

1. Export List views to CSV (Comma Separated Value) file. From any List view toolbar, you can

use the CSV icon to export a CSV file to a spread sheet.

2. Room Service Contract Expiration date. Device Lease (Service) and Manufacturer’s

Warranty Expiration dates. Symphony can optionally track these items for expiration dates

and generate a ticket as desired. The ticket criticality can be adjusted as the expiration date

approaches. For example, if an expiration date is within 2 days, generate a critical ticket.

a. For Devices, track the expiration dates for Lease (Service) and Manufacturer Warranty

expiration.

b. For Rooms, track the expiration date for Service Contract expiration.

The expiration date thresholds for generating tickets can be configured at the Global

Configuration (Default), Account, Location, Room, and Device level.

3. New Meeting Features & Configuration:

a. When the auto-retry setting for endpoints setting is enabled for an account, Symphony

can automatically retry to connect to an endpoint (device) in busy status.

b. When the never terminate VIP meetings setting is enabled for an account, Symphony

will NOT automatically terminate a meeting designated as VIP meeting. The meeting

MUST be terminated by a Producer.

4. Account Ticket Adapter Configuration

Overview

Guide Highlights



2 OVERVIEW

Symphony is a meeting and conferencing solution for monitoring, managing, and analytics all within a single platform to connect and conduct your meetings for workstream harmony.

With Symphony, you can automate meeting scheduling, launch meetings, and utilize a myriad of meeting management and monitoring functions providing global control of your AV and Unified Communications ecosystem.

Symphony integrates with Microsoft Exchange, Cisco TMS (TelePresence® Management Suite) and Crestron/AMX Controllers. One platform, interoperable, with a consistent User experience (UX) for all.

For an overview of Symphony Business Process Automation Module and Symphony as a Service (SYaaS), please refer to the Symphony - Customer Administration User Guide, section Overview.

2.1 GUIDE HIGHLIGHTS

The items in this section focuses on your account onboarding tasks as provisioned by your Administrators. Administrators can provision and manage Users, Locations, Rooms and Devices. You can optionally customize monitoring thresholds and set monitoring restriction schedules as necessary for your account’s associated Locations, Rooms, and Devices.

NOTE You CAN purchase your account onboarding services from AVI-SPL.

➢ Read about Symphony Configuration Scope levels for an understanding of the

Location, Room, and Device inheritance concepts.

➢ Task Outline - Onboarding your Account section describes the steps for configuring and

provisioning your account.

▪ Account Configuration Functions section describes how to view, configure, and

manage your account.

▪ Customizing Account (Overriding Default Configuration)

▪ Provisioning Roles and Account Users describes all aspects of managing users

and provisioning.

This section describes the Symphony Administrator Role for maintaining your account.

➢ Administration Function

Onboarding - Symphony Administration

About Configuration & Scope Levels



3 ONBOARDING - SYMPHONY ADMINISTRATION

This section describes the tasks involved with onboarding configuration and provisioning for your account’s Locations, Rooms, Devices and Users in Symphony.

3.1 ABOUT CONFIGURATION & SCOPE LEVELS

The levels described in this section provide the scope of the account overall configuration (default configuration) to the most granular scope (device scope) for various items; Monitoring, Tickets, Recording, and other customizations.

You can define custom thresholds used to monitor devices for your account. In addition, you can also define monitoring restrictions. It is not necessary to configure options unless you want to change the default Account configuration.

Configuration item values are inherited from the Symphony Default Configuration to become the default for subsequent levels of configuration; (e.g., account, location, room, device). See the Account Monitoring section for a complete description of monitoring thresholds and restrictions. See next page for example and level descriptions.





For example, your account configuration is inherited from the Default Configuration, (set by AVI-SPL). You can customize device monitoring thresholds and restrictions based on your entire Account, or by Location, Room, Device.

Scope Configuration Level Definitions

Scope Level Name Definition

(Level 1)

Default Configuration

Thresholds and Restrictions

AVI-SPL ONLY. (Global Default level) is the top-level of

configuration scope options. Levels below the Global

Configuration such as Account Configuration, Location,

Room and Device Configuration can inherit from higher

levels when not specifically defined.

(Level 2)

Account Configuration

(inherits Default Config)


Account Configuration is the secondary level of

configuration scope options. When Account

Configurations are not specified, the default values are

inherited.

(Level 3)

Location Configuration

(inherits Account Config)


Location Configuration is the tertiary level of configuration

scope options. When Location Configurations are not

specified, the default values are inherited from the

previous scope level defined.

(Level 4)

Room

(inherits from Location Config)


Room Configuration is the fourth level. Room

Configuration inherits Monitoring Restrictions and

Expiration Date Thresholds only. When Room

Configurations are not specified, the default values are

inherited from the previous scope level defined.

(Level 5)

Device Configuration

(inherits Location Config

and/or Room Config)

Thresholds and

Restrictions

Device Configuration is the bottom-level of configuration

scope options. When Device Configurations are not

specified, the default values are inherited from the

previous scope level defined.





3.1.1 Levels and Inheritance (Quick Ref)

This chart is for quick reference once you have begun your provisioning and understand the configuration items such as monitoring thresholds and restrictions, see Account Monitoring for a complete description of topics.

The default configuration can be overridden as depicted in the tables below. The levels and inheritance level order are specified in the tables.

Monitoring Inheritance

Inheritance

Order

Video Endpoint

Thresholds

Infrastructure

Elements

Thresholds

AV Device

Thresholds (Generic)

Other Monitoring

Items

Level

General

e.g.

Comm,

packet

loss, etc

Advanced

Source

e.g.

SNMP

General

e.g.

Comm,

packet

loss,

etc.)

Advanced

Source

e.g.

SNMP

General

e.g.

Comm

Advanced

Source

e.g. Room

controller,

SNMP, etc

Monitoring

Restriction

&

Expiration

Dates

SNMP

OID

1. Default

Config.

(AVI-SPL) ✓ ✓ ✓ ✓ ✓ ✓ ✓

✓ Device

Model

2. Account

Inherits

Default

Config

✓ ✓ ✓ ✓ ✓ ✓ ✓

3. Location

Inherits Acc ✓ ✓ ✓ ✓ ✓ ✓ ✓

5. Room

Inherits

Loc

✓

5. Device Inherits

Loc

✓

Inherits

Loc

✓

Inherits

Room ✓

Inherits

Loc

✓ SNMP

Tab

All Other Global Config Inheritance

Inheritance Order & Tier (Level) Scheduling Tickets Roles Recording

1. Default Configuration (AVI-SPL)

✓ ✓ ✓ ✓

2. Account

Inherit Default Configuration ✓ ✓ ✓ ✓


Task Outline - Onboarding Your Account



3.2 TASK OUTLINE - ONBOARDING YOUR ACCOUNT

The task outline provides a checklist of items to be performed/considered when provisioning account data and users.

3.2.1 Account Configuration Tasks

Configure Account and Other Tasks

Task Reference Comment

Add Locations Account Locations OPTIONAL: You can add physical Location address,

country, time zone and other information. Your

account has locations unless your account has only

VMR services.

Add Rooms Account Rooms OPTIONAL: You can add physical rooms to locations

as desired unless your account is VMR only.

Add Devices Account Devices OPTIONAL: Your account has devices unless your

account is VMR only.

Configure Calendar

Synchronization

Account Calendar OPTIONAL: READ-ONLY Only necessary when your

account has Cisco TMS or Microsoft Exchange

integration enabled.

Configure Account

Customization

Account

Customization

OPTIONAL: You can update the Portal Logos and

Email Logo.

Configure LDAP

integration

Account LDAP OPTIONAL: Only necessary when account has LDAP

integration.

Account Entitlements Account

Entitlements

INFORMATIONAL ONLY: AVI-SPL configures the

account entitlements and services for Symphony as a

Service.

You can verify the number of Conferencing and/or

VMR licenses available and utilized via the

Entitlements display screen.

Registration &

Licensing (Users)

User Registration REQUIRED: You can enable users to self-register

when desired for your account. In addition, you can

define default roles and licensing for users.

Virtual Meeting Room

(VMR)

Account VMR OPTIONAL: Only necessary when account is using

VMR.





3.2.2 Customizing Account (Overriding Default Configuration)

You can customize the following items to meet your account needs. It is not necessary to change the default configuration unless desired.

Customizing Account Thresholds and Other Tasks


Customizing Account - Overriding the default Configuration for Account

Configure Monitoring Thresholds

• Video Endpoint Threshold

• Infrastructure Element Threshold

• AV Devices Threshold

• Computer Threshold

• Expiration Date Thresholds

• Monitoring Restrictions

Account

Monitoring

OPTIONAL: You can break the

inheritance as described in About

Configuration & Scope Levels.

Configure scheduling policies,

Email Notifications (Meeting

Invites)

Account

Scheduling

REQUIRED: You can verify the default

policies are accurate, update as

necessary. You can break the inheritance

as described in About Configuration &

Scope Levels

Check tickets policies Account Tickets REQUIRED: You can verify the default

ticket policies are accurate.

OPTIONAL: Update Ticket policies as

necessary for account custom policies.

Recording Account

Recording

OPTIONAL: When you have purchased

Symphony recording services, you can

define whether guests can view public

and/or unlisted meeting recordings.

Other Customized Configurations - Override Configurations

LOCATION: Override the inherited

configuration

Override Account

Location

Monitoring

(Thresholds)


inheritance chain to override the inherited

default values.

ROOM: Override the inherited

configuration

Override Account

Room Monitoring

(Thresholds) and

Restrictions



default values.

DEVICE: Overriding the inherited

configuration

Override Account

Device

(Thresholds,

SNMP,

Monitoring

Restrictions)



default values.





3.2.3 Provisioning Roles and Account Users

Create Account and Other Tasks


Configure Account User

Registration

(Policy, License, Default Role)

Account User Registration REQUIRED: Determine self-

registration, auto-license

assignment, default role for user

upon add/import.

Add Users to the Account

Create a User (Singular) Create a User (User Profile) OPTIONAL: This feature adds one

user at a time and their role.

Mass import users from a

CSV file

Mass import users OPTIONAL: Use a CSV or. txt (text)

file to mass import account user info

into a default role.

Create one or more account

administrators

(Roles)

Create a user

Assigning the proper role to

the user via User Capabilities

OPTIONAL: Only if the account is

required to have one or more

customer account administrators.

Reset the password of a

user

Manage User: Password

Reset and Welcome Email

OPTIONAL: You have an option to

change the password of a user.

When a user contacts you for

forgotten password, ask the user to

click the Forgot Password link on the

portal and to follow the instructions in

the email.

Resend the Welcome Email Manage User: Password

Reset and Welcome Email

OPTIONAL: You can resend the

welcome email to a user which

includes the link to the Symphony

portal, types of services, and

Symphony documentation links.

Administration Function

Account Users



4 ADMINISTRATION FUNCTION

The Administration function on the left navigation bar displays the options available to your account. Make sure you are familiar with the Symphony Administration Basics section in the Symphony - Customer Admin User Guide, (e.g., toolbar options, crumb trail navigation, search features and more).

Figure 1: Administration Function on left navigation bar

4.1 ACCOUNT USERS

You can onboard users using these methods.

➢ Add, Update or Delete individual Users

➢ Mass Import Users from a file

To manage user(s) for an account, see:

➢ Managing Account User Registration.

➢ Manage user roles via User Capabilities (Roles).

➢ Change User Password or Resend Welcome email.

4.1.1 List Users

1 Navigate to Administration > Users on the left navigation bar. Click on the Username to update user roles and capabilities.

Figure 2: User List


Account Users



4.1.2 Toolbar Options

These icons appear in the account Users toolbar based on your user permissions. Your ability to perform functions within an option can also be restricted.

User Configuration Toolbar Icon Definitions

Icon Definition

USER List Toolbar ONLY You can Mass Import user email addresses from a file. The

default role is derived from the Account User Registration.

To add row(s) to a list, press the plus sign. The plus sign is used for provisioning

Users, Locations, Rooms, Devices.

To delete row(s) from the list, check the box for the row(s) and press the minus sign

on the toolbar.

Refresh the screen display.

Export csv file. You can export data to a Comma Separated Value (CSV) File. The

exported data can be viewed, sorted, annotated and shared for easy collaboration via a

spreadsheet. These export options are supported:

• Display data (the readable format which displays on the List view screen),

• Raw data (the raw data returned from the Middleware, basically shows more

fields).

4.1.3 Managing User Account Registration Options

These methods are available when creating users and their corresponding registration:

Method Description

Self-Registration When self-registration for your account is active, users can register their own

user account.

Self-Activation As an Administrator, you can opt to start the process, add the email address of a

user and allow users to self-activate. The user receives an email with a link to

enter relevant information for completing their registration.

Manual

Registration

As an Administrator, you can choose to enter all the information for a user

(including a password) manually and reach out to the user who is out of band.

The graphic flow below summarizes the methods.


Account Users



4.1.3.1 Registration Work Flow

Figure 3: Symphony User Registration Workflow


Account Users



4.1.4 Add a User, Update, or Delete (User Profile)

You can manage user Information, Capabilities, Conferencing, and Personal VMR (if your account has VMR services). Select a user toolbar option on the User List screen to add or delete users. To edit a user, click the Username on the User list.

Figure 4: Add User


Account Users



NOTE The Conferencing tab is NOT relevant when account is VMR only.

The indicators and ways to register a user are described below.

Action/Field Description

This field contains the users email address and is the

username a user enters to sign in to Symphony.

The User is active checkbox indicates that the user can

login to the portal using the assigned password.

When self-registration for your account is active, users

can register their own user account. Checking the box

for a user to Self-activate indicates the user enters all

their own profile information into the portal upon

registration.

Admin manually registers

user

If you do NOT want the user to Self-activate, enter all the

remaining required information, (asterisk denotes

required fields).

4.1.4.1 User Capabilities (Roles)

The Capabilities tab of the User Profile screen allows you to set the role of the user. You must have permission to utilize the Capabilities function. The example shows the administrator role for SYaaS.

Figure 5: User Capabilities (Role) Tab

1 Select a user from the User list and navigate to the Capabilities tab to update a user role.

NOTE AVI-SPL configures the roles and associated permissions for an account.

2 Press Update button (bottom of screen).


Account Users



4.1.4.2 User Conferencing Tab

The Conferencing tab allows you to set conferencing services for which this user is entitled. If the account is also configured with Personal Audio Conferencing Service, you can add the user’s personal audio conferencing codes and PINs in this screen.

Figure 6: User Conferencing Tab

4.1.4.3 VMR Personal Tab

1 You can enable a Personal VMR for the user by adding information to the corresponding tab and checking the box. Please see VMR Field Definitions in the next section.

Figure 7: User VMR Personal Tab


Account Users



4.1.4.3.1 VMR Field Definitions

The fields for the VMR are described below.

Field Definition

Video Meeting

(VMR Number)

This field contains the address you and your meeting participants use to connect to

your VMR.

This address is like an email address, with a 10-digit number followed by the

domain of your VMR portal. This address is assigned to you and cannot be

changed.

Passcode This field contains a 5-digit number you and your guests enter when hosting a

meeting. There is no concept of Host PIN in Cisco CMS. Everyone joins as guests.

NOTE: If you start your meeting by logging on to the Symphony portal and opening

your VMR, it is not necessary to enter the Host PIN.

View Please refer to View Field Definition section.

4.1.4.3.2 Screen Layouts (View Field Definition)

For a VMR (My Room), you specify one View for the host and all participants.

1 You can use the drop-down arrow to change the default view for meetings in a user's VMR. The View field contains the options shown and the user can change the options on their Preferences > My VMR tab screen. See table below for examples of view screen layouts.

Figure 8: User Conferencing - View field options

The following table shows examples of the various view options. Please see screen layouts for SIP endpoints for a complete description of the layouts available.

https://kb.acano.com/content/33/273/en/what-are-the-screen-layouts-for-sip-endpoints.html#content

https://kb.acano.com/content/33/273/en/what-are-the-screen-layouts-for-sip-endpoints.html#content


Account Users



View Field Options

Screen Layout Option

One of the options below is selected automatically based on

the number of participants.

Automatic

Telepresence

Stack

Speaker Only

All Equal

All Equal Quarters


Account Users



View Field Options

Screen Layout Option

All Equal Ninths

All Equal Sixteenths

All Equal Twenty Fifths

One Plus Five

One large active speaker video with 9 smaller videos below One Plus Nine


Account Users



4.1.5 Manage Users (Change Password / Resend Welcome Email)

1 Navigate to Administration > Users and select a user from the User list.

2 From any tab, you can click the buttons on the bottom of the tab screen to:

➢ Change/Reset Password OR

➢ Resend Welcome Email to the user.

Figure 9: Change/Reset Password and Resend Welcome Email


Account Users



4.1.6 Mass Import Users

1 You can mass import users from a file by clicking on the cloud down-arrow icon on the toolbar of the User list.

If the self-registration option is enabled for your account, the User will self-activate option is automatically enabled for the users imported. All users receive an email containing instructions to set a password and enter their profile information.

The default role assigned to the users is configured by AVI-SPL, typically user has User View capabilities. You can assign the administrator role manually after the import using the User Capabilities tab.

Figure 10: Mass Import Users

2 FILE FORMAT: Use the File button browse and select a file containing the email addresses only for the users you wish to import, (one email address per line). The file can be designated as .csv (comma separated value) or .txt (text file).

3 Press Upload.


Account Locations



4.2 ACCOUNT LOCATIONS

This section describes Location provisioning and configuration. Be sure to understand monitoring threshold and restriction inheritance for Configuration & Scope Levels.

1 You can navigate to Administration > Locations (left navigation bar) to view the Location List.

Figure 11: Location List Screen (Edit, Configure, Provision)

2 You can click the Location Name drill down to view, edit, or configure the Location.

3 You can click the blue drill-down link columns to access Rooms and Devices for a location.

4 To add or delete locations, you can use the toolbar options.

5 You can use the ellipsis menu to navigate to the location’s Rooms, Devices, or to Configure monitoring thresholds.


Account Locations



4.2.1 Edit Location

1 Clicking on the Location Name from the Location List opens the Edit Location view.

Figure 12: Edit Location View

2 You can change the location image by clicking the Change link below the image.

3 Click the Configuration button to configure Monitoring for the location, (i.e. override the standard Location configuration (i.e., override monitoring inheritance).

4 Press Update.

4.2.1.1 Location Field Descriptions

Location Field Descriptions & Notes

Field Descriptions & Notes Valid and/or Sample

Values

Location Is Active OPTIONAL: This field indicates whether the

location displays for the Symphony Meeting

scheduler. This field also determines whether

Monitoring capabilities (thresholds) are actively

enforced for the location/rooms/devices. Keep

this indicator off while you are configuring

rooms/devices subordinate to this location to

prevent ticket generation.

Boolean: True/False


Account Locations



Location Field Descriptions & Notes

Field Descriptions & Notes Valid and/or Sample

Values

Reference IP address OPTIONAL: This field is for customer reference

and use only.

123.23.123.12

Geo Location OPTIONAL: This field allows Symphony to

position the location on the Map Views for

meetings and devices.

• If Geo Location value is set to

Automatic, Symphony automatically

retrieves coordinates from the location

address.

• If Geo Location value is set to Manual,

the longitude and latitude for the location

are specified by the user.

Manual or Automatic

For Manual: sample

Longitude: -82.460794

Latitude: 27.987439

4.2.1.2 Override Location Configuration (Thresholds & Restrictions)

You can override a location’s inherited default Monitoring Thresholds or Restrictions. To understand monitoring inheritance read About Configuration & Scope Levels.

1 From the Location list click the ellipsis menu and select Configuration

-OR- from the Edit Location view click the Configure button at the bottom of the screen.

The Monitoring Thresholds and Restrictions pane displays. See Account Monitoring Definitions for definitions of each monitoring category and to link to configuration examples.

2 To change any of the thresholds, click on the chain icon next to the threshold to

break the default inheritance chain associated with the Configuration & Scope

Levels. The broken chain enables you to edit an item. You can toggle the icon by clicking again to revert back to the inheritance chain value (solid chain).

3 You can use the crumb trail to easily navigate when Configuring items.


Account Rooms



4.3 ACCOUNT ROOMS

This section describes Room provisioning and configuration. Be sure to understand monitoring threshold and restriction inheritance for Configuration & Scope Levels.

1 You can navigate to Administration > Rooms (left navigation bar) to view the Room List.

Figure 13: Rooms List (Edit, Configure, Provision)

2 You can click the Room Name drill down to view, edit, or configure the room.

3 You can click the blue column drill-down links to access the Location or Devices.

4 To add or delete rooms, you can use the toolbar options.


Account Rooms



4.3.1 Edit Room

1 Clicking on the Room Name from the Room List opens the Edit Room view.

These tab functions are associated with the room as depicted below; Information, Monitoring Restrictions, Expiration Date Thresholds, and Comments.

Figure 14: Edit Room View


Account Rooms



1 You can change the image by clicking the Change link below the image.

2 Type in the Room fields.

3 Override room Monitoring Thresholds and Monitoring Restrictions (as desired).

4 Add room Comments (as desired).

5 Click Update.

4.3.1.1 Room Field Descriptions

Room Field Description & Notes

Field Descriptions & Notes Valid and/or Sample Values

Managed Room OPTIONAL: This field determines whether

your operations center is managing the room.

For TMS synchronization & monitoring

devices associated with the room, this

checkbox must be checked.

Boolean: True/False

In Service OPTIONAL: This field indicates whether

Monitoring capabilities (thresholds) are actively

enforced for the rooms/devices. Keep this

indicator off while you are configuring devices

subordinate to this room to prevent ticket

generation.

For TMS synchronization & monitoring

devices associated with the room, this

checkbox must be checked.

Boolean: True/False

Public Room OPTIONAL: This field is for customer use.

Symphony stores the data.

Boolean: True/False

Room Is VIP OPTIONAL: This field determines whether the

room is considered to have VIP Devices and

treatment.

See Symphony - Customer Admin User Guide,

section VIP Management for information

regarding VIP meetings and rooms.

Boolean: True/False

Room Type REQUIRED: This field defines the type of

room. Select a room type from the drop-down

menu.

Audio, AVI-SPL Hosting PoP,

Office, Cubicle, Huddle

Space, Data Closet,

Telepresence


Account Rooms



Room Field Description & Notes


Scheduling Option

Please refer to the

Symphony - User

Guide section,

Scheduling a Meeting,

sub-section

Conferencing Tab for

more information on

Symphony Meeting

scheduling.

REQUIRED: This field indicates whether the

room is used for Symphony:

• Video Conferencing (VC) Scheduling

means the room can be utilized for

Symphony Meeting Web Scheduling

via the Conferencing Tab, (Rooms).

• Room Only Scheduling the room is

available for Symphony Meeting Web

Scheduling but there are no devices

associated with the room that

Symphony launches/monitors/utilizes.

• None means the room not utilized by

Symphony Meeting Web Scheduler.

VC Scheduling

Room Only Scheduling

None

TMS ID OPTIONAL: When the Scheduling Option

equals value VC Scheduling and TMS is

utilized, add the TMS ID for the room.

10

Exchange ID OPTIONAL: When the Scheduling Option

equals value VC Scheduling and MS

Exchange is utilized, add the Exchange ID.

Format:

exchangeID@<Domain>.com

[email protected]

Initial Certification

Date

OPTIONAL: This date field contains the date

of the initial certification of devices/MCU for an

account as specified in AVI-SPL contract.

NOTE: You cannot alter this field.

-

Re Certification Date OPTIONAL: This date field contains the date

of re-certification of devices/MCU for an

account as specified in AVI-SPL contract.

NOTE: You cannot alter this field.

-

Service Contract

Expiration

OPTIONAL: This field contains the expiration

date for the service contract associated with

this room. This field is monitored using the

expiration date thresholds configuration. When

the threshold is violated a ticket can be

generated. If the field is empty, no monitoring

is performed.

Date Format or use Widget

MM/DD/YYYY

Room Camera URL OPTIONAL: This field can contain any

clickable hyperlink. Please see Room Camera

URL Field below.

www.mycaddrawings.com

4.3.1.1.1 Room Camera URL Field

The Room Camera URL field enables you to add a camera URL (e.g. IP camera) and other items such as CAD drawings or other device URLs associated with a room.

mailto:exchangeID@%3cDomain%3e.com


Account Rooms



1 If you added the Room Camera URL field to the Edit Room screen, you can view the room information. Click the Room Camera button to open a page for the device or other item associated with the room.

Figure 15: Room Details (Room Camera Button)

4.3.1.2 Override Room Configuration (Thresholds & Restrictions)

You can override a room’s inherited default Monitoring Thresholds (e.g., for room Expiration Date applies) or Restrictions. To understand monitoring inheritance read About Configuration & Scope Levels.

1 From the Edit Room select the Expiration Dates and/or Monitoring Restrictions tabs for configuration examples.






Account Devices



4.4 ACCOUNT DEVICES

This section describes Device provisioning and configuration. Be sure to understand monitoring threshold and restriction inheritance for Configuration & Scope Levels.

1 You can navigate to Administration > Device (left navigation bar) to view the Device List.

Figure 16: Device List (Edit, Configure, Provision)

1 You can click the Device Name drill down to view, edit, or configure the device.

2 You can click the blue column drill-down link to access device Rooms and Locations.

3 To add or delete devices, you can use the toolbar options.

4 You can use the ellipsis menu to navigate to the Device Monitoring view, or you can configure Device, Rooms and Locations.


Account Devices



4.4.1 Edit Device

1 Clicking on the Device Name from the Device List opens the Edit Device view.

These tabs are displayed; Information, Properties, General Thresholds, Advanced Thresholds, SNMP, Monitoring Restrictions, Expiration Date Thresholds, and Comments.

Figure 17: Edit Device


Account Devices



1 You can change the image by clicking the Change link below the image.

2 Type in the Device Fields for all tabs as required/desired.

3 Override device Monitoring Thresholds and Monitoring Restrictions (as desired).

4 Type in Comments (as desired).

5 Click Update.

4.4.1.1 Device Information Field Descriptions

Device Field Descriptions & Notes


Device Name REQUIRED: This field can be any name ideally the

naming intuitively indicates the device type, make, model,

and possibly owner.

Crestron PRO3

AMX Occupancy Sensor

Avaya XTE240

Cisco C90

CEO Office PC

Type REQUIRED: This field is the broader term for what the

device represents. Select from the predefined Types.

For Controller: AV Devices

For Devices: can be: Codecs, AV Device,

Infrastructure, Unknown

For Symphony supported Codecs,

• Profile as usual and do not associate with a Room

Controller.

• -OR- you can profile the Codecs under a Room

Controller like any other device.

See Symphony - Crestron-AMX Configuration and

Monitoring Guidance, section FAQ Configuring Codecs.

AV Devices

Codecs

Computer

Infrastructure

Unknown

Category REQUIRED: DEPENDENT ON: Type. The selection list

displayed for this field designates the category to further

specify the device. Select Generic when the A/V device

does not fit into the other selection categories.

Type is Codecs and category is Telepresence, then

Symphony supports an array of devices with best quality

audio and video.

AV Controller, Desktop,

Generic (e.g., TWS-750), Lights

MCU, Telepresence

Manufacturer REQUIRED: DEPENDENT ON: Type and Category. The

selection list displayed for this field designates the

manufacturer to further specify the device. Select Other

when the manufacturer is not listed.

Avaya, Crestron, Other (e.g.,

Tablet), Polycom, Sony

Model REQUIRED: DEPENDENT ON: Type, Category,

Manufacturer. The selection list displayed for this field

designates the model to further specify the device. Select

Generic or Unknown when the Manufacturer value is

Other.

PRO3, Scopia Desktop, Trio

8800, Unknown


Account Devices





Device Is

Active

OPTIONAL: This field indicates whether to enable and

actively enforce the device Monitoring capabilities

(thresholds).

Keep this indicator off while you are configuring device to

prevent ticket generation.

Boolean: True/False

Device is

V.I.P.

OPTIONAL: This field designates whether to enable VIP

capabilities for the device determining how the device is

treated, see Symphony - Customer Admin User Guide,

section VIP Management for details.

Boolean: True/False

Room REQUIRED: This field contains the name of the room

where the device resides.

The drop-down list contains all

rooms for an account.

Service Type REQUIRED: This field determines whether a device is

Monitored by Symphony and/or Managed by Symphony,

or neither (e.g. None).

Please see Symphony - Customer Admin User Guide,

section Device Information Tab for details regarding

Managed vs. Monitoring Only devices.

Monitor & Manage

Monitoring Only

None

Monitoring

Source

REQUIRED: This column contains the information

associated with how the location is monitored.

For Controller: CommProxy

NOTE: Use CommProxy when configuring a

separate Codecs entity, see Symphony -

Crestron-AMX Configuration and Monitoring

Guidance, section FAQ Configuring Codecs.

For all other Devices: Room Controller.

CommProxy

Room Controller

Third-party ID OPTIONAL: The Third Party IDs are the Device IDs

found in the retrieved .json files from the controller. See

Symphony - Crestron-AMX Configuration and Monitoring

Guidance, section Crestron .json or AMX .json for sample

format of this field.

Format (alphanumeric)

Example:

XXXXXXXX-XXXX-XXXX-

XXXX-XXXXXXXXXXXX

Customer

Cost Center ID

OPTIONAL: This field is provided for your account’s use.

Symphony simply stores the field.

Customer defined

Lease

Expiration

OPTIONAL: This field contains the expiration date of the

lease/service for the device. This field is monitored by the

expiration date thresholds configuration. When the

threshold is violated a ticket can be generated. If the field

is empty, no monitoring is performed.

Format: MM/DD/YYYY

Manufacturer

Warranty

Expiration

OPTIONAL: This field contains the expiration date of the

manufacturer’s device warranty for the device. This field is

monitored by the expiration date thresholds configuration.

When the threshold is violated a ticket can be generated.

If the field is empty, no monitoring is performed.

Format: MM/DD/YYYY


Account Devices





Management

IP

REQUIRED: This field contains the IP address of the

device.

123.12.123.123

Management Interfaces

IMPORTANT NOTE: These fields pertain to devices that have a Service Type of Managed and/or

Monitored.

Protocols REQUIRED: At least one of the checkboxes must be

checked when Service Type equal to value Manage &

Monitor. These protocols are utilized for communicating

from the device to Symphony and vice-versa.

For Crestron/AMX Controllers: Check the HTTP box.

HTTP, SSH, TELNET

Secure REQUIRED: The SSH (Secure Shell) protocol box is

always checked by default. This field indicates whether

credentials are necessary for utilizing the protocol/device.

For example, when HTTP protocol:

• For HTTP do NOT check the box

• For HTTPS check the box

For Crestron/AMX Controllers: Box must be unchecked.

Boolean: True/False

Username &

Password

OPTIONAL: These fields contain any valid User ID and

Password credentials as necessary for managing the

device.

For Crestron/AMX Controllers: Use any valid credentials

N/A

Local Port OPTIONAL: This field contains the device Local port

number when necessary for the device.

For Crestron/AMX Controllers: Value MUST be 8080.

22

8080

Remote Port OPTIONAL: This field contains the Remote port number

when necessary for the device.

For Crestron/AMX Controllers: Leave Blank

8080

4.4.1.2 Device Properties Tab

The Properties tab displays the specific properties of the device.


Account Devices



Figure 18: Device Properties Tab


Account Devices



4.4.1.2.1 Device Properties Descriptions



Management IP REQUIRED: This field contains the IP address

of the device.

123.45.678.999

Protocol REQUIRED: This field the Voice over Internet

Protocol (VoIP), if any, for the device.

Dual H.323 & SIP, H323 Only,

SIP Only, ISDN, None

Software Version OPTIONAL: This field contains the software

version for the device.

Release - 6.1.3-390050

Serial Number OPTIONAL: This field contains the device

serial number.

82144443143ABC

Mac Address OPTIONAL: This field contains the MAC

address of the device.

00:D0:AC:41:12:3D

E.164 OPTIONAL: DEPENDENT ON Protocol

• If the protocol includes H.323, this

field is REQUIRED and contains the

E.164 alias of the device.

• If the protocol is ISDN, this field

contains the phone number.

H323 protocol:

7771231234

ISDN protocol:

Gatekeeper IP OPTIONAL: DEPENDENT ON Protocol

If protocol includes H.323, this field should

contain IP address of the gatekeeper with

which the device is registered.

123.45.678.88

Position OPTIONAL: DEPENDENT ON

Category=TELEPRESENCE.

This field only applicable to telepresence

devices and contains position on the device in

telepresence suite.

5

Audio Bridge Dial Out

Supported

OPTIONAL: DEPENDENT ON Category=

MCU.

This field applies only to MCU devices and

indicates whether MCU has audio (PSTN) dial

out capabilities.

Boolean: True/False

Bandwidth OPTIONAL: This field applies only to video

conferencing devices (Codecs) and contains

default bandwidth utilized when dialing device

in a call. Value is typically in Kbps (kilobits per

second).

1090, 3072, 4096

ISDN Dial Out

Supported

OPTIONAL: DEPENDENT ON Category=

MCU This field applies to MCU devices and

indicates whether MCU has ISDN dial out

capabilities.

Boolean: True/False


Account Devices





SNMP Community OPTIONAL: This field contains the SNMP

community string. If specified, Symphony

monitors SNMP OIDs configured for this

device model.

Public, Blank, 8-10CharRand

Total Ports OPTIONAL: DEPENDENT ON Category=

MCU. This field applies to MCU devices and

contains total number of MCU ports available.

50

H323.ID OPTIONAL: DEPENDENT ON Protocol

If protocol includes H.323, this field may

contain the H.323 ID alias of the device.

[email protected]

Direct Dial In Prefix OPTIONAL: DEPENDENT ON Category=

MCU. This field is reserved for future use.

N/A

SIP Dial In Prefix OPTIONAL: DEPENDENT ON Category=

MCU This field applies to MCU devices and

contains the prefix to be used when dialing

devices with SIP Protocol.

[email protected]

H323 Dial In Prefix OPTIONAL: DEPENDENT ON Category

=MCU. This field applies to MCU devices and

contains the prefix to be used when dialing

devices with H.323 Protocol. The field is

based on the routing rules configured on

customer network.

123

12345

1

SIP URI OPTIONAL: DEPENDENT ON Protocol

If protocol includes SIP, this field is

REQUIRED and contains SIP address of the

device.

[email protected]

SIP Registrar OPTIONAL: DEPENDENT ON Protocol

If protocol includes SIP, this field contains IP

address of the gatekeeper with which the

device is registered.

172.31.123.12

4.4.1.3 Device SNMP Tab

The values on this screen are entered by AVI-SPL for SNMP monitored devices.

4.4.1.4 Override Device Configuration (Thresholds & Monitoring Restrictions)

You can override a device’s inherited default Monitoring Thresholds or Restrictions. To understand monitoring inheritance read About Configuration & Scope Levels.

1 From the Device List, click the Device name link to Edit Device. See Account Monitoring for definitions of each monitoring category and to link to configuration examples.


Account Configuration Functions







4.5 ACCOUNT CONFIGURATION FUNCTIONS

After onboarding Locations, Rooms and Devices you can proceed to configuration as necessary, see the Task Outline - Onboarding Your Account for guidance on items to onboard and suggested order of tasks. It is not necessary to configure options unless you want to change the default configuration.

1 Navigate to Administration > Configuration on the left navigation bar to view account configuration options available.

Figure 19: Account Configuration Options

From this screen, you can configure all account functions listed on the screen. Account default settings can be overridden for the account. The list of options varies based on the services for your account.





CRUMB TRAIL TIP

You can use the crumb trail to quickly navigate to other screens on the crumb trail.

For example, the crumb trail (under the screen title),

By clicking Central Office navigates from the Device information to the Room information.

4.5.1 Account Configuration Definitions

Account Configuration Functions Defined

Activity Description

Monitoring (Default Monitoring

Thresholds and Restrictions)

This feature sets monitoring across the account. When a threshold

is exceeded, a ticket is generated to alert you of the situation.

You can override the default Monitoring Thresholds for account,

locations, rooms, and devices.

Scheduling You can adjust the meeting setup time for the account and change

any of the meeting notification email policies.

Calendar This function enables you to describe the active calendar

synchronization. There are these types of calendar

synchronization:

• Microsoft Exchange Server (Outlook)

• Cisco Telepresence Management Suite (TMS)

Customization This function allows you to customize images for the account

portal logo (large image and small icon image), email logo and

VMR theme.

LDAP This function allows you to setup LDAP integration for an account.

Entitlements The function shows all Symphony related licenses (used/available)

and entitlements for the account. This information is NOT

configurable. These entries are performed exclusively by AVI-

SPL.

Tickets The Ticket function allows you to set custom ticket handling

capabilities for this account.

Registration and Licenses This function allows you to set the policy for user registration,

license assignment and default role assigned to new users.

Recording Optional Service. This function contains the recording and event

(live streaming) abilities for an account if the account has this

service.

VMR Services Optional Service. This function is available for VMR phone

numbers. The phone dial-in information for a VMR meeting

invitation is set in this function.





4.5.2 Account Monitoring

This section allows you to define custom thresholds used to monitor devices for your account. In addition, you can also define monitoring restrictions. It is not necessary to configure options unless you want to change the default configuration. See About Configuration & Scope Levels to understand monitoring levels thresholds, restrictions and inheritance.

Although this section specifically shows examples at the account configuration level, the same concepts apply for overriding the monitoring thresholds at the location, room, and device, scope level. Account monitoring restrictions can be overridden at the Location, Room, and Device scope level.

➢ Monitoring Thresholds: Symphony can generate tickets for device or other issues that

violate the monitoring thresholds configured for at the Account, Location, or Device

levels based on your configuration. When a threshold is violated, Symphony

determines whether to generate a ticket to alert you of the situation.

➢ Monitoring Restrictions: Symphony allows you to:

▪ Restrict monitoring schedules to disable monitoring as necessary (e.g., for

maintenance, moving, etc.) based on your entire account or by location, room,

device.

▪ ALSO, you can customize if and when to generate tickets based on the monitoring

threshold violation conditions.

4.5.2.1 Set Monitoring Configurations

1 From the Account Configuration Options, click Monitoring to choose the type of monitoring for which you want to configure thresholds.

Figure 20: Account Monitoring Thresholds and Restrictions

NOTE Device monitoring information available to Symphony depends on what the device can offer.

WARNING: Be extra careful and precise when setting thresholds to avoid unexpected situations like not receiving tickets for important issues or ticket flooding.





4.5.2.1.1 Account Monitoring Definitions

The table below describes the configurable monitoring options. When a threshold is violated, a ticket is generated to alert you of the situation.

1 Click the Activity link column in the table to navigate to examples for these configurations.

Account Configuration: Monitoring Threshold Categories


Video Endpoint

Thresholds

This category contains the following thresholds for monitoring your video

endpoints.

• General Tab thresholds support communication with device, ping

latency, packet loss, audio and video jitter, video speed, and video

resolution.

• Advanced Tab thresholds provide detailed monitoring for Video

Endpoints and SNMP if supported by device. (SNMP has substantially

more information than the other monitoring methods.)

Infrastructure

Elements

Thresholds

This category contains the following thresholds for monitoring your infrastructure

elements.

These thresholds are utilized when you provision a new device. Under

Infrastructure, you can have Edge, Gateway, Generic, Gatekeeper/SIP registrar,

Management, MCU and Recording.

• General Tab thresholds are Communication w/Device, Ping Latency,

and Monitor MCU port Usage.

• Advanced Tab thresholds provide detailed monitoring for infrastructure

elements and SNMP. (SNMP has substantially more information than

the other monitoring methods.)

AV Devices

Threshold

This category contains the following thresholds for monitoring your audio and

video devices.

• General Tab threshold supports communication with devices.

• Advanced Tab thresholds provide detailed monitoring for A/V devices

(e.g., room controller) elements and SNMP. (SNMP has substantially

more information than the other monitoring methods.)

Computer

Thresholds

This category contains the following thresholds for monitoring your computers.

• General Tab threshold supports communication with devices, CPU

usage, memory usage, bandwidth (in and out).

• Advanced Tab thresholds provide detailed monitoring for computers

and SNMP. (SNMP has substantially more information than the other

monitoring methods.)

Expiration Date

Thresholds

This option allows you to set the date for generating tickets and setting ticket

criticality (Ticket Priority) as the expiration date approaches. Currently, the

expiration dates using this threshold are:

• Devices, track the expiration dates for Lease (Service) Expiration and

Manufacturer Warranty Expiration.

• Rooms, track the expiration date for Service Contract Expiration.





Account Configuration: Monitoring Threshold Categories


Monitoring

Restrictions

This option allows you to stop monitoring during scheduled periods, (e.g.,

maintenance, moving). You can also decide whether to generate monitoring

threshold violation issues (tickets) or Pause monitoring indefinitely.

4.5.2.2 Account Video Endpoint Thresholds

For a definition of this monitoring category, please refer to Monitoring Video Endpoints definition.

4.5.2.2.1 General Tab (Account)

The General tab allows you to configure a variety of thresholds for monitoring devices. For example, when monitoring a video endpoint, you can customize configurable thresholds such as; communication with device, ping latency, packet loss, audio and video jitter, video speed, and video resolution.

Figure 21: Video Endpoints Threshold - General Tab

For example, you can set a monitoring threshold of critical for a video endpoint with monitoring ping latency values (e.g. 400 millisecond) and their associated ticket priority (e.g., critical [P1], major [P2], minor[P3]).





WARNING Be extra careful and precise when setting thresholds to avoid unexpected situations like not receiving tickets for important issues or ticket flooding.

You can customize the fields as required for monitoring sensitivity.




2 Press Update.

4.5.2.2.2 Advanced Tab (SNMP & Other Source Monitoring)

You can customize the fields as required for monitoring and ticket priorities of endpoints.

Figure 22: Monitoring Video Endpoints - Advanced Tab

1 Use the Advanced tab toolbar to add or delete SNMP Monitoring thresholds.




3 Press Update.

4.5.2.2.2.1 Edit Label Ticketing Details

1 If you have permission, you can click the label link to display editable fields.





Figure 23: Advanced Tab - Ticketing Details

2 The fields break down as follows.

When a hardware issue arises for SNMP source, generate a major ticket for this account.

➢ New Event When identifies a set of numbers separated by dots to generate a

ticket/event based on conditions. For example, 123.34.34.34.23.3.4.44

represents the battery level of a remote. When the condition (less than as

operator) meets the percentage field (e.g. 10) then battery level is low and

generates a ticket (event).

➢ Cleared Event When identifies a set of numbers separated by dots to clear a

ticket/event based on conditions. For example, 123.34.34.34.23.3.4.44

represents the battery level of a remote and the battery level is (more than 90

percent), clear event as (likely someone replaced the battery).





4.5.2.3 Account Infrastructure Elements Thresholds

For a definition of this monitoring category, please refer to Infrastructure Elements Thresholds Definition. The images below show the monitoring information for this category.

For an explanation of the General and Advanced tabs work, see Video Endpoints Thresholds. The tabs work in the same manner for this monitoring category.

Figure 24: Infrastructure Elements Thresholds - General Tab





Figure 25: Infrastructure Elements Thresholds - Advanced Tab

4.5.2.4 Account A/V Device Thresholds

For a definition of this monitoring category, please refer to A/V Devices Thresholds Definition. The images below show the monitoring information for this category.

The General tab for A/V Devices has monitoring available for configuring Generic devices. Generic configuration is for devices that do not have a video endpoint such as projector, monitors, (could be anything).

For an explanation of how the General and Advanced tabs work, see Video Endpoints Thresholds. The tabs work in the same manner for this monitoring category.

Figure 26: A/V Device Thresholds - General Tab





The Advanced tab has monitoring available for other devices that contain a specific source which provides more detailed monitoring data.

Figure 27: A/V Device Thresholds - Advanced Tab

4.5.2.5 Account Computer Thresholds

For a definition of this monitoring category, please refer to the computer thresholds definition. The images below show the monitoring information for this category.

For an explanation of how the General and Advanced tabs work, see Video Endpoints Thresholds. The tabs work in the same manner for this category.

Figure 28: Computer Thresholds - General Tab





Figure 29: Computer Thresholds - Advanced Tab





4.5.2.6 Account Expiration Date Thresholds

For a definition of this monitoring category, please refer to the expiration date thresholds definitions. Monitoring thresholds can be overridden at the Account, Location, Room, and Device level.

NOTE If the device Lease Expiration Date, or device Manufacturer Warranty Expiration Date, or room Service Contract Expiration Date actual dates are NOT configured, no tickets are generated.

Figure 30: Account - Expiration Date Thresholds

1 To generate tickets based on the approaching expiration date, set the days to expiration threshold for generating tickets. You can generate tickets based on criticality (Critical, Major, Minor) related to the approaching expiration date.

Blank out fields (empty) if you do NOT wish to generate a ticket.








3 Press Update.

4.5.2.7 Account Monitoring Restrictions

For a definition of this monitoring category, please refer to the monitoring restrictions definition. Monitoring restrictions can be overridden at the Account, Location, Room, and Device level, see Account Monitoring for more.

Figure 31: Monitoring Restrictions Configuration




2 Press Update.





4.5.3 Account Scheduling

From this screen you can customize the meeting setup time for the account. You can change any of the meeting notification email policies.

In addition, you can set these feature options for meetings:

➢ Never automatically terminate VIP meetings and/or

➢ Any meeting to automatically retry busy endpoints.

Figure 32: Account Scheduling Configuration




2 Press Update.

4.5.3.1 Never Auto terminate VIP Meetings

The feature to NEVER auto-terminate V.I.P. meetings is configurable by account and





determined by the meeting type is VIP meeting. You must use the VIP Meeting checkbox on the Producer tab when scheduling a meeting to utilize this feature.

When the feature to never auto-terminate V.I.P. meetings is enabled and a meeting is designated as V.I.P. Meeting when scheduled (Producer Tab), devices stay connected no matter when the meeting ends. Producer’s MUST MANUALLY terminate the meeting. For instance,

➢ If the meeting end time does not exceed the scheduled end time the meeting STILL

REQUIRES manual termination by a producer using the meeting moderation button

(terminate).

➢ If another (subsequent) meeting tries to auto-connect to an endpoint which is still in

use by the V.I.P. meeting, the subsequent meeting endpoint receives an invite to the

original V.I.P. meeting and can accept or decline the invitation.

Supported MCUs. All supported MCUs act in the same manner described below.

➢ RMX (Polycom)

NOTE For RMX only, the property setting in the RMX MCU profile for auto-terminate must equal FALSE. This setting ensures RMX will NOT auto-terminate the meeting and this feature works as described.

➢ Cisco Meeting Server (CMS)

➢ Pexip

The global default configuration for this feature is FALSE (off) which means V.I.P. meetings/devices ARE automatically terminated upon meeting completion.

To enable the never auto-terminate V.I.P. meetings feature for an account, navigate to Administration > Configuration > Scheduling:

Figure 33: Account Configuration (break inheritance; enable Never Auto-terminate V.I.P. feature)

4.5.3.2 Auto-Retry Busy Endpoints

Based on your account configuration, Symphony automatically retries to connect to busy endpoints scheduled for a meeting. The number or retries for connection and the duration between retries is configured by account.

Auto-retries to busy endpoints can be performed when the meeting launches. Once the meeting launches, any participants (endpoints) invited at meeting time also have the auto-retry capability.





NOTE When selecting (adding) rooms in the web scheduler (Conferencing Tab), select a room and ensure the Automatically connect devices to the meeting check box is checked.

Supported MCUs are:

➢ RMX (Polycom)

➢ Cisco Meeting Server (CMS)

➢ Pexip

NOTE For CMS, the participant is re-added to the meeting after endpoint disconnect. RMX disconnected participants are simply shown as disconnected before the retry.

These auto-retry settings are configured for an account by navigating to Administration > Configuration > Scheduling:

➢ auto-retry busy endpoint (default is FALSE disabled, meaning no auto-try of busy endpoint). If auto-retry busy endpoint is enabled (TRUE), you can set:

▪ auto-retry number of times to attempt retry busy connection.

▪ auto-retry interval minutes until next retry busy connection attempt.

Figure 34: Account Configuration (Auto-retry Busy Endpoints)

4.5.4 Account Calendar

This screen describes the active calendar synchronization, (screens are configured by AVI-SPL and are read only). There are these types of calendar synchronization:

➢ Microsoft Exchange Server (Outlook)

➢ Cisco Telepresence Management Suite (TMS)

For TMS synchronization, select the direction of the sync when the account is entitled to TMS sync service). For more information, read about TMS.





Figure 35: Account Calendar Configuration - TMS Example

4.5.5 Account Customization (Portal Logos, Email Logo and VMR Theme)

You can customize images for the account portal logo (large image and small icon image), email logo and VMR theme.

1 To customize, click the Change link below the desired image category and upload an image.

NOTE The VMR theme must be a zip file.

Figure 36: Custom Logo Configuration





4.5.6 Account LDAP

This screen allows you to setup the LDAP integration for a customer. When LDAP integration is enabled, users can login to the portal using their LDAP (single sign-on SSO) credentials.

Figure 37: Account LDAP Configuration





4.5.6.1 LDAP Field Descriptions

The table describes each field on the LDAP Configuration screen. Coordinate with AVI-SPL for LDAP configuration.

LDAP Configuration Fields Defined

Field Description

Enable LDAP Integration Check this box to enable LDAP server integration with Symphony

for this account.

Secure LDAP Check this box to enable LDAP server. LDAP servers can be on

customer’s premises which can be accessible from Symphony

cloud.

Use CommProxy When LDAP server is deployed on customer premises this

checkbox must be to be checked.

LDAP Enabled

Server Hostname Enter the IP address of the LDAP server.

Server Port Enter the port number of the LDAP server

User DN This field contains the Distinguished Name (DN) for connecting to

LDAP. See definitions https://msdn.microsoft.com/en-

us/library/aa366101(v=vs.85).aspx

Example: CN=XXXXVMR,OU=Service

Accounts,OU=Org,DC=YYYY,DC=LOCAL

User Password This field contains the user password for connecting to LDAP.

Search Bases This field contains LDAP/Active Directory parameters that

represent:

CN = Common Name

OU = Organizational Unit

DC = Domain Component

Example: OU=Org,DC=XXXXXX,DC=LOCAL.

https://msdn.microsoft.com/en-us/library/aa366101(v=vs.85).aspx

https://msdn.microsoft.com/en-us/library/aa366101(v=vs.85).aspx





4.5.7 Account Entitlements

This function shows Symphony related licenses and entitlements (SKUs, etc.) for an account. The information displayed for the account is provisioned by AVI-SPL personnel and fields are read-only.

Licenses Count: Primarily, you are concerned with licenses and number count, (e.g., Premier conferencing 31 / 50000).

➢ Licenses in use for your account (first number, e.g. 6 licenses used).

➢ Licenses allotted for your account (second number, e.g. out of 50000 allotted

licenses).

Entitlements: Shows the services to which the account is entitled, expired Entitlements are displayed in red.

Figure 38: Entitlements (Licensing) License Counts (used/allotted)

Figure 39: Entitlements (Shows your accounts bridging and other services)

1 You can use the filter icon to show or hide the ISDN SKUs on the display, (default is hide).





4.5.8 Account Tickets

The Ticket function allows you to set custom ticket handling capabilities for this account.

4.5.8.1 Ticket Adapter Configuration (TAL)

To synchronize a third-party account ticketing solution, you must have the Ticket Adapter enabled, contact AVI-SPL to enable a ticketing solution, (e.g., ServiceNow, Salesforce). You can select the ticketing system from the drop-down list, (e.g. Customer Ticketing Solution).

Figure 40: Ticket Adapter (disabled)





4.5.8.2 Tickets (Closing Policies)

The ticket closing policy field values are inherited from the default configuration. Items displayed can be updated by clicking on the chain icon to break the inheritance and set an account value.

You can set monitoring restrictions to stop ticket generation for location(s), room(s), device(s) as necessary (e.g., maintenance, move etc.).

For a complete explanation of ticketing and their workflow, status, etc., please refer to the Symphony - Customer Admin User Guide, section About Tickets.

Figure 41: Account Ticketing Closing Policies

The check box options are:

➢ Automatically set Open tickets to Pending Close when issue is resolved.

➢ Automatically set Pending Close to Close.

➢ Automatically Close aging tickets.






break the default inheritance chain. The broken chain enables you to edit an item. You can toggle the icon by clicking again to revert back to the inheritance chain value (solid chain).

2 Press Update.

4.5.9 Account User Registration (Policy, Licensing and Role Defaults)

This function allows you to set the policy for user registration, license assignment, and default role assigned to new users. The account’s policies in this section are the basis for providing account default roles and other User configuration.

Figure 42: Registration & Licenses Configuration

1 In the General section, you can specify whether users for this account are allowed to self-register from the Symphony user portal (see Register Account link below the Sign-in to your account box. To enable self-registration, check the box (under General).

Figure 43: Symphony Portal Sign In





2 You can additionally allow users with an email address matching a particular domain to register, (e.g., acme.com, gmail.com, etc.). The delimiter for multiple domains is a comma.

3 License Assignment enables the account user roles to possess conferencing and/or VMR services. Conferencing license options are:

▪ Premier Conferencing (default) - Allows the user to login to user portal and

schedule meetings. For Managed Services Powered by Symphony, Users can call

the AVI-SPL GSOC to schedule meetings, change schedules, etc. Meetings which

engage a GSOC producer and/or meeting attendance are charged regardless of

service type.

NOTE Standard Conferencing is obsolete.

▪ None - No Symphony conferencing service (account can have VMR access

without conferencing setup).

4 Default role for new users is set using the drop-down selection list. When you Add a user, this default role is utilized unless specifically changed for the user.





4.5.10 Account Recording

This function contains the recording and event (live streaming) abilities for an account. The guest privileges for viewing are inherited from the default configuration settings for Recording.

Figure 44: Recording Configuration


break the default inheritance chain. The broken chain enables you to edit an item. You can toggle the icon by clicking again to revert back to the inheritance chain value (solid chain).

2 See Enable Recording Field Descriptions section and configure accordingly.

3 Press Update.

4.5.10.1 Enable Recording Field Descriptions

The table describes each field on the Enable Recording section of the screen. Recording is provided via the rec.vc service.

Enable Recording Configuration Fields Defined

Field Description

Username This field contains the User Name for cloud Rec.vc. service login.





Enable Recording Configuration Fields Defined

Field Description

Password This field contains the Password for cloud Rec.vc. service login.

Max number of simultaneous

recordings

This field contains the max number of concurrent meeting

recordings allowed.

Recorder Name This field is used for configuring the recorder and should not be

changed by anyone unfamiliar with recorder settings.

Recorder URI This field is used for configuring the recorder and should not be


Recorder Hostname This field is used for configuring the recorder and should not be


Recorder Status This field is used for configuring the recorder and should not be


Recordings Storage This field is used for configuring where account records will be

stored, (i.e. locally or cloud) .This setting should not be changed

by anyone unfamiliar with recorder settings.

4.5.11 Account VMR

The phone dial-in information for a VMR meeting invitation is set via this configuration.

Figure 45: Account VMR Configuration