Ažuriranja API -ja 40.12.0

Ažuriranja XML API -ja 40.12.0

Kliknite ovdje za preuzimanje XML API 40.12.0 sheme

XML API podržava tip privatnog sastanka

XML API-ji biti pogođeni

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

  • Ako je Webex sastanak zakazan s vrstom privatnog sastanka, GetSessionInfo GetMeeting, LstSummarySession i LstCalendarSession vratit će novo ime elementa je PrivateMeeting to znati.

  • GetMeetingType i LstMeetingType vratiti novo imenovanje elementa SupportPrivateMeeting što pokazuje podržava li privatne sastanke ili ne.

Promjene sheme

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

XML API: LstSummarySession: Dodati <isPrivateMeeting> element.

XML API: LstCalendarSession: Dodati <isPrivateMeeting> element.

XML API: GetSessionInfo: Dodati <isPrivateMeeting> element.

XML API: GetMeeting : Dodati <isPrivateMeeting> element.

Zahtjev za XML API: CreateMeeting

Zahtjev za CreateMeeting s vrstom privatnog sastanka

<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
<schedule>
<startDate>25.10.2020. 13:00 sati</startDate>
<duration> 45</duration>
<timeZoneID> 45</timeZoneID>
</schedule>
<accessControl>
<meetingPassword> ******** </meetingPassword>
</accessControl>
<metaData>
<confName> MC_ PrivatniMeeting_ Testirajte</confName>
<meetingType> 168</meetingType> //169 je uzorak koji podržava privatni sastanak
</metaData>
</bodyContent>
</body>

Odgovor XML API-ja: GetSessionInfo

Odgovor za isPrivateMeeting

<ep:supportE2E>lažno</ep:supportE2E>
<ep:isAllowJBH> istina</ep:isAllowJBH>
<ep:isPrivateMeeting> istina</ep:isPrivateMeeting> //točno: sastanak podržava Privatni sastanak; lažno: sastanak ne podržava privatni sastanak.
<ep:isCETMeeting> lažno</ep:isCETMeeting>
<ep:isPersonalMeetingRoom> lažno</ep:isPersonalMeetingRoom>
<ep:isNextUpcomingInstance> istina</ep:isNextUpcomingInstance>

GetSite API će vratiti 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 Education Connectoru i Webex učionicama da pokažu ove predloške kako bi nastavnici mogli odabrati te predloške tijekom zakazivanja svojih on-line sesija.

API-ji su pogođeni

Ako postoje prilagođeni predlošci sastanka koji su na razini web-mjesta, GetSite api će vratiti ove predloške na razini web-mjesta.

Ime elemenata

Opis

meetingTemplateName

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

serviceType

Webex Meetings, Webex obuke i Webex događaji

Promjene sheme

GetSite : Dodati <meetingTemplates> element.

Uzorak 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> Centar za sastanke </ns1:serviceType>
</ns1:meetingTemplate>
<ns1:meetingTemplate>
<ns1:meetingTemplateName> Tempalte sastanka EC 2</ns1:meetingTemplateName>
<ns1:serviceType> EventCenter </ns1:serviceType>
</ns1:meetingTemplate>
<ns1:meetingTemplate>
<ns1:meetingTemplateName> Predložak sastanka TC 3</ns1:meetingTemplateName>
<ns1:serviceType> Centar za obuku</ns1:serviceType>
</ns1:meetingTemplate>
</ns1:meetingTemplates>

XML API SetUser ne može promijeniti element supportedServices kada je stranica CI unified site

Opis

XMLAPI SetUser ne podržava promjenu vrijednosti " supportedServices" u zahtjevu API -ja kada je web-mjesto sjedište povezano s kontrolnim čvorištem Unified Webex Meeting.

Promjene sheme

Nema promjene sheme na API-ju: SetUser.

WEBEX-15436: Dodajte zaštitu kako biste izbjegli dupliciranje e-poruka Mtgconfattendeelist

Opis

Ako je više sudionika koji imaju istu adresu e-pošte dodano na isti sastanak u istom API zahtjevu, obrađujemo samo prvog sudionika s e-poštom.

Pogođeni API-ji

  • CreateMeetingAttendee

  • CreateUser

  • SetUser

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

Primjer API -ja

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> lozinka</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
<sessionKey> 1714904382 </sessionKey>
<person>
<email> test@webex.com</email>
<name> ime1 </name>
</person>
<attendees>
<person>
<email> test@webex.com</email>
<name> ime2 </name>
</person>
<sessionKey> 1714904382</sessionKey>
</attendees>
</bodyContent>
</body>
</serv:message>

Ažuriranja API -ja 40.11.0

Ažuriranja XML API -ja 40.11.0

Kliknite ovdje za preuzimanje XML API 40.11.0 sheme

XMLAPI CreateUser podržava naziv za prikaz

CreateUser podupire dispalyname kada se značajka preklopi EnableDisplayName je kao 1. Ako prekidač značajke nije 1, tada je displayName bit će zanemarena.

Promjene sheme

CreateUser:

XMLAPI SetUser podržava naziv za prikaz

