Synergy Manage platform overview and requirements

The Synergy Manage platform is made up of a number of modules:

SKY WinNode Server
SKY SQL Database Server
Linux Com Node Server
Windows Remote Agent Server (Optional)

We strongly recommend that each server is used only for Synergy Manage (with the exception of the SKY SQL Database Server).

Hardware requirements

Minimum server resources:

Server	Operating system	Purpose	CPU	RAM	HDD	Comments
SKY WinNode Server	Windows Server 2012 Windows Server 2012 r2 Windows Server 2016 Windows Server 2019	Runs: IIS web applications SKY-specific windows services	2 GHz 4 Cores	8 GB	50 GB
SKY SQL Database Server	Windows Server 2012 Windows Server 2012 r2 Windows Server 2016 Windows Server 2019	Synergy Manage SQL database	2 Ghz 2 Cores	8 GB	50 GB	Requires SQL Server 2012, 2014 or 2016
SKY ComNode	Linux	Synergy Manage Mongo and LDAP databases, and communication hub: DBNode XMPPNode MemNode Third party infrastructure communication (Pexip and Cisco CMS): Data harvesting Provisioning Internal SKY applications	2 GHz 6 cores	16 GB	170 GB	High performance disk recommended (SSD/SAS)
(Undefined variable: WinRemoteAgentServerLong) (optional)	Windows Server 2012 Windows Server 2012 r2 Windows Server 2019	Gathers status information and call data records from Cisco, Microsoft Skype for Business, and Polycom infrastructure components deployed at remote sites Gathers status information from Cisco CMS and Pexip infrastructure components deployed at remote sites	2 Ghz 2 Cores	8 GB	50 GB

Remote Agent Server (optional)

The main purpose of a Remote Agent server is to fetch status information and call data records from infrastructure devices deployed at remote sites. This server is not mandatory in all types of installations, but is recommended for deployments where infrastructure devices are installed remotely.

If your Remote Agent server communicates with remotely located Cisco, Polycom or Skype for Business infrastructure components, then you will require a Windows Remote Agent (RA WinNode).

Network requirements

Synergy Manage requires that the following ports are open on your network (<-> = bidirectional):

Win Node:

Source	Destination	Protocol	Port (TCP unless otherwise stated)	Description
Win Node	Cisco CMS MCU	HTTPS	443	Read status
Win Node	Pexip Infinity Management node Pexip Infinity Conference node	SSH	22	Read status
Win Node	Cisco Codian MCU Cisco Codian ISDN Gateway	XML over RPC	80 (if HTTPS is not enabled on the gateway) 443	Read status and data harvesting from MCU and/or ISDN RPC API
Win Node	Cisco TCS	HTTP/HTTPS	80/443	Read status and data harvesting from TCS API
Win Node	Cisco TMS	HTTP/HTTPS SQL	80/443 1443 (or whichever port you have configured, if not default)	Read status, data harvesting
Win Node	Cisco VCS	HTTP/HTTPS	80/443	Read status and data harvesting from VCS API
Win Node	Polycom RMX	HTTP/HTTPS	80/443	Read status
Win Node	Polycom DMA	HTTP/HTTPS SNMP	80/443 8443 UDP: 161	Read status DMA API port Real time status
Win Node	Skype for Business front-end server	SQL	1433 (or whichever port you have configured, if not default)	Read status
Win Node	Skype for Business CDR server	SQL	1433 (or whichever port you have configured, if not default)	Data harvesting
Win Node	SMTP server(s)	HTTP/HTTPS SMTP	80/443 25 (or any port configured for SMTP)	Send password reset email(s) and scheduled reports
Win Node	SNMP Receiver	SNMP	161	SNMP Traps/Alarms
Win Node	(Undefined variable: SQLDBServerShort)	SQL	1433	Read/write to/from SQL database
Win Node	External AD/LDAP server	LDAP	389	AD/LDAP user sync.
Win Node	Exchange	HTTP/HTTPS	80/443	Exchange web services and API for Scheduling.
Win Node	Com Node	HTTP LDAP LDAPS XMPP	80 <-> 389 636 5222 <->	Com Node API LDAP directory LDAPS directory XMPP communications

Com Node:

