Configuring SRV Records for Inbound B2B Calls | Cisco Collaboration Cloud and Edge Solutions

Inbound B2B Calls SRV Record Configuration

Question

An engineer is deploying an Expressway solution for the SIP domain Cisco.com.

Which SRV record should be configured in the public DNS to support inbound B2B calls?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2018/pdf/BRKCOL-2018.pdf

When deploying an Expressway solution for a SIP domain such as Cisco.com, it is important to configure the appropriate SRV record in the public DNS to support inbound business-to-business (B2B) calls.

In this scenario, the correct SRV record to configure is option A: _collab-edge._tls.cisco.com.

The _collab-edge SRV record is used to support Mobile and Remote Access (MRA) and B2B communication. It specifies the FQDN of the Expressway-E server and the port number to use for SIP over TLS.

The _tls part of the SRV record specifies that the communication will be encrypted using TLS, which provides secure communication between the endpoints.

The cisco.com part of the FQDN specifies the SIP domain that is being used for the deployment.

Option B, _cisco-uds._tcp.cisco.com, is used to support the Cisco Unified Communications Manager (CUCM) User Data Service (UDS) for device configuration and directory access. This is not related to B2B calls.

Option C, _sip._tcp.cisco.com, is a generic SRV record for SIP communication, but it does not specify any particular function or service.

Option D, _cuplogin._tcp.cisco.com, is used to support Cisco Unified Personal Communicator (CUPC) login services, which is not related to B2B calls.

Therefore, the correct answer is A: _collab-edge._tls.cisco.com.