For example, if the URL is, the Webex Site that you have to enter is splunk.
#Webex teams troubleshooting install#
Installation Steps for cloudĬreate a support ticket with APP-CERT reference to get it installed on the Cloud instance OR follow the cloud-ops steps to install non-published applications. Install the TA on one of the Heavy Forwarder(s). This application can be installed on-prem and cloud. Please copy the Client ID and Client Secret somewhere for further use. Description: Enter some details about what your integration does.Note: If your Splunk site is not in en-US, please change it to your true value. For example, if the domain of your HF or IDM is, the Redirect URI you have to enter is:
Please replace the with the domain of your Splunk Heavy Forwarder (or IDM). Redirect URI: The Redirect URI MUST follow this pattern:.Integration name: Enter a integration name as you like.Log in to Cisco DevNet using a Webex Meetings Site Admin account.Ĭlick on Add App Information button on the top right corner. After login you can create a dedicated integeration app for this Add-on. Please make sure you pick the Login with Webex Meetings option, and other log in options will not work for this purpose. The dialog prompt for logging in to DevNet has the option to Login with Webex Meetings. This requires you to be logged in to Cisco DevNet using a Webex Meetings Site Admin account. Create a Webex Meetings OAuth Integration AppĪn integration is what you'd have to use if you have Single Sign-On (SSO) or OAuth enabled in your Webex account and you are not able to create a Service Account. If you are managing the site from Control Hub, please take a look at this link it should help.Īlternatively, Add-Users-Manually-in-Cisco-Webex-Control-Hub can also be a workaround if you have AD Connector setup as well.
#Webex teams troubleshooting license#
If you do not have any automation enabled, you should be able to create a user, you will have to assign a license to the user and then give the user partial Site Admin read-only rights. Generally, Webex Teams and Webex Meetings portal are completely automated from Active directory connector and adding a local user is DISABLED as soon as AD connector is set up. If you have to go to (Control Hub) to login and manage your webex account, you may run into some issues. Once the API user was created it was linked to the Control Hub because we have linked sites.īased on which Cisco Webex Meetings you have, the account creation might be different. Create a Service AccountĬreate the service account in Webex Meetings site's admin portal ().
Therefore it's recommended to set the interval to 86400 or more for historical input. XML APIĬisco:webex:meetings:history:trainingattendeehistoryĬisco:webex:meetings:history:supportattendeehistoryĬisco:webex:meetings:history:eventattendeehistoryĬisco:webex:meetings:history:meetingattendeehistoryĬisco:webex:meetings:history:meetingusagehistoryĬisco:webex:meetings:history:eventsessionhistoryĬisco:webex:meetings:history:recordaccesshistoryĬisco:webex:meetings:history:supportsessionhistoryĬisco:webex:meetings:history:trainingsessionhistoryĬisco:webex:meetings:general:summarysessionĭISCLAIMER: Guidance from Cisco states historical data retrieval may be incomplete if fetched less than 48 hours from time meetings ended. These API endpoints are being hit to fetch data for the meetings.
This is a TA to pull in data from Cisco WebEx Meetings XML API. The Cisco WebEx Meetings Add-on for Splunk uses the Webex Meetings XML API to fetch data and ingest it into Splunk.
0 kommentar(er)
