Skip to main content
Skip table of contents

WebRTC Channel Configuration Guide


Features

Description

WebRTC Video Support in Customer widget via Secure link

https://expertflow-docs.atlassian.net/wiki/spaces/CX/pages/89948451/4.5+Customer+Widget+Admin+Guide#WebRTC-Video-Call-Support-via-Secure-Link

The WebRTC Video Call feature via secure link enhances the customer widget by allowing standalone video calls without relying on the chat features. This is facilitated through secure link and token authentication, ensuring privacy and security. The feature is activated based on a specific secure link and session code generated by the agent during an active chat with the customer on any chat channel, The Generated Link will be valid for the next 30 minutes allowing the customer to rejoin if mistaken disconnect any active video call session. Once the secure link expires, will through Session Expired error on the screen.

image-20240222-081333.png

Secure Link APIs Deployment:

Customer Widget Deployment Steps:

In Expertflow CX Deployment:

  1. Navigate to the ConfigMaps folder and open ef-customer-widget-configmap.yaml file.

  2. Add a new config with the following names:

    1. AUTHENTICATOR_URL : https://<FQDN>/secure-link → FQDN of a secure link verification API to verify session code.

      image-20240222-075343.png
  3. Run the following commands to update the configMaps of the customer widget

    CODE
    kubectl delete -f ef-customer-widget-configmaps.yaml -n expertflow
    CODE
    kubectl delete -f ef-customer-widget-configmaps.yaml -n expertflow
  4. Navigate to the Deployments folder and open ef-customer-widget-deployment.yaml file.

  5. Map three new configs in deployment file as shown in the screenshot:

  6. Update the Image Tag to latest

image-20240222-075741.png

  1. Run the following commands to update the deployment container of the customer widget

    CODE
    kubectl delete -f ef-customer-widget-deployment.yaml -n expertflow
    CODE
    kubectl delete -f ef-customer-widget-deployment.yaml -n expertflow

Unified Agent:

In Expertflow CX Deployment:

  1. Navigate to the ConfigMaps folder and open ef-unified-agent-configmap.yaml file.

  2. Add a new config with the following name:

    1. SECURE_LINK_URL : https://<FQDN>/secure-link → FQDN of a secure link generation API with session code to push to customer active channel.

image-20240222-081142.png

  1. Run the following commands to update the configMaps of the unified-agent

    CODE
    kubectl delete -f ef-unified-agent-configmaps.yaml -n expertflow
    CODE
    tkubectl delete -f ef-unified-agent-configmaps.yaml -n expertflow
  2. Navigate to the Deployments folder and open ef-customer-widget-deployment.yaml file.

  3. Map three new configs in the deployment file as shown in the screenshot:

  4. Update the Image Tag to the latest

image-20240222-084451.png

  1. Run the following commands to update the deployment container of the unified-agent

    CODE
    kubectl delete -f ef-unified-agent-deployment.yaml -n expertflow
    CODE
    kubectl delete -f ef-unified-agent-deployment.yaml -n expertflow

EFSwitch

