In order to perform a provision to Cisco Webex, there are several pre-requisites that must be considered before attempting an automated provisioning task.

You have the necessary login details for the account
The account has adaquate licenses for users, devices etc.
You know the email domain for the account

UCentric SPA Options

When using Webex Calling provisioning, you will need to ensure the following information is available:-

You will required either;

The Administrator Account details for the tenant (administrator username and password),

or

Webex wholesales credentials AND the Organisation Id for the tenant you are trying to provision to.

Direct Provisioning to a customer account

Wholesale Provisioning

Admin Credentials for the Webex account

Wholesale Credentials

Organisation ID for the customer

e.g. something like this:

Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi82NzA0Njc3NS0wNGQxLTQ5ZDEtOTcyYS1iZDAyYmU0Y2MzMjc

Panel

bgColor	#E6FCFF

Pre-flight checklist (LLD)

Before provisioning to Webex Calling, you must ensure that the data is properly prepared and suitable for provisioning. Here is a simple checklist to follow:

☑️ Email addresses

📧 Ensure that all accounts have a valid email address, and that the domain matches the customer account

☑️ Phone types

☎️ Ensure that supported phone types are defined in the primaryModel column of both the Devices and Profiles tabs of the spreadsheet. You will also need a valid, maching primaryMAC address for the device - Note: simple numbers will suffice; 8865 will match DMS Cisco 8865

☑️ Numbers

☎️ Ensure that all the users you want to have Webex Calling facilities have a valid number in the line1DDI column, and an extension number in the line1DN column

☑️ Primary Model / MAC Address

☎️ If you have both the Model and MAC defined, then the device will be allocated to the user. If you just have the Model, then an ‘Activation code’ will be requested and provided in the provisioning results report

Panel

bgColor	#E6FCFF

Pre-flight checklist (Webex calling)

Before provisioning to Webex Calling, you must ensure that the tentant has a PSTN Connection configured to a primary location - Cisco do not expose this functionality through their APIs, so it is a required manual step.

⚠️ If you don’t perform these steps, then you cannot provision any devices

☑️ Wholesale Customer

🧑‍💼 You must create your ‘Customer' on the Wholesale portal and get the orgId in order to provision to Wholesale

☑️ Licenses

🧑‍💼 You must make sure you have allocated licenses to the organisation

An example below is from a ‘Sandbox’ account

☑️ PSTN

☎️ You MUST create the primary location listed in your LLD sheet, and enable ‘Calling’ by setting up the PSTN connection. If the PSTN cannot be fully configured, then set as “Premise-based PSTN” and “None” for the “Trunk group” as this will allow the provisioning to take place.

It is advisable to add all the E.164 numbers to each location if you are able to as you will be informed if any of the numbers are assigned to another tenant (the API doesn’t expose this)

☑️ Valid numbers + MAC addresses

☎️ Regardless of using a real customer or a Sandbox, all numbers must be unique (and valid in the ‘location’) - e.g. UK locations will only accept UK numbers. You cannot re-use dummy MAC addresses or telephone numbers. See the bottom of this article for dummy ranges you can use in the UK.

Panel

bgColor	#E6FCFF

\uD83D\uDCD8 Instructions

First create a Webex LLD export of the required Audit. Note, select the Webex LLD version will automatically highlight mandatory columns in the bulk-loader to assist you with provisioning.

There are some mandatory pieces of information that must be present in the Profiles tab for a successful provision to Webex Calling. Some of these will be populated automatically, but this is very much dependant on the ‘source’ audit (e.g. If you are coming from a legacy analog PABX, you are unlikely to see device types, DDIs or email addresses)

LLD Field Name

What you need to put here

Example and comments

line1DN

The Extension number

7890

line1DDI

The DDI or PSTN number

+441234567890 (full E164 number)

Add additional DDI’s to the additionalDDIs column (comma delimited if there are more than 1)

firstName

The user’s first or given name

Fred

lastName

The user’s last or family name

Bloggs

email

Email address for user

fred@xyz.com

NOTE: This must match the customer account DNS domain. This is shown in the Administration Account details as “Host Account” under “Licenses”

Note: If this is empty, but the UserServicePacks is set to

Webex Calling - Workspaces

and there is a “Department” defined, then a “Workspace” phone will be created.

regionName

The Location of the user/device

Headquarters

Note: This needs to match a entry in the “Locations” tab. If there is only a single location, use Default as the regionName

primaryModel

A Webex calling compatible handset name

Cisco 8875

Note: This must match the names of Webex accepted types, although it will match partial values, e.g. “8875” will map to “Cisco 8875” automatically

^{Note: See supported device list below}

primaryMAC

MAC address of device to be assigned to the user

Valid MAC address in one of these formats:

0010490D59A9
00:10:49:0D:59:A9
00-10-49-0D-59-A9

Note
NOTE: You cannot use the same MAC address in different tenants/customers

