You can configure the Media Gateway role from the Video task in Security Center Config Tool.
Media Gateway - Properties tab
Click the Propertiestab to enable the RTSP protocol on the Media
Gateway and to configure the stream settings used by the Media Gateway to transcode video
streamed to the Web Client or Genetec™ Web App.
- RTSP
- RTSP protocol settings.
- Enable
- This option is turned off by default for security reasons. Turn it on to see the other settings.
- Start multicast address
- Start multicast address and port number for IPv4 and IPv6. In multicast, all video sources are streamed to different multicast addresses using the same port number, because multicast switches and routers use the destination IP address to make their routing decisions. Similarly, the Media Gateway assigns that same port number to all streaming cameras, starting with the specified IP address and incrementing the IP address by 1 for each new camera it encounters.
- Listening port
- Incoming TCP command port used by the Media Gateway.
- Require TLS (RTSPS)
- This option is turned off by default because RTSPS is rarely supported. However, if your client application does support RTSPS, turn it on to heighten the security of your system.
- User authentication
- This option is turned on by default for security reasons. When the switch is
on, only authorized users can connect to the Media Gateway. When the switch is
off, anyone can connect to the Media Gateway without credentials.NOTE: The cameras that an RTSP client application can view in the system depend on the user account the client uses to log on to Security Center. If RTSPS is disabled, you must specifically add the users you allow to access this Media Gateway role to the Accessible to list. Assign to each user a different password than the one used for connecting to Security Center to minimize the risks of exposing their Security Center passwords. If RTSPS is enabled, the Media Gateway uses regular Security Center credentials to validate access. Moreover, the Security Center users must have the Log on using the SDK privilege.
- HTTP
- HTTP ports and URL settings.
- Use the default web ports of the server
- By default, the Media Gateway communicates with the Mobile Server and Web
Server roles over HTTPS port 443 and HTTP port 80. These ports are defined on
the servers that host the Mobile Server and the Web Server roles respectively.
If your IT policy requires different ports, or there is some sort of conflict,
you can change the ports. Turn off the option to use the default ports, then
change the HTTP port and secure HTTP port settings.IMPORTANT: If you have an unsigned (invalid) SSL certificate and end-users monitor video in Web Client using Mozilla Firefox or Microsoft Edge browsers, ensure that the ports set on the Media Gateway match the ports on the web server.
- Web address
- Define the suffix of the URL used by the Mobile Server and Web Server roles to
connect to the Media Gateway. The format of the URL is
https://host:port/web address, where
host is the IP address or host name of the server that
hosts the Media Gateway role, port is the HTTP port or the
HTTPS port, and web address is
mediaby default.
- Video streaming
- Video settings for streaming video over HTTP. Only the Web Client use these
settings. For streaming to mobile devices, the Media Gateway follows the settings
configured for the Mobile Server role.
- Default live stream
- The default stream used for streaming live video. It is either one of the five
standard streams: Live, Recording, Remote, Low
resolution, High resolution, or it is Automatic.With the Automatic option, the Media Gateway decides between the Low resolution, the Live, or the High resolution stream, based on the resolution of the viewing tile in the browser. The following thresholds help the Media Gateway make that decision.
- Low resolution to Live
- Resolution at which the Media Gateway decides to use the Live stream. Below this resolution, the Media Gateway uses the Low resolution stream.
- Live to High resolution
- Resolution at which the Media Gateway decides to use the High resolution stream.
- Allow transcoding
- Controls whether the Media Gateway should be allowed to transcode and in what
situation. Transcoding is very CPU intensive and
should only be performed by high end servers.
- Never
- The Media Gateway never transcodes. If the client device cannot decode the stream, the error "Unsupported codec" is displayed.
- Only for PTZ control and Mobile Server
- The Mobile Server role can request transcoded streams at any time. Other applications can only use transcoding to reduce video latency while the user is controlling a PTZ, otherwise an error message is displayed.
- Always (for unsupported devices and codecs)
- The Media Gateway transcodes when:
- The client application requests it.
- PTZ camera is being moved (to reduce latency).
- The codec used by the camera is not supported by the client application.
- Maximum resolution for MJPEG transcoding
- When transcoding, downscale the resulting transcoded stream to this resolution. Stream that are not transcoded are untouched.
- Frame rate
- Maximum frame rate of the resulting transcoded stream.
Media Gateway - Resources tab
Click the Resources tab to
configure the servers assigned to this role.
The Media Gateway role does not require a database.
- Servers
- Servers hosting this role.