300-810 · Question #271
Refer to the exhibit. A collaboration engineer is troubleshooting an issue with MWIs not working for SIP-integrated Cisco Unity Connection users on Cisco UCM. Calls to the Cisco Unity Connection…
The correct answer is D. Assign a Calling Search Space to the SIP Trunk on Cisco UCM. MWI notifications sent from Unity Connection over a SIP trunk require that trunk to have a Calling Search Space assigned so UCM can route the outbound NOTIFY messages to the endpoint phones.
Question
Refer to the exhibit. A collaboration engineer is troubleshooting an issue with MWIs not working for SIP-integrated Cisco Unity Connection users on Cisco UCM. Calls to the Cisco Unity Connection work, but MWIs do not light. This problem affects all users on the system. Which action resolves the issue?
Exhibit
Options
- AConfigure the Message Waiting Numbers on Cisco UCM.
- BIncrease the Delay Between Requests timer on Cisco Unity Connection.
- CModify the SIP Trunk Security Profile on Cisco UCM.
- DAssign a Calling Search Space to the SIP Trunk on Cisco UCM.
How the community answered
(52 responses)- A10% (5)
- B15% (8)
- C4% (2)
- D71% (37)
Why each option
MWI notifications sent from Unity Connection over a SIP trunk require that trunk to have a Calling Search Space assigned so UCM can route the outbound NOTIFY messages to the endpoint phones.
Message Waiting Numbers define the pilot numbers UCM dials to reach Unity Connection, which is already working since calls reach voicemail successfully.
The Delay Between Requests timer controls pacing of MWI updates on Unity Connection and would not cause a total outage affecting all users.
The SIP Trunk Security Profile governs TLS and digest authentication, not the routing capability needed to deliver MWI NOTIFY messages.
When Unity Connection sends a SIP NOTIFY message to light or extinguish an MWI lamp, the SIP trunk on UCM must have a Calling Search Space assigned so the call routing engine can locate the destination directory number. Without a CSS, UCM cannot resolve where to send the MWI signal, causing all MWI notifications to silently fail while normal call routing continues to work.
Concept tested: SIP trunk CSS required for MWI routing in UCM
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/integration/guide/cucimsgd_b_cuc-integration-guide-cisco-ucm/cucimsgd_b_cuc-integration-guide-cisco-ucm_chapter_010.html
Topics
Community Discussion
No community discussion yet for this question.