Dodatne informacije o XML API-jem 41 potražite u pregledu ažuriranja API-ja za sastanke cisco webexa (API 41)

Dodatne informacije o XML API-jem 39 i XML API-jem 11 potražite u pregledu XML API ažuriranja sastanaka cisco webexa (XML API 39 istariji).

Ažuriranja za XML API 11 SP9 i starije verzije potražite u odjeljku Cisco DevNet.

Ažuriranja api 40.12.0

Ažuriranja XML API-ja 40.12.0

Kliknite ovdje da biste preuzeli shemu XML API 40.12.0

XML API podržava vrstu privatnog sastanka

To utječe na XML API-je

  • Možemo koristiti API: CreateMeeting i SetMeeting za zakazivanje ili ažuriranje Webex sastanka vrstom privatnog sastanka.

  • Ako je zakazan web-sastanak s vrstom privatni sastanak, GetSessionInfo GetMeeting, LstSummarySession i LstCalendarSession vratit će novo imenovanje elemenata PrivateMeeting da to znam.

  • GetMeetingType i LstMeetingType vraćanje imenovanja novog elementa SupportPrivateMeeting što pokazuje podržava li privatne sastanke ili ne.

Promjene sheme

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

XML API:LstSummarySession: Dodajte <isPrivateMeeting> element.

XML API:LstCalendarSession: Dodajte <isPrivateMeeting> element.

XML API:GetSessionInfo: Dodajte <isPrivateMeeting> element.

XML API:GetMeeting: Dodajte <isPrivateMeeting> element.

Zahtjev XML API-ja: Stvorimeeting

Zahtjev za stvaranjemeetinga s vrstom privatnog sastanka

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

Odgovor XML API-ja: 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 vratit će predloške sastanaka na razini web-mjesta

Korisnička priča/Opis zadatka

GetSite API za vraćanje predloška sastanka na razini web-mjesta. To će omogućiti učionicama Education Connector i Webex da prikažu ove predloške kako bi učitelji odabrali i odabrali ove predloške dok zakazuju svoje on-line sesije.

Api-jeovi su pogođeni

Ako postoje prilagođeni predlošci sastanaka koji su na razini web-mjesta, GetSite api vratit će te predloške na razini web-mjesta.

Naziv elemenata

Opis

meetingTemplateName

naziv prilagođenih predložaka sastanaka na razini web-mjesta

serviceType

Webex sastanci, Webex treninzi i Webex događaji

Promjene sheme

GetSite : Dodajte <meetingTemplates> element.

Uzorak odgovora

GetSite odgovor

<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 može promijeniti element supportedServices kada je web-mjesto CI objedinjeno web-mjesto

Opis

XMLAPI SetUser ne podržava promjenu vrijednosti " supportedServices" u API zahtjevu kada je web-mjesto kontrolni centar povezan s web-mjestima za sastanke objedinjenog web-exa.

Promjene sheme

Na API-jeu nema promjene sheme: SetUser.

WEBEX-15436: Dodavanje zaštite da biste izbjegli duplicirane poruke e-pošte u Mtgconfattendeelist

Opis

Ako se više sudionika koji imaju istu e-poštu doda na isti sastanak u istom ZAHTJEVU za API, obrađujemo samo prvog sudionika e-poštom.

Pogođeni API-je

  • CreateMeetingAttendee

  • CreateUser

  • SetUser

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

Ogledni API

Zahtjev

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

Ažuriranja api 40.11.0

Xml API 40.11.0 ažuriranja

Kliknite ovdje da biste preuzeli shemu XML API 40.11.0

XMLAPI CreateUser podržava zaslonsko ime

CreateUser podržava dispalyname kada se značajka uključi/isključi EnableDisplayName je kao 1. Ako preklopni gumb značajke nije 1, displayName bit će zanemarena.

Promjene sheme

CreateUser:

XMLAPI SetUser podržava zaslonsko ime

SetUser podržava dispalyname kada se značajka uključi/isključi EnableDisplayName je 1. Ako preklopni gumb značajke nije 1, displayName bit će zanemarena.

Promjene sheme

