Za več informacij o XML API 41 glejte Pregled posodobitev API-ja za sestanke Cisco Webex (API 41)

Za več informacij o XML API 39 in XML API 11 glejte Pregled posodobitev API-ja za Cisco Webex Meetings XML (XML API 39 in starejše).

Za posodobitve za XML API 11 SP9 in starejše pojdite na Cisco DevNet.

Posodobitve API-ja 40.12.0

Posodobitve XML API 40.12.0

Kliknite tukaj za prenos sheme XML API 40.12.0

XML API podpira vrsto zasebnega srečanja

API-ji XML

  • Uporabimo lahko API: CreateMeeting in SetMeeting za načrtovanje ali posodobitev sestanka Webex z vrsto zasebnega sestanka.

  • Če je sestanek Webex načrtovan z vrsto zasebnega sestanka, GetSessionInfo GetMeeting, LstSummarySession, in LstCalendarSession vrne novo poimenovanje elementa PrivateMeeting vedeti to.

  • GetMeetingType in LstMeetingType vrne novo poimenovanje elementa SupportPrivateMeeting ki označuje, ali podpira zasebne sestanke ali ne.

Spremembe sheme

XML API: GetMeetingType/LstMeetingType: Pripnite <SupportPrivateMeeting> element.

XML API: LstSummarySession: pripnite <isPrivateMeeting> element.

XML API: LstCalendarSession: pripnite <isPrivateMeeting> element.

XML API: GetSessionInfo: pripnite <isPrivateMeeting> element.

XML API: GetMeeting: Pripnite <isPrivateMeeting> element.

Zahteva XML API: CreateMeeting

Zahteva CreateMeeting z vrsto zasebnega sestanka

<body>
    <bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
        <schedule>
            <startDate>10/25/2020 13:00:00</startDate>
            <duration>45</duration>
            <timeZoneID>45</timeZoneID>
        </schedule>
        <accessControl>
            <meetingPassword>********</meetingPassword>
        </accessControl>
        <metaData>
            <confName>MC_PrivateMeeting_Test</confName>
            <meetingType>168</meetingType>      //169 is a sample which supports Private Meeting
        </metaData>
    </bodyContent>
</body>

Odziv API-ja XML: GetSessionInfo

Odgovor za isPrivateMeeting

<ep:supportE2E>false</ep:supportE2E>
<ep:isAllowJBH>true</ep:isAllowJBH>
<ep:isPrivateMeeting>true</ep:isPrivateMeeting>     //true: the meeting supports Private Meeting; false: the meeting does not support Private Meeting.
<ep:isCETMeeting>false</ep:isCETMeeting>
<ep:isPersonalMeetingRoom>false</ep:isPersonalMeetingRoom>
<ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>

GetSite API bo vrnil predloge sestankov na ravni spletnega mesta

Uporabniška zgodba/opis naloge

GetSite API za vrnitev predloge sestanka na ravni spletnega mesta. To bo omogočilo izobraževalnemu povezovalniku in učilnicam Webex, da prikažeta te predloge za učitelje, da izberejo in izberejo te predloge med razporejanjem svojih spletnih sej.

Prizadeti API-ji

Če obstajajo prilagojene predloge sestankov na ravni spletnega mesta, bo API GetSite vrnil te predloge na ravni spletnega mesta.

Ime elementov

Opis

meetingTemplateName

ime prilagojenih predlog sestankov na ravni spletnega mesta

serviceType

Sestanki Webex, usposabljanja Webex in dogodki Webex

Spremembe sheme

GetSite : pripnite <meetingTemplates> element.

Vzorec odgovora

GetSite Response

<ns1:meetingTypes>
    <ns1:meetingTypeID>3</ns1:meetingTypeID>
    <ns1:meetingTypeName>PRO</ns1:meetingTypeName>
</ns1:meetingTypes>
<ns1:meetingTemplates>
    <ns1:meetingTemplate>
        <ns1:meetingTemplateName>MC Meeting Tempalte 1</ns1:meetingTemplateName>
        <ns1:serviceType>MeetingCenter</ns1:serviceType>
    </ns1:meetingTemplate>
    <ns1:meetingTemplate>
        <ns1:meetingTemplateName>EC Meeting Tempalte 2</ns1:meetingTemplateName>
        <ns1:serviceType>EventCenter</ns1:serviceType>
    </ns1:meetingTemplate>
    <ns1:meetingTemplate>
        <ns1:meetingTemplateName>TC Meeting Template 3</ns1:meetingTemplateName>
        <ns1:serviceType>TrainingCenter</ns1:serviceType>
    </ns1:meetingTemplate>
</ns1:meetingTemplates>

XML API SetUser ne more spremeniti elementa supportedServices ko je spletno mesto enotno mesto CI

Opis

XMLAPI SetUser ne podpirajo spremembe vrednosti " supportedServices" v zahtevi API-ja, ko je spletno mesto spletno mesto Unified Webex Meeting, povezano s kontrolnim središčem.

Spremembe sheme

V API-ju ni sprememb sheme: SetUser.

WEBEX-15436: Dodajte zaščito, da preprečite podvojena e-poštna sporočila Mtgconfattendeelist

Opis

Če je istemu sestanku v isti zahtevi API dodanih več udeležencev z istim e-poštnim naslovom, obdelamo samo prvega udeleženca z e-poštnim naslovom.

Prizadeti API-ji

  • CreateMeetingAttendee

  • CreateUser

  • SetUser

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

Vzorec API-ja

Prošnja

<?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>testSite</siteName>
            <webExID>testUser</webExID>
            <password>password</password>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
            <sessionKey>1714904382</sessionKey>
            <person>
                <email>test@webex.com</email>
                <name>name1</name>
            </person>
            <attendees>
                <person>
                    <email>test@webex.com</email>
                    <name>name2</name>
                </person>
                <sessionKey>1714904382</sessionKey>
            </attendees>
        </bodyContent>
    </body>
</serv:message>

Posodobitve API-ja 40.11.0

Posodobitve XML API 40.11.0

Kliknite tukaj za prenos sheme XML API 40.11.0

XMLAPI CreateUser podpira prikazno ime

CreateUser podpira dispalyname ko preklopite funkcijo EnableDisplayName je kot 1. Če preklop funkcije ni 1, potem je displayName bo prezrt.

Spremembe sheme

CreateUser:

XMLAPI SetUser podpira prikazno ime

SetUser podpira dispalyname ko preklopite funkcijo EnableDisplayName je 1. Če preklop funkcije ni 1, je displayName bo prezrt.

Spremembe sheme

SetUser:

XMLAPI GetUser podpira prikazno ime

GetUser podpira dispalyname ko preklopite funkcijo EnableDisplayName je 1. Če preklop funkcije ni 1, je displayName ne bo prikazan.

Kdaj displayName v DB je nič in funkcija preklopi EnableDisplayName je 1, displayName bo firstName+" "+lastName za neazijske znake in firstName+lastName za azijske like.

Spremembe sheme

GetUserResponse:

Nadzor uporabniške ravni XMLAPI za CMR Hybrid Voip

The cmrHybridVoip nastavitev se uporablja za nastavitev in pridobitev nastavitve ravni uporabnika za EnableCMRHybridVoIP.

Spremembe sheme

GetUser Response:

CreateUser Request:

SetUser Request:

Posodobitve API-ja 40.10.0

