How to Activate Dedicated Instance in webex
A modern user experience with all the features is available after you purchase a Dedicated Instance for Webex Calling.
Dedicated Instance Service Activation
In order to activate Webex Calling, you must purchase the Dedicated Instance feature, which is an optional add-on to the service.
There are two ways of activating Dedicated Instances, either during the First Time Setup Wizard (FTSW) or later by using the Control Hub after the FTSW is complete.
You will receive a welcome email advising you how to set up your Dedicated Instance just after ordering Webex Calling as part of an initial order or after adding it to the subscription at a later date. You will find the link to Create a Cisco Webex Order for a Customer on the Cisco Webex Order Creation page. You can select the Set up Dedicated Instance option from the First Time Setup Wizard once you have created the order and navigated to the First Time Setup Wizard to activate the service. In addition, you have the option of skipping this step and completing activation when you are ready.
There are three input values that should be provided when opting to set up a dedicated instance in the Administration Console. It is required that you specify the region(s) where the Dedicated Instance will be deployed and activated for a specific geographical location, at the time of deployment. Additionally, you will need to input the number of users and workspace devices for each Dedicated Instance region. A dedicated instance is sized according to these parameters after it has been activated. It is important to note that the total number of Webex Calling subscription licenses and the number of users across the different regions cannot exceed the corresponding quantity of licenses.
UC applications and Mobile and Remote Access (MRA) applications will be accessed through the SIP URI address value provided by the customer, and will therefore be used across the specified region(s).
The activation of a dedicated instance in a region cannot be reversed once it has been completed.
As part of the Cisco Webex Order for a Customer wizard, the Cisco Webex Order for a Customer wizard will provide the details for Dedicated Instance UC application access along with the credentials to the email ID provided by the partner or customer. If the partner’s email ID is not available, then the customer’s email ID will be used for the Webex App message notification when the access document is shared via via the Webex. If the partner’s email ID is unavailable, then the partner’s email ID will be used.
For more information, please refer to the Webex Application | Signing In for the First Time guide.
A notification is displayed on the Control Hub Overview page if the process of setting up the Dedicated Instance was skipped during the First Time Setup Wizard, reminding you to complete the process.
It will be necessary to activate the dedicated instance(s) in the specified region(s) after the setup of the dedicated instance as part of the FTSW has been completed.
Dedicated Instance Service Activation Status
In the Calling > Dedicated Instance > Status section, the status of the Dedicated Instance service activation can be viewed.
The following UC applications are deployed as part of the activation of the service, and are sized accordingly:
-
UC Manager is a Cisco product that manages unified communications
-
Unity Connection from Cisco Unified Communications
-
Cisco Unified Instant Messaging and Presence Service
-
The Cisco Expressway architecture consists of a core and an edge component
-
(Only available in the AMER region) Cisco Emergency Responder
Additionally, as part of the activation of the Dedicated Instance, SIP connectivity is established between the platform that hosts the multi-tenancy and the platform that hosts the Dedicated Instance.
The activated Dedicate Instance services will appear under Usage by region as soon as activation of the service is completed successfully.
Dial Plan Configuration
The dial plan elements in both the multi-tenant platform and each instance of the Dedicated Instance are configured after a Dedicated Instance has been activated, in order to allow for call routing in Webex Calling. It is imperative that you incorporate the Webex Calling and the Dedicated Instance UCM dial plans based on the routing requirements between the platforms if you need calls to be routed between the platforms.
-
Dial Plan Elements configured for Webex Calling
-
Location
-
SIP trunk
-
Route Group
-
-
Elements of the Cisco Unified Communications Manager (Dedicated Instance) Dial Plan that has been configured
-
SIP trunk
-
Route Group
-
Route List
-
In a multi-tenant platform, dial plans for pre-configured elements are prefixed with ‘WXC-DI’. For example, WXC-DI-<region>-<dial plan element> is a dial plan element of WXC-DI.
A Cisco Unified Communications Manager dial plan element is prefixed with the prefix ‘xWxC’ to indicate that it has been preconfigured. There is a call plan element named xWxC that has a region named <unk>region>.
For more information on the components that are already pre-configured for Webex Calling, please refer to Dedicated Instance for Webex Calling – Base Configuration.
In order to make any calls from the multi-tenant location of the customer, you need to configure a Main Number (E.164) prior to making any calls from the location of the multi-tenant.
In order to proceed to adding the Main number, you will be required to add a PSTN connection first. More information about setting up a PSTN connection can be found in Configure PSTN Connection.
Those pre-configured interoperability dial plan elements are pre-configured to work with each other. It is important that you do not edit or delete any of these elements otherwise it could cause call failures between the platforms.
Configure PSTN Connection
The first step in adding a Main number is to configure the PSTN connection on your device.
-
Go to https://admin.webex.com/login and sign in to Control Hub.
-
Select Services > Calling > Location from the drop-down menu.
-
On the right-pane of the screen, click Manage against PSTN Connection and select the default location that was created by Cisco.
-
You will see Premises-based PSTN in the window that appears after you click Next.
-
In the Routing drop-down list, select the default Route Group and check the disclaimer box. Once you have completed these steps, click Next.
-
You can click Done (add number later) if you want to add the Main Number later rather than adding the Main Number now if you wish to make or receive calls from the Main Number.