Valid SRV Records for SIP and H.323 Communication | example.com

SRV Records for SIP and H.323 Communication

Question

An organization with a domain name of example.com.

Which two SRV records are valid for a SIP and H.323 communication? (Choose two.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

AC.

SRV (Service) records are used to locate specific services such as SIP, H.323, or other services in a domain. They help in identifying the location of the service and the protocol to be used for communication. In this scenario, the organization has a domain name of example.com and needs to create two valid SRV records for SIP and H.323 communication.

The two valid SRV records for SIP and H.323 communication are:

A. _sips._tcp.example.com D. _h323ls._tcp.example.com

Explanation:

A. _sips._tcp.example.com: This SRV record is valid for SIP communication over a TCP connection. The '_sips' prefix indicates that the communication is secure and encrypted using TLS. The '_tcp' suffix indicates that the protocol used is TCP. Therefore, this SRV record is used for secure SIP communication over TCP.

B. _sips._udp.example.com: This SRV record is not valid as SIP communication over UDP is not secure.

C. _h323ls._udp.example.com: This SRV record is not valid for H.323 communication as it specifies the use of UDP. H.323 typically uses TCP as the transport protocol for signaling messages.

D. _h323ls._tcp.example.com: This SRV record is valid for H.323 communication over TCP. The '_h323ls' prefix indicates that the communication is secure and encrypted using TLS. The '_tcp' suffix indicates that the protocol used is TCP. Therefore, this SRV record is used for secure H.323 communication over TCP.

E. _collab-edge._tls.example.com: This SRV record is not valid for either SIP or H.323 communication. It is used for locating Cisco Collaboration Edge services for mobile and remote access.