Info
If this is left ‘blank’, but a ‘primaryModel’ is provided, then an Activation Code will be requested and provided in the provisioning report - NOTE: This is only supported on Cisco devices. Any 3rd-party device must be in the supported vendors shown below and provided with a MAC address. For unlisted SIP devices, you can attempt to use “Generic IPPhone Customer Managed“

UserServicePacks

Licenses to assign to the user (comma delimited)

Info
Note the use of Subscription below when multiple license pools are available

One or more of the following (comma delimited)

Webex Calling - Professional
Webex Calling - Workspaces
Call on Webex (1:1 call, non-PSTN)
Basic Space Meetings
Basic Messaging

Panel

panelIconId	atlassian-warning
panelIcon	:warning:
bgColor	#FFF0B3

NOTE: If you have a DDI defined, then “Webex Calling - Professional” will be assumed.

Subscription

(Optional) Subscription id of Webex Calling License

This is used to apply specific Webex licenses to particular users, and is used where there are differing pools of licenses available.

department

Workspace name to use / create

Only actioned if UserServicePacks is set to

Webex Calling - Workspaces

SoftKey1 → SoftKey16

speedial;number;label

(e.g. speeddial;08442478881;MIT)

This will set up custom key templates for the user and apply the speedial buttons

Panel

panelIconId	atlassian-warning
panelIcon	:warning:
bgColor	#FFF0B3

Avoid Keys 1 and 2 as they are used for normal line appearances on Webex calling. If you place values in these keys, it will not provision any of the keys for the device.

hoteling

Yes / No

This is used to indicated that the user can use the Hoteling function of Webex Calling. It’s optional and will be assumed to be “No” if not present.

overrideDDIs

Yes / No

Panel

panelIconId	atlassian-warning
panelIcon	:warning:
bgColor	#FFF0B3

Use with caution!

This will remove all DDI-style numbers from the user and add the DDI number in the LLD in replacement.

callWaiting

Yes / No

This will enable or disable “Call Waiting” - Default is “No” if the column is missing.

Panel

bgColor	#E6FCFF

Hunt Groups and Queues

Hunt groups are created automatically from the Hunt, Work, ACD, Ring etc. tab in the Excel LLD spreadsheet. In order to create a Queue instead, the orchestrator looks for certain key group types or characteristics and then adapts them to Queues automatically. The highlighted values below show all the types that are automatically transformed from a ‘Hunt group’ to a ‘Queue’

Panel

bgColor	#E6FCFF

Shared Lines

Shared lines are added by including information on the Bridged Extensions tab of the LLD. If this is missing, just add a new tab with this exact name, and exsure that you have User DN, Name and Shared Call Appearance columns as the headers (the rest won’t matter)

The User DN is the user’s device on which you want to show the shared appearance, and the Shared Call Appearance is what will becomea Shared Line button on the phone.

Note
Note: As at November 2024, we cannot automatically provision Lines2/3/4/5/6 from a Cisco CUCM to Webex Calling as the APIs are not available from Cisco till January 2025

Panel

bgColor	#E6FCFF

🔢 Workspaces

It is possible to add a ‘Workspace’ device to Webex Calling, providing the following settings are adhered to for the entry in the LLD

No email address
Has a valid 'Cisco' device (with MAC address)
Has a line1DN (and line1DDI if needed)
Has a "Department" name
Has "Webex Calling - Workspaces" in UserServicePacks

The ‘Department’ name will become the ‘Workspace’, so please ensure that these are unique. UCentric can only provision a single device to each workspace.

If you fail to give them unique department names, they will be given a sequential suffix, e.g. “Huddle Room_1”, “Huddle Room_2” etc.

Panel

bgColor	#E6FCFF

🔢 Unallocated numbers

It is possible to add ‘unallocated' numbers to the tenant by simple adding them in the ‘Unallocated numbers’ tab in the LLD as shown below.

These will be created and be visible in the Calling section, but remain unassigned to any device or user

Panel

bgColor	#DEEBFF

Webex Calling - Sandboxes

You can setup temporary Sandboxes for testing using this link on the Cisco webex website:

https://developer.webex.com/docs/developer-sandbox-guide

Panel

bgColor	#DEEBFF

Webex Calling Supported Devices (as of Nov 2024)