SetUser:

XMLAPI GetUser podržava zaslonsko ime

GetUser podržava dispalyname kada se značajka uključi/isključi EnableDisplayName je 1. Ako preklopni gumb značajke nije 1, displayName neće se prikazati.

Kada displayName u DB je null i značajka preklopni EnableDisplayName je 1, displayName bit će firstName+" "+lastName za neazijske znakove i firstName+lastName za azijske znakove.

Promjene sheme

GetUserResponse:

XMLAPI kontrola korisničke razine za CMR hibridni voip

The cmrHybridVoip koristi se za postavljanje i dohvaćanje postavke korisničke razine za EnableCMRHybridVoIP.

Promjene sheme

GetUser Response:

CreateUser Request:

SetUser Request:

Ažuriranja api 40.10.0

Ažuriranja XML API-ja 40.10.0

Kliknite ovdje da biste preuzeli shemu XML API 40.10.0

XML API support for meeting UUID u API zahtjevu i odgovoru

Ogledni XML API: GetSessionInfo Zahtjev:

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

Zahvaćeni API:

  • CreateMeetingAttendee

  • DelMeetingAttendee

  • RegisterMeetingAttendee

  • CreateTeleconferenceSession

  • SetTeleconferenceSession

  • GetTeleconferenceSession

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

  • DelTrainingSession

  • CreateEvent

  • SetEvent

  • DelEvent

XMLAPI će vratiti dodatni element za konfiguraciju administratora web-mjesta kako bi onemogućio snimanje zaslona

Zahtjev dolazi od sigurnosti - oba PenTest bugovi i kupci, poput Goldman Sachsa. Krajnjim korisnicima ne žele dopustiti snimanje zaslona u aplikaciji Sastanci. U međuvremenu, mnogi drugi kupci žele ovu značajku - dopustiti snimanje zaslona. Također, korisnici Educationa također žele dopustiti snimanje zaslona. Tako ćemo za to imati konfiguraciju administratora web-mjesta, a XMLAPI će vratiti dodatno polje EnableMobileScreenCapture u odgovoru na GetSite kako bi se to podržalo.

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

Zahvaćeni API

GetSite

XMLAPI podrška MEET-269 Poboljšanje pridruživanja bez PIN-a

XMLAPI dodaje NOVU OPCIJU Sustavi za videokonferencije u mojoj tvrtki ili ustanovi mogu pokretati sastanke i uključiti se u njih bez upita za sastanak osobne sobe i sastanak MC-a.

  • createUser/setUser/getUser dodavanje novog čvora deviceCanStartMyPMR za personalMeetingRoom.

  • createMeeting/setMeeting/getMeeting dodavanje novog čvora deviceCanStartMeeting u rasporedu.

Mogućnost u Webex UI za sastanak osobne sobe :

Promjene sheme

CreateUser:

SetUser:

getUserResponse:

CreateMeeting:

setMeeting:

getMeetingResponse:

Ažuriranja api-ja 40.9.0

Ažuriranja XML API-ja 40.9.0

Kliknite ovdje da biste preuzeli shemu XML API 40.9.0

XML API support for meeting UUID zahtjev i odgovor

Dodali smo UUID sastanka u api zahtjev i odgovor gdje god podržavamo kao meetingKey ili sessionKey.

Ogledni XML API: GetSessionInfo Zahtjev:

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

Zahvaćeni API:

  • GetEnrollmentInfo

  • LstsummaryTrainingSession

  • AddScheduledTest

  • SetScheduledTest

  • DelScheduledTest

  • GetTestInformation

  • UploadEventImage

  • SendInvitationEmail

  • CreateSupportSession

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

  • LsteventsessionPreliminaryHistory

  • LsteventattendeePreliminaryHistory

  • LstTrainingPollResultsHistory

Webex sastanci imat će zaključano predvorje sastanka u kojem korisnici mogu čekati da budu primljeni u sastanak

Raspored XML API-ja i uređivanje MC sastanka radi podrške zaključanom predvorju prilikom značajke ( ConsistentLockedLobby), preklopite se.

Promjene sheme

