For a complete list of call formats, please see TrueConf Server documentation on SIP<\/a> and H.323<\/a>. If you want to call devices using third-party protocols, your server should have a license for SIP\/H.323 gateway<\/a>.<\/p>\n The first part of our article focuses on how to call third-party SIP\/H.323 devices from TrueConf application for Windows. The second part is about how third-party devices can use these protocols to join conferences on TrueConf Server or call TrueConf users. For demonstration purposes, we are using Polycom RealPresence Desktop (a licensed version of this video conferencing application) and Bria Solo<\/a> (previously X-Lite) SIP softphone as SIP\/H.323 devices.<\/p>\n TrueConf users have a single call string format for third-party SIP\/H.323 devices:<\/p>\n Where:<\/p>\n The call method being described below determines how these parameters can be defined and when some of them can be omitted. By the way, the names of the supported protocols are not limited to To call SIP\/H.323 devices that are not registered with TrueConf Server by IP address, use Let\u2019s take a closer look at how to call Polycom application by IPv4 address.<\/p>\n Examples:<\/p>\n SIP:<\/b>\u00a0 H.323:\u00a0<\/b> In TrueConf application window,\u00a0 use the search field to enter the call string in a relevant format and click on the handset button. You can also add this call string to yourx address book<\/a> as a new contact by clicking on the plus icon or include it in a scheduled conference <\/a>.<\/p>\n No additional settings are required. The gateway embedded into TrueConf Server will automatically reconcile the codecs being used, adjust available protocol extensions, and set up a connection. Resolution, video and audio quality will be dynamically adapted to fit the available channel width between a user, TrueConf Server, and a device being called. Therefore, you shouldn\u2019t worry about lost packets even if the gateway uses UDP most often.<\/p>\n TrueConf for Windows<\/p>\n TrueConf for Android<\/p>\n TrueConf for iOS<\/p>\n If you need to call a specific user, device, or virtual room on the remote server, PBX, or MCU, you should use the full format:<\/p>\n An account name, phone number, or H.323 device ID in E.164 format can be used as a username ( H.323:<\/b><\/p>\n If you created SIP or H.323 rules for connections with Default SIP Proxy<\/strong>, Default VoIP Server<\/strong>, or Default H.323 Gatekeeper<\/strong> roles on TrueConf Server, you are not required to explicitly include the server in the call string. In this case, the format is as follows:<\/p>\n Learn more about differences between these roles and how to assign them in our article about default servers<\/a>.<\/p>\n Many SIP\/H.323 devices can log on to a third-party server or gatekeeper and become accessible by their account names. This is often used to obviate the need for entering the device\u2019s IP address before each call session.<\/p>\n Our TrueConf Server can be used as a mentioned server to allow you to call SIP\/H.323 devices as a regular TrueConf user. Authorized TrueConf users can be invited to SIP\/H.323 conferences from outside. To that end, use the following format in SIP\/H.323 devices:<\/p>\n Where: The address of TrueConf Server gateway can be found out in the Gateways<\/strong> \u2192 SIP<\/strong><\/a>\u00a0and Gateways<\/strong> \u2192 H.323<\/strong><\/a> section in the control panel.<\/p>\n Example:\u00a0 To make a call to a running conference on TrueConf Server from a SIP\/H.323 device, you need to know CID<\/b>, a conference ID <\/a>. A conference ID can be found in the TrueConf Server control panel only for scheduled conferences.<\/p>\n Similarly to the previous section, it is just enough to call up the following string on SIP\/H.323 endpoint to join the conference:<\/p>\n Where:<\/p>\n Additionally, to make a call via SIP, you can explicitly specify the protocol name (UDP is used by default).<\/p>\n To join a PIN-protected conference from an SIP\/H.323 endpoint, it is necessary to add PIN, separated by a comma after the conference ID in the call string:<\/p>\n Yes, when participating in a TrueConf conference via SIP, users can send DTMF commands with a remote control or keyboard. This feature is also available for H.323 devices<\/a>. During a role-based conference<\/a>, you can send the following DTMF commands:<\/p>\n Please note that you may have to activate this feature in the settings of your endpoint. To learn more, check the documentation for the specific device.<\/p>\n","protected":false},"excerpt":{"rendered":" You can use TrueConf applications to call SIP and H.323 devices. In this case, calls may vary in: Call string format Call method For a complete list of call formats, please see TrueConf Server documentation on SIP and H.323. If you want to call devices using third-party protocols, your server should have a license for […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[260],"tags":[189],"class_list":["post-12630","post","type-post","status-publish","format-standard","hentry","category-knowledge-base","tag-sip-and-h-323","wpautop"],"_links":{"self":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/12630","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/comments?post=12630"}],"version-history":[{"count":31,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/12630\/revisions"}],"predecessor-version":[{"id":25868,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/12630\/revisions\/25868"}],"wp:attachment":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/media?parent=12630"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/categories?post=12630"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/tags?post=12630"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}How to Call SIP\/H.323 Devices<\/h2>\n
#sip:<user>@<server>:<port>;transport=<protocol><\/code><\/p>\n#h323:<user>@<server><\/code><\/p>\n<sip|h323><\/code>is a protocol name being used.<\/p>\n<user><\/code> is a username on the server.<\/p>\n<server><\/code> is a server address or name.<\/p>\n<port><\/code> (optional parameter) is a server port where you send a call.<\/p>\n<protocol><\/code> (optional parameter) is a communication protocol \u2014 TCP <\/a> or UDP <\/a>.<\/p>\n#sip<\/code> (for SIP) and #h323<\/code> (for H.323), as we have #rtsp<\/code> prefix used to call IP cameras <\/a> and connect to streams via RTSP.<\/p>\nCalling Devices by IP Address<\/h3>\n
#<sip|h323>:@<IP><\/code>, where <IP><\/code> is IPv4\/IPv6 address or DNS name of a device. Make sure that this device can field calls via the protocol of your choice.<\/p>\n#sip:@192.168.21.114;protocol=TCP<\/code><\/p>\n#h323:@192.168.21.114<\/code><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/en-1.png\" "\\"\\"")
<\/a><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/en-2.png\" "\\"\\"")
<\/a><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/en-3.png\" "\\"\\"")
<\/a><\/p>\nCalling Users by IP Address and Username<\/h3>\n
#<sip|h323>:<user>@<IP><\/code><\/p>\n<user><\/code>). Let\u2019s delve into a few examples.
\nSIP:<\/b><\/p>\n#sip:john@company.com<\/code><\/p>\n#sip:8000@mcu.company.com:8888<\/code><\/p>\n#sip:101@pbx.company.com<\/code><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/en-4.png\" "\\"\\"")
<\/a><\/p>\n#h323:hdx8000@192.168.1.2<\/code><\/p>\n#h323:8000@mcu.company.com<\/code><\/p>\n#h323:\\e\\84951234567<\/code><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/en-5.png\" "\\"\\"")
<\/a><\/p>\nCalling Devices via the Default Server<\/h3>\n
#<sip|h323>:<user><\/code><\/p>\nDevices Registered with TrueConf Server<\/h3>\n
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/rpd_sip_en-690x334.png\" "\\"\\"")
<\/a><\/p>\n
\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/en-6.png\" "\\"\\"")
<\/a><\/p>\nHow to Call TrueConf Users and Join TrueConf Conferences from SIP\/H.323 Devices<\/h2>\n
Inviting TrueConf Users to SIP\/H.323 Conferences<\/h3>\n
<user>@<trueconf_server><\/code><\/p>\n
\n<user><\/code> is a name of a TrueConf user you want to invite.<\/p>\n<trueconf_server><\/code> is one of the external addresses of TrueConf Server SIP\/H.323 gateway.<\/p>\njohn@192.168.21.114<\/code><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/rpd_call_en-1024x496.png\" "\\"\\"")
<\/a><\/p>\nJoining TrueConf Server Conferences from SIP\/H.323 Devices<\/h3>\n
00<conf_id>@<trueconf_server>:<port>;transport=<protocol><\/code><\/p>\n00<\/code> is two zeros.<\/p>\n<conf_id><\/code> is a part of CID after \\c\\<\/code> prefix.<\/p>\n<trueconf_server><\/code> is an address of TrueConf Server gateway.<\/p>\n<port><\/code> \u2013 connection port (if it is different from the standard 5060<\/b> for SIP and 1720<\/b> for H.323).<\/p>\n00<conf_id>@<trueconf_server>:<port>;transport=<protocol><\/code><\/p>\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2019\/08\/rpd_conf_en-1024x495.png\" "\\"\\"")
<\/a><\/p>\n00<conf_id>,pin@<trueconf_server>:<port>;transport=<protocol><\/code><\/p>\n<trueconf_server>##00<user><\/code><\/p>\n<trueconf_server>##00<conf_id><\/code><\/p>\n<\/div>\nDoes TrueConf support tone dialing (DTMF) for SIP endpoints?<\/h2>\n
\n
1<\/code> \u2013 request the podium<\/li>\n2<\/code> \u2013 leave the podium.<\/li>\n<\/ul>\n