Source	Destination	Protocol	Port (TCP unless otherwise stated	Description
Com Node	Pexip Infinity Management node	HTTPS	443	Provision VMRs.
Com Node	Cisco CMS MCU	HTTPS	443	Provision Spaces Initiate user synchronization
Com Node	SMTP server(s)	SMTP	25 (or any port configured for SMTP)	Send alert and scheduling email(s).
Com Node	Cisco Codian MCU	XML over RPC	80 (if HTTPS is not enabled on the gateway) 443	Provision VMRs.
All Com Nodes	(Undefined variable: SQLDBServerShort)	SQL	1433	Create/update SQL database Legacy sync service
Cisco CMS MCU	Win Node	HTTP/HTTPS	Configurable (default is 6060)	CDR Receiver for data harvesting
Cisco CMS MCU	Com Node	LDAP LDAPS	389 636	Synchronization of users

Remote Agent Servers (if implemented):

Source	Destination	Protocol	Port (TCP unless otherwise stated)	Description
RA WinNode	Cisco CMS MCU	HTTP/HTTPS	80/443	Read status
RA WinNode	Pexip Infinity Management node Pexip Infinity Conference node	HTTP/HTTPS SSH	80/443 22	Read status
RA WinNode	Cisco Codian MCU Cisco Codian ISDN Gateway	XML over RPC	80 (if HTTPS is not enabled on the gateway) 443	Read status and data harvesting from MCU and/or ISDN RPC API
RA WinNode	Cisco VCS	HTTP/HTTPS	80/443	Read status and data harvesting from VCS API
RA WinNode	Polycom RMX	HTTP/HTTPS	80/443	Read status
RA WinNode	Polycom DMA	HTTP/HTTPS SNMP	80/443 8443 UDP: 161	Read status DMA API port Real time status
RA WinNode	Skype for Business front-end server	SQL	1433 (or whichever port you have configured, if not default)	Read status
RA WinNode	Skype for Business CDR server	SQL	1433 (or whichever port you have configured, if not default)	Data harvesting
RA WinNode	SQL Server	SQL	1433 (or whichever port you have configured, if not default)	Data harvesting
RA WinNode	Win Node	HTTP	80	Harvest API
Cisco CMS MCU	Win Node	HTTP/HTTPS	80/443	CDR Receiver for data harvesting

Network diagram

Supported infrastructure components

The following infrastructure software versions are supported for use with Synergy Manage. It is your responsibility to ensure that any infrastructure you want to integrate with Synergy Manage is running a supported software version:

Infrastructure	Version	Comments
Cisco VCS	All versions from X4.3 - X8.10.2
Polycom DMA	v6.1	H.323 call matching is supported on a best-effort basis for Polycom DMA registrations, which can lead to incomplete reports and invoices. SIP registrations are fully supported for Polycom DMA. Provisioning is not supported for Polycom DMA. The RealPresence Platform API license is required to integrate the Polycom DMA with Synergy Manage (at additional cost from Polycom).
Skype for Business	2013	Billing and Provisioning are not supported for Skype for Business.
Skype for Business	2015	Billing and Provisioning are not supported for Skype for Business.
Codian MCU	All versions from 4.2 - 4.5	UTC offset must be set to 0 due to the lack of support for automatic DST change.
Cisco TelePresence Server	v3.0 and v3.1	Provisioning is not supported for Cisco TelePresence Server.
Pexip Infinity MCU	All versions from v11.x+	FQDN host addresses are not supported for Pexip Infinity nodes. A cluster must be created for any Pexip management and conference node (s). The management node must be set as the conference master. Any conference nodes must be added to their intended cluster.
Cisco CMS Server	v1.8.x up to v 2.7
Polycom RMX	v8.5.1	H.323 call matching is supported on a best-effort basis for Polycom RMX calls, which can lead to incomplete reports and invoices. SIP calls are fully supported for Polycom RMX. Provisioning is not supported for Polycom RMX.
Cisco Codian ISDN Gateway	API v2.7 (sw v2.1 or later)	UTC offset must be set to 0 due to the lack of support for automatic DST change. Provisioning is not supported for Cisco Codian ISDN Gateway.
Cisco TelePresence Management Suite (TMS)	all versions from v13.2 - v15.4
Cisco TelePresence Content Server (TCS)	v5.0 - v6.1	Reporting and Billing are only supported if the call is routed through a Cisco VCS. CDR harvest is not supported for Cisco TCS. Provisioning is not supported for CIsco TCS.