SetUser podupire dispalyname kada se značajka preklopi EnableDisplayName je 1. Ako prekidač značajke nije 1, displayName bit će zanemarena.

Promjene sheme

SetUser:

XMLAPI GetUser podržava naziv za prikaz

GetUser podupire dispalyname kada se značajka preklopi EnableDisplayName je 1. Ako prekidač značajke nije 1, displayName neće biti prikazano.

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

Promjene sheme

GetUserResponse:

XMLAPI Kontrola razine korisnika za Hibridni CMR Voip

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

Promjene sheme

GetUser Response:

CreateUser Request:

SetUser Request:

Ažuriranja API -ja 40.10.0

Ažuriranja XML API -ja 40.10.0

Kliknite ovdje za preuzimanje XML API 40.10.0 sheme

XML API support for meeting UUID u API zahtjevu i odgovoru

Primjer XML API-ja: 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> Testirajte</webExID>
<password> xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey> 805325231</sessionKey>
ili
<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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> NE_ NEDOSTATAK</ep:status>
<ep:isLocked> lažno</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 za onemogućavanje snimka zaslona

Zahtjev dolazi od Sigurnosti - oboje PenTest bugova i kupaca, poput Goldman Sachsa. Ne žele dopustiti krajnjim korisnicima snimanje snimka zaslona u aplikaciji Sastanci. U međuvremenu puno drugih kupaca želi ovu značajku - omogućiti snimka zaslona. Korisnici obrazovanja također žele dopustiti i snimka zaslona . Dakle, za to ćemo imati konfiguraciju administratora web-mjesta, a XMLAPI će vratiti dodatno polje EnableMobileScreenCapture u odgovoru na GetSite podržati ovo.

Uzorak 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> Testirajte</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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> lažno</ns1:EnableMobileScreenCapture>
...
</ns1:securityOptions>
...
</ns1:siteInstance>
</serv:bodyContent>
</serv:body>
</serv:message>

Zahvaćeni API

GetSite

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

XMLAPI dodaje NOVU OPCIJU Sustavi videokonferencija u mojoj organizaciji mogu započeti i pridružiti se sastancima bez upita za sastanak u osobnoj sobi i MC sastanak.

  • createUser/setUser/getUser dodati novi čvor deviceCanStartMyPMR za personalMeetingRoom.

  • createMeeting/setMeeting/getMeeting dodati novi čvor deviceCanStartMeeting u rasporedu.

Opcija u korisničkom sučelju Webex za sastanak u osobnoj sobi:

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 za preuzimanje XML API 40.9.0 sheme

XML API support for meeting UUID zahtjev i odgovor

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

Primjer XML API-ja: 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> Testirajte</webExID>
<password> xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey> 805325231</sessionKey>
ili
<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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> NE_ NEDOSTATAK</ep:status>
<ep:isLocked> lažno</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 na sastanak

XML API zakazuje i uredi MC sastanak kako bi podržao zaključano predvorje kada značajka ( ConsistentLockedLobby) uključiti.

Promjene sheme

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

Element

Opis

externalAttendeeSecurity

Kada je sastanak otključan, postoje tri opcije vanjske sigurnosti korisnika.

AllowJoin: Može se odmah pridružiti sastanku;

AllowJoinWithLobby: Mogu se pridružiti sastanku samo ako ih domaćin pusti;

BlockFromJoin: Ne mogu se pridružiti sastanku;

autoLock

Da li se sastanak automatski zaključava.

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

Netočno: Ne zaključava automatski sastanak nakon početka sastanka

autoLockWaitTime

