Dedicated Instance service activation

Before you begin: Dedicated Instance is an optional add-on to Webex Calling that you must purchase before proceeding with the activation.

  1. Once the order is placed for Dedicated Instance, a welcome email to set up the services will be sent to the email address provided in the “Provisioning Contact email” in Cisco Commerce Workspace (CCW).

  2. Perform one of the two:

    • You can activate Dedicated Instance as part of the First Time Setup Wizard (FTSW).

    • Activation can be deferred and completed later from Control Hub.

  3. Click the link that is provided in the welcome email to Create a Cisco Webex Order for a Customer.

    The partner administrator email address in the above wizard is mandatory as it is used to notify the Dedicated Instance UC application access details along with the credentials. You should also be able to login to Webex App using the same email ID.

  4. Once the Customer Organization is created, navigate to the First Time Setup Wizard (FTSW) and activate the Dedicated Instance service.

    Perform one of the following:

    • Choose to skip the Dedicated Instance setup by not selecting any of the regions and complete the activation later from Control Hub (Calling > Dedicated Instance > Status option).

    • Based on the available number of Dedicated Instance regions purchased, you can activate all or subset of required regions, by specifying the quantity of Professional, Standard, and Workspace devices.

      These parameters are only used to size the Dedicated Instance UC applications upon activation (for more information, see Dedicated Instance Sizing). The sum of the users and workspace devices across the regions cannot exceed the corresponding license quantity on the Webex Calling subscription.

FTSW

For more information on the data center locations, peering information, UC and IaaS applications network details, refer Dedicated Instance datacenter locations.

There will be no new Dedicated Instance deployments in the EMEA region. The customer will need to choose between the EU or UK region for Dedicated Instance deployments.

Once you activate the Dedicated Instance in a given region, it cannot be undone or changed to a different region.

The SIP address name is appended to the Cisco's Webex domain to form a unique domain name, for example if contasa name was entered, then the domain will be contasa.amer.wxc-di.webex.com for that Dedicated Instance region. This domain is used for the Dedicated Instance UC applications and also as the voice service domain for Mobile and Remote Access (MRA).

Make sure not to exceed 10 characters, as the FQDN of the UC applications will become long and is not recommended.

Once the Dedicated Instance region is activated with a domain, the same will be used for subsequent region activations within the same Control Hub organisation. Also, the UC applications domain cannot be changed once the Dedicated Instance service activation is completed or submitted.

As part of service activation, the following UC applications are deployed and sized by us based on the numbers provided in the FTSW for Knowledge Workers and Workspace devices for a region:

  1. Cisco Unified Call Manager

  2. Cisco Unified Unity Connection

  3. Cisco Expressway-Core and Edge

  4. Cisco Emergency Responder (only in AMER region)

    Cisco Unified IM and Presence application is no longer provided by default as part of Dedicated Instance deployment. It is deployed only if you had selected Legacy Jabber for calling, messaging and presence option as part of FTSW screen.

    Option with IM and Presence

    Option without IM and Presence

In addition, as part of activation, SIP connectivity is established between the Webex Calling Dedicated Instance and Multi-tenant platforms for inter-op calls.

Upon successful completion of the service activation, the UC apps will appear in the Calling > Dedicated Instance > Manage tab. For more details regarding accessing the UC applications, refer Access Dedicated Instance Applications from Control Hub.

You need to activate inter-op SIP trunk between Webex Calling Dedicated Instance and Multi-tenant platforms. Refer to Activate inter-op SIP trunk to Webex Calling multi-tenant for more information.