The Network link available from the main administration interface can be used to control various network settings for your central node and your remote nodes.

Basic or Details
The Basic network settings will display basic port information, including HTTP, HTTPS and UDP ports as well as let you enable or disable IP multicast.

The Details page gives you the possibility to specify UDP port ranges, bind the Manager to a specific network interface and better control multicast.

BASIC NETWORK SETTINGS

Select Node
Select what node you wish to review or modify the networks settings for. If you wish to change the configuration of a remote node, please select it here.

This alternative is only available if you have several nodes defined.

Web Server
Normal HTTP: 8000 (Default) This is the http (web) port used for reaching the Manager. While the default port is 8000, the Manager may be using another one if 8000 is busy. For simplicity's sake, many admins switch this port to 80, the standard port for http traffic. When doing this, beware of conflicts with Apache Web Server or IIS..

Administrators not wanting any HTTP traffic to their server may switch it off. (see below)

Secure HTTP (HTTPS): 8001 (Default) This is the https (web) port used for encrypted HTTP traffic. Use of HTTPS is recommended. For simplicity's sake, many admins switch this port to 443, the standard port for HTTPS traffic. When doing this, beware of port conflicts with Apache Web Server or IIS that may also be using these ports.

Before enabling HTTPS the first time, you will need to create or import a web server certificate. Directly from the Manager's web interface, you may: create a self signed certificate or import an existing web server certificate (Recommended). Read more about this further below.

Redirect HTTP to HTTPS: This option will redirect all unencrypted HTTP traffic to the more secure HTTPS port. Therefore, users surfing to the unencrypted port will be redirected and secured automatically. (Recommended)

Session Engine
Select a range of ports for UDP traffic between 1 and 65535. The default range is between 52000 52999. Try to use an unused range. Remember that each active meeting requires 12 ports.

Enable Multicast: This will enable IP multicast on your Manager. Marratech clients will automatically attempt to use multicast when joining a meeting. If it fails, it will attempt to join via unicast automatically.

Click Apply to save your changes.

DETAILED NETWORK SETTINGS

Network Interface
Bind address: Use this to bind to a specific network interface, should your server have more than one.

Session Engine
Extra Address: If your server is placed behind a NAT and you wish to give outside access to it via port forwarding, enter the external NAT address here. When setting an external address for NAT handling, a manual restart of the whole server is required.

UDP port ranges: For extra flexibility, you may enter many UDP port ranges instead of only one, as offered in the Basic network settings page.

Multicast range and Time To Live: Set your IP multicast address range and the time to live for your packets here.

	If you have more than one node with multicast enabled, and they reside within the same multicast network, you will need to assign a unique address range to each node to avoid address collision.
	Click Apply to save your changes.

ABOUT WEB SERVER CERTIFICATES

A web server certificate is required to secure the information sent from the Manager to the Marratech client. The certificate will secure (by using SSL) vital information such as meeting keys, Manager passwords as well as all the web pages being sent to the Marratech client. Furthermore, a proper web certificate proves the identity of your Manager to all users connecting to it. With Manager 3.1, you may use two types of certificate, a self generated, self signed certificate or a real certificate purchased from the proper authorities.

A self-signed certificate must be imported in the web browsers of all users in order to get rid of the security warnings telling the user that the certificate is not issued by a known CA (Certificate Authority). It does not prove to your users the authenticity of your Manager.

A real certificate issued by a CA will automatically be accepted by most web browsers. A real certificate from a CA is worth the investment and is strongly recommended by Marratech. Furthermore, it removes the security warnings shown by your users' web browsers. Marratech has tested certificates from Thawte and Verisign.

The web server certificates you have added can be found in the Advanced section, under the Control Unit section and clicking on CTRL@Central button. You can also generate a signature request using this page.

A signature request is sent to a CA when purchasing a real issued certificate.