本文包含 XML API 每月 SP 發行版的更新和變更。

如需 XML API 40 和 REST API 40 的相關資訊,請參閱 Cisco Webex Meetings API 更新概觀 (API 40)

如需 XML API 11 SP9 及更早版本的更新,請轉至 Cisco DevNet

XML API 39.11.0 更新

按一下這裡以下載 XML API 39.11 網要。

LstSummaryUser 可以依照上次修改時間查詢使用者帳戶

我們即將升級 LstSummaryUser API,以便使用者能夠依據上次修改的時間查詢使用者帳戶。 三個新元素 modifiedDateStartmodifiedDateEndlastModifiedTime 已新增至 API。


此查詢的最大時間範圍是 90 天。 如果您輸入的時間範圍超過 90 天,則會出現錯誤: 999999 修改日期查詢的最大日期範圍是 90 天

受影響的 API:

  • LstSummaryUser

LastSummaryUser 請求和回覆更新:

LstSummaryUser 請求範例:

<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
  <securityContext>
    <siteName>Site_Name</siteName>
    <webExID>SiteAdmin</webExID>
    <password>密碼</password>
    <partnerID>webexpartner</partnerID>
  </securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.user.LstsummaryUser">
        <dataScope>
            <modifiedDateStart>10/01/2019 09:24:54</modifiedDateStart>
            <modifiedDateEnd>11/30/2019 09:24:54</modifiedDateEnd>
            <timeZoneID>4</timeZoneID>
        </dataScope>
    </bodyContent>
</body>
</message>

LstSummaryUser 回應範例:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:use="http://www.webex.com/schemas/2002/06/service/user">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>**5124***</use:userID>
                <use:webExId>***MR***</use:webExId>
                <use:firstName>***MR***</use:firstName>
                <use:lastName>***est***</use:lastName>
                <use:email>***est***@qa.webex.com</use:email>
                <use:userRoleType>主持</use:userRoleType>
                <use:registrationDate>06/19/2016 22:13:06</use:registrationDate>
                <use:active>DEACTIVATED</use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:meetingTypes>
                    <use:meetingType>3</use:meetingType>
                    <use:meetingType>9</use:meetingType>
                    <use:meetingType>10</use:meetingType>
                    <use:meetingType>11</use:meetingType>
                    <use:meetingType>13</use:meetingType>
                    <use:meetingType>14</use:meetingType>
                    <use:meetingType>102</use:meetingType>
                </use:meetingTypes>
                <use:lastLoginTime>10/19/2019 23:13:14</use:lastLoginTime>
                <use:lastModifiedTime>11/11/2019 19:11:11</use:lastModifiedTime>
            </use:user>

XML API 39.10.0 更新

按一下這裡以下載 XML API 39.10 網要。

使用匿名存取時,GetSessionInfoGetUserCard 會傳回驗證碼

作為安全更新,我們增強了具有 CAPTCHA 代碼回應保護的 GetSessionInfoGetUserCard API。 如果您的應用程式使用匿名存取來呼叫 API,請增強應用程式以支援 CAPTCHA 代碼輸入。

受影響的 API:

  • GetSessionInfo

  • GetUserCard

CAPTCHA 安全和回應更新:

GetSessionInfo 沒有 CAPTCHA 的回應範例:

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>找不到對應的會議</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

GetSessionInfo 具有 CAPTCHA 的回應範例:

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>找不到對應的會議</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
            <serv:CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</serv:CAPTCHAID>
           <serv:CAPTCHAImage>
                iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA
                ...........
                maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu+ZUFb7SAAAAAElFTkSuQmCC
            </serv:CAPTCHAImage>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

如果收到 CAPTCHA 回應並繼續呼叫 API,請在 API 請求中加入 CAPTCHAID 和 CAPTCHAWord:

<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
    <siteName>sqdemo6</siteName>
    <CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</CAPTCHAID>
    <CAPTCHAWord>pyjihk</CAPTCHAWord>
</securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
        <sessionKey>715801743</sessionKey>
    </bodyContent>
</body>
</serv:message>

GetSessionInfo 針對不正確的 CAPTCHAID 和 CAPTCHAWord 產生的回應範例:

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>CAPTCHA ID 和單字無效或遺漏</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>030113</serv:exceptionID>
            <serv:CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</serv:CAPTCHAID>
           <serv:CAPTCHAImage>
                iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA
                ...........
                maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu+ZUFb7SAAAAAElFTkSuQmCC
            </serv:CAPTCHAImage>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

LstSummaryUser 支援返回個人會議室 URL

我們已將一個新的回應元素 personalMeetingRoomURL 新增至 LstSummaryUser API。

LstSummaryUser 回應範例:

XML API 39.9.0 更新

按一下這裡以下載 XML API 39.9 網要。

對個人會議室 (PMR) 的簡短 SIP URL 的支援

對 PMR 的簡短 SIP URL 格式的支援會影響 GetSessionInfoGetMeetingGetUserGetMe API。 新回應元素 displayMeetingUrl 已新增至 GetUserGetMe API,並且已經在 GetSessionInfoGetMeeting 中。displayMeetingUrl 會傳回使用者的 PMR URL。

受影響的 API:

  • GetSessionInfo

  • GetMeeting

  • GetUser

  • GetMe

GetUser 回應範例:

GetMe 回應範例:

GetSessionInfo 傳回匿名存取所需的元素

出於安全考量,現在只能由 GetSessionInfo 返回必要的元素供匿名存取。

回應範例:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:sessionkey>715952675</ep:sessionkey>
    <ep:accessControl>
        <ep:listStatus>公開</ep:listStatus>
        <ep:registration>false</ep:registration>
        <ep:passwordReq>true</ep:passwordReq>
        <ep:registrationURL>https://sqdemo6.dmz.webex.com/ec3300/eventcenter/enroll/register.do?loadFlag=1&reqFlag=1&confId=123203663769372547&siteurl=sqdemo6</ep:registrationURL>
        <ep:registrationURLForMobile>https://sqdemo6.dmz.webex.com/ec3300/eventcenter/enroll/mobileRegister.do?formId=0&formType=0&loadFlag=1&from=mobileClient&siteurl=sqdemo6&confId=123203663769372547</ep:registrationURLForMobile>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Anony_Meeting_Retuning</ep:confName>
        <ep:serviceType>MeetingCenter</ep:serviceType>
    </ep:metaData>
    <ep:schedule>
        <ep:startDate>2019 年 3 月 29 日上午 11:55:00</ep:startDate>
        <ep:duration>60</ep:duration>
        <ep:timeZone>GMT-07:00,太平洋地區(聖荷西)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>false</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>true</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>false</ep:isPersonalMeetingRoom>
    <ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/e.php?MTID=m2399b241f12722ca325388495e845103</ep:meetingLink>
    <ep:sipURL>715952675@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>715952675@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
</serv:bodyContent>

受影響的 API:

  • GetSessionInfo

排定會議和活動的行為變更

預設情況下,所有排定的會議都是支援視訊裝置的會議。 但是,當您排定會議但針對會議的音訊選取其他時,該會議將排定為不支援視訊裝置的 Webex 會議。

受影響的 API:

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

XML API 39.8.0 更新

按一下這裡以下載 XML API 39.8 網要。

LsttrainingattendeeHistory 現在傳回會議出席者的注意力

新回應元素 attentionToDurationPercentage 已新增至 LsttrainingattendeeHistory API。 LsttrainingattendeeHistory 傳回會議出席者的注意力詳細資訊。 採用下列格式傳回元素:

<history:attentionToDurationPercentage>100</history:AttentionToDurationPercentage>

受影響的 API:

  • LsttrainingattendeeHistory

    • attentionToDurationPercentage

    • attentionToAttendancePercentage

回應範例:

<history:endTime>2019 年 4 月 17 日下午 11:37:07</history:endTime>
<history:duration>6</history:duration>
    <history:attentionToDurationPercentage>100</history:AttentionToDurationPercentage>
    <history:attentionToAttendancePercentage>100</history:AttentionToAttendancePercentage>
<history:registered>否</history:registered>
<history:invited>否</history:invited>

GetSite 現在傳回授權計數

提供了新的回應元素以在 GetSite API 內傳回不同的授權計數。

受影響的 API:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

GetSiteFTSetSiteFT 重新設計

GetSiteFTSetSiteFT API 已經過重新設計,允許切換動態功能。

受影響的 API:

  • GetSiteFT

  • SetSiteFT

GetSite 請求範例:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <siteName>{siteName}</siteName>
            <accessToken>{這是機器帳戶存取權杖}</accessToken>
        </securityContext>
    </header>
    <bodyContent xsi:type="java:com.webex.service.binding.site.GetSiteFT">
        <featureToggles>
            <name>SupportCrossLaunch</name>
            <name>RemoveCMRLicenseSA</name>
        </featureToggles>
    </bodyContent>

</serv:message>

GetSite 回應範例:

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteFTResponse">
            <ns1:featureToggles>
                <ns1:featureToggle>
                    <ns1:name>SupportCrossLaunch</ns1:name>
                    <ns1:value>false</ns1:value>
                </ns1:featureToggle>
                <ns1:featureToggle>
                    <ns1:name>RemoveCMRLicenseSA</ns1:name>
                    <ns1:value>false</ns1:value>
                </ns1:featureToggle>
            </ns1:featureToggles>
        </serv:bodyContent>
    </serv:body>
</serv:message>

SetSite 請求範例:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <siteName>{siteName}</siteName>
            <accessToken>{這是機器帳戶存取權杖}</accessToken>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.site.SetSiteFT">
            <featureToggles>
                <featureToggle>
                    <name>SupportCrossLaunch</name>
                    <value>false</value>
                </featureToggle>
                <featureToggle>
                    <name>SupportPeopleInsight</name>
                    <value>true</value>
                </featureToggle>
            </featureToggles>
        </bodyContent>
    </body>
</serv:message>

SetSiteFT 回應範例:

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:setSiteFTResponse"/>
    </serv:body>
</serv:message>

會議說明的長度現在限於 2500 個字元

下列 API 的會議說明元素內容長度現在限於 2500 個字元:

受影響的 API:

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

這是為了防止 Cisco Webex 無法處理請求。 如果會議說明長度超過 2500 個字元,則會傳回一則錯誤訊息。

XML API 39.5.0 更新

新元素 videoMeshInterclusters 新增至 SetSite 和 GetSite 綱要

一個名為 videoMeshInterclusters 的新元素已新增至 SetSite 元素。videoMeshInterclusters 還包含三個子元素:videoMeshHomeCluster1videoMeshHomeCluster2videoMeshHomeCluster3

受影響的 API:

  • SetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