Dodana su tri nova elementa ( externalAttendeeSecurity, autoLock, autoLockWaitTime) u API-jee CreateMeeting, SetMeeting i GetMeeting.

Element

Opis

externalAttendeeSecurity

Kada je sastanak otključan, postoje tri stavke sigurnosti vanjskog korisnika koje mogu biti odabiri.

AllowJoin: Može se odmah uključiti u sastanak;

AllowJoinWithLobby: Može se pridružiti sastanku samo ako ih domaćin pusti unutra;

BlockFromJoin: Nije moguće uključiti se u sastanak;

autoLock

Hoće li se sastanak automatski zaključati.

Istina: Automatski zaključaj sastanak nakon # minuta nakon početka sastanka

Neistinito: Ne zaključava automatski sastanak nakon početka sastanka

autoLockWaitTime

Zapisnik (0,5,10,15, 20) za automatsko zaključavanje sastanka nakon početka sastanka

Uzorak zahtjeva i 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>

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

Zahvaćeni API:

  • CreateMeeting

  • SetMeeting

  • GetMeeting

Poboljšanje GetSessionInfo API za vraćanje statusa sudionika na sesiju u tijeku

Dodana su dva nova elementa ( hasHostInMeeting, hasAttendeeInMeeting) kao odgovor na GetSessionInfo. Ta će se dva elementa vratiti kada sastanak bude sastanak u tijeku.

Element

Opis

hasHostInMeeting

Je li se domaćin pridružio sastanku u tijeku.

Istina: Host je na sastanku u tijeku.

False/Null: Host nije na sastanku koji je u tijeku ili sastanak nije u tijeku.

hasAttendeeInMeeting

Je li se sudionik/domaćin pridružio sastanku u tijeku.

Istina: na sastanku koji je u tijeku nalazi se sudionik ili domaćin.

False/Null: u sastanku koji je u tijeku nema sudionika ili domaćina ili sastanak nije u tijeku.

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

Zahvaćeni API:

GetSessionInfo

API GetUserCard zahtijeva autorizaciju.

Poboljšanje sigurnosti XML API-ja GetUserCard zahtijeva autorizaciju za dobivanje korisničkih podataka.

Zahvaćeni API:

GetUserCard

Ažuriranja za API 40.8.0

Ažuriranja XML API-ja 40.8.0

Kliknite ovdje da biste preuzeli shemu XML API 40.8.0

GetSessionInfo poboljšanje odgovora

Ako niste pozvani ili odobreni sa sastanka, poziv XML API-jem: GetSessionInfo neće vratiti elemente: confName, startDate, duration, timeZone, meetingLink, sipURL, displayMeetingUrl u tijelu za odgovor API-ja.

Primjer odgovora API-ja za sastanke:

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

Primjer odgovora API-ja za treninge/događaje:

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

Zahvaćeni API:

  • GetSessionInfo

GetSessionInfo, GetUserCard Poboljšanja sigurnosti

Napravili smo sigurnosno poboljšanje XML API-ja GetSessionInfo i GetUserCard. Blokirat ćemo korisnicima pristup ova dva API-ja u sljedeća dva sata ako je njihov poziv dosegao ograničenje u jednom satu bez pogrešaka pronađenih podataka.

Odgovor na stanje pogreške je: "403 zabranjeno"

Zahvaćeni API-je:

  • GetSessionInfo

  • GetUserCard

meetingUUID u API zahtjevu i podršci za odgovor

Dodali smo meetingUUID zahtjevu i odgovoru API-ja gdje god podržavamo meetingKey/sessionKey.

GetSessionInfo Zahtjev:

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

Zahvaćeni API:

  • LstOpenSession

  • GetEnrollmentInfo

  • LstsummaryMeeting

  • LstScheduledTests

  • GetEvent

  • LstsummaryEvent

  • LstmeetingusageHistory

  • LsttrainingsessionHistory

  • LsteventsessionHistory

  • LstsupportsessionHistory

  • DelSession

Predložak obrazovnih web-mjesta (vrsta sesije EDU-a) u podršci za XML API