Posodobitve XML API 40.10.0

Kliknite tukaj za prenos sheme XML API 40.10.0

XML API support for meeting UUID v zahtevi in odgovoru API-ja

Vzorec API-ja XML: GetSessionInfo Prošnja:

<?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">
<header>
  <securityContext>
      <siteName>xxx</siteName>
      <webExID>Test</webExID>
      <password>xxx</password>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
    <sessionKey>805325231</sessionKey>
    or
    <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

odgovor:

<?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: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:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:isLocked>false</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID>
            ...
            ...
        </serv:bodyContent>
    </serv:body>
</serv:message>

Prizadeti API:

  • CreateMeetingAttendee

  • DelMeetingAttendee

  • RegisterMeetingAttendee

  • CreateTeleconferenceSession

  • SetTeleconferenceSession

  • GetTeleconferenceSession

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

  • DelTrainingSession

  • CreateEvent

  • SetEvent

  • DelEvent

XMLAPI bo vrnil dodaten element za konfiguracijo skrbnika mesta, da onemogoči zajem zaslona

Zahteva prihaja iz varnosti - oboje PenTest napake in stranke, kot je Goldman Sachs. Končnim uporabnikom ne želijo dovoliti, da posnamejo zaslon v aplikaciji Meetings. Medtem pa veliko drugih strank želi to funkcijo - omogočiti zajem zaslona. Tudi uporabniki Education želijo dovoliti tudi zajem zaslona. Za to bomo imeli konfiguracijo skrbnika mesta, XMLAPI pa bo vrnil dodatno polje EnableMobileScreenCapture v odgovoru GetSite podpirati to.

Vzorec zahteve GetSite

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <header>
      <securityContext>
         <siteName>xxxx</siteName>
         <webExID>Test</webExID>
         <password>xxxx</password>
      </securityContext>
   </header>
   <body>
      <bodyContent xsi:type="java:com.webex.service.binding.site.GetSite" />
   </body>
</serv:message>

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns: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:securityOptions>
                    ...
                    ...
                    <ns1:EnableMobileScreenCapture>false</ns1:EnableMobileScreenCapture>
                    ...
                </ns1:securityOptions>
                ...
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Prizadeti API

GetSite

XMLAPI podpira MEET-269 Izboljšanje pridružitve brez PIN-a

XMLAPI dodaj NOVO MOŽNOST Videokonferenčni sistemi v moji organizaciji lahko začnejo sestanke in se jim pridružijo brez pozivov za srečanje v osebni sobi in srečanje MC.

  • createUser/setUser/getUser dodajte novo vozlišče deviceCanStartMyPMR v personalMeetingRoom.

  • createMeeting/setMeeting/getMeeting dodajte novo vozlišče deviceCanStartMeeting v urniku.

Možnost v uporabniškem vmesniku Webex za sestanek v osebni sobi:

Spremembe sheme

CreateUser:

SetUser:

getUserResponse:

CreateMeeting:

setMeeting:

getMeetingResponse:

Posodobitve API-ja 40.9.0

Posodobitve XML API 40.9.0

Kliknite tukaj za prenos sheme XML API 40.9.0

XML API support for meeting UUID zahteva in odgovor

Zahtevi in odgovoru API-ja smo dodali UUID srečanja povsod, kjer podpiramo kot meetingKey oz sessionKey.

Vzorec API-ja XML: GetSessionInfo Prošnja:

<?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">
<header>
  <securityContext>
      <siteName>xxx</siteName>
      <webExID>Test</webExID>
      <password>xxx</password>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
    <sessionKey>805325231</sessionKey>
    or
    <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

odgovor:

<?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: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:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:isLocked>false</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID>
            ...
            ...
        </serv:bodyContent>
    </serv:body>
</serv:message>

Prizadeti API:

  • GetEnrollmentInfo

  • LstsummaryTrainingSession

  • AddScheduledTest

  • SetScheduledTest

  • DelScheduledTest

  • GetTestInformation

  • UploadEventImage

  • SendInvitationEmail

  • CreateSupportSession

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

  • LsteventsessionPreliminaryHistory

  • LsteventattendeePreliminaryHistory

  • LstTrainingPollResultsHistory

Sestanki Webex bodo imeli zaklenjeno preddverje za sestanke, kjer lahko uporabniki počakajo, da jih sprejmejo na sestanek

XML API urnik in urejanje srečanja MC za podporo zaklenjenega preddverja, ko funkcija ( ConsistentLockedLobby) vklopite.

Spremembe sheme

Dodani trije novi elementi ( externalAttendeeSecurity, autoLock, autoLockWaitTime) v CreateMeeting, SetMeeting in GetMeeting API-ji.

Element

Opis

externalAttendeeSecurity

Ko je srečanje odklenjeno, so na voljo trije elementi varnosti zunanjega uporabnika.

AllowJoin: Sestanku se lahko pridruži takoj;

AllowJoinWithLobby: Sestanku se lahko pridruži le, če ga gostitelj dovoli;

BlockFromJoin: ne morem se pridružiti sestanku;

autoLock

Samodejno zaklepanje sestanka.

Prav: Samodejno zakleni sestanek po # minutah po začetku sestanka

False: Ne zaklene samodejno sestanka po začetku sestanka

autoLockWaitTime

minute (0,5,10,15,20) za samodejno zaklepanje sestanka po začetku sestanka

Vzorec zahteve in odgovora

Request of CreateMeeting:

<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
    ...
    <attendeeOptions>
        ...
        <joinRequiresAccount>false</joinRequiresAccount>
        <externalAttendeeSecurity>AllowJoinWithLobby</externalAttendeeSecurity>
        <autoLock>true</autoLock>
        <autoLockWaitTime>10</autoLockWaitTime>
    </attendeeOptions>
    ...
   </bodyContent>
</body>
</serv:message>

Request of SetMeeting:

<bodyContent xsi:type="java:com.webex.service.binding.meeting.SetMeeting">
    <meetingkey>2###1###01</meetingkey>
    ...
    <attendeeOptions>
        ...
        <joinRequiresAccount>false</joinRequiresAccount>
        <externalAttendeeSecurity>AllowJoinWithLobby</externalAttendeeSecurity>
        <autoLock>true</autoLock>
        <autoLockWaitTime>10</autoLockWaitTime>
    </attendeeOptions>
    ...
   </bodyContent>
</body>
</serv:message>

Odziv od GetMeeting:

<?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:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="meet:getMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            ...
            <meet:attendeeOptions>
                ...
                <meet:joinRequiresAccount>false</meet:joinRequiresAccount>
                <meet:externalAttendeeSecurity>AllowJoin</meet:externalAttendeeSecurity>
                <meet:autoLock>true</meet:autoLock>
                <meet:autoLockWaitTime>10</meet:autoLockWaitTime>
            </meet:attendeeOptions>
            ...
   </bodyContent>
</body>
</serv:message>

Prizadeti API:

  • CreateMeeting

  • SetMeeting

  • GetMeeting

Izboljšanje GetSessionInfo API za vrnitev statusa udeležencev v seji v teku

Dodana dva nova elementa ( hasHostInMeeting, hasAttendeeInMeeting) v odgovor GetSessionInfo. Ta dva elementa bosta vrnjena, ko je sestanek sestanek v teku.

Element

Opis

hasHostInMeeting