SetSite 請求:

GetSite 回應:

XML API 39.3.0 更新

XML API 中的簡短 SIP URL,新元素 displayMeetingUrl

按一下這裡以下載 XML API 39.3 網要。

目前,在加入 Webex 會議時,應用程式或裝置必須提供網站資訊,這會使加入會議變得比較困難。 從 SIP 裝置撥入時尤其如此,因為使用者必須鍵入 meeting_number@sitename.webex.com

若要使加入會議變得更加容易,我們移除了輸入會議 SIP URI 中的網站名稱這項要求: meeting_number@webex.com。

若要保持與舊版相容,sipURL 會使用舊格式,而將新格式附加至新元素 displayMeetingUrl

受影響的 API:

  • GetMeeting

    • displayMeetingUrl

  • GetEvent

    • displayMeetingUrl

  • GetSessionInfo

    • displayMeetingUrl

工作流程圖表

GetMeeting 綱要

GetMeeting 範例回應

    <meet:isCETMeeting>true</meet:isCETMeeting>
    <meet:meetingLink>https://sqdemo.dmz.webex.com/sqdemo/j.php?MTID=m0cdefe09626ba0bec956cdf9088bff55</meet:meetingLink>
    <meet:sipURL>712296997@sqdemo.dmz.webex.com</meet:sipURL>
    <meet:displayMeetingUrl>712296997@dmz.webex.com</meet:displayMeetingUrl>

GetEvent 綱要

GetEvent 範例回應

    <event:hostType>1001001</event:hostType>
    <event:isCETMeeting>true</event:isCETMeeting>
    <event:sipURL>713847821@sqdemo.dmz.webex.com</event:sipURL>
    <event:displayMeetingUrl>713847821@dmz.webex.com</event:displayMeetingUrl>

GetSessionInfo 綱要

GetSessionInfo 範例回應

    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
    <ep:meetingLink>https://sqdemo.dmz.webex.com/sqdemo/j.php?MTID=ee7d38639d0b4a9ed2eb8802cfa2810dd</ep:meetingLink>
    <ep:sipURL>713847821@sqdemo.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>713847821@dmz.webex.com</ep:displayMeetingUrl>

電子郵件範例

說明的長度現在限於 1024 個字元

下列 API 的說明元素內容長度現在限於 1024 個字元:

受影響的 API:

  • CreateTrainingSession

  • SetTrainingSession

  • CreateEvent

  • SetEvent

這是為了防止 Cisco Webex 無法處理請求。 如果說明長度超過 1024 個字元,則會傳回一則錯誤訊息: 「060067 輸入說明無效。 說明不得超過最多 1024 個顯示字元的長度限制。」

說明長度的範例回應超過 1024 個字元

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:sess="http://www.webex.com/schemas/2002/06/service/session" xmlns:train="http://www.webex.com/schemas/2002/06/service/trainingsession" xmlns:qti="http://www.webex.com/schemas/2002/06/service/trainingsessionqti" xmlns:qtiasi="http://www.webex.com/schemas/2002/06/service/trainingsessionqtiasi">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>
輸入說明無效。 說明不得超過最多 1024 個顯示字元的長度限制
            </serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>060067</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

當有匿名使用者在使用 API 時,GetSessionInfo 現在只會傳回個人會議室的基本資訊

為確保更高的安全性,當有匿名出席者在使用 API 時,我們將減少 GetSessionInfo 傳回的資訊量。 在本更新中,我們將減少 API 回應中的下列元素:

受影響的 API:

  • GetSessionInfo

    • <ep:accessControl>

  • <ep:sessionPassword>

    • <ep:telephony>

    • <ep:isAlternateHost>…</ep:isAlternateHost>

    • <ep:isCreator>…</ep:isCreator>

    • <ep:hostKey>…</ep:hostKey>

    • <ep:supportE2E>…</ep:supportE2E>

回應比較

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:isLocked>false</ep:isLocked>
    <ep:sessionkey>712419789</ep:sessionkey>
    <ep:confID>120396209273701973</ep:confID>
    <ep:accessControl>
        <ep:sessionPassword></ep:sessionPassword>   <!--Removed-->
        <ep:listStatus>不公開</ep:listStatus>
        <ep:registration>false</ep:registration>
        <ep:passwordReq>false</ep:passwordReq>
        <ep:isEnforceAudioPassword>false</ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin>false</ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Simon Test 的個人會議室</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType>MeetingCenter</ep:serviceType>
        <ep:isRecurring>false</ep:isRecurring>
        <ep:agendaFormat>文字</ep:agendaFormat>
        <ep:descriptionFormat>文字</ep:descriptionFormat>
        <ep:isException>false</ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException>false</ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>回撥</ep:telephonySupport> <!--Removed-->
        <ep:globalCallInNumbersURL>https://sqdemo6.dmz.webex.com/sqdemo6/globalcallin.php?serviceType=MC&ED=0</ep:globalCallInNumbersURL>   <!--Removed-->
        <ep:tollFreeRestrictionsURL>https://www.webex.com/pdf/tollfree_restrictions.pdf</ep:tollFreeRestrictionsURL>    <!--Removed-->
        <ep:dialInSequences>AutoDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[AttendeeID]#|SilentDialInSequence:[AccessNumber],,*01*[AccessCode]#[AttendeeID]#*01*|AutoLGDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[ProfileID]#,,,[PIN]#|SilentLGDialInSequence:[AccessNumber],,*01*[AccessCode]#[ProfileID]#[PIN]#*01*|AutoLGPWDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[ProfileID]#,,,[PIN]#,,,[Password]#|SilentLGPWDialInSequence:[AccessNumber],,*01*[AccessCode]#[ProfileID]#[PIN]#[Password]#*01*</ep:dialInSequences>  <!--Removed-->
        <ep:callInNum>    <!--Removed-->
            <serv:tollNum>14085452910</serv:tollNum>    <!--Removed-->
            <serv:globalNum>  <!--Removed-->
                <serv:countryAlias>14085452912</serv:countryAlias>  <!--Removed-->
                <serv:phoneNumber>14085452912</serv:phoneNumber>    <!--Removed-->
                <serv:tollFree>false</serv:tollFree>    <!--Removed-->
                <serv:default>false</serv:default>  <!--Removed-->
            </serv:globalNum> <!--Removed-->
        </ep:callInNum>   <!--Removed-->
        <ep:labels>   <!--Removed-->
            <ep:tollFreeCallInLabel>撥入免費號碼(美國/加拿大)</ep:tollFreeCallInLabel>   <!--Removed-->
            <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->
        </ep:labels>  <!--Removed-->
        <ep:isMPAudio>false</ep:isMPAudio>  <!--Removed-->
        <ep:voip>true</ep:voip> <!--Removed-->
        <ep:enableTSP>false</ep:enableTSP>  <!--Removed-->
    </ep:telephony>   <!--Removed-->
    <ep:host>
        <ep:firstName>Simon</ep:firstName>
        <ep:lastName>測試</ep:lastName>
        <ep:email>simon0@qa.webex.com</ep:email>
        <ep:webExId>Simon</ep:webExId>
        <ep:allowAnyoneHostMeeting>false</ep:allowAnyoneHostMeeting>
    </ep:host>
    <ep:schedule>
        <ep:startDate>2068 年 12 月 31 日下午 01:00:00</ep:startDate>
        <ep:duration>720</ep:duration>
        <ep:timeZone>GMT-08:00,太平洋地區(聖荷西)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
        <ep:openTimeInSec>0</ep:openTimeInSec>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>false</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly>false</ep:isAudioOnly>
    <ep:telePresence>false</ep:telePresence>
    <ep:isAlternateHost>false</ep:isAlternateHost>  <!--Removed-->
    <ep:isCreator>true</ep:isCreator>   <!--Removed-->
    <ep:hostKey>954462</ep:hostKey> <!--Removed-->
    <ep:supportE2E>false</ep:supportE2E>    <!--Removed-->
    <ep:isAllowJBH>false</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>true</ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
    <ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed</ep:meetingLink>
    <ep:sipURL>simon0@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>simon0@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
    <ep:isAutoRecord>false</ep:isAutoRecord>
</serv:bodyContent>

XML API 39.2.0 更新

新元素 lastLoginTime 已在 LstSummaryUser 回應中傳回

說明:

新回應元素 lastLoginTime 已新增至 LstSummaryUser API。lastLoginTime 會傳回每個使用者的最後一次登入時間。 採用下列格式傳回元素:

<lastLoginTime>2018 年 4 月 12 日下午 10:40:01**</lastLoginTime>

受影響的 API:

  • LstSummaryUser

    • lastLoginTime

GetAPIVersion 回應:

回應範例:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:use="http://www.webex.com/schemas/2002/06/service/user">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>3469487</use:userID>
                <use:objectGUID>a14e3312-e1d1-4e41-82b9-6ddac80c9f9a</use:objectGUID>
                <use:webExId>sangeetha.swaminathan@gmail.com</use:webExId>
                <use:firstName>Sangee</use:firstName>
                <use:lastName>Gmail</use:lastName>
                <use:email>sangeetha.swaminathan@gmail.com</use:email>
                <use:userRoleType>主持</use:userRoleType>
                <use:registrationDate>2018 年 12 月 11 日下午 02:41:27</use:registrationDate>
                <use:active>DEACTIVATED</use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:lastLoginTime>2018 年 4 月 12 日下午 10:40:01</use:lastLoginTime>
            </use:user>
            <use:matchingRecords>
                <serv:total>1</serv:total>
                <serv:returned>1</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </use:matchingRecords>
        </serv:bodyContent>
    </serv:body>
</serv:message>

XML API 39.1.0 更新

按一下這裡以下載 XML API 39.1.0 網要。

新元素 apiVer 已新增至 API GetAPIVersion

說明:

新回應元素 apiVer 已新增至 GetAPIVersion API。 在此更新中,XML API 版本命名慣例會變更以符合與其他 Cisco Webex 產品區域聯合的版本號碼。apiVer 會傳回新的版本資訊,例如,39.1.0 表示 2019 年 1 月更新。

受影響的 API:

  • GetAPIVersion

    • apiVer

將在 2019 年 5 月 1 日棄用元素 apiVersion,並且將在 2019 年 5 月 1 日為元素 release 指定一個新值 XML API。

GetAPIVersion 回應:

回應範例:

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ep:getAPIVersionResponse">
            <ep:apiVersion>Webex XML API 11.0.0 版</ep:apiVersion>
            <ep:release>SP22</ep:release>
            <ep:apiVer>39.1.0</ep:apiVer>
        </serv:bodyContent>
    </serv:body>
</serv:message>

HQ/HD 參數已從 XML API 中移除

