Connecting to a conference via web client: различия между версиями
Alina (обсуждение | вклад) (Новая страница: «Connection to a conference via a web client is possible through the account's personal account (hereinafter PA) or bypassing the personal account directly through...») |
Alina (обсуждение | вклад) |
||
| (не показаны 3 промежуточные версии этого же участника) | |||
| Строка 4: | Строка 4: | ||
== Connect directly via web client == | == Connect directly via web client == | ||
| + | |||
| + | The user can access the web client from the main authorization page or via a link received from the conference moderator. | ||
| + | [[Файл:MFWC 14.jpg|800px|безрамки|центр|MFWC 14]] | ||
| + | With this connection way you can only log in as a WS account or connect unauthorized as anonymous. | ||
| + | |||
| + | When connecting as anonymous the use of authentication data (account number and password) is not required; you must specify a display name. | ||
| + | [[Файл:MFWC 15.jpg|800px|безрамки|центр|MFWC 15]] | ||
| + | |||
| + | == Connection via personal account == | ||
| + | |||
| + | An account of any type can connect via a web client to a conference to which he has been added as a participant after logging into his personal account and following the link from the “Connect to the conference” widget. In this case the web client will not request authentication data and the connection will be made on behalf of the account who logged into the PA. | ||
| + | |||
| + | Connection is also possible from the sidebar of menu. | ||
| + | |||
| + | If the conference is closed you can become a participant only after entering a PIN code or waiting for a moderator connect you to a conference. | ||
| + | |||
| + | Pay attention! Conference PIN cannot start with 0. | ||
| + | |||
| + | Connections via the link in the widget and in the side menu are available if you enter the login (account number) and password on the main page for accounts of any type (WS, SIP, Loop or H.323) but only to the conference of which they are participants. | ||
| + | |||
| + | Note: if a participant attempts to log into the web client as an anonymous user but has previously entered their authorization data on the main page the system will recognize them as an authorized participant (account). | ||
Текущая версия на 14:53, 15 августа 2024
Connection to a conference via a web client is possible through the account's personal account (hereinafter PA) or bypassing the personal account directly through the web client.
Each of the ways has conditions and limitations which we will consider below. It is worth noting that the web client can only make an incoming call to the server since it is impossible to call an account from the server who will be connected via the web client. The logic of incoming call routing is described in this article.
Connect directly via web client
The user can access the web client from the main authorization page or via a link received from the conference moderator.
With this connection way you can only log in as a WS account or connect unauthorized as anonymous.
When connecting as anonymous the use of authentication data (account number and password) is not required; you must specify a display name.
Connection via personal account
An account of any type can connect via a web client to a conference to which he has been added as a participant after logging into his personal account and following the link from the “Connect to the conference” widget. In this case the web client will not request authentication data and the connection will be made on behalf of the account who logged into the PA.
Connection is also possible from the sidebar of menu.
If the conference is closed you can become a participant only after entering a PIN code or waiting for a moderator connect you to a conference.
Pay attention! Conference PIN cannot start with 0.
Connections via the link in the widget and in the side menu are available if you enter the login (account number) and password on the main page for accounts of any type (WS, SIP, Loop or H.323) but only to the conference of which they are participants.
Note: if a participant attempts to log into the web client as an anonymous user but has previously entered their authorization data on the main page the system will recognize them as an authorized participant (account).
