Setting up OneAgentWeb

OneAgentWeb is a server-installed, browser-based application designed for Microsoft Internet Explorer and Chrome. Some features may not work at their best on other browsers.

Its major components interconnect as follows:

 

 

 

To run OneAgentWeb, check the topics below and act accordingly.

Note: The topics under Setting up OneAgentWeb are meant for supervisors, system administrators or IT personnel ONLY.

 

Requirements

Running OneAgentWeb requires:

  • Microsoft Internet Explorer (with Temasys WebRTC Plugin) or Google Chrome 
  • (32-bit) Java, if screen recording is necessary.
    Note: screen recording is not supported on Chrome as of version 45
  • setting up Microsoft Windows Sound.

Handling interactions requires a microphone/loudspeaker set.
Depending on what your supervisor set up for you, they'll be made available by either:

  • a softphone (Collab's OnePhone, X-Lite, etc.)
  • a hardphone, registered on OneContact's proxy, with the same extension as the one assigned to you (Cisco, Yealink, etc.).
  • the browser itself.
    On Chrome, you must authorize camera and microphone usage
    every time you log in:



    On Internet Explorer:



Windows Sound 

Microsoft Windows sound devices must be set up.
Proceed as follows:

  1. in Windows, open Control Panel > Sound > Playback and select the Default Device:



  2. click Recording and select the Default Device:

 

 

Bandwidth

OneAgentWeb requires minimum bandwidth for both Audio and Video. Please verify if your connection meet this requirements:

Audio

For audio communications the required bandwidth is the following:

 

Application

Signalling

Media

Total

Tunneling

4,1 kbps

284 kbps

288,1 kbps

WebRTC UDP

4,1 kbps

786 bps

169 kbps

173,9 kbps

WebRTC SSL/TCP

4,1 kbps

1,3 kbps

209 kbps

214,4 kbps

SIP UDP with RTP

0

1,5 kbps

172 kbps (86 kbps in each direction) with G711 voice codec

173,5 kbps

 

Notes:

  • The current working standard is WebRTC SSL/TCP. You should only use one of the other options if you can't meet this requirements.
  • The WebRTC UDP must only be used if you have the necessary UDP ports available for audio.
  • All bandwidth values are full duplex.
  • QoS requirements for VoIP traffic depend on each manufacturer but we can consider good parameters, Maximum latency 180ms with packet lost less than 1% and Jitter less than 30ms.
  • When there's recording, since there's no media release, traffic doubles going through the server.

 

Video

 For video communications, the following bandwidth must be added:

  • Video over WebRTC with codec VP8:
    • Minimum bandwidth consumption 100kbps;
    • Maximum bandwidth consumption 2Mbps;
    • Resolution 720p a 30 frames per second (FPS): 1.0 a 2.0 Mbps;
    • Resolution 360p a 30 frames per second (FPS): 0.5 a 1.0 Mbps;
    • Resolution 180p a 30 frames per second (FPS): 0.1 a 0.5 Mbps.
Note: QoS requirements for VoIP traffic depend on each manufacturer but we can consider good parameters, Maximum latency 180ms with packet lost less than 1% and Jitter less than 30ms.

OneAgentWeb is a server-installed, browser-based application designed for Microsoft Internet Explorer and Chrome. Some features may not work at their best on other browsers.

Its major components interconnect as follows:

 

 

 

To run OneAgentWeb, check the topics below and act accordingly.

Note: The topics under Setting up OneAgentWeb are meant for supervisors, system administrators or IT personnel ONLY.

 

Requirements

Running OneAgentWeb requires:

  • Microsoft Internet Explorer (with Temasys WebRTC Plugin) or Google Chrome 
  • (32-bit) Java, if screen recording is necessary.
    Note: screen recording is not supported on Chrome as of version 45
  • setting up Microsoft Windows Sound.

Handling interactions requires a microphone/loudspeaker set.
Depending on what your supervisor set up for you, they'll be made available by either:

  • a softphone (Collab's OnePhone, X-Lite, etc.)
  • a hardphone, registered on OneContact's proxy, with the same extension as the one assigned to you (Cisco, Yealink, etc.).
  • the browser itself.
    On Chrome, you must authorize camera and microphone usage
    every time you log in:



    On Internet Explorer:



Windows Sound 

Microsoft Windows sound devices must be set up.
Proceed as follows:

  1. in Windows, open Control Panel > Sound > Playback and select the Default Device:



  2. click Recording and select the Default Device:

 

 

Bandwidth

OneAgentWeb requires minimum bandwidth for both Audio and Video. Please verify if your connection meet this requirements:

Audio

For audio communications the required bandwidth is the following:

 

Application

Signalling

Media

Total

 

 Downstream

Upstream

 Downstream

Upstream

 Downstream

Upstream

Downstream

Upstream

WebRTC UDP

2,05 kbps

2,05 kbps

393 bps

393 bps

84,5 kbps

84,5 kbps 

86,95 kbps

86,95 kbps

WebRTC SSLTCP

2,05 kbps

2,05 kbps

650 bps

 650 bps

104,5 kbps

104,5 kbps 

107,2 kbps

107,2 kbps

SIP UDP with RTP

0

0

750 bps

750 bps

86 kbps (with G711 voice codec)

86 kbps (with G711 voice codec) 

86,75 kbps

86,75 kbps

  

Notes:

  • The current working standard is WebRTC SSL/TCP. You should only use one of the other options if you can't meet this requirements.
  • The WebRTC UDP must only be used if you have the necessary UDP ports available for audio.
  • All bandwidth values are full duplex.
  • QoS requirements for VoIP traffic depend on each manufacturer but we can consider good parameters, Maximum latency 180ms with packet lost less than 1% and Jitter less than 30ms.
  • When there's recording, since there's no media release, traffic doubles going through the server.

 

Video

 For video communications, the following bandwidth must be added:

  • Video over WebRTC with codec VP8:
    • Minimum bandwidth consumption 100kbps;
    • Maximum bandwidth consumption 2Mbps;
    • Resolution 720p a 30 frames per second (FPS): 1.0 a 2.0 Mbps;
    • Resolution 360p a 30 frames per second (FPS): 0.5 a 1.0 Mbps;
    • Resolution 180p a 30 frames per second (FPS): 0.1 a 0.5 Mbps.
Note: QoS requirements for VoIP traffic depend on each manufacturer but we can consider good parameters, Maximum latency 180ms with packet lost less than 1% and Jitter less than 30ms.