Cisco Unity Connection system is integrated with two Cisco UCM clusters cluster A and duster B Voicemail is working perfectly for users on cluster A Users on cluster B report Message Waiting factor (MWI) lights are not working at all. however they can still send/receive messages. Which action resolves the issue?
The scenario describes a classic Message Waiting Indicator (MWI) issue specifically affecting users on cluster B of a Cisco Unity Connection setup integrated with two UCM clusters. The most likely cause is mismatched MWI ON/OFF ports between cluster B and Cisco Unity Connection. This option addresses that:
'Use Same Port for Enabling and Disabling MWIs' Checkbox:This setting ensures that Cisco Unity Connection utilizes a single port for both activating and deactivating MWIs, streamlining the process and preventing port mismatches.
An engineer in a company have access to voice calling and voicemail from desktop phones As the company transitions to remote work, users are utilizing the Cisco Jabber client through Mobile and Remote .. to access company phone services. Users cannot access voicemail through the Cisco Jabber client, even though voicemail is functioning in the office on the desk phone. Cisco Jabber works IM and Presence, including calling through Mobile and Remote Access What is the cause of the issue?
The scenario indicates that Cisco Jabber clients used over Mobile and Remote Access (MRA) cannot access voicemail, even though the feature works perfectly from desk phones. This strongly suggests a missing integration between Cisco Unity Connection and internal Cisco UCM clusters. Here's why:
MRA and Cisco Unity Connection:Jabber clients using MRA often rely on integration with Cisco Unity Connection on the internal network for voicemail access.
An engineer must configure XMPP federation on a Cisco Instant Messaging and Presence Service node, but the XCP XMPP Federation Connection Manager service fails to start. Which action must the engineer take to resolve the issue?
The Cisco XCP XMPP Federation Connection Manager service on the IM & Presence node depends on the Cisco XCP Router service. If the XMPP Federation Connection Manager fails to start, a likely cause is an issue with the XCP Router.
An engineer is informed that high availability for a Cisco IM and Presence server fails While the engineer examines the Cisco UCM presence redundancy group in the Ul. they discover that the first .. is in the Idle state, and the second node is in the running in backup mode state Which action must the engineer take to place both nodes back in the normal state?
The scenario indicates a high availability failover condition for a Cisco IM and Presence server: one node is idle, the other is running in backup mode. To restore both nodes to normal operation, initiating a controlled failover is the best approach:
Failover Action:This will gracefully switch the active role to the idle node, making it primary and restoring redundancy.
Refer to the exhibit.
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?
The scenario describes an issue where Message Waiting Indicators (MWIs) aren't lighting up for SIP-integrated Cisco Unity Connection users, even though calls reach voicemail. This points towards a configuration problem with MWI notifications on Cisco UCM.
A) Modify the SIP Trunk Security Profile on Cisco UCM:While SIP trunk security is important, it likely wouldn't affect MWI functionality in this case.
B) Increase the Delay Between Requests timer on Cisco Unity Connection:This setting might be used for other purposes but wouldn't directly address MWI notification issues on Cisco UCM.
C) Assign a Calling Search Space to the SIP Trunk on Cisco UCM:Calling Search Space defines call routing, not MWI notification.
Caprice
19 days agoLuis
22 days agoMaira
26 days ago