Drag and Drop Question An engineer is configuring a Jabber client installation switch for a phone system using Cisco UCM as the registration server, with a softphone control address of 10.0.1.200. and

Question

Exhibit

Answer Area

Explanation

The question tests knowledge of Cisco Jabber client installation command-line parameters for integrating with Cisco UCM, specifically for clearing configurations, setting the product mode, specifying authentication, and providing TFTP and CTI server addresses.

Approach. Based on the provided solution image and the scenario details:

• CLEAR=1: The scenario states 'after all previous configurations are cleared'. The CLEAR parameter, when set to 1, ensures that any existing Jabber configurations are removed before the new installation, fulfilling this requirement.
• PRODUCT_MODE=Phone_Mode: The scenario mentions 'Jabber client installation switch for a phone system' and 'softphone control'. Phone_Mode is the correct PRODUCT_MODE setting for Jabber to function as a softphone or to control a desk phone, integrating with the phone system.
• AUTHENTICATOR=CUCM: The scenario specifies 'Cisco UCM as the registration server'. CUCM (Cisco Unified Communications Manager) is the correct authenticator value for Jabber clients registering with a UCM cluster.
• TFTP=10.11.20.201: The scenario indicates 'configuration files received from 10.11.20.201'. TFTP (Trivial File Transfer Protocol) is used by Cisco devices, including Jabber, to download configuration files. Thus, 10.11.20.201 is the TFTP server address.
• CTI=10.0.1.200: The scenario specifies a 'softphone control address of 10.0.1.200'. CTI (Computer Telephony Integration) is the protocol used for controlling telephony functions, and the CTI parameter points to the CTI server (typically a UCM publisher or subscriber) responsible for this control. Therefore, 10.0.1.200 is the CTI server address.

Common mistakes.

• common_mistake. Common mistakes include misidentifying the purpose of each parameter or confusing the IP addresses. For example:
• Dragging 'Clear' to CLEAR= instead of '1'. 'Clear' describes the action, but '1' is the actual value for the msiexec switch.
• Using 'Softphone' for PRODUCT_MODE= instead of 'Phone_Mode'. While 'Softphone' describes the client's function, 'Phone_Mode' is the specific msiexec parameter value.
• Swapping the TFTP and CTI IP addresses (10.11.20.201 and 10.0.1.200). The question explicitly links configuration files to 10.11.20.201 (TFTP) and softphone control to 10.0.1.200 (CTI).
• Using 'Registration' instead of 'CUCM' for AUTHENTICATOR=. While UCM handles registration, 'CUCM' is the specific identifier used in the parameter.
• Attempting to use '2' for CLEAR= when '1' is the standard value for enabling the clear function in this context.

Concept tested. Understanding of Cisco Jabber client installation parameters via msiexec command-line switches, including configuration clearing, product modes, authentication servers (Cisco UCM), TFTP server configuration for file retrieval, and CTI server configuration for call control.

No community discussion yet for this question.