300-810 · Question #254
Refer to the exhibit. Users report that they cannot use the voicemail option in Cisco Jabber, but other features work as expected. An engineer verifies that all the services are running on the Cisco…
The correct answer is C. The name does not represent the FQDN of the server. In Cisco UCM UC Service configuration for voicemail, the server address field must contain the Fully Qualified Domain Name (FQDN) of the Unity Connection server, not a short hostname or IP address. Jabber validates the server's TLS certificate against the hostname it connects…
Question
Refer to the exhibit. Users report that they cannot use the voicemail option in Cisco Jabber, but other features work as expected. An engineer verifies that all the services are running on the Cisco Unity Connection server and that voicemail is reachable by using a phone device. The UC Service Information settings for Voicemail are associated to a service profile used by all users. What is the cause of the issue?
Exhibit
Options
- AThe protocol must be HTTPS.
- BThe IP address is misconfigured.
- CThe name does not represent the FQDN of the server
- DThe port must be 443.
How the community answered
(41 responses)- A5% (2)
- B12% (5)
- C76% (31)
- D7% (3)
Explanation
In Cisco UCM UC Service configuration for voicemail, the server address field must contain the Fully Qualified Domain Name (FQDN) of the Unity Connection server, not a short hostname or IP address. Jabber validates the server's TLS certificate against the hostname it connects to. If only a hostname (not FQDN) is entered, certificate validation fails because the certificate's CN or SAN contains the full FQDN. This mismatch causes Jabber to fail the voicemail connection silently. Since voicemail works on physical phones (which use a different integration path), the issue is isolated to the UC Service configuration used by Jabber.
Topics
Community Discussion
No community discussion yet for this question.