Kada vaša web-mjesta omoguće vrstu sesije Instruktora obrazovanja (EDU), XML API može podržati zakazivanje sastanka pomoću predloška sastanka EDU-a.

Zahvaćeni API:

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

XML API CreateMeetingAttendee i RegisterMeetingAttendee podrška

Oba CreateMeetingAttendee i RegisterMeetingAttendee mogu provjeriti potreban obrazac za registraciju sudionika za registraciju Webex sastanaka.

I postoji nova iznimka za ovaj zadatak:

Broj iznimke

Poruka iznimke

040014

Nedostaju obavezna polja (obrazac za registraciju): ...

Na primjer, ako ste odabrali "Naziv radnog mjesta" i "Naziv tvrtke" kao obavezna polja za registraciju sastanaka web-sastanka sudionika kao što je prikazano u nastavku, prilikom pozivanja dva api-ja morate navesti vrijednost na "Naziv radnog mjesta" i "Naziv tvrtke": CreateMeetingAttendee i RegisterMeetingAttendee.

RegisterMeetingAttendee Zahtjev:

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

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


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

Zahvaćeni API:

  • CreateMeetingAttendee

  • RegisterMeetingAttendee

Poboljšanja provjere valjanosti XML API e-pošte

XML API ne smije dopustiti znakove bijelog razmaka u e-pošti, pa smo poboljšali provjeru valjanosti e-pošte kako bismo se uskladili s ponašanjem stranice web-sastanaka.

Zahvaćeni API:

  • CreateMeetingAttendee

  • CreateEvent

  • SetEvent

  • CreateContact

  • SetContact

  • SetRecordingInfo

  • CreateMeetingAttendee

  • CreateTrainingSession

  • SetTrainingSession

  • CreateUser

  • SetUser

  • CreateMeeting

  • SetMeeting

  • RegisterMeetingAttendee

Ažuriranja api 40.7.0

Ažuriranja XML API-ja 40.7.0

Kliknite ovdje da biste preuzeli shemu XML API 40.7.0

meetingUUID podrška

Dodali smo meetingUUID na API zahtjev i odgovor gdje god podržavamo meetingKey ili sessionKey.

GetSessionInfo Primjer zahtjeva:

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

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

Zahvaćeni API-je:

  • LstmeetingattendeeHistory

  • LsttrainingattendeeHistory

  • LsteventattendeeHistory

  • LstsupportattendeeHistory

CreateUser API pozdravlja podršku putem e-pošte za četiri nova jezika

XMLAPI html e-pošta dobrodošlice podržava sljedeća četiri nova jezika:

  • Češki (languageID=19)

  • Poljski (languageID=20)

  • Mađarski (languageID=21)

  • Rumunjski (languageID=22)

XMLAPI šalje e-poštu dobrodošlice u skladu s jezikom ili ID-om jezika u CreateUser zahtjev.

Koristeći CreateUser da biste poslali primjer html e-pošte dobrodošlice (češki):

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

Ažuriranja za API 40.6.1, 40.4.9

Xml API 40.6.1, 40.4.9 ažuriranja

Kliknite ovdje da biste preuzeli shemu XML API 40.6.1

Kliknite ovdje da biste preuzeli shemu XML API 40.4.9

CreateMeeting/SetMeeting podrška

Kada zakažete webex sastanak, XML API CreateMeeting/SetMeeting omogućuje provjeru ili poništavanje ili klik na obavezno ili neobavezno polje iz obrasca za registraciju sudionika.

Slijedi ogledni raspored sastanaka s web-stranice korisnika na kojem možete provjeriti obavezna polja kao što su "Naziv radnog mjesta", "Naziv tvrtke", "Grad"i "Država" na obrascu za registraciju sudionika:

Slijedi mapiranje između polja stranice i elemenata XML API-ja:

Polja stranice XMLAPI Element
Naziv radnog mjesta 
<title>
Naziv tvrtke 
<company>
Adresa 1 
<address1>
Adresa 2 
<address2>
Grad 
<city>
Savezna država 
<state>
Poštanski broj 
<postalCode>
Država/regija 
<country>
Poslovni telefon 
<phone>
Faks 
<fax>

