Dear,
The quality of our solution stands or falls with a correct implementation in the customer's network.
Our years of experience have shown that we cannot guarantee the quality if the solution has to be behind a firewall that is beyond our control.
That is why we would like to completely decouple our solution from the firewall to ensure that you can communicate with customers and employees without any worries.
If you do decide that the solution should be behind the firewall, we will provide you with a document asking you to confirm that you take responsibility for any quality issues and call interruptions.
Firewall requirements
SIP ALG must always be switched off!
If the managing party really does not want to allow all traffic, for example due to regulations, these are the known necessary firewall configurations:
- Disable SIP ALG
- Allow outgoing UDP/5060 (target ports, source ports must be 'any')
- Allow outgoing TCP/5061 (target ports, source ports must be 'any')
- Allow outgoing RTP (UDP ports 6000-65531, both source and destination ports)
- Allow outgoing DNS (UDP port 53)
- Allow outgoing NTP (UDP port 123)
- Allow outgoing HTTP(S) (TCP ports 80 and 443)
Again, it is recommended to just open all traffic to our IP ranges.
Make sure the links below are allowed or whitelisted.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article