How To Configure Cisco Spark Hybrid Service In Expressway

Deploy Cisco Webex Hybrid Message Service

Annals Superhighway-C Connector Hosts to the Webex Cloud

Webex Hybrid Services use software connectors hosted on Expressway-C to deeply connect Webex to your organization's environs. Use this procedure to annals Freeway-C resources to the cloud.

After yous complete the registration steps, the connector software is automatically deployed on your on-premises Pike-C.

Before yous begin

• Make certain your Expressway-C is running on a version that's supported for hybrid services. Run into the Supported Versions of Expressway for Cisco Webex Hybrid Services Connectors documentation (https://help.webex.com/article/ruyceab) for more data about which versions are supported for new and existing registrations to the deject.

• Sign out of whatsoever open up connections to the Throughway-C interface that are open in other browser tabs.

• If your on-bounds environs proxies the outbound traffic, you must first enter the details of the proxy server on before you lot complete this procedure. Doing so is necessary for successful registration.

Procedure

---

Stride 1	Sign in to the customer view of https://admin.webex.com/login.
Step two	In the left-hand navigation pane, under Services click Hybrid and then choose one: If this is the start connector host you're registering, click Set up on the carte du jour for the hybrid service you're deploying, and and so click Adjacent. If you've already registered i or more connector hosts, click View all on the card for the hybrid service yous're deploying, and then click Add Resource. The Webex cloud rejects whatsoever endeavor at registration from the State highway web interface. You must first annals your Pike through Control Hub, considering the Control Hub needs to mitt out a token to the Expressway to constitute trust betwixt premises and cloud, and complete the secure registration.
Stride three	Choose a method to register the Pike-C: New Expressways—choose Annals a new Expressway with its Fully Qualified Domain Name (FQDN), enter your Superhighway-C IP accost or fully qualified domain name (FQDN) then that Webex creates a record of that Expressway-C and establishes trust, and then click Side by side. You lot tin also enter a display name to identify the resource in Control Hub. Caution To ensure a successful registration to the deject, use but lowercase characters in the hostname that you set for the Superhighway-C. Capitalization is not supported at this time. Existing Expressways—cull Select an existing State highway cluster to add resources to this service, and so choose the node or cluster from the drop-down that you previously registered. You can utilize it to run more than one hybrid service. Tip If you're registering a cluster, register the primary peer. You don't need to register any other peers, because they register automatically when the primary registers. If you start with i node set up as a master, subsequent additions do not require a organization reboot.
Step 4	Click Next, and for new registrations, click the link to open up your Expressway-C. You tin can then sign in to load the Connector Management window.
Step 5	Decide how you desire to update the Expressway-C trust list: A check box on the welcome page determines whether y'all will manually append the required CA certificates to the Expressway-C trust list, or whether you allow Webex to add those certificates for yous. Choose one of the post-obit options: Check the box if you want Webex to add the required CA certificates to the Expressway-C trust list. When you annals, the root certificates for the regime that signed the Webex deject certificates are installed automatically on the Superhighway-C. This means that the Expressway-C should automatically trust the certificates and be able to gear up the secure connection. Note If you change your listen, you tin use the Connector Management window to remove the Webex cloud CA root certificates and manually install root certificates. Uncheck the box if you lot want to manually update the Expressway-C trust list. Run into the Expressway-C online help for the process. Caution When you register, you will get certificate trust errors if the trust listing does not currently have the right CA certificates. See Certificate Authorities for Hybrid Services.
Pace half dozen	Click Annals . After you're redirected to Control Hub, read the on-screen text to confirm that Webex identified the correct State highway-C.
Footstep 7	Subsequently you verify the information, click Allow to register the Motorway-C for Webex Hybrid Services. Registration can accept up to 5 minutes depending on the configuration of the Expressway and whether information technology'due south a first-time registration. After the Expressway-C registers successfully, the Webex Hybrid Services window on the Expressway-C shows the connectors downloading and installing. The direction connector automatically upgrades itself if in that location is a newer version available, and then installs any other connectors that you selected for the Expressway-C connector host. Each connector installs the interface pages that you need to configure and activate that connector. This process tin can have a few minutes. When the connectors are installed, you lot can see new carte items on the menu on your Motorway-C connector host. Troubleshooting Tips If registration fails and your on-bounds surround proxies the outbound traffic, review the Before You Begin section of this procedure. If the registration procedure times out or fails (for example, y'all must gear up document errors or enter proxy details), you can restart registration in Control Hub.

---

Certificate Government for Hybrid Services

The tabular array lists the Certificate Government that your on-premises or existing surround must trust when using Webex Hybrid Services.

If yous opted to have Webex manage the required certificates, then you exercise non need to manually append CA certificates to the Pike-C trust list.

Note

The issuers used to sign the Webex host certificates may change in time to come, and the tabular array below may and so be inaccurate. If you are manually managing the CA certificates, y'all must append the CA certificates of the issuing government that signed the currently valid certificates for the hosts listed below (and remove expired/revoked CA certificates).

Cloud hosts signed by this CA	Issuing CA	Must exist trusted by	For this purpose
CDN	O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root	Superhighway-C	To ensure State highway downloads connectors from a trusted host
Common identity service	O=VeriSign, Inc., OU=Grade iii Public Primary Certification Authority	Windows Server 2003 or Windows Server 2008 hosting the Cisco Directory Connector State highway-C	To synchronize users from your Active Directory with Webex and to authenticate Webex Hybrid Services users
Webex	O=The Go Daddy Group, Inc., OU=Go Daddy Form 2 Certification Dominance	Motorway-C

