Skip to main content
CallTower Solutions Center

Webex Syncing

Overview

Webex Syncing allows CallTower Connect to securely communicate with your organization’s Webex Control Hub account. Once authorized, Webex locations can be synced into Connect, and phone numbers managed in Connect can be synchronized with Webex Control Hub for provisioning.

How It Works

To enable syncing, your organization must already be active on Webex services, and Connect must be authorized to access Webex Control Hub through the Webex API. This guide outlines the key steps for confirming prerequisites, authenticating the integration, syncing locations, and managing DIDs.

Webex Services Requirement

  • Before Webex syncing can be configured, your organization must already be active on Webex services.
  • If Webex services are not active for your organization, please contact your CallTower representative before continuing with the syncing process.

Authenticate the Webex API

  • To link Connect with Webex Control Hub, go to Menu > Administration > Corporate Administration > Cisco Webex > API Authentication.

A screenshot of a phone

AI-generated content may be incorrect.

  • Select the appropriate authorized Webex administrator and send the authentication email.

A screenshot of a computer

AI-generated content may be incorrect.

  • Open the authentication email and select the Webex Authorization link.

A screenshot of a computer

AI-generated content may be incorrect.

  • Sign in to Webex Control Hub using an administrator account with the required permissions.

A screenshot of a login form

AI-generated content may be incorrect.

  • When prompted, select Allow to authorize the API integration between Webex Control Hub and Connect.

A screenshot of a phone

AI-generated content may be incorrect.

  • A confirmation message will indicate that the integration was completed successfully.

A screenshot of a message

AI-generated content may be incorrect.

  • After authentication is complete, Webex Actions will be available in Connect under Menu > Locations.

 

Sync Locations

  • Locations should be created in Webex Control Hub first, then synced into Connect. 

A screenshot of a computer

AI-generated content may be incorrect.

  • In Webex Control Hub, go to Locations > Manage Locations, complete the required fields, enter the address, select the matching address from the dropdown, and select Create.

  • If calling must be configured for the location, open the location in Webex Control Hub, select the Calling tab, and choose Set Up Calling.

A screenshot of a computer

AI-generated content may be incorrect.

  • Select Cloud Connect PSTN, then select Next.

A screenshot of a computer

AI-generated content may be incorrect.

  • Select CallTower as the provider, then select Next.

A screenshot of a computer

AI-generated content may be incorrect.

  • Select the carrier. For US and Canada locations, select CallTower. Then select Next.

A screenshot of a computer

AI-generated content may be incorrect. 

  • In Connect, go to Menu > Locations, select Webex Actions > Sync Webex Locations, then choose New Location for locations that should be imported or Don’t Import for locations that should not be imported yet. If a location matches between Webex and Connect already, the name of the location will be in the Locations field. Select Don’t Import if you do not want to import these at this time or leave them as is to import. Select Save.

  • Wait for the sync event to complete, then refresh the Locations screen. The synced locations will appear in the Locations grid.

 

Manage DIDs

  • DIDs can be uploaded to or released from Webex Control Hub through Connect. In Connect, go to Locations, expand the applicable location, and select DIDs > Cisco Webex > Upload Webex DIDs.

A screenshot of a computer

AI-generated content may be incorrect.

  • Select the DIDs to upload, choose the appropriate Usage Type and trunk, then select Save. After the event completes, the DID will appear in Webex Control Hub as active and ready for provisioning.

·       Usage Types:

  • Standard: Used for people, workspaces, or numbers left in inventory. This option is not optimized for high-concurrency scenarios.
  • Service: Used for Auto Attendants, Contact Center, Call Queues, Hunt Groups, main location lines, or other high-concurrency scenarios.

 

·       The Sync Webex DIDs action compares DIDs in Connect with DIDs in Webex Control Hub and updates licensing or DID status where applicable.

    • If a DID is marked as uploaded or unavailable in Connect but is not present in Webex Control Hub, Connect will update the DID to available.
    • If a DID is available in Connect but already exists in Webex Control Hub, Connect will update the DID to unavailable.

 

A screenshot of a computer

AI-generated content may be incorrect.

Important Notes

·       A number assigned to a user or configured as a main location number in Webex Control Hub must be unassigned in Webex Control Hub before it can be released in Connect.

·       If Webex API authentication has not been completed, the Sync Webex Locations action will return an error.

A screenshot of a message

AI-generated content may be incorrect.

·       If a location has not yet been synced from Webex Control Hub into Connect, location-based DID actions may return an error.

A pink box with black text

AI-generated content may be incorrect.

 

Subtypes

o   For API-synced customers, licensing is synced once per week and numbers are licensed if assigned, but not when simply uploaded.

API-synced licensing subtypes:

       -Upload User Only-not licensed

       -Upload Voice App Only-not licensed

       -Upload Mobile Only-not licensed

-Upload Call Path Only-not licensed

-User-licensed

       -Voice App-licensed

-Mobile-licensed

-Call Path-licensed

o   For customers that are not API synced, licensing occurs when the number is uploaded, regardless of assignment status in Webex Control Hub.

Non-API-synced licensing subtypes:

       -No Auth User-licensed

       -No Auth Voice App-licensed

       -No Auth Mobile-licensed

- No Auth Call Path-licensed

  • Was this article helpful?