Hvis du vil ha mer informasjon om XML API 41, kan du se Oversikten over oppdateringer til Cisco Webex Meetings API (API 41)

Denne artikkelen inneholder oppdateringer og endringer for månedlige SP-utgivelser for XML API.

Hvis du vil ha mer informasjon om XML API 40, kan du se Oversikten over oppdateringer til Cisco Webex Meetings API (API 40).

For oppdateringer for XML API 11 SP9 og tidligere, gå til Cisco DevNet.

Oppdateringer for XML API 39.11.0

Klikk her for å laste ned XML API 39.11-skjemaet.

LstSummaryUser kan spørre brukerkontoer etter tidspunktet for siste endring

Vi oppgraderer LstSummaryUser API-en for å la brukere spørre brukerkontoer basert på tidspunktet de sist ble endret. Tre nye elementer, modifiedDateStart, modifiedDateEnd og lastModifiedTime, har blitt lagt til i API-en.


Maksimum tidsområde for denne spørringen er 90 dager. Hvis du legger inn et tidsområde som er mer enn 90 dager, vises en feil: 999999 Maksimum datoområde er 90 dager for spørring om endringsdato.

Berørte API-er:

  • LstSummaryUser

LastSummaryUser Eksempel på forespørsel:

<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
  <securityContext>
    <siteName>Site_Name</siteName>
    <webExID>SiteAdmin</webExID>
    <password>Password</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 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:use="http://www.webex.com/schemas/2002/06/service/user">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>**5124***</use:userID>
                <use:webExId>***MR***</use:webExId>
                <use:firstName>***MR***</use:firstName>
                <use:lastName>***est***</use:lastName>
                <use:email>***est***@qa.webex.com</use:email>
                <use:userRoleType>HOST</use:userRoleType>
                <use:registrationDate>06/19/2016 22:13:06</use:registrationDate>
                <use:active>DEACTIVATED</use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:meetingTypes>
                    <use:meetingType>3</use:meetingType>
                    <use:meetingType>9</use:meetingType>
                    <use:meetingType>10</use:meetingType>
                    <use:meetingType>11</use:meetingType>
                    <use:meetingType>13</use:meetingType>
                    <use:meetingType>14</use:meetingType>
                    <use:meetingType>102</use:meetingType>
                </use:meetingTypes>
                <use:lastLoginTime>10/19/2019 23:13:14</use:lastLoginTime>
                <use:lastModifiedTime>11/11/2019 19:11:11</use:lastModifiedTime>
            </use:user>

Oppdateringer for XML API 39.10.0

Klikk her for å laste ned XML API 39.10-skjemaet.

GetSessionInfo og GetUserCard returnerer en CAPTCHA-kode ved bruk av anonym tilgang

Som en sikkerhetsoppdatering har vi forbedret GetSessionInfo og GetUserCard API-ene med responsbeskyttelse fra CAPTCHA-kode. Hvis programmene dine kaller på API-ene ved bruk av anonym tilgang, kan du forbedre programmet ditt ved å støtte inndata fra CAPTCHA-kode.

Berørte API-er:

  • GetSessionInfo

  • GetUserCard

Oppdateringer for CAPTCHA-sikkerhet og respons:

GetSessionInfo Svar uten 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>FAILURE</serv:result>
            <serv:reason>Corresponding Meeting not found</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

GetSessionInfo 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>FAILURE</serv:result>
            <serv:reason>Corresponding Meeting not found</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
            <serv:CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</serv:CAPTCHAID>
           <serv:CAPTCHAImage>
                iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA
                ...........
                maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu+ZUFb7SAAAAAElFTkSuQmCC
            </serv:CAPTCHAImage>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Hvis du mottar et CAPTCHA-svar og fortsetter å kalle på API-en, inkluder du CAPTCHAID og CAPTCHAWord i API-forespørselen din:

<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 Eksempel på svar på feil CAPTCHAID og CAPTCHAWord:

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

LstSummaryUser støtte for retur av URL-adresser for personlig rom

Vi har lagt til et nytt svarelement, personalMeetingRoomURL, til LstSummaryUser API-en.

LstSummaryUser Eksempel på svar:

Oppdateringer for XML API 39.9.0

Klikk her for å laste ned XML API 39.9-skjemaet.

Støtte for korte SIP URL-er for personlige møterom (PMR)

Støtte for det korte SIP URL-formatet for PMR-er påvirker GetSessionInfo, GetMeeting, GetUser og GetMe API-ene. Et nytt svarelement ved navn displayMeetingUrl ble lagt til i GetUser og GetMe API-ene, og finnes allerede i GetSessionInfo og GetMeeting. displayMeetingUrl returnerer en brukers PMR-URL.

Berørte API-er:

  • GetSessionInfo

  • GetMeeting

  • GetUser

  • GetMe

GetUser Eksempel på svar:

GetMe Eksempel på svar:

GetSessionInfo returnerer nødvendige elementer for anonym tilgang

Som et sikkerhetskrav kan kun nødvendige elementer nå returneres av GetSessionInfo for anonym tilgang.

GetSessionInfo Eksempel på svar:

<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>PUBLIC</ep:listStatus>
        <ep:registration>false</ep:registration>
        <ep:passwordReq>true</ep:passwordReq>
        <ep:registrationURL>https://sqdemo6.dmz.webex.com/ec3300/eventcenter/enroll/register.do?loadFlag=1&amp;reqFlag=1&amp;confId=123203663769372547&amp;siteurl=sqdemo6</ep:registrationURL>
        <ep:registrationURLForMobile>https://sqdemo6.dmz.webex.com/ec3300/eventcenter/enroll/mobileRegister.do?formId=0&amp;formType=0&amp;loadFlag=1&amp;from=mobileClient&amp;siteurl=sqdemo6&amp;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>false</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>true</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>false</ep:isPersonalMeetingRoom>
    <ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/e.php?MTID=m2399b241f12722ca325388495e845103</ep:meetingLink>
    <ep:sipURL>715952675@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>715952675@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