說明:

現在,HQ 和 HD 視訊內容是在網站層次決定,而它們先前是在使用者層次決定。 當從下列 API 傳送請求時,會忽略這些參數的兩個選項:

  • CreateMeeting

  • SetMeeting

  • CreateTrainingSession

  • SetTrainingSession

GetMeetingGetTrainingSession API 仍會傳回兩個選項(由網站層次及使用者層次決定)以避免破壞現有代碼。

這個已變更的行為沒有變更綱要。

新元素 uploadLogFileUrl 已新增至傳回給桌面應用程式的網站中繼資料

說明:

新元素 uploadLogFileUrl 已新增至傳回給桌面應用程式的回應(當桌面應用程式在 XML API 伺服器中呼叫 API getSite 時)。 桌面應用程式可將記錄檔案上傳至 uploadLogFileUrl

受影響的 API:

  • GetSite

    • uploadLogFileUrl

綱要:

回應範例:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="ns1:getSiteResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ns1:siteInstance>
                <ns1:metaData>
                    <ns1:isEnterprise>true</ns1:isEnterprise>
                    <ns1:serviceType>Meeting Center</ns1:serviceType>
                    <ns1:serviceType>Event Center</ns1:serviceType>
                    <ns1:serviceType>Training Center</ns1:serviceType>
                    <ns1:serviceType>Support Center</ns1:serviceType>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>9</ns1:meetingTypeID>
                        <ns1:meetingTypeName>ONS</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>11</ns1:meetingTypeID>
                        <ns1:meetingTypeName>TRS</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>13</ns1:meetingTypeID>
                        <ns1:meetingTypeName>SC3</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>16</ns1:meetingTypeID>
                        <ns1:meetingTypeName>AUO</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>214</ns1:meetingTypeID>
                        <ns1:meetingTypeName>專業版</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:siteName>sqdemo28</ns1:siteName>
                    <ns1:brandName>sqdemo28</ns1:brandName>
                    <ns1:brandName>sqdemo28-de</ns1:brandName>
                    <ns1:brandName>sqdemo28-en</ns1:brandName>
                    <ns1:brandName>sqdemo28-fr</ns1:brandName>
                    <ns1:region>法國</ns1:region>
                    <ns1:currency>法國法郎</ns1:currency>
                    <ns1:timeZoneID>4</ns1:timeZoneID>
                    <ns1:timeZone>GMT-08:00,太平洋日光節約時間(聖荷西)</ns1:timeZone>
                    <ns1:parterID>7Dsupoc6DOfzpgcNViYvUA</ns1:parterID>
                    <ns1:webDomain>sqwd</ns1:webDomain>
                    <ns1:meetingDomain>sqmd</ns1:meetingDomain>
                    <ns1:telephonyDomain>sqtd</ns1:telephonyDomain>
                    <ns1:pageVersion>T33L</ns1:pageVersion>
                    <ns1:clientVersion>T33L</ns1:clientVersion>
                    <ns1:pageLanguage>法文</ns1:pageLanguage>
                    <ns1:activateStatus>true</ns1:activateStatus>
                    <ns1:webPageType>J2EE</ns1:webPageType>
                    <ns1:iCalendar>true</ns1:iCalendar>
                    <ns1:myWebExDefaultPage>我的會議</ns1:myWebExDefaultPage>
                    <ns1:componentVersion>cmp3300</ns1:componentVersion>
                    <ns1:accountNumLimit>999999</ns1:accountNumLimit>
                    <ns1:activeUserCount>40</ns1:activeUserCount>
                    <ns1:displayMeetingActualTime>false</ns1:displayMeetingActualTime>
                    <ns1:displayOffset>true</ns1:displayOffset>
                    <ns1:supportWebEx11>false</ns1:supportWebEx11>
                </ns1:metaData>
                <ns1:ucf>
                    <ns1:ucfConfiguration>UCF 2.1</ns1:ucfConfiguration>
                </ns1:ucf>
                <ns1:clientPlatforms>
                    <ns1:msWindows>true</ns1:msWindows>
                    <ns1:macOS9>true</ns1:macOS9>
                    <ns1:macOSX>true</ns1:macOSX>
                    <ns1:sunSolaris>true</ns1:sunSolaris>
                    <ns1:linux>true</ns1:linux>
                    <ns1:hpUnix>false</ns1:hpUnix>
                    <ns1:java>true</ns1:java>
                    <ns1:palm>false</ns1:palm>
                </ns1:clientPlatforms>
                <ns1:resourceRestrictions>
                    <ns1:isLicenseManager>true</ns1:isLicenseManager>
                    <ns1:concurrentLicense>0</ns1:concurrentLicense>
                    <ns1:fileFolderCapacity>1000</ns1:fileFolderCapacity>
                    <ns1:maxConcurrentEvents>0</ns1:maxConcurrentEvents>
                    <ns1:archiveStorageLimit>0</ns1:archiveStorageLimit>
                </ns1:resourceRestrictions>
                <ns1:supportAPI>
                    <ns1:autoLogin>true</ns1:autoLogin>
                    <ns1:aspAndPHPAPI>true</ns1:aspAndPHPAPI>
                    <ns1:backwardAPI>false</ns1:backwardAPI>
                    <ns1:xmlAPI>true</ns1:xmlAPI>
                    <ns1:cAPI>false</ns1:cAPI>
                    <ns1:scorm>true</ns1:scorm>
                </ns1:supportAPI>
                <ns1:myWebExConfig>
                    <ns1:myContacts>true</ns1:myContacts>
                    <ns1:myProfile>true</ns1:myProfile>
                    <ns1:myMeetings>true</ns1:myMeetings>
                    <ns1:trainingRecordings>true</ns1:trainingRecordings>
                    <ns1:folders>false</ns1:folders>
                    <ns1:eventDocument>true</ns1:eventDocument>
                    <ns1:myReport>false</ns1:myReport>
                    <ns1:myComputer>false</ns1:myComputer>
                    <ns1:personalMeetingPage>false</ns1:personalMeetingPage>
                    <ns1:myFilesStorage>1000</ns1:myFilesStorage>
                    <ns1:myComputerNumbers>0</ns1:myComputerNumbers>
                    <ns1:enableMyWebExPro>true</ns1:enableMyWebExPro>
                    <ns1:myWebExProMaxHosts>999999</ns1:myWebExProMaxHosts>
                    <ns1:restrictAccessAnyApps>false</ns1:restrictAccessAnyApps>
                    <ns1:restrictAccessAnyAppsNum>0</ns1:restrictAccessAnyAppsNum>
                    <ns1:addlAccessAnyComputersLimit>STRICT</ns1:addlAccessAnyComputersLimit>
                    <ns1:addlAccessAnyComputers>0</ns1:addlAccessAnyComputers>
                    <ns1:addlStorageLimit>STRICT</ns1:addlStorageLimit>
                    <ns1:addlStorage>0</ns1:addlStorage>
                    <ns1:myContactsPro>true</ns1:myContactsPro>
                    <ns1:myProfilePro>true</ns1:myProfilePro>
                    <ns1:myMeetingsPro>true</ns1:myMeetingsPro>
                    <ns1:trainingRecordingsPro>true</ns1:trainingRecordingsPro>
                    <ns1:foldersPro>false</ns1:foldersPro>
                    <ns1:eventDocumentPro>true</ns1:eventDocumentPro>
                    <ns1:myReportPro>true</ns1:myReportPro>
                    <ns1:myComputerPro>false</ns1:myComputerPro>
                    <ns1:personalMeetingPagePro>true</ns1:personalMeetingPagePro>
                    <ns1:myFilesStoragePro>1000</ns1:myFilesStoragePro>
                    <ns1:myComputerNumbersPro>0</ns1:myComputerNumbersPro>
                    <ns1:PMRheaderBranding>false</ns1:PMRheaderBranding>
                </ns1:myWebExConfig>
                <ns1:telephonyConfig>
                    <ns1:isTSPUsingTelephonyAPI>false</ns1:isTSPUsingTelephonyAPI>
                    <ns1:serviceName>個人會議號</ns1:serviceName>
                    <ns1:participantAccessCodeLabel>出席者存取碼</ns1:participantAccessCodeLabel>
                    <ns1:subscriberAccessCodeLabel>主持人存取碼</ns1:subscriberAccessCodeLabel>
                    <ns1:attendeeIDLabel>出席者 ID</ns1:attendeeIDLabel>
                    <ns1:internetPhone>true</ns1:internetPhone>
                    <ns1:supportCallInTypeTeleconf>true</ns1:supportCallInTypeTeleconf>
                    <ns1:callInTeleconferencing>true</ns1:callInTeleconferencing>
                    <ns1:tollFreeCallinTeleconferencing>true</ns1:tollFreeCallinTeleconferencing>
                    <ns1:intlCallInTeleconferencing>true</ns1:intlCallInTeleconferencing>
                    <ns1:callBackTeleconferencing>true</ns1:callBackTeleconferencing>
                    <ns1:callInNumber>1</ns1:callInNumber>
                    <ns1:defaultTeleServerSubject>0.0.0.0</ns1:defaultTeleServerSubject>
                    <ns1:subscribeName>問與答</ns1:subscribeName>
                    <ns1:subscribePassword>pass</ns1:subscribePassword>
                    <ns1:defaultPhoneLines>10</ns1:defaultPhoneLines>
                    <ns1:defaultSpeakingLines>10</ns1:defaultSpeakingLines>
                    <ns1:majorCountryCode>1</ns1:majorCountryCode>
                    <ns1:majorAreaCode>408</ns1:majorAreaCode>
                    <ns1:publicName>撥入使用者</ns1:publicName>
                    <ns1:hybridTeleconference>true</ns1:hybridTeleconference>
                    <ns1:instantHelp>false</ns1:instantHelp>
                    <ns1:customerManage>false</ns1:customerManage>
                    <ns1:maxCallersNumber>500</ns1:maxCallersNumber>
                    <ns1:isSpecified>false</ns1:isSpecified>
                    <ns1:isContinue>false</ns1:isContinue>
                    <ns1:intlCallBackTeleconferencing>true</ns1:intlCallBackTeleconferencing>
                    <ns1:personalTeleconf>
                        <ns1:primaryLargeServer>
                            <serv:tollNum>14085452910</serv:tollNum>
                            <serv:globalNum>
                                <serv:countryAlias>14085452912</serv:countryAlias>
                                <serv:phoneNumber>14085452912</serv:phoneNumber>
                                <serv:tollFree>false</serv:tollFree>
                                <serv:default>false</serv:default>
                            </serv:globalNum>
                            <serv:enableServer>true</serv:enableServer>
                            <serv:tollLabel>14085452910</serv:tollLabel>
                            <serv:tollFreeLabel>免費撥入號碼(美國/加拿大)</serv:tollFreeLabel>
                        </ns1:primaryLargeServer>
                        <ns1:backup1LargeServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>付費撥入號碼(美國/加拿大)</serv:tollLabel>
                            <serv:tollFreeLabel>免費撥入號碼(美國/加拿大)</serv:tollFreeLabel>
                        </ns1:backup1LargeServer>
                        <ns1:backup2LargeServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>備份付費撥入號碼(美國/加拿大)</serv:tollLabel>
                            <serv:tollFreeLabel>備份免費撥入號碼(美國/加拿大)</serv:tollFreeLabel>
                        </ns1:backup2LargeServer>
                        <ns1:primarySmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>付費撥入號碼(美國/加拿大)</serv:tollLabel>
                            <serv:tollFreeLabel>免費撥入號碼(美國/加拿大)</serv:tollFreeLabel>
                        </ns1:primarySmallServer>
                        <ns1:backup1SmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>付費撥入號碼(美國/加拿大)</serv:tollLabel>
                            <serv:tollFreeLabel>免費撥入號碼(美國/加拿大)</serv:tollFreeLabel>
                        </ns1:backup1SmallServer>
                        <ns1:backup2SmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>備份付費撥入號碼(美國/加拿大)</serv:tollLabel>
                            <serv:tollFreeLabel>備份免費撥入號碼(美國/加拿大)</serv:tollFreeLabel>
                        </ns1:backup2SmallServer>
                        <ns1:joinBeforeHost>false</ns1:joinBeforeHost>
                    </ns1:personalTeleconf>
                    <ns1:multiMediaPlatform>true</ns1:multiMediaPlatform>
                    <ns1:multiMediaHostName>msa1mcccl01.dmz.webex.com</ns1:multiMediaHostName>
                    <ns1:broadcastAudioStream>true</ns1:broadcastAudioStream>
                    <ns1:tspAdaptorSettings>
                        <ns1:primaryLarge>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>撥入號碼</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>免費撥入號碼</ns1:label>
                            </ns1:mpAudio>
                        </ns1:primaryLarge>
                        <ns1:backup1Large>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>撥入號碼</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>免費撥入號碼</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup1Large>
                        <ns1:backup2Large>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>撥入號碼</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>免費撥入號碼</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup2Large>
                    </ns1:tspAdaptorSettings>
                    <ns1:meetingPlace>
                        <ns1:persistentTSP>false</ns1:persistentTSP>
                        <ns1:mpAudioConferencing>WithoutIntegration</ns1:mpAudioConferencing>
                    </ns1:meetingPlace>
                    <ns1:supportOtherTypeTeleconf>false</ns1:supportOtherTypeTeleconf>
                    <ns1:otherTeleServiceName>其他電話會議服務</ns1:otherTeleServiceName>
                    <ns1:supportAdapterlessTSP>false</ns1:supportAdapterlessTSP>
                    <ns1:displayAttendeeID>false</ns1:displayAttendeeID>
                    <ns1:provisionTeleAccount>true</ns1:provisionTeleAccount>
                    <ns1:choosePCN>false</ns1:choosePCN>
                    <ns1:audioOnly>true</ns1:audioOnly>
                    <ns1:configTollAndTollFreeNum>false</ns1:configTollAndTollFreeNum>
                    <ns1:configPrimaryTS>false</ns1:configPrimaryTS>
                    <ns1:teleCLIAuthEnabled>false</ns1:teleCLIAuthEnabled>
                    <ns1:teleCLIPINEnabled>false</ns1:teleCLIPINEnabled>
                </ns1:telephonyConfig>
                <ns1:commerceAndReporting>
                    <ns1:trackingCode>false</ns1:trackingCode>
                    <ns1:siteAdminReport>true</ns1:siteAdminReport>
                    <ns1:subScriptionService>false</ns1:subScriptionService>
                    <ns1:isECommmerce>false</ns1:isECommmerce>
                    <ns1:customereCommerce>false</ns1:customereCommerce>
                    <ns1:isLocalTax>false</ns1:isLocalTax>
                    <ns1:localTaxName>VAT</ns1:localTaxName>
                    <ns1:localTaxtRate>0,0</ns1:localTaxtRate>
                    <ns1:holReport>1</ns1:holReport>
                </ns1:commerceAndReporting>
                <ns1:tools>
                    <ns1:businessDirectory>false</ns1:businessDirectory>
                    <ns1:officeCalendar>false</ns1:officeCalendar>
                    <ns1:meetingCalendar>true</ns1:meetingCalendar>
                    <ns1:displayOnCallAssistLink>false</ns1:displayOnCallAssistLink>
                    <ns1:displayProfileLink>true</ns1:displayProfileLink>
                    <ns1:recordingAndPlayback>true</ns1:recordingAndPlayback>
                    <ns1:recordingEditor>true</ns1:recordingEditor>
                    <ns1:publishRecordings>true</ns1:publishRecordings>
                    <ns1:instantMeeting>true</ns1:instantMeeting>
                    <ns1:emails>false</ns1:emails>
                    <ns1:outlookIntegration>true</ns1:outlookIntegration>
                    <ns1:wirelessAccess>false</ns1:wirelessAccess>
                    <ns1:allowPublicAccess>true</ns1:allowPublicAccess>
                    <ns1:ssl>true</ns1:ssl>
                    <ns1:handsOnLab>true</ns1:handsOnLab>
                    <ns1:holMaxLabs>999999</ns1:holMaxLabs>
                    <ns1:holMaxComputers>999999</ns1:holMaxComputers>
                    <ns1:userLockDown>false</ns1:userLockDown>
                    <ns1:meetingAssist>false</ns1:meetingAssist>
                    <ns1:sms>false</ns1:sms>
                    <ns1:encryption>NONE</ns1:encryption>
                    <ns1:internalMeeting>false</ns1:internalMeeting>
                    <ns1:enableTP>false</ns1:enableTP>
                    <ns1:enableTPplus>false</ns1:enableTPplus>
                    <ns1:uploadLogFileUrl>https://sqwd.webex.com/logadmin/spr.do?SiteUrl=sqdemo28&LanguageId=1</ns1:uploadLogFileUrl>
                </ns1:tools>
                <ns1:custCommunications>
                    <ns1:displayType>
                        <ns1:prodSvcAnnounce>false</ns1:prodSvcAnnounce>
                        <ns1:trainingInfo>false</ns1:trainingInfo>
                        <ns1:eNewsletters>false</ns1:eNewsletters>
                        <ns1:promotionsOffers>false</ns1:promotionsOffers>
                        <ns1:pressReleases>false</ns1:pressReleases>
                    </ns1:displayType>
                    <ns1:displayMethod>
                        <ns1:email>false</ns1:email>
                        <ns1:fax>false</ns1:fax>
                        <ns1:phone>false</ns1:phone>
                        <ns1:mail>false</ns1:mail>
                    </ns1:displayMethod>
                </ns1:custCommunications>
                <ns1:trackingCodes/>
                <ns1:supportedServices>
                    <ns1:meetingCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>mc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                    </ns1:meetingCenter>
                    <ns1:trainingCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>tc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                    </ns1:trainingCenter>
                    <ns1:supportCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>sc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                        <ns1:webACD>true</ns1:webACD>
                    </ns1:supportCenter>
                    <ns1:eventCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>ec3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                        <ns1:marketingAddOn>false</ns1:marketingAddOn>
                        <ns1:optimizeAttendeeBandwidthUsage>false</ns1:optimizeAttendeeBandwidthUsage>
                    </ns1:eventCenter>
                    <ns1:salesCenter>
                        <ns1:enabled>false</ns1:enabled>
                    </ns1:salesCenter>
                </ns1:supportedServices>
                <ns1:securityOptions>
                    <ns1:passwordExpires>false</ns1:passwordExpires>
                    <ns1:passwordLifetime>0</ns1:passwordLifetime>
                    <ns1:ECMeetingsUnlisted>false</ns1:ECMeetingsUnlisted>
                    <ns1:TCMeetingsUnlisted>false</ns1:TCMeetingsUnlisted>
                    <ns1:allMeetingsUnlisted>true</ns1:allMeetingsUnlisted>
                    <ns1:allMeetingsPassword>true</ns1:allMeetingsPassword>
                    <ns1:joinBeforeHost>false</ns1:joinBeforeHost>
                    <ns1:audioBeforeHost>false</ns1:audioBeforeHost>
                    <ns1:audioBeforeHostEC>false</ns1:audioBeforeHostEC>
                    <ns1:audioBeforeHostTC>false</ns1:audioBeforeHostTC>
                    <ns1:changePersonalURL>true</ns1:changePersonalURL>
                    <ns1:changeUserName>false</ns1:changeUserName>
                    <ns1:meetings>
                        <ns1:strictPasswords>true</ns1:strictPasswords>
                    </ns1:meetings>
                    <ns1:strictUserPassword>true</ns1:strictUserPassword>
                    <ns1:accountNotify>false</ns1:accountNotify>
                    <ns1:requireLoginBeforeSiteAccess>false</ns1:requireLoginBeforeSiteAccess>
                    <ns1:changePWDWhenAutoLogin>false</ns1:changePWDWhenAutoLogin>
                    <ns1:enforceBaseline>true</ns1:enforceBaseline>
                    <ns1:passwordChangeIntervalOpt>false</ns1:passwordChangeIntervalOpt>
                    <ns1:passwordChangeInterval>24</ns1:passwordChangeInterval>
                    <ns1:firstAttendeeAsPresenter>false</ns1:firstAttendeeAsPresenter>
                    <ns1:isEnableUUIDLink>true</ns1:isEnableUUIDLink>
                    <ns1:isEnableUUIDLinkForSAC>true</ns1:isEnableUUIDLinkForSAC>
                    <ns1:enforceRecordingPwdForMC>true</ns1:enforceRecordingPwdForMC>
                    <ns1:enforceRecordingPwdForEC>false</ns1:enforceRecordingPwdForEC>
                    <ns1:enforceRecordingPwdForTC>false</ns1:enforceRecordingPwdForTC>
                    <ns1:enforceRecordingPwdForMisc>true</ns1:enforceRecordingPwdForMisc>
                </ns1:securityOptions>
                <ns1:defaults>
                    <ns1:emailReminders>true</ns1:emailReminders>
                    <ns1:entryExitTone>BEEP</ns1:entryExitTone>
                    <ns1:voip>true</ns1:voip>
                    <ns1:teleconference>
                        <ns1:telephonySupport>CALLBACK</ns1:telephonySupport>
                        <ns1:tollFree>true</ns1:tollFree>
                        <ns1:intlLocalCallIn>true</ns1:intlLocalCallIn>
                    </ns1:teleconference>
                    <ns1:joinTeleconfNotPress1>false</ns1:joinTeleconfNotPress1>
                    <ns1:updateTSPAccount>false</ns1:updateTSPAccount>
                </ns1:defaults>
                <ns1:scheduleMeetingOptions>
                    <ns1:scheduleOnBehalf>true</ns1:scheduleOnBehalf>
                    <ns1:saveSessionTemplate>true</ns1:saveSessionTemplate>
                </ns1:scheduleMeetingOptions>
                <ns1:navBarTop>
                    <ns1:button>
                        <ns1:order>1</ns1:order>
                        <ns1:serviceName>歡迎</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>2</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Meeting Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>3</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Event Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>4</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Support Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>5</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Training Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>6</ns1:order>
                        <ns1:serviceName>網站管理</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>7</ns1:order>
                        <ns1:enabled>false</ns1:enabled>
                        <ns1:serviceName>Sales Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:displayDisabledService>true</ns1:displayDisabledService>
                </ns1:navBarTop>
                <ns1:navMyWebEx>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:partnerLinks>
                        <ns1:partnerLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:partnerLink>
                    </ns1:partnerLinks>
                    <ns1:partnerIntegration>true</ns1:partnerIntegration>
                    <ns1:support>
                        <ns1:target>NEW</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:target>NEW</ns1:target>
                    </ns1:training>
                </ns1:navMyWebEx>
                <ns1:navAllServices>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:support>
                        <ns1:name>支援</ns1:name>
                        <ns1:target>NEW</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:name>訓練</ns1:name>
                        <ns1:target>NEW</ns1:target>
                    </ns1:training>
                    <ns1:supportMenu>
                        <ns1:userGuides>
                            <ns1:target>NEW</ns1:target>
                        </ns1:userGuides>
                        <ns1:downloads>
                            <ns1:target>NEW</ns1:target>
                        </ns1:downloads>
                        <ns1:training>
                            <ns1:target>NEW</ns1:target>
                        </ns1:training>
                        <ns1:contactUs>
                            <ns1:target>NEW</ns1:target>
                        </ns1:contactUs>
                        <ns1:supportMyResources>true</ns1:supportMyResources>
                    </ns1:supportMenu>
                </ns1:navAllServices>
                <ns1:passwordCriteria>
                    <ns1:mixedCase>false</ns1:mixedCase>
                    <ns1:minLength>4</ns1:minLength>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallowWebTextSessions>true</ns1:disallowWebTextSessions>
                    <ns1:disallowWebTextAccounts>true</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>true</ns1:disallowList>
                    <ns1:disallowValue>密碼</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>pass</ns1:disallowValue>
                </ns1:passwordCriteria>
                <ns1:recordingPasswordCriteria>
                    <ns1:mixedCase>true</ns1:mixedCase>
                    <ns1:minLength>8</ns1:minLength>
                    <ns1:minAlpha>2</ns1:minAlpha>
                    <ns1:minNumeric>1</ns1:minNumeric>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallowWebTextSessions>false</ns1:disallowWebTextSessions>
                    <ns1:disallowList>false</ns1:disallowList>
                    <ns1:disallowValue>密碼</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>pass</ns1:disallowValue>
                </ns1:recordingPasswordCriteria>
                <ns1:accountPasswordCriteria>
                    <ns1:mixedCase>false</ns1:mixedCase>
                    <ns1:minLength>0</ns1:minLength>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallow3XRepeatedChar>false</ns1:disallow3XRepeatedChar>
                    <ns1:disallowWebTextAccounts>true</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>true</ns1:disallowList>
                    <ns1:disallowValue>密碼</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>pass</ns1:disallowValue>
                    <ns1:disallowValue>Webex</ns1:disallowValue>
                    <ns1:disallowValue>cisco</ns1:disallowValue>
                    <ns1:disallowValue>xebew</ns1:disallowValue>
                    <ns1:disallowValue>ocsic</ns1:disallowValue>
                </ns1:accountPasswordCriteria>
                <ns1:productivityTools>
                    <ns1:enable>true</ns1:enable>
                    <ns1:installOpts>
                        <ns1:autoUpdate>true</ns1:autoUpdate>
                    </ns1:installOpts>
                    <ns1:integrations>
                        <ns1:outlook>true</ns1:outlook>
                        <ns1:outlookForMac>true</ns1:outlookForMac>
                        <ns1:lotusNotes>true</ns1:lotusNotes>
                        <ns1:oneClick>true</ns1:oneClick>
                        <ns1:showSysTrayIcon>true</ns1:showSysTrayIcon>
                        <ns1:office>true</ns1:office>
                        <ns1:excel>true</ns1:excel>
                        <ns1:powerPoint>true</ns1:powerPoint>
                        <ns1:word>true</ns1:word>
                        <ns1:IE>true</ns1:IE>
                        <ns1:firefox>false</ns1:firefox>
                        <ns1:explorerRightClick>false</ns1:explorerRightClick>
                        <ns1:instantMessenger>true</ns1:instantMessenger>
                        <ns1:aolMessenger>false</ns1:aolMessenger>
                        <ns1:googleTalk>false</ns1:googleTalk>
                        <ns1:lotusSametime>true</ns1:lotusSametime>
                        <ns1:skype>true</ns1:skype>
                        <ns1:windowsMessenger>true</ns1:windowsMessenger>
                        <ns1:yahooMessenger>false</ns1:yahooMessenger>
                        <ns1:ciscoIPPhone>false</ns1:ciscoIPPhone>
                        <ns1:pcNow>false</ns1:pcNow>
                        <ns1:iGoogle>false</ns1:iGoogle>
                        <ns1:iPhoneDusting>true</ns1:iPhoneDusting>
                    </ns1:integrations>
                    <ns1:oneClick>
                        <ns1:allowJoinUnlistMeeting>true</ns1:allowJoinUnlistMeeting>
                        <ns1:requireApproveJoin>false</ns1:requireApproveJoin>
                    </ns1:oneClick>
                    <ns1:templates>
                        <ns1:useTemplate>false</ns1:useTemplate>
                    </ns1:templates>
                    <ns1:lockDownPT>
                        <ns1:lockDown>false</ns1:lockDown>
                    </ns1:lockDownPT>
                    <ns1:imSettings>
                        <ns1:attendeeInviteOther>true</ns1:attendeeInviteOther>
                    </ns1:imSettings>
                </ns1:productivityTools>
                <ns1:meetingPlace/>
                <ns1:salesCenter>
                    <ns1:allowJoinWithoutLogin>false</ns1:allowJoinWithoutLogin>
                </ns1:salesCenter>
                <ns1:connectIntegration>
                    <ns1:integratedWebEx11>false</ns1:integratedWebEx11>
                </ns1:connectIntegration>
                <ns1:video>
                    <ns1:HQvideo>true</ns1:HQvideo>
                    <ns1:maxBandwidth>MEDIUM</ns1:maxBandwidth>
                    <ns1:HDvideo>true</ns1:HDvideo>
                </ns1:video>
                <ns1:siteCommonOptions>
                    <ns1:SupportCustomDialRestriction>false</ns1:SupportCustomDialRestriction>
                    <ns1:SupportTelePresence>false</ns1:SupportTelePresence>
                    <ns1:SupportTelePresencePlus>false</ns1:SupportTelePresencePlus>
                    <ns1:EnableCloudTelepresence>true</ns1:EnableCloudTelepresence>
                    <ns1:EnableCMRForAllUsers>true</ns1:EnableCMRForAllUsers>
                    <ns1:enablePersonalMeetingRoom>true</ns1:enablePersonalMeetingRoom>
                    <ns1:SupportAlternateHost>true</ns1:SupportAlternateHost>
                    <ns1:SupportAnyoneHostMeetings>true</ns1:SupportAnyoneHostMeetings>
                </ns1:siteCommonOptions>
                <ns1:samlSSO>
                    <ns1:enableSSO>false</ns1:enableSSO>
                    <ns1:autoAccountCreation>false</ns1:autoAccountCreation>
                </ns1:samlSSO>
                <ns1:attendeeLimitation>
                    <ns1:maxInviteesNumberForMC>1000</ns1:maxInviteesNumberForMC>
                    <ns1:maxRegistrantsNumberForMC>1000</ns1:maxRegistrantsNumberForMC>
                    <ns1:maxInviteesNumberForTC>1000</ns1:maxInviteesNumberForTC>
                    <ns1:maxRegistrantsNumberForTC>1000</ns1:maxRegistrantsNumberForTC>
                    <ns1:maxInviteesNumberForEC>10000</ns1:maxInviteesNumberForEC>
                    <ns1:maxRegistrantsNumberForEC>10000</ns1:maxRegistrantsNumberForEC>
                </ns1:attendeeLimitation>
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForCMRHost>200</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>true</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>40</ns1:accountNumberUsedForCMRHost>
                    <ns1:accountNumberLimitForEEHost>200</ns1:accountNumberLimitForEEHost>
                    <ns1:allowOverageForEEHost>true</ns1:allowOverageForEEHost>
                    <ns1:accountNumberUsedForEEHost>40</ns1:accountNumberUsedForEEHost>
                    <ns1:attendeeCapacityForMC>200</ns1:attendeeCapacityForMC>
                    <ns1:attendeeCapacityForTC>200</ns1:attendeeCapacityForTC>
                    <ns1:attendeeCapacityForEC>200</ns1:attendeeCapacityForEC>
                    <ns1:attendeeCapacityForSC>200</ns1:attendeeCapacityForSC>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

