The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Applies to all the Cisco Jabber clients.
multiResource (default)—Users can sign in to multiple instances of the client at the same time.
wbxconnect—Users can sign in to one instance of the client at a time. This option applies to cloud and hybrid deployments only.
The client appends the wbxconnect suffix to the user's JID. Users cannot sign in to any other Cisco Jabber client that uses the wbxconnect suffix.
mutualExclusion—Users can sign in to one instance of the client at a time. This option applies to all deployment types (on-premises, cloud, and hybrid). New sign ins automatically sign out users from older instances of the client.
Example: <LoginResource>mutualExclusion</LoginResource>
Example: <PresenceServerAddress>hostname</PresenceServerAddress>
Specifies the Central Authentication Service (CAS) URL for the Cisco WebEx Messenger service.
Example: <PresenceServerURL>https://loginp.webexconnect.com/cas/sso/ex_org/orgadmin.app</PresenceServerURL>
Applies to Cisco Jabber for Windows.
true - Users' presence changes to "In a WebEx meeting" even if they do not join the Cisco WebEx session link.
false (default) - Users must join the Cisco WebEx session link for their presence to change to "In a WebEx meeting". Otherwise, their presence remains "Available", even if the meeting is in their Microsoft Outlook calendar.
Example: <CalendarWebExMeetingPresence>true</CalendarWebExMeetingPresence>