As a MiCollab user in Audio, Web and Video conference, with the introduction of the feature of two-way audio mode, the user can use the AWV web client for two-way audio, similar to a desktop client.
The user will see the two-way audio option if the feature is configured on the server and if the supported browsers and operating systems are used, otherwise the listen-only mode will work.
When the audio participant joins a conference through two-way audio mode, the participant is shown as Anonymous to all clients (AWV Web Client, AWV PC Client, End User Portal and AWV reports).
NOTE: When a user tries to join the audio through the Audio, Web and Video Web Client UI, sometimes the AWV does not recognize the personal ID sent by the Web Client. In such scenarios the user should join the conference call by manually dialing the personal ID or access code using the keypad icon available on the AWV Web Client UI.
Requirements for two-way audio from the Web Client
Component |
Requirement |
Mobile Device Operating System |
|
Web Browser |
|
Operating System |
|
Devices |
|
NOTE: The two-way audio will work on the devices and browsers on which it is compatible and for rest of the browsers and devices which the AWV supports, the listen only mode will continue to work.
NOTE: Two-way audio mode is not supported over virtual platforms.
The configuration of two-way audio involves a few mandatory steps. To begin with, a SIP trunk is needed between MiCollab and the PBX.
When a WebRTC client connects to the MBG gateway, the WebRTC signalling and media translate into SIP signals and media, which in turn is delivered to PBX over a SIP trunk connection. From there it appears like any other SIP device making a call into AWV.
For configuration of SIP trunk between MiCollab and PBX for anonymous WebRTC calls, go to the help section of the server manager and then search WebRTC SIP and then click the first link. There you can configure two-way audio for MiVoice Business and MiVoice 5000.