Configuring Sip Srv Records - Cisco TelePresence Administrator's Manual

_Service and _Proto will be different for H.323 and SIP, and will depend on the protocol and transport
n
type being used
Name is the domain in the URI that the VCS is hosting (such as example.com)
n
Port is the IP port on the VCS that has been configured to listen for that particular service and protocol
n
combination
Target is the FQDN of the VCS.
n
Configuring H.323 SRV records
Annex O of ITU Specification: H.323
endpoints and for resolving H.323 URL aliases. It also defines parameters for use with the H.323 URL.
The VCS supports the location, call and registration service types of SRV record as defined by this Annex.
Location service SRV records
Location records are required for gatekeepers that route calls to the VCS. For each domain hosted by the
VCS, you should configure a location service SRV record as follows:
_Service is _h323ls
n
_Proto is _udp
n
Port is the port number that has been configured from
n
Registration UDP port
Call signaling SRV records
Call signaling SRV records (and A/AAAA records) are intended primarily for use by non-registered endpoints
which cannot participate in a location transaction, exchanging LRQ and LCF. For each domain hosted by the
VCS, you should configure a call signaling SRV record as follows:
_Service is _h323cs
n
_Proto is _tcp
n
Port is the port number that has been configured from
n
Call signaling TCP port.
Registration service SRV records
Registration records are used by devices attempting to register to the VCS. For each domain hosted by the
VCS, you should configure a registration service SRV record as follows:
_Service is _h323rs
n
_Proto is _udp
n
Port is the port number that has been configured from
n
Registration UDP port

Configuring SIP SRV records

RFC 3263 describes the DNS procedures used to resolve a SIP URI into the IP address, port, and transport
protocol of the next hop to contact.
If you want the VCS to be contactable using SIP URI dialing, you should configure an SRV record for each
SIP transport protocol enabled on the VCS (that is, UDP, TCP or TLS) as follows:
Cisco VCS Administrator Guide (X7.2)
defines the procedures for using DNS to locate gatekeepers and
VCS configuration > Protocols > H.323
VCS configuration > Protocols > H.323
VCS configuration > Protocols > H.323
Dial plan and call processing
as the
as the
as the
Page 202 of 498