Note	Mobile application management currently isn't supported for Webex Meetings Online customers.

• The Mobile Application Management (MAM) wrapper program's focus is to make IPA and APK files available to customers outside of app stores for MAM integration purposes. This program is provided free of charge (normal Jabber and Webex licensing costs do apply).

• Cisco doesn't test any MAM wrappers or SDK integrations with Jabber or Webex, and only supports the unwrapped (latest released) version of Jabber and Webex. Any issues that customers find with the modified versions of Jabber or Webex must be reproduced with the unwrapped versions before submitting a Cisco support case.

• While others may test their integrations with Cisco applications, Cisco cannot make any support statement around those integrations.

• Integrations may sandbox applications, meaning that some interaction with other apps (such as Webex cross-launch) may not perform correctly.

• Cisco only supports the latest version of Cisco Jabber, Webex App, and Webex Meetings mobile apps. As a result, there’s an expectation that customers upgrade their user bases once Cisco releases new versions in the App Store and Google Play Store. These versions will also be available through the MAM program.

• Even if an initial MAM integration is successful, subsequent changes to the ecosystem including OS updates, new devices, new Jabber or Webex versions, and new wrappers, SDKs, or other software versions could break subsequent integrations. As such, we recommend that customers participate in our Early Adopter Program (EAP) also to ensure that updates to Jabber do not break use cases that the customer is targeting.

The Mobile Application Management License Agreement is an agreement that's made between Cisco and another organization or licensee looking to wrap the mobile application.

For more information, contact your Site Administrator or CSM .

You can use your own domain in the Jabber client to login. It is necessary to understand how the Jabber client authentication works and why the certificates are checked for particular SAN entries.

During the TLS handshake, a standard TLS client checks the validity of the TLS server certificate. However, this implementation could potentially bring in 'man-in-the-middle' attack, when Jabber deploys over the internet. During login, if an hacker presents Jabber their own server with a valid TLS certificate instead of the expressway, then Jabber in the absence of further control, it accepts that certificate, and the user can be connected to a malicious system. To avoid this issue, Jabber performs an additional validation step which is not part of the standard TLS, it checks that the domain entered during the login process by the user matches the Subject Alternative Names (SAN) included in the certificate. Only if it matches, Jabber tries to connect to the Expressway. Any SAN entry made in the certificate requires to be signed by the Certification Authority (CA), which means only the company that owns the domain will be able to get a CA-signed certificate.

Any SAN entered in the certificate is subject to validation from the Certification Authority (CA), so only the company that owns the domain is able to get a CA-signed certificate. It makes it much more difficult to steal the identity of the Expressway.

In Dedicated Instance Cisco manages the certificates for the UC applications and hence the certificates are signed with the Cisco provided domain only, for example, customer.amer.wxc-di.webex.com. However, for an end user to login to the Jabber client with the customer email address, can be achieved by the following options:

Option 1 - Jabber Initial End User Login

The users can be communicated that for their initial login to the Jabber client, they need to use the Cisco’s voice service domain user@customer.amer.wxc-di.webex.com in the initial screen followed by their username or company’s email address and password in the next screen. Since this is most simplest approach, the steps are illustrated more in detail:

1. The user needs to enter the Cisco provided voice service domain, for example: user@customer.amer.wxc-di.webex.com in the initial Jabber login screen as show in the figure below.

   

   Note	The customer’s voice service domain is shared by Cisco for every region when the service activation is completed. This information is part of the access details document shared in the Webex App space. For more details, see Dedicated Instance Service Activation.

2. The user is prompted to enter the username or company’s email id along with the password for authentication as shown in the figure below.

   

   Note	If SSO is enabled, similar operation will be performed by the IdP.

Subsequent logins after this does not require the user to perform Step 1, unless the Jabber client is reset.

Use the Voice Service Domain

With this approach the Jabber client can differentiate between the customer’s domain entered by the user and the service discovery domain. In the installer if the voice service domain is set to customer.amer.wxc-di.webex.com, the user can login to the Jabber client using their company’s email address and Jabber can still do the service discovery based on the value set in voice service domain. This will remove the necessity to provide voice service domain in the initial jabber login as per the above option.

For Windows:

Tools such as Microsoft Orca can be used to create custom Jabber installers, that can include the voice service domain. The users can be instructed to use these installers for Jabber client.

For MAC, iOS, Android:

Tools such as MDM can be used to create custom Jabber installers, that can include the voice service domain.

Use the Configuration URL

A configuration URL can be used to set Jabber parameters before the initial login, such as the voice services domain. An example of a configuration URL: ciscojabber://provision?ServicesDomain=customer.com&VoiceServicesDomain=customer.amer.wxc-di.webex.com

By clicking the above link, the voice service domain can be set in Jabber client running on MAC, Android or iOS devices.

Note

This configuration is not persistent, the user would need to click on the link again if the Jabber client is reset. It is worth to note that Webex App does not have the above requirement; the client performs the domain check, but it is possible to provision the voice service domain in the Control Hub. When the Webex App connects to Webex, it gets the voice services domain and registers the same. For more information regarding Webex App In-app calling setup, see Webex Application Integration with Dedicated Instance for In-App Calling.

Useful Link: On-Premises Deployment for Cisco Jabber 14.0

Jabber can be set up to make calls from the Webex App.

