Cisco 300-810 Practice Test - Questions Answers, Page 18

This option blocks calls to 9005551234 for any caller that reaches the Caller System Transfer conversation, which is one of the ways that Cisco Unity Connection can transfer calls outside. The default Transfer Restriction Table is associated with the default System Call Handler class of service, which is used by the Caller System Transfer conversation. Blocking 900 on this table prevents toll fraud by restricting calls to any number that starts with 900, which are usually premium-rate numbers.

Reference:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/security/guide/10xcucsecx/10xcucsec020.html

https://www.cisco.com/c/en/us/support/docs/unified-communications/unity-connection/119337-technote-cuc-00.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.

Reference:

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

This option is the correct service to restart for changes to chat settings or chat node aliases to be reflected for users. The Cisco XCP Text Conference Manager Service is responsible for managing chat rooms and chat sessions on the IM and Presence Service. If this service is not restarted after making changes to chat configuration, the users may not see the updated settings or aliases.

Reference:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/10_5_1/CUP0_BK_CE43108E_00_config-admin-guide-imp-105/CUP0_BK_CE43108E_00_config-admin-guide-imp-105_chapter_0110.html

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/11_5_1/CUP0_BK_CE08159C_00_config-admin-guide-imp-1151/CUP0_BK_CE08159C_00_config-admin-guide-imp-1151_chapter_01100.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_01111.html

This option is the correct protocol that provides device monitoring when integrating Cisco UACA and Cisco UCM. CTI/TAPI stands for Computer Telephony Integration/Telephony Application Programming Interface, and it allows Cisco UACA to monitor and control the devices registered to Cisco UCM. CTI/TAPI is also used for call control, call park, call pickup, and other features on Cisco UACA.

Reference:

https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucmac/cuaca/12_0_3/admin_guide/CUACA_AG_120301.pdf

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmfeat/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100/CUCM_BK_F3AC1C0F_00_cucm-features-and-services-guide_chapter_010010.html

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.

Reference:

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

These two options are the correct rules to configure in the Unity Connection restriction table to block all calls to international phone numbers and numbers that contain 10 digits and begin with 0. The rules use wildcard characters to match any number that meets the criteri

a. The ? character matches any single digit, while the X character matches any single digit except 0. Therefore, 0??? blocks any number that starts with 0 and has nine more digits, while 0XXXXXXXXX blocks any number that starts with 0 and has nine more digits that are not 0.

The other options are incorrect. A.9! matches any number that starts with 9 and has one or more digits after it, which is not the requirement. D.9* matches any number that starts with 9, which is also not the requirement. E.0-9* matches any number that starts with a digit from 0 to 9, which is too broad and would block valid numbers as well.

Reference:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx/10xcucsag170.html

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx/10xcucsag080.html

This option is the correct action to resolve the issue of users receiving the error ''Single Sign On Failed.Invalid Status code in Resume'' when trying to log in through the SAML SSO. The error indicates that the SAML response from the internal IdP is invalid or expired, and that the Webex app cannot resume the SSO process. To fix this issue, the administrator must configure SSO in Control Hub ADFS, which is a Microsoft service that acts as an IdP and provides SAML authentication for Webex. By configuring SSO in Control Hub ADFS, the administrator can ensure that the SAML response is valid and matches the Webex app requirements.

Reference:

https://help.webex.com/en-us/article/WBX9000009033/SSO-Error-Single-Sign-On-failed-Invalid-Status-code-in-Response

https://help.webex.com/en-us/njfoz4/Configure-Single-Sign-On-for-Your-Webex-Site

This option is the correct MFA solution that can be integrated with Cisco Jabber via SAML and used independently of an IdP. Cisco DUO is a cloud-based MFA service that provides an additional layer of security for SAML SSO. Cisco DUO can be configured as a SAML IdP proxy that sits between Cisco Jabber and the actual IdP, or as a standalone SAML IdP that does not require another IdP. Cisco DUO supports various authentication methods, such as push notifications, phone calls, SMS messages, or hardware tokens.

Reference:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_6/cjab_b_planning-guide-cisco-jabber-12-6/cjab_b_planning-guide-cisco-jabber-12-6_chapter_0100.html

https://duo.com/docs/sso-cisco-jabber

This option is the correct way to find information about packet loss, jitter, and codecs in use in the Webex App for Windows during a call. The Settings menu allows users to access various options and preferences for the Webex App, including the Status option. The Status option shows the current network status and quality of service for the app. Users can press Diagnostics or use the keyboard shortcut Ctrl+Shift+Alt+S to open a detailed report of the call statistics, including packet loss, jitter, and codecs in use for audio and video.

Reference:

https://help.webex.com/en-us/article/np8ugnq/Webex-App-Status

https://help.webex.com/en-us/article/np8ugnq/Webex-App-Status#id_136835