[Index]
To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com
This procedure adds a Webex Teams service.
Webex Teams Feature Reference
Prequisites:
To allow VOSS-4-UC to connect to the Webex Teams Cloud API, obtain the following from the Cisco Webex page:
Perform these steps:
Log in to the Admin GUI as a provider or reseller administrator.
Select the hierarchy path to the correct customer node.
Select Services > Webex Teams > Access Token to display Webex Teams Account.
The form opens on a separate tab, at the following URL: https://us-central1-webex-teams-auth-token.cloudfunctions.net/webex_teams_oauth
Click the GET TOKENS link.
In the Email address field on the Cisco Webex page, enter a valid email address; then, click Next.
An email address and password are only required the first time you log in to the Cisco Webex site.
In the Password field on the Cisco Webex page, enter a valid password; then, click Sign In.
View the codes/tokens generated and displayed on the form:
- Organization ID
- Access Token (14 days)
- Refresh Access Token (90 days)
Note
- VOSS-4-UC automatically refreshes the access tokens every 7 days. To manually refresh the access tokens, click GET TOKENS on the Webex Teams Account form or Action > Refresh Access Token on the Customer Access form.
- The Refresh Token is valid for 90 days. The number of valid days remaining for the access token is displayed in the Refresh Token Expires in counter on the Webex Teams Access Token Management for VOSS4UC page.
- See https://developer.webex.com/docs/integrations for more details on access token management.
Click on each Copy button in turn to copy the item, return to the VOSS-4-UC tab, and paste in the appropriate field on the Customer Access form. Note that the access tokens must also be pasted into the 'Repeat' fields.
Fill out, at minimum, the other mandatory fields on the Customer Access form under Account Details:
Field | Description |
Webex Teams Customer Name | Populated automatically, using the customer name. |
Default Calling Behaviour | Can be applied to synced in users, if also set in Global Settings (Automatically apply default calling behaviour on Webex Teams user data sync) |
Use Organization's Domain | Can be enabled if you select option Calling in Webex Teams (Unified CM) (same as Webex Teams Control Hub behavior) When selected, you may also enable Default UC Manager Profile |
Email Domain for Hybrid Calling in Workspaces | When hybrid calling is enabled for a workspace, a dummy subscriber email domain can be added. |
Subscription ID | Fill out the subscription ID (as seen on the Control Hub portal) to selectively manage multiple subscriptions in multiple sites. If required, fill out the newly managed subscription ID here. |
Site URL | The site URL for Webex Enterprise Edition meeting services. When syncing licenses and subscriptions, VOSS-4-UC only syncs in subscriptions matching the ID and services from the site. See also Webex Teams Licenses |
Enterprise Content Management Enabled and | These settings match the configuration setting on the |
Jabber Team Messaging Mode Enabled | user feature of the Webex Teams Control Hub, and apply to the corresponding Default Calling Behaviour selection: Calling in Webex Teams (Unified CM) and Cisco Jabber app. Note that with these calling behaviour options, Quick Add Group Templates for Jabber devices under the Webex Teams group are applied. See Quick Add Subscriber Group Default Model |
UC Manager Profiles | Added for use when managing users. |
HTTP Proxy String | Required only if a proxy server is required to connect to the Webex Teams cloud, for example: http://[ip address]:port |
HTTPS Proxy String | Required only if a proxy server is required to connect to the Webex Teams cloud, for example: https://[ip address]:port |
Click Save. The Webex Teams Service is added.
Sync the Webex Teams Users for the customer. To do this, click Action > Sync Webex Teams Users on the Customer Access form.
Note
Webex Teams Users can also be synced from Administration Tools > Data Sync, and then running the SyncSpark[Customer] data.
Workflow Animation
The animation demonstrates how to create a Webex Teams service.
This relation implements the workflows to manage Spark Customer connection parameters and enabled services.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Customer Name * | Name of this customer |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Organization Account Number * | This can be found when logging into the Webex Teams Admin portal under the My Company Info section |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Default Calling Behaviour | This is the default calling behaviour for the organization. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Use Organization's Domain | This is the global setting that determines whether to use the Webex Teams organization domain for Calling in Webex Teams (Unified CM). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Default UC Manager Profile | This is the default UC Manager Profile for when the calling behaviour is Calling in Webex Teams (Unified CM). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Subscription ID | This is the Subscription ID to be used for license selection e.g. Sub160730. Only licenses of this Subscription ID will be synced into VOSS-4-UC and be assignable to users. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Site URL | This is the Site URL to use for assigning 'Meeting - Webex Enterprise Edition' licenses. If this is not set, the license will not be synced into VOSS-4-UC and will not be assignable to users |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Email Domain for Hybrid Calling in Workspaces | This is the email domain that will be used when creating a Unified CM user associated with a Workspace in Webex Teams Control Hub for hybrid calling. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enterprise Content Management Enabled | This setting must be enabled if Content Management is enabled in Webex Teams Control Hub. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Jabber Team Messaging Mode Enabled | This setting must be enabled if Jabber Team Messaging Mode is enabled in Webex Teams Control Hub. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
UC Manager Profiles | This list of UC Manager profiles must be configured to match the list of profiles in Webex Teams Control Hub. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Admin Access Token | This is the Access Token provided when logging into Webex Teams Developer portal. This token is valid for 14 days. The Refresh token can be used to generate a new Access Token. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Refresh Token | This is the Refresh Token provided when logging into Webex Teams Developer portal. This token will be used to create a new access token. The refresh token is valid for 90 dyas. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Access Token Expires In | Time when the Access Token will expire. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Refresh Token Expires In | Time when the Refresh Token will expire. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
HTTP Proxy String | HTTP Proxy string e.g. http://10.10.10.10:8123 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
HTTPS Proxy String | HTTPS Proxy string e.g. https://10.10.10.10:8123 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Sync on Create | Sync this organization's roles and licenses from Control Hub on creation. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Shadow |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Name * |
|