Configure an Awarding Account for Message Connector

Configure an business relationship for Message Connector to admission the AXL API of the Cisco Unified Communications Manager IM and Presence Service. You must utilize an independent administrator business relationship, not the main administrator account. Remember the details of this business relationship so y'all can enter them in the Message Connector configuration after.

Procedure

---

Pace 1	From Cisco Unified CM Administration, get to , and then choose ane: Click Find and, from the list, choose the administrator account that the connector will apply to communicate with Cisco Unified Communications Director IM and Presence Service. Click Add New to create a new awarding user account.
Step ii	Configure the account with the Standard AXL API Admission office.
Stride 3	Click Salve .

---

Configure the Connexion to IM and Presence Service

To enable Hybrid Message Service, yous must link Bulletin Connector to your IM and Presence Service cluster past entering server information for the publisher node. This step builds a span between IM and Presence Service and the Webex deject, with the connector interim as a broker between the two.

On each Freeway cluster that y'all are using for Hybrid Message Service, sign in to the master node and consummate the following configuration:

Before you begin

• Configure an Awarding Account for Message Connector

• The connector on Throughway maintains a resilient connectedness betwixt your Hybrid Bulletin Service cluster and the deject. You lot merely need to add the publisher to the Expressway-C connector configuration. If a specific node goes down in the cluster, the connector volition movement to another server.

Procedure

---

Step 1	Go to
Step ii	Click New.
Pace 3	Enter the hostname or IP accost of the IM and Presence Service publisher node that has Cisco AXL Web Service enabled. The connector uses AXL to query the publisher and discover the other nodes in the cluster.
Stride iv	Enter the credentials of the Message Connector AXL account you lot created on the IM and Presence Service publisher. Note This must non be the main administrator account. You must create an account explicitly for the Message Connector.
Footstep 5	(Optional) Change Certificate validation to Disabled if yous desire Expressway to waive the cheque on the server certificate from the publisher node. If certificate validation is enabled (which is the default), and so the tomcat document from the IM and Presence Service node must be valid and signed by a CA that the Motorway trusts. If you are using a self-signed certificate, re-create it into the Expressway'southward Trusted CA certificate list.
Stride vi	Click Add to store the connector configuration on the Motorway-C.
Step seven	Repeat this chore if you need to connect this Pike cluster to any other IM and Presence Service clusters.

---

What to do next

Start the Message Connector

Start the Message Connector

Manually enable the Message Connector afterward you lot configured the connector with the IM and Presence publisher and the AXL account.

Procedure

---

Step 1	From Expressway-C, get to , and so click Message Connector .
Step 2	Choose Enabled from the Active driblet-down listing.
Footstep iii	Click Relieve . The connector starts and the status changes to Running on the Connector Management window.

---

Verify the Connector Condition

Verify that the Message Connector is running, before you enable users for Hybrid Message Service.

Process

---

From Expressway-C, go to . Verify the configuration items in the Condition column.

---

What to practice next

Enable Hybrid Message Service for Users

Enable Hybrid Message Service for Users

Utilise this procedure to enable Webex App users i at a time for Hybrid Message Service.

See Ways to Add and Manage Users in Your Arrangement (https://collaborationhelp.cisco.com/article/nj34yk2) for other methods, such as using a bulk CSV template or Active Directory synchronization through Cisco Directory Connector.

Note

When yous apply majority import or directory synchronization to import users, users must have email addresses in the source system. Those must exist the addresses they utilize for Webex App because you map them to the Webex user ID. If a user does non take an electronic mail address in IM and Presence Service, the Message Connector cannot detect the user. Hybrid Bulletin Service does non piece of work for that user. Using Cisco Directory Connector you tin can map a chosen attribute (eg. the mail aspect or the userPrincipalName attribute) to the Webex UID, just the value of the attribute must be the user'southward electronic mail accost.

Procedure

---

Step i	From the customer view in https://admin.webex.com, become to Users , choose a specific user from the listing, or use the search to narrow the list, and so click the row to open an overview of the user.
Step 2	Click Edit, and then ensure that the user is assigned at to the lowest degree one paid service under Licensed Collaboration Services. Brand necessary changes, and then click Save.
Stride 3	Click Message Service, toggle the setting to plow it on, and and so save your changes. The user experiences a delay of upwards to one hour earlier reliably being able to send messages from Webex to Cisco Jabber.

---

Test Hybrid Bulletin

Before you begin

Y'all need at least ii users who are enabled for Hybrid Message. They should both have Cisco Jabber and Webex App installed.

Procedure

	Command or Action	Purpose
Step one	One user opens Webex App client.	Let'south call this person user A or Alice for the sake of this process.
Pace two	The other user opens Cisco Jabber client.	Let's call this person user B or Bob for the sake of this procedure.
Pace 3	Send a message from Alice's Webex App customer to Bob'southward Jabber client.
Pace 4	Check that the bulletin arrives in Bob'south Jabber client and that Alice's status shows in that location equally "Bachelor".
Pace five	Reply from Bob'due south Jabber client to Alice's Webex App customer.
Footstep 6	Check in Alice's Webex App client that Bob appears to be typing.
Pace 7	Echo the exam, starting from Alice's Jabber client and Bob's Webex App client.

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/spark/hybridservices/messageservice/cmgt_b_spark-hybrid-message-deployment-guide/cmgt_b_spark-hybrid-message-deployment-guide_chapter_010.html

Posted by: rileylecrid.blogspot.com

Share this post