WebEx Calling Integration with Nectar DXP

Introduction

This document is designed to provide required use a step by step guide on how to integrate their Webex Calling instance with Nectar DXP.

Prerequisites

• Access to Nectar DXP with Super Admin permissions

• Access to the Webex instance with Webex Calling Detailed Call History API Access permissions for authorization

• The following Webex information which can be obtained from the following link:

  • developer.webex.com/my-apps/*Name of Instance*

    • Webex Client ID

    • Client Secret

    • Client Integration ID

WebEx Calling Application Configuration

1. Login to https://developer.webex.com with an account that has Webex Calling Detailed Call History API Access permissions for authorization

2. Click on your user picture on the top-right and select My Webex Apps

3. Click on Create a New App and select Create an Integration
   
   

4. Select No for Will this integration use a mobile SDK?

5. Give the integration a useful name such as Nectar DXP

6. Use the following icon if desired. It matches the dimension requirements:
   

7. Add the following description for the application:
   Get better visibility of your Webex data with Nectar DXP. Nectar DXP makes it easy to find issues that may be affecting your Webex user's calling experience.

   * See if any of your corporate locations are having network quality issues.

   * Quickly find all the Webex calls a particular user has participated in

   * Get actionable insights into poor quality issues that may be affecting multiple users at a corporate location, or even at the user's home ISP level.

   * Create customized, automated reports that can tell whatever story your management team requires

   * Get alerted in near-real time when specific users or locations are having quality issues

   Requires a paid subscription to Nectar DXP. For more information, see https://www.nectarcorp.com/

8. Obtain the appropriate Redirect URI from your Nectar Professional Services representative. It will look similar to https://demo.us.nectar.services/adminapi/oauth/cisco-webex-calling/authorize

9. Under Scopes, select the following:

   • analytics:read_all

   • spark-admin:calling_cdr_read
     

10. Scroll to the bottom and select Add Integration

11. You should be taken to a new screen that shows details about the new integration. Make note of the following to provide to your Nectar Professional Services representative:

    • Client ID

    • Client Secret

    • Integration ID
      

Client OAuth Setup

Firstly we have to configure the Webex Calling OAuth configuration to do this follow the steps below

1. Click on your username in the top right and select Tenants Management

   

2. Select the Client OAuth Setup tab and then click add Configuration

   

3. Enter the details for the Client OAuth Setup

   

   Property	Description
   Platform	Select Cisco (WebEx Calling)
   Name	This name is used to identify the Client OAuth when configuring for the DXP instance
   Client ID	Webex Calling instance
   Client Secret	Webex Calling Secret Key
   Verification ID	Webex Calling Verification ID

4. Select Add and you are done with the OAuth configuration.

Configure Webex Calling for the DXP Instance

1. Within Nectar DXP, navigate to the  Admin → Advanced Settings → Configurations → Data Sources screen and then scroll down to Cisco Webex Calling section and click Add Source.

   

2. Enter the required details:

   

   Property	Description
   Display Name	Give a name in which to identify this Webex Calling instance within Nectar DXP
   Nectar Cloud Connector Instance	There should only be 1 available connector instance to select
   OAuth Application	Select the OAuth instance that you created in the previous section

3. Save when all details have been entered

4. After some time has passed you will receive an action required prompt to finalize the Cisco Webex Calling integration with your Nectar DXP environment

   

5. Click Accept from the idbroker.webex.com screen

   

Congratulations Cisco Webex Calling has successfully being authorized for integration and should now be working within Nectar DXP.