This article summarises the exceptions needed for using Dekko in environments with strict network and device restrictions.
Browsers
Dekko encourages the use of up-to-date browsers to get the most out of our platform and promote good general security risk management practices.
Dekko is officially supported for Google Chrome and Microsoft Edge. Support is offered for the current stable version, as well as the previous two versions.
Functionality and feature availability on older versions and alternative browsers is not guaranteed.
To see the current and previous Chrome versions click here.
To see current and and previous Edge versions click here.
To check and update your current browser version enter the following in to your address bar:
Chrome: chrome://settings/help
Edge: edge://settings/help
Or go to whatismybrowser.com
Network whitelisting
As a web application Dekko requires whitelisting in corporate network/device environments where strict firewall and filtering systems may be in operation. The following is inclusive for Dekko meetings encrypted conferencing.
To allow Dekko to function reliably the following should be added to network whitelisting policies:
| Configuration | DekkoGov-AU | DekkoGov-CA | DekkoPro |
| URL* |
*.dekko.io |
*.dekko.io |
*.dekko.io |
| TCP | 443 (HTTPS) | 443 (HTTPS) | 443 (HTTPS) |
| UDP** | 10000-20000 (SRTP) for *.dekko.io | 10000-20000 (SRTP) for *.dekko.io | 10000-20000 (SRTP) for *.dekko.io |
The above settings are required for general Dekko functions such as file upload, file download, hosting and joinging meetings, etc.
If users experience interruption to these basic activities, it is highly likely that network filtering settings are preventing the Dekko front end (web app) from succesfully communicating with the Dekko backend (cloud infrastructure).
* For service reliability, DekkoGov uses load balancers which comprise of multiple bridges which change dynamically, so we cannot define a single subdomain - therefore *.dekko.io is specified. For infrastructure failover and DDoS protection, DekkoGov’s IP is not static and change over the time, so we cannot provide a single IP.
** Required for Dekko Meetings encrypted video conferencing.
In addition, the following browser policies are recommended:
| Configuration | DekkoGov-AU | DekkoGov-CA | DekkoPro |
| Cookies |
au.dekko.io [*.]au-api.dekko.io |
ca.dekko.io [*.]ca-api.dekko.io |
pro.dekko.io [*.]pro-be.dekko.io |
|
Pop-ups (for AAD SSO windows) |
au.dekko.io |
ca.dekko.io |
pro.dekko.io |
| Microphone** |
au.dekko.io |
ca.dekko.io |
pro.dekko.io |
| Camera** |
au.dekko.io |
ca.dekko.io |
pro.dekko.io |
| Notifications |
au.dekko.io |
ca.dekko.io |
pro.dekko.io |
** Required for Dekko Meetings encrypted video conferencing.
Optionally, it is recommended that cookie and data clearing settings are enabled:
Local settings can be accessed by entering the following in to your address bar:
Chrome: chrome://settings/privacy
Edge: edge://settings/privacy
Device/Notifications prompts
If presented, press Allow for microphone and camera device permissions for au.dekko.io/pro.dekko.io (for Dekko Meetings):
