# Two-Way Audio Settings

## About MiCollab AWV Two-Way Audio

As a MiCollab user in Audio, Web and Video conference (AWV), with the introduction of the feature of two-way audio mode, the user can use the AWV web client for two-way audio functionality, similar to an AWV desktop client.

This topic provides instructions on how to integrate and configure the two-way audio feature with the supported PBXs.

## Two-Way Audio Integration

The user will see the two-way audio option in AWV web client if the feature is configured on the MiCollab server and if the WebRTC supported browsers and operating systems are used.AWV web client uses MiVoice Border Gateway (MBG) anonymous call WebRTC capability.

Two-way audio integration with MiCollab is a three-step process:

- AWV Configuration

- MBG Configuration

- PBX Configuration

Note: The supported platforms for two-way audio are MiVoice Business, MiVoice 5000, and MX-One.
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: MBG should be provisioned with an additional RAM and CPU for proper functioning of two-way audio WebRTC calls. For more information on memory and CPU usage, see MiCollab Engineering Guidelines > MiVoice Border Gateway Guidelines section.

## Requirements for Two-Way Audio from the Web Client

Component | Requirement
Mobile Device Operating System | Android (Mobile/Tablets)
Web Browser | Mozilla Firefox® Standard Release 43 or higher Google Chrome™ 47 or higher
Operating System | Windows 7,8 and 10 Mac™
Devices | Surface Pro

## To Enable Two-Way Audio

## 1. AWV Configuration

Configure the following fields for MBG WebRTC Settings under Server Manager > Audio, Web and Video Conferencing > Configuration > Two-Way Audio Settings.

- 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 is 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 AWV hunt group number of PBX must be configured under the Dial-In Phone Number 1 field which is present in the system options of the AWV admin portal. If that value does not match the MiVB AWV Hunt Group Number, MBG will be unable to connect with audio.

To view and update the MBG WebRTC settings, see Server Manager > MiVoice Border Gateway > Teleworking > WebRTC.

## 2. MBG Configuration

1. Log in to MiCollab Server Manager and navigate to MiVoice Border Gateway >Teleworking >WebRTC.

2. Select the Enabled checkbox to enable the WebRTC Service.

3. Under Licenses, make sure you have active Anonymous calls licenses. If this value is “0” then purchase the following license from AMC and sync MiCollab licenses.

   “MBG: 1 SIP Trunking Channel License”.

   Note: Purchasing 1 SIP Trunking Channel License will allow you only one 2-way audio connection. You will need to buy enough licenses to meet your expected usage.

4. Change the Hosting mode to anonymous and subscriber.

5. Configure the Webserver shared secret password.

6. Click Save

For detailed description of WebRTC settings, see Configuration > WebRTC section in the MBG online help document.

## 3. PBX Configuration

The SIP trunking configurations on different PBX is explained in below sections:
Note: Make sure SIP trunk is established between MBG and the PBX, and anonymous call is allowed in the PBX.

MiVoice Business Configuration

1. In the MiVoice Business System Administration Tool, click View by Category.

2. Add licenses using the following procedure:

   1. Access the License and Options Selection form.

   2. Under Trunking Networking, enter the number of SIP Trunk licenses for your implementation. This is the maximum number of concurrent trunk sessions that can be configured.

3. Configure a network element for MBG:

   1. Access the Network Elements form and add a new entry.

   2. Configure the following fields:

      Field | Description
      Name | Enter a unique name of up to nine characters for the network element (e.g. WebRTC).
      Type | Select Other.
      FQDN or IP Address | Enter the LAN IP address of MBG, provided that MBG is operating in Server-Gateway mode.

   3. Record the network element Name. You will require it in step 5, below.

   4. Select the SIP Peer check box and configure the following fields:

      Field | Description
      SIP Peer Transport | Select UDP
      SIP Peer Port | Enter 5064
      SIP Peer Status | Select Always Active

   5. Click Save.

