Polycom 7000 manual Additional DNS Records for the H.323 Gatekeeper

Polycom RealPresence DMA System Initial Configuration Summary

●SRV records for each transport protocol that identify the host names of the SIP proxies that service a particular domain. Configure these statically to point to the host names of the Call Servers in the domain. Here are example records for two clusters:

_sips._tcp.example.com. 86400 IN SRV 10 1001 5061 dma-asia.example.com. _sips._tcp.example.com. 86400 IN SRV 10 1002 5061 dma-europe.example.com. _sip._tcp.example.com. 86400 IN SRV 20 1001 5060 dma-asia.example.com. _sip._tcp.example.com. 86400 IN SRV 20 1002 5060 dma-europe.example.com. _sip._udp.example.com. 86400 IN SRV 30 1001 5060 dma-asia.example.com. _sip._udp.example.com. 86400 IN SRV 30 1002 5060 dma-europe.example.com.

To enable access from the public internet, create corresponding SRV records, visible from outside the firewall, for the public address of each SIP session border controller (SBC).

For more information about the use of DNS in SIP, refer to RFCs 3263 and 2782.

Additional DNS Records for the H.323 Gatekeeper

To support the use of your Polycom RealPresence DMA system as an H.323 gatekeeper and ease future network administrative burdens, create SRV records that identify the host names of the gatekeepers that service a particular domain. These records are necessary in order to enable the optional inbound URL dialing feature. Configure them statically to point to the host names of the Call Servers in the domain. Here are example records for two clusters:

_h323ls._udp.example.com. 86400 IN SRV 0 1 1719 dma-asia.example.com. _h323ls._udp.example.com. 86400 IN SRV 0 1 1719 dma-europe.example.com. _h323cs._tcp.example.com. 86400 IN SRV 0 1 1720 dma-asia.example.com. _h323cs._tcp.example.com. 86400 IN SRV 0 1 1720 dma-europe.example.com.

To enable access from the public internet, create corresponding SRV records, visible from outside the firewall, for the public address of each H.323 session border controller (SBC).

For more information about the use of DNS in H.323, refer to the H.323 specification, Annex O, and the H.225.0 specification, Appendix IV.

Additional DNS Records for the Optional Embedded DNS Feature

To support DNS publishing by your Polycom RealPresence DMA system’s embedded DNS servers (see Embedded DNS), a DNS NS record is needed for the physical host name of each server in each cluster in the supercluster. These records identify the Polycom RealPresence DMA system’s embedded DNS servers as authoritative for the specified logical host name. The logical host name you specify is the one in the Call server sub-domain controlled by RealPresence DMA field on the Embedded DNS page. Here are example records for two dual-server clusters:

callservers.example.com. 86400 IN NS dma-asia-server1.example.com. callservers.example.com. 86400 IN NS dma-asia-server2.example.com. callservers.example.com. 86400 IN NS dma-europe-server1.example.com. callservers.example.com. 86400 IN NS dma-europe-server2.example.com.

Polycom, Inc. 29