XML API 11.0.0 SP22 更新

檔案大小限制(針對 UploadPMRImage)

使用 API UploadPMRImage 來上傳頭像時,新的限制將檔案大小限制為 5 MB。 現在,嘗試上傳大於此大小的檔案將會收到錯誤訊息: 「010100 上傳的影像大小太大。 請嘗試上傳大小小於 5MB 的影像。

XML API 11.0.0 SP21 更新

按一下這裡以下載 XML API 11.0 SP21 網要。

新元素 autoRecord 已新增至 API CreateMeeting、SetMeeting、GetMeetingLstMeeting

說明:

名為 autoRecord 的新元素已新增至 CreateMeeting、SetMeeting、GetMeetingLstMeeting API。autoRecord 允許人員自動從會議排程器錄製 Webex Meetings。 這會提供會議層級的精度,在此情況下,用來自動錄製會議的舊方法只能在網站層級上以廣域方式存取。

附註: 目前,autoRecord 元素僅適用於 Webex Meetings。 它不適用於 Webex Events 或 Webex Training。

受影響的 API:

  • CreateMeeting

    • autoRecord

  • SetMeeting

    • autoRecord

  • GetMeeting

    • autoRecord

  • LstMeeting

    • autoRecord

綱要變更

CreateMeeting:

autoRecord 設定

在「網站管理」頁面上停用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True

在會議開始時自動開始錄製。

False(預設值)

在會議開始時不自動開始錄製。

無元素

在會議開始時不自動開始錄製。

autoRecord 設定

在「網站管理」頁面上啟用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

TrueFalse 或無元素

忽略 XML 請求中的 元素 autoRecord。 在會議開始時自動開始錄製,因為它已在「網站管理」頁面上啟用。

設定會議:

autoRecord 設定

在「網站管理」頁面上停用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True

在會議開始時自動開始錄製。

False(預設值)

在會議開始時不自動開始錄製。

無元素

在會議開始時不自動開始錄製。

autoRecord 設定

在「網站管理」頁面上啟用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

TrueFalse 或無元素

忽略 XML 請求中的 元素 autoRecord。 在會議開始時自動開始錄製,因為它已在「網站管理」頁面上啟用。

GetMeeting:

autoRecord 設定

在「網站管理」頁面上停用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True

在會議開始時自動開始錄製。

False

在會議開始時不自動開始錄製。

autoRecord 設定

在「網站管理」頁面上啟用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True(永遠)

在會議開始時自動開始錄製,因為它已在「網站管理」頁面上啟用。

範例 GetMeeting 回應:

LstMeeting:

autoRecord 設定

在「網站管理」頁面上停用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True

在會議開始時自動開始錄製。

False

在會議開始時不自動開始錄製。

autoRecord 設定

在「網站管理」頁面上啟用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True(永遠)

在會議開始時自動開始錄製,因為它已在「網站管理」頁面上啟用。

範例 LstMeeting 回應:

新元素 isAutoRecord 已新增至 API GetSessionInfo

說明:

除了對上述 API 進行的變更以外,新元素 isAutoRecord 也已新增至 GetSessionInfo API。 此元素可用來指定在會議開始時自動開始錄製。

受影響的 API:

  • GetSessionInfo

    • isAutoRecord

綱要變更

GetSessionInfo:

isAutoRecord 設定

在「網站管理」頁面上停用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True

在會議開始時自動開始錄製。

False

在會議開始時不自動開始錄製。

isAutoRecord 設定

在「網站管理」頁面上啟用「使用網路型錄製功能自動錄製所有階段作業」時的行為。

True(永遠)

在會議開始時自動開始錄製,因為它已在「網站管理」頁面上啟用。

範例 GetSessionInfo 回應:

XML API 11.0.0 SP20 更新

新元素 returnShareToMeRecording 已新增至 API LstRecording 請求

按一下這裡以下載 XML API 11.0 SP20 網要。


此內容先前在 XML API 11.0 SP17 中宣告過,但正在套用至本更新。

一個名為 returnShareToMeRecording 的新元素已新增至 LstRecording API。returnShareToMeRecording 在對 LstRecording 的請求中是一個布林值。

已新增此新元素以支援擷取出席者或受邀者的錄製檔。returnShareToMeRecording 是讓 API LstRecording 知道它必須傳回出席者或受邀者錄製檔的標幟。

returnShareToMeRecording 設定為 True 時,LstRecording 傳回作為所有者的錄製檔使用者,而且也傳回作為所有者共用的出席者或受邀者的錄製檔使用者。 附註: 如果同時關閉自動共用和手動共用標幟,則 LstRecording 僅傳回作為錄製檔所有者的使用者。

returnShareToMeRecording 設定為 False,或請求中不包括此元素時,LstRecording 遵循之前相同的邏輯: 它傳回作為所有者的錄製檔使用者。

受影響的 XML API 和元素:

  • LstRecording

    • returnShareToMeRecording(新)

綱要

已知問題

元素 shareToMe 已新增至 API LstRecording 回應


此內容先前在 XML API 11.0 SP17 中宣告過,但正在套用至本更新。

一個名為 shareToMe 的新元素已被新增至 LstRecording API。shareToMe 在對 LstRecording 的回應中是一個布林值。

已新增此新元素以支援擷取出席者或受邀者的錄製檔。shareToMe 是一個定義針對當前錄製檔,該使用者是所有者、出席者或是受邀者的標幟。

shareToMe 設為 True,該使用者不是當前錄製檔的所有者。 該使用者可能是出席者或受邀者,或錄製檔是由所有者共用的。

shareToMe 設為 False,或回應中不包括此元素時,LstRecording 遵循之前相同的邏輯: 該使用者是當前錄製檔的所有者。

受影響的 XML API 和元素:

  • LstRecording

    • shareToMe(新)

綱要

已知問題

returnShareToMeRecordingshareToMe 的 XML 範例

XML 請求範例

XML 回應範例

新元素已新增至 API GetEvent

四個新元素已新增至 GetEvent API:

  • isCETMeeting: 布林值 True/False 指出 Webex 活動是否支援 Webex 視訊平台 2 (CMR 4.0)

  • sipURL: 用來透過視訊會議系統或應用程式加入 Webex 視訊會議的 URL

  • standaloneDialingIPAddress: 可用來透過視訊會議系統或應用程式撥入 Webex 視訊會議的 IP 位址

  • panelistNumericPassword: 用來透過視訊會議系統或應用程式加入 Webex 視訊會議的密碼

如果網站支援 Webex 視訊,則主持人具有 Webex Events 視訊特權,且活動支援 Webex 視訊平台 2 (CMR 4.0),GetEvent 會傳回以下四個新元素。 否則,GetEvent 不會傳回以下四個新元素。

受影響的 XML API 和元素:

  • GetEvent

    • isCETMeeting(新)

    • sipURL(新)

    • standaloneDialingIPAddress(新)

    • panelistNumericPassword(新)

已知問題

新元素 panelistNumericPassword 已新增至 API GetSessionInfo

GetSessionInfo 具有新元素 panelistNumericPassword,其中包含用來透過視訊會議系統或應用程式加入 Webex 視訊會議的密碼。

此外,如果網站支援 Webex 視訊,則主持人具有 Webex Events 視訊特權,且活動支援 Webex 視訊平台 2 (CMR 4.0),GetSessionInfo 會傳回以下四個元素:

  • isCETMeeting: 布林值 True/False 指出 Webex 活動是否支援 Webex 視訊平台 2 (CMR 4.0)

  • sipURL: 用來透過視訊會議系統或應用程式加入 Webex 視訊會議的 URL

  • standaloneDialingIPAddress: 可用來透過視訊會議系統或應用程式撥入 Webex 視訊會議的 IP 位址

  • panelistNumericPassword: 用來透過視訊會議系統或應用程式加入 Webex 視訊會議的密碼

請注意,對於 Webex Meetings,以下三個元素已在 GetSessionInfo 中:

  • isCETMeeting

  • sipURL

  • standaloneDialingIPAddress

受影響的 XML API 和元素:

  • GetSessionInfo

    • panelistNumericPassword(新)

已知問題

GetEventGetSessionInfo 已變更綱要

GetEvent

GetSessionInfo

XML API 11.0.0 SP18 更新

新元素 EnableCloudTelepresence 已新增至 API getSite

按一下這裡以下載 XML API 11.0 SP18 網要。

一個名為 EnableCloudTelepresence 的新元素已新增至 getSite API。

當選項 EnableCETForAllUsers 已啟用,Webex 將檢查使用者是否支援 Webex 視訊 (CMR)。 它現在也會傳回一個新元素 EnableCloudTelepresence(在 getSite API 中)。

受影響的 XML API

  • getSite

  • EnableCloudTelepresence(新增)

綱要

範例 XML 回應

已知問題

XML API 11.0.0 SP17 更新

新元素 returnShareToMeRecording 已新增至 API LstRecording 請求

一個名為 returnShareToMeRecording 的新元素已新增至 LstRecording API。returnShareToMeRecording 在對 LstRecording 的請求中是一個布林值。

已新增此新元素以支援擷取出席者或受邀者的錄製檔。returnShareToMeRecording 是讓 API LstRecording 知道它必須傳回出席者或受邀者錄製檔的標幟。

returnShareToMeRecording 設定為 True 時,LstRecording 傳回作為所有者的錄製檔使用者,而且也傳回作為所有者共用的出席者或受邀者的錄製檔使用者。 附註: 如果同時關閉自動共用和手動共用標幟,則 LstRecording 僅傳回作為錄製檔所有者的使用者。

returnShareToMeRecording 設定為 False,或請求中不包括此元素時,LstRecording 遵循之前相同的邏輯: 它傳回作為所有者的錄製檔使用者。

受影響的 XML API

  • LstRecording

  • returnShareToMeRecording(新)

綱要

已知問題

新元素 shareToMe 已新增至 API LstRecording 回應

一個名為 shareToMe 的新元素已被新增至 LstRecording API。shareToMe 在對 LstRecording 的回應中是一個布林值。

已新增此新元素以支援擷取出席者或受邀者的錄製檔。shareToMe 是一個定義針對當前錄製檔,該使用者是所有者、出席者或是受邀者的標幟。

shareToMe 設為 True,該使用者不是當前錄製檔的所有者。 該使用者可能是出席者或受邀者,或錄製檔是由所有者共用的。

shareToMe 設為 False,或回應中不包括此元素時,LstRecording 遵循之前相同的邏輯: 該使用者是當前錄製檔的所有者。

受影響的 XML API

  • LstRecording

  • shareToMe(新)

綱要

針對出席者容量的新元素已新增至 API getSite 回應

四個新元素已新增至 API getSite 以分別為四種 Webex 產品指定出席者容量:

attendeeCapacityForMC - Webex Meetings

attendeeCapacityForEC – Webex Events

attendeeCapacityForTC – Webex Training

attendeeCapacityForSC – Webex Support

這些傳回值表示會議、活動或課程可以容納的出席者人數上限。 它們是回應 CISiteLicenseInfo 中元素的子項。

受影響的 XML API:

  • getSite

  • attendeeCapacityForMC(新增)

  • attendeeCapacityForEC(新增)

  • attendeeCapacityForTC(新增)

  • attendeeCapacityForSC(新增)

綱要

範例 getSite 回應

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
            <ns1:siteInstance>
...
...
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
                    <ns1:allowOverageForMC>false</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>false</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC>false</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>false</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>false</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                    <ns1:attendeeCapacityForMC>1000</ns1:attendeeCapacityForMC>
                    <ns1:attendeeCapacityForTC>1000</ns1:attendeeCapacityForTC>
                    <ns1:attendeeCapacityForEC>3000</ns1:attendeeCapacityForEC>
                    <ns1:attendeeCapacityForSC>500</ns1:attendeeCapacityForSC>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

已知問題

XML API 11.0.0 SP16 更新

新 API hostStreamURL 已新增至 lstRecordingResponse

元素 hostStreamURL 已新增至 LstRecording 回應作為錄製檔詳細資料的一部分。hostStreamURL 傳回讓主持人用來檢視錄製檔,而不必先登入的 URL。 此 URL 在它產生後的 30 分鐘內有效。

受影響的 XML API

hostStreamURL

綱要

<xsd:complexType name="recordingType">
<xsd:sequence>
<xsd:element name="recordingID" type="xsd:int"/>
<xsd:element name="hostWebExID" type="xsd:string"/>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="description" type="xsd:string"/>
<xsd:element name="createTime" type="xsd:string"/>
<xsd:element name="timeZoneID" type="xsd:int"/>
<xsd:element name="size" type="xsd:float"/>
<xsd:element name="streamURL" type="xsd:string"/>
<xsd:element name="hostStreamURL" type="xsd:string" minOccurs="0"/>
<xsd:element name="fileURL" type="xsd:string"/>

GetSite API 使用新 WebDB 模型傳回資料

根據客戶請求,API GetSite 現在會擷取更為精確的主持人授權、使用報告資料,和使用新 WebDB 模型的 CI 網站的其他資料。

受影響的 XML API

GetSite

綱要

範例 getSite 一般網站的回應

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
            <ns1:siteInstance>
...
...
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
                    <ns1:allowOverageForMC>false</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>false</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC>false</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>false</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>false</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

範例 getSite EE 網站的回應

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
            <ns1:siteInstance>
...
...
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForCMRHost>80</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>true</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>99</ns1:accountNumberUsedForCMRHost>
                    <ns1:accountNumberLimitForEEHost>999999</ns1:accountNumberLimitForEEHost>
                    <ns1:allowOverageForEEHost>false</ns1:allowOverageForEEHost>
                    <ns1:accountNumberUsedForEEHost>368</ns1:accountNumberUsedForEEHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

XML API 11.0.0 SP15 更新

使用 GetSessionsInfo API 傳回 Webex Meetings 會議鏈結

GetSessionInfo API 的網要有新的傳回值 meetingLink。 您可以使用會議鏈結作為主持人開始 Webex 會議,或作為出席者加入 Webex 會議。

受影響的 XML API

  • GetSessionInfo

  • meetingLink

綱要變更

XML 回應範例

GetSessionInfo 回應範例

    <ep:meetingLink>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=m265e64705c6660d4132c2d4f19aed7e7</ep:meetingLink>

透過 RecordingID(在 LstRecording API 中)的新查詢條件

您現在可以使用 LstRecording 以查詢使用 recordingID 的錄製檔。

共有兩種類型的錄製檔 ID:

  • 針對 Webex Meetings、Webex Events 和 Webex Training 的錄製檔 ID

  • 針對其他的 NBR 錄製檔 ID

如果 XML 請求中有 serviceType 元素,則 LstRecording 僅傳回服務錄製檔(Webex Meetings、Webex Events 和 Webex Training)。

如果 XML 請求中沒有 serviceType 元素,則 LstRecording 僅傳回 NBR 錄製檔。

受影響的 XML API

  • LstRecording

  • RecordingID

綱要變更

服務錄製檔 ID 的 XML 請求範例

<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
    <serviceTypes>
        <serviceType>MeetingCenter</serviceType>
        <serviceType>EventCenter</serviceType>
        <serviceType>TrainingCenter</serviceType>
    </serviceTypes>
    <recordingID>974164492</recordingID>
    <order>
         <orderBy>CREATETIME</orderBy>
         <orderAD>DESC</orderAD>
         <orderBy>HOSTID</orderBy>
         <orderAD>ASC</orderAD>
         <orderBy>RECORDNAME</orderBy>
         <orderAD>ASC</orderAD>
    </order>
</bodyContent>

NBR 錄製檔 ID 的 XML 請求範例

<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
    <recordingID>974154032</recordingID>
    <order>
         <orderBy>CREATETIME</orderBy>
         <orderAD>DESC</orderAD>
         <orderBy>HOSTID</orderBy>
         <orderAD>ASC</orderAD>
         <orderBy>RECORDNAME</orderBy>
         <orderAD>ASC</orderAD>
    </order>
</bodyContent>

XML API 11.0.0 SP14 更新

Meeting Center 初步使用摘要報告

已為 Meeting Center 初步報告新增兩個新的 API:LstmeetingusagePreliminaryHistoryLstmeetingattendeePreliminaryHistory。 在最終報告中,這些 API 與 LsteventsessionPreliminaryHistoryLsteventattendeePreliminaryHistory 具有相同的行為。

受影響的 XML API

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

綱要

LstmeetingusagePreliminaryHistory 請求:

LstmeetingusagePreliminaryHistory 回應:

LstmeetingattendeePreliminaryHistory 請求:

LstmeetingattendeePreliminaryHistory 回應:

範例請求/回應

LstmeetingusagePreliminaryHistory 請求

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <webExID>testuser</webExID>
            <password>****</password>
            <siteName>testsite</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingusagePreliminaryHistory">
            <startTimeScope>
                <sessionStartTimeStart>2018 年 4 月 23 日上午 12:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>2018 年 4 月 24 日上午 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>和</listMethod>
            </listControl>
            <order>
                <orderBy>STARTTIME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFNAME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

LstmeetingusagePreliminaryHistory 回應

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:history="http://www.webex.com/schemas/2002/06/service/history">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingusagePreliminaryHistoryResponse">
            <history:meetingUsagePreliminaryHistory>
                <history:confID>93115261364733685</history:confID>
                <history:sessionKey>800150023</history:sessionKey>
                <history:confName>200804231215</history:confName>
                <history:openTime>2018 年 4 月 23 日下午 07:16:34</history:openTime>
                <history:timeZoneID>4</history:timeZoneID>
                <history:meetingType>專業版</history:meetingType>
                <history:timeZoneWithDST>舊金山(太平洋日光節約時間,GMT-07:00)</history:timeZoneWithDST>
                <history:trackingCode>
                    <com:trackingCode1>mytrackingcode1</com:trackingCode1>
                    <com:trackingCode2>mytrackingcode2</com:trackingCode2>
                </history:trackingCode>
                <history:registered>1</history:registered>
                <history:invited>1</history:invited>
                <history:attended>3</history:attended>
            </history:meetingUsagePreliminaryHistory>
            <history:matchingRecords>
                <serv:total>1</serv:total>
                <serv:returned>1</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
        </serv:bodyContent>
    </serv:body>
</serv:message>

LstmeetingattendeePreliminaryHistory 請求

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <webExID>testuser</webExID>
            <password>****</password>
            <siteName>testsite</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingattendeePreliminaryHistory">
            <startTimeScope>
                <sessionStartTimeStart>2018 年 4 月 23 日上午 12:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>2018 年 4 月 24 日上午 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>和</listMethod>
            </listControl>
            <order>
                <orderBy>STARTTIME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

LstmeetingattendeePreliminaryHistory 回應

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:history="http://www.webex.com/schemas/2002/06/service/history">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingattendeePreliminaryHistoryResponse">
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:company>XYZ</history:company>
                <history:title>DJ</history:title>
                <history:phoneNumber>1,222,654-3210,,,,</history:phoneNumber>
                <history:address1>1 任意街道</history:address1>
                <history:address2>xyz</history:address2>
                <history:city>聖荷西</history:city>
                <history:state>CA</history:state>
                <history:country>美國</history:country>
                <history:zipCode>95111</history:zipCode>
                <history:name>使用者 test2</history:name>
                <history:email>ut2@qa.webex.com</history:email>
                <history:joinTime>2018 年 4 月 23 日下午 07:13:06</history:joinTime>
                <history:participantType>出席者</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name>zzz zzzz</history:name>
                <history:email>z6@webex.com</history:email>
                <history:joinTime>2018 年 4 月 23 日下午 07:14:10</history:joinTime>
                <history:participantType>出席者</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name>測驗主持人</history:name>
                <history:email>testuser@webex.com</history:email>
                <history:joinTime>2018 年 4 月 23 日下午 07:12:42</history:joinTime>
                <history:participantType>出席者</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:matchingRecords>
                <serv:total>3</serv:total>
                <serv:returned>3</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
        </serv:bodyContent>
    </serv:body>
</serv:message>

已知問題

從 GLA GetsessionInfo API 傳回 SIP URL 和 Skype URL

兩個名為 <sipURL><skypeURL> 的新元素已附加至回應(當呼叫 GLA GetSessionInfo API 時)。 這兩個元素是可以透過匿名存取傳回的基本元素。

  • <sipURL> 可用於從 TelePresence 裝置或其他 Cisco 視訊裝置加入會議,因此僅適用於使用 Cisco 視訊平台版本 1.0 或 2.0 的會議,GetSessionInfo 應該傳回元素 <sipURL>

  • <skypeURL> 可用於從 Microsoft Skype 應用程式加入會議,而無需任何限制或條件,因此它可以被每個呼叫傳回。

受影響的 XML API

GetSessionInfo

範例回應

已知問題

傳回 SIP URL 及會議鏈結(從 GetMeeting API)

三個名為 <isCETMeeting><meetingLink><sipURL> 的新元素已附加至回應(當呼叫 GetMeeting API)時。

  • <isCETMeeting> 可瞭解會議是否正在使用 Cisco 視訊平台(支援 TelePresence 和視訊)。

  • <meetingLink> 可開始或加入會議。 主持人可以使用它來開始會議。 出席者可以使用它來加入會議。

  • <sipURL> 可用於從 TelePresence 裝置或其他 Cisco 視訊裝置加入會議,因此僅適用於使用 Cisco 視訊平台版本 1.0 或 2.0 的會議,GetMeeting 應該傳回元素。

受影響的 XML API

GetMeeting

綱要

範例回應

已知問題

XML API 11.0.0 SP13 更新

棄用母項中 <siteID> 元素聲明 <securityContext>

Cisco 計劃棄用 <siteID> 元素(位於母項 <securityContext> 元素中)並將其取代為 <siteName>。 這樣做是因為大量 <siteID> 元素在網站移轉期間經常被變更,並且需要較高的維護成本才能保持使用此元素。 這是一個提前兩年的通知。

  • 對於現有的 Webex 客戶,影響將於 2020 年 5 月 1 日發生。

  • 新客戶必須使用 <siteName> 元素(從 2018 年 5 月 1 日開始)。

  • 與 CI、Spark 或 Atlas 系統進行整合的客戶必須從 2018 年 5 月 1 日開始使用 <siteName> 元素。

受影響的 XML API

  • <siteName>

  • <securityContext>

<tollCallInData><tollFreeCallInData> 元素的資料驗證

從開始年 6 月 1 日,<tollCallInData><tollFreeCallInData> 這兩個 API 將進行資料驗證。 這會影響 <CreateUser><SetUser> API。

在撥入資料中使用無效字串或不正確格式化的字串的網站,必須更正這些字串,以使這些元素通過資料驗證。

以下是範例 XML API CreateUserSetUsertollCallInDatatollFreeCallInData 的正確格式:

<tspAccount>
    <tspAccount>
        <tollFreeCallInNumber>86,123,4567000</tollFreeCallInNumber>
        <tollFreeCallInData>1,86</tollFreeCallInData>
        <accountIndex>1</accountIndex>
        <tollCallInNumber>86,123,4567890</tollCallInNumber>
        <tollCallInData>0,86</tollCallInData>
        <subscriberAccessCode>12341234</subscriberAccessCode>
        <participantAccessCode>12341234</participantAccessCode>
        <createOnBridge>false</createOnBridge>
        <defaultFlag>false</defaultFlag>
    </tspAccount>
</tspAccount>
...

XML API 11.0.0 SP12 更新

兩個新 API SetContactDelContacts

XML API 綱要先前僅有兩個 API:CreateContactsLstContacts,其中沒有提供完整的使用者聯絡人管理功能。 為了使用 XML API 提供更好的功能來管理使用者聯絡人,我們已新增以下兩個新 API:SetContactDelContacts

受影響的 XML API

新 API SetContactDelContacts

API

附註

SetContact

呼叫此 API 可修改一項聯絡人資訊,例如電子郵件、姓名、職務、語言等。

例外:

  • 如果不能按元素 contactEmail 找到聯絡人,會傳回例外狀況 140004「找不到聯絡人」

  • 如果 Webex 網站不支援給定的語言,會傳回例外狀況 030060「不是有效的語言」

  • 如果使用者想要變更的新電子郵件地址已與另一個在「我的聯絡人」清單中的聯絡人重複,會傳回例外狀況 140001「電子郵件由另一個聯絡人使用」

DelContacts

根據給定的電子郵件地址,呼叫此 API 以從「我的聯絡人」清單中刪除一個或多個聯絡人。

如果給定的電子郵件地址可從「我的聯絡人」清單中找到,則傳回 contactID。 如果給定的電子郵件地址不在「我的聯絡人」清單中,則忽略。

如果所有給定的電子郵件地址都無法從「我的聯絡人」清單中找到,將傳回例外情況 00015「抱歉,沒有找到記錄」。

綱要

SetContact 請求:

SetContact 範例請求:

<?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>SiteName</siteName>
      <webExID>UserID</webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.SetContact">
            <contactEmail>聯絡人電子郵件地址</contactEmail>
           <contact>
                <name>新增聯絡人姓名</name>
                <email>新增聯絡人電子郵件地址</email>
                <title>新標題</title>
                <company>新增公司</company>
                <notes>���記事</notes>
                <url>新增鏈結</url>
                <phones>
                    <phone>1,,408######,,,,</phone>
                    <mobilePhone>1,,408######,,,,</mobilePhone>
                    <fax>1,,408######,,,,</fax>
                </phones>
                <address>
                    <address1>新增地址 1</address1>
                    <address2>新增地址 2</address2>
                    <city>新增城市</city>
                    <state>新增州/省</state>
                    <zipCode>新增郵遞區號</zipCode>
                    <country>新增公司</country>
                </address>
                <language>新語言</language>
            </contact>
</bodyContent>
</body>
</serv:message>

SetContact 回應:

SetContact 範例回應

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="ep:setContactResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
    </serv:body>
</serv:message>

DelContacts 請求:

DelContacts 範例

<?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>SiteName</siteName>
      <webExID>UserID</webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.DelContacts">
        <contactEmail>contact1@qa.webex.com</contactEmail>
        <contactEmail>contact2@qa.webex.com</contactEmail>
</bodyContent>
</body>
</serv:message>

DelContacts 回應:

已成功從「我的聯絡人」清單中刪除兩個現有的聯絡人

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="ep:delContactsResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:contactID>31830997</ep:contactID>
            <ep:contactID>31831002</ep:contactID>
        </serv:bodyContent>
    </serv:body>
</serv:message>

如果給定的電子郵件地址不在「我的聯絡人」清單中

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>抱歉,找不到記錄</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

已知問題

XML API 11.0.0 SP11 更新

新 API LstTrainingPollResultsHistory

請求僅適用於 T32/XML API11.0.0。

LstTrainingPollResultsHistory API 最初在 URL API 中實作。 根據客戶要求,它現在在 XML API 中實作。

透過輸入 Training Center sessionKey 傳回清單輪詢結果。 可以透過 Training Center 課程所有者或網站管理員請求 API。


在訓練輪詢結果儲存在 Webex 資料庫中之前,必須先啟用一個網站選項:

受影響的 XML API:

LstTrainingPollResultsHistory

設計

輪詢結果的資料庫表格關係:

綱要

LstTrainingPollResultHistory 請求:

LstTrainingPollResultHistory 回應:

範例請求:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <!-- <returnAdditionalInfo>true</returnAdditionalInfo> -->
            <webExID>ut2</webExID>
            <password>xxxxxxx</password>
            <siteName>testsite1</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent
xsi:type="java:com.webex.service.binding.history.LstTrainingPollResultsHistory"
            xmlns:meet="http://www.webex.com/schemas/2002/06/service/history">
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
            </listControl>
            <confID>81722715648558691</confID>
        </bodyContent>
    </body>
</serv:message>

範例回應:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:history="http://www.webex.com/schemas/2002/06/service/history">
    <serv:header>
        <serv:response>
            <serv:result>成功&nbsp;</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="history:lstTrainingPollResultsHistoryResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <history:matchingRecords>
                <serv:total>2</serv:total>
                <serv:returned>2</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
            <history:sessionInfo>
                <history:sessionKey>81901776767288734</history:sessionKey>
                <history:confName>TC 民意調查測驗 20171220 1635</history:confName>
                <history:host>John Doe</history:host>
            </history:sessionInfo>
            <history:polls>
                <history:poll>
                    <history:pollDesc>測試</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>2017 年 12 月 20 日下午 04:54:48</history:startTime>
                    <history:endTime>2017 年 12 月 20 日下午 04:58:07</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>測驗問題 1(多選/單個答案)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>測驗答案 4</history:answerChoice>
                                <history:answerChoice>測驗答案 3</history:answerChoice>
                                <history:answerChoice correct="true">測驗答案 2</history:answerChoice>
                                <history:answerChoice>測驗答案 1</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>測驗答案 2</history:pollResponse>
                                    <history:isCorrect>true</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>測驗答案 1</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>未回答</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>測驗問題 2(多選/多個答案)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>測驗答案 D</history:answerChoice>
                                <history:answerChoice>測驗答案 C</history:answerChoice>
                                <history:answerChoice correct="true">測驗答案 B</history:answerChoice>
                                <history:answerChoice correct="true">測驗答案 A</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>測驗答案 B,測驗答案 A</history:pollResponse>
                                    <history:isCorrect>true</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>測驗答案 D,測驗答案 C,測驗答案 B,測驗答案 A</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>未回答</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>測驗問題 2(簡短答案)</history:questionDesc>
                            <history:questionType>3</history:questionType>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>ans1</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>ans2</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>未回答</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
                <history:poll>
                    <history:pollDesc>調查</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>2017 年 12 月 20 日下午 04:58:57</history:startTime>
                    <history:endTime>2017 年 12 月 20 日下午 05:02:39</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>問卷調查問題 1(多選/單個答案)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>問卷調查答案 3</history:answerChoice>
                                <history:answerChoice>問卷調查答案 2</history:answerChoice>
                                <history:answerChoice>問卷調查答案 1</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>問卷調查答案 3</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465762</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>問卷調查答案 2</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465767</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>未回答</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>問卷調查問題 2(多選/多個答案)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>問卷調查答案 D</history:answerChoice>
                                <history:answerChoice>問卷調查答案 C</history:answerChoice>
                                <history:answerChoice>問卷調查答案 B</history:answerChoice>
                                <history:answerChoice>問卷調查答案 A</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>問卷調查答案 D, 問卷調查答案 C</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465762</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>問卷調查答案 C, 問卷調查答案 B</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465767</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>未回答</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>問卷調查問題 3(簡短答案)</history:questionDesc>
                            <history:questionType>3</history:questionType>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>AAA</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465762</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>BBB</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465767</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>未回答</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
            </history:polls>
        </serv:bodyContent>
    </serv:body>
</serv:message>

如果找不到會議,或會議不屬於登入使用者,或登入使用者不是網站管理員,回應將有所不同。

範例回應:

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:history="http://www.webex.com/schemas/2002/06/service/history">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>抱歉,找不到記錄</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

已知問題

attendeeSendVideo 選項(在 API CreateTrainingSessionSetTrainingSessionGetTrainingSession 中的)

說明:

請求僅適用於 T32/XML API11.0.0。

由於排定 Training Center 課程時,可用的選項包括「傳送視訊」,XML API 現已新增 attendeeSendVideo 選項以建立、取得,以及設定 Training Center 課程的 API。

受影響的 XML API:

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

設計

選項已在資料庫表格 WbxMMConfParam/paramvalue 中儲存為 paramname = ‘optionSupportSendVideo’

綱要變更

CreateTrainingSession 請求:

SetTrainingSession 請求:

GetTrainingSession 回應:

已知問題

ConfName 大小限制變更為最多 128 個顯示字元

會議名稱字串 ConfName 目前限制為最多 128 個顯示字元。 此變更與 J2EE 首頁限制相符。 如果 API 請求中包含的 ConfName 為空或超過了 128 個顯示字元長度,會顯示下列錯誤訊息:

「060065 非法輸入的會議名稱。 會議名稱不能為空或超過最多 128 個顯示字元的長度限制。」

受影響的 XML API

ConfName

已知問題

在 API LstRecording 中例外狀況訊息已變更

查詢時間範圍超過 API LstRecording 的最大限制時,擲出的例外狀況訊息已變更。 依預設,查詢支援 4 週的錄製檔。 超過 4 週的請求會收到下列錯誤訊息:

「999999 超過最大查詢時間範圍 28 天」。

受影響的 XML API

LstRecording

已知問題

XML API 11.0.0 SP10 更新

XML API 11.0 SP10 發行版沒有包含綱要變更。