Denne artikel indeholder opdateringer og ændringer til XML API månedlig SP-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 tidspunktet for seneste ændring

Vi opgraderer LstSummaryUser- API'en for at give brugerne mulighed for at forespørge brugerkonti, afhængigt af hvornår de sidst blev ændret. Tre nye elementer, modifiedDateStart, modifiedDateEndog lastModifiedTime, er blevet føjet til API'en.


Det maksimale tidsinterval for denne forespørgsel er 90 dage. Hvis du indtaster 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 -anmodninger og respone-opdateringer:

LstSummaryUser- anmodning 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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>* * 5124 * * *</use:userID>                 <use:webExId>* * * Mr * * * * * * hr * * * * *</use:webExId>                 <use:firstName></use:firstName>                 <use:lastName>* Est * * *</use:lastName>                 <use:email>* * * Est * * * @qa. Webex.com</use:email>
                <use:userRoleType>VÆRT</use:userRoleType>
                <use:registrationDate>06/19/2016 22:13:06</use:registrationDate>
                <use:active>DEAKTIVERET</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 der bruges anonym adgang

Som en sikkerhedsopdatering har vi forbedret GetSessionInfo -og GetUserCard- API'erne med captcha-beskyttelse af svarkode. Hvis dine applikationer ringer til API'erne vha. anonym adgang, skal du forbedre din applikation til 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>OPSTÅ</serv:result>
            <serv:reason>Tilsvarende møde ikke fundet</serv:reason>
            <serv:gsbStatus>VIGTIGSTE</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>OPSTÅ</serv:result>
            <serv:reason>Tilsvarende møde ikke fundet</serv:reason>
            <serv:gsbStatus>VIGTIGSTE</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>OPSTÅ</serv:result>
            <serv:reason>CAPTCHA-ID og Word er ugyldige eller mangler</serv:reason>
            <serv:gsbStatus>VIGTIGSTE</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 personligt lokale

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

LstSummaryUser svar eksempel:

XML API-39.9.0 opdateringer

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

Support til korte SIP URL-adresser til personlige mødelokaler (PMR)

Support til det korte SIP URL-format til PMRs påvirker GetSessionInfo, GetMeeting, GetUserog GetMe API'er. Et nyt svarelement med navnet displayMeetingUrl blev føjet til GetUser -og GetMe -API'er 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.

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>PRIVATE</ep:listStatus>
        <ep:registration>returneres</ep:registration>
        <ep:passwordReq>sand</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, Pacific (San Francisco)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>returneres</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>sand</ep:isAllowJBH>
    <ep:isCETMeeting>sand</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>returneres</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 begivenheders adfærds ændring

Alle planlagte møder er som standard video enheds aktiverede møder. Men når du planlæg et møde men vælger ingen eller andre for dit mødes lyd, planlægges mødet som et ikke-videoenhed-aktiveret Webex-møde.

Påvirkede API'er:

  • CreateMeeting

  • 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 med navnet attentionToDurationPercentage blev føjet til LsttrainingattendeeHistory- API'en. 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

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

Der blev leveret nye svar elementer til at returnere forskellige licens tællinger i GetSite- API'en.

Påvirkede API'er:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

GetSiteFT -og SetSiteFT- design

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

Påvirkede API'er:

  • GetSiteFT

  • SetSiteFT

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

</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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>returneres</ns1:value>
                </ns1:featureToggle>
                <ns1:featureToggle>
                    <ns1:name>RemoveCMRLicenseSA</ns1:name>
                    <ns1:value>returneres</ns1:value>
                </ns1:featureToggle>
            </ns1:featureToggles>
        </serv:bodyContent>
    </serv:body>
</serv:message>

SetSite- anmodning 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>returneres</value>
                </featureToggle>
                <featureToggle>
                    <name>SupportPeopleInsight</name>
                    <value>sand</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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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 beskrivelsens indholdslængde begrænset til 2500 tegn:

Påvirkede API'er:

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

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

XML API-39.5.0 opdateringer

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

Et nyt element med navnet videoMeshInterclusters blev føjet til SetSite- elementet. videoMeshInterclusters indeholder også tre underordnede elementer videoMeshHomeCluster1, videoMeshHomeCluster2og videoMeshHomeCluster3.

Påvirkede API'er:

  • SetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

SetSite- anmodning:

GetSite- svar:

XML API-39.3.0 opdateringer

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

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

Når du i øjeblikket deltager i et Webex-møde, skal applikationen eller enheden give webstedets oplysninger, dette gør mødets deltagelse svær. 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 nemmere, fjernede vi kravet om at indtaste sitename fra Meeting SIP URI: meeting_number@webex.com.

For at bevare bagudkompatibilitet fungerer det gamle format på sipURL, og ny formatet tilføjes til det nye element displayMeetingUrl

Påvirkede API'er:

  • GetMeeting

    • displayMeetingUrl

  • GetEvent

    • displayMeetingUrl

  • GetSessionInfo

    • displayMeetingUrl

Arbejdsprocesdiagram

GetMeeting- skema

GetMeeting- prøve svar

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

GetEvent- skema

GetEvent- prøve svar

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

GetSessionInfo- skema

GetSessionInfo- prøve svar

    <ep:isCETMeeting>sand</ep:isCETMeeting>
    <ep:isNextUpcomingInstance>sand</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>

E-mail eksempel

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

Følgende API'er har nu indholdslængde for Description-elementet begrænset til 1024 tegn:

Påvirkede API'er:

  • CreateTrainingSession

  • SetTrainingSession

  • CreateEvent

  • SetEvent

Dette er for at forhindre Cisco Webex i at blive ikke i stand til at behandle anmodningen. Hvis beskrivelsen er længere end 1024 tegn, returneres en fejlmeddelelse: "060067 ugyldig beskrivelse af input. Beskrivelsen må ikke overstige den maksimale visnings tegns længde 1024. "

Prøve svar for 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>OPSTÅ</serv:result>
            <serv:reason>
Ugyldig beskrivelse af input. Beskrivelsen må ikke overstige den maksimale visnings tegns længde 1024
            </serv:reason>
            <serv:gsbStatus>VIGTIGSTE</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'en

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>