Promijenjena shema: Dodavanje elementa "registrationForm" u CreateMeeting

Promijenjena shema: Dodavanje elementa "registrationForm" u SetMeeting

Promijenjena shema: Dodavanje elementa "registrationForm" u GetMeeting

CreateMeetingPrimjer zahtjeva:

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

SetMeetingPrimjer zahtjeva:

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

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

Zahvaćeni API-je:

  • CreateMeeting

  • SetMeeting

  • GetMeeting

  • DelMeeting

Vrsta sastanka E2EE ne podržava PMR sastanak

Kada tijekom poziva s API-jem omogućite PMR: CreateUser/SetUser/GetUser/GetMe i samo je vrsta sastanka E2EE dostupna, ona će odaslati sljedeću poruku o pogrešci: "110063 Korisnik mora imati barem jednu vrstu sastanka koja nije E2EE da bi omogućio PMR."

Zahvaćeni API-je:

  • CreateUser

  • SetUser

  • GetUser

  • GetMe

Ažuriranja API-ja 40.6.0

Ažuriranja XML API-ja 40.6.0

Kliknite ovdje da biste preuzeli shemu XML API 40.6.0

Dodana uloga upravljanja korisnicima

Stvorili smo ulogu upravljanja korisnicima i datoteka sheme za sljedeće se promijenila.

Promijenjena shema: CreateUserzahtjev:

Promijenjena shema: SetUser

Promijenjena shema: GetMeodgovor:

Promijenjena shema: LstsummaryUserodgovor:

Zahvaćeni API-je:

  • CreateUser

  • SetUser

  • GetMe

  • LstsummaryUser

CreateUserPrimjer zahtjeva:

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

Podrška za korištenje API ključa pristupa GetUserCard

Sada podržavamo korištenje API ključa (generiranog JWT tokena) pristupamo API-jem: GetUserCard u ovom izdanju.

Možete se pozvati na ove stranice o primjeni jednog API ključa i generirati JWT token:

Kako primijeniti jedan API ključ

Kako generirati JWT token

GetUserCardPrimjer zahtjeva:

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>  

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

Podrška za meetingUUID u API zahtjevu i odgovoru

Dodali smo meetingUUID na API zahtjev i odgovor kada podržavamo meetingKey ili sessionKey.

Zahvaćeni API-je:

  • LstRecording

  • LstsummarySession

  • GetSesssionInfo

  • GethosturlMeeting

  • GetjoinurlMeeting

  • LstMeetingAttendee

  • CreateMeeting

  • SetMeeting

  • GetMeeting

  • DelMeeting

  • LstCalendarSession

meetingUUIDPrimjer zahtjeva:

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

meetingUUIDPrimjer 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čevi PMR sastanka neće se mijenjati iz privremeno deaktiviranog korisnika ili onemogućenog PMR-a

Kada se privremeni deaktivirani korisnik ili onemogućeni PMR ponovno aktivira u roku od tjedan dana, sada ponovno aktivirani korisnik ili omogućen ključ pmr sastanka se ne mijenja, bit će isti kao i prije.

Zahvaćeni API-je:

  • SetUser

  • DelUser

LstSummarySession Poboljšanja

Poboljšali smo API: LstSummarySession vratiti zakazani PMR da bi imao jedan novi element, returnScheduledPMR, u zahtjevu. A zadana značajka preklopa je isključena.

Zahvaćeni API-je:

  • LstSummarySession

Promjena sheme:

Dodajemo novi naziv elementa returnScheduledPMR u zahtjevu API LstSummarySession.

Dodajemo novi naziv elementa isScheduledPMR u API LstSummarySession odgovoru.

LstSummarySessionPrimjer zahtjeva:

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

LstSummarySessionPrimjer 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 Poboljšanja

Dodali smo GetSite uključi/isključi značajku odgovora SupportXMLAPIReturnScheduledPMR

Zahvaćeni API-je:

  • GetSite

Promjena sheme:

The XML API GetSite novi element odgovora je: SupportXMLAPIReturnScheduledPMR

