Registration mode on a third-party SIP server using REGISTER request:
off - REGISTER request cannot be sent, au-thorisation is performed during a call;
permanent - automatic authorisation on each server's launch, available untill the server
shutdown;
before call - REGISTER request is sent di-rectly before a call and is supported during a call only.
Status of the connection to the SIP server
connected - connection with the SIP/VoIP server has been established;
wrong authorization - authrization error (wrong login or password);
invalid server - incorrectly specified SIP/VoiP server.
3.2.3.1. SIP-terminal calling format from TrueConf Client
One of the formats given below can be used:
#sip:Call_ID@Server_name, where Call_ID is SIP user, Server_name is a host name or IP address
of the SIP server;
#sip:Call_ID, call is directed to the Call_ID user on the server, which is indicated in the VoIP
Server/SIP Proxy of the SIP Gateway tab;
#sip:@IP, call to the IP address of the SIP terminal.
#sip:@hostname, call to the DNS name of the SIP terminal.
Call routing Value
Via VoIP
Calls are redirected to phone numbers
(#tel:89261112233)
Via SIP Proxy Calls are redirected to user’s Call_ID (#sip:james78)
3.2.3.2. Invitation of TrueConf customer to the conference that is held on the SIP server.
login to the client application TrueConf Client;
organize conference on the SIP server (MCU), invite terminals to the conference;
add to the conference TrueConf ID you used to login to the client application TrueConf Client, as
TrueConf_ID@IP, where IP – gateway address of the TrueConf Server, which is indicated in the SIP
Gateway tab:
3.2.3.3. Invitation of the SIP terminal to the conference that is held on the TrueConf Server.
There are two ways ot inviting a SIP endpoint into a video conference - from Address book of TrueConf
Client application or from TrueConf Web Manager.
1. From Address Book in TrueConf Client application. Do the following:
To Next Page
Loading...