Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP.

Cinegy Port Usage

Service names are assigned on a first-come, first-served process.

Port numbers are assigned in various ways, based on three ranges: system ports (0-1023), registered (user) ports (1024-49151), and dynamic and/or private ports (49152-65535).

Dynamic ports are not assigned.

Caution
All new port usages SHOULD NOT collide with common existing protocols - but over port 8000 is preferable and normally safe. Assigned ports, both system and registered ports, SHOULD NOT be used without or prior to IANA registration. Check IANA.

Here is a list of ports used by Cinegy:

Product Name Type Technology Port Number(s) Root URL Firewall URL Reser-vation Notes

Cinegy Traffic Gateway

TCP

WCF SOAP

14544

http://+:14544/bxfgateway

Yes

Yes

This is the industry standard port for BXF interchange

Cinegy Traffic Gateway

TCP

WCF SOAP

8097

http://+:8097/gateway

Yes

Yes

Main service host WCF endpoint

Cinegy Traffic Gateway

TCP

WCF SOAP

8097

http://+:8097/license

Yes

Yes

Endpoint for verifying license status

Cinegy Player PRO

TCP

WCF REST

8123

http://+:8123/player

Yes

Yes

REST methods for interaction from third parties and browsers

Cinegy Multiviewer

TCP

WCF REST

8000

http://+:8000/

Yes

Yes

Remote control static webpage hosting

Cinegy Multiviewer

TCP

WCF REST

8090

http://+:8090/Multiviewer/Rest

Yes

Yes

REST methods for controlling Multiviewer

Cinegy Multiviewer

TCP

WCF SOAP

8091

http://+:8091/Multiviewer/Event

Yes

Yes

SOAP methods for event subscription

Cinegy MCRItem Service

TCP

WCF REST

8911

http://+:8911/

Yes

Yes

REST methods for getting MCRItem XML

Cinegy Identity Service

TCP

WCF REST

7500

http://+:7500/

Yes

Yes

REST service methods (see swagger sandbox)

Cinegy License Portal

TCP

WCF REST

7600

http://+:7600/

Yes

Yes

REST service methods (see swagger sandbox)

Cinegy Process Coordination Service

TCP

WCF SOAP

8555

http://+:8555/CinegyProcess-CoordinationService/soap

Yes

Yes

Main service host WCF endpoint

Cinegy Process Coordination Service

TCP

OWIN REST

8666

http://+:8666/pcs

Yes

Yes

REST service methods (see swagger sandbox)

Cinegy Playout Engine

UDP

SRT

Main preview: 5421-5436 Cued preview: 5471-5486

Yes

SRT feedback stream: Main preview: 5421+N Cued preview: 5471+N (where N is the zero-based Engine instance number)

Cinegy Playout Engine

TCP

RPC

5321-5336

Yes

RPC port for control API (5321 + instanceNo)

Cinegy Playout Engine

TCP

HTTP

5521-5536

http://+:port/

Yes

No

HTTP API (5521 + instanceNo)

Cinegy Air Web API Service

TCP

OWIN REST

7501

http://+:7501/

Yes

Yes

REST service methods (see swagger sandbox)

Cinegy Playout Engine Agent Service

TCP

OWIN REST

7502

http://+:7502/

Yes

Yes

REST service methods (see swagger sandbox)

Cinegy Agent Service (software management)

TCP

OWIN REST

7503

http://+:7503/

Yes

Yes

REST service methods (see swagger sandbox)

Cinegy License Service

TCP

RPC

5437

No

N/A

RPC port for license sharing

Cinegy License Service

TCP

HTTP

8989

http://+:8989/getinfo

No

No

HTTP XML body indicating license service status, version, licenses and connections

Cinegy Convert Agent Manager

TCP

WCF SOAP

7601

http://+:7601/

Yes

Yes

Cinegy Convert machine resource monitor service

Cinegy Capture Engine

TCP

WCF SOAP

8001-8099

http://+:port/Cinegy/CaptureControl

Yes

Yes

SOAP methods for Capture Engine controlling

Cinegy Capture Engine

TCP

WCF REST

8001-8099

http://+:port/REST

Yes

Yes

REST methods for Capture Engine controlling

Cinegy Capture Agent

TCP

WCF SOAP

7000

http://+:7000/CaptureAgentService

Yes

Yes

SOAP methods for Capture Agent controlling

Cinegy Capture Web Control

TCP

HTTP

7000

http://+:7000/control/web/

Yes

Yes

Access to Capture Web Control web page

Cinegy Capture Archive Adapter

TCP

WCF SOAP

8020

http://+:8020/Cinegy/ArchiveAdapter

Yes

Yes

SOAP methods for Capture Archive Adapter controlling

Cinegy Capture Planner

TCP

HTTP

8888

http://+:8888

Yes

Yes

Access to Capture Planner web page

Cinegy Capture Planner

TCP

WCF SOAP

8010

http://+:8010/Host

Yes

Yes

SOAP methods for Capture Planner controlling

Cinegy Route Directory Svc

TCP

.Net Remoting

9995

Yes

N/A

RPC port for client tool connections

Cinegy Route Directory Svc

TCP

HTTP

9996

Yes

N/A

HTTP requests (e.g. for Virtual Destination queries)

To access an instance of the SQL Server through a firewall, you must configure the firewall on the computer that is running SQL Server. For more information about the relevant procedure, see the article Configure the Windows Firewall to Allow SQL Server Access