Sammenligning af svar

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:isLocked>returneres</ep:isLocked>
    <ep:sessionkey>712419789</ep:sessionkey>
    <ep:confID>120396209273701973</ep:confID>
    <ep:accessControl>
        <ep:sessionPassword></ep:sessionPassword>   <!--Removed-->
        <ep:listStatus>IKKE angivet</ep:listStatus>
        <ep:registration>returneres</ep:registration>
        <ep:passwordReq>returneres</ep:passwordReq>
        <ep:isEnforceAudioPassword>returneres</ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin>returneres</ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Simon test 's personlige lokale</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType>MeetingCenter</ep:serviceType>
        <ep:isRecurring>returneres</ep:isRecurring>
        <ep:agendaFormat>TEKST</ep:agendaFormat>
        <ep:descriptionFormat>TEKST</ep:descriptionFormat>
        <ep:isException>returneres</ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException>returneres</ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>Tilbagekalds</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-kode] # * 01 * | AutoLGPWDialInSequence: [AccessNumber],, * 00 * [adgangskode] #,,, [ProfileID] #,,, [PIN] #,,, [adgangskode] # | SilentLGPWDialInSequence: [AccessNumber],, * 01 * [adgangskode] # [ProfileID] # [PIN-kode] # [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>falsk</serv:tollFree>    <!--Removed-->                 <serv:default>falsk indgå</serv:default>  <!--Removed-->             </serv:globalNum> <!--Removed-->         </ep:callInNum>   <!--Removed-->         <ep:labels>   <!--Removed-->             <ep:tollFreeCallInLabel>ende opkald-gratisnummer (USA/Canada)</ep:tollFreeCallInLabel>   <!--Removed-->             <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->         </ep:labels>  <!--Removed-->         <ep:isMPAudio>falsk</ep:isMPAudio>  <!--Removed-->         <ep:voip>sand</ep:voip> <!--Removed-->         <ep:enableTSP></ep:enableTSP>  <!--Removed-->     </ep:telephony>   falsk<!--Removed-->     <ep:host>         <ep:firstName>Chef</ep:firstName>
        <ep:lastName>Test</ep:lastName>
        <ep:email>simon0@qa.webex.com</ep:email>
        <ep:webExId>Simon</ep:webExId>
        <ep:allowAnyoneHostMeeting>returneres</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>returneres</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly>returneres</ep:isAudioOnly>
    <ep:telePresence>returneres</ep:telePresence>
    <ep:isAlternateHost>falsk</ep:isAlternateHost>  <!--Removed-->     <ep:isCreator>sand</ep:isCreator>   <!--Removed-->     <ep:hostKey>954462</ep:hostKey> <!--Removed-->     <ep:supportE2E>falsk</ep:supportE2E>    <!--Removed-->     <ep:isAllowJBH>falsk</ep:isAllowJBH>
    <ep:isCETMeeting>sand</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>sand</ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance>sand</ep:isNextUpcomingInstance>
    <ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed</ep:meetingLink>
    <ep:sipURL>simon0@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>simon0@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
    <ep:isAutoRecord>returneres</ep:isAutoRecord>
</serv:bodyContent>

XML API-39.2.0 opdateringer

Nyt element lastLoginTime returneret i LstSummaryUser- svar

Beskrivelse:

Et nyt svarelement med navnet lastLoginTimeblev føjet til LstSummaryUser- API'en. 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

GetAPIVersion- svar:

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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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 API GetAPIVersion

Beskrivelse:

Et nyt svarelement med navnet apiVerblev føjet til GetAPIVersion- API'en. 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, f. eks. 39.1.0 for opdateringen i januar 2019.

Påvirkede API'er:

  • GetAPIVersion

    • apiVer

Elementet apiVersion vil blive anbefalet den 1. maj 2019, og element udgivelsen vil blive tildelt en ny XML-API d. 1. maj 2019.

GetAPIVersion- svar:

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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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/HD-parametre fjernet fra XML API

Beskrivelse:

HQ-og HD-Videoegenskaber bestemmes nu på webstedsniveau, hvorved de tidligere blev bestemt på brugerniveau. De to valgmuligheder for disse parametre ignoreres, når der sendes anmodninger fra følgende API'er:

  • CreateMeeting

  • SetMeeting

  • CreateTrainingSession

  • SetTrainingSession

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

Der er ingen skemaændringer til denne ændrede adfærd.

Nyt element uploadLogFileUrl føjet til webstedets metadata, der returneres til desktop-appen

Beskrivelse:

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

Påvirkede API'er:

  • GetSite

    • uploadLogFileUrl

