Which option describes how you can show the same contacts in your Jabber for Windows on-premise client as you do on the corporate directory of your IP phone?
LDAP contact resolutionThe client cannot use LDAP for contact resolution when outside of the corporate firewall.
Instead, the client must use UDS for contact resolution.
When users are inside the corporate firewall, the client can use either UDS or LDAP for contact resolution.
If you deploy LDAP within the corporate firewall, Cisco recommends that you synchronize your LDAP directory server with Cisco Unified Communications Manager to allow the client to connect with UDS when users are outside the corporate firewall.
References: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97/ JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97_chapter_0111.html#CJAB_CN_C2733196_00
Jabber for Windows on-premise client is an instant messaging and collaboration tool used in Cisco Unified Communications environment. One of the common requirements in such an environment is to have a consistent set of contacts across different endpoints and applications, such as IP phones, Jabber clients, and corporate directories.
To show the same contacts in Jabber for Windows as in the corporate directory of an IP phone, you need to ensure that both endpoints are using the same source of contact information. Here are the explanations for each of the options given:
A. Switch your Jabber client to use UDS instead of EDI. Jabber for Windows supports two protocols for retrieving contact information: User Data Service (UDS) and Enterprise Directory Integration (EDI). UDS is a protocol used to retrieve user and device information from Cisco Unified Communications Manager (CUCM) and IM&P server. EDI, on the other hand, is a protocol used to retrieve directory information from a corporate directory, such as Microsoft Active Directory or LDAP. If you want to show the same contacts in Jabber as in the corporate directory of an IP phone, you need to switch your Jabber client to use EDI instead of UDS. Therefore, option A is incorrect.
B. Switch your Jabber client to use EDI instead of UDS. As explained in option A, to show the same contacts in Jabber for Windows as in the corporate directory of an IP phone, you need to switch your Jabber client to use EDI instead of UDS. This option is correct.
C. Update your IM&P server to sync off of the same LDAP directory as your Cisco Unified Communications Manager. IM&P server is the messaging and presence component of Cisco Unified Communications. It can integrate with various directory sources, such as LDAP, to retrieve contact information. However, updating the IM&P server to sync off the same LDAP directory as CUCM does not necessarily ensure that the same contacts will be shown in Jabber for Windows and the corporate directory of an IP phone. The reason is that the two endpoints may still use different protocols to retrieve contact information, as explained in options A and B. Therefore, option C is incorrect.
D. Add Jabber to your inbound/outbound firewall rules on your P. Firewall rules determine which traffic is allowed to pass through a network boundary, such as between an enterprise network and the internet. Adding Jabber to inbound/outbound firewall rules does not have any direct impact on the visibility of contacts in Jabber for Windows. Therefore, option D is incorrect.
E. Jabber can only pull directly from LDAP and cannot directly search the Cisco Unified Communications Manager user database. This statement is incorrect. As explained in options A and B, Jabber for Windows can pull contact information from both LDAP and CUCM user database, depending on the protocol used. Therefore, option E is incorrect.
In conclusion, the correct answer to the question is B: switch your Jabber client to use EDI instead of UDS.