</serv:bodyContent>

Berørte API-er:

  • GetSessionInfo

Atferdsendring i planlegging av møter og hendelser

Alle planlagte møter er som standard videoenhetaktiverte møter. Når du planlegger et møte, men velger Ingen eller Andre for møtets lyd, planlegges imidlertid møtet som et ikke-videoenhetaktivert Webex-møte.

Berørte API-er:

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

Oppdateringer for XML API 39.8.0

Klikk her for å laste ned XML API 39.8-skjemaet.

LsttrainingattendeeHistory returnerer nå møtedeltakerens oppmerksomhet

Et nytt svarelement, attentionToDurationPercentage, ble lagt til i LsttrainingattendeeHistory API-en. LsttrainingattendeeHistory returnerer informasjon om møtedeltakerens oppmerksomhet. Elementet returneres i dette formatet:

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

Berørte API-er:

  • LsttrainingattendeeHistory

    • attentionToDurationPercentage

    • attentionToAttendancePercentage

LsttrainingattendeeHistory Eksempel på svar:

<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 nå lisensantall

Nye svarelementer ble gitt for å returnere forskjellige lisensantall i GetSite API-en.

Berørte API-er:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

GetSiteFT og SetSiteFT Redesign

API-ene GetSiteFT og SetSiteFT har fått ny utforming for å tillate dynamiske funksjonsbrytere.

Berørte API-er:

  • GetSiteFT

  • SetSiteFT

GetSite Eksempel på forespørsel:

<?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>{This is machine account access token}</accessToken>
        </securityContext>
    </header>
    <bodyContent xsi:type="java:com.webex.service.binding.site.GetSiteFT">
        <featureToggles>
            <name>SupportCrossLaunch</name>
            <name>RemoveCMRLicenseSA</name>
        </featureToggles>
    </bodyContent>
</body>
</serv:message>

GetSite 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:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteFTResponse">
            <ns1:featureToggles>
                <ns1:featureToggle>
                    <ns1:name>SupportCrossLaunch</ns1:name>
                    <ns1:value>false</ns1:value>
                </ns1:featureToggle>
                <ns1:featureToggle>
                    <ns1:name>RemoveCMRLicenseSA</ns1:name>
                    <ns1:value>false</ns1:value>
                </ns1:featureToggle>
            </ns1:featureToggles>
        </serv:bodyContent>
    </serv:body>
</serv:message>

SetSite Eksempel på forespørsel:

<?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>{This is machine account access token}</accessToken>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.site.SetSiteFT">
            <featureToggles>
                <featureToggle>
                    <name>SupportCrossLaunch</name>
                    <value>false</value>
                </featureToggle>
                <featureToggle>
                    <name>SupportPeopleInsight</name>
                    <value>true</value>
                </featureToggle>
            </featureToggles>
        </bodyContent>
    </body>
</serv:message>

SetSiteFT 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:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:setSiteFTResponse"/>
    </serv:body>
</serv:message>

Lengden på møtebeskrivelsen er nå begrenset til 2500 tegn

Følgende API-er har nå innholdslengden for møtebeskrivelseselementet begrenset til 2500 tegn:

Berørte API-er:

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

Dette er for å forhindre at Cisco Webex ikke kan behandle forespørselen. Hvis møtebeskrivelsen er på mer enn 2500 tegn, returneres en feilmelding.

Oppdateringer for XML API 39.5.0

Nytt element videoMeshInterclusters lagt til i SetSite og GetSite-skjemaer

Et nytt element, videoMeshInterclusters, ble lagt til i SetSite element. videoMeshInterclusters inneholder også tre underordnede elementer videoMeshHomeCluster1, videoMeshHomeCluster2 og videoMeshHomeCluster3.

Berørte API-er:

  • SetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

SetSite Forespørsel om oppdateringer:

GetSite Svaroppdateringer:

Oppdateringer for XML API 39.3.0

Kort SIP URL i XML API, nytt element displayMeetingUrl

Klikk her for å laste ned XML API 39.3-skjemaet.

For øyeblikket, når du blir med i et Webex-møte, må appen eller enheten oppgi nettstedsinformasjon, hvilket gjør det vanskelig å bli med på møter noen ganger. Dette er spesielt sant når du ringer fra en SIP-enhet, fordi brukeren må angi meeting_number@sitename.webex.com.

For å gjøre det enklere å delta i møter, fjernet vi kravet om å angi nettstedsnavnet fra møtets SIP URI: meeting_number@webex.com. For å beholde bakoverkompatibilitet, fungerer det gamle formatet på sipURL, og det nye formatet legges til det nye elementet displayMeetingUrl.

Berørte API-er:

  • GetMeeting

    • displayMeetingUrl

  • GetEvent

    • displayMeetingUrl

  • GetSessionInfo

    • displayMeetingUrl

GetMeeting Eksempel på svar:

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

GetEvent Eksempel på svar:

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

GetSessionInfo Eksempel på svar:

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

Eksempel på e-post:

Beskrivelseslengden er nå begrenset til 1024 tegn

Følgende API-er har nå begrenset beskrivelseselementets innhold til 1024 tegn:

Berørte API-er:

  • CreateTrainingSession

  • SetTrainingSession

  • CreateEvent

  • SetEvent

Denne endringen er for å forhindre at Cisco Webex ikke kan behandle forespørselen. Hvis beskrivelsen er lengre enn 1024 tegn, returneres en feilmelding: «060067 ugyldig inndatabeskrivelse. Beskrivelsen kan ikke overskride maksimum antall tegn på 1024 tegn.»

