350-801 Cisco Implementing Cisco Collaboration Core Technologies (350-801 CLCOR) Free Practice Exam Questions (2025 Updated)

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.

To implement toll fraud prevention on Cisco UCM, an administrator can use the following parameters:

Enable Forced Authorization Code 112211.

Set an authorization level of 3 for the route pattern 8005551212.

Require no access code to dial 10-digit numbers.

The route pattern must be implemented as follows:

Pattern = 1122113.8005551212

This will require users to enter the authorization code 112211 followed by the number 8005551212 to dial this number. The authorization level of 3 will prevent users from transferring calls to this number.

The codec preference list for the "Dallas-REG" region is "Factory Default low loss". This list includes the following codecs in order of preference:

G.729

G.711

OPUS

MP4A-LATM

The codec preference list for the "Austin-REG" region is "Factory Default low loss". This list includes the following codecs in order of preference:

G.729

G.711

OPUS

MP4A-LATM

Since both regions have the same codec preference list, the codec that will be used for a call made between "Dallas-REG" and "Austin-REG" is G.729.

G.729 is a narrowband speech codec that was developed by the ITU-T in 1988. It is a low-bitrate codec that provides good quality speech at a bitrate of 8 kbps. G.729 is widely used in VoIP applications and is the default codec for many VoIP systems.

G.711 is a wideband speech codec that was developed by the ITU-T in 1972. It is a high-bitrate codec that provides excellent quality speech at a bitrate of 64 kbps. G.711 is not as widely used as G.729 due to its high bitrate requirements.

OPUS is a lossy audio codec that was developed by the IETF in 2012. It is a low-bitrate codec that provides good quality speech at a bitrate of 6 kbps. OPUS is widely used in VoIP applications and is the default codec for many VoIP systems.

MP4A-LATM is a lossy audio codec that was developed by the IETF in 1999. It is a high-bitrate codec that provides excellent quality speech at a bitrate of 24 kbps. MP4A-LATM is not as widely used as G.729 or OPUS due to its high bitrate requirements.

This is the first thing that must be verified when troubleshooting the issue of phone status showing rejected in Cisco UCM1. Auto-registration allows new phones to register with Cisco UCM without manual configuration1. If auto-registration is disabled, the phone will not be able to register and will show a rejected status1.

The other options are not the first things that must be verified when troubleshooting the issue:

B. whether the Initial Trust List and Certificate Trust List files on the phone are correct is not the first thing to verify, but it may be a possible cause of the issue if the phone has an ITL file from another cluster that prevents it from registering with Cisco UCM2. To resolve this issue, the ITL file needs to be deleted from the phone or exchanged between the clusters2.

C. whether the phone is in the correct VLAN is not the first thing to verify, but it may be a possible cause of the issue if the phone is not in the same VLAN as the Cisco UCM server or cannot reach it due to network issues3. To resolve this issue, the network connectivity and VLAN configuration need to be checked and fixed3.

D. whether the phone’s MAC address is correct in Cisco UCM is not the first thing to verify, but it may be a possible cause of the issue if the phone’s MAC address does not match the one configured in Cisco UCM. To resolve this issue, the MAC address needs to be corrected and updated in Cisco UCM.