Calls via SIP/H.323 to TrueConf Server

Joining a conference

To make a call from a hardware or software SIP/H.323 terminal (including TrueConf Group) to a conference hosted on TrueConf Server, use the call string in one of the following formats:

• 00<Conference_ID>@<server>

• 00<Conference_ID>@<server>:<port>

where:

• <Conference_ID> — Conference ID;

• <server> — the server domain name or IP address

• <port> — the connection port (used if the port is different from standard 5060 for SIP and 1720 for H.323).

For example:

001949195144@video.company.com

001949195144@video.company.com:1730 (the port is explicitly specified because it differs from the default 1720)

Please note that when calling from TrueConf Videobar and TrueConf Server, you need to use the same format as for client applications, specifically #sip:00<Conference_ID>@<server>.

To join a PIN-protected conference from an SIP endpoint, it is necessary to add PIN, separated by a comma after the conference ID in the call string:

00<conf_id>,pin@<server>:<port>

Call a TrueConf Server User

To call a user registered on TrueConf Server from the terminal, use one of the following formats:

• <User_ID>@<server>

• <User_ID>@<server>:<port>

where:

• <User_ID> — TrueConf ID of the user;

• <server>— IP address or domain name of the server where the call should be routed

• <port> — the connection port (used if the port is different from standard 5060 for SIP and 1720 for H.323).

For example:

james78@video.company.com

james78@video.company.com:5070 (the port is specified explicitly because it differs from the default 5060)

Additional features

Additionally, to make a call via SIP, you can explicitly specify the protocol name (UDP is used by default):

00<conf_id>,pin@<server>:<port>;transport=<protocol>

Some H.323 terminals, such as Cisco, also support the call string format with double hashes ##. In that case, users can make a call in the TrueConf conference as follows:

<server>##00<user>

<server>##00<conf_id>