This list shows a list of Room Lists from your Exchange or Google Environment

Room lists are special address books in Exchange/ Google that only contain room resources.

If no room lists are shown, ask your administrator to create one for you based on the examples below.

Once a list of Room Lists is shown, you can select the rooms you would like to add and click the 'Add Selected Rooms' button in order to add them to the rooms to be monitored.

Example for creating room lists in the Microsoft Exchange PowerShell tool:

$RoomAlias = Get-Mailbox -RecipientTypeDetails RoomMailbox -Filter {Office -eq 'HQ'} | select -ExpandProperty Alias

New-DistributionGroup -RoomList -Name 'HQ Meetingrooms' -Members $RoomAlias

$RoomAlias = Get-Mailbox -RecipientTypeDetails RoomMailbox | select -ExpandProperty Alias

New-DistributionGroup -RoomList -Name 'All Meetingrooms' -Members $RoomAlias

This button is used to refresh the room list dropdown.

Note: It can take up to 15 minutes before a room list is visible here after adding a room list in Exchange.

Click this button to add rooms from Exchange manually.

This is done by providing a display name and an alias for the room.

ON/OFF to allow the room's resource calendar to be monitored.

This is the selected policy that will be executed if nobody shows up in the meeting room. You can read more about policies in this guide.

If something like TMS exists in your environment, it may try to update endpoints with meeting information regularly which can overwrite the OBTP information Synergy SKY sends to endpoints.

Switching this on will cause the Software to connect to the endpoints more frequently thus updating the OBTP information more frequently.

This dropdown list contains all available meeting rooms added in the Rooms tab. You can associate the video system directly with a meeting room here, or you can set it to None and associate it later - either from this page or from the Rooms page.

Note: If set to None, the video system will be disabled by default.

The address of the video system on which the Software can communicate with the endpoint. This field is only applicable for Cisco endpoints.

The username and password the Software must use to authenticate with the video system. Only applicable for Cisco endpoints.

The video address (URI) of the video system. This information is applicable only if the Connectivity type is set to 'Dial-out'.

Video systems configured with dynamic IP address assignment (DHCP) will be tracked and updated. The Software is able to track changes to the IP address and automatically update its connection details to make sure it can continue pushing One Button To Push data to the video system even though it has changed its IP address. This is currently available for Cisco video systems only.

Video systems that support people count functionality, like Cisco Webex Room systems, can report the number of people in meetings. In order to activate this reporting, enable this field.

The different video system manufacturers might have different software platforms on their different models. Synergy SKY will try to automatically identify the software type when it connects to the system, but we recommend setting it here regardless.

This setting defines how the video endpoints should be connected into the meeting. The valid options are:

One Button To Push:

The video system will be populated with a Join button by Synergy SKY. When clicking the Join button the video system will dial into the correct meeting. This feature is only available for Cisco and Poly endpoints.

Dial-out:

For video systems not supporting the One Button To Push mechanism, Synergy SKY can initiate the meeting to dial out to the video system. The video system can e.g. be configured with 'auto answer' mode so that it will be automatically connected without any user interaction. The dial-out feature is only supported by on-premise Pexip Infinity and Cisco Meeting Server MCUs.

None:

Synergy SKY will not perform any action toward the endpoints if None is selected

This rule makes JOIN look for Skype invites in hidden text in the invite.

This will normally work for all Skype meetings when the invitation is sent internally in the organization. The information may however be lost if the email jumps multiple Exchange servers, or when the invite comes from someone outside the organization.

This rule analyzes the Hyperlink in the body of the invitation to find the URI of the Skype meeting. This will work in most environments, both internally and externally, but is slower. It is therefore recommended to use this as a fallback rule with lower priority than the Skype URI in Headers rule.

Note: This function requires Synergy JOIN to have access over HTTPS to the Skype server where the meeting is hosted; either directly or via a proxy server.

This rule makes JOIN look for Teams invites in hidden text in the invite.

This will normally work for all Teams meetings when the invitation is sent internally in the organization. The information may however be lost if the email jumps multiple Exchange servers, or when the invite comes from someone outside the organization.

