# MBG WebRTC Settings

To initialize the audio connection for two-way audio in AWV Web Client, the Anonymous mode should be enabled and licenses of anonymous calls must be available in MBG WebRTC configuration. Click here on Two-way Web Audio for detailed information on two-way audio in AWV Web Client.

To view the settings of MBG WebRTC, refer to the following section in the Server Manager: Click Server Manager> MiVoice Border gateway > Teleworking > WebRTC.

Configure the following fields for MBG WebRTC Settings as follows.

- MBG Server Name - Enter the name of the MBG server
- MBG WebRTC Port - Enter the port number of WebRTC. The default value of MBG WebRTC port should be 5063.
- Web Server Shared Secret - This value should be same as the WebRTC value for MBG configuration
- SIP URI - Enter the SIP URI details from the MiVoice 5000 PBX configuration. Note that this field is case sensitive. This field is visible only when MiVoice 5000 is selected.

NOTE: The supported platforms for two-way audio are MiVoice Business and MiVoice 5000.

NOTE: The two-way audio on MX-One is supported only on Standalone MBG.

NOTE: The MBG WebRTC settings should be configured on AWV for the two-way audio to work.

NOTE: For two-way audio functionality, the AWV hunt group number of PBX should be configured under Dial-In Phone Number 1 field which is present in the system options of AWV admin portal.

## Resetting MBG WebRTC settings

In the MBG WebRTC page, when you click the Reset option, the following changes take place:

- All fields are cleared, except the MBG WebRTC Port value of 5063, which is saved.

#### To reset the MBG WebRTC settings

1. In the Server Manager page, under Application click on Audio, Web and Video Conferencing.

2. Click on the MBG WebRTC Settings.

3. In MBG WebRTC Settings page , click on the Reset button.

A warning message is displayed, which states that resetting will restart the call server, resulting in the loss of all the current calls.

4. Click OK to confirm or click Cancel to terminate the task.

Scenarios for AWV Web Client errors:

Sl No | AWV WebClient Error Messages Reported by User | Possible correction steps for Admin/User
1 | Failed to reach MBG audio gateway. Please check your network connection and try again. If problem persists, contact the administrator. | The user should check the network connection, which should be in working condition and stable. MBG FQDN and PORT should be accessible from the user's system The administrator should check if the MBG FQDN and PORT configured in MBG WebRTC settings are correct.
2 | MBG audio gateway authentication has failed, please contact the administrator. | The Web Server shared secret provided in MBG WebRTC Settings isn’t valid. To retrieve the currently used Webserver shared secret key, go to Admin Portal>MBG>Teleworking>WebRTC>Download SDK. Extract the downloaded file, open config.php file, look for $websocket_passphrase entry. The value against it is the secret key. Use this key for configuring MBG WebRTC in AWV. Admin can set a new secret key in Admin Portal>MBG>Teleworking>WebRTC, and use that in MBG WebRTC in AWV.
3 | Failed to establish connection with MBG audio gateway. Please try again. If problem persists, contact the administrator. | In case of this error, the user should download the Web Client logs from, More > Web Client Logs, and share it with the support team.
4 | An error occurred while joining the audio. Please refresh your browser and try again. If problem persists, contact administrator. | If refreshing the browser doesn't resolve the issue then Web Client logs should be downloaded from, More > Web Client Logs, and shared with the support team.
5 | No audio device detected on system. Please check your system audio settings and try again. | User needs to attach an audio device to the system and recheck. If audio device is already attached to the system, then user needs to check and configure it in System Audio Setting.
6 | User reports about audio getting silent in an on-going call | User needs to reconnect the audio call. If that doesn't work then refresh the Web Client. If the user is continuously facing this issue, the AWV Web client logs should be collected and shared with the support team.

To know more about on how to configure WebRTC on MBG and configure ICP for WebRTC, see Configure ICP for WebRTC and Configure MBG for WebRTC.

Refer the MiCollab Engineering Guidelines for MBG hardware resource requirement for supporting WebRTC Audio Calls in AWV.