Minute ( 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> lažno</joinRequiresAccount>
<externalAttendeeSecurity> DopustiJoinWithLobby</externalAttendeeSecurity>
<autoLock> istina</autoLock>
<autoLockWaitTime> 10 </autoLockWaitTime>
</attendeeOptions>
...
</bodyContent>

Request of SetMeeting:

<bodyContent xsi:type="java:com.webex.service.binding.meeting.SetMeeting">
<meetingkey>2###1###01</meetingkey>
...
<attendeeOptions>
...
<joinRequiresAccount> lažno</joinRequiresAccount>
<externalAttendeeSecurity> DopustiJoinWithLobby</externalAttendeeSecurity>
<autoLock> istina</autoLock>
<autoLockWaitTime> 10 </autoLockWaitTime>
</attendeeOptions>
...
</bodyContent>

Odgovor 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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI </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> lažno</meet:joinRequiresAccount>
<meet:externalAttendeeSecurity> Dopusti pridružiti se</meet:externalAttendeeSecurity>
<meet:autoLock> istina</meet:autoLock>
<meet:autoLockWaitTime> 10 </meet:autoLockWaitTime>
</meet:attendeeOptions>
...


Zahvaćeni API:

  • CreateMeeting

  • SetMeeting

  • GetMeeting

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

Dodana dva nova elementa ( hasHostInMeeting, hasAttendeeInMeeting) u odgovor na GetSessionInfo. Ova dva elementa bit će vraćena kada je sastanak u tijeku.

Element

Opis

hasHostInMeeting

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

Istina: Domaćin je na sastanku u tijeku.

False/Null : Domaćin nije na sastanku u tijeku ili sastanak nije sastanak u tijeku.

hasAttendeeInMeeting

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

Istina: na sastanku u tijeku postoji sudionik ili domaćin.

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

Uzorak API odgovora:

<?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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI </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>NEDOSTATAK</ep:status>


<ep:hasHostInMeeting>istina</ep:hasHostInMeeting>

<ep:hasAttendeeInMeeting>istina</ep:hasAttendeeInMeeting>

...


Zahvaćeni API:

GetSessionInfo

API GetUserCard zahtijeva autorizaciju.

Poboljšanje sigurnosti XML API GetUserCard zahtijeva autorizaciju za dobivanje podataka o korisniku.

Zahvaćeni API:

GetUserCard

Ažuriranja API -ja 40.8.0

Ažuriranja XML API -ja 40.8.0

Kliknite ovdje za preuzimanje XML API 40.8.0 sheme

GetSessionInfo poboljšanje odziva

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

Primjer API odgovora za sastanke:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:status>NE_ NEDOSTATAK</ep:status>
<ep:sessionkey> 1####2###4</ep:sessionkey>
<ep:accessControl>
<ep:listStatus>NENAPISANO</ep:listStatus>
<ep:registration> lažno</ep:registration>
<ep:passwordReq> istina</ep:passwordReq>
<ep:isRegisterIDRequired> lažno </ep:isRegisterIDRequired>
</ep:accessControl>
<ep:metaData>
<ep:serviceType> Centar za sastanke </ep:serviceType>
</ep:metaData>
<ep:attendeeOptions>
<ep:joinRequiresAccount> lažno </ep:joinRequiresAccount>
</ep:attendeeOptions>
<ep:isAllowJBH> istina</ep:isAllowJBH>
<ep:isCETMeeting> istina</ep:isCETMeeting>
<ep:isPersonalMeetingRoom> lažno</ep:isPersonalMeetingRoom>
</serv:bodyContent>

Primjer API odgovora za treninge/događaje:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:status>NE_ NEDOSTATAK</ep:status>
<ep:sessionkey> 1####5###9</ep:sessionkey>
<ep:accessControl>
<ep:listStatus>NENAPISANO</ep:listStatus>
<ep:registration> istina </ep:registration>
<ep:registrationURL>https://sitename.webex.com/tc3300/trainingcenter/register/registerSession.do?siteurl=sitename&confID=16###92######61</ep:registrationURL>
<ep:passwordReq> istina </ep:passwordReq>
<ep:registrationURLForMobile>https://sitename.webex.com/tc3300/trainingcenter/meeting/sessionInfoMobile.do?siteurl=sitename&confID=16###92######61</ep:registrationURLForMobile>
<ep:joinStatus> POZOVI/REGISTRIRAJ SE/ODBACI</ep:joinStatus>
<ep:isRegisterIDRequired> lažno </ep:isRegisterIDRequired>
</ep:accessControl>
<ep:metaData>
<ep:serviceType> Centar za obuku </ep:serviceType>
</ep:metaData>
<ep:attendeeOptions>
<ep:joinRequiresAccount> lažno </ep:joinRequiresAccount>
</ep:attendeeOptions>
<ep:isAllowJBH> istina</ep:isAllowJBH>
<ep:isCETMeeting> istina</ep:isCETMeeting>
<ep:isPersonalMeetingRoom> lažno</ep:isPersonalMeetingRoom>
</serv:bodyContent>

Zahvaćeni API:

  • GetSessionInfo

GetSessionInfo, GetUserCard Sigurnosna poboljšanja

Napravili smo sigurnosno poboljšanje na XML API -ju GetSessionInfo i GetUserCard. Korisnicima ćemo blokirati pristup ova dva API-ja u sljedeća dva sata ako njihov poziv dosegne ograničenje u jednom satu bez pronađenih pogrešaka u podacima.

Odgovor statusa greške je: "403 Zabranjeno"

Zahvaćeni API-ji:

  • GetSessionInfo

  • GetUserCard

meetingUUID u podršci za API zahtjeve i odgovore

Dodali smo meetingUUID u API zahtjev i odgovor gdje god podržavamo a 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> Testirajte</webExID>
<password> xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey> 805325231</sessionKey>
ili
<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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> NE_ NEDOSTATAK</ep:status>
<ep:isLocked> lažno</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 (tip EDU sesije) u podršci za XML API

Kada vaša web-mjesta omoguće tip sesije Education Instructor (EDU), XML API može podržati zakazati sastanak s predloškom sastanka EDU.

Zahvaćeni API:

  • CreateMeeting

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

XML API CreateMeetingAttendee i RegisterMeetingAttendee podrška

Oboje CreateMeetingAttendee i RegisterMeetingAttendee mogu provjeriti potreban obrazac za registracija sudionika za registraciju na Webex Meetings .

I postoji nova iznimka za ovaj zadatak:

Broj iznimke

Poruka iznimke

040014

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

Na primjer, ako ste odabrali "Job Title" i "Company Name" kao obavezna polja za registraciju sudionika Webex Meetings kao što je prikazano u nastavku, tada morate navesti vrijednost za "Job Title" i "Company Name" kada pozivate dva API-ja : CreateMeetingAttendee i RegisterMeetingAttendee.

RegisterMeetingAttendee Zahtjev:

<body>
<bodyContent xsi:type="java:com.webex.service.binding.attendee.RegisterMeetingAttendee">
<attendees>
<person>
<name>Imeb Prezime</name>
<firstName> Imeb</firstName>
<lastName> Prezime</lastName>
<title>Inženjer</title> // Naziv radnog mjesta
<company> Cisco1234</company> //Naziv tvrtke
...
<email>****@*****.com</email>
<type> POSJETITELJ</type>
<sendReminder> istina</sendReminder>
</person>
<role> PRISUTNIK</role>
<joinStatus> PRIHVATI</joinStatus>
<emailInvitations> istina</emailInvitations>
<sessionKey> 1####4####1</sessionKey>
</attendees>
</bodyContent>
</body>

CreateMeetingAttendee Zahtjev:

<bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
<person>
<name>ImeA PrezimeA</name>
<firstName> Ime A</firstName>
<lastName> PrezimeA</lastName>
<title>Inženjer</title> // Naziv radnog mjesta
<company> Cisco1234</company> //Naziv tvrtke
...
<email>*****@*****.com</email>
<type> POSJETITELJ</type>
<sendReminder> istina</sendReminder>
</person>
<role> PRISUTNIK</role>
<joinStatus> PRIHVATI</joinStatus>
<emailInvitations> istina</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>NEUSPJEH</serv:result>
<serv:reason> Nedostaju obavezna polja (obrazac za registraciju): naziv, tvrtka</serv:reason>
<serv:gsbStatus> PRIMARNI</serv:gsbStatus>
<serv:exceptionID> 040014</serv:exceptionID>
<serv:value> naslov, tvrtka</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 -ja e-pošta

XML API ne bi trebao dopustiti znakove razmaka u e-poruci, stoga smo poboljšali provjeru valjanosti e-pošte kako bismo se uskladili s ponašanjem stranice Webex Meetings .

Zahvaćeni API:

  • CreateMeetingAttendee

  • CreateEvent

  • SetEvent

  • CreateContact

  • SetContact

  • SetRecordingInfo

  • CreateMeetingAttendee

  • CreateTrainingSession

  • SetTrainingSession

  • CreateUser

  • SetUser

  • CreateMeeting

  • SetMeeting

  • RegisterMeetingAttendee

Ažuriranja API -ja 40.7.0

Ažuriranja XML API -ja 40.7.0

Kliknite ovdje za preuzimanje XML API 40.7.0 sheme

meetingUUID podrška

Dodali smo meetingUUID na zahtjev i odgovor API -ja 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> Testirajte</webExID>
<password> xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey> 805325231</sessionKey>
ili
<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> Testirajte</webExID>
<password> xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey> 805325231</sessionKey>
ili
<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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> NE_ NEDOSTATAK</ep:status>
<ep:isLocked> lažno</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-ji:

  • LstmeetingattendeeHistory

  • LsttrainingattendeeHistory

  • LsteventattendeeHistory

  • LstsupportattendeeHistory

CreateUser Podrška putem e-pošte za API dobrodošlice za četiri nova jezika

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

  • češki (languageID=19)

  • poljski (languageID=20)

  • mađarski (languageID=21)

  • rumunjski (languageID=22)

XMLAPI šalje poruku dobrodošlice prema jeziku ili ID-u jezika u CreateUser zahtjev.

Korištenje CreateUser za slanje HTML primjera e-pošta -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> Testirajte</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> testirati</firstName>
<lastName> korisnika</lastName>
<webExId> testuser</webExId>
<password> xxxxxx</password>
<email> testuser@test.com </email>
<privilege>
<host> istina </host>
</privilege>
<languageID> 19</languageID>
ili
<language> češki</language>
<active> AKTIVIRANA</active>
<sendWelcome> istina</sendWelcome>
<isHTMLEmail> istina</isHTMLEmail>
</bodyContent>
</bodyContent>
</body>

API 40.6.1, 40.4.9 Ažuriranja

XML API 40.6.1, 40.4.9 Ažuriranja

Kliknite ovdje za preuzimanje XML API 40.6.1 sheme

Kliknite ovdje za preuzimanje XML API 40.4.9 sheme

CreateMeeting/SetMeeting podrška

Kada zakažete Webex sastanak, XML API CreateMeeting/SetMeeting omogućuje vam da označite ili poništite ili kliknete na obavezno ili neobvezno obavezno polje u obrascu za registracija sudionika .

Slijedi primjer rasporeda sastanaka s korisničke web-stranica gdje možete provjeriti potrebna polja kao što su npr "Naziv posla", "Naziv tvrtke", "Grad" , i "država" na obrascu za registracija sudionika :

Sljedeće je mapiranje između polja stranice i elemenata XML API-ja:

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

Promijenjena shema: Dodajte element "registrationForm". CreateMeeting

Promijenjena shema: Dodajte element "registrationForm". SetMeeting

Promijenjena shema: Dodajte element "registrationForm". GetMeeting

CreateMeetingPrimjer zahtjeva:

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

SetMeetingPrimjer zahtjeva:

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

<metaData>
<confName>Naziv konferencije</confName>
<meetingType> 3 </meetingType>
</metaData>

<attendeeOptions>
<emailInvitations> istina</emailInvitations>
<registration> istina</registration>
<auto> istina</auto>
</attendeeOptions>

<registrationForm>
<title><req>točno</req></title>
<company><req>istina</req></company>
<address1><req>lažno</req></address1>
<address2><req>lažno </req></address2>
<city><req> istina </req></city>
<state><req> istina </req></state>
<postalCode><req> lažno </req></postalCode>
<country><req> lažno </req></country>
<phone><req> lažno </req></phone>
<fax><req> lažno</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>lažno </meet:req></meet:phone>
<meet:title><meet:req> istina </meet:req></meet:title>
<meet:company><meet:req> istina </meet:req></meet:company>
<meet:address1><meet:req> lažno </meet:req></meet:address1>
<meet:address2><meet:req> lažno </meet:req></meet:address2>
<meet:city><meet:req> istina </meet:req></meet:city>
<meet:state><meet:req> istina </meet:req></meet:state>
<meet:postalCode><meet:req> lažno </meet:req></meet:postalCode>
<meet:country><meet:req> lažno </meet:req></meet:country>
<meet:fax><meet:req> lažno</meet:req></meet:fax>
</meet:registrationForm>


Zahvaćeni API-ji:

  • CreateMeeting

  • SetMeeting

  • GetMeeting

  • DelMeeting

Vrsta sastanka E2EE ne podržava PMR sastanak

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

Zahvaćeni API-ji:

  • CreateUser

  • SetUser

  • GetUser

  • GetMe

Ažuriranja API -ja 40.6.0

Ažuriranja XML API -ja 40.6.0

Kliknite ovdje za preuzimanje XML API 40.6.0 sheme

Dodana je uloga Upravljanje korisnicima

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

Promijenjena shema: CreateUserzahtjev:

Promijenjena shema: SetUser

Promijenjena shema: GetMeodgovor:

Promijenjena shema: LstsummaryUserodgovor:

Zahvaćeni API-ji:

  • 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> Administrator stranice</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> istina</umSiteAdmin>
<host> lažno </host>

<siteAdmin> lažno</siteAdmin>
<labAdmin> lažno</labAdmin>
<voiceOverIp> lažno </voiceOverIp>
</privilege>
<languageID> 3</languageID>
<active> AKTIVIRANA</active>
<sendWelcome> istina</sendWelcome>
<isHTMLEmail> istina</isHTMLEmail>
</bodyContent>
</body>

Podrška korištenjem API ključa za pristup GetUserCard

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

Možete pogledati ove stranice o primjeni jednog API ključa i generiranju JWT tokena:

Kako primijeniti jedan API ključ

Kako generirati JWT token

GetUserCardPrimjer zahtjeva:

POST https://{sitename}.webex.com/WBXService/XMLService
Zaglavlje:
Content-Type application/json;charset=utf-8
JWTToken ${jwttoken}
tijelo:
<?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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> lažno </use:isUploaded>
</use:avatar>
<use:personalMeetingRoom>
<use:title> Testova osobna soba </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-ji:

  • 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> Testirajte</webExID>
<password> xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey> 805325231</sessionKey>
ili
<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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> NE_ NEDOSTATAK</ep:status>
<ep:isLocked> lažno</ep:isLocked>
<ep:sessionkey> 805325231</ep:sessionkey>
<ep:meetingUUID> 039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
<ep:confID> 158941507534980823</ep:confID>
...
...
</serv:bodyContent>
</serv:body>
</serv:message>

PMR ključevi sastanka neće se mijenjati od privremeno deaktiviranog korisnika ili onemogućenog PMR-a

Kada se privremeno deaktivirani korisnik ili onemogućen PMR ponovno aktivira unutar jednog tjedna, sada ponovno aktivirani korisnik ili omogućen PMR-ov ključ sastanka se ne mijenja, bit će isti kao i prije.

Zahvaćeni API-ji:

  • SetUser

  • DelUser

LstSummarySession poboljšanja

Poboljšali smo API: LstSummarySession vrati planirani-PMR da ima jedan novi element, returnScheduledPMR, u zahtjevu. I zadana opcija za prebacivanje je isključena.

Zahvaćeni API-ji:

  • LstSummarySession

Promjena sheme:

Dodamo novi naziv elementa returnScheduledPMR u zahtjevu API -ja LstSummarySession.

Dodamo novi naziv elementa isScheduledPMR u odgovoru API -ja LstSummarySession.

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> Testirajte</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> I </listMethod>
</listControl>
<dateScope>
<startDateStart> 01.11.2019. 8:0:0</startDateStart>
<startDateEnd> 12/01/2019 7:59:59</startDateEnd>
<timeZoneID> 4</timeZoneID>
<endDateStart> 01.11.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> POČETAK</orderBy>
<orderAD> ASC </orderAD>
</order>
<serviceTypes>
<serviceType> EventCenter</serviceType>
<serviceType> Centar za sastanke</serviceType>
<serviceType> Prodajni centar</serviceType>
<serviceType> Centar za obuku</serviceType>
<serviceType> Centar za podršku </serviceType>
</serviceTypes>
<returnScheduledPMR> istina</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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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. godine</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> Timski sastanak</ep:confName>
<ep:sessionType> 3</ep:sessionType>
<ep:serviceType> Centar za sastanke</ep:serviceType>
<ep:hostWebExID> Testirajte</ep:hostWebExID>
<ep:hostFirstName> Testirajte</ep:hostFirstName>
<ep:hostLastName> Testirajte</ep:hostLastName>
<ep:otherHostWebExID> Testirajte</ep:otherHostWebExID>
<ep:timeZoneID> 2</ep:timeZoneID>
<ep:timeZone> GMT-10:00, Havaji (Honolulu)</ep:timeZone>
<ep:status> NE_ NEDOSTATAK</ep:status>
<ep:startTime> 12.10.2019. 00:35:41</ep:startTime>
<ep:duration> 60</ep:duration>
<ep:listStatus> JAVNO</ep:listStatus>
<ep:hostEmail> Test@webex.com</ep:hostEmail>
<ep:passwordReq> istina</ep:passwordReq>
<ep:hostJoined> lažno</ep:hostJoined>
<ep:participantsJoined> lažno</ep:participantsJoined>
<ep:confID> 141672157056861215</ep:confID>
<ep:registration> lažno</ep:registration>
<ep:isRecurring> istina</ep:isRecurring>
<ep:hostType> 1019001</ep:hostType>
<ep:isAudioOnly> lažno</ep:isAudioOnly>
<ep:isTCSingleRecurrence> lažno</ep:isTCSingleRecurrence>
<ep:isAllowJBH> lažno</ep:isAllowJBH>
<ep:isCETMeeting> istina</ep:isCETMeeting>
<ep:isException> lažno</ep:isException>
<ep:isNextUpcomingInstance> lažno</ep:isNextUpcomingInstance>
<ep:seriesMeetingKey> 0</ep:seriesMeetingKey>
<ep:recurrenceId> 0</ep:recurrenceId>
<ep:isScheduledPMR> istina </ep:isScheduledPMR>
</ep:session>
<ep:session>
<ep:sessionKey> 805660167</ep:sessionKey>
<ep:confName> xmlmc Molly08Konzola816960001</ep:confName>
<ep:sessionType> 3</ep:sessionType>
<ep:serviceType> Centar za sastanke</ep:serviceType>
<ep:hostWebExID> Molly08Konzola81696000</ep:hostWebExID>
<ep:hostFirstName> Molly08Konzola81696000</ep:hostFirstName>
<ep:hostLastName> Molly08Konzola81696000</ep:hostLastName>
<ep:otherHostWebExID> Molly08Konzola81696000</ep:otherHostWebExID>
<ep:timeZoneID> 2</ep:timeZoneID>
<ep:timeZone> GMT-10:00, Havaji (Honolulu)</ep:timeZone>
<ep:status> NE_ NEDOSTATAK</ep:status>
<ep:startTime> 12.10.2019. 00:35:41</ep:startTime>
<ep:duration> 60</ep:duration>
<ep:listStatus> JAVNO</ep:listStatus>
<ep:hostEmail> Molly08Console81696000@webex.com</ep:hostEmail>
<ep:passwordReq> istina</ep:passwordReq>
<ep:hostJoined> lažno</ep:hostJoined>
<ep:participantsJoined> lažno</ep:participantsJoined>
<ep:confID> 141672108716459038</ep:confID>
<ep:registration> lažno</ep:registration>
<ep:isRecurring> istina</ep:isRecurring>
<ep:hostType> 1019001</ep:hostType>
<ep:isAudioOnly> lažno</ep:isAudioOnly>
<ep:isTCSingleRecurrence> lažno</ep:isTCSingleRecurrence>
<ep:isAllowJBH> lažno</ep:isAllowJBH>
<ep:isCETMeeting> istina</ep:isCETMeeting>
<ep:isException> lažno</ep:isException>
<ep:isNextUpcomingInstance> lažno</ep:isNextUpcomingInstance>
<ep:seriesMeetingKey> 0</ep:seriesMeetingKey>
<ep:recurrenceId> 0</ep:recurrenceId>
<ep:isScheduledPMR> istina</ep:isScheduledPMR>
</ep:session>
</serv:bodyContent>
</serv:body>
</serv:message>

GetSite poboljšanja

Dodali smo a GetSite značajka odgovora preklop na SupportXMLAPIReturnScheduledPMR

Zahvaćeni API-ji:

  • GetSite

Promjena sheme:

XML API GetSite odgovor novi element 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> Testirajte</webExID>
<password> xxx</password>
<clientInfo> xxx</clientInfo>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.site.GetSite">
</bodyContent>
</body>

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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> istina</ns1:SupportXMLAPIReturnScheduledPMR>
...
</ns1:siteCommonOptions>
</ns1:siteInstance>
</serv:bodyContent>
</serv:body>
</serv:message>

API 40.4.8, 40.2.9 Ažuriranja

Ažuriranja XML API -ja 40.4.8, 40.2.9

Kliknite ovdje za preuzimanje XML API 40.4.8 sheme

Kliknite ovdje za preuzimanje XML API 40.2.9 sheme

Novi odgovor prilikom ažuriranja zakazanih sastanaka u XMLAPI

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

Ti API-ji: GetMeeting, GetTrainingSession, GetEvent i GetTeleconferenceSession, imat će ove nove elemente kao odgovor: audioPassword(numerička lozinka), isEnforceAudioPassword, isEnforceAudioLogin za Webex Meetings, timove i centre za događaje.

Promijenjena shema:

Zahvaćeni API-ji:

  • 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> testirati</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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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> lažno</meet:listToPublic>
<meet:isPublic> lažno</meet:isPublic>
<meet:meetingPassword> PkzC8tP7kM5</meet:meetingPassword>
<meet:audioPassword> 75928877</meet:audioPassword>
<meet:isEnforceAudioPassword> istina</meet:isEnforceAudioPassword>
<meet:isEnforceAudioLogin> lažno </meet:isEnforceAudioLogin>
</meet:accessControl>
...
...
</serv:bodyContent>
</serv:body>
</serv:message>

API 40.4.5, 40.2.6 Ažuriranja

XML API 40.4.5, 40.2.6 Ažuriranja

GetUserCard i GetSessionInfo ograničenje upotrebe

Implementiramo ograničenje upotrebe na API -ju GetUserCard i GetSessionInfo, mogli biste dobiti poruku o poruka o pogrešci: "403 zabranjeno" ako dosegnete ograničenje upotrebe.

Zahvaćeni API-ji:

  • GetUserCard

  • GetSessionInfo

Ažuriranja API -ja 40.4.4, 40.2.5

XML API 40.4.4, 40.2.5 Ažuriranja

BodyContent ograničenje broja

Dodali smo ograničen broj BodyContent u svakom odjeljku XML API -ja. Kada dodate previše BodyContent u API zahtjevu vratit će se sljedeći kod kôd pogreške i poruka: "000053 Broj sadržaja tijela u zahtjevu mora biti manji od {number}"

Zahvaćeni API-ji:

  • Bilo koji XML API

XML API zahtjev s višestrukim 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>

Ažuriranja API -ja 40.4.3, 40.2.4

Ažuriranja XML API -ja 40.4.3, 40.2.4

Kliknite ovdje za preuzimanje XML API 40.4.3, 40.2.4 sheme.

CreateUser poboljšanja

Poboljšali smo CreateUser za podršku e-pošte dobrodošlice na više jezika. Datoteka CreateUser sada zahtjeva isHTMLEmail

Zahvaćeni API-ji:

  • 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> istina</host>
<siteAdmin> lažno</siteAdmin>
<labAdmin> lažno</labAdmin>
<voiceOverIp> lažno </voiceOverIp>
</privilege>
<languageID> 3</languageID>
<active> AKTIVIRANA</active>
<sendWelcome> istina</sendWelcome>
<isHTMLEmail> istina</isHTMLEmail>
</bodyContent>
</body>

Ažuriranja API -ja 40.4.0

Ažuriranja XML API -ja 40.4.0

Provedi provjeru e-pošte prilikom mijenjanja e-pošte u XML API -ju

Nakon što je administrator web-mjesta omogućio Za ažuriranje adresa e-pošte potrebna je potvrda u Webex Administracijsko web-mjesto:

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


     

    Ako administrator web-mjesta nazove SetUser API nekoliko puta bez dovršetak postupka potvrde e-pošte, trenutna e-pošta se čuva, a najnovija nova e-pošta je ona koja se mora potvrditi.

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

Zahvaćeni API-ji:

  • SetUser

GetEnrollmentInfo timeout i reset veze

Datoteka GetEnrollmentInfo API trenutno traži IP adrese u sustavu naziva domene, što izaziva velike utjecaje na performanse. Planiramo pojednostaviti ovaj proces, s praznim odgovorom u <domain> polje.

Zahvaćeni API-ji:

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

</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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI </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> lažno </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> 27.02.2020 22:03:57</att:submitTime>
<att:status> ODOBRENO </att:status>
</att:attendee>
<att:attendee>
<att:attendeeID> 3191797 </att:attendeeID>
<att:enrollFields>
<att:defaultFields>
<att:firstName> AlexKKK</att:firstName>
<att:lastName> Testirajte</att:lastName>
<att:email> achillesyang@hotmail.com </att:email>
<att:company></att:company>
<att:phoneNum></att:phoneNum>
<att:title></att:title>
<att:receiveInfo> lažno </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> 27.02.2020 22:07:38</att:submitTime>
<att:status> ODOBRENO </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>

Ažuriranja API -ja 40.2.0

Ažuriranja XML API -ja 40.2.0

Kliknite ovdje za preuzimanje XML API 40.2.0 sheme.

Ukloni anonimni pristup za LstSummarySession

Kao sigurnosno poboljšanje, zaustavljamo podršku za anonimni pristup LstSummarySession API. Ako Webex Meetings anonimno pristupa API-ju, vraća se sljedeći kod kôd pogreške i poruka: "000015 Nažalost, nije pronađen zapis."

Zahvaćeni API-ji:

  • 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>naziv web mjesta1</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>NEUSPJEH</serv:result>
<serv:reason> Nažalost, zapis nije pronađen</serv:reason>
<serv:gsbStatus> PRIMARNI</serv:gsbStatus>
<serv:exceptionID> 000015</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>

CreateMeeting i SetMeeting sigurnosna poboljšanja


 

Ova promjena je napravljena u XML API -ju 40.2.0, ali je njezin opis uređen nakon što je dobio povratne informacije od korisnika.

Kao sigurnosno poboljšanje, ažurirali smo CreateMeeting i SetMeeting API-ji koji ne dopuštaju korisnicima da zakažu vrijeme početka zakazati sastanak koje je već prošlo. Ako pokušaju, API traži poruku o poruka o pogrešci: "060016 vrijeme početka sesije treba biti kasnije od trenutnog vremena." Ako korisnik treba zakazati trenutni sastanak, preporučujemo da se vrijeme početka sastanka postavi pet minuta kasnije od trenutnog vremena.

Zahvaćeni API-ji:

  • CreateMeeting

  • SetMeeting

Ažuriranja API -ja 40.1.2

Ažuriranja XML API -ja 40.1.2

Kliknite ovdje za preuzimanje XML API 40.1.2 sheme.

Zakazivanje sastanka automatski generira lozinku ako ona nije navedena

Poboljšali smo CreateMeeting, CreateEvent, CreateTrainingSession i CreateTeleconferenceSession uključiti lozinku u tijelo API odgovora.

Prema zadanim postavkama, Svi sastanci/događaji/sjednice moraju imati lozinku postavka je omogućena. U ovom scenariju, ako API zahtjev ne uključuje lozinku, lozinka se automatski generira iz XML API poslužitelja.

Ako je Svi sastanci/događaji/sjednice moraju imati lozinku postavka je onesposobljena , a API zahtjev ne uključuje lozinku, lozinka jest ne generiran od XML API poslužitelja.

Ako API zahtjev uključuje lozinku, tada će odgovor uključivati tu lozinku, bez obzira na Svi sastanci/događaji/sjednice moraju imati lozinku postavka je omogućena ili onemogućena.

Zahvaćeni API-ji:

  • CreateMeeting

  • CreateEvent

  • CreateTrainingSession

  • CreateTeleconferenceSession

Datoteka 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>naziv web mjesta1</siteName>
<webExID> ID korisnika</webExID>
<password> *****</password>
<partnerID> webexpartner </partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
<metaData>
<confName> Test_ Auto_ G enerated_mtg_pwd</confName>
<meetingType> 3 </meetingType>
</metaData>

<schedule>
<startDate> 28.10.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>USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI</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>

Datoteka CreateEvent odgovor sada ima eventPassword element:

Datoteka CreateTrainingSession i CreateTeleconferenceSession odgovori sada imaju sessionPassword element:

Ažuriranja API -ja 40.1.0

Ažuriranja XML API -ja 40.1.0

Kliknite ovdje za preuzimanje XML API 40.1 sheme.

GetSessionInfo poboljšanja

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

Zahvaćeni API-ji:

  • GetSessionInfo

GetSessionInfo Zatražite 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 ili 123456789_go @webex.com ili 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 odgovorite s podacima izvješća Webex Access Anywhere .

Zahvaćeni API-ji:

  • LstAccessAnywhereHistory

LstAccessAnywhereHistory Zatražite 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> testirati</webExID>
<password> P@ss1234 </password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.history.LstAccessAnywhereHistory">
<hostWebexID> test 1 </hostWebexID>
<startTimeScope>
<sessionStartTimeStart> 29.09.2019. 00:42:34</sessionStartTimeStart>
<sessionStartTimeEnd> 29.12.2019. 04:42:34 </sessionStartTimeEnd>
</startTimeScope>
<endTimeScope>
<sessionEndTimeStart> 29.9.2019. 02:42:34</sessionEndTimeStart>
<sessionEndTimeEnd> 29.12.2019. 05:42:34 </sessionEndTimeEnd>
</endTimeScope>
<listControl>
<serv:startFrom> 1</serv:startFrom>
<serv:maximumNum> 10</serv:maximumNum>
<serv:listMethod> ILI </serv:listMethod>
</listControl>
<order>
<orderBy> POČETAK</orderBy>
<orderAD> ASC</orderAD>
</order>
</bodyContent>
</body>

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:povijest="http://www.webex.com/schemas/2002/06/service/history">
<serv:header>
<serv:response>
<serv:result> USPJEH</serv:result>
<serv:gsbStatus> PRIMARNI </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> dekan</history:userName>
<history:computerName> 6926 _dean</history:computerName>
<history:clientIP> 10.224.222.183</history:clientIP>
<history:startTime> 29.11.2019 03:05:44</history:startTime>
<history:endTime> 29.11.2019. 03:10:06</history:endTime>
<history:duration> 5</history:duration>
</history:accessAnyWhereInfo>

</serv:body>