Ali se je gostitelj pridružil sestanku v teku.

Prav: Gostitelj je na sestanku v teku.

False/Null: Gostitelj ni na sestanku v teku ali sestanek ni sestanek v teku.

hasAttendeeInMeeting

Ali se je sestanku v teku pridružil udeleženec/gostitelj.

Prav: na srečanju v teku je udeleženec ali gostitelj.

False/Null: na sestanku v teku ni nobenega udeleženca ali gostitelja ali pa sestanek ni sestanek v teku.

Vzorec odgovora API-ja:

<?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:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="meet:getMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            ...

             <ep:status>INPROGRESS</ep:status>


             <ep:hasHostInMeeting>true</ep:hasHostInMeeting>

             <ep:hasAttendeeInMeeting>true</ep:hasAttendeeInMeeting>

            ...
   </bodyContent>
</body>
</serv:message>

Prizadeti API:

GetSessionInfo

API GetUserCard zahteva avtorizacijo.

Izboljšanje varnosti XML API GetUserCard zahteva avtorizacijo za pridobitev podatkov o uporabniku.

Prizadeti API:

GetUserCard

Posodobitve API-ja 40.8.0

Posodobitve XML API 40.8.0

Kliknite tukaj za prenos sheme XML API 40.8.0

GetSessionInfo izboljšanje odziva

Če niste povabljeni ali odobreni s sestanka, vaš klic v XML API: GetSessionInfo ne bo vrnil elementov: confName, startDate, duration, timeZone, meetingLink, sipURL, displayMeetingUrl v telesu odgovora API-ja.

Primer odziva API-ja za sestanke:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:sessionkey>1####2###4</ep:sessionkey>
    <ep:accessControl>
        <ep:listStatus>UNLISTED</ep:listStatus>
        <ep:registration>false</ep:registration>
        <ep:passwordReq>true</ep:passwordReq>
        <ep:isRegisterIDRequired>false</ep:isRegisterIDRequired>
    </ep:accessControl>
    <ep:metaData>
        <ep:serviceType>MeetingCenter</ep:serviceType>
    </ep:metaData>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>false</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>true</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>false</ep:isPersonalMeetingRoom>
</serv:bodyContent>

Primer odziva API za usposabljanja/dogodke:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:sessionkey>1####5###9</ep:sessionkey>
    <ep:accessControl>
        <ep:listStatus>UNLISTED</ep:listStatus>
        <ep:registration>true</ep:registration>
        <ep:registrationURL>https://sitename.webex.com/tc3300/trainingcenter/register/registerSession.do?siteurl=sitename&amp;confID=16###92######61</ep:registrationURL>
        <ep:passwordReq>true</ep:passwordReq>
        <ep:registrationURLForMobile>https://sitename.webex.com/tc3300/trainingcenter/meeting/sessionInfoMobile.do?siteurl=sitename&amp;confID=16###92######61</ep:registrationURLForMobile>
        <ep:joinStatus>INVITE/REGISTER/REJECT</ep:joinStatus>
        <ep:isRegisterIDRequired>false</ep:isRegisterIDRequired>
    </ep:accessControl>
    <ep:metaData>
        <ep:serviceType>TrainingCenter</ep:serviceType>
    </ep:metaData>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>false</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>true</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>false</ep:isPersonalMeetingRoom>
</serv:bodyContent>

Prizadeti API:

  • GetSessionInfo

GetSessionInfo, GetUserCard Varnostne izboljšave

Izvedli smo varnostno izboljšavo API-ja XML GetSessionInfo in GetUserCard. Uporabnikom bomo v naslednjih dveh urah blokirali dostop do teh dveh API-jev, če je njihov klic dosegel omejitev v eni uri brez napak, najdenih podatkov.

Odgovor o stanju napake je: "403 Prepovedano"

Prizadeti API-ji:

  • GetSessionInfo

  • GetUserCard

meetingUUID v podpori za zahteve in odzive API-ja

Zahtevi in odgovoru API-ja smo dodali meetingUUID povsod, kjer podpiramo a meetingKey/sessionKey.

GetSessionInfo Prošnja:

<?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">
<header>
  <securityContext>
      <siteName>xxx</siteName>
      <webExID>Test</webExID>
      <password>xxx</password>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
    <sessionKey>805325231</sessionKey>
    or
    <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

odgovor:

<?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: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:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:isLocked>false</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID>
            ...
            ...
        </serv:bodyContent>
    </serv:body>
</serv:message>

Prizadeti API:

  • LstOpenSession

  • GetEnrollmentInfo

  • LstsummaryMeeting

  • LstScheduledTests

  • GetEvent

  • LstsummaryEvent

  • LstmeetingusageHistory

  • LsttrainingsessionHistory

  • LsteventsessionHistory

  • LstsupportsessionHistory

  • DelSession

Predloga izobraževalnih spletnih mest (vrsta seje EDU) v podpori za XML API

Ko vaša spletna mesta omogočijo vrsto seje izobraževalnega inštruktorja (EDU), lahko API XML podpira načrtovanje sestanka s predlogo sestanka EDU.

Prizadeti API:

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

XML API CreateMeetingAttendee in RegisterMeetingAttendee podpora

Oboje CreateMeetingAttendee in RegisterMeetingAttendee lahko preverijo zahtevani obrazec za registracijo udeležencev za registracijo Webex Meetings.

Za to nalogo obstaja nova izjema:

Številka izjeme

Sporočilo o izjemi

040014

Manjkajo obvezna polja (obrazec za registracijo): ...

Če ste na primer izbrali »Job Title« in »Company Name« kot zahtevani polji za registracijo udeleženca Webex Meetings, kot je prikazano spodaj, potem morate pri klicanju dveh API-jev navesti vrednost za »Job Title« in »Company Name«. : CreateMeetingAttendee in RegisterMeetingAttendee.

RegisterMeetingAttendee Prošnja:

<body>        
        <bodyContent xsi:type="java:com.webex.service.binding.attendee.RegisterMeetingAttendee">
            <attendees>
                <person>
                    <name>FirstNameb LastName</name>
                    <firstName>FirstNameb</firstName>
                    <lastName>LastName</lastName>
                    <title>Engineer</title>             //Job Title
                    <company>Cisco1234</company>        //Company Name
                    ...
                    <email>****@*****.com</email>              
                    <type>VISITOR</type>
                    <sendReminder>true</sendReminder>
                </person>
                <role>ATTENDEE</role>
                <joinStatus>ACCEPT</joinStatus>
                <emailInvitations>true</emailInvitations>
                <sessionKey>1####4####1</sessionKey>
            </attendees>
        </bodyContent>  
    </body>
</serv:message>

CreateMeetingAttendee Prošnja:

<bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
        <person>
            <name>FirstNameA LastNameA</name>
            <firstName>FirstNameA</firstName>
            <lastName>LastNameA</lastName>
            <title>Engineer</title>         //Job Title
            <company>Cisco1234</company>    //Company Name
            ...
            <email>*****@*****.com</email>
            <type>VISITOR</type>
            <sendReminder>true</sendReminder>
        </person>
    <role>ATTENDEE</role>
    <joinStatus>ACCEPT</joinStatus>
    <emailInvitations>true</emailInvitations>
    <sessionKey>1###4####1</sessionKey>

040014 Exception of Response primer:


<?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:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>FAILURE</serv:result>
            <serv:reason>Missing required fields (registration form) : title,company</serv:reason>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
            <serv:exceptionID>040014</serv:exceptionID>
            <serv:value>title,company</serv:value>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Prizadeti API:

  • CreateMeetingAttendee

  • RegisterMeetingAttendee

Izboljšave preverjanja veljavnosti e-pošte XML API

API XML ne bi smel dovoljevati presledkov v e-pošti, zato smo izboljšali preverjanje e-pošte, da se uskladimo z vedenjem strani Webex Meetings.

Prizadeti API:

  • CreateMeetingAttendee

  • CreateEvent

  • SetEvent

  • CreateContact

  • SetContact

  • SetRecordingInfo

  • CreateMeetingAttendee

  • CreateTrainingSession

  • SetTrainingSession

  • CreateUser

  • SetUser

  • CreateMeeting

  • SetMeeting

  • RegisterMeetingAttendee

Posodobitve API-ja 40.7.0

Posodobitve XML API 40.7.0

Kliknite tukaj za prenos sheme XML API 40.7.0

meetingUUID podpora

Dodali smo meetingUUID na zahtevo API in odgovor, kjerkoli podpiramo meetingKey ali sessionKey.

GetSessionInfo Primer zahteve:

<?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">
<header>
  <securityContext>
      <siteName>xxx</siteName>
      <webExID>Test</webExID>
      <password>xxx</password>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
    <sessionKey>805325231</sessionKey>
    or
    <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

GetSessionInfo Primer zahteve:

<?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">
<header>
  <securityContext>
      <siteName>xxx</siteName>
      <webExID>Test</webExID>
      <password>xxx</password>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
    <sessionKey>805325231</sessionKey>
    or
    <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

GetSessionInfo Primer odgovora:

<?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: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:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:isLocked>false</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID>
            ...
            ...
        </serv:bodyContent>
    </serv:body>
</serv:message>

Prizadeti API-ji:

  • LstmeetingattendeeHistory

  • LsttrainingattendeeHistory

  • LsteventattendeeHistory

  • LstsupportattendeeHistory

CreateUser API dobrodošla e-poštna podpora za štiri nove jezike

Pozdravna html e-pošta XMLAPI podpira naslednje štiri nove jezike:

  • češčina (languageID=19)

  • poljščina (languageID=20)

  • madžarščina (languageID=21)

  • romunščina (languageID=22)

XMLAPI pošlje pozdravno e-pošto glede na jezik ali ID jezika v CreateUser prošnja.

Uporaba CreateUser za pošiljanje pozdravnega e-poštnega sporočila Html Primer (češčina):

<?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">
    <header>
        <securityContext>
            <siteName>xxx</siteName>
            <webExID>Test</webExID>
            <password>xxx</password>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
            <bodyContent xsi:type="java:com.webex.service.binding.user.CreateUser">
                <firstName>test</firstName>
                <lastName>user</lastName>
                <webExId>testuser</webExId>
                <password>xxxxxx</password>
                <email>testuser@test.com</email>
                <privilege>
                    <host>true</host>
                </privilege>
                <languageID>19</languageID>
                or
                <language>Czech</language>
                <active>ACTIVATED</active>
                <sendWelcome>true</sendWelcome>
                <isHTMLEmail>true</isHTMLEmail>
            </bodyContent>
        </bodyContent>
    </body>
</serv:message>

API 40.6.1, 40.4.9 posodobitve

XML API 40.6.1, 40.4.9 posodobitve

Kliknite tukaj za prenos sheme XML API 40.6.1

Kliknite tukaj za prenos sheme XML API 40.4.9

CreateMeeting/SetMeeting podpora

Ko načrtujete sestanek Webex, XML API CreateMeeting/SetMeeting vam omogoča, da označite ali počistite ali kliknete zahtevano ali neobvezno polje v obrazcu za registracijo udeleženca.

Sledi vzorec razporeda sestankov z uporabniške spletne strani, kjer lahko preverite zahtevana polja, kot je npr "Naziv delovnega mesta", "Ime podjetja", "Mesto", in "Država" na obrazcu za prijavo udeležencev:

Sledi preslikava med polji strani in elementi XML API-ja:

Polja strani Element XMLAPI
Naziv delovnega mesta 
<title>
ime podjetja 
<company>
Naslov 1 
<address1>
naslov 2 
<address2>
Mesto 
<city>
Država 
<state>
Poštna številka 
<postalCode>
Država/regija 
<country>
Delovni telefon 
<phone>
faks 
<fax>

Spremenjena shema: Dodajte element "registrationForm" v CreateMeeting

Spremenjena shema: Dodajte element "registrationForm" v SetMeeting

Spremenjena shema: Dodajte element "registrationForm" v GetMeeting

CreateMeetingPrimer zahteve:

<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
      <accessControl>
          <meetingPassword>password</meetingPassword>
      </accessControl>    
      <attendeeOptions>
          <emailInvitations>true</emailInvitations>
          <registration>true</registration>
          <auto>false</auto>
      </attendeeOptions>      
      <registrationForm>
          <title><req>true</req></title>          <!-- true -->
          <company><req>true</req></company>      <!-- true -->
          <address1><req>false</req></address1>
          <address2><req>false</req></address2>
          <city><req>true</req></city>            <!-- true -->
          <state><req>true</req></state>          <!-- true -->
          <postalCode><req>false</req></postalCode>
          <country><req>false</req></country>
          <phone><req>false</req></phone>
          <fax><req>false</req></fax>
      </registrationForm>

SetMeetingPrimer zahteve:

<bodyContent xsi:type="java:com.webex.service.binding.meeting.SetMeeting">
    <meetingkey>1015045339</meetingkey>

    <metaData>
        <confName>Conference Name</confName>
        <meetingType>3</meetingType>
    </metaData>
    
    <attendeeOptions>
        <emailInvitations>true</emailInvitations>
        <registration>true</registration>
        <auto>true</auto>
    </attendeeOptions>
    
    <registrationForm>
        <title><req>true</req></title>    
        <company><req>true</req></company>    
        <address1><req>false</req></address1>
        <address2><req>false</req></address2>
        <city><req>true</req></city>          
        <state><req>true</req></state>        
        <postalCode><req>false</req></postalCode>
        <country><req>false</req></country>
        <phone><req>false</req></phone>
        <fax><req>false</req></fax>
    </registrationForm>

GetMeetingPrimer odgovora:

            <meet:sipURL>1234567890@sitename.webex.com</meet:sipURL>
            <meet:displayMeetingUrl>1234567890@sitename.webex.com</meet:displayMeetingUrl>
            <meet:registrationForm>
                <meet:phone><meet:req>false</meet:req></meet:phone>
                <meet:title><meet:req>true</meet:req></meet:title>        
                <meet:company><meet:req>true</meet:req></meet:company>    
                <meet:address1><meet:req>false</meet:req></meet:address1>
                <meet:address2><meet:req>false</meet:req></meet:address2>
                <meet:city><meet:req>true</meet:req></meet:city>          
                <meet:state><meet:req>true</meet:req></meet:state>        
                <meet:postalCode><meet:req>false</meet:req></meet:postalCode>
                <meet:country><meet:req>false</meet:req></meet:country>
                <meet:fax><meet:req>false</meet:req></meet:fax>
            </meet:registrationForm>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Prizadeti API-ji:

  • CreateMeeting

  • SetMeeting

  • GetMeeting

  • DelMeeting

