Minimum Requirements
Infrastructure
Connectivity and Bandwidth Requirements
One-way latency (mouth to ear) no more than 150 ms
100 kbits UP/DOWN per concurrent voice call, plus web traffic bandwidth for the Daktela web interface (average is 100kbits DOWN for each active working agent)
Loss no more than 1 percent IP exchanges, VoIP networks
Average one-way jitter targeted at less than 30 ms
Optional: Voice traffic should be marked to DSCP EF per the QoS Baseline and RFC 3246
When using a firewall, the customer must configure and change it for the VoIP and data stream to allow communication between the on premise instance, its phones and the Daktela platform
Disabled SIP-ALG on LAN devices and firewall, as default. May be enabled in some specific cases.
Due to their complexity, Daktela doesn’t provide support for customer LAN infrastructure and firewalls!
Professional LAN network infrastructure based on min. full duplex 100 Mbit/s switches and of type CAT5e or better.
The network must not run at full capacity even during peak hours. Adequate capacity must be available for the anticipated voice traffic. It is ideal to separate and prioritise the telephony data, e.g. via VLAN.
Separate switches for IP phones and PCs are recommended for high volume data exchange over the local network.
IP phones must be assigned a valid IP configuration including internet gateway designated for voice traffic by means of a DHCP server.
Firewall
Customer uses SIP/SIPS/WebRTC phones to PBX in Daktela Cloud
allow established connections
outgoing 80/tcp, 443/tcp, 443/udp to IP list (web)
outgoing 5060/udp, 5060/tcp, 5061/tcp, 8089/tcp to IP list (sip)
outgoing 10000-20000/udp to IP list (rtp stream)
incoming - it depends on what kind of NAT they have (rtp stream)
UDP traffic is not bidirectional, so the following things must be ensured
>> allow UDP hole punching on FW/routerRFC5128 3.3
optionally allow incoming 10000-20000/udp from IP list (rtp stream)
outgoing 990/tcp, 44000-44100/tcp to IP list (FTPS cmd and data channel)
outgoing 636/tcp (LDAPS) to IP list - optionally enable it depending on whether it uses such a service
Customer uses SIP/SIPS/WebRTC phones to on-premise PBX
allow established connections
incoming 22/tcp (ssh) from 82.113.42.139, 95.80.200.192 to on-premise pbx
outgoing 10051/tcp (zabbix) from on-premise pbx to 82.113.42.131
outgoing 80/tcp, 443/tcp, 443/udp to IP list (web)
outgoing 5060/udp, 5060/tcp, 5061/tcp, 8089/tcp to IP list (sip)
incoming 5060/udp, 5060/tcp, 5061/tcp from IP list (sip)
outgoing 10000-20000/udp to IP list (rtp stream)
outgoing 80/tcp, 443/tcp, 443/udp from on-premise pbx to 95.80.209.239 (services - sms, social integrations)
incoming 80/tcp, 443/tcp, 443/udp from 95.80.209.239 to on-premise pbx (services callbacks - sms, social integrations)
incoming - it depends on what kind of NAT they have (rtp stream)
UDP traffic is not bidirectional, so the following things must be ensured
>> allow UDP hole punching on FW/routerRFC5128 3.3
optionally allow incoming 10000-20000/udp from IP list (rtp stream)
outgoing 990/tcp, 44000-44100/tcp to IP list (FTPS cmd and data channel)
outgoing 636/tcp (LDAPS) to IP list - optionally enable it depending on whether it uses such a service
IP List
Daktela LIR: 194.176.107.3/32, 194.176.107.4/32, 194.176.107.5/32, 194.176.107.6/32, 194.176.107.7/32, 194.176.107.8/32, 194.176.107.9/32, 194.176.107.10/32, 194.176.107.12/32, 194.176.107.13/32
CloudFlare: 45.133.137.215/32, 45.133.137.217/32, 45.133.137.219/32, 45.133.137.221/32, 45.133.137.224/32, 45.133.137.225/32, 45.133.137.229/32
http://OVH.de : 51.68.176.67/32
http://OVH.uk : 51.89.161.247/32
Backup8 (Donjon): 82.113.42.139/32
It is required to add an IP address of your PBX. You can get it via ping -c 1 mypbx.daktela.com
Hardware and Phones
Software IP Phones
We support SW phones – see our Documentation.
SW phones for Windows – Microsip – download the Daktela branded version – or Linphone.
SW phones for MacOS – Telephone (available in the App Store), Zoiper or Linphone.
Support
While Daktela V6 should work with all of the SW phones above, Daktela provides support only for the Daktela Software Phone.
Hardware IP Phones
Suggested HW phones: Yealink IP phones, Cisco SPA, Gigaset
Phone transport set as UDP, allowed codecs G.711 A-law
Min. computer requirements
PC with CPU min. 2.0 GHz (4+ cores ), min. 8 GB RAM (16 GB RAM preferred), Audio In/Out
MacBook with min. 8 GB RAM (16 GB RAM preferred)
Emails and Tickets
Requirements to Send and Receive Email Using the Daktela Helpdesk
Daktela must be the only mail client using the mailbox.
The customer must be aware of the amount of sent emails to prevent blocking etc.
The customer must provide:
access to the incoming and outgoing mail server.
any additional required parameters.
the maximum number of title characters is 128.
For customers utilising the Daktela helpdesk, we recommend verifying the DKIM (DomainKeys Identified Mail) and DMARC (Domain-based Message Authentication, Reporting, and Conformance) configurations on your mail server.
These settings are purely related to your mail server and are independent of our helpdesk system. However, incorrect or missing configurations may mark your emails as suspicious. To address such issues, we suggest referring to this guide:
DKIM is being configured:
On the mail server (e.g., Exchange, Postfix, Gmail, etc.).
In the domain’s DNS, a TXT record containing the public key is created (e.g.,
default._domainkey.yourdomain.com).
DMARC is being configured:
A TXT record is created in the domain’s DNS (e.g.,
_dmarc.yourdomain.com).This record contains rules, such as the strictness of SPF/DKIM checks and where to send reports (e.g.,
v=DMARC1; p=quarantine; rua=mailto:report@yourdomain.com).
Where and How to Configure These Settings?
DNS Records:
Log in to the interface of your DNS provider (e.g., Wedos, Cloudflare, or your domain provider).
Add the necessary TXT records:
DKIM: Contains the public key.
DMARC: Contains the rules.
Mail Server:
Ensure your mail server supports DKIM (e.g., in Exchange, keys are generated and the DNS record is configured).
Implement SPF if not already configured (SPF is another protective mechanism for verifying sender IP addresses).
Testing:
Test using online tools such as Mail-tester or MXToolbox.