4. Configure the SIP trunk attributes:

   1. Access the Trunk Attributes form and select a trunk service number that is available to be changed.

   2. Configure the following fields:

      Field | Description
      Non-Dial-In Trunks Answer Point - Day | Enter the destination number (answer point) to which incoming WebRTC trunk calls are routed during the Day service. This can be a station, hunt group pilot number, DISA number, or System Speed call number on the ICP.
      Non-Dial-In Trunks Answer Point - Night 1 | Enter the same value as specified above.
      Non-Dial-In Trunks Answer Point - Night 2 | Enter the same value as specified above.
      Trunk Label | (Optional) Enter the character string to identify the trunk.
      Note: For anonymous mode WebRTC calls, the trunk must use the same answer point for each mode of service.

   3. Click Save.

   4. Record the Trunk Service Number that you have modified. You will require it in the next step.

5. Configure the SIP peer profile.

   1. Access the SIP Peer Profile form and add a new entry.

   2. Configure the following fields:

      Field | Description
      SIP Peer Profile Label | Enter the name of the network element (e.g. WebRTC).
      Network Element | Select the network element that you created for the MBG
      Address Type | Select IP Address
      Trunk Service | Enter the SIP Trunk Service Number that you modified in the previous step.

   3. Click Save.

   4. Record the SIP Peer Profile Label. You will require it in the next step.

6. Configure the SIP Peer Profile Assignment by Incoming DID:

   1. Access the SIP Peer Profile Assignment by Incoming DID form and add a new entry.

   2. Configure the following fields:

      Field | Description
      Incoming DID Range | Enter the destination number (answer point) to which incoming WebRTC trunk calls are routed on the ICP.
      SIP Peer Profile Label | Select the SIP Peer Profile Label that you added in the previous step.

   3. Click Save.

MiVoice 5000 Configuration

1. Log-in to the MVoice 5000, navigate to Dialing Plan > Direction names and configure the Associated direction.

   Enter the Private direction value in the textbox (for example, DIR_SIP).

2. Navigate to Dialing Plan > Plan for Internet links > Access to specific domains, enter the domain name or IP address under the Domain/IP Address 1 textbox (for example, mytest.com).
3. Navigate to the Trunk Group. In the Trunk group selection page, click on the Select the item button.
4. Select the following fields:
   1. - Signaling type as SIP.
   2. - Subtype as Internet Link.
5. Click the Characteristics button.
6. Enter the values as displayed in the screenshots below (for example, IP address: MBG’s IP) and then click the Advanced mode icon (on top of the page) to view and configure the settings.
7. Open the Hunt group page and enter the SIP URI details AWVHuntGroup@mytest.com) as shown below:

MiVoice MX-One Configuration
Note: The two-way audio on MX-One is supported only on Standalone MBG.

Run the below commands on MX-One server (using MDSH commands) for creating SIP trunking between MX-One and MBG. Fill MBG-IP, MX-One-IP, MBG’s FQDN, and RouteNo (any free Route) values in below mentioned commands:

set _ECHO=yes

sip_route -set -route RouteNo-profile 'MBG-anonymous-webRTC' -uristring0 'sip:?@MBG-IP' -uristring1 'sip:+?@MBG-IP' -remoteport '5064' -fromuri0 'sip:!?@Mxone-IP' -fromuri1 'sip:+!?@Mxone-IP' -accept FROM_DOMAIN -match 'MBG's FQDN' -challenge no

ROCAI:ROU=RouteNo,SEL=7110000000000010,SIG=0111110000A0,TRAF=03151515,TRM=4,SERV=3100001001,BCAP=001100;

RODAI:ROU=RouteNo,TYPE=TL66,VARI=00000000,VARC=00000000,VARO=00000000;

ROEQI:ROU=RouteNo,TRU=1-1&&1-9;

set _ECHO=no

## To Disable Two-Way Audio in AWV

In the Two-Way Audio Settings page, when you click the Reset option, All fields are cleared, except the MBG WebRTC Port value of 5063, which is saved.

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

2. Click on the Two-Way Audio Settings.

3. In Two-Way Audio 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.

## Troubleshooting

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.

Parent topic: Configuration
↑