Calls to TrueConf Server via SIP/H.323

Connecting to a conference

To make a call from a hardware or software SIP/H.323 endpoint (including TrueConf Group) to a conference hosted on TrueConf Server, use a 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 as it differs from the default 1720)

Please note that when calling from TrueConf Videobar and TrueConf Server, the format should be the same 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 to a TrueConf Server user

To make a call from the endpoint to a user registered on TrueConf Server use one of the following formats:

• <User_ID>@<server>

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

where:

• <User_ID> — the user's TrueConf ID

• <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 endpoints like Cisco also support call strings with double hashes ##. In this case TrueConf users and conferences can be called in this way:

<server>##00<user>

<server>##00<conf_id>