Refer to the exhibit. A collaboration engineer is troubleshooting an issue with Cisco Jabber for Windows deployed in phone-only mode. The users are reporting that they cannot access voicemail…

Question

Exhibit

Options

• AAdd a secondary voicemail service to Cisco UCM to allow Cisco Jabber users to receive voice
• BApply the voicemail service to a service profile so that the client can retrieve the settings
• CUpdate the jabber-config xml file with the correct voicemail parameters and restart the
• DAdd a primary voicemail service to Cisco UCM to allow Cisco Jabber users to receive voice

• A
  6% (1)
• B
  6% (1)
• C
  69% (11)
• D
  19% (3)

Explanation

In a Cisco Jabber phone-only mode deployment, voicemail service settings are typically delivered via the jabber-config.xml file hosted on the TFTP server. If users cannot access voicemail, the most likely cause is that the jabber-config.xml file is missing or has incorrect voicemail parameters (such as the MailStore server address or credentials). Updating the jabber-config.xml with the correct voicemail configuration parameters and restarting the TFTP service (or the Cisco Jabber client) will push the correct settings to the client. A service profile (Option B) is the mechanism for non-phone-only deployments where UCM service profiles deliver settings.

No community discussion yet for this question.