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

When deploying co-resident VMs by using Cisco UCM, it is important to avoid hardware oversubscription. This means that you should not assign more resources to the VMs than the physical hardware can provide. For example, if you have a server with 16 CPU cores, you should not assign more than 16 CPU cores to the VMs.

If you oversubscribe the hardware, the VMs will not be able to get the resources they need to run properly. This can lead to performance problems and even outages.

To avoid hardware oversubscription, you should carefully plan your VM deployments. You should also monitor the performance of the VMs to make sure that they are not overusing the resources.

Here are some additional tips for deploying co-resident VMs by using Cisco UCM:

Use a virtualization platform that supports Cisco UCM.

Make sure that the VMs have the correct operating system and software installed.

Configure the VMs to use the correct network settings.

Monitor the performance of the VMs to make sure that they are running properly.

The asterisk (*) wildcard is used to match any sequence of characters, including an empty sequence. Therefore, it can be used to match any domain name in a SIP Route Pattern.

The other options are not correct because:

B. @: The @ symbol is used to separate the user name from the domain name in an email address.

C. !: The ! symbol is used to negate a character class.

D. .: The . symbol is used to match any single character.

The Restrict setting in the Webex Calling dial plan prevents users from placing certain types of outbound calls. For example, you can use the Restrict setting to prevent users from making international calls or calls to premium-rate numbers.

The Block setting in the Webex Calling dial plan prevents users from placing any outbound calls. The Transfer to Number setting in the Webex Calling dial plan transfers all outbound calls to a specified number. The Reject setting in the Webex Calling dial plan rejects all outbound calls.

Here is a table summarizing the different dial plan settings and their effects:

Dial Plan Setting

Effect

Block

Prevents users from placing any outbound calls.

Transfer to Number

Transfers all outbound calls to a specified number.

Reject

Rejects all outbound calls.

Restrict

Prevents users from placing certain types of outbound calls.

A location is a physical site that contains users, devices, and resources. Locations are used to organize calling features within a physical site. For example, you can create a location for each of your offices and then assign users, devices, and resources to that location. This will allow you to manage calling features for each office separately.

The two protocols that can be configured for the Cisco Unity Connection and Cisco UCM integration are SIP and SCCP.

SIP, or Session Initiation Protocol, is a signaling protocol used for initiating, maintaining, and terminating real-time sessions, including voice, video, and messaging applications.

SCCP, or Skinny Client Control Protocol, is a Cisco proprietary signaling protocol used for controlling Cisco IP phones.

H.323 is an older signaling protocol that is no longer widely used. MGCP, or Media Gateway Control Protocol, is a protocol used for controlling media gateways. RTP, or Real-time Transport Protocol, is a protocol used for transporting real-time data, such as voice and video

Cisco IP Phone 7800 Series devices support remote command-line access through SSH, but this access is disabled by default in Cisco Unified Communications Manager (CUCM). When an engineer is unable to reach the phone’s command line while the device is otherwise reachable via ICMP/HTTP and registered to CUCM, the most common cause is that SSH is not enabled or the required credentials have not been configured.

Within the Phone Configuration → Product Specific Configuration Layout, CUCM provides administrative controls for remote access capabilities. The “SSH Access” parameter in this menu explicitly controls whether the phone will accept SSH connections; this must be enabled for any CLI access to function. In addition, CUCM requires the configuration of SSH username and password under the Secure Shell Information section. These credentials are then provisioned to the phone through its configuration file. If SSH is enabled but no credentials are defined, the phone will reject the connection even if TCP/22 is open.

Other listed options (such as disabling Web Access, enabling Settings Access, or turning on FIPS mode) do not impact SSH functionality. Web Access controls HTTP/HTTPS availability, Settings Access controls local phone menu access, and FIPS mode enforces cryptographic compliance but does not enable SSH by itself.

Therefore, the two actions that resolve the issue are:

Enabling SSH Access in the Product Specific Configuration Layout

Configuring SSH username and password under Secure Shell Information

These steps ensure the phone downloads updated configuration files, activates SSH, and allows authenticated remote CLI access—fully aligned with Cisco’s standard operational behavior for 7800 Series endpoints.

The following commands are used to configure the codec on a Cisco Unified Border Element to prefer the G.711 ulaw and use G.711 alaw as the next codec:

Code snippet

voice class codec 100

codec preference 1 g711ulaw

codec preference 2 g711alaw

The voice class codec 100 command creates a new voice class with the ID of 100. The codec preference 1 g711ulaw command sets the preference for the G.711 ulaw codec to 1. The codec preference 2 g711alaw command sets the preference for the G.711 alaw codec to 2.

The correct answers are B and C.

To ensure that end users are not prompted to accept the end-user license agreement (EULA) when they start the Webex app, the engineer must set the following two registry keys:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\CiscoCollabHost\Eula_disable

HKEY_LOCAL_MACHINE\Software\CiscoCollabHost\Eula Setting\Eula_disable

Setting these registry keys will disable the EULA prompt for all users who start the Webex app.

The other options are not valid actions to ensure that end users are not prompted to accept the EULA.

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.