...
Software requirements
Windows 10 and 11 are supported
.NET framework version 4.5.2 or above
BDfW Software installation requires Administrator privileges
Hardware requirements
Processor: 1 GHz
RAM: 512 MB
Disk space (minimum):
4,.5 GB for .NET installation, and for Voice for BDfWWindows
Application The application size on disk is 110 MB.
The selected Windows audio devices are used to handle the audio in a call. The used devices should be able to support professional sound.
Firewall configuration
When a Firewall is running rules “inside-to-outside”, traffic from Clients to Benemen Enreach Data Center needs to be allowed. If a router or firewall is SIP-aware or SIP ALG-enabled, this should be turned off. Following
The following traffic should be allowed from clients to Benemen 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 of BDfW, 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 BDfWWindows:
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 BeneDesk Voice for Windows and the Benemen 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 BDfW Voice for Windows (SRTP) is recommended.If priority queueing
In cases where dedicated data connection between the customer network and Enreach DataCenter is valid, separate traffic specification document should be created.
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 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.