Versions Compared

Old Version 33

changes.mady.by.user Product Knowledge

Saved on

compared with

New Version 34

changes.mady.by.user Product Knowledge

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

ON THIS PAGE

Table of Contents
The XCALLY Motion 

On this page

Table of Contents
minLevel1
maxLevel2
outlinefalse
stylenone
typelist
printablefalse

📋 What’s About

The XCALLY Motion WebRTC Bar (Web Real Time Communication Bar) is ais a native application embedded in the Omni Desktop Interface, that .

The WebRTC can be used by the Contact Center Agents, who have been configured as WebRTC Agents in order to make it appear on the desktop interface header, to , and so able to manage incoming and outgoing calls.

info

It’s not possible to use webRTC as Users

If you need to enable your Agents to use the WebRTC feature, please contact the XCALLY Sales Team.

 Image Removed

Warning

It is impossible to use WebRTC as Users

(blue star) Requirements

You don't need to install any software on the Agent workstation, but you must have the meet the following requirements:

Panel
bgColor#EAE6FF

  • You must install a valid HTTPS certificate: you need a VALID SSL certificate provided by an official Certification authority (the use of a Self-Signed certificate is not enough and will not make the WebRTC working)

  • From Chrome Version 110.0.5481.78, it is required to configure the STUN Server on the XCALLY Networks Settings to use the WebRTC properly

  • The Agent PC has proper audio devices

  • You need a WebRTC specific license to make it work

  • If your Motion Server is behind NAT, remember to configure the STUN server

  • The Agent who logs in must be configured as WebRTC Typology

  • The Web Socket Service Port 8089 must be open on your server 

  • UDP: ports 10000 up to 20000 must be open

  • The Browser on the Agent Desktop must be: Opera, Chrome or Safari

  • OS must be one of the following:

OS:

  • MAC OS, MS Windows from 10 on, Linux OS,

 Chrome OS, Chromium OS

  • You must install a valid HTTPS certificate*  VERY IMPORTANT!!! (Please note that you need a VALID SSL certificate provided by an official Certification authority (the use of a Self-Signed certificate is not enough and will not make the WebRTC working).

    • Note

    WebRTC Urgent Update

    From Chrome Version 110.0.5481.78, it is required to configure the STUN Server on the XCALLY Networks Settings to make the WebRTC work properly.

    •  Chrome OS, Chromium OS

    (blue star) XCALLY Public STUN servers

    You have the opportunity to use our public STUN servers.

    Image Removed

    Image Added
    Info

    Please note, this service is public and free without any warranty or support.

    Note

    Stun server is necessary if you use Chrome

    Check which one is the nearest to your location:

    InfoPlease note this service is public and free without any warranty or support.

    To verify correct communication with the stun server, you must execute this command on root user:
    asterisk -rx "stun show status"

    If successful, the following message will be displayed:

    Panel
    bgColor#F4F5F7

    Hostname Port Period Retries Status ExternAddr ExternPort

    eu-stun.xenialab.com 15349 30 3 OK 35.178.170.143 43745

    WebRTC appears in this way:Image RemovedImage Removed

    This is how the WebRTC displays:

    Image Added
    Image Added

    To check if Agent's PC local requirements are met:

    1. Access into XCALLY from the WebRTC Agent PC

    2. Click on the Agentname: from the drop-down menu, select Settings

    3. Check the Requirements section:

    Image Added

    • If all of them are tagged with a green checkmark it means that , the local configuration is ok

    • If one or more of them are tagged with a red checkmark it means that , the corresponding requirement is not properly configured/working.

    Image Removed

    Image Removed

    🔧 Troubleshooting

    To check if ensure that you are using a compatible browser with WebRTC services, there are many tools are available. 
    You can for instance For example, you might use this tool to see if your browser is suitable or not for WebRTC use:
    WebRTC Troubleshooter

    Image Removedimage-20240404-101755.pngImage Added
    Image Removedimage-20240404-101836.pngImage Added

    🎧 Jabra USB Headphones

    This section is dedicated to Agents using Jabra USB Headphones on the WebRTC bar (only for MAC/Windows using Chrome).

    All professional Jabra headsets and Jabra speakerphones are supported. (i.e. Jabra Evolve series, Jabra Pro series, Jabra Biz series, and Jabra Speak series).

    Your Agents can use Jabra Headphones remote control to perform the actions usually executed clicking the WebRTC Bar buttons like: Accept, Hold, Hang-up, Volume up/down, Mute on/off.

    Image Removed

    In order to To configure this device, you have to do the following activities in sequence for all the PCs involved:

    1. Install a Driver on all the PCs used by the Agents that you can find in the following links:

      1. for MAC: https://github.com/gnaudio/jabra-browser-integration/raw/master/downloads/JabraChromeHost2.0.0.dmg

      2. for WINDOWS: https://github.com/gnaudio/jabra-browser-integration/raw/master/downloads/JabraChromeHost2.0.0.msi

    2. Install the Chrome extension: using  using the Browser Chrome, go to https://chrome.google.com/webstore/detail/jabra-browser-integration/okpeabepajdgiepelmhkfhkjlhhmofma?hl=en-US  and click on the button Add to Chrome 

    3. Go to the Settings of the WebRTC Bar:

     Image Removed
    1. image-20240404-102835.pngImage Added

    and

    1.  and choose the Jabra Device Audio equipment:

    Image Removed
    1. Image Added

    (blue star) Debugging in the browser

    Image Removedimage-20240404-103045.pngImage Added

    By default, WebRTC logs nothing to the browser console. In order to To enable debugging, run the following command in the browser console and reload the page:

    Code Block
    languagebash
    JsSIP.debug.enable('JsSIP:*');

    Note that the logging settings get stored into in the browser LocalStorage. To disable it, run the following command in the browser console and reload the page:

    Code Block
    languagebash
    JsSIP.debug.disable('JsSIP:*');
    Image Removed
    e04c898c-228b-4856-b56d-42951804a464-20240404-103148.jpgImage Added
    (blue star) Related topics
     Filter by label (Content by label)
    showLabelsfalse
    maxCheckboxfalse
    showSpacefalse
    reversefalse
    cqllabel = "webrtc"