Svareksempel for beskrivelseslengde på mer enn 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>FAILURE</serv:result>
            <serv:reason>
Illegal input description. The description can't exceed the maximum display characters's length 1024
            </serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>060067</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

GetSessionInfo returnerer nå kun grunnleggende informasjon for personlige rom når det er en anonym bruker av API

For å sikre bedre sikkerhet, reduserer vi mengden informasjon som returneres av GetSessionInfo når en anonym deltaker bruker API-en. I denne oppdateringen vil vi redusere følgende elementer i API-svaret:

Berørte 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>

Svarsammenligninger:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:isLocked>false</ep:isLocked>
    <ep:sessionkey>712419789</ep:sessionkey>
    <ep:confID>120396209273701973</ep:confID>
    <ep:accessControl>
        <ep:sessionPassword></ep:sessionPassword>   <!--Removed-->
        <ep:listStatus>UNLISTED</ep:listStatus>
        <ep:registration>false</ep:registration>
        <ep:passwordReq>false</ep:passwordReq>
        <ep:isEnforceAudioPassword>false</ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin>false</ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Simon Test's Personal Room</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType>MeetingCenter</ep:serviceType>
        <ep:isRecurring>false</ep:isRecurring>
        <ep:agendaFormat>TEXT</ep:agendaFormat>
        <ep:descriptionFormat>TEXT</ep:descriptionFormat>
        <ep:isException>false</ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException>false</ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>CALLBACK</ep:telephonySupport> <!--Removed-->
        <ep:globalCallInNumbersURL>https://sqdemo6.dmz.webex.com/sqdemo6/globalcallin.php?serviceType=MC&amp;ED=0</ep:globalCallInNumbersURL>   <!--Removed-->
        <ep:tollFreeRestrictionsURL>https://www.webex.com/pdf/tollfree_restrictions.pdf</ep:tollFreeRestrictionsURL>    <!--Removed-->
        <ep:dialInSequences>AutoDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[AttendeeID]#|SilentDialInSequence:[AccessNumber],,*01*[AccessCode]#[AttendeeID]#*01*|AutoLGDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[ProfileID]#,,,[PIN]#|SilentLGDialInSequence:[AccessNumber],,*01*[AccessCode]#[ProfileID]#[PIN]#*01*|AutoLGPWDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[ProfileID]#,,,[PIN]#,,,[Password]#|SilentLGPWDialInSequence:[AccessNumber],,*01*[AccessCode]#[ProfileID]#[PIN]#[Password]#*01*</ep:dialInSequences>  <!--Removed-->
        <ep:callInNum>    <!--Removed-->
            <serv:tollNum>14085452910</serv:tollNum>    <!--Removed-->
            <serv:globalNum>  <!--Removed-->
                <serv:countryAlias>14085452912</serv:countryAlias>  <!--Removed-->
                <serv:phoneNumber>14085452912</serv:phoneNumber>    <!--Removed-->
                <serv:tollFree>false</serv:tollFree>    <!--Removed-->
                <serv:default>false</serv:default>  <!--Removed-->
            </serv:globalNum> <!--Removed-->
        </ep:callInNum>   <!--Removed-->
        <ep:labels>   <!--Removed-->
            <ep:tollFreeCallInLabel>Call-in toll-free number (US/Canada)</ep:tollFreeCallInLabel>   <!--Removed-->
            <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->
        </ep:labels>  <!--Removed-->
        <ep:isMPAudio>false</ep:isMPAudio>  <!--Removed-->
        <ep:voip>true</ep:voip> <!--Removed-->
        <ep:enableTSP>false</ep:enableTSP>  <!--Removed-->
    </ep:telephony>   <!--Removed-->
    <ep:host>
        <ep:firstName>Simon</ep:firstName>
        <ep:lastName>Test</ep:lastName>
        <ep:email>simon0@qa.webex.com</ep:email>
        <ep:webExId>Simon</ep:webExId>
        <ep:allowAnyoneHostMeeting>false</ep:allowAnyoneHostMeeting>
    </ep:host>
    <ep:schedule>
        <ep:startDate>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>false</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly>false</ep:isAudioOnly>
    <ep:telePresence>false</ep:telePresence>
    <ep:isAlternateHost>false</ep:isAlternateHost>  <!--Removed-->
    <ep:isCreator>true</ep:isCreator>   <!--Removed-->
    <ep:hostKey>954462</ep:hostKey> <!--Removed-->
    <ep:supportE2E>false</ep:supportE2E>    <!--Removed-->
    <ep:isAllowJBH>false</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>true</ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
    <ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed</ep:meetingLink>
    <ep:sipURL>simon0@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>simon0@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
    <ep:isAutoRecord>false</ep:isAutoRecord>
</serv:bodyContent>

Oppdateringer for XML API 39.2.0

Nytt element lastLoginTime returnert i LstSummaryUser svar

Et nytt svarelement, lastLoginTime, ble lagt til i LstSummaryUser API-en. lastLoginTime returnerer klokkeslett for siste pålogging for hver bruker. Elementet returneres i dette formatet:

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

Berørte API-er:

  • LstSummaryUser

    • lastLoginTime

LstSummaryUser 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:use="http://www.webex.com/schemas/2002/06/service/user">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>3469487</use:userID>
                <use:objectGUID>a14e3312-e1d1-4e41-82b9-6ddac80c9f9a</use:objectGUID>
                <use:webExId>sangeetha.swaminathan@gmail.com</use:webExId>
                <use:firstName>Sangee</use:firstName>
                <use:lastName>Gmail</use:lastName>
                <use:email>sangeetha.swaminathan@gmail.com</use:email>
                <use:userRoleType>HOST</use:userRoleType>
                <use:registrationDate>12/11/2018 14:41:27</use:registrationDate>
                <use:active>DEACTIVATED</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>

