Configuration URL Workflow
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
|
|
Step 2 |
Configuration URL
To enable users to launch Cisco Jabber without having to manually enter service discovery information, create and distribute a configuration URL to users.
You can provide a configuration URL link to users by emailing the link to the user directly, or by posting the link to a website.
-
ServicesDomain—Required. Every configuration URL must include the domain of the IM and presence server that Cisco Jabber needs for service discovery.
-
VoiceServiceDomain—Required only if you deploy a hybrid cloud-based architecture where the domain of the IM and presence server differs from the domain of the voice server. Set this parameter to ensure that Cisco Jabber can discover voice services.
-
ServiceDiscoveryExcludedServices—Optional. You can exclude any of the following services from the service discovery process:
-
Webex—When you set this value, the client: -
Does not perform CAS lookup
-
Looks for:
-
_cisco-uds
-
_cuplogin
-
_collab-edge
-
-
-
CUCM—When you set this value, the client: -
Does not look for _cisco-uds
-
Looks for:
-
_cuplogin
-
_collab-edge
-
-
-
CUP—When you set this value, the client: -
Does not look for _cuplogin
-
Looks for:
-
_cisco-uds
-
_collab-edge
-
-
You can specify multiple, comma-separated values to exclude multiple services.
If you exclude all three services, the client does not perform service discovery and prompts the user to manually enter connection settings.
-
-
ServicesDomainSsoEmailPrompt—Optional. Specifies whether the user is shown the email prompt for the purposes of determining their home cluster.
-
ON
-
OFF
-
-
Telephony_Enabled—Specifies whether the user has phone capability or not. The default is true. -
True
-
False
-
-
ForceLaunchBrowser—Used to force user to use the external browser. Applies to Cisco Jabber mobile clients. -
True
-
False
Note
ForceLaunchBrowser is used for client certificate deployments and for devices with Android OS below 5.0.
-
ciscojabber://provision?ServicesDomain=<domain_for_service_discover>
&VoiceServicesDomain=<domain_for_voice_services>
&ServiceDiscoveryExcludedServices=<services_to_exclude_from_service_discover>
&ServicesDomainSsoEmailPrompt=<ON/OFF>
Note |
|
-
ciscojabber://provision?ServicesDomain=cisco.com
-
ciscojabber://provision?ServicesDomain=cisco.com &VoiceServicesDomain=alphauk.cisco.com
-
ciscojabber://provision?ServicesDomain=service_domain &VoiceServicesDomain=voiceservice_domain&ServiceDiscoveryExcludedServices=WEBEX
-
ciscojabber://provision?ServicesDomain=cisco.com &VoiceServicesDomain=alphauk.cisco.com&ServiceDiscoveryExcludedServices=CUCM,CUP
-
ciscojabber://provision?ServicesDomain=cisco.com &VoiceServicesDomain=alphauk.cisco.com&ServiceDiscoveryExcludedServices=CUCM,CUP &ServicesDomainSsoEmailPrompt=OFF
Provide Users with Configuration URL from a Website
You can provide a configuration URL link to users by emailing the link to the user directly, or by posting the link to a website.
Note |
Due to a limitation of the Android operating system, Cisco Jabber for Android users can encounter an issue if they open the configuration URL directly from an Android application. To work around this issue, we recommend that you distribute your configuration URL link using a website. |
If you want to use the website explore option for URL provisioning, we recommended you to use Mozilla Firefox.
Use the following procedure to distribute the link from a website.
Procedure
Step 1 |
Create an internal web page that includes the configuration URL as an HTML hyperlink. |
Step 2 |
Email the link to the internal web page to users.
|