Server Requirements
The server requirements depend upon the hosting preference you choose for your Synergy SKY platform. Please refer to Getting Started with a New Installation to view the supported deployment types.
Network Requirements
| Source | Destination | Protocol | Port (TCP unless otherwise stated) | Purpose |
|---|---|---|---|---|
| Customer Network | Synergy SKY Suite |
HTTPS HTTP |
443 80 |
Access the configuration tool UI |
| Customer Network | Synergy SKY Suite | SSH | 22 | Access the server configuration |
| Synergy SKY Suite |
Microsoft Exchange https://portal.azure.com |
HTTPS | 443 | Collecting calendar scheduling data. |
| Synergy SKY Suite | Cisco TMS |
HTTPS HTTP |
443 80 |
Tracking codecs on DHCP. |
| Synergy SKY Suite | Pexip Infinity Management Node |
HTTPS |
443 |
Initiating dial-out calls. Provisioning one-time VMRs Receiving dall data |
| Synergy SKY Suite | Pexip Conference Node | HTTPS | 443 | Optional: JOIN requires access to one Pexip conference node for displaying “End of Conference Warnings” |
| Synergy SKY Suite | StarLeaf Cloud https://api.starleaf.com | HTTPS | 443 | Provisioning gateway call in StarLeaf Cloud. |
| Synergy SKY Suite | Cisco Meeting Server (CMS) |
HTTPS HTTP |
443 80 |
Initiating dial-out calls. Provisioning one-time VMRs. Receiving call data |
| CMS callbridges | Synergy SKY Suite |
HTTPS HTTP |
8585 | Pushing CDRs from the CMS to Synergy SKY |
| Synergy SKY Suite | Cisco devices, rooms and codecs |
HTTPS HTTP |
443 80 |
Updating devices with Cisco OBTP information using direct integration Endpoint Control |
| Cisco devices, rooms and codecs | Synergy SKY Suite |
HTTPS HTTP |
443 80 |
Endpoint Control CDR Collection |
| Synergy SKY Suite |
Webex APIs
https://webexapis.com
|
HTTPS |
443 |
Updating devices with Cisco OBTP information using Webex integration |
| Synergy SKY Suite | Cisco VCS API |
HTTPS HTTPS |
443 80 |
CDR Harvest |
| Cisco codecs | Synergy SKY Suite |
HTTPS HTTP |
443 80 |
Applicable if the Cisco Webex Room endpoints are being used as occupancy sensors, refer to How To: Configure an Occupancy Sensor. |
| Synergy SKY Suite |
https://licensing.synergysky.com 20.126.214.19 |
HTTPS HTTP |
443 80 |
Synergy SKY License Management |
| Synergy SKY Suite |
https://download.synergysky.com 84.22.108.36/32 |
HTTPS HTTP |
443 80 |
Software Upgrades |
| Synergy SKY Suite | Internet |
HTTPS HTTP |
443 80 |
Optional: Synergy SKY requires internet access to find the address to the Skype meeting for CMS Microsoft 365 meetings, and for all external Skype invitations that are forwarded. |
| Synergy SKY Suite | Cisco IX, TX and CTS Codecs | HTTP | 8081/9501 | Updating the IX,TX and CTS Codecs with Cisco OBTP information |
| Synergy SKY Suite |
Synergy SKY IoT Cloud https://sensor.synergysky.com 37.252.127.218
https://dev-utf4mram.eu.auth0.com/ 104.16.96.94 104.18.244.88 |
HTTPS HTTP |
443 80 |
Synergy SKY requires internet access to communicate with Synergy SKY IoT Cloud to receive sensor data |
Port forwarding to Cisco endpoints
Cisco video systems that are on external networks can be reached directly over the internet by setting up a port forwarding rule in the firewall to allow direct access to the video system.
Note the following if using port forwarding to Cisco endpoints:
- Ensure the Port Forwarding rule only accepts requests from the specific IP address that Synergy SKY will connect from.
- Ensure the Port Forwarding rule forwards requests to the HTTPS service of the Video System.
- Ensure the Video System's HTTPS service is enabled.
- Ensure the Video System has a strict password set.
- Include the port number after the IP address when configuring the Video System in Synergy SKY (e.g. 213.112.33.179:8081).
Service accounts
| Account type | Permissions required |
|---|---|
| Microsoft Exchange User (with a mailbox) |
An Exchange administrator will have to configure the Exchange environment by following the relevant guide below:
Read and Write access to Meeting room resource mailboxes (Editor access to user mailboxes required if using in-body update). |
| Pexip MCU | Admin API account or LDAP API account. |
| Cisco CMS | Admin API account. |
| Cisco codecs | Admin user account. |
| Polycom codecs | N/A - Synergy SKY does not talk to the codec - the Polycom endpoints get the meetings from Exchange. |
| Cisco TMS (optional - used to track codecs on DHCP) | Site administrator user account. |
| Google API Access | API Scopes to allow for calendar access |
| Google Service Account |
Google Super Admin account in GSuite(admin.google.com). Additionally, Enable Domain Wide Delegation on the service account( console.cloud.google.com)
A Google Suite Administrator will have to configure the Google environment by following this guide: |
API Access Requirements
| API | Minimum Access Level | Description |
|---|---|---|
| Pexip API | Administrator | Used for configuring syslog servers |
| Cisco VCS | Read only, API access | Used for harvesting CDRs |
| CMS | API role | Used for configuring CDR receivers |
Supported Calendar Platforms
| Calendar Platform | Description |
|---|---|
|
Microsoft Exchange |
Exchange 2013 and above |
| Microsoft 365 | Microsoft Exchange platforms hosted in Microsoft 365 |
| Microsoft GCC-Moderate (IL-2) | Microsoft Exchange platforms hosted in Microsoft 365 Government GCC environment |
| Microsoft GCC-High (IL-4) | Microsoft Exchange platforms hosted in Microsoft 365 Government GCC environment |
| Microsoft GCC-DoD (IL-5) | Microsoft Exchange platforms hosted in Microsoft 365 Government GCC environment |
| Google Calendar | Part of Google Workspace (formerly G Suite) |
Supported Sensor Systems
| Manufacturer | Model | Description |
|---|---|---|
| Elsys | ERS | ERS Indoor Sensor using LoRaWAN. Can be purchased through Synergy SKY. See https://www.elsys.se/en/ers/ for technical information on the sensors. |
| N|Fuse | lRWGW8-RPI-868 | Gateway for all ERS Sensors. Can be purchased through Synergy SKY. |
| Cisco | Webex Room Series | Cisco Webex Room Kit Mini, Plus and Pro endpoints with People Count Technology |
Device Support
| Device | Version | Comments |
|---|---|---|
|
Microsoft Exchange |
On Prem, 0ffice 365 (Exchange Online) and GCC(IL-2, IL-4, and IL-5)
|
|
| Cisco TMS | 12.0 - 15.5 | |
| Pexip MCU | 13 - 24 | |
| Cisco CMS | 1.8 - 3.1 |
Must be configured with Dual Homed: The “Lync Simplejoin domain” must be present on the ExpresswayVCS if the endpoints route calls through one. Also, the CMS must have a working Lync outbound rule set up (Trunk type: Lync). |
|
Cisco codecs:
|
|
|
|
Polycom codecs:
|
All versions supporting Polycom OTD |
The endpoints must be configured to poll calendar data from Exchange using the Polycom Calendaring service:
NOTE:
The Polycom Trio is supported with Polycom One Touch Dial for one- Time-VMRs and regex/static VMRs in Synergy JOIN version 2.6. Microsoft Skype and Teams support is available in JOIN version 3.0. The reason is that the Trio will incorrectly try to call the hidden Skype GRUU if it finds it in the meeting invitation header when there is a different URI in the Polycom VMR token Synergy JOIN generates, even if the Trio is not registered towards a Skype server. |
Supported Internet Browsers
| Browser | Minimum Version |
|---|---|
| Google Chrome | 65.0.3325 |
| Mozilla Firefox | 61.01 |
Conference Control Limitations
There are some limitations in Pexip Infinity and Cisco Meeting Server itself when it comes to active meeting controls. Some of these limitations are overcome by the integration of Synergy JOIN (if integration is conducted) but direct controls related to participants are still dependent on API possibilities of the supported technologies.
| Technology | Mute/Unmute Microphone | Mute/ Unmute Video | Mute/ Unmute Sound | Disconnect Participant | Meeting Locking |
|---|---|---|---|---|---|
| Pexip Infinity | Yes | No | No | Yes | Yes |
| Cisco Meeting Server | Yes | Yes | Yes | Yes | Yes* |
* Note: In order to get Meeting Locking working properly on CISCO systems it necessary to distinguish between host and guest calls to a VMR (or co-space). It is important to setup “guest” and “host” accounts where for a guest the 'needsActivation' parameter has to be set. Refer to the Cisco CMS documentation for more information on how to set this