Oppdateringer for XML API 39.1.0

Klikk her for å laste ned XML API 39.1.0-skjemaet.

Nytt element apiVer lagt til i GetAPIVersion API

Et nytt svarelement, apiVer, ble lagt til i GetAPIVersion API-en. Med denne oppdateringen endres navnekonvensjonen for XML API-versjonsnavn slik at det samsvarer med et enhetlig versjonsnummer med andre Cisco Webex-produktområder. apiVer returnerer den nye versjonsinformasjonen, for eksempel 39.1.0 for oppdateringen fra januar 2019.

Berørte API-er:

  • GetAPIVersion

    • apiVer

Elementet apiVersion vil bli avskrevet 1. mai 2019, og elementet release vil bli tildelt en ny XML API-verdi den 1. mai 2019.

GetAPIVersion 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: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>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ep:getAPIVersionResponse">
            <ep:apiVersion>WebEx XML API V11.0.0</ep:apiVersion>
            <ep:release>SP22</ep:release>
            <ep:apiVer>39.1.0</ep:apiVer>
        </serv:bodyContent>
    </serv:body>
</serv:message>

HQ og HD-parametere fjernet fra XML API

HQ og HD-videoegenskaper bestemmes nå på områdenivå i stedet for brukernivå. De to alternativene for disse parameterne ignoreres når du sender forespørsler fra følgende API-er:

  • CreateMeeting

  • SetMeeting

  • CreateTrainingSession

  • SetTrainingSession

API-ene GetMeeting og GetTrainingSession API-er returnerer fremdeles de to alternativene (bestemt på områdenivå og brukernivå), for å unngå å bryte eksisterende kode.

Nytt element uploadLogFileUrl lagt til i nettstedets metadata returnert til skrivebordsappen

Et nytt element uploadLogFileUrl ble lagt til i svaret som er returnert til skrivebordsappen når den kaller på getSite API i XML API-serveren. Skrivebordsappen kan laste opp loggfilen til uploadLogFileUrl.

Berørte API-er:

  • GetSite

    • uploadLogFileUrl

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

XML API 11.0.0 SP22-oppdateringer

Filstørrelsesbegrensning for UploadPMRImage

Ved opplasting av avatarer med API-en UploadPMRImage, er det en ny begrensning på filstørrelsen til 5 MB. Forsøk på å laste opp filer større enn dette vil nå motta en feilmelding: « 010100 Size of the image being uploaded is too big. Try an image smaller than 5MB in size. «

XML API 11.0.0 SP21-oppdateringer

Klikk her for å laste ned XML API 11.0 SP21-skjemaet.

Nytt element autoRecord lagt til i CreateMeeting, SetMeeting, GetMeeting og LstMeeting

Et nytt element med navnet autoRecord ble lagt til i CreateMeeting, SetMeeting, GetMeeting og LstMeeting API-ene. autoRecord lar brukere automatisk ta opp Webex-møter direkte fra møteplanleggeren. Dette gir detaljnivå for møtet, der den forrige metoden for automatisk opptak av møter kun kunne nås globalt på områdenivå.


API-ene autoRecord-elementet gjelder kun for Webex Meetings. Det gjelder ikke for Webex Events eller Webex Training.

Berørte API-er:

  • CreateMeeting

    • autoRecord

  • SetMeeting

    • autoRecord

  • GetMeeting

    • autoRecord

  • LstMeeting

    • autoRecord

CreateMeeting Oppdateringer:

autoRecord Innstilling

Adferd når Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er deaktivert på nettstedsadministrasjon

True

Begynn opptak automatisk når møtet begynner

False(Standard) eller ikke noe element

Starter ikke opptak automatisk når møtet begynner

Hvis Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er aktivert, ignoreres elementet, og opptaket starter automatisk når møtet starter.

SetMeeting Oppdateringer:

autoRecord Innstilling

Adferd når Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er deaktivert på nettstedsadministrasjon

True

Begynn opptak automatisk når møtet begynner

False(Standard) eller ikke noe element

Starter ikke opptak automatisk når møtet begynner

Hvis Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er aktivert, ignoreres elementet, og opptaket starter automatisk når møtet starter.

GetMeeting Oppdateringer:

autoRecord Innstilling

Adferd når Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er deaktivert på nettstedsadministrasjon

True

Begynn opptak automatisk når møtet begynner

False

Starter ikke opptak automatisk når møtet begynner

Hvis Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er aktivert, ignoreres elementet, og opptaket starter automatisk når møtet starter.

GetMeeting Eksempel på svar:

LstMeeting Oppdateringer:

autoRecord Innstilling

Adferd når Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er deaktivert på nettstedsadministrasjon

True

Begynn opptak automatisk når møtet begynner

False

Starter ikke opptak automatisk når møtet begynner

Hvis Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er aktivert, ignoreres elementet, og opptaket starter automatisk når møtet starter.

LstMeeting Eksempel på svar:

Nytt element isAutoRecord lagt til i GetSessionInfo API

Sammen med endringene som gjøres i de ovennevnte API-ene, ble et nytt element, isAutoRecord, ble lagt til i GetSessionInfo API-en. Dette elementet kan brukes til å indikere om opptak starter automatisk når et møte starter.

Berørte API-er:

  • GetSessionInfo

    • isAutoRecord

GetSessionInfo Oppdateringer:

isAutoRecord Innstilling

Adferd når Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er deaktivert på nettstedsadministrasjon

True

Begynn opptak automatisk når møtet begynner

False

Starter ikke opptak automatisk når møtet begynner

Hvis Automatisk opptak av alle økter ved bruk av nettverksbasert opptak er aktivert, ignoreres elementet, og opptaket starter automatisk når møtet starter.

GetSessionInfo Eksempel på svar:

