A collaboration engineer is configuring SIP interdomain federation for Cisco IM and Presence. The external domain cannot be discovered using DNS SRV. If the external enterprise domain is…

The correct answer is A. com.ciscocollab.*. In Cisco IM and Presence, when configuring a static route for SIP interdomain federation to a domain that cannot be discovered via DNS SRV, the destination pattern field uses a reverse-domain-notation wildcard format. For the domain 'ciscocollab.com', the correct static route…

Cisco Unified IM and Presence

Question

A collaboration engineer is configuring SIP interdomain federation for Cisco IM and Presence. The external domain cannot be discovered using DNS SRV. If the external enterprise domain is ciscocollab.com, what destination pattem should the engineer use for a static route?

Options

Acom.ciscocollab.*
B_sipfederationtls._tcp.ciscocollab.com
C.ciscocollab.com,
D.ciscocollab.com

How the community answered

(46 responses)

A
78% (36)
B
4% (2)
C
7% (3)
D
11% (5)

Explanation

In Cisco IM and Presence, when configuring a static route for SIP interdomain federation to a domain that cannot be discovered via DNS SRV, the destination pattern field uses a reverse-domain-notation wildcard format. For the domain 'ciscocollab.com', the correct static route destination pattern is 'com.ciscocollab.*' - the domain labels are reversed and a wildcard is appended. This format is specific to Cisco IM and Presence's routing engine. Option B is the DNS SRV record name used for discovery, not a static route pattern. Option C uses an incorrect mixed format. Option D is missing the wildcard and leading dot combination that would be required for subdomain matching in a different context.

Topics

#SIP Federation#Cisco IM and Presence#Static Route Configuration#DNS SRV Troubleshooting

Community Discussion

No community discussion yet for this question.

Full 300-810 Practice