Configure ICP for WebRTC

To enable the ICP to receive WebRTC Anonymous calls, a SIP trunk must be configured between MBG and the call controller.

Configuring the MiVoice Business (3300 Controller) to Support SIP Trunks

Note: The following instructions describe how to set up a SIP trunk without security. Instructions that include the use of SSL certificates will be added in a later release.

To configure a MiVoice Business to support SIP trunking:

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

  2. Add licenses:
    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 (for example, 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.

Configuring the MiVoice 5000 to Support SIP Trunks

To configure a MiVoice 5000 to support SIP trunking, refer to the “Characteristics of a VoIP trunk group” procedure in the Mitel 5000 Gateways XD–XL–XS–500 and MiVoice 5000 Server Operating Manual.

Parent topic: WebRTC Implementation