Webex Meetings

Release Notes 11.0.0 SP7

Important: The XML API 11.0.0 SP7 release changes some schema definitions. For the latest schema definitions, see the release notes announcements page. The features in this release are backward compatible with previous releases.

Overview

This release note describes the changes made in the release of Webex XML API 11.0.0 SP7. These changes apply to your integration with WBS 32. All features are backward compatible with existing integrations. The changes to the latest schema definitions are explained below.

What is New in this Release

This section describes the new features in XML API 11.0.0 SP7.

XML API support for machine account access for service-to-service calling

Note: This feature is only applicable for WBS 31 (XML API v11.0.0).

Inside the Webex and Cisco components, the XML API now provides a new way to sign in with the CI access token for both user and machine accounts, only for service-to-service calling. This new support is provided by the new element accessToken, the CI access token in the sign in process.

XML API does not support service accounts due to security issues. Unless you require an account which needs user management for all customers, you should be using a machine account for service-to-service calling.

Affected APIs

  • securityType

High-Level Diagram

Schema Change

Sample Request

Code Snippet
Copy<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
    <securityContext>
      <siteName>Webex_Site_Name</siteName>
      <webExID>Webex_User_Account</webExID>
      <accessToken>CI_Access_Token which include Site and User Account information (Support CI User Token and CI Service Toekn)</accessToken>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.SetUser">
    <webExId>Webex_User_ID</webExId>
    <privilege>
        ...
    </privilege>
</bodyContent>
</body>
</serv:message>

Known Issues

None

GetSessionInfo: Toll-free numbers not available if toll-only enabled

Previously, the GetSessionInfo API response included all the global call-in numbers regardless of whether only toll or both toll and toll-free options were selected in the audio privileges. With this change, we now only display the global call-in numbers corresponding to the audio privileges selected. For example, only toll global call-in numbers are displayed if toll only is selected as the audio privilege, and all the global call-in numbers are displayed if the toll and toll-free options are selected.

APIs impacted

GetSessionInfo

Example

When "toll-only" is selected:

Previous functionality:

New functionality:

Known Issues

None

LstRecording SQL default time range of 4 weeks

Note: This feature is only applicable for WBS 32 (XML API v11.0.0).

The LstRecording SQL applies a default time range of 4 weeks if no time scope is specified. This is to fix an issue of DB timeouts related with NBR/Service recordings. If no time scope is indicated for calling the LstRecording API, the XML API system sets a default time of 4 weeks (28 days from the call time). If the time scope indicated is more than 28 days in the XML request, an exception occurs with the message, “Maximum querying date range is 28 days”.

Affected XML APIs

  • LstRecording

Known Issues

None

LstmeetingusageHistory returns timezone in String type

This schema change is to address the bug where the LstmeetingusageHistory API would not return the timezone attribute for the meeting with timezoneID > 61. Previously, timezone was returned as an object defined by the schema, which uses hard-coded mapping methodology that only supports timezoneID values from 0 - 61. Now, both the timezoneID(int) and timezone description(string) are queried from the DB, so it no longer depends on a schema check.

Note: This schema change is for both WBS 31 and WBS 32.

Affected XML APIs

  • LstmeetingusageHistory

Known Issues

None

The XML API schemas and release notes are available at the Cisco Webex Developer Portal:

XML API Reference

The URL API release notes are available at the Cisco Webex Developer Portal:

URL API Reference

Next