Network Best Practices

Updated 

Network configuration

Ensure you have enough bandwidth reserved to work with Sprinklr. Follow these points listed here:

  • A good rule of thumb is a 1 Mbps symmetrical connection per device.

  • For VoIP calling, the preferred network connectivity is ILL/MPLS/SDWAN/Direct connect/Express route.

  • Avoid having other people using/sharing your bandwidth while you are on a call, especially if it involves activities that consume a considerable amount of bandwidth, such as: 

- Streaming multimedia content (4K/HD/Full HD movies)

- Online gaming

- Downloading large content(such as torrents)

- Disable recordings on any DVD/Set-top boxes, as this consumes bandwidth.

- For Screen recordings requirement, ensure bandwidth is proportional to screen resolution.

- If you require big resolutions across multiple monitors(eg: 4k), the minimum requirements increases to ~2Mbps.

Sample Network Recommendations at Optimal way

Per Agent Minimum Bandwidth

500

Kbps

No Of Users

25


Total Bandwidth

12.5

Mpbs

Recommended bandwidth (30% more bandwidth than user bandwidth)

16.25

Mbps

Recommended Upstream

16.25

Mbps

Recommended Downstream

16.25

Mbps

Note:

  • The latency with the tunnel IP is below 120 ms.

  • Ensure no packet loss is incurred.

  • Real-time alerts on high bandwidth utilization or packet loss.

  • Sprinklr & WebRTC server bypassed from the firewall.

  • Browser is of the latest version.

  • Total bandwidth = No. of users * Per agent Minimum Bandwidth

  • Recommended bandwidth = Total Bandwidth *1.3

Ensure the above recommended bandwidth is present for both upstream and downstream note.

Connection best practices

Follow these guidelines regarding the type of connection:

  • Ethernet is the preferred connection type. Use a Cat5E cable, or above.

  • Set the following DNS servers (if possible):

    • Primary DNS: 8.8.8.8 

    • Secondary DNS: 1.1.1.1

  • Avoid using VPN (Virtual Private Network). If you do need to use a VPN, configure split tunneling in order to ensure that traffic from Sprinklr is routed directly to the internet instead of through the VPN.

Where possible, avoid running Sprinklr directly within Virtual Desktop Infrastructure (VDI) or Remote environments. Although practical from a systems administration perspective, virtual/remote desktop environments are still a suboptimal solution when it comes to real-time voice, and add complexity and latency to the real-time voice needs within the Sprinklr CX Cloud product. Successful usage of Sprinklr in a VDI environment requires tuning and additional testing by the customer's system administrator(s) / VDI provider(s).