The following protocols should be installed and available on the network:
|DHCP||Devices that receive an internal IP address assignment via Dynamic Host Configuration Protocol (DHCP) are recommended. Devices can be given static IPs, however, this is more labor intensive.|
|SIP||Phones initiate a SIP session with hosted system. NAT keep-alives need to be permitted to keep these sessions continuously open. Keep-alives are sent on a 30 second interval.|
|QoS||In a converged network, Quality of Service (QoS) must be applied to prioritize voice and video traffic over all other traffic types.|
|DNS*||DNS is used to resolve the URL for handset configuration files and a time server. Some user agent devices also use DNS to perform SRV lookups.
Note: Be sure that the phones are using a reliable DNS server as a DNS failure can delay or prevent call setup. We strongly recommend using Google’s DNS, 18.104.22.168 and 22.214.171.124.
|Public IPs||In most cases, you will not need a static IP address from your internet service provider (ISP); however, there are situations where this is preferable. Some Jive devices, such as Jive Voice Gateways (usually an Adtran router) and Jive HD Video units may require public IPs to function properly. Public IPs are not required (nor recommended) for the hosted VoIP handsets.|
|*Recursive DNS Resolvers||Properly-configured DNS is crucial to the performance, stability, and failover of your Jive solution. DNS resolvers must respect and not modify the TTL returned in RRs. Jive uses low TTLs to facilitate seamless failover in the event of any Internet, platform, or infrastructure instability. To ensure calls are routed to the optimal datacenter based, Jive respects EDNS0-client-subnet attributes in DNS queries; it is therefore important that customer DNS queries come from a stable IP address (i.e. not load-balanced across multiple public IP addresses). That is why it is recommended to use Google’s DNS resolvers (126.96.36.199 and 188.8.131.52).|