350-801 · Question #169
An administrator would like to set several Cisco Jabber configuration parameters to only apply to mobile clients (iOS and Android). How does the administrator accomplish this with Cisco Jabber 12.9…
The correct answer is A. Assign the desired configuration file to "Mobile" Jabber Client Configuration in the Service. To apply specific Cisco Jabber configuration parameters exclusively to mobile clients, administrators should leverage the Cisco Unified Communications Manager (UCM) Service Parameters for Cisco Jabber Client Configuration. This allows for assigning a distinct jabber-config.xml…
Question
An administrator would like to set several Cisco Jabber configuration parameters to only apply to mobile clients (iOS and Android). How does the administrator accomplish this with Cisco Jabber 12.9 and Cisco UCM 12.5?
Options
- AAssign the desired configuration file to "Mobile" Jabber Client Configuration in the Service
- BDeploy jabber-config-user.xml on iOS and Android devices.
- CUpload the jabber-config.enc file to TFTP
- DCreate a user profile in Jabber Policies.
How the community answered
(47 responses)- A81% (38)
- B11% (5)
- C2% (1)
- D6% (3)
Why each option
To apply specific Cisco Jabber configuration parameters exclusively to mobile clients, administrators should leverage the Cisco Unified Communications Manager (UCM) Service Parameters for Cisco Jabber Client Configuration. This allows for assigning a distinct jabber-config.xml file to the "Mobile" client type, ensuring those settings are only delivered to iOS and Android devices.
Cisco Unified Communications Manager (UCM) provides Service Parameters under the Cisco Jabber Client Configuration that allows administrators to specify different jabber-config.xml files for various client types, including "Mobile." By creating a jabber-config.xml file with desired mobile-specific parameters and assigning it to the "Mobile" Jabber Client Configuration, only iOS and Android devices will retrieve and apply those settings.
jabber-config-user.xml is intended for user-specific overrides or local configurations and is not the standard method for centrally applying different policies based on client type (mobile vs. desktop) across an organization.
Uploading a jabber-config.enc file (which is the encrypted form of jabber-config.xml) to TFTP is a necessary step for any Jabber configuration, but it doesn't, by itself, provide the mechanism to make parameters only apply to mobile clients. The assignment mechanism is required.
While Jabber Policies in UCM exist, they are not the primary mechanism to differentiate configuration files based on client type (desktop vs. mobile); the Jabber Client Configuration service parameters are designed for this specific purpose.
Concept tested: Cisco Jabber client configuration differentiation (mobile vs. desktop)
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/planning/CJAB_BK_C272C8EC_00_cisco-jabber-planning-guide-129.html
Topics
Community Discussion
No community discussion yet for this question.