XML API 11.0.0 SP20-oppdateringer

Klikk her for å laste ned XML API 11.0 SP20-skjemaet.

Nytt element returnShareToMeRecording lagt til i LstRecording API-forespørsel


Denne endringen ble tidligere kunngjort i XML API 11.0 SP17, men brukes i denne oppdateringen.

Et nytt element, returnShareToMeRecording, ble lagt til i LstRecording API-en. returnShareToMeRecording er en boolsk i forespørselen om LstRecording.

Dette nye elementet ble lagt til for å støtte å finn opptak fra deltaker eller invitert person. returnShareToMeRecording er et flagg for å la LstRecording API-en vite at den må returnere opptaket fra deltaker eller invitert person.

Når returnShareToMeRecording er angitt til True, LstRecording returnerer opptaksbrukeren som eier, og returnerer også opptaksbrukeren som deltaker eller invitert person delt av eieren.


Hvis flaggene for både automatisk deling og manuell deling er OFF, LstRecording returneres brukeren kun som eier av opptakene.

Når returnShareToMeRecording er angitt til False, eller dette elementet er ikke inkludert i forespørselen, LstRecording følger samme logikk som før: den returnerer bruker av opptaket som eier.

Berørte API-er:

  • LstRecording

    • returnShareToMeRecording

LstRecording Oppdateringer:

Element shareToMe lagt til i LstRecording API-svar


Denne endringen ble tidligere kunngjort i XML API 11.0 SP17, men brukes i denne oppdateringen.

Et nytt element, shareToMe, ble lagt til i LstRecording API-en. shareToMe er en boolsk verdi i svaret for LstRecording.

Dette nye elementet ble lagt til for å støtte å finn opptak fra deltaker eller invitert person. shareToMe er et flagg for å definere om brukeren er eieren av eller en deltaker for gjeldende opptak.

Når shareToMe er True, er brukeren ikke eieren av gjeldende opptak. Brukeren kan være en deltaker, eller opptaket deles av eieren.

Når shareToMe er False, eller dette elementet er ikke i svaret, LstRecording følger samme logikk som før: brukeren er eieren av det gjeldende opptaket.

Berørte API-er:

  • LstRecording

    • shareToMe

LstRecording Oppdateringer:

returnShareToMeRecording og shareToMe Eksempler på forespørsel:

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

returnShareToMeRecording og shareToMe Eksempler på svar:

Nye elementer lagt til i GetEvent API

Fire nye elementer ble lagt til i GetEvent API:

  • isCETMeeting: en boolsk sann/usann verdi som angir om Webex-hendelsen støtter Webex-videoplattform 2 (CMR 4.0)

  • sipURL: URL-en som brukes til å bli med i Webex-videomøter fra et videokonferansesystem eller -program

  • standaloneDialingIPAddress: IP-adressen som kan brukes til å ringe til Webex-videomøtet fra et videokonferansesystem eller -program

  • panelistNumericPassword: passordet for å bli med i Webex-videomøtet fra et videokonferansesystem eller -program

Hvis nettstedet støtter Webex-video, har verten videorettigheter for Webex Events, og hendelsen støtter Webex-videoplattform 2 (CMR 4.0), GetEvent returnerer disse elementene. Ellers returnerer GetEvent dem ikke.

Berørte API-er:

  • GetEvent

    • isCETMeeting

    • sipURL

    • standaloneDialingIPAddress

    • panelistNumericPassword

Nytt element panelistNumericPassword lagt til i GetSessionInfo API

GetSessionInfo har et nytt element, panelistNumericPassword, som inneholder passordet for å bli med i Webex-videomøtet fra et videokonferansesystem eller -program.

Hvis nettstedet støtter Webex-video, har verten videorettigheter for Webex Events, og hendelsen støtter Webex-videoplattform 2 (CMR 4.0), GetSessionInfo returnerer disse fire elementene:

  • isCETMeeting: en boolsk sann/usann verdi som angir om Webex-hendelsen støtter Webex-videoplattform 2 (CMR 4.0)

  • sipURL: URL-en som brukes til å bli med i Webex-videomøter fra et videokonferansesystem eller -program

  • standaloneDialingIPAddress: IP-adressen som kan brukes til å ringe til Webex-videomøtet fra et videokonferansesystem eller -program

  • panelistNumericPassword: passordet for å bli med i Webex-videomøtet fra et videokonferansesystem eller -program


For Webex Meetings eksisterte disse elementene allerede i GetSessionInfo:

  • isCETMeeting

  • sipURL

  • standaloneDialingIPAddress

Berørte API-er:

  • GetSessionInfo

    • panelistNumericPassword

Skjemaendringer gjort i GetEvent og GetSessionInfo

GetEvent Oppdateringer:

GetSessionInfo Oppdateringer:

XML API 11.0.0 SP18-oppdateringer

Klikk her for å laste ned XML API 11.0 SP18-skjemaet.

Nytt element EnableCloudTelepresence lagt til i getSite API

Et nytt element, EnableCloudTelepresence ble lagt til i getSite API-en.

Når alternativet EnableCETForAllUsers er aktivert, kontrollerer Webex for å se om brukeren støtter Webex-video (CMR). Det returnerer nå også et nytt element EnableCloudTelepresence i getSite API-en.

Berørte API-er:

  • getSite

  • EnableCloudTelepresence

getSite Eksempel på svar:

XML API 11.0.0 SP17-oppdateringer

Nytt element returnShareToMeRecording lagt til i LstRecording API-forespørsel

Et nytt element, returnShareToMeRecording, ble lagt til i LstRecording API-en. returnShareToMeRecording er en boolsk i forespørselen om LstRecording.

Dette nye elementet ble lagt til for å støtte å henting av opptak fra deltaker eller invitert person. returnShareToMeRecording er et flagg for å la LstRecording API-en vite at den må returnere opptaket fra deltaker eller invitert person.