2N Customer Managed
Algo Customer Managed
Axis Customer Managed
Cisco 9841
Cisco 9851
Cisco 9861
Cisco 9871
CyberData Customer Managed
DMS AudioCodes MP-124E
DMS AudioCodes MP-1288
DMS AudioCodes MP202
DMS AudioCodes MP202R
DMS AudioCodes MP204
DMS AudioCodes MP204R
DMS Cisco 191
DMS Cisco 192
DMS Cisco 6821
DMS Cisco 6841
DMS Cisco 6851
DMS Cisco 6861
DMS Cisco 6871
DMS Cisco 7811
DMS Cisco 7821
DMS Cisco 7832
DMS Cisco 7841
DMS Cisco 7861
DMS Cisco 840
DMS Cisco 860
DMS Cisco 8811
DMS Cisco 8832
DMS Cisco 8841
DMS Cisco 8845
DMS Cisco 8851
DMS Cisco 8861
DMS Cisco 8865
DMS Cisco 8875
DMS Cisco VG400
DMS Cisco VG410
DMS Cisco VG420
DMS Polycom CCX400
DMS Polycom CCX500
DMS Polycom CCX505
DMS Polycom CCX600
DMS Polycom CCX700
DMS Polycom EE100
DMS Polycom EE220
DMS Polycom EE300
DMS Polycom EE320
DMS Polycom EE350
DMS Polycom EE400
DMS Polycom EE450
DMS Polycom EE500
DMS Polycom EE550
DMS Polycom SSIP5000
DMS Polycom SSIP6000
DMS Polycom Trio8300
DMS Polycom Trio8500
DMS Polycom Trio8800
DMS Polycom VVX101
DMS Polycom VVX150
DMS Polycom VVX201
DMS Polycom VVX250
DMS Polycom VVX301
DMS Polycom VVX311
DMS Polycom VVX350
DMS Polycom VVX401
DMS Polycom VVX411
DMS Polycom VVX450
DMS Polycom VVX501
DMS Polycom VVX601
DMS Yealink CP920
DMS Yealink CP925
DMS Yealink CP960
DMS Yealink CP965
DMS Yealink T33G
DMS Yealink T34W
DMS Yealink T40G
DMS Yealink T41S
DMS Yealink T42S
DMS Yealink T43U
DMS Yealink T46S
DMS Yealink T46U
DMS Yealink T48S
DMS Yealink T48U
DMS Yealink T53W
DMS Yealink T54W
DMS Yealink T57W
DMS Yealink T58V
DMS Yealink W52P
DMS Yealink W56P
DMS Yealink W60P
DMS Yealink W70P
FaxBack Customer Managed
Generic Gateway Customer Managed
Generic IPPhone Customer Managed
Grandstream Customer Managed
Imagicle Customer Managed
Partner Managed Gateway
Partner Managed Phone
Singlewire Customer Managed

Note

Fake Numbers / MAC Addresses

If you are setting up a Sandbox account, the numbers and MAC addresses still need to appear “Valid” to the WebEx APIs, so please note the following:-

The numbers and MACs you use cannot appear on any other instance in WebEx!
The numbers must be valid numbers for the target country (see below for ‘fake’ ranges that are reserved for testing in the UK)

Geographic Numbers

Geographic area	Geographic area code	Telephone number range (1000 numbers in each range)
Leeds	0113	496 0000 to 496 0999
Sheffield	0114	496 0000 to 496 0999
Nottingham	0115	496 0000 to 496 0999
Leicester	0116	496 0000 to 496 0999
Bristol	0117	496 0000 to 496 0999
Reading	0118	496 0000 to 496 0999
Birmingham	0121	496 0000 to 496 0999
Edinburgh	0131	496 0000 to 496 0999
Glasgow	0141	496 0000 to 496 0999
Liverpool	0151	496 0000 to 496 0999
Manchester	0161	496 0000 to 496 0999
London	020	7946 0000 to 7946 0999
Tyneside/Durham/Sunderland	0191	498 0000 to 498 0999
Northern Ireland	028	9649 6000 to 9649 6999
Cardiff	029	2018 0000 to 2018 0999
No area	01632	960000 to 960999

Non-geographic numbers

Ofcom’s published list of recommended dummy numbers includes a thousand mobile numbers (07700 900000 to 900999), a thousand Freephone numbers (08081 570000 to 570999), a thousand premium rate service numbers (0909 8790000 to 8790999), and one thousand UK-wide numbers (03069 990000 to 990999).

Note: Don’t use premium rate numbers for devices - they are shown solely for information purposes

Telephone number type	Telephone number range (1000 numbers in each range)
Mobile	07700 900000 to 900999
Freephone	08081 570000 to 570999
Premium rate services	0909 8790000 to 8790999
UK-wide	03069 990000 to 990999

Versions Compared

Old Version 24

New Version Current

Key

UCentric SPA Options

Pre-flight checklist (LLD)

Pre-flight checklist (Webex calling)

\uD83D\uDCD8 Instructions

Hunt Groups and Queues

Shared Lines

🔢 Workspaces

🔢 Unallocated numbers

Webex Calling - Sandboxes

Webex Calling Supported Devices (as of Nov 2024)

Fake Numbers / MAC Addresses

Geographic Numbers

Non-geographic numbers

Page Comparison

Versions Compared

Old Version 24

New Version Current

Key

UCentric SPA Options

Pre-flight checklist (LLD)

Pre-flight checklist (Webex calling)

\uD83D\uDCD8 Instructions

Hunt Groups and Queues

Shared Lines

🔢 Workspaces

🔢 Unallocated numbers

Webex Calling - Sandboxes

Webex Calling Supported Devices (as of Nov 2024)

Fake Numbers / MAC Addresses

Geographic Numbers

Non-geographic numbers