Vrsta srečanja E2EE ne podpira srečanja PMR

Ko omogočite PMR med klicem z API-ji: CreateUser/SetUser/GetUser/GetMe in je na voljo samo vrsta srečanja E2EE, se bo odzval na naslednje sporočilo o napaki: "110063 Uporabnik mora imeti vsaj eno vrsto srečanja, ki ni E2EE, da omogoči PMR."

Prizadeti API-ji:

  • CreateUser

  • SetUser

  • GetUser

  • GetMe

Posodobitve API-ja 40.6.0

Posodobitve XML API 40.6.0

Kliknite tukaj za prenos sheme XML API 40.6.0

Dodana je vloga za upravljanje uporabnikov

Ustvarili smo vlogo za upravljanje uporabnikov in datoteka sheme za naslednje se je spremenila.

Spremenjena shema: CreateUserprošnja:

Spremenjena shema: SetUser

Spremenjena shema: GetMeodgovor:

Spremenjena shema: LstsummaryUserodgovor:

Prizadeti API-ji:

  • CreateUser

  • SetUser

  • GetMe

  • LstsummaryUser

CreateUserPrimer zahteve:

<?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">
<header>
    <securityContext>
       <siteName>xxx</siteName>      
       <webExID>SiteAdmin</webExID>
       <password>xxxx</password>      
    </securityContext>  
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.CreateUser">
    <firstName>xxx</firstName>
    <lastName>xxx</lastName>
    <webExId>xxx</webExId>
    <password>xxx</password>
    <email>xxx</email>
    <privilege>
        <umSiteAdmin>true</umSiteAdmin>
        <host>false</host>

        <siteAdmin>false</siteAdmin>
        <labAdmin>false</labAdmin>
        <voiceOverIp>false</voiceOverIp>
    </privilege>
    <languageID>3</languageID>
    <active>ACTIVATED</active>
    <sendWelcome>true</sendWelcome>
    <isHTMLEmail>true</isHTMLEmail>
</bodyContent>  
</body>
</serv:message>

Podpora z uporabo ključa API dostop do GetUserCard

Zdaj podpiramo uporabo ključa API (generiranega žetona JWT) za dostop do API-ja: GetUserCard v tej izdaji.

Oglejte si te strani o uporabi enega ključa API in ustvarjanju žetona JWT:

Kako uporabiti en ključ API

Kako ustvariti žeton JWT

GetUserCardPrimer zahteve:

POST https://{sitename}.webex.com/WBXService/XMLService
Header:
    Content-Type application/json;charset=utf-8
    JWTToken ${jwttoken}
Body:  
<?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>{sitename}</siteName>
    </securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.user.GetUserCard">
        <webExId>{userName}</webExId>
    </bodyContent>
</body>
</message>  

Primer odgovora:

<?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:getUserCardResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:avatar>
                <use:url>https://xxxx.webex.com/svc3300/svccomponents/html/img/avatar160.png</use:url>
                <use:lastModifiedTime>1587493389768</use:lastModifiedTime>
                <use:isUploaded>false</use:isUploaded>
            </use:avatar>
            <use:personalMeetingRoom>
                <use:title>Test's Personal Room</use:title>
                <use:personalMeetingRoomURL>https://xxxx.webex.com/meet/Test</use:personalMeetingRoomURL>
                <use:accessCode>713289692</use:accessCode>
            </use:personalMeetingRoom>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Podpora za meetingUUID v zahtevi in odgovoru API-ja

Dodali smo meetingUUID na zahtevo API in odgovor, ko podpiramo meetingKey ali sessionKey.

Prizadeti API-ji:

  • LstRecording

  • LstsummarySession

  • GetSesssionInfo

  • GethosturlMeeting

  • GetjoinurlMeeting

  • LstMeetingAttendee

  • CreateMeeting

  • SetMeeting

  • GetMeeting

  • DelMeeting

  • LstCalendarSession

meetingUUIDPrimer zahteve:

<?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">
<header>
  <securityContext>
      <siteName>xxx</siteName>
      <webExID>Test</webExID>
      <password>xxx</password>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
    <sessionKey>805325231</sessionKey>
    or
    <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

meetingUUIDPrimer odgovora:

<?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: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:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:isLocked>false</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID>
            ...
            ...
        </serv:bodyContent>
    </serv:body>
</serv:message>

Ključi sestanka PMR ne bodo spremenjeni iz začasno deaktiviranega uporabnika ali onemogočenega PMR

Ko se začasno deaktiviran uporabnik ali onemogočen PMR ponovno aktivira v enem tednu, se zdaj ponovno aktivirani uporabnik ali omogočen ključ srečanja PMR ne spremeni, ampak bo enak kot prej.

Prizadeti API-ji:

  • SetUser

  • DelUser

LstSummarySession izboljšave

Izboljšali smo API: LstSummarySession vrni načrtovani PMR, da bo imel en nov element, returnScheduledPMR, v zahtevi. In privzeti preklop funkcije je izklopljen.

Prizadeti API-ji:

  • LstSummarySession

Sprememba sheme:

Dodamo novo ime elementa returnScheduledPMR v zahtevi API LstSummarySession.

Dodamo novo ime elementa isScheduledPMR v odzivu API LstSummarySession.

LstSummarySessionPrimer zahteve:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <header>
      <securityContext>
         <siteName>xxx</siteName>
         <webExID>Test</webExID>
         <password>xxx</password>
         <partnerID>xxxx</partnerID>
         <clientInfo>xxxx</clientInfo>
      </securityContext>
   </header>
   <body>
      <bodyContent xsi:type="java:com.webex.service.binding.ep.LstsummarySession">
         <listControl>
            <startFrom>1</startFrom>
            <maximumNum>2</maximumNum>
            <listMethod>AND</listMethod>
         </listControl>
         <dateScope>
            <startDateStart>11/01/2019 8:0:0</startDateStart>
            <startDateEnd>12/01/2019 7:59:59</startDateEnd>
            <timeZoneID>4</timeZoneID>
            <endDateStart>11/01/2019 8:0:0</endDateStart>
            <endDateEnd>12/01/2019 7:59:59</endDateEnd>
         </dateScope>
         <order>
            <orderBy>HOSTWEBEXID</orderBy>
            <orderAD>ASC</orderAD>
            <orderBy>CONFNAME</orderBy>
            <orderAD>ASC</orderAD>
            <orderBy>STARTTIME</orderBy>
            <orderAD>ASC</orderAD>
         </order>
         <serviceTypes>
            <serviceType>EventCenter</serviceType>
            <serviceType>MeetingCenter</serviceType>
            <serviceType>SalesCenter</serviceType>
            <serviceType>TrainingCenter</serviceType>
            <serviceType>SupportCenter</serviceType>
         </serviceTypes>
         <returnScheduledPMR>true</returnScheduledPMR>
      </bodyContent>
   </body>
</serv:message>

LstSummarySessionPrimer odgovora:

<?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: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:lstsummarySessionResponse">
         <ep:matchingRecords>
            <serv:total>1787</serv:total>
            <serv:returned>2</serv:returned>
            <serv:startFrom>1</serv:startFrom>
         </ep:matchingRecords>
         <ep:session>
            <ep:sessionKey>809914325</ep:sessionKey>          
            <ep:MeetingUUID>809914325</ep:MeetingUUID>
            <ep:confName>Team Meeting</ep:confName>
            <ep:sessionType>3</ep:sessionType>
            <ep:serviceType>MeetingCenter</ep:serviceType>
            <ep:hostWebExID>Test</ep:hostWebExID>
            <ep:hostFirstName>Test</ep:hostFirstName>
            <ep:hostLastName>Test</ep:hostLastName>
            <ep:otherHostWebExID>Test</ep:otherHostWebExID>
            <ep:timeZoneID>2</ep:timeZoneID>
            <ep:timeZone>GMT-10:00, Hawaii (Honolulu)</ep:timeZone>
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:startTime>10/12/2019 00:35:41</ep:startTime>
            <ep:duration>60</ep:duration>
            <ep:listStatus>PUBLIC</ep:listStatus>
            <ep:hostEmail>Test@webex.com</ep:hostEmail>
            <ep:passwordReq>true</ep:passwordReq>
            <ep:hostJoined>false</ep:hostJoined>
            <ep:participantsJoined>false</ep:participantsJoined>
            <ep:confID>141672157056861215</ep:confID>
            <ep:registration>false</ep:registration>
            <ep:isRecurring>true</ep:isRecurring>
            <ep:hostType>1019001</ep:hostType>
            <ep:isAudioOnly>false</ep:isAudioOnly>
            <ep:isTCSingleRecurrence>false</ep:isTCSingleRecurrence>
            <ep:isAllowJBH>false</ep:isAllowJBH>
            <ep:isCETMeeting>true</ep:isCETMeeting>
            <ep:isException>false</ep:isException>
            <ep:isNextUpcomingInstance>false</ep:isNextUpcomingInstance>
            <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
            <ep:recurrenceId>0</ep:recurrenceId>
            <ep:isScheduledPMR>true</ep:isScheduledPMR>
         </ep:session>
         <ep:session>
            <ep:sessionKey>805660167</ep:sessionKey>
            <ep:confName>xmlmc Molly08Console816960001</ep:confName>
            <ep:sessionType>3</ep:sessionType>
            <ep:serviceType>MeetingCenter</ep:serviceType>
            <ep:hostWebExID>Molly08Console81696000</ep:hostWebExID>
            <ep:hostFirstName>Molly08Console81696000</ep:hostFirstName>
            <ep:hostLastName>Molly08Console81696000</ep:hostLastName>
            <ep:otherHostWebExID>Molly08Console81696000</ep:otherHostWebExID>
            <ep:timeZoneID>2</ep:timeZoneID>
            <ep:timeZone>GMT-10:00, Hawaii (Honolulu)</ep:timeZone>
            <ep:status>NOT_INPROGRESS</ep:status>
            <ep:startTime>10/12/2019 00:35:41</ep:startTime>
            <ep:duration>60</ep:duration>
            <ep:listStatus>PUBLIC</ep:listStatus>
            <ep:hostEmail>Molly08Console81696000@webex.com</ep:hostEmail>
            <ep:passwordReq>true</ep:passwordReq>
            <ep:hostJoined>false</ep:hostJoined>
            <ep:participantsJoined>false</ep:participantsJoined>
            <ep:confID>141672108716459038</ep:confID>
            <ep:registration>false</ep:registration>
            <ep:isRecurring>true</ep:isRecurring>
            <ep:hostType>1019001</ep:hostType>
            <ep:isAudioOnly>false</ep:isAudioOnly>
            <ep:isTCSingleRecurrence>false</ep:isTCSingleRecurrence>
            <ep:isAllowJBH>false</ep:isAllowJBH>
            <ep:isCETMeeting>true</ep:isCETMeeting>
            <ep:isException>false</ep:isException>
            <ep:isNextUpcomingInstance>false</ep:isNextUpcomingInstance>
            <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
            <ep:recurrenceId>0</ep:recurrenceId>
            <ep:isScheduledPMR>true</ep:isScheduledPMR>
         </ep:session>
      </serv:bodyContent>
   </serv:body>
</serv:message>

GetSite izboljšave

Dodali smo a GetSite preklop odzivne funkcije SupportXMLAPIReturnScheduledPMR

Prizadeti API-ji:

  • GetSite

Sprememba sheme:

API XML GetSite odgovor nov element je: SupportXMLAPIReturnScheduledPMR

GetSitePrimer zahteve:

<?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">
<header>
  <securityContext>
   <siteName>xxx</siteName>
   <webExID>Test</webExID>
   <password>xxx</password>
   <clientInfo>xxx</clientInfo>
  </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.site.GetSite">
</bodyContent>    
</body>
</serv:message>

GetSitePrimer odgovora:

<?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:siteCommonOptions>
                    ...
                    <ns1:SupportXMLAPIReturnScheduledPMR>true</ns1:SupportXMLAPIReturnScheduledPMR>
                    ...
                </ns1:siteCommonOptions>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

API 40.4.8, 40.2.9 posodobitve

XML API 40.4.8, 40.2.9 posodobitve

Kliknite tukaj za prenos sheme XML API 40.4.8

Kliknite tukaj za prenos sheme XML API 40.2.9

Nov odgovor pri posodabljanju načrtovanih sestankov v XMLAPI

Ko stranke uporabijo XMLAPI za posodabljanje sestankov, načrtovanih prek njihove strani, bomo poslali številčno geslo v e-poštnem sporočilu o posodobitvi sestanka in ga uporabili za centre za sestanke, ekipe in dogodke Webex.

Ti API-ji: GetMeeting, GetTrainingSession, GetEvent in GetTeleconferenceSession, bo imel kot odgovor te nove elemente: audioPassword(številčno geslo), isEnforceAudioPassword, isEnforceAudioLogin za centre za sestanke, ekipe in dogodke Webex.

Spremenjena shema:

Prizadeti API-ji:

  • GetMeeting

  • GetTrainingSession

  • GetEvent

  • GetTeleconferenceSession

GetMeetingPrimer zahteve:

<?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>testSite</siteName>
    <webExID>test</webExID>
    <password>xxx</password>
    <partnerID>xx</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.GetMeeting">
    <meetingKey>803328224</meetingKey>
</bodyContent>
</body>
</serv:message>

Primer odgovora:

<?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:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="meet:getMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <meet:accessControl>
                <meet:listToPublic>false</meet:listToPublic>
                <meet:isPublic>false</meet:isPublic>
                <meet:meetingPassword>PkzC8tP7kM5</meet:meetingPassword>
                <meet:audioPassword>75928877</meet:audioPassword>
                <meet:isEnforceAudioPassword>true</meet:isEnforceAudioPassword>
                <meet:isEnforceAudioLogin>false</meet:isEnforceAudioLogin>
            </meet:accessControl>
            ...
            ...
        </serv:bodyContent>
    </serv:body>
</serv:message>

Posodobitve API-ja 40.4.5, 40.2.6

XML API 40.4.5, 40.2.6 Posodobitve

GetUserCard in GetSessionInfo omejitev uporabe

Izvajamo omejitev uporabe API-ja GetUserCard in GetSessionInfo, lahko dobite sporočilo o napaki: "403 prepovedano", če dosežete omejitev uporabe.

Prizadeti API-ji:

  • GetUserCard

  • GetSessionInfo

