Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Web browser support

Voice for Browser is tested and validated for Google Chrome browser on Windows 10.

Network requirements.

When a Firewall is running rules “inside-to-outside”, traffic from Clients to Enreach data center needs to be allowed.

Please note the same also possible workstation level firewall solutions.

Destinations to data center

Destination ports

Description

80.88.187.64/26

443 (TCP)
16384-32768 (UDP)

HTTPS
STUN & RTP audio traffic

217.77.201.224/27

443 (TCP)
16384-32768 (UDP)

HTTPS
STUN & RTP audio traffic

Enreach server side never initiates connections towards Voice for Browser clients. If customer is using stateless firewall it must be ensured that return traffic from Enreach servers to originating source ports is passed through.

Quality of service

The connection between Voice for Browser and the Enreach data center is routed via public Internet. To ensure needed call quality make sure that the Internet connection of the client network has enough bandwidth. Under heavy load, prioritizing audio traffic (SRTP) is recommended. If priority queuing is used for audio traffic, enough bandwidth must be configured for the priority queue. DSCP marking should be done on network level devices. Workstation clients are not DSCP-marking RTP traffic .

The bandwidth requirement of one concurrent voice call is 100 kbps

  • No labels