Depending upon the user’s calling license, the calling behavior options can be set up.

• For Unified CM licensed users, you can set up to make calls directly from the Cisco Jabber or through the Webex App, and choose the domain (organization domain or UC Manager profile) that gets applied to the users. You can configure the settings at organization level, group level, and user level.

• For users without paid calling services from Cisco, you can set up third-party applications to initiate calls. By default, all calls through the Webex App use "Call on Webex" option. You can configure the settings at the organization level.

• For Webex Calling licensed users, the Webex App is the default calling application to make calls. Hence, no specific calling behavior configuration is needed.

For more information, see the Set up calling behavior article.

If you are a moderator or an administrator, you can add people to persistent chat rooms. When you add people who have not already signed up to Cisco Jabber, they'll get a notification after they sign in for the first time.

Organization Administrator only

You can add custom emoticons to Cisco Jabber for Windows by creating emoticon definitions in an XML file and saving it to the file system. To achieve optimal results, your custom emoticons should conform to the following guidelines:

• Dimensions: 17 x 17 pixels

• Transparent background

• PNG file format

• RGB colors

Note

Custom emoticon definitions are available to users only if they are defined locally in emoticonDefs.xml. If you send custom emoticons to users who do not have the same emoticon definitions, those users receive the default keys, not the icons; for example: User A defines a custom emoticon in emoticonDefs.xml. The custom emoticon definition exists only on User A's local file system. User A sends that custom emoticon to User B. User B receives only the default key for the custom emoticon. User B does not receive the icon.

Emoticon Definitions

Cisco Jabber for Windows loads emoticon definitions from emoticonDefs.xml. The following XML snippet shows the basic structure for the emoticon definitions file:

• <emoticons>
• <emoticon defaultKey=" image=" text=" order=" hidden=">
• <alt></alt>
• </emoticon>
• </emoticons>

The following table describes the elements and attributes for defining custom emoticons:

When your users are in Cisco Webex and also in Cisco Jabber, you can use the interoperability setting to allow people in both apps to communicate with each other.

Note	This article provides interoperability between your cloud-based Jabber deployment and Webex. This is different to the interoperability between on-premises Jabber deployments and Webex users (see https://www.cisco.com/go/hybrid-services-message for more on that deployment).

With the Cisco Webex / Jabber Interop setting enabled:

• People can send or receive messages between Webex and Jabber apps.

• Jabber users see a status of On Cisco Webex, when their contact is using Webex.

Deployment Requirements

Supported for Cisco Jabber cloud deployments only.

Before you enable this setting, check the following:

• Your organization must be added to the Cisco Platform identity service. You can check in Cisco Webex Control Hub to see if your organization has been added. If your organization hasn't been added, you can contact the Cisco Customer Support team or your Cisco Customer Success Manager to request that your organization is added to the Cisco Platform identity service. This process to add users to the identity service takes some time to complete.

  For more information on the request process for Cisco Customer Support or Cisco Customer Success Manager, see this support article.

  Cisco Jabber (Webex Messenger) and Webex domains must be identical for the Webex Messenger Org to be synched into the Cisco Platform identity service.

  Cisco Directory Connector must be disabled in Control Hub, as this method of managing users is not compatible with how users are managed in a Jabber cloud deployment.

• If you use Single Sign On (SSO) for Webex Messenger then you must set up SSO for Cisco Platform identity service. For more information about configuring SSO, see the Cisco Webex Messenger Install and Upgrade documentation.

Known Limitations

• Users can only send text between Jabber and Webex, sending any other content is not supported.

• You can only send messages in a space with one person, you can't send messages in group spaces.

• End-to-end AES encryption is not supported.

• All users must have the Cisco Webex / Jabber Interop setting enabled.

  When a Jabber user without interop enabled attempts to send a message to an interop enabled user who isn't signed in to Jabber, they receive this message This user is currently offline in Jabber and the message cannot be delivered.

Jabber Requirements

Cisco Jabber clients 11.9 or later.

Ensure the following parameter is set to False in the jabber-config.xml file:<Persistent_Chat_Enabled>False</Persistent_Chat_Enabled>

AES encryption must be disabled in Cisco Webex Messenger Administration Tool (Org Admin). In the Policy Editor tab, disable the Support End-To-End Encryption for IM setting.

Cisco Webex Control Hub Settings

You can enable the Cisco Webex / Jabber Interop setting in Control Hub for your entire organization and then for specific people. The setting is also available as one of the services to choose in the CSV file user setup.

You can integrate Slack messaging with Cisco Calling to make voice and video calls from within the application using the Dedicated Instance service.

Slack can be used by Dedicated Instance customers to integrate Slack messaging with Cisco Calling. The Cisco Jabber calling application or Cisco Webex calling application for Slack is a plug-in application within Slack that enables a Slack user to make voice and video calls from within the application using the Dedicated Instance service.

The Slack user installs the Cisco Calling application within Slack in his/her personal device. Webex application or Jabber application must be already installed and registered with Dedicated Instance following all Dedicated Instance requirements. When both installations are done, Slack can make calls using Dedicated Instance Call Control. The Slack support provides the following features within Dedicated Instance for end users:

• Make calls directly from the Slack client through the Unified CM

• Call using the chat window using the Slack application call icon

• Call using the slash option of the Slack application