Configuring Protocols

SIP Configuration

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

1. Enable item Enable SIP.

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

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

   • Forbidden - not used;
   • Allowed – using encryption is preferable but not mandatory, meaning if the subscriber does not have it, the connection will still be established;
   • Mandatory – TrueConf Group will not connect with users who do not support SRTP.

4. On the Registration tab, enable the Enable the SIP server option. Additionally, you can select the SIP transport to use.

5. To save the settings, click Apply.

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

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

2. Enter the address TrueConf Server.

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

4. To save the settings, click Apply.

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

H.323 Configuration

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

1. Enable item Enable H.323.

2. In section H.235 encryption, select whether to use encryption via the H.235 protocol:

   • Forbidden - not used;
   • Allowed – using encryption is preferable but not mandatory, meaning if the subscriber does not have it, the connection will still be established;
   • Mandatory – TrueConf Group will not connect with users who do not support H.235.

3. Specify H.323 ID and Extension number (E.164) below for calls to TrueConf Group without needing to provide the terminal's IP address (otherwise, the system name will be used as the default value).

All entered fields will be transmitted 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 feature. To do this:

1. Toggle the switch .

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

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

4. To save the settings, click Apply.

If the entered data is correct, the text in block Registration status 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 an ARQ request to the gatekeeper.

NAT Configuration

In section Settings → Protocols → NAT traversal, the following settings options are available to you:

1. Public IPv4 address (WAN)Specify the public (external) IP address of your TrueConf Group, for example, the WAN IP of the router to which it is connected.
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

   • Использовать TURN.

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

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 section Settings → Protocols → RTP QoS, you can configure:

• MTU limitation on the size of data transmitted over the network (RTP packet size excluding UDP and IP headers);

• QoS method traffic prioritization (QoS) – DSCP or IP Precedence. QoS label settings are available for the selected method.