GetSitePrimjer zahtjeva:

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

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

Ažuriranja za API 40.4.8, 40.2.9

XML API 40.4.8, 40.2.9 Ažuriranja

Kliknite ovdje da biste preuzeli shemu XML API 40.4.8

Kliknite ovdje da biste preuzeli shemu XML API 40.2.9

Novi odgovor prilikom ažuriranja zakazanih sastanaka u XMLAPI-ju

Kada korisnici koriste XMLAPI za ažuriranje sastanaka zakazanih putem njihove stranice, poslat ćemo brojčanu lozinku u ažuriranju e-pošte sastanka i primijeniti je na webex sastanke, timove i centre za događaje.

Ti API-je: GetMeeting, GetTrainingSession, GetEvent i GetTeleconferenceSession, imat će te nove elemente kao odgovor: audioPassword(numerička lozinka), isEnforceAudioPassword, isEnforceAudioLogin za web-sastanke, timove i centre događaja.

Promijenjena shema:

Zahvaćeni API-je:

  • GetMeeting

  • GetTrainingSession

  • GetEvent

  • GetTeleconferenceSession

GetMeetingPrimjer zahtjeva:

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

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

Ažuriranja za API 40.4.5, 40.2.6

XML API 40.4.5, 40.2.6 Ažuriranja

GetUserCard i GetSessionInfo ograničenje korištenja

Implementiramo ograničenje korištenja API-ja GetUserCard i GetSessionInfo, možete dobiti poruku o pogrešci: "403 zabranjeno" ako dosegnete ograničenje korištenja.

Zahvaćeni API-je:

  • GetUserCard

  • GetSessionInfo

Api 40.4.4, 40.2.5 Ažuriranja

XML API 40.4.4, 40.2.5 Ažuriranja

BodyContent ograničenje broja

Dodali smo ograničen broj BodyContent u svakoj sekciji XML API-ja. Kada dodate previše BodyContent u api zahtjevu vratit će se sljedeći kod pogreške i poruka: "000053 Broj BodyContenta u zahtjevu mora biti manji od {number}"

Zahvaćeni API-je:

  • Bilo koji XML API

XML API zahtjev s višekratnikom BodyContent Primjer:

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

Ažuriranja api 40.4.3, 40.2.4

XML API 40.4.3, 40.2.4 Ažuriranja

Kliknite ovdje da biste preuzeli shemu XML API 40.4.3, 40.2.4.

CreateUser Poboljšanja

Poboljšali smo CreateUser da biste podržali e-poštu dobrodošlice na više jezika. The CreateUser sada zahtjevi isHTMLEmail

Zahvaćeni API-je:

  • CreateUser

CreateUser Primjer zahtjeva:

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

Ažuriranja api 40.4.0

Ažuriranja XML API-ja 40.4.0

Nametni provjeru e-pošte prilikom promjene e-pošte u XML API-jem

Nakon što je administrator web-mjesta omogućio potvrdu potrebnu korisniku za ažuriranje adrese e-pošte u administraciji web-mjesta:

  • Ako račun administratora koji nije web-mjesto pozove SetUser API za promjenu adresa e-pošte, trenutna e-pošta ostaje dok se ne potvrdi nova e-pošta. E-pošta s potvrdom promjene računa šalje se na novu adresu e-pošte s "Potvrdom promjene webex računa". Nakon što kliknete vezu u e-poruci za potvrdu, nova adresa e-pošte odmah se povezuje.


    Ako administrator koji nije na web-mjestu nazove SetUser API nekoliko puta bez završetka postupka provjere e-pošte, trenutna e-pošta se čuva, a najnovija nova e-pošta je ona koja se mora provjeriti.

  • Ako račun administratora web-mjesta nazove SetUser API za promjenu adresa e-pošte, postupak potvrde e-pošte se ne pokreće. Nova e-pošta odmah će biti povezana s računom domaćina ili sudionika.

Zahvaćeni API-je:

  • SetUser

GetEnrollmentInfo prekoračenje vremena i ponovno postavljanje veze

