Port requirements for clients
2024-11-06Last updated
To enable communication with clients, you must open specific network ports.
Outbound port | Endpoint domain | Port usage |
---|---|---|
Web clients | ||
TCP 443 | securitycentersaas.genetec.cloud us.securitycentersaas.genetec.cloud |
Security Center SaaS Web Services |
login.genetec.com id.login.genetec.com assets.login.genetec.com challenges.cloudflare.com |
Genetec™ single sign-on (SSO) | |
login.microsoftonline.com aadcdn.msauth.net login.live.com |
||
events.launchdarkly.com app.launchdarkly.com clientstream.launchdarkly.com |
Genetec features management | |
sgnlr-uni-prodglobal-eastus2.service.signalr.net canadacentral-1.in.applicationinsights.azure.com |
Monitoring & eventing | |
az416426.vo.msecnd.net dc.services.visualstudio.com widget.intercom.io js.intercomcdn.com |
Dependencies | |
Genetec™ Operation web and mobile applications | ||
TCP 443 | *.gsc-cloud.com a.tile.openstreetmap.org b.tile.openstreetmap.org |
HTTPS port |
Genetec™ Configuration web | ||
TCP 443 | eastus2.video.genetec.cloud | HTTPS port for video operations |
Genetec Operation and Genetec Configuration desktop applications | ||
TCP 5500 | *.gsc-cloud.com | Genetec Security Center TLS proxy |
TCP 554 TCP 560 |
*.gsc-cloud.com | RTSP port (over TLS) |
TCP 960 | *.gsc-cloud.com | Live and playback stream requests |
TCP 443 | downloadcenter1.genetec.com | HTTPS |
TCP 8012 | *.gsc-cloud.com | Communication between the Map Manager role and desktop client applications |