Configuring Protocols

SIP Settings

To enable your terminal to use the SIP protocol, configure it in the Settings → Protocols → SIP section.

1. Enable the Enable SIP option.

2. Select the protocol for transmitting the content being shared from the BFCP transport dropdown list: UDP or TCP.

3. In the SRTP encryption dropdown list, select whether to use encryption via the SRTP protocol:

   • Forbidden – not used;

   • Allowed – the use of encryption is preferred but not mandatory, meaning that if the participant does not have it, a connection will still be established;

   • Mandatory – TrueConf Group will not connect with users who do not support SRTP.

• In the Registration tab, activate the Enable the SIP server option. Additionally, you can select the SIP transport to be used.

• To save the settings, click Apply.

Additionally, you can configure which server will handle outgoing SIP calls:

1. Activate Use the server as proxy for outgoing calls.

2. Enter the TrueConf Server address.

3. Enter the username (TrueConf ID) and password.

4. To save the settings, click Apply.

If the entered data is correct, the text in the Registration status section will change to Registered.

H.323 Settings

To configure the H.323 protocol through the terminal's main menu, use the remote control to navigate to Settings → Protocols → H.323.

1. Enable the Enable H.323 option.

2. In the H.235 encryption menu, select if it is necessary to use H.235 encryption:

   • Forbidden – not used;

   • Allowed – the use of encryption is preferred but not mandatory, meaning that if the participant does not have it, a connection will still be established;

   • Mandatory – TrueConf Group will not connect to the endpoints if they do not support H.235 encryption.

• Below, specify the H.323 ID and Extension number (E.164) for calling TrueConf Group without needing to enter the terminal's IP address (otherwise, the system name will be used as the default value).

All the entered fields will be transferred to the gatekeeper in the following order:

• Username for authorization.

• Extension number.

• H323 name.

• System name.

Additionally, you can use the Use the server as proxy for outgoing calls function. To do this:

1. Activate the Use server for outgoing calls toggle switch.

2. Specify the Gatekeeper address if you choose to enter it manually.

3. Enter the Gatekeeper login and Password for authorization (if required).

4. To save the settings, click Apply.

If the entered data is correct, the text in the Registration status section will change to Registered.

If this feature is not configured, calls specifying an IP address that does not match the gatekeeper's address are sent directly to the recipient without an ARQ request. Once this feature is configured, all calls are sent as ARQ requests to the gatekeeper.

NAT Settings

In the Settings → Protocols → NAT traversal section, the following settings are available to you: Protocols1. Public IPv4 address (WAN). Specify the public (external) IP address of your TrueConf Group, such as the WAN IP of the router it is connected to.

2. Ports with a range for protocols:

• RTP (UDP);

• H.245 (TCP)

• BFCP (UDP, TCP).

3. H.323:

• Signaling traversal (H.460.18);

• Media traversal (H.460.19).

4. SIP:

• Use ICE;

• Use TURN.

  • Specify the TURN server, username, and password (these fields can be edited regardless of the status of the Enable ICE and Enable TURN switches).

When resetting the TrueConf Group settings to factory defaults, the port ranges will revert to the standard default values for TrueConf Server:

• RTP (UDP) – 50000-51999.

• H.245 (TCP) – 52000-52499.

• BFCP (UDP, TCP) – 52500-52999.

RTP QoS

In the Settings → Protocols → RTP QoS section, you can specify:

• MTU limit for network data transfer (RTP packet size excluding UDP and IP headers) headings);

• QoS method of traffic prioritization (QoS) - DSCP or IP Precedence. QoS tag settings are available for the selected method.