Cisco Jabber 10.6 Planning Guide

Cisco Jabber 10.6 Planning Guide

C H A P T E R

6

Service Discovery

About Service Discovery, page 45

How the Client Locates Services, page 46

Cisco UDS SRV Record, page 48

CUP Login SRV Record, page 50

Collaboration Edge SRV Record, page 51

About Service Discovery

Service discovery enables clients to automatically detect and locate services on your enterprise network.

Clients query domain name servers to retrieve service (SRV) records that provide the location of servers.

The primary benefits to using service discovery are as follows:

• Speeds time to deployment.

• Allows you to centrally manage server locations.

Important

If you are migrating from Cisco Unified Presence 8.x to Cisco Unified Communications Manager IM and

Presence Service 9.0 or later, you must specify the Cisco Unified Presence server FQDN in the migrated

UC service on Cisco Unified Communications Manager. Open Cisco Unified Communications Manager

Administration interface. Select User Management > User Settings > UC Service.

For UC services with type IM and Presence, when you migrate from Cisco Unified Presence 8.x to Cisco

Unified Communications Manager IM and Presence Service the Host Name/IP Address field is populated with a domain name and you must change this to the Cisco Unified Presence server FQDN.

However, the client can retrieve different SRV records that indicate to the client different servers are present and different services are available. In this way, the client derives specific information about your environment when it retrieves each SRV record.

The following table lists the SRV records that you can deploy and explains the purpose and benefits of each record:

Cisco Jabber 10.6 Planning Guide

45

Service Discovery

How the Client Locates Services

SRV Record

_cisco-uds

Purpose

Provides the location of Cisco

Unified Communications Manager version 9.0 and later.

The client can retrieve service profiles from Cisco Unified

Communications Manager to determine the authenticator.

Why You Deploy

• Eliminates the need to specify installation arguments.

• Lets you centrally manage configuration in

UC service profiles.

• Enables the client to discover the user's home cluster.

As a result, the client can automatically get the user's device configuration and register the devices. You do not need to provision users with Cisco Unified Communications

Manager IP Phone (CCMCIP) profiles or

Trivial File Transfer Protocol (TFTP) server addresses.

• Supports mixed product modes.

You can easily deploy users with full UC,

IM only, or phone mode capabilities.

• Supports Expressway for Mobile and

Remote Access.

_cuplogin

Provides the location of Cisco

Unified Presence.

Sets Cisco Unified Presence as the authenticator.

• Supports deployments with Cisco Unified

Communications Manager and Cisco

Unified Presence version 8.x.

• Supports deployments where all clusters have not yet been upgraded to Cisco Unified

Communications Manager 9.

_collab-edge

Provides the location of Cisco VCS

Expressway or Cisco Expressway-E.

The client can retrieve service profiles from Cisco Unified

Communications Manager to determine the authenticator.

• Supports deployments with Expressway for

Mobile and Remote Access.

How the Client Locates Services

The following steps describe how the client locates services with SRV records:

1

The client's host computer or device gets a network connection.

When the client's host computer gets a network connection, it also gets the address of a Domain Name

System (DNS) name server from the DHCP settings.

46

Cisco Jabber 10.6 Planning Guide

Service Discovery

How the Client Locates Services

2

The user employs one of the following methods to discover the service during the first sign in:

• Manual—The user starts Cisco Jabber and then inputs an email-like address on the welcome screen.

• URL configuration—URL configuration allows users to click on a link to cross-launch Cisco Jabber without manually inputting an email.

• Mobile Configuration Using Enterprise Mobility Management—As an alternative to URL configuration, you can configure Cisco Jabber using Enterprise Mobility Management (EMM) with

Android for Work on Cisco Jabber for Android and with Apple Managed App Configuration on

Cisco Jabber for iPhone and iPad. You need to configure the same parameters in the EMM console that are used for creating URL configuration link.

To create a URL configuration link, you include the following:

• ServicesDomain—The domain that Cisco Jabber uses for service discovery.

• VoiceServicesDomain—For a hybrid deployment, the domain that Cisco Jabber uses to retrieve the

DNS SRV records can be different from the ServicesDomain that is used to discover the Cisco Jabber domain.

• ServiceDiscoveryExcludedServices—In certain deployment scenarios, services can be excluded from the service discovery process. These values can be a combination of the following:

• WEBEX

• CUCM

• CUP

Note

When all three parameters are included, service discovery does not happen and the user is prompted to manually enter connection settings.

Create the link in the following format: ciscojabber://provision?ServicesDomain=<domain_for_service_discover>

&VoiceServicesDomain=<domain_for_voice_services>

&ServiceDiscoveryExcludedServices=<services_to_exclude_from_service_discover>

Examples:

• ciscojabber://provision?servicesdomain=example.com

• ciscojabber://provision?servicesdomain=example.com

&VoiceServicesDomain=VoiceServices.example.com

• ciscojabber://provision?servicesdomain=example.com

&ServiceDiscoveryExcludeServices=WEBEX,CUCM

Provide the link to users using email or a website.

Note

