# Configuring Protocols
# SIP Settings
To enable your terminal to use the SIP protocol, configure it in the Settings → Protocols → SIP section.
Enable SIP support.
Select the protocol for streaming the shared content in the BFCP transport menu: UDP or TCP.
In the SRTP encryption section, select whether to use SRTP protocol encryption:
Off – is not used
Optional – encryption is preferred, but not required which means that the connection will be established if the encryption is not configured on the far-end side
Mandatory – TrueConf Group will not connect with users who do not support SRTP.
On the tab, activate the option. Additionally, you can select the to be used.
To save the settings, click Apply.
Additionally, you can configure which server will handle outgoing SIP calls:
Activate Use server for outgoing calls.
Enter the address of the TrueConf Server.
Enter the username (TrueConf ID) and password.
To save the settings, click Apply.
If the entered data is correct, the text in the section will change to Registered.
# H.323 Settings
To configure the H.323 protocol, use the remote control to navigate to Settings → Protocols → H.323 in the terminal's main menu.
Enable H.323 support.
In the H.235 encryption menu, select if it is necessary to use H.235 encryption:
Off – is not used
Optional – encryption is preferred, but not required which means that the connection will be established if the encryption is not configured on the far-end side
Mandatory – TrueConf Group will not connect to the endpoints if they do not support H.235 encryption.
- In the tab, specify the H.323 Alias and H.323 extension (E.164) for calls to TrueConf Group without needing to enter the terminal's IP address (otherwise, the system name will be used as the default value).
All entered fields will be transferred to the gatekeeper in the following order:
Username for authentication.
Extension number.
H323 name.
System name.
Additionally, you can use the Use server for outgoing calls feature. To do this:
Activate Use server for outgoing calls.
Enter the Gatekeeper address (if you choose to input it manually).
Enter the Gatekeeper login and Password for authentication (if required).
To save the settings, click Apply.
If the entered data is correct, the text in the 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 an ARQ request to the gatekeeper.
# NAT Settings
In the Configuration → Network → NAT section, you have access to the following settings sections:
- 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
H.245 (TCP)
BFCP (UDP, TCP).
3. H.323 Settings:
H.460.18 Signaling Traversal;
Media traversal (H.460.19).
4. :
Use ICE;
Use TURN.
5. Настройки TURN. Specify the TURN server, username, and password.
When resetting 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 section, you can configure:
MTU limit on the size of data transmitted over the network (RTP packet size excluding UDP and IP headers). headers);
QoS method of traffic prioritization (QoS) – DSCP or IP Precedence. QoS tag settings are available for the selected method.