Når returnShareToMeRecording er angitt til True, LstRecording returnerer brukeren som eier opptakene, og returnerer også opptaksbrukeren som deltaker eller invitert person delt av eieren.


Hvis flaggene for automatisk deling og manuell deling er deaktivert, returnerer LstRecording kun brukeren som eieren av opptakene.

Når returnShareToMeRecording er angitt til False, eller dette elementet er ikke inkludert i forespørselen, LstRecording følger samme logikk som før: den returnerer bruker av opptaket som eier.

Berørte API-er:

  • LstRecording

  • returnShareToMeRecording

LstRecording Oppdateringer:

Nytt element shareToMe lagt til i LstRecording API-svar

Et nytt element, shareToMe, ble lagt til i LstRecording API-en. shareToMe er en boolsk verdi i svaret for LstRecording.

Dette nye elementet ble lagt til for å støtte å henting av opptak fra deltaker eller invitert person. shareToMe er et flagg for å definere om brukeren er eieren, eller de er deltakeren eller invitert person for nåværende opptak.

Når shareToMe er True, er brukeren ikke eieren av det gjeldende opptaket. Brukeren kan være en deltaker eller invitert person, eller opptaket deles av eieren.

Når shareToMe er False, eller dette elementet er ikke i svaret, LstRecording følger samme logikk som før: brukeren er eieren av det gjeldende opptaket.

Berørte API-er:

  • LstRecording

  • shareToMe

LstRecording Oppdateringer:

Nye elementer for deltakerkapasitet lagt til i API getSite Respons

Fire nye elementer ble lagt til i getSite API for å indikere deltakerkapasiteten for følgende Webex-tjenester:

attendeeCapacityForMC- Webex Meetings

attendeeCapacityForEC – Webex Events

attendeeCapacityForTC – Webex Training

attendeeCapacityForSC – Webex Support

Disse returnerte verdiene angir maksimalt antall deltakere som møtet, arrangementet eller økten kan ha. De er underordnet CISiteLicenseInfo-elementet i responsen.

Berørte API-er:

  • getSite

  • attendeeCapacityForMC

  • attendeeCapacityForEC

  • attendeeCapacityForTC

  • attendeeCapacityForSC

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

XML API 11.0.0 SP16-oppdateringer

Ny API hostStreamURL lagt til i lstRecordingResponse

Elementet hostStreamURL ble lagt til i LstRecording svar som en del av opptaksdetaljene. hostStreamURL returnerer en URL som verten kan bruke til å vise opptaket uten å måtte logge på først. Denne URL-en er gyldig i 30 minutter etter at den er generert.

Berørte API-er:

  • hostStreamURL

hostStreamURL Eksempel på svar:

<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-en bruker ny WebDB-modellering til å returnere data

Etter kundeforespørsel, GetSite henter API-en nå mer presis vertslisens, bruksrapporteringsdata og andre data ved bruk av den nye WebDB-modelleringen for CI-nettsteder.

Berørte API-er:

  • GetSite

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

GetSite Eksempel på svar for EE-områder:

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

XML API 11.0.0 SP15-oppdateringer

Returner møtekoblingen for Webex Meetings ved bruk av GetSessionsInfo API

Skjemaet for GetSessionInfo API-en har en ny svarverdi, meetingLink. Du kan bruke en møtekobling for å starte et Webex-møte som vert eller ved å bli med i et Webex-møte som deltaker.

Berørte API-er:

  • GetSessionInfo

  • meetingLink

GetSessionInfo Eksempel på svar:

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

Ny betingelse for spørring av RecordingID på LstRecording API

Du kan nå bruke LstRecording for å spørre om opptak ved bruk av recordingID. Det finnes to typer opptaks-ID-er:

  • Opptaks-ID-er for Webex Meetings, Webex Events og Webex Training

  • ID for NBR-opptak, for diverse opptak

Hvis det finnes et serviceType-element i XML-forespørselen, returnerer LstRecording kun et tjenesteopptak (Webex Meetings, Webex Events og Webex Training).

Hvis det ikke er et serviceType-element i XML-forespørselen, returnerer LstRecording returneres kun et NBR-opptak.

Berørte API-er:

  • LstRecording

  • RecordingID

LstRecording Eksempler på svar:

Eksempel på forespørsel for en tjenesteopptaks-ID:

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

Eksempel på forespørsel for en NBR-opptaks-ID:

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

XML API 11.0.0 SP14-oppdateringer

Sammendragsrapporter om foreløpig bruk av Meeting Center

To nye API-er er lagt til for foreløpige rapporter om Meeting Center, LstmeetingusagePreliminaryHistory og LstmeetingattendeePreliminaryHistory. Disse vil ha samme atferd som LsteventsessionPreliminaryHistory og LsteventattendeePreliminaryHistory i den endelige rapporten.

Berørte API-er:

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

LstmeetingusagePreliminaryHistory Eksempel på forespørsel:

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