Schema

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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>sand</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>TILFØJELSES</ns1:meetingTypeName>
                        <ns1:hideInScheduler>returneres</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>11</ns1:meetingTypeID>
                        <ns1:meetingTypeName>TRS</ns1:meetingTypeName>
                        <ns1:hideInScheduler>returneres</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>13</ns1:meetingTypeID>
                        <ns1:meetingTypeName>SC3</ns1:meetingTypeName>
                        <ns1:hideInScheduler>returneres</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>16</ns1:meetingTypeID>
                        <ns1:meetingTypeName>AUO</ns1:meetingTypeName>
                        <ns1:hideInScheduler>returneres</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>214</ns1:meetingTypeID>
                        <ns1:meetingTypeName>ARBEJDE</ns1:meetingTypeName>
                        <ns1:hideInScheduler>returneres</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>Frankrig</ns1:region>
                    <ns1:currency>Franske franc</ns1:currency>
                    <ns1:timeZoneID>4</ns1:timeZoneID>
                    <ns1:timeZone>GMT-08:00, Pacific (San Douglas)</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>fransk</ns1:pageLanguage>
                    <ns1:activateStatus>sand</ns1:activateStatus>
                    <ns1:webPageType>J2EE</ns1:webPageType>
                    <ns1:iCalendar>sand</ns1:iCalendar>
                    <ns1:myWebExDefaultPage>Mine møder</ns1:myWebExDefaultPage>
                    <ns1:componentVersion>cmp3300</ns1:componentVersion>
                    <ns1:accountNumLimit>999999</ns1:accountNumLimit>
                    <ns1:activeUserCount>40</ns1:activeUserCount>
                    <ns1:displayMeetingActualTime>returneres</ns1:displayMeetingActualTime>
                    <ns1:displayOffset>sand</ns1:displayOffset>
                    <ns1:supportWebEx11>returneres</ns1:supportWebEx11>
                </ns1:metaData>
                <ns1:ucf>
                    <ns1:ucfConfiguration>UCF 2,1</ns1:ucfConfiguration>
                </ns1:ucf>
                <ns1:clientPlatforms>
                    <ns1:msWindows>sand</ns1:msWindows>
                    <ns1:macOS9>sand</ns1:macOS9>
                    <ns1:macOSX>sand</ns1:macOSX>
                    <ns1:sunSolaris>sand</ns1:sunSolaris>
                    <ns1:linux>sand</ns1:linux>
                    <ns1:hpUnix>returneres</ns1:hpUnix>
                    <ns1:java>sand</ns1:java>
                    <ns1:palm>returneres</ns1:palm>
                </ns1:clientPlatforms>
                <ns1:resourceRestrictions>
                    <ns1:isLicenseManager>sand</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>sand</ns1:autoLogin>
                    <ns1:aspAndPHPAPI>sand</ns1:aspAndPHPAPI>
                    <ns1:backwardAPI>returneres</ns1:backwardAPI>
                    <ns1:xmlAPI>sand</ns1:xmlAPI>
                    <ns1:cAPI>returneres</ns1:cAPI>
                    <ns1:scorm>sand</ns1:scorm>
                </ns1:supportAPI>
                <ns1:myWebExConfig>
                    <ns1:myContacts>sand</ns1:myContacts>
                    <ns1:myProfile>sand</ns1:myProfile>
                    <ns1:myMeetings>sand</ns1:myMeetings>
                    <ns1:trainingRecordings>sand</ns1:trainingRecordings>
                    <ns1:folders>returneres</ns1:folders>
                    <ns1:eventDocument>sand</ns1:eventDocument>
                    <ns1:myReport>returneres</ns1:myReport>
                    <ns1:myComputer>returneres</ns1:myComputer>
                    <ns1:personalMeetingPage>returneres</ns1:personalMeetingPage>
                    <ns1:myFilesStorage>1000</ns1:myFilesStorage>
                    <ns1:myComputerNumbers>0</ns1:myComputerNumbers>
                    <ns1:enableMyWebExPro>sand</ns1:enableMyWebExPro>
                    <ns1:myWebExProMaxHosts>999999</ns1:myWebExProMaxHosts>
                    <ns1:restrictAccessAnyApps>returneres</ns1:restrictAccessAnyApps>
                    <ns1:restrictAccessAnyAppsNum>0</ns1:restrictAccessAnyAppsNum>
                    <ns1:addlAccessAnyComputersLimit>STRENGE</ns1:addlAccessAnyComputersLimit>
                    <ns1:addlAccessAnyComputers>0</ns1:addlAccessAnyComputers>
                    <ns1:addlStorageLimit>STRENGE</ns1:addlStorageLimit>
                    <ns1:addlStorage>0</ns1:addlStorage>
                    <ns1:myContactsPro>sand</ns1:myContactsPro>
                    <ns1:myProfilePro>sand</ns1:myProfilePro>
                    <ns1:myMeetingsPro>sand</ns1:myMeetingsPro>
                    <ns1:trainingRecordingsPro>sand</ns1:trainingRecordingsPro>
                    <ns1:foldersPro>returneres</ns1:foldersPro>
                    <ns1:eventDocumentPro>sand</ns1:eventDocumentPro>
                    <ns1:myReportPro>sand</ns1:myReportPro>
                    <ns1:myComputerPro>returneres</ns1:myComputerPro>
                    <ns1:personalMeetingPagePro>sand</ns1:personalMeetingPagePro>
                    <ns1:myFilesStoragePro>1000</ns1:myFilesStoragePro>
                    <ns1:myComputerNumbersPro>0</ns1:myComputerNumbersPro>
                    <ns1:PMRheaderBranding>returneres</ns1:PMRheaderBranding>
                </ns1:myWebExConfig>
                <ns1:telephonyConfig>
                    <ns1:isTSPUsingTelephonyAPI>returneres</ns1:isTSPUsingTelephonyAPI>
                    <ns1:serviceName>Personlig konference nr.</ns1:serviceName>                     <ns1:participantAccessCodeLabel>Mødedeltager adgangskode</ns1:participantAccessCodeLabel>
                    <ns1:subscriberAccessCodeLabel>Værtsadgangskode</ns1:subscriberAccessCodeLabel>
                    <ns1:attendeeIDLabel>Mødedeltager-ID</ns1:attendeeIDLabel>
                    <ns1:internetPhone>sand</ns1:internetPhone>
                    <ns1:supportCallInTypeTeleconf>sand</ns1:supportCallInTypeTeleconf>
                    <ns1:callInTeleconferencing>sand</ns1:callInTeleconferencing>
                    <ns1:tollFreeCallinTeleconferencing>sand</ns1:tollFreeCallinTeleconferencing>
                    <ns1:intlCallInTeleconferencing>sand</ns1:intlCallInTeleconferencing>
                    <ns1:callBackTeleconferencing>sand</ns1:callBackTeleconferencing>
                    <ns1:callInNumber>1</ns1:callInNumber>
                    <ns1:defaultTeleServerSubject>0.0.0.0</ns1:defaultTeleServerSubject>
                    <ns1:subscribeName>SVAR</ns1:subscribeName>
                    <ns1:subscribePassword>opfylder</ns1:subscribePassword>
                    <ns1:defaultPhoneLines>10</ns1:defaultPhoneLines>
                    <ns1:defaultSpeakingLines>10</ns1:defaultSpeakingLines>
                    <ns1:majorCountryCode>1</ns1:majorCountryCode>
                    <ns1:majorAreaCode>408</ns1:majorAreaCode>
                    <ns1:publicName>Indgående opkalds bruger</ns1:publicName>
                    <ns1:hybridTeleconference>sand</ns1:hybridTeleconference>
                    <ns1:instantHelp>returneres</ns1:instantHelp>
                    <ns1:customerManage>returneres</ns1:customerManage>
                    <ns1:maxCallersNumber>500</ns1:maxCallersNumber>
                    <ns1:isSpecified>returneres</ns1:isSpecified>
                    <ns1:isContinue>returneres</ns1:isContinue>
                    <ns1:intlCallBackTeleconferencing>sand</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>returneres</serv:tollFree>
                                <serv:default>returneres</serv:default>
                            </serv:globalNum>
                            <serv:enableServer>sand</serv:enableServer>
                            <serv:tollLabel>14085452910</serv:tollLabel>
                            <serv:tollFreeLabel>Indgående opkald gratisnummer (USA/Canada)</serv:tollFreeLabel>                         </ns1:primaryLargeServer>                         <ns1:backup1LargeServer>                             <serv:enableServer>falsk</serv:enableServer>
                            <serv:tollLabel>Indgående Opkaldsnummer (USA/Canada) indgå</serv:tollLabel>                             <serv:tollFreeLabel>ende opkald – gratisnummer (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup1LargeServer>                         <ns1:backup2LargeServer>                             <serv:enableServer>falsk</serv:enableServer>
                            <serv:tollLabel>Sikkerhedskopi indgående opkaldsnummer, betaling (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>sikkerhedskopieret gratis opkaldsnummer (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup2LargeServer>                         <ns1:primarySmallServer>                             <serv:enableServer>falsk</serv:enableServer>
                            <serv:tollLabel>Indgående Opkaldsnummer (USA/Canada) indgå</serv:tollLabel>                             <serv:tollFreeLabel>ende opkald – gratisnummer (USA/Canada)</serv:tollFreeLabel>                         </ns1:primarySmallServer>                         <ns1:backup1SmallServer>                             <serv:enableServer>falsk</serv:enableServer>
                            <serv:tollLabel>Indgående Opkaldsnummer (USA/Canada) indgå</serv:tollLabel>                             <serv:tollFreeLabel>ende opkald – gratisnummer (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup1SmallServer>                         <ns1:backup2SmallServer>                             <serv:enableServer>falsk</serv:enableServer>
                            <serv:tollLabel>Sikkerhedskopi indgående opkaldsnummer, betaling (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>sikkerhedskopieret gratis opkaldsnummer (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup2SmallServer>                         <ns1:joinBeforeHost>falsk</ns1:joinBeforeHost>
                    </ns1:personalTeleconf>
                    <ns1:multiMediaPlatform>sand</ns1:multiMediaPlatform>
                    <ns1:multiMediaHostName>msa1mcccl01.dmz.webex.com</ns1:multiMediaHostName>
                    <ns1:broadcastAudioStream>sand</ns1:broadcastAudioStream>
                    <ns1:tspAdaptorSettings>
                        <ns1:primaryLarge>
                            <ns1:enableAdaptor>returneres</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Opkaldsnummer</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Gratis opkaldsnummer</ns1:label>
                            </ns1:mpAudio>
                        </ns1:primaryLarge>
                        <ns1:backup1Large>
                            <ns1:enableAdaptor>returneres</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Opkaldsnummer</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Gratis opkaldsnummer</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup1Large>
                        <ns1:backup2Large>
                            <ns1:enableAdaptor>returneres</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Opkaldsnummer</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Gratis opkaldsnummer</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup2Large>
                    </ns1:tspAdaptorSettings>
                    <ns1:meetingPlace>
                        <ns1:persistentTSP>returneres</ns1:persistentTSP>
                        <ns1:mpAudioConferencing>WithoutIntegration</ns1:mpAudioConferencing>
                    </ns1:meetingPlace>
                    <ns1:supportOtherTypeTeleconf>returneres</ns1:supportOtherTypeTeleconf>
                    <ns1:otherTeleServiceName>Andre telekonferencetjenesteydelser</ns1:otherTeleServiceName>
                    <ns1:supportAdapterlessTSP>returneres</ns1:supportAdapterlessTSP>
                    <ns1:displayAttendeeID>returneres</ns1:displayAttendeeID>
                    <ns1:provisionTeleAccount>sand</ns1:provisionTeleAccount>
                    <ns1:choosePCN>returneres</ns1:choosePCN>
                    <ns1:audioOnly>sand</ns1:audioOnly>
                    <ns1:configTollAndTollFreeNum>returneres</ns1:configTollAndTollFreeNum>
                    <ns1:configPrimaryTS>returneres</ns1:configPrimaryTS>
                    <ns1:teleCLIAuthEnabled>returneres</ns1:teleCLIAuthEnabled>
                    <ns1:teleCLIPINEnabled>returneres</ns1:teleCLIPINEnabled>
                </ns1:telephonyConfig>
                <ns1:commerceAndReporting>
                    <ns1:trackingCode>returneres</ns1:trackingCode>
                    <ns1:siteAdminReport>sand</ns1:siteAdminReport>
                    <ns1:subScriptionService>returneres</ns1:subScriptionService>
                    <ns1:isECommmerce>returneres</ns1:isECommmerce>
                    <ns1:customereCommerce>returneres</ns1:customereCommerce>
                    <ns1:isLocalTax>returneres</ns1:isLocalTax>
                    <ns1:localTaxName>MOMSPRODUKTBOGF</ns1:localTaxName>
                    <ns1:localTaxtRate>0,0</ns1:localTaxtRate>
                    <ns1:holReport>1</ns1:holReport>
                </ns1:commerceAndReporting>
                <ns1:tools>
                    <ns1:businessDirectory>returneres</ns1:businessDirectory>
                    <ns1:officeCalendar>returneres</ns1:officeCalendar>
                    <ns1:meetingCalendar>sand</ns1:meetingCalendar>
                    <ns1:displayOnCallAssistLink>returneres</ns1:displayOnCallAssistLink>
                    <ns1:displayProfileLink>sand</ns1:displayProfileLink>
                    <ns1:recordingAndPlayback>sand</ns1:recordingAndPlayback>
                    <ns1:recordingEditor>sand</ns1:recordingEditor>
                    <ns1:publishRecordings>sand</ns1:publishRecordings>
                    <ns1:instantMeeting>sand</ns1:instantMeeting>
                    <ns1:emails>returneres</ns1:emails>
                    <ns1:outlookIntegration>sand</ns1:outlookIntegration>
                    <ns1:wirelessAccess>returneres</ns1:wirelessAccess>
                    <ns1:allowPublicAccess>sand</ns1:allowPublicAccess>
                    <ns1:ssl>sand</ns1:ssl>
                    <ns1:handsOnLab>sand</ns1:handsOnLab>
                    <ns1:holMaxLabs>999999</ns1:holMaxLabs>
                    <ns1:holMaxComputers>999999</ns1:holMaxComputers>
                    <ns1:userLockDown>returneres</ns1:userLockDown>
                    <ns1:meetingAssist>returneres</ns1:meetingAssist>
                    <ns1:sms>returneres</ns1:sms>
                    <ns1:encryption>INGEN</ns1:encryption>
                    <ns1:internalMeeting>returneres</ns1:internalMeeting>
                    <ns1:enableTP>returneres</ns1:enableTP>
                    <ns1:enableTPplus>returneres</ns1:enableTPplus>
                    <ns1:uploadLogFileUrl>https://sqwd.webex.com/logadmin/spr.do?SiteUrl=sqdemo28&LanguageId=1</ns1:uploadLogFileUrl>
                </ns1:tools>
                <ns1:custCommunications>
                    <ns1:displayType>
                        <ns1:prodSvcAnnounce>returneres</ns1:prodSvcAnnounce>
                        <ns1:trainingInfo>returneres</ns1:trainingInfo>
                        <ns1:eNewsletters>returneres</ns1:eNewsletters>
                        <ns1:promotionsOffers>returneres</ns1:promotionsOffers>
                        <ns1:pressReleases>returneres</ns1:pressReleases>
                    </ns1:displayType>
                    <ns1:displayMethod>
                        <ns1:email>returneres</ns1:email>
                        <ns1:fax>returneres</ns1:fax>
                        <ns1:phone>returneres</ns1:phone>
                        <ns1:mail>returneres</ns1:mail>
                    </ns1:displayMethod>
                </ns1:custCommunications>
                <ns1:trackingCodes/>
                <ns1:supportedServices>
                    <ns1:meetingCenter>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:pageVersion>mc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                    </ns1:meetingCenter>
                    <ns1:trainingCenter>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:pageVersion>tc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                    </ns1:trainingCenter>
                    <ns1:supportCenter>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:pageVersion>sc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                        <ns1:webACD>sand</ns1:webACD>
                    </ns1:supportCenter>
                    <ns1:eventCenter>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:pageVersion>ec3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                        <ns1:marketingAddOn>returneres</ns1:marketingAddOn>
                        <ns1:optimizeAttendeeBandwidthUsage>returneres</ns1:optimizeAttendeeBandwidthUsage>
                    </ns1:eventCenter>
                    <ns1:salesCenter>
                        <ns1:enabled>returneres</ns1:enabled>
                    </ns1:salesCenter>
                </ns1:supportedServices>
                <ns1:securityOptions>
                    <ns1:passwordExpires>returneres</ns1:passwordExpires>
                    <ns1:passwordLifetime>0</ns1:passwordLifetime>
                    <ns1:ECMeetingsUnlisted>returneres</ns1:ECMeetingsUnlisted>
                    <ns1:TCMeetingsUnlisted>returneres</ns1:TCMeetingsUnlisted>
                    <ns1:allMeetingsUnlisted>sand</ns1:allMeetingsUnlisted>
                    <ns1:allMeetingsPassword>sand</ns1:allMeetingsPassword>
                    <ns1:joinBeforeHost>returneres</ns1:joinBeforeHost>
                    <ns1:audioBeforeHost>returneres</ns1:audioBeforeHost>
                    <ns1:audioBeforeHostEC>returneres</ns1:audioBeforeHostEC>
                    <ns1:audioBeforeHostTC>returneres</ns1:audioBeforeHostTC>
                    <ns1:changePersonalURL>sand</ns1:changePersonalURL>
                    <ns1:changeUserName>returneres</ns1:changeUserName>
                    <ns1:meetings>
                        <ns1:strictPasswords>sand</ns1:strictPasswords>
                    </ns1:meetings>
                    <ns1:strictUserPassword>sand</ns1:strictUserPassword>
                    <ns1:accountNotify>returneres</ns1:accountNotify>
                    <ns1:requireLoginBeforeSiteAccess>returneres</ns1:requireLoginBeforeSiteAccess>
                    <ns1:changePWDWhenAutoLogin>returneres</ns1:changePWDWhenAutoLogin>
                    <ns1:enforceBaseline>sand</ns1:enforceBaseline>
                    <ns1:passwordChangeIntervalOpt>returneres</ns1:passwordChangeIntervalOpt>
                    <ns1:passwordChangeInterval>24</ns1:passwordChangeInterval>
                    <ns1:firstAttendeeAsPresenter>returneres</ns1:firstAttendeeAsPresenter>
                    <ns1:isEnableUUIDLink>sand</ns1:isEnableUUIDLink>
                    <ns1:isEnableUUIDLinkForSAC>sand</ns1:isEnableUUIDLinkForSAC>
                    <ns1:enforceRecordingPwdForMC>sand</ns1:enforceRecordingPwdForMC>
                    <ns1:enforceRecordingPwdForEC>returneres</ns1:enforceRecordingPwdForEC>
                    <ns1:enforceRecordingPwdForTC>returneres</ns1:enforceRecordingPwdForTC>
                    <ns1:enforceRecordingPwdForMisc>sand</ns1:enforceRecordingPwdForMisc>
                </ns1:securityOptions>
                <ns1:defaults>
                    <ns1:emailReminders>sand</ns1:emailReminders>
                    <ns1:entryExitTone>BIP</ns1:entryExitTone>
                    <ns1:voip>sand</ns1:voip>
                    <ns1:teleconference>
                        <ns1:telephonySupport>RINGE</ns1:telephonySupport>
                        <ns1:tollFree>sand</ns1:tollFree>
                        <ns1:intlLocalCallIn>sand</ns1:intlLocalCallIn>
                    </ns1:teleconference>
                    <ns1:joinTeleconfNotPress1>returneres</ns1:joinTeleconfNotPress1>
                    <ns1:updateTSPAccount>returneres</ns1:updateTSPAccount>
                </ns1:defaults>
                <ns1:scheduleMeetingOptions>
                    <ns1:scheduleOnBehalf>sand</ns1:scheduleOnBehalf>
                    <ns1:saveSessionTemplate>sand</ns1:saveSessionTemplate>
                </ns1:scheduleMeetingOptions>
                <ns1:navBarTop>
                    <ns1:button>
                        <ns1:order>1</ns1:order>
                        <ns1:serviceName>Velkommen</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>2</ns1:order>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:serviceName>Meeting Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>3</ns1:order>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:serviceName>Event Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>4</ns1:order>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:serviceName>Support Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>5</ns1:order>
                        <ns1:enabled>sand</ns1:enabled>
                        <ns1:serviceName>Training Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>6</ns1:order>
                        <ns1:serviceName>Webstedsadministration</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>7</ns1:order>
                        <ns1:enabled>returneres</ns1:enabled>
                        <ns1:serviceName>Sales Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:displayDisabledService>sand</ns1:displayDisabledService>
                </ns1:navBarTop>
                <ns1:navMyWebEx>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:partnerLinks>
                        <ns1:partnerLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:partnerLink>
                    </ns1:partnerLinks>
                    <ns1:partnerIntegration>sand</ns1:partnerIntegration>
                    <ns1:support>
                        <ns1:target>NYT</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:target>NYT</ns1:target>
                    </ns1:training>
                </ns1:navMyWebEx>
                <ns1:navAllServices>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NYT</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:support>
                        <ns1:name>Support</ns1:name>
                        <ns1:target>NYT</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:name>Undervisning</ns1:name>
                        <ns1:target>NYT</ns1:target>
                    </ns1:training>
                    <ns1:supportMenu>
                        <ns1:userGuides>
                            <ns1:target>NYT</ns1:target>
                        </ns1:userGuides>
                        <ns1:downloads>
                            <ns1:target>NYT</ns1:target>
                        </ns1:downloads>
                        <ns1:training>
                            <ns1:target>NYT</ns1:target>
                        </ns1:training>
                        <ns1:contactUs>
                            <ns1:target>NYT</ns1:target>
                        </ns1:contactUs>
                        <ns1:supportMyResources>sand</ns1:supportMyResources>
                    </ns1:supportMenu>
                </ns1:navAllServices>
                <ns1:passwordCriteria>
                    <ns1:mixedCase>returneres</ns1:mixedCase>
                    <ns1:minLength>4</ns1:minLength>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallowWebTextSessions>sand</ns1:disallowWebTextSessions>
                    <ns1:disallowWebTextAccounts>sand</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>sand</ns1:disallowList>
                    <ns1:disallowValue>adgangskode</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>opfylder</ns1:disallowValue>
                </ns1:passwordCriteria>
                <ns1:recordingPasswordCriteria>
                    <ns1:mixedCase>sand</ns1:mixedCase>
                    <ns1:minLength>8</ns1:minLength>
                    <ns1:minAlpha>2</ns1:minAlpha>
                    <ns1:minNumeric>1</ns1:minNumeric>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallowWebTextSessions>returneres</ns1:disallowWebTextSessions>
                    <ns1:disallowList>returneres</ns1:disallowList>
                    <ns1:disallowValue>adgangskode</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>opfylder</ns1:disallowValue>
                </ns1:recordingPasswordCriteria>
                <ns1:accountPasswordCriteria>
                    <ns1:mixedCase>returneres</ns1:mixedCase>
                    <ns1:minLength>0</ns1:minLength>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallow3XRepeatedChar>returneres</ns1:disallow3XRepeatedChar>
                    <ns1:disallowWebTextAccounts>sand</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>sand</ns1:disallowList>
                    <ns1:disallowValue>adgangskode</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>opfylder</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>sand</ns1:enable>
                    <ns1:installOpts>
                        <ns1:autoUpdate>sand</ns1:autoUpdate>
                    </ns1:installOpts>
                    <ns1:integrations>
                        <ns1:outlook>sand</ns1:outlook>
                        <ns1:outlookForMac>sand</ns1:outlookForMac>
                        <ns1:lotusNotes>sand</ns1:lotusNotes>
                        <ns1:oneClick>sand</ns1:oneClick>
                        <ns1:showSysTrayIcon>sand</ns1:showSysTrayIcon>
                        <ns1:office>sand</ns1:office>
                        <ns1:excel>sand</ns1:excel>
                        <ns1:powerPoint>sand</ns1:powerPoint>
                        <ns1:word>sand</ns1:word>
                        <ns1:IE>sand</ns1:IE>
                        <ns1:firefox>returneres</ns1:firefox>
                        <ns1:explorerRightClick>returneres</ns1:explorerRightClick>
                        <ns1:instantMessenger>sand</ns1:instantMessenger>
                        <ns1:aolMessenger>returneres</ns1:aolMessenger>
                        <ns1:googleTalk>returneres</ns1:googleTalk>
                        <ns1:lotusSametime>sand</ns1:lotusSametime>
                        <ns1:skype>sand</ns1:skype>
                        <ns1:windowsMessenger>sand</ns1:windowsMessenger>
                        <ns1:yahooMessenger>returneres</ns1:yahooMessenger>
                        <ns1:ciscoIPPhone>returneres</ns1:ciscoIPPhone>
                        <ns1:pcNow>returneres</ns1:pcNow>
                        <ns1:iGoogle>returneres</ns1:iGoogle>
                        <ns1:iPhoneDusting>sand</ns1:iPhoneDusting>
                    </ns1:integrations>
                    <ns1:oneClick>
                        <ns1:allowJoinUnlistMeeting>sand</ns1:allowJoinUnlistMeeting>
                        <ns1:requireApproveJoin>returneres</ns1:requireApproveJoin>
                    </ns1:oneClick>
                    <ns1:templates>
                        <ns1:useTemplate>returneres</ns1:useTemplate>
                    </ns1:templates>
                    <ns1:lockDownPT>
                        <ns1:lockDown>returneres</ns1:lockDown>
                    </ns1:lockDownPT>
                    <ns1:imSettings>
                        <ns1:attendeeInviteOther>sand</ns1:attendeeInviteOther>
                    </ns1:imSettings>
                </ns1:productivityTools>
                <ns1:meetingPlace/>
                <ns1:salesCenter>
                    <ns1:allowJoinWithoutLogin>returneres</ns1:allowJoinWithoutLogin>
                </ns1:salesCenter>
                <ns1:connectIntegration>
                    <ns1:integratedWebEx11>returneres</ns1:integratedWebEx11>
                </ns1:connectIntegration>
                <ns1:video>
                    <ns1:HQvideo>sand</ns1:HQvideo>
                    <ns1:maxBandwidth>MILJØ</ns1:maxBandwidth>
                    <ns1:HDvideo>sand</ns1:HDvideo>
                </ns1:video>
                <ns1:siteCommonOptions>
                    <ns1:SupportCustomDialRestriction>returneres</ns1:SupportCustomDialRestriction>
                    <ns1:SupportTelePresence>returneres</ns1:SupportTelePresence>
                    <ns1:SupportTelePresencePlus>returneres</ns1:SupportTelePresencePlus>
                    <ns1:EnableCloudTelepresence>sand</ns1:EnableCloudTelepresence>
                    <ns1:EnableCMRForAllUsers>sand</ns1:EnableCMRForAllUsers>
                    <ns1:enablePersonalMeetingRoom>sand</ns1:enablePersonalMeetingRoom>
                    <ns1:SupportAlternateHost>sand</ns1:SupportAlternateHost>
                    <ns1:SupportAnyoneHostMeetings>sand</ns1:SupportAnyoneHostMeetings>
                </ns1:siteCommonOptions>
                <ns1:samlSSO>
                    <ns1:enableSSO>returneres</ns1:enableSSO>
                    <ns1:autoAccountCreation>returneres</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>sand</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>40</ns1:accountNumberUsedForCMRHost>
                    <ns1:accountNumberLimitForEEHost>200</ns1:accountNumberLimitForEEHost>
                    <ns1:allowOverageForEEHost>sand</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, der er større end dette, vil nu modtage en fejlmeddelelse: "010100 størrelse af det billede, der overføres, er for stort. Prøv et billede 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.

Ny automatisk post føjet til API'er CreateMeeting, SetMeeting, GetMeeting ogLstMeeting

Beskrivelse:

Et nyt element med navnet post blev føjet til CreateMeeting, SetMeeting, GetMeeting ogLstMeeting API'er. automatisk optagelse tillader personer automatisk at optage Webex-møder direkte fra møde planlægningsprogrammet. Dette giver en granulerings grad på møder, hvor den tidligere metode til automatisk optagelse af møder kun kunne tilgås globalt på webstedsniveau.

Bemærk: I øjeblikket gælder elementet for automatisk optagelse kun for Webex-møder. Det gælder ikke for Webex-begivenheder eller Webex-undervisning.

Påvirkede API'er:

  • CreateMeeting

    • automatisk optagelse

  • SetMeeting

    • automatisk optagelse

  • GetMeeting

    • automatisk optagelse

  • LstMeeting

    • automatisk optagelse

Skemaændringer

CreateMeeting:

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er deaktiveret på webstedsadministration-siden.

SANDT

Start automatisk optagelsen, når mødet starter.

Falsk (standard)

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

Intet element

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

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er aktiveret på webstedsadministration-siden.

Sand, falskeller intet element

Ignorer element -automatisk optagelse fra XML-anmodning. Start automatisk optagelsen, når mødet starter, fordi det er aktiveret på webstedsadministration-siden.

SetMeeting:

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er deaktiveret på webstedsadministration-siden.

SANDT

Start automatisk optagelsen, når mødet starter.

Falsk (standard)

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

Intet element

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

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er aktiveret på webstedsadministration-siden.

Sand, falskeller intet element

Ignorer element -automatisk optagelse fra XML-anmodning. Start automatisk optagelsen, når mødet starter, fordi det er aktiveret på webstedsadministration-siden.

GetMeeting:

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er deaktiveret på webstedsadministration-siden.

SANDT

Start automatisk optagelsen, når mødet starter.

Falsk

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

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er aktiveret på webstedsadministration-siden.

Sand (altid)

Start automatisk optagelsen, når mødet starter, fordi det er aktiveret på webstedsadministration-siden.

Eksempel på GetMeeting svar:

LstMeeting:

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er deaktiveret på webstedsadministration-siden.

SANDT

Start automatisk optagelsen, når mødet starter.

Falsk

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

indstilling for automatisk optagelse

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er aktiveret på webstedsadministration-siden.

Sand (altid)

Start automatisk optagelsen, når mødet starter, fordi det er aktiveret på webstedsadministration-siden.

Eksempel på LstMeeting svar:

Nyt element isAutoRecord FØJET til API GetSessionInfo

Beskrivelse:

Sammen med de ændringer, der er foretaget til ovenstående API'er, blev et nyt element , der hedder isAutoRecord, tilføjet til GetSessionInfo- API'en. Dette element kan bruges til at angive automatisk start af en optagelse, når mødet starter.

Påvirkede API'er:

  • GetSessionInfo

    • isAutoRecord

Skemaændringer

GetSessionInfo:

isAutoRecord indstilling

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er deaktiveret på webstedsadministration-siden.

SANDT

Start automatisk optagelsen, når mødet starter.

Falsk

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

isAutoRecord indstilling

Funktionsmåde, når "automatisk optagelse af alle sessioner vha. netværksbaseret optagelse" er aktiveret på webstedsadministration-siden.

Sand (altid)

Start automatisk optagelsen, når mødet starter, fordi det er aktiveret på webstedsadministration-siden.

Eksempel på GetSessionInfo svar:

XML API 11.0.0-SP20 opdateringer

Nyt element returnShareToMeRecording FØJET til API LstRecording anmodning

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


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

Et nyt element med navnet returnShareToMeRecordingblev føjet til LstRecording- API'en. returnShareToMeRecording er en boolesk værdi i anmodningen om LstRecording.

Dette nye element blev tilføjet for at understøtte indsendelsen af mødedeltager eller inviterede optagelser. returnShareToMeRecording er et flag, der lader API- LstRecording vide, at det skal returnere mødedeltager eller inviterede optagelser.

Når returnShareToMeRecording er indstillet til sand, returnerer LstRecording optagelses brugeren som ejer og returnerer også optagelses brugeren som en mødedeltager eller inviterer delt af ejeren. Bemærk: Hvis automatisk deling og manuelle delings flag begge er slåetfra , returnerer LstRecording kun brugeren som ejer af optagelserne.

Når returnShareToMeRecording er indstillet til falsk, eller dette element ikke er inkluderet i anmodningen, følger LstRecording samme logik som før: den returnerer brugeres optagelser som ejer.

Påvirkede XML API'er og elementer:

  • LstRecording

    • returnShareToMeRecording (nyt)

Skema

Kendte problemer

Ingen

Element shareToMe FØJET til API LstRecording- svar


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

Et nyt element med navnet shareToMeblev føjet til LstRecording- API'en. shareToMe er en boolesk værdi i svaret for LstRecording.

Dette nye element blev tilføjet for at understøtte indsendelsen af mødedeltager eller inviterede optagelser. shareToMe er et flag, der definerer, om brugeren er ejer eller deltager eller inviterer til aktuel optagelse.

Når shareToMe er sand, er brugeren ikke ejer af aktuel optagelse. Brugeren kan være en mødedeltager eller invitere, eller optagelsen deles af ejeren.

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

Påvirkede XML API'er og elementer:

  • LstRecording

    • shareToMe (nyt)

Skema

Kendte problemer

Ingen

XML-prøver til returnShareToMeRecording og shareToMe

Eksempel på XML-anmodning

XML-svar prøve

Nye elementer føjet til API GetEvent

Fire nye elementer blev tilføjet til GetEvent- API'en:

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

  • sipURL: den URL-adresse, der bruges til at deltage i Webex-video møder fra en videokonferencesystem eller applikation

  • standaloneDialingIPAddress: den IP-adresse, der kan bruges til at ringe op til Webex-video mødet fra en videokonferencesystem eller applikation

  • panelistNumericPassword: adgangskoden til deltagelse i Webex-video mødet fra en videokonferencesystem 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 fire nye elementer. Ellers returnerer GetEvent ikke disse fire nye elementer.

Påvirkede XML API'er og elementer:

  • GetEvent

    • isCETMeeting (nyt)

    • sipURL (nyt)

    • standaloneDialingIPAddress (nyt)

    • panelistNumericPassword (nyt)

Kendte problemer

Ingen

Nyt element panelistNumericPassword føjet til API GetSessionInfo

GetSessionInfo har et nyt element med navnet panelistNumericPassword , som indeholder adgangskoden til at deltage i Webex-video mødet fra en videokonferencesystem eller en applikation.

Derudover, 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å sand/falsk, der angiver, om Webex-begivenheden understøtter Webex-video platform 2 (CMR 4,0) eller ikke

  • sipURL: den URL-adresse, der bruges til at deltage i Webex-video møder fra en videokonferencesystem eller applikation

  • standaloneDialingIPAddress: den IP-adresse, der kan bruges til at ringe op til Webex-video mødet fra en videokonferencesystem eller applikation

  • panelistNumericPassword: adgangskoden til deltagelse i Webex-video mødet fra en videokonferencesystem eller applikation

Bemærk, at for Webex-møder findes disse tre elementer allerede i GetSessionInfo:

  • isCETMeeting

  • sipURL

  • standaloneDialingIPAddress

Påvirkede XML API'er og elementer:

  • GetSessionInfo

    • panelistNumericPassword (nyt)

Kendte problemer

Ingen

Skemaændringer foretaget til GetEvent og GetSessionInfo

GetEvent

GetSessionInfo

XML API 11.0.0-SP18 opdateringer

Nyt element EnableCloudTelepresence FØJET til API getSite

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

Et nyt element med navnet EnableCloudTelepresence blev føjet til getSite- API'en.

Når valgmuligheden EnableCETForAllUsers er aktiveret, kontrollerer Webex, om brugeren understøtter Webex-video (CMR). Det returnerer nu også en ny element EnableCloudTelepresence i getSite- API'en.

Påvirkede XML APIer

  • getSite

  • EnableCloudTelepresence (nyt)

Skema

Eksempel på XML-svar

Kendte problemer

Ingen

XML API 11.0.0-SP17 opdateringer

Nyt element returnShareToMeRecording FØJET til API LstRecording anmodning

Et nyt element med navnet returnShareToMeRecordingblev føjet til LstRecording- API'en. returnShareToMeRecording er en boolesk værdi i anmodningen om LstRecording.

Dette nye element blev tilføjet for at understøtte indsendelsen af mødedeltager eller inviterede optagelser. returnShareToMeRecording er et flag, der lader API- LstRecording vide, at det skal returnere mødedeltager eller inviterede optagelser.

Når returnShareToMeRecording er indstillet til sand, returnerer LstRecording optagelses brugeren som ejer og returnerer også optagelses brugeren som en mødedeltager eller inviterer delt af ejeren. Bemærk: Hvis automatisk deling og manuelle delings flag begge er slået fra , returnerer LstRecording kun brugeren som ejer af optagelserne.

Når returnShareToMeRecording er indstillet til falsk, eller dette element ikke er inkluderet i anmodningen, følger LstRecording samme logik som før: den returnerer brugeres optagelser som ejer.

Påvirkede XML APIer

  • LstRecording

  • returnShareToMeRecording (nyt)

Skema

Kendte problemer

Ingen

Nyt element shareToMe FØJET til API LstRecording- svar

Et nyt element med navnet shareToMeblev føjet til LstRecording- API'en. shareToMe er en boolesk værdi i svaret for LstRecording.

Dette nye element blev tilføjet for at understøtte indsendelsen af mødedeltager eller inviterede optagelser. shareToMe er et flag, der definerer, om brugeren er ejer eller deltager eller inviterer til aktuel optagelse.

Når shareToMe er sand, er brugeren ikke ejer af aktuel optagelse. Brugeren kan være en mødedeltager eller invitere, eller optagelsen deles af ejeren.

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

Påvirkede XML APIer

  • LstRecording

  • shareToMe (nyt)

Skema

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

Fire nye elementer blev føjet til API'EN getSite for at angive mødedeltager kapaciteten for hver af de fire Webex-produkter:

attendeeCapacityForMC -Webex-møder

attendeeCapacityForEC – Webex events

attendeeCapacityForTC – Webex-undervisning

attendeeCapacityForSC – Webex-support

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

Påvirkede XML API'er:

  • getSite

  • attendeeCapacityForMC (nyt)

  • attendeeCapacityForEC (nyt)

  • attendeeCapacityForTC (nyt)

  • attendeeCapacityForSC (nyt)

Skema

Eksempel på getSite- svar

<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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>returneres</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>returneres</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC>returneres</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>returneres</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>returneres</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>

Kendte problemer

Ingen

XML API 11.0.0-SP16 opdateringer

Ny API- hostStreamURL tilfø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 få vist optagelsen uden først at skulle logge ind. Denne URL-adresse er gyldig i 30 minutter, efter den genereres.

Påvirkede XML APIer

hostStreamURL

Skema

<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 kundens 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 XML APIer

GetSite

Skema

Eksempel på getSite- svar for et normalt websted

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

Eksempel på getSite- svar for et ee-websted

<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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>returneres</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 ved hjælp af 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 vært eller ved at deltage i et Webex-møde som mødedeltager.

Påvirkede XML APIer

  • GetSessionInfo

  • meetingLink

Skemaændring

XML-svar prøve

Eksempel på GetSessionInfo- svar

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

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 er to typer optagelses-id'er:

  • Optagelses-ID til Webex-møder, Webex-begivenheder og Webex-undervisning

  • NBR optagelses-ID for diverse

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

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

Påvirkede XML APIer

  • LstRecording

  • Optagelses-id

Skemaændring

Eksempel på XML-anmodning til 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>Beskrivelse</orderAD>
         <orderBy>HOSTID</orderBy>
         <orderAD>ASC</orderAD>
         <orderBy>RECORDNAME</orderBy>
         <orderAD>ASC</orderAD>
    </order>
</bodyContent>

Eksempel på XML-anmodning til NBR-optagelses-ID

<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
    <recordingID>974154032</recordingID>
    <order>
         <orderBy>CREATETIME</orderBy>
         <orderAD>Beskrivelse</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 XML APIer

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

Skema

LstmeetingusagePreliminaryHistory- anmodning:

LstmeetingusagePreliminaryHistory- svar:

LstmeetingattendeePreliminaryHistory- anmodning:

LstmeetingattendeePreliminaryHistory- svar:

Eksempel på anmodning/svar

LstmeetingusagePreliminaryHistory anmodning

<?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>TIDSPUNKT</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFNAME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

LstmeetingusagePreliminaryHistory- svar

<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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>ARBEJDE</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 anmodning

<?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>TIDSPUNKT</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

LstmeetingattendeePreliminaryHistory- svar

<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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>S</history:company>
                <history:title>DJ</history:title>
                <history:phoneNumber>1222654-3210,,,,</history:phoneNumber>                 <history:address1>1 enhver gade</history:address1>
                <history:address2>s</history:address2>
                <history:city>SanJose</history:city>
                <history:state>VIA</history:state>
                <history:country>USA</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>

Kendte problemer

Ingen

Vender tilbage til SIP URL-adresse og Skype URL-adresse fra GLA GetsessionInfo API

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

  • <sipURL> er til at deltage i møde fra en telepresence-enhed eller en anden Cisco-videoenhed, så kun for møder, der bruger Cisco-video platformversion 1,0 eller 2,0, skal GetSessionInfo returnere elementet <sipURL>.

  • <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 XML APIer

GetSessionInfo

Eksempel på svar

Kendte problemer

Ingen

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

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

  • <isCETMeeting> er at vide, om mødet bruger Cisco-video platform (understøtter telepresence og video).

  • <meetingLink> er at starte eller deltage i mødet. Værter kan bruge den til at starte et møde. Mødedeltagere kan bruge den til at deltage i et møde.

  • <sipURL> er til at deltage i et møde fra en telepresence-enhed eller en anden Cisco-videoenhed, så kun for møder, der bruger Cisco video platformversion 1,0 eller 2,0, skal GetMeeting returnere elementet.

Påvirkede XML APIer

GetMeeting

Skema

Eksempel på svar

Kendte problemer

Ingen

XML API 11.0.0-SP13 opdateringer

Meddelelse om frarådelse af <siteID> elementet i overordnet <securityContext>

Cisco planlægger at forælde <siteID> elementet i det overordnede <securityContext> element og erstatte det med <siteName>. Grunden til dette er, at et stort antal <siteID> elementer ofte ændres under webstedsmigreringer, og at brugen af dette element medfører store vedligeholdelsesomkostninger. 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 <siteName> elementet fra d. 1. maj 2018.

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

Påvirkede XML APIer

  • <siteName>

  • <securityContext>

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

Fra og med juni starter både API'er <tollCallInData> og <tollFreeCallInData> data. Dette påvirker <CreateUser> og <SetUser> API'erne.

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

Nedenfor er eksempel XML API 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>returneres</createOnBridge>
        <defaultFlag>returneres</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 gav en komplet administration af brugerkontakter. For at levere bedre funktionalitet til håndtering af bruger kontakt ved hjælp af XML API har vi tilføjet disse to nye API'er, SetContact og DelContacts.

Påvirkede XML APIer

Nye API'er SetContact og DelContacts

API

Noter

SetContact

Ring til denne API for at modificere en kontakt information for eksempel, e-mail, navn, titel, sprog osv.

Korrektur

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

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

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

DelContacts

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

Returnerer contactID , hvis den angivne e-mail kan findes fra listen mine kontakter. Ignorerer den angivne e-mail, hvis den ikke er på min kontaktliste.

Hvis alle angivne e-mails ikke findes fra min kontaktliste, returneres undtagelsen 00015 (beklager, ingen optagelse fundet).

Skema

SetContact- anmodning:

Eksempel på SetContact:

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
    <securityContext>
      <siteName>SiteName</siteName>
      <webExID>UserID</webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.SetContact">
            <contactEmail>Kontakt e-mailadresse</contactEmail>
           <contact>
                <name>Ny kontaktnavn</name>
                <email>Ny kontakt-e-mailadresse</email>
                <title>Ny titel</title>
                <company>Ny virksomhed</company>
                <notes>Nye noter</notes>
                <url>Nyt link</url>
                <phones>
                    <phone>1,, 408 # # # # # #,,,,</phone>                     <mobilePhone>1,, 408 # # # # # #,,,,</mobilePhone>                     <fax>1,, 408 # # # # # #,,,,</fax>                 </phones>                 <address>                     <address1>ny adresse 1</address1>
                    <address2>Ny adresse 2</address2>
                    <city>Ny by</city>
                    <state>Ny tilstand</state>
                    <zipCode>Ny ZipCode</zipCode>
                    <country>Ny virksomhed</country>
                </address>
                <language>Nyt sprog</language>
            </contact>
</bodyContent>
</body>
</serv:message>

SetContact- svar:

Eksempel på SetContact

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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- anmodning:

Eksempel på DelContacts

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
    <securityContext>
      <siteName>SiteName</siteName>
      <webExID>UserID</webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.DelContacts">
        <contactEmail>contact1@qa.webex.com</contactEmail>
        <contactEmail>contact2@qa.webex.com</contactEmail>
</bodyContent>
</body>
</serv:message>

DelContacts- svar:

Slettede to eksisterende kontakter fra min kontaktliste

<?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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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>

Hvis de angivne e-mails ikke er på min kontaktliste

<?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>OPSTÅ</serv:result>
            <serv:reason>Beklager, der blev ikke fundet nogen post</serv:reason>
            <serv:gsbStatus>VIGTIGSTE</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Kendte problemer

Ingen

XML API 11.0.0-SP11 opdateringer

Ny API LstTrainingPollResultsHistory

Anmodningen er kun for T32/XML API11.0.0.

LstTrainingPollResultsHistory API blev oprindeligt implementeret i URL-adressen API. Efter kundens anmodning er den nu implementeret i XML API.

Resultaterne af liste-menings målingen returneres ved at indtaste en Training Center sessionKey. API'EN kan anmodes af enten Training Center-session-ejeren eller en af webstedsadministrationen.


Der er en websteds valgmulighed, der skal aktiveres, før undervisnings resultaterne gemmes i Webex-DATABASEn:

Berørt XML API:

LstTrainingPollResultsHistory

Design

DB-tabelrelation for resultatet af menings målingen:

Skema

LstTrainingPollResultHistory- anmodning:

LstTrainingPollResultHistory- svar:

Eksempel på anmodning:

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

Eksempel på svar:

<?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>SENERE</serv:result>
            <serv:gsbStatus>VIGTIGSTE</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 menings måling 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>12/20/2017 16:54:48</history:startTime>
                    <history:endTime>12/20/2017 16:58:07</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>test spørgsmål 1 (flere valgmuligheder/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>returneres</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>returneres</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>test spørgsmål 2 (flere-choiec. flere 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 A</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>test svar B, test svar en</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, test svar C, test svar B, test svar en</history:pollResponse>
                                    <history:isCorrect>returneres</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>returneres</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>test spø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>12/20/2017 16:58:57</history:startTime>
                    <history:endTime>12/20/2017 17:02:39</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>undersøgelses spørgsmål 1 (flere-choiec/sinngle-svar)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>undersøgelsessvar 3</history:answerChoice>
                                <history:answerChoice>undersøgelsessvar 2</history:answerChoice>
                                <history:answerChoice>undersøgelsessvar 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øgelsessvar 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øgelsessvar 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øgelses spørgsmål 2 (flere-choiec/fler svar)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>undersøgelsessvar D</history:answerChoice>
                                <history:answerChoice>undersøgelse svar C</history:answerChoice>
                                <history:answerChoice>undersøgelsessvar B</history:answerChoice>
                                <history:answerChoice>undersøgelsessvar A</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>undersøgelsessvar 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øgelses spø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, eller mødet ikke hører til login-brugeren, eller fordi brugeren ikke er websteds administrator.

Eksempel på svar:

<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>OPSTÅ</serv:result>
            <serv:reason>Beklager, der blev ikke fundet nogen post</serv:reason>
            <serv:gsbStatus>VIGTIGSTE</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Kendte problemer

Ingen

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

Beskrivelse:

Anmodningen er kun for T32/XML API11.0.0.

Da de tilgængelige valgmuligheder under planlægning af en Training Center-session omfatter "Send video", har XML API nu tilføjet attendeeSendVideo- valgmuligheden til oprettelse, Get og set api'er til Training Center sessioner.

Påvirkede XML API'er:

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

Design

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

Skemaændringer

CreateTrainingSession- anmodning:

SetTrainingSession- anmodning:

GetTrainingSession- svar:

Kendte problemer

Ingen

Skift ConfName- størrelsesbegrænsning maks. 128 display tegn

Konference navnets streng ConfName er nu begrænset til maksimalt 128 display tegn. Denne ændring justeres med J2EE-startsidens begrænsning. 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 XML APIer

ConfName

Kendte problemer

Ingen

Undtagelsesmeddelelse ændret i API LstRecording

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

"999999 har overskredet det maksimale antal forespørgsler for tid på 28 dage".

Påvirkede XML APIer

LstRecording

Kendte problemer

Ingen

XML API 11.0.0-SP10 opdateringer

XML API 11,0-SP10-udgivelsen indeholder ingen skemaændringer.