Conversations
Calls in Conversations
Get started with calls

Get started with calls

This guide covers the prerequisites and technical requirements you need to know before implementing Calls in your Conversations contact center. Review these requirements carefully to ensure optimal call quality and performance.


Prerequisites

To start using the Calls channel properly, you need to fulfill a few prerequisites:

  1. Create a user
  2. Assign Conversations roles
  3. Configure your call center (choose at least one of the following):

Call features overview

Call featuresPhone calls WebRTC calls
Queues
Routing
Automatic agent assignment
Working hours
Waiting strategy
Recording
Make a call
Receive a call
Call wrap-up
VideoN/A
Screen shareN/A
Dialpad DTMF inputsN/A
Transfer calls
Hold

Technical requirements

Below you can find all the technical requirements you need to know before you start using the Conversations Call Center solution.

RequirementSpecification
Operating system64-bit (Windows, macOS, Linux, or Chrome OS)
RAM4 GB minimum (8 GB recommended)
ProcessorDual-core minimum
Bandwidth5 Mbps minimum for agents
Packet lossUnder 1%
LatencyLess than 150 ms one-way
BrowsersChrome, Firefox, Edge, Safari, Opera (5 most recent versions)

System requirements

Audio and video call quality can be very low and unsatisfactory if agents do not have the necessary computing power. Therefore, for a smooth experience, we recommend that the agents' computer has at least the following specifications:

  • 64-bit operating system
  • 4 GB RAM minimum (8 GB RAM recommended)
  • Dual-core processor

Operating systems

Conversations is a cloud-based application that runs in your web browser, so it can be used on any desktop operating system that supports a compatible browser, such as:

  • Windows
  • macOS
  • Linux
  • Chrome OS

Peripheral devices

To make or receive calls, agents need the following equipment:

  • Headphones or speakers
  • Microphone
  • A camera that your browser can recognize as a video device (for video calls)

Media link quality

It is also quite important that you have a solid internet connection for optimal media experience, considering latency and packet loss can negatively impact call quality.

  • Packet loss is under 1%
  • One-way latency less than 150 ms

Network topology variants

When calculating internet speed requirements, take the following into account:

  1. Where are the agents located?
  2. Do you have BYOC (Bring Your Own Carrier) or are you using Infobip voice connection?

The table below covers the audio portion only and assumes that offices use the same internet link for BYOC, SIP trunk to Infobip, and SIP trunk to telecom:

Agent locationTrunkRequired office bandwidth per callAgent home bandwidth
HomeIBN/A5 Mbit for conversations, after that approximately 50 kbps for audio
OfficeIB5 Mbit for conversations, after that approximately 50 kbps for audioN/A
OfficeBYOC2x100 Kbps for BYOC g711 audio (mandatory packet loss less than 1%)5 Mbit for conversations, after that approximately 50 kbps for audio
OfficeBYOC2x100 Kbps for BYOC g711 audio (mandatory packet loss less than 1%). 5 Mbit for conversations, after that approximately 50 kbps for agent audio.N/A

Data centers

Calls in Conversations are relayed to Infobip data centers. To minimize latency, use the nearest data center that matches your agents' physical location.

DCLocationInfo
FrankfurtEUFull solution
MumbaiIndiaFull solution
New YorkUSFull solution
Sao PaoloBrazilMedia only

Codecs in use

AudioVideo
OPUS, PCMVP8, H.264

Browser compatibility (web)

We support up to 5 most recent versions (unless otherwise indicated) of the most commonly used browsers:

 Google ChromeMozilla FirefoxSafari*Microsoft Edge**OperaInternet Explorer
LinuxN/AN/AN/A
MacOSN/A
WindowsN/AN/A

*WebRTC support in Safari started with version 11.

**WebRTC support in Microsoft Edge started with Chromium-based version 79. Only Chromium-based Microsoft Edge versions for Windows are supported for InfobipRTC.

Browser compatibility (mobile)

For mobile, we support the following browsers for WebRTC calls via call link:

 Google ChromeMozilla FirefoxSafari*Microsoft Edge**OperaInternet Explorer
