Difference between revisions of "UCoIP DNS/firewall configuration"
Ipbwikiadmin (Talk | contribs) (→DNS configuration) |
Ipbwikiadmin (Talk | contribs) (→Firewall/Router configuration) |
||
| Line 57: | Line 57: | ||
=Firewall/Router configuration= | =Firewall/Router configuration= | ||
| − | + | UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1). | |
| + | |||
| + | But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is: | ||
<pre> | <pre> | ||
Revision as of 10:08, 7 April 2016
DNS configuration
In order to get the full UCoIP concept working at LAN/Internet it's necessary to configure some DNS records at internal and external DNS servers of the company domain.
Next is given an example for the public DNS zone configuration. In that example lets suppose that:
DNS domain: domain.com IPBrick FQDN: voip.domain.com Public IP associated to IPBrick: 88.88.88.88 User UCoIP page to create: jsmith.domain.com
So in this case we need to configure the following DNS records:
A records:
voip A 88.88.88.88 webrtc A 88.88.88.88 webrtcproxy A 88.88.88.88
CNAME records:
im CNAME voip jwchat CNAME voip webphone CNAME voip groupware CNAME voip cafe CNAME voip jsmith CNAME voip
SRV records for VoIP (SIP):
_sips._tcp.domain.com. IN SRV 1 0 5061 voip.domain.com. _sip._tcp.domain.com. IN SRV 1 0 5060 voip.domain.com. _sip._udp.domain.com. IN SRV 1 0 5060 voip.domain.com.
SRV records for chat (Jabber/XMPP):
_jabber._tcp.domain.com. 86400 IN SRV 5 0 5269 voip.domain.com. _xmpp-server._tcp.domain.com. 86400 IN SRV 5 0 5269 voip.domain.com. _xmpp-client._tcp.domain.com. 86400 IN SRV 5 0 5222 voip.domain.com.
If IPBrick will be the email server, we need to modify/add the MX record:
domain.com MX 5 voip.domain.com
Firewall/Router configuration
UCoIP concept uses many services running on their standard ports. IPBrick firewall is prepared to accept all this traffic at public interface (eth1).
But if IPBrick public interface is behind a NAT at Router/Firewall, its necessary to forward the necessary traffic to IPBrick. The list is:
HTTP - 80 TCP HTTPS - 443 TCP SMTP - 25 TCP SIP - 5060 UDP/TCP SIPS - 5061 TCP RTP - 40000:45000 UDP RTP - 50000:55000 UDP RTP - 60000:65000 UDP XMPP - 5222 TCP XMPP - 5269 TCP XMPPS - 5223 TCP WebRTC - 8888 TCP Webphone - 10060 UDP/TCP Webphone - 10062 TCP
