Method for Installing Jabber for windows
“User the Command Line”or “Create a Custom Installer”aims to specifying some login & system-level config parameters (such as whether clear existing bootstrap file, Server Type[CUP, Webex or CUCM], Server IP address, Domain, Install Language, Phone Mode, etc) during Installation. All those parameters are stored in a Bootstrap file (jabber-bootstrap.properties file – location: C:\ProgramData\Cisco Systems\Cisco Jabber) which will be read by Jabber for every login attempt.
“Run the MSI Manually”suits for a fresh install without any login & config parameters specified. When user logins, he has to manually select server type, server IP address etc. Note that, this install method will not clear local existing Bootstrap file and that might result in unexpected login results.
The jabber-bootstrap.properties file enables you to change login or system-level configs for Jabber client even when jabber is already installed. For example, edit jabber-bootstrap.properties file (location: C:\ProgramData\Cisco Systems\Cisco Jabber) and type UseLanguageID:1033 to change the client language.
Events Sequence for Jabber Login
NOTE: According to PDI Helpdesk, basic Presence Profile Settings such as Voicemail profile, conference profile, CCMCIP profile, CTI Gateway profile, Audio profile configured under CUP Admin GUI>Application>Cisco Jabber>User Settings, are applied to Jabber clients automatically without any other actions. However, for LDAP Profiles, Deskphone/Softphone credential source, client policy such as file transfer, video, screen capture etc configured under CUP Admin GUI>Application>Cisco Jabber>Settings are not immediately applied to Jabber clients until jabber-config.xml file is created and uploaded.
- Locate CUP server for authentication and retrieving service profiles. IP address or FQDN of CUP could be obtained by jabber in many ways:
-> manually specified by user when login.
-> refer to Bootstrap file for Server address.
-> Automatically discover CUP server based on local workstation`s domain.
- Phone mode deployment (manual specified when login or as per Bootstrap file config)
If softphone mode, Jabber contact TFTP address obtained from service profile and download the configure file for CSF device
If desk phone control mode, Jabber contact CCMCIP for controlled device list, and setup CTI link to CTI Gateway Server.
How to disable multiple instance Jabber login for the same user
Perhaps group policy could help on this issue. or through LOGIN_RESOURCE config.
Jabber for Windows Integrating with LDAP
- Jabber can integrate with LDAP server as a Authentication & Contact Source. As mentioned above, LDAP Profile configuration will not take effect on Jabber client until you create and upload the jabber-config.xml as per below link.
Create and upload Global Config file (jabber-config.xml)
- It is recommended that Jabber connects Global Catalog (TCP port 3268) to fetch contact info for the sake of high efficiency. However, by default, some user attributes you desired might not yet be replicated to Global Catalog on LDAP server. In order to make sure that your desired user attributes are accessible on Global Catalog from you Jabber client, you need to expand (replicate user attributes from domain to Global Catalog) User Attribute Schema of Global Catalog through Schema Manager MMC console following below link.
Creating a Schema Manager MMC Console on Windows Server 2003
- Contact Resolve & Predictive Contact Search
On LDAP server, you need to index the attributes based on which jabber can use to resolve contacts.
In terms of contact search, there are 3 contact source for jabber to search, Local Address Book, Local Contact Cache, and LDAP Server. To enable Predictive Contact Search on specific user attribute, you need to activate index & Ambiguous Name Resolution (ANR) for that attribute on LDAP server through Schema Manager MMC console.
Contact Resolve & Predictive Contact Search.
What is CCMCIP used for?