Note: The Teams rule should be added with a high priority than the Skype rules, since Teams invitations also contains an Skype invitation in the header

This rule enables you to use Regex to define how you want JOIN to work. You can define your own pattern matches, and differentiate between invitations from internal and external organizers.

This rule type can be added multiple times.

Note: This rule contains some pre-set templates for additional meeting types (

This field defines the Regex rule for matching data. For example:

\d@company.com will match all URIs starting with a number and ending with @company.com

This field defines how the matched data should be transformed before being sent to the endpoint.

Pexip:

The value \0 uses the entire matched value, while \1 matches the first pair of parenthesis and so on.

Example:

Matching Value: Id: (\d)

Replace Value: \1@video.company.com

Email body: Conference Id: 123456789

URI = 12346789@video.company.com

CMS:

If you have CMS for internal dual-home, you can use a Regex rule to look for "conference id: 123456" from internal meeting organizers.

This field is used to test invites against the matching and replace values you've entered above.

Paste in a sample text and make sure that the rule is giving the expected result. Note: If the invitation is html formatted, you will need to paste in the html source of the email invitation.

The start buffer defines when VMRs are provisioned and can be dialled into, and it defines when the green button in the Cisco OBTP or Polycom OTD message can be pressed on the video system.

If ticked, End of Conference Warning notifications will be presented in the video stream X minutes before a conference is about to end. This applies for:

• Pexip Infinity personal VMRs
• Pexip Infinity One-Time VMRs
• CMS One-Time-VMRs

End of Conference Warning Notifications do not work for Gateway calls or cloud-based conferences.

• End of booking: durations and other specifications are relative to the end time of the booked conference.
• End buffer: durations and other specifications are relative to the conference end buffer.

This function will enable Synergy JOIN to log into the calendar of each meeting's organizer to update the calendar invite and send an update to all invitees. This end-user experience will allow users to book video meeting directly from their native calendar clients without having any custom plug-ins installed, and still have the dial-in information of the video meeting automatically.

Note: Remember to define in which cases the body of the meeting invitation should be updated in the settings above; i.e. One-Time-VMR, Skype Meeting, Regex rule meeting.

Failure to update the calendar will lead to an email being sent to the meeting organizer with the dial-in details, with instructions to update the invite manually. The administrator, defined in the General Settings tab will also be notified about the failure. The notification to the administrator will contain the commands required to fix permissions problems in the organizer's calendar. See Configuring In-Body Update for information on how to set the correct permissions in Microsoft Exchange required for this feature to operate correctly.

Note: Enabling the generation of Host pins for conferences and adding this to the email template will make the host pin visible to all invitees since the same information is sent out to all participants in the meeting. The host pin should therefore be defined in the 'Host pin' template. See Configuring Email templates for more details.

Host PINs will be created to identify the host of the meeting. A 4-digit PIN code will be randomly generated for each One-Time VMR for hosts to use to start the meeting.

Sent to participants external to your organization when a One-Time-VMR meeting is booked. Includes dial-in information for the meeting.

If JOIN fails in updating the organizer's calendar, it will send out an email to the organizer containing this information.

Sent to internal participants when a Skype meeting is booked.

Sent to the meeting organizer when a One-Time-VMR meeting is booked.

Note: This information will be inserted into the calendar invite and is resent to all invitees when the In-Body Update function is used.

Sent to the meeting organizer when a Skype meeting is booked.

Note: This information will be inserted into the calendar invite and is resent to all invitees when the In-Body Update function is used.

Sent to the meeting organizer when a Regex rule meeting is booked.

Note: This information will be inserted into the calendar invite and is resent to all invitees when the In-Body Update function is used.

We recommend settings this to be the Synergy CONTROL server (HTTP or HTTPS URI). Please note that in the case where reverse proxy is used, this URL will be different.

Note : a suffix "/auth-callback" will be added automatically. Please use full URI string in Azure configuration (e.g. https://suite.company.com/control/auth-callback)