You are the administrator for your company’s UCM network. Your company is running the UCM 8.6(1).
Examine the exhibit below, and answer the associated question:
You have verified that the softphone named Jabberwocky has been created and associated with the correct
end user in UCM Administration.
Which of the following is least likely to have caused the Cisco Jabber error message? (Select the best answer.)
A.
The TFTP server is down.
B.
The IM and Presence server is down.
C.
Servers have not been configured by using host names.
D.
Cisco Jabber requires a fully qualified user name.
Explanation:
Although Cisco Jabber does require a fully qualified user name, such as [email protected], to register
with Cisco Unified Communications Manager (UCM) and to configure a new Jabber user for the first time,
typing an incorrectly formatted user name in an unconfigured or manually configured Cisco Jabber client will
produce the following error message:
After Cisco Jabber has been correctly configured and registered with UCM for the first time, it is possible to log
in to Jabber with only a shortened form of the user name in the user name field, as shown in the following
exhibit:
However, if you mistype the user name or type a different, valid user name into the login field, Jabber will
prompt you to verify that you want to completely reset the client configuration, as shown in the following exhibit:
Clicking Reset would cause Jabber to delete the current configuration and attempt to replace it with a new one
for a different user name. Clicking Cancel returns the user to the login screen.
If Jabber had not been previously configured for a given user, Jabber would produce the following if provided
with a short invalid user name:
Cisco Jabber uses Session Initiation Protocol (SIP) to connect to UCM in softphone mode. SIP is an Internet
Engineering Task Force (IETF)standard call signaling protocol. Although SIP is typically used as a peer-to-peer
call signaling protocol, it can also operate in client/server mode. A softphone is software that behaves like a
phone, enabling a user to participate in voice sessions over a typical workstation network connection.
The Cisco Jabber client can be configured automatically by the UCM server or manually by clicking Advanced
Settings from the login screen. Regardless of the configuration method, the Trivial File Transfer Protocol
(TFTP) server and the Cisco Unified Communications Manager IP Phone (CCMCIP) server must be reachable
by the client on which Jabber is installed. If the TFTP server is not available or is misconfigured, the Jabber
client will not be able to download configuration files. If the CCMCIP server is not available or is misconfigured,Jabber cannot participate in instant messaging (IM) and Presence.
Cisco does not recommend configuring endpoints, whether they are desk phones or softphones like Cisco
Jabber, by using host names. Configuring the Jabber client with server information by using host names instead
of IP addresses could cause the error message in this scenario. When using host names or fully qualified
domain names (FQDNs), the Domain Name System (DNS) server or local hosts file must be present and
working. In addition, the Cisco Unified Presence (CUPS) server or IM and Presence server must be up and
working. Otherwise, the user might receive a Cannot communicate with the server error message when
attempting to log in, even if the login servers are correctly configured.https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deploymentinstallation-guide-ciscojabber/CJAB_BK_D6497E98_00_deployment-installation-guideciscojabber_chapter_01001.html
