Skip to end of metadata
Go to start of metadata

 

After installation, the WRTC node needs to be initialized. This section describes how to initialize a WRTC node with EMS and without EMS. This section includes the following topics:

 

Using WRTC Cluster Configuration on EMS (Cluster Mode Installation)

Sonus WebRTC Gateway is managed through Sonus Insight EMS server that helps in creating a Sonus WRTC configuration cluster. WRTC nodes then get registered to this WRTC cluster configured on the EMS to obtain the required configuration information. 

Perform the following steps to initialize the WRTC node by editing wrtcCloudInputs file:

  1. Create a WRTC cluster in EMS server, refer to the Configuring WRTC Using EMS for creating a WRTC cluster configuration in EMS. 
  2. Login to WRTC node instance as a linuxadmin user.

  3. Change to root user by executing su. For more information on accessing WRTC instance refer to Accessing WRTC Instance.

  4. Navigate to the following location:

    cd /opt/sonus/wrtc
  5. Enter the following command to copy the wrtcCloudInputs file contents:

    cp wrtcCloudInputs.cluster wrtcCloudInputs
  6. Open the wrtcCloudInputs file in vi editor and enter the following EMS related information:

    1. EMS username

    2. EMS IP

    3. EMS password

    4. EMS PrivateNodeParameters - cluster ID

      Where
      cluster_id is the cluster ID generated during cluster creation.

  7. Save and exit the wrtcCloudInputs file.

    1. If you are selecting two network interfaces (to separate SIP and Web traffic across the two) while installing WRTC Gateway then, you need to plumb the eth1 IP and edit the wrtcCloudInputs file as mentioned in the following sample configuration:

      EmsUsername="restuser"
      EmsIP="0.0.0.0"
      EmsPassword="sonus123"
      EmsPrivateNodeParameters="cluster_id=cloudwsx1,
      cluster_id=tt52o-7n4a1-18vo4-1teda,data_ip_address=10.54.8.76"
      Interface1="eth0"
      Interface1Usage2="HTTP"
      Interface1Usage1="WebSocket"
      Interface2="eth1"
      Interface2Usage1="SIP"
      SipIP="10.54.8.77" 

      In the preceding scenario, It is mandatory to provide SipIP to ensure the IP that must be used as eth1 IP address.

  8. Run the following command to register the WRTC node with EMS:

    ./wrtcnodeinit start

    In case of cloud deployment, if the WRTC node is not able to get registered with EMS successfully and displays an error you need to edit the wrtcCloudInputs file with the following:

    EmsUsername="<EMS_USERNAME>"
    EmsIP="0.0.0.0"
    EmsPassword="<EMS_PASSWORD>"
    EmsPrivateNodeParameters="vnfc_id=<VNFC_ID>,cluster_id=<VNF_ID>,data_ip_address=<FLOATING_IP_MGMT_EXTERNAL>"
    Interface1="eth0"
    WebIP="<FLOATING_IP_MGMT_EXTERNAL>"
    SipIP="<FLOATING_IP_MGMT_EXTERNAL>"
    DataIP="<127.0.0.1>"
    ManagementIP="<FLOATING_IP_MGMT_EXTERNAL>"
    Interface1Usage1="<SIP>"
    Interface1Usage2="<HTTP>"
    Interface1Usage3="<WebSocket>"

     

    For more information refer to the Deploying WRTC on OpenStack.

  9. After initializing the WRTC node you must login as wrtc user to start the WRTC server. For more information on starting and stopping WRTC server, see Starting and Stopping WRTC Server.

If you are integrating WRTC with EMS then you do not have to configure the startup.json file as the required information will be fetched from EMS.

Using WRTC Configuration With Onboard Configuration Management (Appliance Mode)

In Appliance mode of deployment, WRTC active and standby nodes are managed through Onboard Configuration Management.

Do not edit any other fields other than VirtualInterfaceIP and PeerWRTCAddress in the wrtcCloudInputs file.

Perform the following steps to initialize the WRTC node by editing wrtcCloudInputs file:

After initializing one WRTC node (active) initialize the other WRTC node (standby).

 

  1. Login to WRTC node instance as a linuxadmin user.

  2. Change to root user by executing su. For more information on accessing WRTC instance refer to Accessing WRTC Instance.

  3. Navigate to the following location:

    cd /opt/sonus/wrtc
  4. Enter the following command to copy the wrtcCloudInputs file contents:

    cp wrtcCloudInputs.appliance wrtcCloudInputs
  5. Open the wrtcCloudInputs file in vi editor and enter the IP address for VirtualInterfaceIP and PeerWRTCAddress fields.

    EmsUsername="restuser"
    EmsIP="0.0.0.0"
    EmsPassword="sonus123"
    EmsPrivateNodeParameters="vnfc_id=appliance,cluster_id=appliance,data_ip_address=0.0.0.0"
    Interface1="eth0"
    Interface1Usage1="SIP"
    Interface1Usage2="HTTP"
    Interface1Usage3="WebSocket"
    VirtualInterfaceIP="<Floaring_IP_Address>"
    PeerWRTCAddress="<IP_Address>"
    EmsRegistrationId="WRTC"
    RestUserName="restuser"
    RestPassword="sonus"

    Where,

    VirtualInterfaceIP is the floating IP of active and standby nodes.

    PeerWRTCAddress is the eth0 of the WRTC peer.

    • To configure WRTC in acticve-standby (HA) mode, generate SSH keys for Lsyncd. For information on generating SSH keys, see Sonus WebRTC Deployment in Appliance Mode.
    • WRTC in standalone mode does not require SSH key generation and Lsyncd configuration.
  6. Run the following command to initialize the active node:

    ./wrtcapplianceinit start
  7. After initializing the WRTC node you must login as wrtc user to start the WRTC server. For more information on starting and stopping WRTC server, see Starting and Stopping WRTC Server.

  8. Once the node configuration is complete, save the changes and push the configuration. For more information, refer to Configuring WRTC Through Onboard Management.