Cisco 350-801 - Implementing Cisco Collaboration Core Technologies (350-801 CLCOR)

Balanced mode provides user load balancing and user failover in the event of an outage. Active/standby mode provides an always on standby node in the event of an outage, but it does not provide load balancing.

Here is a more detailed explanation of the two modes:

Balanced mode: In balanced mode, the IM and Presence Service nodes are configured to work together to provide high availability. The nodes are configured in a redundancy group, and the system automatically balances the load of users across the nodes in the group. If one of the nodes fails, the system automatically fails over the users to the other nodes in the group.

Active/standby mode: In active/standby mode, one of the IM and Presence Service nodes is designated as the active node, and the other nodes are designated as standby nodes. The active node handles all of the user traffic, and the standby nodes are only used if the active node fails. If the active node fails, the system automatically fails over to one of the standby nodes.

The engineer should run the following debugs or commands in the voice gateway to troubleshoot the issue:

debug isdn q931 - This debug will show the ISDN Q.931 messages that are being exchanged between the voice gateway and the ISDN switch. This can be used to identify the cause of the "Incomplete Destination" error.

show isdn status - This command will show the status of the ISDN PRI circuit. This can be used to verify that the circuit is up and running.

The other options are not correct. The debug isdn q921 command will show the ISDN Q.921 messages that are being exchanged between the voice gateway and the ISDN switch. This is not necessary for troubleshooting the issue. The term mon command will show the terminal monitor output. This is not necessary for troubleshooting the issue. The debug voip ecapi inout command will show the VoIP ECAP messages that are being exchanged between the voice gateway and the VoIP server. This is not necessary for troubleshooting the issue. The show controller ti command will show the status of the T1 controller. This is not necessary for troubleshooting the issue.

These are the two types of trunks that can be used when configuring a hybrid local gateway for Cisco Webex Calling1. A TLS-based trunk uses Transport Layer Security (TLS) to secure the SIP signaling between the hybrid local gateway and Webex Calling1. A registration-based trunk uses SIP registration to authenticate the hybrid local gateway with Webex Calling and receive calls from the cloud1.

The ALLUSERS property is a command-line argument that can be used to install the Webex app as a "per machine" installation. This means that the app will be installed for all users on the computer, regardless of which user account is currently logged in.

The ACCEPT_EULA property is a command-line argument that can be used to accept the end-user license agreement (EULA) for the Webex app. The INSTALL_ROOT property is a command-line argument that can be used to specify the installation directory for the Webex app. The FORCELOCKDOWN property is a command-line argument that can be used to prevent users from uninstalling the Webex app.