Pronađite sve važne informacije koje su vam potrebne o API-u Cisco Webex sastanaka, kao što su promene šeme i druge objave.
Više informacija o XML API 41 potražite u članku Pregled API ispravki za Cisco Webex sastanke (API 41)
Više informacija o XML API 39 i XML API 11 potražite u članku Pregled XML API ispravki za Cisco Webex sastanke (XML API 39 i ranije).
Za ispravke za XML API 11 SP9 i starije verzije posetite lokaciju Cisco DevNet.
Ispravke za API 40.12.0
Ispravke za XML API 40.12.0
XML API podržava tip privatnog sastanka
XML API-je će biti pogođen
Možemo da koristimo API:
CreateMeeting
iSetMeeting
da biste zakazali ili ažurirali Webex sastanak sa tipom privatnog sastanka.Ako je Webex sastanak zakazan sa tipom privatnog sastanka,
GetSessionInfo
GetMeeting
,LstSummarySession
ILstCalendarSession
će vratiti novi element imenovanja jePrivateMeeting
da to saznam.GetMeetingType
iLstMeetingType
vraćanje imenovanja novog elementa
što ukazuje na to da li podržava privatne sastanke ili ne.SupportPrivateMeeting
Promene šeme
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.
Zahtev XML API-ja: CreateMeeting
Zahtev za kreiranjeMeetinga sa tipom 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 će vratiti predloške sastanaka na nivou lokacije
Korisnička priča/opis zadatka
GetSite API da biste vratili predložak sastanka na nivou lokacije. To će omogućiti učionicama za povezivanje obrazovanja i Webex da prikažu ove predloške nastavnicima da izaberu i odaberu ove predloške prilikom zakazivanja njihovih on-line sesija.
API-je je uticalo
Ako postoje prilagođeni predlošci sastanaka koji su na nivou lokacije, GetSite api će vratiti ove predloške na nivou lokacije.
Ime elemenata |
Opis |
---|---|
|
ime prilagođenih predložaka za sastanke na nivou lokacije |
|
Webex sastanci, Webex obuke i Webex događaji |
Promene šeme
GetSite : Dodaj <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 da promeni element supportedServices
kada je sajt CI objedinjena lokacija
Opis
XMLAPI SetUser
ne podržavaj promenu vrednosti od " supportedServices
" u API zahtevu kada je lokacija kontrolno čvorište povezano sa objedinjenim Webex lokacijama za sastanke.
Promene šeme
Nema promene šeme na API-u: SetUser
.
WEBEX-15436: Dodaj zaštitu da bi se izbegle duplirane e-poruke u Mtgconfattendeelist
Opis
Ako se više učesnika koji imaju istu e-poruku dodaju na isti sastanak u istom API zahtevu, obrađujemo samo prvog učesnika e-poštom.
Udarni API-i
CreateMeetingAttendee
CreateUser
SetUser
CreateMeeting
SetMeeting
CreateEvent
SetEvent
CreateTrainingSession
SetTrainingSession
Uzorak API-ja
Zahtev
<?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>
Ispravke za API 40.11.0
Ispravke za XML API 40.11.0
XMLAPI CreateUser podržava ime prikaza
CreateUser
Podržava dispalyname
kada se funkcija preklopi EnableDisplayName
je kao 1. Ako preklopnik funkcije nije 1, onda je displayName
biće ignorisana.
Promene šeme
CreateUser:
XMLAPI setUser podržava ime prikaza
SetUser
Podržava dispalyname
kada se funkcija preklopi EnableDisplayName
je 1. Ako preklopnik funkcije nije 1, displayName
biće ignorisana.
Promene šeme
SetUser:
XMLAPI GetUser podržava ime prikaza
GetUser
Podržava dispalyname
kada se funkcija preklopi EnableDisplayName
je 1. Ako preklopnik funkcije nije 1, displayName
neće biti prikazana.
Kada displayName
u DB je bez vrednosti i preklopnik funkcije EnableDisplayName
je 1, displayName
biće firstName+" "+lastName
za neazijske znakove i firstName+lastName
za azijske znakove.
Promene šeme
GetUserResponse:
KONTROLA XMLAPI korisničkog nivoa za CMR Hybrid Voip
The cmrHybridVoip
postavka se koristi za postavljanje i preuzimanje postavke korisničkog nivoa za EnableCMRHybridVoIP
.
Promene šeme
GetUser Response:
CreateUser Request:
SetUser Request:
Ispravke za API 40.10.0
Ispravke za XML API 40.10.0
XML API support for meeting UUID
u API zahtevu i odgovoru
Uzorak XML API-ja: GetSessionInfo
Zahtev:
<?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>
ApI koji utiče na to:
CreateMeetingAttendee
DelMeetingAttendee
RegisterMeetingAttendee
CreateTeleconferenceSession
SetTeleconferenceSession
GetTeleconferenceSession
CreateTrainingSession
SetTrainingSession
GetTrainingSession
DelTrainingSession
CreateEvent
SetEvent
DelEvent
XMLAPI će vratiti dodatni element za konfiguraciju administratora lokacije da bi onemogućio hvatanje ekrana
Zahtev potiče od obezbeđenja - oba PenTest
bube i mušterije, kao Goldman Saks. Oni ne žele da dozvole krajnjim korisnicima da preuzmu hvatanje ekrana u aplikaciji "Sastanci". U međuvremenu, mnogi drugi kupci žele ovu funkciju - da omoguće hvatanje ekrana. Takođe, korisnici edukacije žele da dozvole i hvatanje ekrana. Dakle, imaćemo konfiguraciju administratora lokacije za ovo, a XMLAPI će vratiti dodatno polje EnableMobileScreenCapture
u odgovoru GetSite
da podržim ovo.
Uzorak GetSite zahteva
<?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>
ApI pogođen
GetSite
XMLAPI podrška MEET-269 PIN-less Poboljšanje pridruživanja
XMLAPI dodajte NEW OPTION Video konferencijske sisteme u mojoj organizaciji mogu da započnu sastanke i pridruže se sastancima bez odziva za sastanak u ličnoj sobi i MC sastanak.
createUser/setUser/getUser
dodavanje novog čmakadeviceCanStartMyPMR
upersonalMeetingRoom
.createMeeting/setMeeting/getMeeting
dodavanje novog čmakadeviceCanStartMeeting
u rasporedu.
Opcija webex UI za sastanak u ličnoj sobi :
Promene šeme
CreateUser:
SetUser:
getUserResponse:
CreateMeeting:
setMeeting:
getMeetingResponse:
API 40.9.0 ispravke
Ispravke za XML API 40.9.0
XML API support for meeting UUID
zahtev i odgovor
Dodali smo UUID sastanka api zahtevu i odgovoru gde god da ga podržimo kao meetingKey
ili sessionKey
.
Uzorak XML API-ja: GetSessionInfo
Zahtev:
<?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>
ApI koji utiče na to:
GetEnrollmentInfo
LstsummaryTrainingSession
AddScheduledTest
SetScheduledTest
DelScheduledTest
GetTestInformation
UploadEventImage
SendInvitationEmail
CreateSupportSession
LstmeetingusagePreliminaryHistory
LstmeetingattendeePreliminaryHistory
LsteventsessionPreliminaryHistory
LsteventattendeePreliminaryHistory
LstTrainingPollResultsHistory
Webex sastanci će imati zaključani lobi za sastanke gde će korisnici moći da sačekaju da budu primljeni na sastanak
XML API planira i uređuje MC sastanak da bi podržao zaključani lobi kada je funkcija( ConsistentLockedLobby
) preklopnik.
Promene šeme
Dodata tri nova elementa ( externalAttendeeSecurity
, autoLock
, autoLockWaitTime
) u CreateMeeting, SetMeeting i GetMeeting API.
Element |
Opis |
---|---|
|
Kada je sastanak otključan, postoje tri stavke spoljne bezbednosti korisnika koje mogu biti izbore.
|
|
Da li ćete automatski zaključati sastanak. Tačno: Automatsko zaključavanje sastanka nakon početka sastanka # minuti nakon početka sastanka Netačno: Ne zaključava sastanak automatski nakon početka sastanka |
|
Minuti (0,5,10,15,20) za automatsko zaključavanje sastanka nakon početka sastanka |
Uzorak zahteva 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 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>
ApI koji utiče na to:
CreateMeeting
SetMeeting
GetMeeting
Poboljšanje GetSessionInfo
API će vratiti status učesnika na sesiji koja je u toku
Dodata dva nova elementa ( hasHostInMeeting
, hasAttendeeInMeeting
) u odgovor GetSessionInfo
. Ova dva elementa će biti vraćena kada sastanak bude u toku.
Element |
Opis |
---|---|
|
Da li se domaćin pridružio sastanku koji je u toku. Tačno: Domaćin je na sastanku koji je u toku. False/Null: Domaćin nije na sastanku koji je u toku ili sastanak nije u toku. |
|
Da li postoji učesnik/domaćin pridružio se sastanku koji je u toku. Tačno: postoji učesnik ili domaćin na sastanku koji je u toku. False/Null: nema učesnika ili domaćina u sastanku koji je u toku ili sastanak nije u toku. |
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>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>
ApI koji utiče na to:
GetSessionInfo
API GetUserCard zahteva odobrenje.
Bezbednosno poboljšanje XML API-ja GetUserCard
zahteva ovlašćenje da bi se dobile informacije o korisniku.
ApI koji utiče na to:
GetUserCard
Ispravke za API 40.8.0
Ispravke za XML API 40.8.0
GetSessionInfo
poboljšanje odgovora
Ako niste pozvani ili odobreni sa sastanka, vaš poziv za XML API: GetSessionInfo
neće vratiti elemente: confName, startDate, duration, timeZone, meetingLink, sipURL, displayMeetingUrl
u telu API odgovora.
PRIMER API odgovora 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>
API primer odgovora za obuke/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&confID=16###92######61</ep:registrationURL>
<ep:passwordReq>true</ep:passwordReq>
<ep:registrationURLForMobile>https://sitename.webex.com/tc3300/trainingcenter/meeting/sessionInfoMobile.do?siteurl=sitename&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>
ApI koji utiče na to:
GetSessionInfo
GetSessionInfo, GetUserCard
Bezbednosna poboljšanja
Poboljšali smo bezbednost na XML API-u GetSessionInfo
i GetUserCard
. Blokiraćemo korisnicima pristup ova dva API-ja u naredna dva sata ako njihov poziv dostigne ograničenje za jedan sat bez pronađenih grešaka.
Odgovor na status greške je: "403 Zabranjeno"
Api-je koji utiču na to:GetSessionInfo
GetUserCard
meetingUUID
u API zahtevu i podršci za odgovor
Dodali smo sastanakUID apI zahtevu i odgovoru gde god da podržimo meetingKey/sessionKey
.
GetSessionInfo
Zahtev:
<?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>
ApI koji utiče na to:
LstOpenSession
GetEnrollmentInfo
LstsummaryMeeting
LstScheduledTests
GetEvent
LstsummaryEvent
LstmeetingusageHistory
LsttrainingsessionHistory
LsteventsessionHistory
LstsupportsessionHistory
DelSession
Predložak edukativnih lokacija (tip EDU sesije) u XML API podršci
Kada vaše lokacije omoguće tip sesije Instruktora obrazovanja (EDU) , XML API može da podrži da se zakaže sastanak sa predloškom sastanka EDU.
ApI koji utiče na to:
CreateMeeting
SetMeeting
CreateEvent
SetEvent
CreateTrainingSession
SetTrainingSession
XML API CreateMeetingAttendee
i RegisterMeetingAttendee
podrška
Oboje CreateMeetingAttendee
i RegisterMeetingAttendee
mogu da provere da li u potrebnom registracionom obrascu učesnika postoji registracija Webex sastanaka.
I postoji novi izuzetak za ovaj zadatak:
Broj izuzetka |
Poruka izuzetka |
---|---|
040014 |
Nedostaju potrebna polja (obrazac za registraciju): ... |
Na primer, ako ste izabrali "Radno mesto" i "Ime kompanije" kao polja zahteva za registraciju Webex sastanaka učesnika kao što je prikazano ispod, onda prilikom pozivanja dva API-ja morate da navedete vrednost na "Radno mesto" i "Ime kompanije": CreateMeetingAttendee
i RegisterMeetingAttendee
.
RegisterMeetingAttendee
Zahtev:
<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
Zahtev:
<bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
<person>
<name>FirstNameA LastNameA</name>
<firstName>FirstNameA</firstName>
<lastName>LastNameA</lastName>
<title>Engineer</title> //Job Title
<company>Cisco1234</company> //Company Name
...
<email>*****@*****.com</email>
<type>VISITOR</type>
<sendReminder>true</sendReminder>
</person>
<role>ATTENDEE</role>
<joinStatus>ACCEPT</joinStatus>
<emailInvitations>true</emailInvitations>
<sessionKey>1###4####1</sessionKey>
040014 Exception of Response
Primer:
<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
<serv:header>
<serv:response>
<serv:result>FAILURE</serv:result>
<serv:reason>Missing required fields (registration form) : title,company</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>040014</serv:exceptionID>
<serv:value>title,company</serv:value>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
ApI koji utiče na to:
CreateMeetingAttendee
RegisterMeetingAttendee
Poboljšanja provere valjanosti XML API e-pošte
XML API ne bi trebalo da dozvoli znakove belog prostora u e-poruci, tako da imamo poboljšanu proveru valjanosti e-pošte da bismo se uskladili sa ponašanjem Webex stranice za sastanke.
ApI koji utiče na to:
CreateMeetingAttendee
CreateEvent
SetEvent
CreateContact
SetContact
SetRecordingInfo
CreateMeetingAttendee
CreateTrainingSession
SetTrainingSession
CreateUser
SetUser
CreateMeeting
SetMeeting
RegisterMeetingAttendee
Ispravke za API 40.7.0
Ispravke za XML API 40.7.0
meetingUUID
podrška
Dodali smo meetingUUID
na API zahtev i odgovor gde god podržavamo ključ sastanka ili ključ sesije.
GetSessionInfo
Primer zahteva:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>xxx</siteName>
<webExID>Test</webExID>
<password>xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey>805325231</sessionKey>
or
<meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>
GetSessionInfo
Primer zahteva:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>xxx</siteName>
<webExID>Test</webExID>
<password>xxx</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey>805325231</sessionKey>
or
<meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>
GetSessionInfo
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:status>NOT_INPROGRESS</ep:status>
<ep:isLocked>false</ep:isLocked>
<ep:sessionkey>805325231</ep:sessionkey>
<ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
<ep:confID>158941507534980823</ep:confID>
...
...
</serv:bodyContent>
</serv:body>
</serv:message>
Api-je koji utiču na to:
LstmeetingattendeeHistory
LsttrainingattendeeHistory
LsteventattendeeHistory
LstsupportattendeeHistory
CreateUser
API pozdravlja podršku za e-poštu za četiri nova jezika
XMLAPI dobrodošlica html e-poštom podržava sledeća četiri nova jezika:
češki (ID jezika=19)
poljski (jezikID=20)
mađarski (ID jezika=21)
rumunski (iD jezika=22)
XMLAPI šalje e-poruku dobrodošlice u skladu sa jezikom ili ID-om jezika u CreateUser
Zahtev.
Koristite CreateUser
da biste poslali Html primer 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>
API 40.6.1, 40.4.9 Ispravke
Ispravke za XML API 40.6.1, 40.4.9
CreateMeeting/SetMeeting
podrška
Kada planirate Webex sastanak, XML API CreateMeeting/SetMeeting
vam omogućava da proverite ili opozovite ili kliknete na potrebno ili ne zahtevano polje iz registracionog obrasca učesnika.
Sledi uzorak rasporeda sastanaka sa veb stranice korisnika na kojoj možete da proverite obavezna polja kao što su "Radno mesto", "Ime preduzeća","Grad" i "Stanje" u registracionom obrascu učesnika:
Sledi mapiranje između polja stranice i elemenata XML API-ja:
Polja stranice | XMLAPI Element |
---|---|
Radno mesto | <title> |
Ime kompanije | <company> |
Adresa 1 | <address1> |
Adresa 2 | <address2> |
Grad | <city> |
Stanje | <state> |
Poštanski broj | <postalCode> |
Grad/regija | <country> |
Telefon na poslu | <phone> |
Faks | <fax> |
Promenjena šema: Dodaj "registrationForm" element u CreateMeeting
Promenjena šema: Dodaj "registrationForm" element u SetMeeting
Promenjena šema: Dodaj "registrationForm" element u GetMeeting
CreateMeeting
Primer zahteva:
<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>
SetMeeting
Primer zahteva:
<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>
GetMeeting
Primer 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>
Api-je koji utiču na to:
CreateMeeting
SetMeeting
GetMeeting
DelMeeting
Tip sastanka E2EE ne podržava PMR sastanak
Kada omogućite PMR tokom poziva sa API-jem: CreateUser/SetUser/GetUser/GetMe
a samo E2EE tip sastanka je avalibilan, odgovoriće na sledeću poruku o grešci: "110063 Korisnik mora da ima najmanje jedan tip sastanka koji nije E2EE da bi omogućio PMR."
Api-je koji utiču na to:
CreateUser
SetUser
GetUser
GetMe
Ispravke za API 40.6.0
Ispravke za XML API 40.6.0
Dodata uloga korisničkog menadžmenta
Kreirali smo ulogu korisničkog menadžmenta i datoteka šeme za sledeće je promenjena.
Promenjena šema: CreateUser
Zahtev:
Promenjena šema: SetUser
Promenjena šema: GetMe
Odgovor:
Promenjena šema: LstsummaryUser
Odgovor:
Api-je koji utiču na to:
CreateUser
SetUser
GetMe
LstsummaryUser
CreateUser
Primer zahteva:
<?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 pomoću API ključa pristupi GetUserCard
Sada podržavamo korišćenje API ključa (generisani JWT token) pristupa API-u: GetUserCard
u ovom izdanju.
Možete da pogledate ove stranice o primeni jednog API ključa i da generišete JWT simbol:
GetUserCard
Primer zahteva:
POST https://{sitename}.webex.com/WBXService/XMLService
Header:
Content-Type application/json;charset=utf-8
JWTToken ${jwttoken}
Body:
<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
<securityContext>
<siteName>{sitename}</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.GetUserCard">
<webExId>{userName}</webExId>
</bodyContent>
</body>
</message>
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:use="http://www.webex.com/schemas/2002/06/service/user">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="use:getUserCardResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<use:avatar>
<use:url>https://xxxx.webex.com/svc3300/svccomponents/html/img/avatar160.png</use:url>
<use:lastModifiedTime>1587493389768</use:lastModifiedTime>
<use:isUploaded>false</use:isUploaded>
</use:avatar>
<use:personalMeetingRoom>
<use:title>Test's Personal Room</use:title>
<use:personalMeetingRoomURL>https://xxxx.webex.com/meet/Test</use:personalMeetingRoomURL>
<use:accessCode>713289692</use:accessCode>
</use:personalMeetingRoom>
</serv:bodyContent>
</serv:body>
</serv:message>
Podrška za meetingUUID
u API zahtevu i odgovoru
Dodali smo meetingUUID
na API zahtev i odgovor kada podržavamo ključ sastanka ili ključ sesije.
Api-je koji utiču na to:
LstRecording
LstsummarySession
GetSesssionInfo
GethosturlMeeting
GetjoinurlMeeting
LstMeetingAttendee
CreateMeeting
SetMeeting
GetMeeting
DelMeeting
LstCalendarSession
meetingUUID
Primer zahteva:
<?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>
meetingUUID
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:status>NOT_INPROGRESS</ep:status>
<ep:isLocked>false</ep:isLocked>
<ep:sessionkey>805325231</ep:sessionkey>
<ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
<ep:confID>158941507534980823</ep:confID>
...
...
</serv:bodyContent>
</serv:body>
</serv:message>
PMR ključevi za sastanak neće biti promenjeni iz privremeno deaktiviranog korisnika ili onemogućenog PMR-a
Kada se privremeno deaktivirani korisnik ili onemogućeni PMR ponovo aktivira u roku od nedelju dana, sada ponovo aktivirani korisnik ili omogućen taster PMR za sastanak se ne menja, biće isti kao i ranije.
Api-je koji utiču na to:
SetUser
DelUser
LstSummarySession
Poboljšanja
Poboljšali smo API: LstSummarySession
return scheduled-PMR to have one new element, returnScheduledPMR
, u zahtevu. A podrazumevani preklopnik funkcije je isključen.
Api-je koji utiču na to:
LstSummarySession
Promena šeme:
Dodajemo novo ime elementa returnScheduledPMR
u zahtevu API LstSummarySession.
Dodajemo novo ime elementa isScheduledPMR
u apI LstSummarySession odgovor.
LstSummarySession
Primer zahteva:
<?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>
LstSummarySession
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
<serv:header>
<serv:response>
<serv:result>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
preklopnik funkcije odgovora SupportXMLAPIReturnScheduledPMR
Api-je koji utiču na to:
GetSite
Promena šeme:
The XML API GetSite
odgovor novi element je: SupportXMLAPIReturnScheduledPMR
GetSite
Primer zahteva:
<?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>
GetSite
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="ns1:getSiteResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns1:siteInstance>
<ns1:siteCommonOptions>
...
<ns1:SupportXMLAPIReturnScheduledPMR>true</ns1:SupportXMLAPIReturnScheduledPMR>
...
</ns1:siteCommonOptions>
</ns1:siteInstance>
</serv:bodyContent>
</serv:body>
</serv:message>
API 40.4.8, 40.2.9 Ispravke
Ispravke za XML API 40.4.8, 40.2.9
Novi odgovor prilikom ažuriranja planiranih sastanaka u XMLAPI
Kada klijenti koriste XMLAPI za ažuriranje sastanaka zakazanih putem njihove stranice, poslaćemo numeričku lozinku u ispravki e-pošte za sastanak i primeniti je na Webex centre za sastanke, timove i događaje.
Ti API-i: GetMeeting, GetTrainingSession, GetEvent
i GetTeleconferenceSession
, imaće ove nove elemente kao odgovor: audioPassword
(numerička lozinka), isEnforceAudioPassword
, isEnforceAudioLogin
za Webex centre za sastanke, timove i događaje.
Promenjena šema:
Api-je koji utiču na to:
GetMeeting
GetTrainingSession
GetEvent
GetTeleconferenceSession
GetMeeting
Primer zahteva:
<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>testSite</siteName>
<webExID>test</webExID>
<password>xxx</password>
<partnerID>xx</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.GetMeeting">
<meetingKey>803328224</meetingKey>
</bodyContent>
</body>
</serv:message>
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="meet:getMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<meet:accessControl>
<meet:listToPublic>false</meet:listToPublic>
<meet:isPublic>false</meet:isPublic>
<meet:meetingPassword>PkzC8tP7kM5</meet:meetingPassword>
<meet:audioPassword>75928877</meet:audioPassword>
<meet:isEnforceAudioPassword>true</meet:isEnforceAudioPassword>
<meet:isEnforceAudioLogin>false</meet:isEnforceAudioLogin>
</meet:accessControl>
...
...
</serv:bodyContent>
</serv:body>
</serv:message>
API 40.4.5, 40.2.6 Ispravke
Ispravke za XML API 40.4.5, 40.2.6
GetUserCard
i GetSessionInfo
ograničenje upotrebe
Primenjujemo ograničenje upotrebe na API-u GetUserCard
i GetSessionInfo
, možete dobiti poruku o grešci: "403 zabranjeno" ako dostignete ograničenje upotrebe.
Api-je koji utiču na to:
GetUserCard
GetSessionInfo
API 40.4.4, 40.2.5 Ispravke
Ispravke za XML API 40.4.4, 40.2.5
BodyContent
ograničenje broja
Dodali smo ograničen broj BodyContent
u svakom XML API odeljku. Kada dodate previše BodyContent
u API zahtevu, vratiće se sledeći kôd greške i poruka: "000053 Broj BodyContent-a u zahtevu mora biti manji od {number}"
Api-je koji utiču na to:
Bilo koji XML API
XML API zahtev sa više BodyContent
Primer:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<webExID>xxxx</webExID>
<password>xxxx</password>
<siteName>xxx</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.GetUser">
<webExId>xxx</webExId>
</bodyContent>
<bodyContent xsi:type="java:com.webex.service.binding.user.GetSite">
</bodyContent>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey>801020403</sessionKey>
</bodyContent>
</body>
</serv:message>
API 40.4.3, 40.2.4 Ispravke
Ispravke za XML API 40.4.3, 40.2.4
Kliknite ovde da biste preuzeli XML API 40.4.3, 40.2.4 šemu.
CreateUser
Poboljšanja
Poboljšali smo CreateUser
da biste podržali e-poruku dobrodošlice na više jezika. The CreateUser
sada zahtevi isHTMLEmail
Api-je koji utiču na to:
CreateUser
CreateUser
Primer zahteva:
<?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>
API 40.4.0 ispravke
Ispravke za XML API 40.4.0
Primena provere e-pošte prilikom promene e-pošte u XML API
Nakon što je administrator lokacije omogućio potvrdu potrebnu korisniku za ažuriranje e-adrese u administraciji Webex lokacije:
Ako nalog administratora koji nije lokacija zove
SetUser
API da biste promenili e-adrese, trenutna e-pošta ostaje dok se nova e-pošta ne proveri. E-poruka sa potvrdom o promeni naloga se šalje na novu e-adresu sa "Potvrda promene Webex naloga". Nakon što kliknete na vezu u e-poruci da biste potvrdili, nova e-adresa je odmah povezana.Ako administrator koji nije lokacija zove
SetUser
API nekoliko puta bez završetka procesa verifikacije e-pošte, trenutna e-pošta se čuva, a najnovija nova e-pošta je ona koja mora biti verifikovana.Ako nalog administratora lokacije pozove
SetUser
API da biste promenili e-adrese, proces verifikacije e-pošte nije aktiviran. Nova e-pošta će odmah biti povezana sa nalogom domaćina ili učesnika.
Api-je koji utiču na to:
SetUser
GetEnrollmentInfo
uspostavljanje početnih vrednosti vremenskog perioda i veze
The GetEnrollmentInfo
API trenutno traži IP adrese na sistemu imena domena, što pokreće ogromne uticaje performansi. Planiramo da pojednostavimo ovaj proces, sa praznim odgovorom u <domain>
Polje.
Api-je koji utiču na to:
GetEnrollmentInfo
GetEnrollmentInfo
Primer zahteva:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>sqdemo6</siteName>
<webExID>xxx</webExID>
<password>xxxx</password>
<partnerID>webexpartner</partnerID>
</securityContext>
</header>
<body>
<bodyContent
xsi:type="java:com.webex.service.binding.attendee.GetEnrollmentInfo">
<sessionKey>716773566</sessionKey>
</bodyContent>
</body>
</serv:message>
GetEnrollmentInfo
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="att:getEnrollmentInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<att:session>
<att:confID>154279066999981548</att:confID>
<att:attendee>
<att:attendeeID>3191792</att:attendeeID>
<att:enrollFields>
<att:defaultFields>
<att:firstName>Alex</att:firstName>
<att:lastName>Yang</att:lastName>
<att:email>omega.alex.yang@gmail.com</att:email>
<att:company></att:company>
<att:phoneNum></att:phoneNum>
<att:title></att:title>
<att:receiveInfo>false</att:receiveInfo>
<att:address1></att:address1>
<att:address2></att:address2>
<att:city></att:city>
<att:state></att:state>
<att:zipcode></att:zipcode>
<att:country></att:country>
<att:leadSourceID></att:leadSourceID>
<att:leadScore>0.0</att:leadScore>
</att:defaultFields>
<att:customFields/>
</att:enrollFields>
<att:domain> </att:domain>
<att:ipAddress>10.35.240.53</att:ipAddress>
<att:submitTime>02/27/2020 22:03:57</att:submitTime>
<att:status>APPROVED</att:status>
</att:attendee>
<att:attendee>
<att:attendeeID>3191797</att:attendeeID>
<att:enrollFields>
<att:defaultFields>
<att:firstName>AlexKKK</att:firstName>
<att:lastName>Test</att:lastName>
<att:email>achillesyang@hotmail.com</att:email>
<att:company></att:company>
<att:phoneNum></att:phoneNum>
<att:title></att:title>
<att:receiveInfo>false</att:receiveInfo>
<att:address1></att:address1>
<att:address2></att:address2>
<att:city></att:city>
<att:state></att:state>
<att:zipcode></att:zipcode>
<att:country></att:country>
<att:leadSourceID></att:leadSourceID>
<att:leadScore>0.0</att:leadScore>
</att:defaultFields>
<att:customFields/>
</att:enrollFields>
<att:domain> </att:domain>
<att:ipAddress>10.154.181.15</att:ipAddress>
<att:submitTime>02/27/2020 22:07:38</att:submitTime>
<att:status>APPROVED</att:status>
</att:attendee>
<att:matchingRecords>
<serv:total>2</serv:total>
<serv:returned>2</serv:returned>
<serv:startFrom>1</serv:startFrom>
</att:matchingRecords>
<att:sessionKey>716773566</att:sessionKey>
</att:session>
</serv:bodyContent>
</serv:body>
</serv:message>
Ispravke za API 40.2.0
Ispravke za XML API 40.2.0
Uklanjanje anonimnog pristupa LstSummarySession
Kao bezbednosno poboljšanje, zaustavljamo podršku za anonimni pristup LstSummarySession
API. Ako Webex sastanci anonimno pristupe API-u, dobija se sledeći kôd greške i poruka: "000015 izvini, nije pronađen nikakav zapis."
Api-je koji utiču na to:
LstSummarySession
LstSummarySession
Primer zahteva:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>sitename1</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.LstsummarySession">
<sessionKey>211894651</sessionKey>
</bodyContent>
</body>
</serv:message>
LstSummarySession
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
<serv:header>
<serv:response>
<serv:result>FAILURE</serv:result>
<serv:reason>Sorry, no record found</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>000015</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
CreateMeeting
i SetMeeting
bezbednosna poboljšanja
Ova promena je izvršena u XML API 40.2.0, ali je njen opis uređen nakon prijema povratnih informacija korisnika. |
Kao bezbednosno poboljšanje, ažurirali smo CreateMeeting
i SetMeeting
API-je ne dozvoljava korisnicima da zakažu vreme početka sastanka koje je već prošlo. Ako pokušaju, API će zatražiti poruku o grešci: "060016 početka sesije trebalo bi da bude kasnije od trenutnog vremena." Ako korisnik treba da zakaže trenutni sastanak, preporučujemo da vreme početka sastanka bude podešeno pet minuta kasnije od trenutnog vremena.
Api-je koji utiču na to:
CreateMeeting
SetMeeting
API 40.1.2 ispravke
Ispravke za XML API 40.1.2
Planiranje sastanka automatski generiše lozinku ako nije obezbeđena
Pojačali smo CreateMeeting
, CreateEvent
, CreateTrainingSession
I CreateTeleconferenceSession
da biste uključili lozinku u telo API odgovora.
Podrazumevano, svi sastanci/događaji/sesija moraju imati omogućenu postavku lozinke. U ovom slučaju, ako API zahtev ne sadrži lozinku, lozinka se automatski generiše sa XML API servera.
Ako svi sastanci/događaji/sesija moraju da imaju postavku lozinke je onemogućena , a API zahtev ne sadrži lozinku, lozinka se ne generiše sa XML API servera.
Ako API zahtev sadrži lozinku, odgovor će uključiti tu lozinku, bez obzira na sve sastanke/događaje/sesiju koja mora imati postavku lozinke koja je omogućena ili onemogućena.
Api-je koji utiču na to:
CreateMeeting
CreateEvent
CreateTrainingSession
CreateTeleconferenceSession
The CreateMeeting
odgovor sada ima meetingPassword
Element:
CreateMeeting
Primer zahteva:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>siteName1</siteName>
<webExID>userID</webExID>
<password>*****</password>
<partnerID>webexpartner</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.meeting.CreateMeeting">
<metaData>
<confName>Test_Auto_Generated_mtg_pwd</confName>
<meetingType>3</meetingType>
</metaData>
<schedule>
<startDate>10/28/2020 17:35:00</startDate>
</schedule>
</bodyContent>
</body>
</serv:message>
CreateMeeting
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting" xmlns:att="http://www.webex.com/schemas/2002/06/service/attendee">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="meet:createMeetingResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<meet:meetingkey>806745263</meet:meetingkey>
<meet:meetingPassword>UzXJuzUD428</meet:meetingPassword>
<meet:iCalendarURL>
<serv:host>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=md225d5935256319ef21b71dd8ebd0640</serv:host>
<serv:attendee>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=m26bf5e25ca587d32302fb29951b92e15</serv:attendee>
</meet:iCalendarURL>
<meet:guestToken>cfc7f3246d4862f1bb69b803e8615b7a</meet:guestToken>
</serv:bodyContent>
</serv:body>
</serv:message>
The CreateEvent
odgovor sada ima eventPassword
Element:
The CreateTrainingSession
i CreateTeleconferenceSession
odgovori sada imaju sessionPassword
Element:
Ispravke za API 40.1.0
Ispravke za XML API 40.1.0
GetSessionInfo
Poboljšanja
Dodali smo nove elemente u GetSessionInfo
API. API sada vraća informacije i za mobilne uređaje.
Api-je koji utiču na to:
GetSessionInfo
GetSessionInfo
Zahtevaj ispravke:

Primer zahteva:
<?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 iz izveštaja Webex Access Anywhere.
Api-je koji utiču na to:
LstAccessAnywhereHistory
LstAccessAnywhereHistory
Zahtevaj ispravke:

LstAccessAnywhereHistory
Ispravke odgovora:

Primer zahteva:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>sqdemo6</siteName>
<webExID>test</webExID>
<password>P@ss1234</password>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.history.LstAccessAnywhereHistory">
<hostWebexID>test1</hostWebexID>
<startTimeScope>
<sessionStartTimeStart>09/29/2019 00:42:34</sessionStartTimeStart>
<sessionStartTimeEnd>12/29/2019 04:42:34</sessionStartTimeEnd>
</startTimeScope>
<endTimeScope>
<sessionEndTimeStart>9/29/2019 02:42:34</sessionEndTimeStart>
<sessionEndTimeEnd>12/29/2019 05:42:34</sessionEndTimeEnd>
</endTimeScope>
<listControl>
<serv:startFrom>1</serv:startFrom>
<serv:maximumNum>10</serv:maximumNum>
<serv:listMethod>OR</serv:listMethod>
</listControl>
<order>
<orderBy>STARTTIME</orderBy>
<orderAD>ASC</orderAD>
</order>
</bodyContent>
</body>
</serv:message>
Primer odgovora:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message
xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xmlns:com="http://www.webex.com/schemas/2002/06/common"
xmlns:history="http://www.webex.com/schemas/2002/06/service/history">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="history:LstAccessAnywhereHistoryResponse"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<history:matchingRecords>
<serv:total>775</serv:total>
<serv:returned>10</serv:returned>
<serv:startFrom>1</serv:startFrom>
</history:matchingRecords>
<history:accessAnyWhereInfo>
<history:confID>123456</history:confID>
<history:userName>dean</history:userName>
<history:computerName>6926_dean</history:computerName>
<history:clientIP>10.224.222.183</history:clientIP>
<history:startTime>11/29/2019 03:05:44</history:startTime>
<history:endTime>11/29/2019 03:10:06</history:endTime>
<history:duration>5</history:duration>
</history:accessAnyWhereInfo>
</serv:bodyContent>
</serv:body>
</serv:message>