...
The following traffic should be allowed from clients to Enreach Services:
Enreach DataCenter addresses |
|---|
80.88.187.64/26 |
217.77.201.224/27 |
Destination | Destination port | Description |
|---|---|---|
Enreach DataCenter (80.88.187.64/26) | 443 (TCP) | HTTPS for Voice Center and BeneAPI |
Enreach DataCenter (80.88.187.64/26) | 5060-5070 (TCP & UDP) | SIP Signalling |
Enreach DataCenter (80.88.187.64/26) | 16384-32768 (UDP) | RTP audio traffic |
Workstation Firewalls
During the installation, required firewall rules are created to the Windows Firewall. If there is a third-party firewall installed, the following rules should be created for Voice for Windows:
Default program path | C:\Program Files (x86)\BeneDesk for Windows\BeneDesk.exe |
Inbound port | all ports TCP and UDP |
Outbound ports | all ports TCP and UDP |
Quality of Service
By default, the connection between Voice for Windows and the Enreach data center is routed via public Internet. To ensure sufficient call quality make sure that the Internet connection of the client network has sufficient bandwidth. Under heavy load, prioritizing audio traffic of Voice for Windows (SRTP) is recommended.
...
Audio traffic (RTP packets) are not marked with DSCP by Voice for Windows. Classification and marking of voice traffic should be done in network. If priority queueing queuing is used for audio traffic, enough bandwidth must be configured for the priority queue. The bandwidth requirement of one concurrent voice call is 100 kbps.