300-810 Exam Dumps : Implementing Cisco Collaboration Applications (CLICA)

This option is the correct action to resolve the issue of MWI not working when a new message is received. The SIP server list on the Cisco Unity Connection port group defines the destination addresses for SIP messages, such as MWI notifications, that Unity Connection sends to Cisco UCM. If the SIP server list does not match the device pool settings on the SIP trunk, Cisco UCM may not be able to route the MWI notifications to the correct devices, and may respond with a SIP 503 Service Unavailable message. References:

• https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/integration/guide/cucm_sip/cucintcucmsip100x.pdf
• https://www.cisco.com/c/en/us/support/docs/unified-communications/unity-connection/200453-Configure-MWI-for-SIP-Integration-Betwee.html

This option explains why the user sessions have not fallen back to the homed nodes after the failed service or server was restored. The Client Re-Login upper limit setting determines how long the Jabber clients will attempt to re-login to their homed nodes after a failover event. If the failed service or server is offline longer than this setting, the Jabber clients will stop trying to re-login and will remain on the backup node until the administrator manually initiates a fallback or recovery. The default value for this setting is 30 minutes, but it can be changed in the Server Recovery Manager Service Parameters. References:

• https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-im-presence-service/200958-IM-and-Presence-Server-High-Availability.html
• https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/11_5_1/cup0_b_config-and-admin-guide-1151su5/cup0_b_imp-system-configuration-1151su5_chapter_0100.html