The GetEnrollmentInfo API trenutno traži IP adrese u sustavu naziva domena, što pokreće ogromne učinke na performanse. Taj proces planiramo pojednostaviti praznim odgovorom u <domain> polje.

Zahvaćeni API-je:

  • GetEnrollmentInfo

GetEnrollmentInfo Primjer zahtjeva:

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

Ažuriranja api-ja 40.2.0

Ažuriranja XML API-ja 40.2.0

Kliknite ovdje da biste preuzeli shemu XML API 40.2.0.

Ukloni anonimni pristup LstSummarySession

Kao sigurnosno poboljšanje, zaustavljamo podršku za anonimni pristup LstSummarySession API. Ako Webex sastanci anonimno pristupaju API-jem, vraćaju se sljedeći kôd pogreške i poruka: "000015 Žao mi je, nije pronađen nijedan zapis."

Zahvaćeni API-je:

  • LstSummarySession

LstSummarySession Primjer zahtjeva:

<?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 Primjer 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 i SetMeeting poboljšanja sigurnosti


Ta je promjena izvršena u XML API 40.2.0, ali je njezin opis uređen nakon primitka povratnih informacija od korisnika.

Kao sigurnosno poboljšanje ažurirali smo CreateMeeting i SetMeeting API-jeva da korisnicima ne dopuštaju zakazivanje vremena početka sastanka koje je već prošlo. Ako pokušaju, API će zatražiti poruku o pogrešci: "060016 vrijeme početka sesije trebalo bi biti kasnije od trenutnog vremena." Ako korisnik treba zakazati trenutni sastanak, preporučujemo da vrijeme početka sastanka bude postavljeno pet minuta kasnije od trenutnog vremena.

Zahvaćeni API-je:

  • CreateMeeting

  • SetMeeting

Ažuriranja api 40.1.2

Ažuriranja XML API-ja 40.1.2

Kliknite ovdje da biste preuzeli shemu XML API 40.1.2.

Zakazivanje sastanka automatski generira lozinku ako nije navedena

Poboljšali smo CreateMeeting, CreateEvent, CreateTrainingSession i CreateTeleconferenceSession za uključivanje lozinke u tijelo API odgovora.

Prema zadanim postavkama svi sastanci/događaji/sesija moraju imati omogućenu postavku lozinke. U ovom scenariju, ako API zahtjev ne sadrži lozinku, lozinka se automatski generira s XML API poslužitelja.

Ako svi sastanci/događaji/sesija moraju imati onemogućenu postavku lozinke , a api zahtjev ne sadrži lozinku, lozinka se ne generira s XML API poslužitelja.

Ako API zahtjev sadrži lozinku, odgovor će sadržavati tu lozinku, bez obzira na to jesu li svi sastanci/događaji/sesija morali imati omogućenu ili onemogućenu postavku lozinke.

Zahvaćeni API-je:

  • CreateMeeting

  • CreateEvent

  • CreateTrainingSession

  • CreateTeleconferenceSession

The CreateMeeting odgovor sada ima meetingPassword element:

CreateMeeting Primjer zahtjeva:

<?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 Primjer 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 odgovor sada ima eventPassword element:

The CreateTrainingSession i CreateTeleconferenceSession odgovori sada imaju sessionPassword element:

Ažuriranja api 40.1.0

Ažuriranja XML API-ja 40.1.0

Kliknite ovdje da biste preuzeli shemu XML API 40.1.

GetSessionInfo Poboljšanja

Dodali smo nove elemente u GetSessionInfo API. API sada vraća informacije i za mobilne uređaje.

Zahvaćeni API-je:

  • GetSessionInfo

GetSessionInfo Zatraži ažuriranja:

Primjer zahtjeva:

<?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 Poboljšanja

Dodali smo novi API, lstAccessAnywhereHistory, da biste odgovorili informacijama o izvješću Webex Access Anywhere.

Zahvaćeni API-je:

  • LstAccessAnywhereHistory

LstAccessAnywhereHistory Zatraži ažuriranja:

LstAccessAnywhereHistory Ažuriranja odgovora:

Primjer zahtjeva:

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

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