Posodobitve API-ja 40.4.4, 40.2.5

Posodobitve XML API 40.4.4, 40.2.5

BodyContent omejitev števila

Dodali smo omejeno število BodyContent v vsakem razdelku XML API. Ko dodate preveč BodyContent v zahtevi API-ja se vrneta naslednja koda napake in sporočilo: "000053 Število BodyContent v zahtevi mora biti manjše od {number}"

Prizadeti API-ji:

  • Kateri koli API XML

Zahteva XML API z več BodyContent primer:

<?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">
<header>
    <securityContext>
    <webExID>xxxx</webExID>
    <password>xxxx</password>
    <siteName>xxx</siteName>
    </securityContext>  
</header>
<body>

<bodyContent xsi:type="java:com.webex.service.binding.user.GetUser">
<webExId>xxx</webExId>
</bodyContent>

<bodyContent xsi:type="java:com.webex.service.binding.user.GetSite">
</bodyContent>

<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey>801020403</sessionKey>
</bodyContent>

</body>
</serv:message>

Posodobitve API-ja 40.4.3, 40.2.4

XML API 40.4.3, 40.2.4 posodobitve

Kliknite tukaj za prenos sheme XML API 40.4.3, 40.2.4.

CreateUser izboljšave

Izboljšali smo CreateUser za podporo pozdravnega e-poštnega sporočila v več jezikih. The CreateUser zdaj zahteva isHTMLEmail

Prizadeti API-ji:

  • CreateUser

CreateUser Primer zahteve:

<?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">
<header>
    <securityContext>
    <webExID>administrator</webExID>
    <password>xxxx</password>
    <siteName>xxx</siteName>
    </securityContext>  
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.CreateUser">
    <firstName>xxx</firstName>
    <lastName>xxx</lastName>
    <webExId>xxx</webExId>
    <password>xxx</password>
    <email>xxx</email>
    <privilege>
        <host>true</host>
        <siteAdmin>false</siteAdmin>
        <labAdmin>false</labAdmin>
        <voiceOverIp>false</voiceOverIp>
    </privilege>
    <languageID>3</languageID>
    <active>ACTIVATED</active>
    <sendWelcome>true</sendWelcome>
    <isHTMLEmail>true</isHTMLEmail>
</bodyContent>  
</body>
</serv:message>

Posodobitve API-ja 40.4.0

Posodobitve XML API 40.4.0

Uveljavi preverjanje e-pošte pri spreminjanju e-pošte v API-ju XML

Po omogočenem skrbniku spletnega mesta Za posodobitev e-poštnega naslova je potrebna potrditev uporabnika v administraciji spletnega mesta Webex:

  • Če račun, ki ni skrbnik mesta, pokliče SetUser API za spreminjanje e-poštnih naslovov, trenutni e-poštni naslov ostane, dokler se novi e-poštni naslov ne preveri. Potrditveno e-poštno sporočilo o spremembi računa je poslano na novi e-poštni naslov s »Potrditvijo spremembe računa Webex«. Ko kliknete povezavo v e-poštnem sporočilu za potrditev, se novi e-poštni naslov takoj poveže.


    Če pokliče neskrbnik mesta SetUser API večkrat brez ko končate postopek preverjanja e-pošte, se trenutni e-poštni naslov ohrani, zadnji novi e-poštni naslov pa je tisti, ki ga je treba preveriti.

  • Če skrbniški račun mesta pokliče SetUser API za spreminjanje e-poštnih naslovov, postopek preverjanja e-pošte se ne sproži. Nov e-poštni naslov bo takoj povezan z računom gostitelja ali udeleženca.

Prizadeti API-ji:

  • SetUser

GetEnrollmentInfo časovna omejitev in ponastavitev povezave

The GetEnrollmentInfo API trenutno išče naslove IP v sistemu domenskih imen, kar močno vpliva na zmogljivost. Ta postopek nameravamo poenostaviti s praznim odgovorom v <domain> polje.

Prizadeti API-ji:

  • GetEnrollmentInfo

GetEnrollmentInfo Primer zahteve:

<?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">
<header>
<securityContext>
<siteName>sqdemo6</siteName>
<webExID>xxx</webExID>
<password>xxxx</password>
<partnerID>webexpartner</partnerID>
</securityContext>
</header>
    <body>
        <bodyContent
            xsi:type="java:com.webex.service.binding.attendee.GetEnrollmentInfo">
            <sessionKey>716773566</sessionKey>
        </bodyContent>
    </body>
</serv:message>

GetEnrollmentInfo Primer odgovora:

<?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:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="att:getEnrollmentInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <att:session>
                <att:confID>154279066999981548</att:confID>
                <att:attendee>
                    <att:attendeeID>3191792</att:attendeeID>
                    <att:enrollFields>
                        <att:defaultFields>
                            <att:firstName>Alex</att:firstName>
                            <att:lastName>Yang</att:lastName>
                            <att:email>omega.alex.yang@gmail.com</att:email>
                            <att:company></att:company>
                            <att:phoneNum></att:phoneNum>
                            <att:title></att:title>
                            <att:receiveInfo>false</att:receiveInfo>
                            <att:address1></att:address1>
                            <att:address2></att:address2>
                            <att:city></att:city>
                            <att:state></att:state>
                            <att:zipcode></att:zipcode>
                            <att:country></att:country>
                            <att:leadSourceID></att:leadSourceID>
                            <att:leadScore>0.0</att:leadScore>
                        </att:defaultFields>
                        <att:customFields/>
                    </att:enrollFields>
                    <att:domain> </att:domain>
                    <att:ipAddress>10.35.240.53</att:ipAddress>
                    <att:submitTime>02/27/2020 22:03:57</att:submitTime>
                    <att:status>APPROVED</att:status>
                </att:attendee>
                <att:attendee>
                    <att:attendeeID>3191797</att:attendeeID>
                    <att:enrollFields>
                        <att:defaultFields>
                            <att:firstName>AlexKKK</att:firstName>
                            <att:lastName>Test</att:lastName>
                            <att:email>achillesyang@hotmail.com</att:email>
                            <att:company></att:company>
                            <att:phoneNum></att:phoneNum>
                            <att:title></att:title>
                            <att:receiveInfo>false</att:receiveInfo>
                            <att:address1></att:address1>
                            <att:address2></att:address2>
                            <att:city></att:city>
                            <att:state></att:state>
                            <att:zipcode></att:zipcode>
                            <att:country></att:country>
                            <att:leadSourceID></att:leadSourceID>
                            <att:leadScore>0.0</att:leadScore>
                        </att:defaultFields>
                        <att:customFields/>
                    </att:enrollFields>
                    <att:domain> </att:domain>
                    <att:ipAddress>10.154.181.15</att:ipAddress>
                    <att:submitTime>02/27/2020 22:07:38</att:submitTime>
                    <att:status>APPROVED</att:status>
                </att:attendee>
                <att:matchingRecords>
                    <serv:total>2</serv:total>
                    <serv:returned>2</serv:returned>
                    <serv:startFrom>1</serv:startFrom>
                </att:matchingRecords>
                <att:sessionKey>716773566</att:sessionKey>
            </att:session>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Posodobitve API-ja 40.2.0

Posodobitve XML API 40.2.0

Kliknite tukaj za prenos sheme XML API 40.2.0.

Odstrani anonimni dostop do LstSummarySession