If your organization uses a mail application that supports cross-launching proprietary protocols or custom links, you can provide the link to users using email, otherwise provide the link to users using a website.

3

The client gets the address of the DNS name server from the DHCP settings.

Cisco Jabber 10.6 Planning Guide

47

Service Discovery

Cisco UDS SRV Record

4

The client issues an HTTP query to a Central Authentication Service (CAS) URL for the Cisco WebEx

Messenger service.

This query enables the client to determine if the domain is a valid Cisco WebEx domain.

5

The client queries the name server for the following SRV records in order of priority:

• _cisco-uds

• _cuplogin

• _collab-edge

The client caches the results of the DNS query to load on subsequent launches.

The following is an example of an SRV record entry:

_cisco_uds._tcp.DOMAIN SRV service location: priority = 0 weight = 0 port = 8443 svr hostname=192.168.0.26

Cisco UDS SRV Record

In deployments with Cisco Unified Communications Manager version 9 and later, the client can automatically discover services and configuration with the _cisco-uds SRV record.

48

Cisco Jabber 10.6 Planning Guide

Service Discovery

The following figure shows how the client uses the _cisco-uds SRV record.

Figure 6: UDS SRV Record Login Flow

Cisco UDS SRV Record

1

The client queries the domain name server for SRV records.

2

The domain name server returns the _cisco-uds SRV record.

3

The client locates the user's home cluster.

As a result, the client can retrieve the device configuration for the user and automatically register telephony services.

Important

In an environment with multiple Cisco Unified Communications Manager clusters, you can configure the

Intercluster Lookup Service (ILS). ILS enables the client to find the user's home cluster and discover services.

If you do not configure ILS, you must manually configure remote cluster information, similar to the

Extension Mobility Cross Cluster (EMCC) remote cluster setup. For more information on remote cluster configurations, see the Cisco Unified Communications Manager Features and Services Guide.

4

The client retrieves the user's service profile.

The user's service profile contains the addresses and settings for UC services and client configuration.

The client also determines the authenticator from the service profile.

Cisco Jabber 10.6 Planning Guide

49

Service Discovery

CUP Login SRV Record

5

The client signs the user in to the authenticator.

The following is an example of the _cisco-uds SRV record:

_cisco-uds._tcp.example.com

priority = 6 weight = 30

SRV service location: port = 8443 svr hostname = cucm3.example.com

_cisco-uds._tcp.example.com

priority = 2

SRV service location: weight port

= 20

= 8443 svr hostname = cucm2.example.com

_cisco-uds._tcp.example.com

priority = 1

SRV service location: weight port

= 5

= 8443 svr hostname = cucm1.example.com

CUP Login SRV Record

Cisco Jabber can automatically discover and connect to Cisco Unified Presence or Cisco Unified

Communications Manager IM and Presence Service with the _cuplogin SRV record.

The following figure shows how the client uses the _cuplogin SRV record.

Figure 7: CUP SRV Record Login Flow

1

The client queries the domain name server for SRV records.

2

The name server returns the _cuplogin SRV record.

As a result, Cisco Jabber can locate the presence server and determine that Cisco Unified Presence is the authenticator.

50

Cisco Jabber 10.6 Planning Guide

Service Discovery

Collaboration Edge SRV Record

3

The client prompts the user for credentials and authenticates to the presence server.

4

The client retrieves service profiles from the presence server.

Tip

The _cuplogin SRV record also sets the default server address on the Advanced Settings window.

The following is an example of the _cuplogin SRV record:

_cuplogin._tcp.example.com

priority = 8 weight port

= 50

= 8443

SRV service location: svr hostname = cup3.example.com

_cuplogin._tcp.example.com

SRV service location: priority weight port

= 5

= 100

= 8443 svr hostname = cup1.example.com

_cuplogin._tcp.example.com

SRV service location: priority weight

= 7

= 4 port = 8443 svr hostname = cup2.example.com

Collaboration Edge SRV Record

Cisco Jabber can attempt to connect to internal servers through Expressway for Mobile and Remote Access to discover services with the following _collab-edge SRV record.

Cisco Jabber 10.6 Planning Guide

51

Collaboration Edge SRV Record

The following figure shows how the client uses the _collab-edge SRV record.

Figure 8: Collaboration Edge Record Login Flow

Service Discovery

1

The client queries the external domain name server for SRV records.

2

The name server returns the _collab-edge SRV record and does not return the _cuplogin or

_cisco-uds

SRV records.

As a result, Cisco Jabber can locate the Cisco Expressway-E server.

3

The client requests the internal SRV records (through Expressway) from the internal domain name server.

These SRV records must include the _cisco-uds SRV record.

4

The client obtains the internal SRV records (through Expressway).

As a result, the client can locate the Cisco Unified Communications Manager server.

5

The client requests the service profiles (through Expressway) from Cisco Unified Communications Manager.

6

The client retrieves the service profiles (through Expressway) from Cisco Unified Communications

Manager.

The service profile contains the user's home cluster, the primary source of authentication, and the client configuration.

52

Cisco Jabber 10.6 Planning Guide

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents