Denne artikel indeholder opdateringer og ændringer til XML API-månedlige udgivelser.

For yderligere oplysninger om XML API 40 og REST API 40, se Oversigt over Cisco WEBEX MEETINGS API-opdateringer (api 40).

For opdateringer til XML API 11 SP9 og tidligere skal du gå til Cisco DevNet.

XML API 39.11.0-opdateringer

Klik her for at downloade XML API 39,11-skemaet.

LstSummaryUser kan forespørge brugerkonti efter det seneste ændrede tidspunkt

Vi opgraderer LstSummaryUser API for at lade brugere forespørge på brugerkonti baseret på tidspunktet, hvor de sidst blev ændret. Tre nye elementer, modifiedDateStart, modifiedDateEnd ogseneste ændringstidspunkt, er blevet føjet til API'en.


Det maksimale tidsinterval for denne forespørgsel er 90 dage. Hvis du indtastede et tidsinterval, der er mere end 90 dage, vises en fejl: 999999 maksimum datointerval er 90 dage for ændring af dato forespørgsel.

Påvirkede API'er:

  • LstSummaryUser

LastSummaryUser- anmodnings eksempel:

<?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>webstedsadministrator-</webExID>
    <password>adgangskode</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 svar eksempel:

<?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>Succes,</serv:result>
            <serv:gsbStatus>primær</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>* * * hr * * *</use:webExId>
                <use:firstName>* * * hr * * *</use:firstName>
                <use:lastName>* * * Est * * *</use:lastName>
                <use:email>* * * Est * * * @qa. Webex.com-</use:email>
                <use:userRoleType>vært 06/19/2016 22:13:06 deaktiveret</use:userRoleType>
                <use:registrationDate></use:registrationDate>
                <use:active></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-opdateringer

Klik her for at downloade XML API 39,10-skemaet.

GetSessionInfo og GetUserCard returnerer en captcha kode, når anonym adgang bruges

Som sikkerhedsopdatering har vi forbedret GetSessionInfo -og GetUserCard- API'erne med captcha-kode svar beskyttelse. Hvis dine applikationer ringer til API'erne ved hjælp af anonym adgang, skal du forbedre din applikation for at understøtte CAPTCHA kode input.

Påvirkede API'er:

  • GetSessionInfo

  • GetUserCard

CAPTCHA sikkerheds-og svar opdateringer:

GetSessionInfo- svar uden captcha eksempel:

<?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>FEJL</serv:result>
            <serv:reason>tilsvarende møde ikke fundet</serv:reason>
            <serv:gsbStatus>primær</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

GetSessionInfo- svar med captcha eksempel:

<?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>Fejl</serv:result>
            <serv:reason>tilsvarende møde ikke fundet</serv:reason>
            <serv:gsbStatus>primær</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>

Hvis du modtager et CAPTCHA-svar og fortsætter med at ringe til API'EN, skal du inkludere CAPTCHAID og CAPTCHAWord i din API-anmodning:

<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 -svar til forkert CAPTCHAID og CAPTCHAWord eksempel:

<?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>Fejl</serv:result>
            <serv:reason>captcha-id og Word er ugyldige eller mangler</serv:reason>
            <serv:gsbStatus>primær</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 -support til returnering af URL-adresser til personlige lokaler

Vi har tilføjet et nyt svarelement, personalMeetingRoomURL, til LstSummaryUser API.

LstSummaryUser svar eksempel:

XML API 39.9.0-opdateringer

Klik her for at downloade XML API 39,9-skemaet.

Understøttelse af korte SIP URL-adresser til personlige mødelokaler (PMR)

Support til det korte SIP URL-format til PMRs påvirker GetSessionInfo, GetMeeting, GetUser ogGetMe API'er. Et nyt svarelement med navnet displayMeetingUrl blev føjet til GetUser -og GetMe -API'erne og findes allerede i GetSessionInfo og GetMeeting. displayMeetingUrl returnerer en brugers PMR URL-adresse.

Påvirkede API'er:

  • GetSessionInfo

  • GetMeeting

  • GetUser

  • GetMe

GetUser svar eksempel:

GetMe svar eksempel:

GetSessionInfo returnerer de nødvendige elementer til anonym adgang

Som et sikkerhedskrav kan kun nødvendige elementer returneres af GetSessionInfo til anonym adgang.

GetSessionInfo svar eksempel:

<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>offentlig</ep:listStatus>
        <ep:registration>falsk</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>03/29/2019 11:55:00</ep:startDate>
        <ep:duration>60</ep:duration>
        <ep:timeZone>GMT-07:00, Stillehavsområdet (San Francisco)</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>falsk</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>

Påvirkede API'er:

  • GetSessionInfo

Planlæg møder og begivenheder ændring af adfærd

Som standard er alle planlagte møder møder med aktiveret videoenhed. Men når du planlægger et møde, men vælger ingen eller andre til dit mødes lyd, vil mødet blive planlagt som et ikke-videoenhed-aktiveret Webex møde.

Påvirkede API'er:

  • Oprettelse af møde

  • SetMeeting

  • CreateEvent

  • SetEvent

XML API 39.8.0-opdateringer

Klik her for at downloade XML API 39,8-skemaet.

LsttrainingattendeeHistory returnerer nu mødedeltagere opmærksomhed

Et nyt svarelement, attentionToDurationPercentage, blev tilføjet til LsttrainingattendeeHistory API. LsttrainingattendeeHistory returnerer en møde deltagers opmærksomhed-detaljer. Elementet returneres i dette format:

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

Påvirkede API'er:

  • LsttrainingattendeeHistory

    • attentionToDurationPercentage

    • attentionToAttendancePercentage

LsttrainingattendeeHistory svar eksempel:

<history:endTime>04/17/2019 23:37:07</history:endTime>
<history:duration>6</history:duration>
    <history:attentionToDurationPercentage>100</history:AttentionToDurationPercentage>
    <history:attentionToAttendancePercentage>100</history:AttentionToAttendancePercentage>
<history:registered>n</history:registered>
<history:invited>n</history:invited>

GetSite returnerer nu licens tællinger

Nye svar elementer blev leveret til at returnere forskellige licens tællinger i GetSite API.

Påvirkede API'er:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

GetSiteFT -og SetSiteFT- redesign

GetSiteFT -og SetSiteFT- API'erne blev ændret for at tillade dynamisk funktions Skift.

Påvirkede API'er:

  • GetSiteFT

  • SetSiteFT

GetSite- anmodnings eksempel:

<?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>{Dette er adgangs token til maskinkonto}</accessToken>
        </securityContext>
    </header>
    <bodyContent xsi:type="java:com.webex.service.binding.site.GetSiteFT">
        <featureToggles>
            <name>SupportCrossLaunch</name>
            <name>RemoveCMRLicenseSA</name>
        </featureToggles>
    </bodyContent>
</body>
</serv:message>

GetSite svar eksempel:

<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>SUCCES</serv:result>
            <serv:gsbStatus>primært</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>falsk</ns1:value>
                </ns1:featureToggle>
                <ns1:featureToggle>
                    <ns1:name>RemoveCMRLicenseSA</ns1:name>
                    <ns1:value>falsk</ns1:value>
                </ns1:featureToggle>
            </ns1:featureToggles>
        </serv:bodyContent>
    </serv:body>
</serv:message>

SetSite- anmodnings eksempel:

<?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>{Dette er adgangs token til maskinkonto}</accessToken>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.site.SetSiteFT">
            <featureToggles>
                <featureToggle>
                    <name>SupportCrossLaunch</name>
                    <value>falsk</value>
                </featureToggle>
                <featureToggle>
                    <name>SupportPeopleInsight</name>
                    <value>True</value>
                </featureToggle>
            </featureToggles>
        </bodyContent>
    </body>
</serv:message>

SetSiteFT resonse eksempel:

<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>SUCCES</serv:result>
            <serv:gsbStatus>PRIMÆR</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>

Møde beskrivelsens længde nu begrænset til 2500 tegn

Følgende API'er har nu møde beskrivelses elementets indholdslængde begrænset til 2500 tegn:

Påvirkede API'er:

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

Dette er for at forhindre Cisco Webex i ikke kunne behandle anmodningen. Hvis møde beskrivelsen er længere end 2500 tegn, returneres en fejlmeddelelse.

XML API 39.5.0-opdateringer

Nyt element videoMeshInterclusters føjet til SetSite -og GetSite-skemaerne

Et nyt element, videoMeshInterclusters, blev tilføjet til SetSite- elementet. videoMeshInterclusters indeholder også tre underordnede elementer videoMeshHomeCluster1, videoMeshHomeCluster2 ogvideoMeshHomeCluster3.

Påvirkede API'er:

  • SetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

SetSite anmodnings opdateringer:

Opdateringer til GetSite- svar:

XML API 39.3.0-opdateringer

Kort SIP URL-adresse i XML API, ny element displayMeetingUrl

Klik her for at downloade XML API 39,3-skemaet.

Når du deltager i et Webex-møde, skal appen eller enheden i øjeblikket opgive websteds oplysninger, hvilket gør det vanskeligt at deltage i møder sommetider. Dette gælder især, når der ringes op fra en SIP-enhed, fordi brugeren skal indtaste meeting_number@sitename.webex.com.

For at gøre deltagelse i møder lettere, fjernede vi kravet om at indtaste webstedets navn fra Meeting SIP URI: meeting_number@webex.com. For at bevare kompatibiliteten fungerer det gamle format på sipURL, og det nye format tilføjes til det nye element displayMeetingUrl.

Påvirkede API'er:

  • GetMeeting

    • displayMeetingUrl

  • GetEvent

    • displayMeetingUrl

  • GetSessionInfo

    • displayMeetingUrl

GetMeeting svar eksempel:

    <meet:isCETMeeting>ægte</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>
</serv:bodyContent>

GetEvent svar eksempel:

    <event:hostType>1001001</event:hostType>
    <event:isCETMeeting>ægte</event:isCETMeeting>
    <event:sipURL>713847821@sqdemo.dmz.webex.com</event:sipURL>
    <event:displayMeetingUrl>713847821@dmz.webex.com</event:displayMeetingUrl>
</serv:bodyContent>

GetSessionInfo svar eksempel:

    <ep:isCETMeeting>ægte</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>
</serv:bodyContent>

E-mail eksempel:

Længde af beskrivelse nu begrænset til 1024 tegn

Følgende API'er har nu beskrivelses elementets indholdslængde begrænset til 1024 tegn:

Påvirkede API'er:

  • CreateTrainingSession

  • SetTrainingSession

  • CreateEvent

  • SetEvent

Denne ændring er at forhindre Cisco Webex i ikke kunne behandle anmodningen. Hvis beskrivelsen er længere end 1024 tegn, returneres en fejlmeddelelse: "060067 ulovlig indtastnings beskrivelse. Beskrivelsen må ikke overstige den maksimale display tegns længde 1024. "

Svar eksempel på beskrivelse længde på mere end 1024 tegn:

<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>FEJL</serv:result>
            <serv:reason> ugyldig beskrivelse af input. Beskrivelsen må ikke overstige den maksimale visnings tegns længde 1024 </serv:reason>
            <serv:gsbStatus>primær</serv:gsbStatus>
            <serv:exceptionID>060067</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

GetSessionInfo returnerer nu kun grundlæggende oplysninger om personlige lokaler, når der er en anonym bruger, der bruger API

For at sikre større sikkerhed reducerer vi mængden af oplysninger, der returneres af GetSessionInfo , når der er en anonym mødedeltager bruger, der bruger API'en. I denne opdatering vil vi reducere følgende elementer i API-svaret:

Påvirkede API'er:

  • GetSessionInfo

    • <ep:accessControl>

  • <ep:sessionPassword>

    • <ep:telephony>

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

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

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

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

Svar sammenligninger:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:isLocked>falsk ikke angivet</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>falsk falsk falsk false</ep:registration>
        <ep:passwordReq></ep:passwordReq>
        <ep:isEnforceAudioPassword></ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin></ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Thomas test s personlige lokale</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType>MeetingCenter</ep:serviceType>
        <ep:isRecurring>falsk</ep:isRecurring>
        <ep:agendaFormat>tekst</ep:agendaFormat>
        <ep:descriptionFormat>tekst</ep:descriptionFormat>
        <ep:isException>falsk</ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException>falsk</ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>tilbagekald</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 * [adgangskode] #,,, [AttendeeID] # | SilentDialInSequence: [AccessNumber],,, * 01 * [adgangskode] # [AttendeeID] # * 01 * | AutoLGDialInSequence: [AccessNumber],, * 00 * [adgangskode] #,,, [ProfileID] #,,, [PIN] # | SilentLGDialInSequence: [AccessNumber],,, * 01 * [adgangskode] # [ProfileID] # [PIN] # * 01 * | AutoLGPWDialInSequence: [AccessNumber],, * 00 * [adgangskode] #,,, [ProfileID] #,,, [PIN] #,,, [adgangskode] # | SilentLGPWDialInSequence: [AccessNumber],,, * 01 * [adgangskode] # [ProfileID] # [PIN] # [adgangskode] # * 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 false indgående</serv:tollFree>    <!--Removed-->
                <serv:default></serv:default>  <!--Removed-->
            </serv:globalNum> <!--Removed-->
        </ep:callInNum>   <!--Removed-->
        <ep:labels>   <!--Removed-->
            <ep:tollFreeCallInLabel>opkald-gratisnummer (USA/Canada) falsk falsk falsk</ep:tollFreeCallInLabel>   <!--Removed-->
            <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->
        </ep:labels>  <!--Removed-->
        <ep:isMPAudio></ep:isMPAudio>  <!--Removed-->
        <ep:voip></ep:voip> <!--Removed-->
        <ep:enableTSP></ep:enableTSP>  <!--Removed-->
    </ep:telephony>   <!--Removed-->
    <ep:host>
        <ep:firstName>Thomas</ep:firstName>
        <ep:lastName>test</ep:lastName>
        <ep:email>simon0@qa.webex.com</ep:email>
        <ep:webExId>Simon</ep:webExId>
        <ep:allowAnyoneHostMeeting>falsk</ep:allowAnyoneHostMeeting>
    </ep:host>
    <ep:schedule>
        <ep:startDate>12/31/2068 13:00:00</ep:startDate>
        <ep:duration>720</ep:duration>
        <ep:timeZone>GMT-08:00, Pacific (San Francisco)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
        <ep:openTimeInSec>0</ep:openTimeInSec>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>falsk</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly>falsk</ep:isAudioOnly>
    <ep:telePresence>falsk</ep:telePresence>
    <ep:isAlternateHost>falsk</ep:isAlternateHost>  <!--Removed-->
    <ep:isCreator>sand</ep:isCreator>   <!--Removed-->
    <ep:hostKey>954462</ep:hostKey> <!--Removed-->
    <ep:supportE2E></ep:supportE2E>    <!--Removed-->
    <ep:isAllowJBH></ep:isAllowJBH>
    <ep:isCETMeeting></ep:isCETMeeting>
    <ep:isPersonalMeetingRoom></ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance></ep:isNextUpcomingInstance>
    <ep:meetingLink></ep:meetingLink>
    <ep:sipURL></ep:sipURL>
    <ep:displayMeetingUrl></ep:displayMeetingUrl>
    <ep:isAutoRecord></ep:isAutoRecord>
</serv:bodyContent>

XML API 39.2.0-opdateringer

Nyt element lastLoginTime returneret i LstSummaryUser- svar

Et nyt svarelement, lastLoginTime, blev tilføjet til LstSummaryUser API. lastLoginTime returnerer den sidste login-tid for hver bruger. Elementet returneres i dette format:

<lastLoginTime>04/12/2018 22:40:01 * *</lastLoginTime>

Påvirkede API'er:

  • LstSummaryUser

    • lastLoginTime

LstSummaryUser svar eksempel:

<?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>Succes</serv:result>
            <serv:gsbStatus>primær</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>vært</use:userRoleType>
                <use:registrationDate>12/11/2018 14:41:27</use:registrationDate>
                <use:active>deaktiveret</use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:lastLoginTime>04/12/2018 22: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-opdateringer

Klik her for at downloade XML API-39.1.0s skemaet.

Nyt element apiVer føjet til GetAPIVersion API

Et nyt svarelement, apiVer, blev tilføjet til GetAPIVersion API. Med denne opdatering ændres navngivningskonventionen for XML API-versioner, så de passer til et samlet versionsnummer med andre Cisco Webex-produkt områder. apiVer returnerer de nye versionsoplysninger, såsom 39.1.0 for januar 2019-opdateringen.

Påvirkede API'er:

  • GetAPIVersion

    • apiVer

Element apiVersion vil blive udfaset den 1. maj 2019, og element udgivelsen vil blive tildelt en ny XML API-værdi d. 1. maj 2019.

GetAPIVersion svar eksempel:

<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>SUCCES</serv:result>
            <serv:gsbStatus>primær</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 v 11.0.0</ep:apiVersion>
            <ep:release>SP22</ep:release>
            <ep:apiVer>39.1.0</ep:apiVer>
        </serv:bodyContent>
    </serv:body>
</serv:message>

HQ og HD-parametre fjernet fra XML API

HQ-og HD-Videoegenskaber fastlægges nu på webstedsniveau i stedet for at blive bestemt på brugerniveau. De to valgmuligheder for disse parametre ignoreres, når der sendes anmodninger fra følgende API'er:

  • Oprettelse af møde

  • SetMeeting

  • CreateTrainingSession

  • SetTrainingSession

GetMeeting -og GetTrainingSession- API'erne returnerer stadig de to valgmuligheder (besluttet af webstedsniveau og brugerniveau) for at undgå at bryde eksisterende kode.

Nyt element uploadLogFileUrl tilføjet til webstedets metadata returneret til desktop-appen

Et nyt element uploadLogFileUrl blev tilføjet til svaret returneret til desktop-appen, når det kalder getSite -API'en i XML API-serveren. Desktop-appen kan overføre logfilen til uploadLogFileUrl.

Påvirkede API'er:

  • GetSite

    • uploadLogFileUrl

GetSite svar eksempel:

<?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>SUCCESS</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>PRO</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>France</ns1:region>
                    <ns1:currency>French Francs</ns1:currency>
                    <ns1:timeZoneID>4</ns1:timeZoneID>
                    <ns1:timeZone>GMT-08:00, Pacific (San Jose)</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>FRENCH</ns1:pageLanguage>
                    <ns1:activateStatus>true</ns1:activateStatus>
                    <ns1:webPageType>J2EE</ns1:webPageType>
                    <ns1:iCalendar>true</ns1:iCalendar>
                    <ns1:myWebExDefaultPage>My Meetings</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>Personal Conference No.</ns1:serviceName>
                    <ns1:participantAccessCodeLabel>Attendee access code</ns1:participantAccessCodeLabel>
                    <ns1:subscriberAccessCodeLabel>Host access code</ns1:subscriberAccessCodeLabel>
                    <ns1:attendeeIDLabel>Attendee 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>QA</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>Call-in User</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>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:primaryLargeServer>
                        <ns1:backup1LargeServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup1LargeServer>
                        <ns1:backup2LargeServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Backup call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Backup call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup2LargeServer>
                        <ns1:primarySmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:primarySmallServer>
                        <ns1:backup1SmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup1SmallServer>
                        <ns1:backup2SmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Backup call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Backup call-in toll-free number (US/Canada)</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>Call-in number</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Call-in toll-free number</ns1:label>
                            </ns1:mpAudio>
                        </ns1:primaryLarge>
                        <ns1:backup1Large>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Call-in number</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Call-in toll-free number</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup1Large>
                        <ns1:backup2Large>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Call-in number</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Call-in toll-free number</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>Other teleconference service</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&amp;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>Welcome</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>Site Administration</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>Support</ns1:name>
                        <ns1:target>NEW</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:name>Training</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>password</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>password</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>password</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-opdateringer

Begrænsning af filstørrelse for UploadPMRImage

Når du overfører avatarer ved hjælp af API -UploadPMRImage, begrænser en ny begrænsning filstørrelsen til 5 MB. Forsøg på at overføre filer større end dette vil nu modtage en fejlmeddelelse: "010100 størrelse på det billede, der overføres, er for stor. Prøv et billede, der er mindre end 5 MB i størrelse."

XML API 11.0.0 SP21-opdateringer

Klik her for at downloade XML API 11,0 SP21-skemaet.

Automatisk optagelse af nyt element føjet til oprettelse af møde, SetMeeting, GetMeetingog LstMeeting

Et nyt element, navngivet post blev tilføjet til oprettelse af møde, SetMeeting, GetMeetingog LstMeeting API'er. automatisk optagelse tillader brugere automatisk at optage Webex møder direkte fra møde planlægningsprogrammet. Dette giver et detaljeret møde niveau, hvor den tidligere metode til automatisk optagelse af møder kun kunne tilgås globalt på webstedsniveau.


Elementet for automatisk optagelse gælder kun for Webex Meetings. Den gælder ikke for Webex Events eller Webex Training.

Påvirkede API'er:

  • Oprettelse af møde

    • automatisk optagelse

  • SetMeeting

    • automatisk optagelse

  • GetMeeting

    • automatisk optagelse

  • LstMeeting

    • automatisk optagelse

Oprettelse af møde- opdateringer:

indstilling for automatisk optagelse

Adfærd, når automatisk optagelse af alle sessioner vha. netværksbaseret optagelse er deaktiveret på Webstedsadministration

SANDT

Begynd automatisk at optage, når mødet starter

Falsk (standard) eller intet element

Starter ikke automatisk optagelsen, når mødet starter


Hvis automatisk optagelse af alle sessioner ved hjælp af netværksbaseret optagelse er aktiveret, ignoreres elementet, og optagelsen starter automatisk, når mødet starter.

SetMeeting- opdateringer:

indstilling for automatisk optagelse

Adfærd, når automatisk optagelse af alle sessioner vha. netværksbaseret optagelse er deaktiveret på Webstedsadministration

SANDT

Begynd automatisk at optage, når mødet starter

Falsk (standard) eller intet element

Starter ikke automatisk optagelsen, når mødet starter


Hvis automatisk optagelse af alle sessioner ved hjælp af netværksbaseret optagelse er aktiveret, ignoreres elementet, og optagelsen starter automatisk, når mødet starter.

GetMeeting- opdateringer:

indstilling for automatisk optagelse

Adfærd, når automatisk optagelse af alle sessioner vha. netværksbaseret optagelse er deaktiveret på Webstedsadministration

SANDT

Begynd automatisk at optage, når mødet starter

Falsk

Starter ikke automatisk optagelsen, når mødet starter


Hvis automatisk optagelse af alle sessioner ved hjælp af netværksbaseret optagelse er aktiveret, ignoreres elementet, og optagelsen starter automatisk, når mødet starter.

GetMeeting svar eksempel:

LstMeeting- opdateringer:

indstilling for automatisk optagelse

Adfærd, når automatisk optagelse af alle sessioner vha. netværksbaseret optagelse er deaktiveret på Webstedsadministration

SANDT

Begynd automatisk at optage, når mødet starter

Falsk

Starter ikke automatisk optagelsen, når mødet starter


Hvis automatisk optagelse af alle sessioner ved hjælp af netværksbaseret optagelse er aktiveret, ignoreres elementet, og optagelsen starter automatisk, når mødet starter.

LstMeeting svar eksempel:

Nyt element isAutoRecord føjet til GetSessionInfo API

Sammen med ændringerne foretaget af ovenstående API'er, blev et nyt element, isAutoRecord, føjet til GetSessionInfo API. Dette element kan bruges til at angive, om optagelsen automatisk starter, når et møde starter.

Påvirkede API'er:

  • GetSessionInfo

    • isAutoRecord

GetSessionInfo- opdateringer:

isAutoRecord- indstilling

Adfærd, når automatisk optagelse af alle sessioner vha. netværksbaseret optagelse er deaktiveret på Webstedsadministration

SANDT

Begynd automatisk at optage, når mødet starter

Falsk

Starter ikke automatisk optagelsen, når mødet starter


Hvis automatisk optagelse af alle sessioner ved hjælp af netværksbaseret optagelse er aktiveret, ignoreres elementet, og optagelsen starter automatisk, når mødet starter.

GetSessionInfo svar eksempel:

XML API 11.0.0 SP20-opdateringer

Klik her for at downloade XML API 11,0 SP20-skemaet.

Nyt element returnShareToMeRecording føjet til LstRecording API-anmodningen


Denne ændring blev tidligere annonceret i XML API 11,0 SP17, men anvendes til denne opdatering.

Et nyt element, returnShareToMeRecording, blev tilføjet til LstRecording API. returnShareToMeRecording er en boolesk værdi i anmodningen om LstRecording.

Dette nye element blev tilføjet til support til at finde mødedeltager-eller invitations optagelser. returnShareToMeRecording er et flag, der lader LstRecording- API'en vide, at det skal returnere mødedeltager eller inviterede optagelser.

Når returnShareToMeRecording er indstillet til True, returnerer LstRecording optagelses brugeren som ejer og returnerer også optagelses brugeren som en mødedeltager eller besøgende deles af ejeren.


Hvis automatisk deling og manuelle delings flag begge er deaktiveret, vil LstRecording kun returnere brugeren som ejer af optagelserne.

Når returnShareToMeRecording er indstillet til False, eller dette element ikke er inkluderet i anmodningen, vil LstRecording følge samme logik som før: den returnerer optagelses brugeren som ejer.

Påvirkede API'er:

  • LstRecording

    • returnShareToMeRecording

LstRecording- opdateringer:

Element shareToMe føjet til LstRecording API-svar


Denne ændring blev tidligere annonceret i XML API 11,0 SP17, men anvendes til denne opdatering.

Et nyt element, shareToMe, blev tilføjet til LstRecording API. shareToMe er en boolesk værdi i svaret for LstRecording.

Dette nye element blev tilføjet til support til at finde mødedeltager-eller invitations optagelser. shareToMe er et flag, der definerer, om brugeren er ejer af eller en mødedeltager for aktuel optagelse.

Når shareToMe er True, er brugeren ikke ejeren af den aktuelle optagelse. Brugeren kan være en mødedeltager, eller optagelsen deles af ejeren.

Når shareToMe er falsk, eller dette element ikke er i svaret, vil LstRecording følge samme logik som før: brugeren er ejeren af den aktuelle optagelse.

Påvirkede API'er:

  • LstRecording

    • shareToMe

LstRecording- opdateringer:

returnShareToMeRecording -og shareToMe- anmodnings eksempler:

<bodyContent xsi:type=”java.com.webex.service.binding..ep.LstRecording”>
<hostWebExID>auto243</hostWebExID>
<createTimeScope>
<createTimeStart>08/15/2018 8:0:0</createTimeStart>
<createTimeEnd>09/05/2018 7:59:59</createTimeEnd>
<timeZoneID>20</timeZoneID>
</createTimeScope>
<serviceTypes>
<serviceType>MeetingCenter</serviceType>
<serviceType>EventCenter</serviceType>
<serviceType>TrainingCenter</serviceType>
</serviceTypes>
<returnShareToMeRecording>True</returnShareToMeRecording>
</bodyContent>

returnShareToMeRecording og ShareToMe svar eksempler:

Nye elementer føjet til GetEvent API

Der blev tilføjet fire nye elementer til GetEvent API:

  • isCETMeeting: en boolesk værdi på true/false, der angiver, om Webex begivenheden understøtter Webex-video platform 2 (CMR 4,0)

  • sipURL: URL-adressen, der bruges til at deltage i Webex videomøde fra et videokonference system eller-applikation

  • standaloneDialingIPAddress: den IP-adresse, der kan bruges til at ringe op til Webex-videomøde fra et videokonference system eller-applikation

  • panelistNumericPassword: adgangskoden til at deltage i Webex-videomøde fra et videokonference system eller-applikation

Hvis webstedet understøtter Webex video, har værten Webex Events video privilegier, og begivenheden understøtter Webex video platform 2 (CMR 4,0), GetEvent returnerer disse elementer. Ellers returnerer GetEvent ikke dem.

Påvirkede API'er:

  • GetEvent

    • isCETMeeting

    • sipURL

    • standaloneDialingIPAddress

    • panelistNumericPassword

Nyt element panelistNumericPassword føjet til GetSessionInfo API

GetSessionInfo har et nyt element, panelistNumericPassword, som indeholder adgangskoden til deltagelse i Webex-videomøde fra et videokonference system eller-applikation.

Hvis webstedet understøtter Webex video, har værten Webex Events video privilegier, og begivenheden understøtter Webex video platform 2 (CMR 4,0), GetSessionInfo returnerer disse fire elementer:

  • isCETMeeting: en boolesk værdi på true/false, der angiver, om Webex begivenheden understøtter Webex-video platform 2 (CMR 4,0)

  • sipURL: URL-adressen, der bruges til at deltage i Webex videomøde fra et videokonference system eller-applikation

  • standaloneDialingIPAddress: den IP-adresse, der kan bruges til at ringe op til Webex-videomøde fra et videokonference system eller-applikation

  • panelistNumericPassword: adgangskoden til at deltage i Webex-videomøde fra et videokonference system eller-applikation


For Webex Meetings fandtes disse elementer allerede i GetSessionInfo:

  • isCETMeeting

  • sipURL

  • standaloneDialingIPAddress

Påvirkede API'er:

  • GetSessionInfo

    • panelistNumericPassword

Skemaændringer foretaget til GetEvent og GetSessionInfo

GetEvent- opdateringer:

GetSessionInfo- opdateringer:

XML API 11.0.0 SP18-opdateringer

Klik her for at downloade XML API 11,0 SP18-skemaet.

Nyt element EnableCloudTelepresence føjet til getSite API

Et nyt element, EnableCloudTelepresence blev føjet til getSite API.

Når valgmuligheden EnableCETForAllUsers er aktiveret, skal du Webex kontrollere, om brugeren understøtter Webex video (CMR). Det returnerer nu også et nyt element EnableCloudTelepresence i getSite API.

Påvirkede API'er:

  • getSite

  • EnableCloudTelepresence

getSite- eksempel svar:

XML API 11.0.0 SP17-opdateringer

Nyt element returnShareToMeRecording føjet til LstRecording API-anmodningen

Et nyt element, returnShareToMeRecording, blev tilføjet til LstRecording API. returnShareToMeRecording er en boolesk værdi i anmodningen om LstRecording.

Dette nye element blev tilføjet for at understøtte at trække mødedeltagere eller inviterede optagelser. returnShareToMeRecording er et flag, der lader LstRecording- API'en vide, at det skal returnere mødedeltager eller inviterede optagelser.

Når returnShareToMeRecording er indstillet til True, returnerer LstRecording optagelserne bruger som ejer og returnerer også optagelses brugeren som en mødedeltager eller besøgende deles af ejeren.


Hvis automatisk deling og manuelle delings flag er deaktiveret, returnerer LstRecording kun brugeren som ejer af optagelserne.

Når returnShareToMeRecording er indstillet til False, eller dette element ikke er inkluderet i anmodningen, vil LstRecording følge samme logik som før: den returnerer optagelses brugeren som ejer.

Påvirkede API'er:

  • LstRecording

  • returnShareToMeRecording

LstRecording- opdateringer:

Nyt element shareToMe føjet til LstRecording API-svar

Et nyt element, shareToMe, blev tilføjet til LstRecording API. shareToMe er en boolesk værdi i svaret for LstRecording.

Dette nye element blev tilføjet for at understøtte at trække mødedeltagere eller inviterede optagelser. shareToMe er et flag, der definerer, om brugeren er ejer, eller mødedeltageren eller inviterede til den aktuelle optagelse.

Når shareToMe er sand, er brugeren ikke ejeren af den aktuelle optagelse. Brugeren kan være mødedeltager eller inviterende, eller optagelsen deles af ejeren.

Når shareToMe er falsk, eller dette element ikke er i svaret, vil LstRecording følge samme logik som før: brugeren er ejeren af den aktuelle optagelse.

Påvirkede API'er:

  • LstRecording

  • shareToMe

LstRecording- opdateringer:

Nye elementer for mødedeltager kapacitet tilføjet til API getSite- svar

Der blev tilføjet fire nye elementer til getSite API for at angive mødedeltager kapaciteten for følgende Webex-tjenester:

attendeeCapacityForMC -Webex Meetings

attendeeCapacityForEC – Webex events

attendeeCapacityForTC – Webex Training

attendeeCapacityForSC – Webex support

Disse returnerede værdier angiver det maksimale antal mødedeltagere, som mødet, begivenheden eller sessionen kan have. De er børn i CISiteLicenseInfo- elementet i svaret.

Påvirkede API'er:

  • getSite

  • attendeeCapacityForMC

  • attendeeCapacityForEC

  • attendeeCapacityForTC

  • attendeeCapacityForSC

getSite svar eksempel:

<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>SUCCES</serv:result>
            <serv:gsbStatus>primært</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>falsk</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>falsk</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC>falsk</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>falsk</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>falsk</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-opdateringer

Ny API hostStreamURL føjet til lstRecordingResponse

Element hostStreamURL blev føjet til LstRecording- svaret som en del af optagelses oplysningerne. hostStreamURL returnerer en URL-adresse, som værten kan bruge til at se optagelsen uden først at logge ind. Denne URL-adresse er gyldig i 30 minutter, efter den genereres.

Påvirkede API'er:

  • hostStreamURL

hostStreamURL svar eksempel:

<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 bruger ny WebDB-model til at returnere data

Efter kunde anmodning henter API GetSite nu mere nøjagtig værts licens, brugs rapporteringsdata og andre data ved hjælp af den nye WebDB-model for CI-websteder.

Påvirkede API'er:

  • GetSite

GetSite svar eksempel:

<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>SUCCES</serv:result>
            <serv:gsbStatus>primært</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>falsk</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>falsk</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC>falsk</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>falsk</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>falsk</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

GetSite svar eksempel for ee-websteder:

<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>SUCCES</serv:result>
            <serv:gsbStatus>primært</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>sand</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>99</ns1:accountNumberUsedForCMRHost>
                    <ns1:accountNumberLimitForEEHost>999999</ns1:accountNumberLimitForEEHost>
                    <ns1:allowOverageForEEHost>falsk</ns1:allowOverageForEEHost>
                    <ns1:accountNumberUsedForEEHost>368</ns1:accountNumberUsedForEEHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

XML API 11.0.0 SP15-opdateringer

Returner Webex Meetings mødelink vha. GetSessionsInfo API

Skemaet til GetSessionInfo API har en ny returværdi, meetingLink. Du kan bruge et mødelink til at starte et Webex-møde som en vært eller ved at deltage i et Webex møde som en mødedeltager.

Påvirkede API'er:

  • GetSessionInfo

  • meetingLink

GetSessionInfo svar eksempel:

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

Ny betingelse for forespørgsler af RecordingIDLstRecording API

Du kan nu bruge LstRecording til at forespørge på optagelser ved hjælp af recordingID. Der findes to typer optagelses-id'er:

  • Optagelses-id'er for Webex Meetings, Webex Events og Webex Training

  • NBR optagelses-id'er til diverse optagelser

Hvis der er et servicetype -element i XML-anmodningen , returnerer LstRecording kun en tjeneste optagelse (kun Webex Meetings, Webex events og Webex Training).

Hvis der ikke er noget servicetype -element i XML-anmodningen, returnerer LstRecording kun en NBR-optagelse.

Påvirkede API'er:

  • LstRecording

  • Optagelses-id

LstRecording svar eksempler:

Anmod om et eksempel på en tjeneste optagelses-ID:

<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>

Anmodnings eksempel for et NBR optagelses-ID:

<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-opdateringer

Foreløbige rapport over brugs oversigter for Meeting Center

To nye API'er blev tilføjet for Meeting Center foreløbige rapporter, LstmeetingusagePreliminaryHistory og LstmeetingattendeePreliminaryHistory. Disse vil have den samme adfærd som LsteventsessionPreliminaryHistory og LsteventattendeePreliminaryHistory i den endelige rapport.

Påvirkede API'er:

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

LstmeetingusagePreliminaryHistory- anmodnings eksempel:

<?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>4/23/2018 00:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>4/24/2018 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>og</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 svar eksempel:

<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>Succes med</serv:result>
            <serv:gsbStatus>primær</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>04/23/2018 19:16:34</history:openTime>
                <history:timeZoneID>4</history:timeZoneID>
                <history:meetingType>Pro</history:meetingType>
                <history:timeZoneWithDST>San Francisco (Pacific sommertid, 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- anmodnings eksempel:

<?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>4/23/2018 00:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>4/24/2018 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>og</listMethod>
            </listControl>
            <order>
                <orderBy>starttidspunkt</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

LstmeetingattendeePreliminaryHistory svar eksempel:

<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>Succes</serv:result>
            <serv:gsbStatus>primært</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>1222654-3210,,,,</history:phoneNumber>
                <history:address1>1 enhver gade</history:address1>
                <history:address2>XYZ</history:address2>
                <history:city>SanJose</history:city>
                <history:state>ca. en</history:state>
                <history:country></history:country>
                <history:zipCode>95111</history:zipCode>
                <history:name>bruger test2</history:name>
                <history:email>ut2@qa.webex.com</history:email>
                <history:joinTime>04/23/2018 19:13:06</history:joinTime>
                <history:participantType>mødedeltager</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>04/23/2018 19:14:10</history:joinTime>
                <history:participantType>mødedeltager</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name>test vært</history:name>
                <history:email>testuser@webex.com</history:email>
                <history:joinTime>04/23/2018 19:12:42</history:joinTime>
                <history:participantType>mødedeltager</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>

Tilbage vende SIP URL-adresse og Skype URL-adresse fra GLA GetsessionInfo API

To nye elementer, <sipURL> og <skypeURL>, blev tilføjet til svaret, når GLA- GetSessionInfo API kaldes . Disse elementer er basis elementer, der kan returneres til anonym adgang.

  • <sipURL> kan bruges til at deltage i møder fra en TelePresence eller en anden Cisco-videoenhed. På denne måde skal kun møder, der bruger Cisco-video platformversion 1,0 eller 2,0, GetSessionInfo returnere <sipURL> elementet.

  • <skypeURL> kan bruges til at deltage i møder fra en Microsoft Skype-app uden begrænsninger eller betingelser, så den kan returneres for hvert opkald.

Påvirkede API'er:

  • GetSessionInfo

Svar eksempel:

Returnerer SIP URL-adresse og møde link fra GetMeeting API

Tre nye elementer, <isCETMeeting>, <meetingLink>, og <sipURL>, blev tilføjet til svaret, når GetMeeting-API'en ringes op .

  • <isCETMeeting> returnerer, om mødet bruger en Cisco-video platform (understøtter TelePresence og video).

  • <meetingLink> kan bruges til at oprette forbindelse til møder.

  • <sipURL> kan bruges til at deltage i møder fra en TelePresence eller en anden Cisco-videoenhed. På denne måde skal kun møder, der bruger Cisco-video platformversion 1,0 eller 2,0, GetMeeting returnere elementet.

Påvirkede API'er:

  • GetMeeting

GetMeeting svar eksempel:

XML API 11.0.0 SP13-opdateringer

Meddelelse om forældelse af <siteID> elementet i overordnet <securityContext>

Cisco planlægger at forælde <siteID> elementet i det overordnede <securityContext> element og erstatter det med <siteName>. På grund af et stort antal <siteID> elementer, der ofte ændres under websteds overflytninger, pålægges virksomheder høje vedligeholdelsesomkostninger for at fortsætte med at bruge dette element. Dette er en forhåndsmeddelelse to år i forvejen.

  • For eksisterende Webex-kunder vil effekten træde i kraft d. 1. maj 2020.

  • Nye kunder skal bruge elementet fra d. 1. maj 2018.<siteName>

  • Kunder, der foretager integrering med CI, Spark eller Atlas-systemet, skal bruge elementet fra d. 1. maj 2018.<siteName>

Påvirkede API'er:

  • <siteName>

  • <securityContext>

Data validering af <tollCallInData> og- <tollFreeCallInData> elementerne

Fra og med den 1. juni 2018 <tollCallInData> vil både og <tollFreeCallInData> API'erne blive data valideret. Dette påvirker <CreateUser> og <SetUser> API'erne.

Websteder, der bruger ikke-gyldige strenge eller forkert formaterede strenge i deres opkalds data, skal rette strengene, for at disse elementer kan overføre datavalidering.

Nedenfor er eksempler på CreateUser og SetUser, tollCallInData og tollFreeCallInData i det korrekte format:

<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>falsk</createOnBridge>
        <defaultFlag>falsk</defaultFlag>
    </tspAccount>
</tspAccount> ...

XML API 11.0.0 SP12-opdateringer

To nye API'er SetContact og DelContacts

XML API-skemaet havde tidligere kun de to API'er CreateContacts og LstContacts, som ikke leverede en komplet administration af brugerkontakter. For at opnå bedre funktionalitet til at administrere bruger kontakt ved hjælp af XML API har vi tilføjet disse to nye API'er, SetContact og DelContacts.

API

Bemærkninger

SetContact

Ring til dette API for at modificere kontaktoplysninger, såsom e-mail, navn, titel og sprog.

Undtagelser:

  • Hvis kontakten ikke findes af contactEmail -elementet, returneres undtagelsen 140004 "kontakt ikke fundet"

  • Hvis Webex-webstedet ikke understøtter et bestemt sprog, returneres undtagelsen 030060 "ikke et gyldigt sprog"

  • Hvis den nye e-mailadresse, som brugeren ønsker at ændre til, er en dublet med en anden kontakt på listen mine kontakter, returneres undtagelsen 140001 "e-mailen med en anden kontakt"

DelContacts

Ring til denne API for at slette en eller flere kontakter fra listen mine kontakter baseret på bestemte e-mails.

contactID returneres, hvis den angivne e-mail kan findes fra listen over mine kontakter og ignorerer den angivne e-mail, hvis den ikke er på listen over mine kontakter .

Hvis alle angivne e-mails ikke findes på listen mine kontakter , returneres undtagelsen 00015 (beklager, ingen optagelse fundet).

Påvirkede API'er:

  • SetContact

  • DelContacts

SetContact- anmodnings eksempel:

<?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>Bruger-id</webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.SetContact">
            <contactEmail>Kontakt E-mail adresse</contactEmail>
           <contact>
                <name>nyt kontaktnavn</name>
                <email>ny kontakt-e-mailadresse</email>
                <title>Ny titel</title>
                <company>Nye virksomhedens</company>
                <notes>nye noter</notes>
                <url>nyt link</url>
                <phones>
                    <phone>1,, 1,4 # # # # # #,,,, 1,,,,,,,,,,,, * # # # # #</phone>
                    <mobilePhone>#,,,,</mobilePhone>
                    <fax>1,, og 408 # # # # # #,,,,</fax>
                </phones>
                <address>
                    <address1>Ny adresse 1</address1>
                    <address2>ny adresse 2</address2>
                    <city>ny by</city>
                    <state>nyt land</state>
                    <zipCode>ny ZipCode</zipCode>
                    <country>ny virksomhed</country>
                </address>
                <language>Nyt sprog</language>
            </contact>
</bodyContent>
</body>
</serv:message>

SetContact svar eksempel:

<?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>SUCCES</serv:result>
            <serv:gsbStatus>primær</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- anmodnings eksempel:

<?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>Bruger-id</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 svar eksempler:


I dette eksempel slettes to eksisterende kontakter fra listen mine kontakter.

<?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>SUCCES</serv:result>
            <serv:gsbStatus>primær</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>


I dette eksempel er e-mailene ikke listen over mine kontakter.

<?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>FEJL</serv:result>
            <serv:reason>beklager, ingen optagelse fundet</serv:reason>
            <serv:gsbStatus>primær</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-opdateringer

Ny API LstTrainingPollResultsHistory

LstTrainingPollResultsHistory API blev oprindeligt implementeret i URL-adressen API. Efter kunde anmodning er det nu implementeret i XML API.

Resultaterne af liste over meningsmålinger returneres ved at indtaste en Training Center sessionKey. API'EN kan anmodes af enten ejeren af Training Center session eller en webstedsadministrator.


Indstillingen for forbedret TC-menings måling skal være aktiveret, før undervisnings undersøgelsesresultater gemmes i Webex-databasen:

Påvirkede API'er:

  • LstTrainingPollResultsHistory

LstTrainingPollResultHistory- anmodnings eksempel:

<?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>


Anmodningen er kun for T32/XML API-11.0.0.

LstTrainingPollResultHistory svar eksempel:

<? 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>SUCCES</serv:result>
            <serv:gsbStatus>PRIMÆR</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 meningsmåling test 20171220 1635</history:confName>
                <history:host>John Doe</history:host>
            </history:sessionInfo>
            <history:polls>
                <history:poll>
                    <history:pollDesc>Test</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>20/12/2017 16:54:48</history:startTime>
                    <history:endTime>20/12/2017 16:58:07</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>testspørgsmål 1 (multi-choice/enkelt svar)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test svar 4</history:answerChoice>
                                <history:answerChoice>test svar 3</history:answerChoice>
                                <history:answerChoice correct="true">test svar 2</history:answerChoice>
                                <history:answerChoice>test svar 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>test svar 2</history:pollResponse>
                                    <history:isCorrect>sand</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>test svar 1</history:pollResponse>
                                    <history:isCorrect>falsk</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>Intet svar</history:pollResponse>
                                    <history:isCorrect>falsk</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>testspørgsmål 2 (multi-choiec.multi-svar)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test svar D</history:answerChoice>
                                <history:answerChoice>test svar C</history:answerChoice>
                                <history:answerChoice correct="true">test svar B</history:answerChoice>
                                <history:answerChoice correct="true">test svar med et</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>test svar B, teste svar A</history:pollResponse>
                                    <history:isCorrect>sand</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>test svar D, teste svar C, teste svar B, teste svar A</history:pollResponse>
                                    <history:isCorrect>falsk</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>Intet svar</history:pollResponse>
                                    <history:isCorrect>falsk</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>testspørgsmål 2 (kort svar)</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>Intet svar</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
                <history:poll>
                    <history:pollDesc>Undersøgelse</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>20/12/2017 16:58:57</history:startTime>
                    <history:endTime>20/12/2017 17:02:39</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>undersøgelsesspørgsmål 1 (multi-choiec/sinngle-svar)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>undersøgelse svar 3</history:answerChoice>
                                <history:answerChoice>undersøgelse svar 2</history:answerChoice>
                                <history:answerChoice>undersøgelse svar 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>undersøgelse svar 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>undersøgelse svar 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>Intet svar</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>undersøgelsesspørgsmål 2 (multi-choiec/multi-answer)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>undersøgelse svar D</history:answerChoice>
                                <history:answerChoice>undersøgelse svar C</history:answerChoice>
                                <history:answerChoice>undersøgelse svar B</history:answerChoice>
                                <history:answerChoice>undersøgelse svar med et</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>undersøgelse svar D, undersøgelse svar 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>undersøgelse svar C, undersøgelse svar 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>Intet svar</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>undersøgelsesspørgsmål 3 (kort svar)</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>Intet svar</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
            </history:polls>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Svaret er anderledes, hvis mødet ikke findes, tilhører ikke den bruger, der anmoder om det, eller hvis den bruger, der anmoder om det, ikke også er webstedsadministrator.

Svar eksempel:

<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>FEJL</serv:result>
            <serv:reason>beklager, ingen optagelse fundet</serv:reason>
            <serv:gsbStatus>primær</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Ny valgmulighed for AttendeeSendVideo i API'erne CreateTrainingSession, SetTrainingSession og GetTrainingSession

Da valgmulighederne er tilgængelige ved planlægning af en Training Center-session omfatter Send video, har XML API nu tilføjet valgmuligheden attendeeSendVideo for at oprette, få og indstille API'er til Training Center sessioner.

Påvirkede API'er:

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

Design

Valgmuligheden blev gemt i DB-tabellen WbxMMConfParam/paramvalue som paramname = ' optionSupportSendVideo '

CreateTrainingSession anmodnings opdateringer:

SetTrainingSession anmodnings opdateringer:


Anmodningen er kun for T32/XML API11.0.0.

Opdateringer til GetTrainingSession- svar:

Skift ConfName størrelsesgrænse maks. 128 Vis tegn

Konferencenavn streng ConfName er nu begrænset til maksimalt 128 display tegn. Denne ændring stemmer overens med J2EE-Startside begrænsningen. Hvis en API-anmodning inkluderer ConfName , der er tom eller overstiger en 128 Vis tegnlængde, vises følgende fejlmeddelelse:

"060065 ulovligt input konferencenavn. Konferencenavnet må ikke være tomt eller overstige den maksimale visnings tegnlængde 128. "

Påvirkede API'er:

  • ConfName

Undtagelsesmeddelelse ændret i API LstRecording

Undtagelsesmeddelelsen udløses, når forespørgslens tidsområde overstiger den maksimale grænse på API- LstRecording, blev ændret. Som standard understøtter forespørgsler 4 ugers optagelser. Anmodninger med mere end fire uger modtager følgende fejlmeddelelse:

"999999 har oversteget det maksimale antal forespørgsler på 28 dage".

Påvirkede API'er:

  • LstRecording

XML API 11.0.0 SP10-opdateringer

XML API 11,0 SP10-opdateringen har ingen skemaændringer.