AndroidN/AN/A
iOS***N/A

***WebRTC support in browsers other than Safari started with iOS version 14.3.

Note

Mobile browsers are not able to receive calls and maintain call connectivity in the background. We recommend using iOS (opens in a new tab) and Android (opens in a new tab) SDKs for creating mobile WebRTC applications.


Media stream requirements

It is worth noting that media streams are generally symmetric, meaning what you send is roughly equal to what you receive. However, exceptions may occur if the network link is asymmetric.

The initial download size of the Conversations web page is approximately 11 MB, which means the first load may be slow if bandwidth is limited. To ensure smooth and uninterrupted use of the Conversations web application, a minimum bandwidth of 5 Mbps is recommended for agents.

Additional bandwidth requirements by media stream type are outlined below:

Media typeDetailsRequired bandwidth
Standard audio qualityNarrowband to wideband50 Kbps
High audio qualityUp to fullband, stereo100 Kbps
Low-resolution video240x180180 Kbps
SD video640x480600 Kbps
HD video1280x7201500+ Kbps

Additional requirements

JavaScript has to be enabled. Also, you need to grant permission to use the microphone and camera (for video calls).


Agent requirements for receiving calls

To be able to receive calls, agents:

  • Must be in one of the statuses from the available status group
  • Must be assigned to the queue that the call is routed to (note that by default, calls are routed to the Default queue)

The queue that the call is routed to needs to have automatic agent assignment turned on. Calls cannot be manually assigned. By default, automatic agent assignment is turned off for all queues, including the Default queue.


Microphone and camera permissions

When an agent initiates or receives the call for the first time, they will be prompted (by a browser pop-up notification) to allow Conversations access to the device's microphone and camera. If the pop-ups are blocked, you will have to manually enable these settings.

If you have denied the permissions, the call will be rejected showing the following error: Permission to use camera and microphone denied.

Calls - Camera and microphone permissions
Tip

If you are experiencing permission issues, see the Troubleshoot calls guide for detailed instructions on enabling microphone and camera in different browsers.


Device settings

In their everyday work and while handling calls, agents need to be able to configure the desired input and output devices (camera, microphone, and speakers) quickly and effortlessly for both voice and video calls.

To do this, select your profile icon and choose the Audio and video settings option.

Calls - Audio and video settings

The device configuration that you create on the audio and video settings is sticky and will be preserved in the browser. You can choose one of the recognized devices from the drop-down lists for both audio and video input devices.

Here, you can confirm that the devices are functioning properly:

  • Click Test speakers to test the sound. The system will play music for 5 seconds.
  • Click Test microphone to test the microphone. The system will wait for the sound and animate the volume bar accordingly, showing that the microphone is working fine.

The video stream from the selected camera will be automatically shown in the preview window. If available, the devices that you select will be used for the new calls.

Calls - Audio and video setup

Voice numbers

Voice numbers are phone numbers with the capability to receive incoming calls. They can also be used as the Caller ID for outgoing calls.

To set up a Voice communication and receive incoming calls for your business needs, first, you must lease a Voice number from Infobip.

Refer to the Voice numbers section for detailed instructions.


Bring Your Own Carrier

Bring Your Own Carrier or BYOC is a feature that allows our customers to use our platform, regardless of who is the owner of the DID number and connection towards the operator.

This solution provides flexibility by defining SIP trunking between existing customer connection (voice provider) and Infobip platform.

Depending on the use case and client requirements we can provide both inbound and outbound configurations. For any clients that require enhanced security, we can set up additional encryption options: encryption per call or encryption of tunnels between two data centers.


Next steps

Now that you understand the technical requirements and have completed the prerequisites, you can:



Need assistance

Explore Infobip Tutorials

Encountering issues

Contact our support

What's new? Check out

Release Notes

Unsure about a term? See

Glossary
Service status

Copyright @ 2006-2026 Infobip ltd.

Service Terms & ConditionsPrivacy policyTerms of use