300-085 Question #36: Real Exam Question with Answer & Explanation

Question

Options

• AVerify that the trunk has the correct IP address.
• BVerify that the trunk has been enabled for SIP Notify.
• CVerify that the Cisco Messaging Interface service has been started.
• DVerify that the trunk was selected in the Cisco CallManager service parameters.
• EVerify that the CUCM service was restarted after configuration.

Explanation

When no trunk appears in the Cisco Unified Presence SIP publish trunk drop-down, it means the trunk has not yet been designated in the Cisco CallManager service parameters, which is what populates that list.

Common mistakes.

• A. An incorrect IP address on the trunk would cause a connectivity failure after the trunk is selected and saved, but would not prevent the trunk from appearing in the drop-down list in the first place.
• B. SIP Notify enablement on a trunk governs how incoming NOTIFY messages are processed and does not control whether the trunk is listed as a candidate in the CUP publish trunk selection.
• C. The Cisco Messaging Interface service supports JTAPI and TAPI-based messaging integration and has no relationship to the population of the SIP publish trunk drop-down in Cisco Unified Presence.
• E. Restarting the CUCM service can apply pending configuration changes but is not the root cause of a missing trunk entry; the trunk must be designated in service parameters before any restart would make it visible.

Concept tested. SIP publish trunk visibility via CallManager service parameters

Reference. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cups/8_5/english/administration/guide/cuperagu/cupinteg.html

No community discussion yet for this question.