Configure SIP Trunk for outbound calls

  • Open in browser: https://IP-addr, where IP-addr is the IP address of the server that EFSwitch is deployed on. 

  • Add the username and password that was shown upon installation of EFSwitch and press LOGIN.

  • Press the IP address in the top right and select the Domain created in the Domain creation section of the EFSwitch configuration document.

  • Open the Gateways section under the Accounts tab.

    image-20240222-095737.png
  • Press the ADD button in the top right.

    image-20240222-095900.png
  • Set the following fields:

    1. Gateway: A name of your choice e.g. MySipTrunk

    2. Username: The username of the SIP Trunk. Not needed for IP-based SIP trunks.

    3. Password: The password of the SIP Trunk. Not needed for IP-based SIP trunks.

    4. Proxy: The IP address and port of the SIP trunk e.g. 192.168.25.35:5060.

    5. Register: Set to True. Set to False for IP-based SIP trunks.

  • image-20240222-100014.png
  • Press the SAVE button on the top right.

  • Open this newly created gateway and note the URL opened in the browser.

    image-20240222-110233.png
  • From this URL note the gateway ID , i.e. :

  • Add the IP address of the SIP trunk to the EFSwitch ACL:

    • Open SIP Profiles under the Advanced tab.

      image-20240222-100519.png
    • Open the external profile and note the value of the apply-register-acl field.

      image-20240222-100419.png
    • Open Access controls under the Advanced tab.

      image-20240222-100249.png
    • Open the entry that matches the aforementioned apply-register-acl field.

      image-20240222-100648.png

    • At the bottom add an entry where the the Type is set to ‘allow’ and the CIDR field contains the address of the SIP Trunk.

    • Press the SAVE button on the top right.

    • Open SIP Status under the Status tab.

      image-20240222-100938.png
    • Press the Reload ACL button at the top right.

  • Open SIP Profiles under the Advanced tab.

    image-20240222-100519.png
  • Open the external profile and note the value of the sip-port field.

  • Back out via the BACK button on the top right.

  • Open the internal profile and note the value of the sip-port field.

  • Open a terminal and SSH into the EFSwitch machine via the command

    CODE
    ssh EFSwitch-Server-Username@EFSwitch-Server-IP-Address
  • Enter the EFSwitch server SSH password when prompted.

  • Enter and run the command

    CODE
    su
  • And enter the EFSwitch server root password.

  • Run the command

    CODE
    sudo iptables -A INPUT -p tcp -m tcp --dport PORT -j ACCEPT
    • Where PORT is the port noted down in the previous steps. Run the command once for each port.

  • Run the command

    CODE
    sudo iptables-save
  • Contact the SIP Trunk provider and have all traffic from the EFSwitch machine public IP address allowed.

Configuring Call Dialplan

  • Open Unified Admin via the link https://CX-FQDN/unified-admin

    • Where CX-FQDN is the fully qualified domain name of the EF CX.

  • Open the Web Widget section.

    image-20240222-102658.png

  • Open the Widget created for video calling, via the Edit option.

    image-20240222-105659.png
  • Scroll down and note the value of the Dialing URI field.

  • Open in browser: https://IP-addr, where IP-addr is the IP address of the server that EFSwitch is deployed on. 

  • Add the username and password that was shown upon installation of EFSwitch and press LOGIN.

  • Press the IP address in the top right and select the Domain created in the Domain creation section of the EFSwitch configuration document.

  • Open the Dialplan Manager section under the Dialplans tab.

    image-20240222-102113.png
  • Press the ADD button in the top right.

    image-20240222-102222.png
  • Fill the form with following details :

    • Name = WebRTC Video Call

    • Condition 1 =  Select destination_number from list and set the value to the value of the Dialing URI noted in the previous steps.

    • Action 1  =  Select first item from the list  

  • Press the SAVE button on top right Corner.

  • Re-open the WebRTC Video Call dialplan.

  • Set the Context field to the value of the Domain set in the Domain creation section of the EFSwitch configuration document.

  • Set the Domain field to the value of the Domain set in the Domain creation section of the EFSwitch configuration document.

  • Change the value of the Type column in the Action row to bridge and the Data field to sofia/gateway/GATEWAY-ID/55${sip_h_X-Agent-Extension}@DOMAIN

    • Where GATEWAY-ID is the SIP Trunk gateway ID noted in the previous section.

    • And DOMAIN is the value of the Domain set in the Domain creation section.

  • Press the SAVE button on top right Corner.

CX 4.5.1 Limitations

Expand To View Limitations

Release Limitations

Customer Widget Environment:

  • Video Call Dev-Tested on Android

  • Video Call Dev-Tested only on Iphone 12+ devices

  • Video Call Dev-tested on windows 10, 11’s Chrome, Edge and Firefox

QCOPS-34

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.