LstmeetingusagePreliminaryHistory 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>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingusagePreliminaryHistoryResponse">
            <history:meetingUsagePreliminaryHistory>
                <history:confID>93115261364733685</history:confID>
                <history:sessionKey>800150023</history:sessionKey>
                <history:confName>200804231215</history:confName>
                <history:openTime>04/23/2018 19:16:34</history:openTime>
                <history:timeZoneID>4</history:timeZoneID>
                <history:meetingType>PRO</history:meetingType>
                <history:timeZoneWithDST>San Francisco (Pacific Daylight Time, 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 Eksempel på forespørsel:

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

LstmeetingattendeePreliminaryHistory 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>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingattendeePreliminaryHistoryResponse">
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:company>XYZ</history:company>
                <history:title>DJ</history:title>
                <history:phoneNumber>1,222,654-3210,,,,</history:phoneNumber>
                <history:address1>1 Any Street</history:address1>
                <history:address2>xyz</history:address2>
                <history:city>SanJose</history:city>
                <history:state>CA</history:state>
                <history:country>USA</history:country>
                <history:zipCode>95111</history:zipCode>
                <history:name>user test2</history:name>
                <history:email>ut2@qa.webex.com</history:email>
                <history:joinTime>04/23/2018 19:13:06</history:joinTime>
                <history:participantType>ATTENDEE</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>ATTENDEE</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name>test host</history:name>
                <history:email>testuser@webex.com</history:email>
                <history:joinTime>04/23/2018 19:12:42</history:joinTime>
                <history:participantType>ATTENDEE</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>

Returnerer SIP URL og Skype-URL fra GLA GetsessionInfo API

To nye elementer, <sipURL> og <skypeURL>, ble føyd til i svaret når du kaller opp GLA GetSessionInfo API-en. Disse elementene er basiselementer som kan returneres for anonym tilgang.

  • <sipURL> kan brukes til å delta i møter fra en TelePresence eller annen Cisco-videoenhet. På denne måten kan kun møter som bruker Cisco-videoplattformer med versjon 1.0 eller 2.0 få GetSessionInfo til å returnere <sipURL> element.

  • <skypeURL> kan brukes til å delta i møter fra en Microsoft Skype-app, uten begrensninger eller betingelser, slik at den kan returneres for hver samtale.

Berørte API-er:

  • GetSessionInfo

Eksempel på svar:

Returnerer SIP URL og møtekobling fra GetMeeting API

Tre nye elementer, <isCETMeeting>, <meetingLink> og <sipURL>, ble føyd til i svaret da du kalle opp GetMeeting API-en.

  • <isCETMeeting> returnerer om møtet bruker en Cisco-videoplattform (støtter TelePresence og video).

  • <meetingLink> kan brukes til å koble til møter.

  • <sipURL> kan brukes til å delta i møter fra en TelePresence eller annen Cisco-videoenhet. På denne måten skal kun møter som bruker Cisco-videoplattformer med versjon 1.0 eller 2.0 GetMeeting returnere elementet.

Berørte API-er:

  • GetMeeting

GetMeeting Eksempel på svar:

XML API 11.0.0 SP13-oppdateringer

Kunngjøring om avvikling av <siteID>-elementet i overordnet <securityContext>

Cisco planlegger å avvikle <siteID> element i overordnet <securityContext> elementet, og bytte det ut med <siteName>. På grunn av et stort antall <siteID> elementer som ofte endres i løpet av områdemigrering, pådrar organisasjoner seg høye vedlikeholdskostnader for å fortsette å bruke dette elementet. Dette er et forhåndsvarsel på to år.

  • Innvirkningen vil oppstå 1. mai 2020 for eksisterende WebEx-kunder.

  • Nye kunder må bruke <siteName> element fra 1. mai 2018.

  • Kunder som gjør integreringer med CI, Spark eller Atlas-systemet, må bruke <siteName> element fra 1. mai 2018.

Berørte API-er:

  • <siteName>

  • <securityContext>

Datavalidering av <tollCallInData> og <tollFreeCallInData> Elementene

Fra 1. juni 2018 vil både <tollCallInData> og <tollFreeCallInData> API-ene bli datavalidert. Dette påvirker <CreateUser> og <SetUser> API-ene.

Områder som bruker ikke-gyldige strenger eller feilformaterte strenger i innringingsdata, må korrigere strengene for at disse elementene skal bestå datavalidering.

Nedenfor finner du eksempler på CreateUser og SetUser, tollCallInData og tollFreeCallInData i riktig 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>false</createOnBridge>
        <defaultFlag>false</defaultFlag>
    </tspAccount>
</tspAccount>
...

XML API 11.0.0 SP12-oppdateringer

To nye API-er SetContact og DelContacts

XML API-skjemaet hadde tidligere kun de to API-ene CreateContacts og LstContacts, som ikke ga fullstendig administrasjon av brukerkontakter. For å gi bedre funksjonalitet for å administrere brukerkontakt ved bruk av XML API, har vi lagt til disse to nye API-ene, SetContact og DelContacts.

API

Merknader

SetContact

Kall opp denne API-en for å endre kontaktinformasjon som e-post, navn, tittel og språk.

Unntak:

  • Hvis kontakten ikke blir funnet av contactEmail-elementet, returneres unntaket 140004 «Kontakt ikke funnet»

  • Hvis Webex-nettstedet ikke støtter et bestemt språk, returneres unntaket 030060 «Ikke et gyldig språk»

  • Hvis den nye e-postadressen som brukeren ønsker å endre til, er et duplikat av en annen kontakt i listen Mine kontakter, returneres unntaket 140001 «E-postadresse brukes av en annen kontakt»

DelContacts

Kall på denne API-en for å slette én eller flere kontakter fra listen Mine kontakter basert på angitte e-postadresser.

contactID returneres dersom den angitte e-postadressen blir funnet i listen Mine kontakter, og ignorerer den angitte e-postadressen hvis den ikke er i listen Mine kontakter.

Hvis alle angitte e-postadresser ikke finnes i listen Mine kontakter, returneres unntaket 00015 (Beklager, ingen oppføring funnet).

Berørte API-er:

  • SetContact

  • DelContacts

SetContact Eksempel på forespørsel:

<?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>Contact Email adress</contactEmail>
           <contact>
                <name>New Contact Name</name>
                <email>New Contact Email Address</email>
                <title>New Title</title>
                <company>New Company</company>
                <notes>New Notes</notes>
                <url>New Link</url>
                <phones>
                    <phone>1,,408######,,,,</phone>
                    <mobilePhone>1,,408######,,,,</mobilePhone>
                    <fax>1,,408######,,,,</fax>
                </phones>
                <address>
                    <address1>New Address 1</address1>
                    <address2>New Address 2</address2>
                    <city>New City</city>
                    <state>New State</state>
                    <zipCode>New ZipCode</zipCode>
                    <country>New Company</country>
                </address>
                <language>New Language</language>
            </contact>
</bodyContent>
</body>
</serv:message>

SetContact Eksempel på svar:

<?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>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="ep:setContactResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
    </serv:body>
</serv:message>

DelContacts Eksempel på forespørsel:

<?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 Eksempler på svar:


I dette eksempelet slettes to eksisterende kontakter fra listen Mine kontakter.

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

I dette eksempelet finnes ikke e-postadressene i listen Mine kontakter.

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>Sorry, no record found</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

XML API 11.0.0 SP11-oppdateringer

Ny API LstTrainingPollResultsHistory

API-ene LstTrainingPollResultsHistory API-en ble opprinnelig implementert i URL API-en. Etter forespørsel fra kundene, er den nå implementert i XML API.

Resultater av listeavstemninger returneres ved å legge inn et Training Center sessionKey. API-en kan forespørres enten av eieren av Training Center-økten eller en nettstedsadministrator.


Innstillingen Forbedret TC-avstemning må aktiveres før resultater av opplæringsavstemninger lagres i WebEx DB:

Berørte API-er:

  • LstTrainingPollResultsHistory

LstTrainingPollResultHistory Eksempel på forespørsel:

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

Forespørselen gjelder kun for T32/XML API 11.0.0.

LstTrainingPollResultHistory 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>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="history:lstTrainingPollResultsHistoryResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <history:matchingRecords>
                <serv:total>2</serv:total>
                <serv:returned>2</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
            <history:sessionInfo>
                <history:sessionKey>81901776767288734</history:sessionKey>
                <history:confName>TC poll test 20171220 1635</history:confName>
                <history:host>John Doe</history:host>
            </history:sessionInfo>
            <history:polls>
                <history:poll>
                    <history:pollDesc>Test</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>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 question 1 (multi-choice/single-answer)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test answer 4</history:answerChoice>
                                <history:answerChoice>test answer 3</history:answerChoice>
                                <history:answerChoice correct="true">test answer 2</history:answerChoice>
                                <history:answerChoice>test answer 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 answer 2</history:pollResponse>
                                    <history:isCorrect>true</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>test answer 1</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>test question 2 (multi-choiec.multi-answer)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test answer D</history:answerChoice>
                                <history:answerChoice>test answer C</history:answerChoice>
                                <history:answerChoice correct="true">test answer B</history:answerChoice>
                                <history:answerChoice correct="true">test answer 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 answer B,test answer A</history:pollResponse>
                                    <history:isCorrect>true</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>test answer D,test answer C,test answer B,test answer A</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>test question 2 (short answer)</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>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
                <history:poll>
                    <history:pollDesc>Survey</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>survey question 1 (multi-choiec/sinngle-answer)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>survey answer 3</history:answerChoice>
                                <history:answerChoice>survey answer 2</history:answerChoice>
                                <history:answerChoice>survey answer 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>survey answer 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>survey answer 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>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>survey question 2 (multi-choiec/multi-answer)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>survey answer D</history:answerChoice>
                                <history:answerChoice>survey answer C</history:answerChoice>
                                <history:answerChoice>survey answer B</history:answerChoice>
                                <history:answerChoice>survey answer 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>survey answer D,survey answer 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>survey answer C,survey answer 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>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>survey question 3 (short answer)</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>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
            </history:polls>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Svaret er annerledes hvis møtet ikke ble funnet, ikke tilhører brukeren som ber om det, eller hvis brukeren som ber om det ikke også er nettstedsadministrator.

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>FAILURE</serv:result>
            <serv:reason>Sorry, no record found</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Ny attendeeSendVideo alternativet i API-ene CreateTrainingSession, SetTrainingSession og GetTrainingSession

Fordi alternativene som er tilgjengelige ved planlegging av en Training Center-økt inkluderer Send video, har XML API nå lagt til attendeeSendVideo alternativet for å opprette, motta og angi API-er for Training Center-økter.

Berørte API-er:

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

Design

Alternativet ble lagret i DB-tabellen WbxMMConfParam/paramvalue som paramname = 'optionSupportSendVideo'

CreateTrainingSession Forespørsel om oppdateringer:

SetTrainingSession Forespørsel om oppdateringer:


Forespørselen gjelder kun for T32/XML API11.0.0.

GetTrainingSession Svaroppdateringer:

Endre ConfName størrelsesgrense maksimum til 128 visningstegn

Strengen for konferansenavn ConfName er nå begrenset til maksimalt 128 visningstegn. Denne endringen samsvarer med begrensningen på J2EE-startsiden. Dersom en API-forespørsel inkluderer ConfName som er tom eller overskrider en visningslengde på 128 tegn, vises følgende feilmelding:

«060065 Ulovlig inndata for konferansenavn. Konferansenavnet kan ikke være tomt eller overskride maksimum antall visningstegn på 128.»

Berørte API-er:

  • ConfName

Unntaksmelding endret i API LstRecording

Unntaksmeldingen som sendes når tidsområdet for spørring overskrider maksimumsgrensen for API-en LstRecording ble endret. Som standard støtter spørringer fire uker med opptak. Forespørsler på mer enn fire uker mottar følgende feilmelding:

«999999 overskrider maksimum tidsområde for spørring på 28 dager».

Berørte API-er:

  • LstRecording

XML API 11.0.0 SP10-oppdateringer

XML API 11.0 SP10-oppdateringen har ingen skjemaendringer.