Polycom 7000 manual Additional DNS Records for SIP Proxy

Polycom RealPresence DMA System Initial Configuration Summary

Add Required DNS Records for the Polycom RealPresence DMA System

Note: Consult an expert

If you’re not familiar with DNS administration, the creation of various kinds of DNS resource records (A/AAAA,NAPTR, NS, and SRV), your enterprise’s DNS implementation, and tuning for load balancing (if needed), please consult with someone who is.

Your Polycom RealPresence DMA system must be accessible by its host name(s), not just its IP address(es), so you (or your DNS administrator) must create A and/or AAAA records for IPv4 and IPv6, respectively, as well as the corresponding PTR records, on your DNS server(s).

A/AAAA records and PTR records that map each physical host name to the corresponding physical IP address and each virtual host name to the corresponding virtual IP address are mandatory, as are the corresponding PTR records that allow reverse DNS resolution of the system’s physical or virtual host name(s).

Note: Fully qualified domain names

Depending on local DNS configuration, a host name could be the Polycom RealPresence DMA system’s fully qualified domain name (FQDN) or a shorter name that DNS can resolve.

For some features, such as Microsoft Exchange Server integration, it’s imperative that the FQDN can be resolved in DNS, especially by the Exchange server.

The DNS server(s) should also have entries for your Microsoft® Active Directory® server (if different from the DNS server) and any external gatekeepers or SIP peers.

You may need to create additional DNS records as described below.

Additional DNS Records for SIP Proxy

To support the use of your Polycom RealPresence DMA system as a SIP proxy server and ease future network administrative burdens, create the following DNS records (for each cluster in a supercluster, if applicable):

●Optionally, NAPTR records that describe the transport protocols supported by the SIP proxies at a domain and identify the preferred protocol. Configure these statically to match the system’s SIP transport protocol configuration.

Polycom, Inc. 28