Zaradi varnostne izboljšave ukinjamo podporo za anonimni dostop do LstSummarySession API. Če Webex Meetings anonimno dostopa do API-ja, se vrneta naslednja koda napake in sporočilo: "000015 Žal ni nobenega zapisa."

Prizadeti API-ji:

  • LstSummarySession

LstSummarySession Primer zahteve:

<?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">
<header>
    <securityContext>
        <siteName>sitename1</siteName>
    </securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.ep.LstsummarySession">
        <sessionKey>211894651</sessionKey>
    </bodyContent>
</body>
</serv:message>

LstSummarySession Primer odgovora:

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

CreateMeeting in SetMeeting varnostne izboljšave


Ta sprememba je bila narejena v XML API 40.2.0, vendar je bil njen opis urejen po prejemu povratnih informacij strank.

Kot varnostno izboljšavo smo posodobili CreateMeeting in SetMeeting API-ji, ki uporabnikom ne dovolijo načrtovanja začetnega časa sestanka, ki je že potekel. Če poskusijo, API prikaže sporočilo o napaki: "060016 Začetni čas seje mora biti pozneje kot trenutni čas." Če mora uporabnik načrtovati takojšen sestanek, priporočamo, da začetni čas sestanka nastavite pet minut pozneje kot trenutni čas.

Prizadeti API-ji:

  • CreateMeeting

  • SetMeeting

Posodobitve API-ja 40.1.2

Posodobitve XML API 40.1.2

Kliknite tukaj za prenos sheme XML API 40.1.2.

Načrtovanje sestanka samodejno ustvari geslo, če ga ne navedete

Izboljšali smo CreateMeeting, CreateEvent, CreateTrainingSession, in CreateTeleconferenceSession vključite geslo v telo odgovora API-ja.

Privzeto je Vsi sestanki/dogodki/seje morajo imeti geslo nastavitev je omogočena. Če v tem scenariju zahteva API ne vključuje gesla, se geslo samodejno ustvari iz strežnikov XML API.

Če je Vsi sestanki/dogodki/seje morajo imeti geslo nastavitev je onemogočeno, zahteva API-ja pa ne vključuje gesla, ampak geslo ne ustvarjen iz strežnikov XML API.

Če zahteva API vključuje geslo, bo odgovor vključeval to geslo, ne glede na Vsi sestanki/dogodki/seje morajo imeti geslo nastavitev omogočena ali onemogočena.

Prizadeti API-ji:

  • CreateMeeting

  • CreateEvent

  • CreateTrainingSession

  • CreateTeleconferenceSession

The CreateMeeting odziv ima zdaj meetingPassword element:

CreateMeeting Primer zahteve:

<?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">
<header>
<securityContext>

     <siteName>siteName1</siteName>
     <webExID>userID</webExID>
     <password>*****</password>
     <partnerID>webexpartner</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
    <metaData>
        <confName>Test_Auto_Generated_mtg_pwd</confName>
        <meetingType>3</meetingType>
    </metaData>

<schedule>
  <startDate>10/28/2020 17:35:00</startDate>
</schedule>
</bodyContent>
</body>
</serv:message>

CreateMeeting Primer odgovora:

<?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:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
    <serv:header>
        <serv:response>
            <serv:result>SUCCESS</serv:result>
            <serv:gsbStatus>PRIMARY</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="meet:createMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <meet:meetingkey>806745263</meet:meetingkey>
            <meet:meetingPassword>UzXJuzUD428</meet:meetingPassword>
            <meet:iCalendarURL>
                <serv:host>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=md225d5935256319ef21b71dd8ebd0640</serv:host>
                <serv:attendee>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=m26bf5e25ca587d32302fb29951b92e15</serv:attendee>
            </meet:iCalendarURL>
            <meet:guestToken>cfc7f3246d4862f1bb69b803e8615b7a</meet:guestToken>
        </serv:bodyContent>
    </serv:body>
</serv:message>

The CreateEvent odziv ima zdaj eventPassword element:

The CreateTrainingSession in CreateTeleconferenceSession odzivi imajo zdaj sessionPassword element:

Posodobitve API-ja 40.1.0

Posodobitve XML API 40.1.0

Kliknite tukaj za prenos sheme XML API 40.1.

GetSessionInfo izboljšave

Dodali smo nove elemente v GetSessionInfo API. API zdaj vrača podatke tudi za mobilne naprave.

Prizadeti API-ji:

  • GetSessionInfo

GetSessionInfo Zahtevaj posodobitve:

Primer zahteve:

<?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">
<header>
    <securityContext>
        <siteName>sqdemo11</siteName>
        <webExID>siteadmin</webExID>
        <password>P@ss1234</password>
    </securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
        <sessionKey>713707633</sessionKey>
        <pmrUrl>https://go.webex.com/join/dongchen</pmrUrl>
        <sipUrl>dongchen@go.webex.com or 123456789_go@webex.com or 123456789@go.webex.com</sipUrl>
        <meetingLink>https://go.webex.com/go/j.php?MTID=m814c6a483d4b5052d539f88d67acbad6</meetingLink>
        <meetingUuid>34567323456787654323456787654</meetingUuid>
    </bodyContent>
</body>
</serv:message>

LstAccessAnywhereHistory izboljšave

Dodali smo nov API, lstAccessAnywhereHistory, da odgovorite z informacijami o poročilu Webex Access Anywhere.

Prizadeti API-ji:

  • LstAccessAnywhereHistory

LstAccessAnywhereHistory Zahtevaj posodobitve:

LstAccessAnywhereHistory Posodobitve odgovorov:

Primer zahteve:

<?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">
<header>
<securityContext>
<siteName>sqdemo6</siteName>
<webExID>test</webExID>
<password>P@ss1234</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.history.LstAccessAnywhereHistory">
<hostWebexID>test1</hostWebexID>
<startTimeScope>
<sessionStartTimeStart>09/29/2019 00:42:34</sessionStartTimeStart>
<sessionStartTimeEnd>12/29/2019 04:42:34</sessionStartTimeEnd>
</startTimeScope>
<endTimeScope>
<sessionEndTimeStart>9/29/2019 02:42:34</sessionEndTimeStart>
<sessionEndTimeEnd>12/29/2019 05:42:34</sessionEndTimeEnd>
</endTimeScope>
<listControl>
<serv:startFrom>1</serv:startFrom>
<serv:maximumNum>10</serv:maximumNum>
<serv:listMethod>OR</serv:listMethod>
</listControl>
<order>
<orderBy>STARTTIME</orderBy>
<orderAD>ASC</orderAD>
</order>
</bodyContent>
</body>
</serv:message>

Primer odgovora:

<?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:LstAccessAnywhereHistoryResponse"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <history:matchingRecords>
                <serv:total>775</serv:total>
                <serv:returned>10</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
            <history:accessAnyWhereInfo>
                <history:confID>123456</history:confID>
                <history:userName>dean</history:userName>
                <history:computerName>6926_dean</history:computerName>
                <history:clientIP>10.224.222.183</history:clientIP>
                <history:startTime>11/29/2019 03:05:44</history:startTime>
                <history:endTime>11/29/2019 03:10:06</history:endTime>
                <history:duration>5</history:duration>
            </history:accessAnyWhereInfo>
        </serv:bodyContent>
    </serv:body>
</serv:message>