For yderligere oplysninger om XML API 39 og XML API 11, se Oversigt over Cisco WEBEX MEETINGS XML API-opdateringer (XML api 39 og tidligere).

For opdateringer til XML API 11 SP9 og tidligere skal du gå til Cisco DevNet.

API 40.8.0-opdateringer

XML API 40.8.0-opdateringer

Klik her for at downloade XML API 40.8.0-skemaet

GetSessionInfo- svar forbedring

Hvis du ikke er inviteret eller godkendt fra mødet, er dit opkald til XML API: GetSessionInfo vil ikke returnere elementerne: confName, startdate, duration, timeZone, meetingLink, sipURL, displayMeetingUrl i API-svar brødteksten.

API-svar eksempel til møder:

<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 ikke angivet</ep:sessionkey>
    <ep:accessControl>
        <ep:listStatus></ep:listStatus>
        <ep:registration>False</ep:registration>
        <ep:passwordReq>True</ep:passwordReq>
        <ep:isRegisterIDRequired>falsk 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>sand</ep:isAllowJBH>
    <ep:isCETMeeting></ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>falsk false</ep:isPersonalMeetingRoom>
</serv:bodyContent>

API svar eksempel for undervisning/begivenheder:

<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 ikke angivet</ep:sessionkey>
    <ep:accessControl>
        <ep:listStatus></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>Inviter/Tilmeld/Afvis</ep:joinStatus>
        <ep:isRegisterIDRequired>falsk</ep:isRegisterIDRequired>
    </ep:accessControl>
    <ep:metaData>
        <ep:serviceType>trainingcenter</ep:serviceType>
    </ep:metaData>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>falsk</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>sand</ep:isAllowJBH>
    <ep:isCETMeeting>sand</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom></ep:isPersonalMeetingRoom>
</serv:bodyContent>

Berørt API:

  • GetSessionInfo

GetSessionInfo, GetUserCard-sikkerhedsforbedringer

Vi har en sikkerhedsforbedring på XML API- GetSessionInfo og GetUserCard. Vi vil blokere brugere fra at tilgå disse to API'er i de næste to timer, hvis deres opkald nåede grænsen på en time uden data fundet fejl.

Fejlstatus svaret er: "403 forbudt"

Påvirkede API'er:

  • GetSessionInfo

  • GetUserCard

meetingUUID i support til API-anmodning og-svar

Vi har tilføjet meetingUUID til API-anmodningen og svaret, hvor vi understøtter en meetingKey/sessionKey.

GetSessionInfo anmodning:

<?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> eller <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

Svar:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns: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>Vellykket</serv:result>
            <serv:gsbStatus>primær</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>falske</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID> ... ... </serv:bodyContent>
    </serv:body>
</serv:message>

Berørt API:

  • LstOpenSession

  • GetEnrollmentInfo

  • LstsummaryMeeting

  • LstScheduledTests

  • GetEvent

  • LstsummaryEvent

  • LstmeetingusageHistory

  • LsttrainingsessionHistory

  • LsteventsessionHistory

  • LstsupportsessionHistory

  • DelSession

Undervisnings webstedsskabelon (EDU sessionstype) i XML API-support

Når dine websteder har aktiveret undervisnings instruktør (EDU) sessionstype, kan XML API hjælpe med at planlægge et møde med EDU-mødeskabelon.

Berørt API:

  • Oprettelse af møde

  • SetMeeting

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

XML API- CreateMeetingAttendee og RegisterMeetingAttendee- support

Både CreateMeetingAttendee og RegisterMeetingAttendee er i stand til at kontrollere den påkrævede mødedeltagertilmelding formular til en Webex Meetings registrering.

Og der er en ny undtagelse for denne opgave:

Undtagelses nummer

Undtagelsesmeddelelse

040014

Manglende obligatoriske felter (tilmeldingsformular): ...

Hvis du for eksempel valgte "stillings titel" og "Virksomhedsnavn" som felterne Kræv, at en mødedeltager Webex Meetings tilmelding som vist herunder, skal du opgive værdien i "stillings titlen" og "Virksomhedsnavn", når du ringer til de to API'er: CreateMeetingAttendee og RegisterMeetingAttendee.

This image 449144.jpg is not available in preview/cisco.com

RegisterMeetingAttendee anmodning:

<body>        
        <bodyContent xsi:type="java:com.webex.service.binding.attendee.RegisterMeetingAttendee">
            <attendees>
                <person>
                    <name>FirstNameb efter navn</name>
                    <firstName>FirstNameb</firstName>
                    <lastName>efter navn</lastName>
                    <title>Ingeniør</title> Stillingsbetegnelse <company>Cisco1234</company> //Company navn... <email>@ * * * * *. com</email>              
                    <type>besøgende er</type>
                    <sendReminder>ægte</sendReminder>
                </person>
                <role>mødedeltager</role>
                <joinStatus>Accepter</joinStatus>
                <emailInvitations>ægte</emailInvitations>
                <sessionKey>1 # # # #4 # # # #1</sessionKey>
            </attendees>
        </bodyContent>  
    </body>
</serv:message>

CreateMeetingAttendee anmodning:

<bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
        <person>
            <name>Fornavna efter navn,</name>
            <firstName>fornavn, efter</firstName>
            <lastName>navn</lastName>
            <title>Ingeniør</title> Stillingsbetegnelse <company>Cisco1234</company> //Company navn... <email>@ * * * * *. com</email>
            <type>besøgende er</type>
            <sendReminder>ægte</sendReminder>
        </person>
    <role>mødedeltager</role>
    <joinStatus>Accepter</joinStatus>
    <emailInvitations>ægte</emailInvitations>
    <sessionKey>1 # # #4 # # # #1</sessionKey>

040014 undtagelse af svareksempel:

<?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>Fejl</serv:result>
            <serv:reason>mangler påkrævede felter (tilmeldingsformular): titel, virksomhedens</serv:reason>
            <serv:gsbStatus>primære</serv:gsbStatus>
            <serv:exceptionID>040014</serv:exceptionID>
            <serv:value>titel, virksomhed</serv:value>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Berørt API:

  • CreateMeetingAttendee

  • RegisterMeetingAttendee

Forbedringer af XML API-e-mail validering

XML API bør ikke tillade hvide mellemrumstegn i en e-mail, så vi har forbedret e-mail validering for at justere med Webex Meetings side adfærd.

Berørt API:

  • CreateMeetingAttendee

  • CreateEvent

  • SetEvent

  • CreateContact

  • SetContact

  • SetRecordingInfo

  • CreateMeetingAttendee

  • CreateTrainingSession

  • SetTrainingSession

  • CreateUser

  • SetUser

  • Oprettelse af møde

  • SetMeeting

  • RegisterMeetingAttendee

API 40.7.0-opdateringer

XML API 40.7.0-opdateringer

Klik her for at downloade XML API 40.7.0-skemaet

meetingUUID- support

Vi har tilføjet meetingUUID til API-anmodningen og svaret, hvor vi understøtter en MeetingKey eller sessionKey.

GetSessionInfo- anmodnings eksempel:

<?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> eller <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

GetSessionInfo- anmodnings eksempel:

<?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> eller <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

GetSessionInfo svar eksempel:

<?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>Vellykket</serv:result>
            <serv:gsbStatus>primær</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>falske</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID> ... ... </serv:bodyContent>
    </serv:body>
</serv:message>

Påvirkede API'er:

  • LstmeetingattendeeHistory

  • LsttrainingattendeeHistory

  • LsteventattendeeHistory

  • LstsupportattendeeHistory

Velkomst-e-mail support til CreateUser API til fire nye sprog

XMLAPI-velkomst-HTML-e-mailen understøtter følgende fire nye sprog:

  • Tjekkisk (languageID = 19)

  • Polsk (languageID = 20)

  • Ungarsk (languageID = 21)

  • Rumænsk (languageID = 22)

XMLAPI sender velkomst-e-mailen i henhold til sproget eller languageID i CreateUser- anmodningen.

Brug af CreateUser til at sende eksempel på HTML-velkomstmail (tjekkisk):

<?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>bruger</lastName>
                <webExId>testuser</webExId>
                <password>XXXXXX</password>
                <email>testuser@test.com</email>
                <privilege>
                    <host>True</host>
                </privilege>
                <languageID>19</languageID> eller <language>tjekkisk</language>
                <active>aktiveret</active>
                <sendWelcome>True</sendWelcome>
                <isHTMLEmail>True</isHTMLEmail>
            </bodyContent>
        </bodyContent>
    </body>
</serv:message>

This image 447638.jpg is not available in preview/cisco.com

API 40.6.1, 40.4.9-opdateringer

XML API-40.6.1, 40.4.9-opdateringer

Klik her for at downloade XML API 40.6.1-skemaet

Klik her for at downloade XML API 40.4.9-skemaet

Oprettelse af møde/SetMeeting- support

Når du planlægger et Webex-møde, tillader XML API oprettelse af møde/SetMeeting dig at markere eller fjerne markering af eller klikke på et påkrævet eller ikke påkrævet felt fra mødedeltagertilmelding-formularen.

Følgende er eksempler på møder, der planlægges fra bruger websiden, hvor du kan markere obligatoriske felter som "stillings titel", "virksomhedsnavn", "by"og "tilstand" på mødedeltagertilmelding formularen:

This image 447432-3.jpg is not available in preview/cisco.com

Følgende er en tilknytning mellem sidefelter og XML API-elementer:

Sidefelter XMLAPI-element
Jobtitel 
<title>
Virksomhedsnavn 
<company>
Adresse 1 
<address1>
Adresse 2 
<address2>
By 
<city>
Stat 
<state>
Postnummer 
<postalCode>
Land/område 
<country>
Arbejdstelefon 
<phone>
Fax 
<fax>

Ændret skema: Tilføj "registrationForm"-element i oprettelse af møde

This image 447433.jpg is not available in preview/cisco.com

Ændret skema: Tilføj "registrationForm"-element i SetMeeting

This image 447434.jpg is not available in preview/cisco.com

Ændret skema: Tilføj "registrationForm"-element i GetMeeting

This image 447435.jpg is not available in preview/cisco.com

Oprettelse af møde-anmodnings eksempel:

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

SetMeeting-anmodnings eksempel:

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

    <metaData>
        <confName>Konferencenavn</confName>
        <meetingType>3</meetingType>
    </metaData>
    
    <attendeeOptions>
        <emailInvitations>sand</emailInvitations>
        <registration>for</registration>
        <auto>sand</auto>
    </attendeeOptions>
    
    <registrationForm>
        <title><req>sand</req></title>    
        <company><req>sand</req></company>    
        <address1><req>falsk</req></address1>
        <address2><req>falsk false sand</req></address2>
        <city><req></req></city>          
        <state><req></req></state>        
        <postalCode><req>falsk</req></postalCode>
        <country><req>falsk</req></country>
        <phone><req></req></phone>
        <fax><req>falsk falsk falsk</req></fax>
    </registrationForm>

GetMeetingsvar eksempel:

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

Påvirkede API'er:

  • Oprettelse af møde

  • SetMeeting

  • GetMeeting

  • DelMeeting

E2EE-mødetype understøtter ikke et PMR møde

Når du aktiverer en PMR under et opkald med API'erne:CreateUser/SetUser/GetUser/GetMe, og kun en E2EE-mødetype er tilgængelig, vil den besvare følgende fejlmeddelelse: "110063 brugeren skal have mindst én ikke-E2EE mødetype for at aktivere PMR."

Påvirkede API'er:

  • CreateUser

  • SetUser

  • GetUser

  • GetMe

API 40.6.0-opdateringer

XML API 40.6.0-opdateringer

Klik her for at downloade XML API 40.6.0-skemaet

Bruger administrations rolle tilføjet

Vi har oprettet bruger administrations rollen, og skemafilen for følgende er ændret.

Ændret skema: CreateUseranmodning:

This image 446561.jpg is not available in preview/cisco.com

Ændret skema: SetUser

This image 446562.jpg is not available in preview/cisco.com

Ændret skema: GetMe-svar:

This image 446563.jpg is not available in preview/cisco.com

Ændret skema: LstsummaryUser-svar:

This image 446564.jpg is not available in preview/cisco.com

Påvirkede API'er:

  • CreateUser

  • SetUser

  • GetMe

  • LstsummaryUser

CreateUser-anmodnings eksempel:

<?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>webstedsadministrator</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>ægte</umSiteAdmin>
        <host>falsk</host>

        <siteAdmin>falsk</siteAdmin>
        <labAdmin>falsk</labAdmin>
        <voiceOverIp>falsk</voiceOverIp>
    </privilege>
    <languageID>3</languageID>
    <active>aktiveret</active>
    <sendWelcome>True</sendWelcome>
    <isHTMLEmail>True</isHTMLEmail>
</bodyContent>  
</body>
</serv:message>

Support, der bruger API-nøgle adgang til GetUserCard

Vi understøtter nu brug af API-nøglen (genereret JWT token) adgang til API'EN: GetUserCard i denne udgivelse.

Du kan henvise til disse sider for at anvende én API-nøgle og til at generere et JWT-token:

Sådan anvendes en API-nøgle

Sådan genererer du JWT-token

GetUserCard-anmodnings eksempel:

Bogfør https://{sitename}. Webex. com/WBXService/XMLService-header: Content-type applikation/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>Brugernavn</webExId>
    </bodyContent>
</body>
</message>  

Svar eksempel:

<?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>Vellykket</serv:result>
            <serv:gsbStatus>primær</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>falsk</use:isUploaded>
            </use:avatar>
            <use:personalMeetingRoom>
                <use:title>test 's personlige lokale</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>

Support til meetingUUID i API-anmodning og-svar

Vi har tilføjet meetingUUID til API-anmodningen og-svaret, når vi understøtter en MeetingKey eller sessionKey.

Påvirkede API'er:

  • LstRecording

  • LstsummarySession

  • GetSesssionInfo

  • GethosturlMeeting

  • GetjoinurlMeeting

  • LstMeetingAttendee

  • Oprettelse af møde

  • SetMeeting

  • GetMeeting

  • DelMeeting

  • LstCalendarSession

meetingUUID-anmodnings eksempel:

<?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> eller <meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</meetingUUID>
</bodyContent>
</body>
</serv:message>

meetingUUIDsvar eksempel:

<?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>Vellykket</serv:result>
            <serv:gsbStatus>primær</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>falske</ep:isLocked>
            <ep:sessionkey>805325231</ep:sessionkey>
            <ep:meetingUUID>039c00dd25c64ab0812dda22bb8a4fcc</ep:meetingUUID>
            <ep:confID>158941507534980823</ep:confID> ... ... </serv:bodyContent>
    </serv:body>
</serv:message>

PMR møde nøgler vil ikke blive ændret fra en midlertidigt deaktiveret bruger eller deaktiveret PMR

Når en midlertidig deaktiveret bruger eller deaktiveret PMR genaktiveres inden for en uge, vil den nu aktiverede bruger eller aktiveret PMRens Mødenøgle ikke ændres, den vil være den samme som før.

Påvirkede API'er:

  • SetUser

  • DelUser

LstSummarySession- forbedringer

Vi har forbedret API: LstSummarySession returnerede planlagte-PMR for at have ét nyt element, returnScheduledPMR, i anmodningen. Og funktion til eller fra standard er slået fra.

Påvirkede API'er:

  • LstSummarySession

Skemaændring:

Vi tilføjer et nyt elementnavn returnScheduledPMR i API-LstSummarySession anmodningen.

Vi tilføjer et nyt elementnavn isScheduledPMR i API-LstSummarySession-svaret.

LstSummarySession-anmodnings eksempel:

<?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>Og</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>Start</orderBy>
            <orderAD>-</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>

LstSummarySessionsvar eksempel:

<?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>Succes for</serv:result>
         <serv:gsbStatus>primær</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-</ep:confName>
            <ep:sessionType>3</ep:sessionType>
            <ep:serviceType>MeetingCenter test test test</ep:serviceType>
            <ep:hostWebExID></ep:hostWebExID>
            <ep:hostFirstName></ep:hostFirstName>
            <ep:hostLastName></ep:hostLastName>
            <ep:otherHostWebExID></ep:otherHostWebExID>
            <ep:timeZoneID>2</ep:timeZoneID>
            <ep:timeZone>GMT-10:00, Hawaiiansk (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>offentlig</ep:listStatus>
            <ep:hostEmail>test@webex.com</ep:hostEmail>
            <ep:passwordReq>sand</ep:passwordReq>
            <ep:hostJoined>falsk</ep:hostJoined>
            <ep:participantsJoined>falsk falsk falsk false falsk falsk</ep:participantsJoined>
            <ep:confID>141672157056861215</ep:confID>
            <ep:registration></ep:registration>
            <ep:isRecurring></ep:isRecurring>
            <ep:hostType>1019001</ep:hostType>
            <ep:isAudioOnly></ep:isAudioOnly>
            <ep:isTCSingleRecurrence></ep:isTCSingleRecurrence>
            <ep:isAllowJBH></ep:isAllowJBH>
            <ep:isCETMeeting>sand</ep:isCETMeeting>
            <ep:isException>falsk</ep:isException>
            <ep:isNextUpcomingInstance>falsk</ep:isNextUpcomingInstance>
            <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
            <ep:recurrenceId>0</ep:recurrenceId>
            <ep:isScheduledPMR>sand</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, Hawaiiansk (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>offentlig</ep:listStatus>
            <ep:hostEmail>Molly08Console81696000@webex.com</ep:hostEmail>
            <ep:passwordReq>True</ep:passwordReq>
            <ep:hostJoined>falsk</ep:hostJoined>
            <ep:participantsJoined>False</ep:participantsJoined>
            <ep:confID>141672108716459038</ep:confID>
            <ep:registration></ep:registration>
            <ep:isRecurring></ep:isRecurring>
            <ep:hostType>1019001</ep:hostType>
            <ep:isAudioOnly></ep:isAudioOnly>
            <ep:isTCSingleRecurrence></ep:isTCSingleRecurrence>
            <ep:isAllowJBH></ep:isAllowJBH>
            <ep:isCETMeeting></ep:isCETMeeting>
            <ep:isException></ep:isException>
            <ep:isNextUpcomingInstance></ep:isNextUpcomingInstance>
            <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
            <ep:recurrenceId>0</ep:recurrenceId>
            <ep:isScheduledPMR></ep:isScheduledPMR>
         </ep:session>
      </serv:bodyContent>
   </serv:body>
</serv:message>

GetSite- forbedringer

Vi har tilføjet et GetSite-svar funktion til eller fra af SupportXMLAPIReturnScheduledPMR

Påvirkede API'er:

  • GetSite

Skemaændring:

XML API- GetSitesvar nyt element er: SupportXMLAPIReturnScheduledPMR

GetSite-anmodnings eksempel:

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

GetSitesvar eksempel:

<?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>SUCCES</serv:result>
            <serv:gsbStatus>primært</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>sand</ns1:SupportXMLAPIReturnScheduledPMR> ... </ns1:siteCommonOptions>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

API 40.4.8, 40.2.9-opdateringer

XML API-40.4.8, 40.2.9-opdateringer

Klik her for at downloade XML API 40.4.8-skemaet

Klik her for at downloade XML API 40.2.9-skemaet

Nyt svar ved opdatering af planlagte møder i XMLAPI

Når kunder bruger XMLAPI til at opdatere møder planlagt gennem deres side, sender vi den numeriske adgangskode i en e-mail opdatering til et møde og anvender den til Webex Meetings, teams og events Centre.

Disse API'er: GetMeeting, GetTrainingSession, GetEvent og GetTeleconferenceSession, vil have disse nye elementer som svar: audioPassword (numerisk adgangskode), isEnforceAudioPassword, IsEnforceAudioLogin for Webex Meetings, teams og events Centre.

Ændret skema:

This image 446349.jpg is not available in preview/cisco.com

Påvirkede API'er:

  • GetMeeting

  • GetTrainingSession

  • GetEvent

  • GetTeleconferenceSession

GetMeeting-anmodnings eksempel:

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

Svar eksempel:

<?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>Succes</serv:result>
            <serv:gsbStatus>primær</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>falsk</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-opdateringer

XML API-40.4.5, 40.2.6-opdateringer

Grænse for GetUserCardog GetSessionInfoBrug

Vi implementerer brugs grænsen på API GetUserCard og GetSessionInfo, kan du få fejlmeddelelsen: "403 forbudt", hvis du når som brugergrænse.

Påvirkede API'er:

  • GetUserCard

  • GetSessionInfo

API 40.4.4, 40.2.5-opdateringer

XML API-40.4.4, 40.2.5-opdateringer

Grænse for BodyContent- nummer

Vi har tilføjet et begrænset antal BodyContent i hvert XML API-afsnit. Når du tilføjer for mange af BodyContent i API-anmodningen, vil følgende fejlkode og meddelelse blive returneret: "000053 tællingen af BodyContent i en anmodning skal være mindre end {Number}"

Påvirkede API'er:

  • Alle XML API

XML API-anmodning med flere BodyContent eksempel:

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

XML API-40.4.3, 40.2.4-opdateringer

Klik her for at downloade XML API-40.4.3, 40.2.4-skemaet.

CreateUser- forbedringer

Vi forbedrede CreateUser til at understøtte velkomst-e-mailen på flere sprog. CreateUser nu anmoder om isHTMLEmail

Påvirkede API'er:

  • CreateUser

CreateUser- anmodnings eksempel:

<?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>ægte</host>
        <siteAdmin>falsk</siteAdmin>
        <labAdmin>falsk</labAdmin>
        <voiceOverIp>falsk</voiceOverIp>
    </privilege>
    <languageID>3</languageID>
    <active>aktiveret</active>
    <sendWelcome>True</sendWelcome>
    <isHTMLEmail>True</isHTMLEmail>
</bodyContent>  
</body>
</serv:message>

API 40.4.0-opdateringer

XML API 40.4.0-opdateringer

Gennemtving e-mail bekræftelse ved ændring af e-mails i XML API

Efter en websteds administrators aktiverede bekræftelse er påkrævet, for at brugeren kan opdatere e-mailadresse i Webex Webstedsadministration:

  • Hvis en ikke-webstedsadministrator konto kalder SetUser -API'en for at ændre e-mailadresser, forbliver den aktuelle e-mail, indtil den nye e-mail er bekræftet. E-mail bekræftelsen af konto ændringer sendes til den nye e-mailadresse med "bekræftelse af ændring af Webex-konto". Når du har klikket på linket i e-mailen for at bekræfte det, er den nye e-mailadresse straks tilknyttet.


    Hvis en ikke-webstedsadministrator ringer til SetUser -API'en flere gange uden at afslutte e-mail bekræftelsesprocessen, holdes den aktuelle e-mail, og den nyeste nye e-mail er den, der skal verificeres.

  • Hvis en webstedsadministrator konto kalder SetUser API for at ændre e-mailadresser, udløses e-mail bekræftelsesprocessen ikke. Den nye e-mail vil øjeblikkeligt blive knyttet til værtens eller møde deltagerens konto.

Påvirkede API'er:

  • SetUser

GetEnrollmentInfo -timeout og nulstilling af forbindelse

GetEnrollmentInfo API søger i øjeblikket IP-adresser på domænenavne systemet, hvilket udløser enorme påvirkning af præstation. Vi planlægger at forenkle denne proces med et tomt svar i <domain> feltet.

Påvirkede API'er:

  • GetEnrollmentInfo

GetEnrollmentInfo- anmodnings eksempel:

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

<?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>Succes</serv:result>
            <serv:gsbStatus>primær</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>godkendt</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>godkendt</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>

API 40.2.0-opdateringer

XML API 40.2.0-opdateringer

Klik her for at downloade XML API-40.2.0s skemaet.

Fjern anonym adgang til LstSummarySession

Som en sikkerhedsforbedring, stopper vi understøttelsen af anonym adgang til LstSummarySession API. Hvis Webex Meetings anonym adgang til API'EN, returneres følgende fejlkode og meddelelse: "000015 beklager, der blev ikke fundet nogen optagelse."

Påvirkede API'er:

  • LstSummarySession

LstSummarySession- anmodnings eksempel:

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

<?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>FEJL</serv:result>
            <serv:reason>beklager, ingen optagelse fundet</serv:reason>
            <serv:gsbStatus>primær</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Oprettelse af møde og SetMeeting sikkerhedsforbedringer


Denne ændring blev foretaget i XML API-40.2.0, men dens beskrivelse er blevet redigeret efter at have modtaget kundefeedback.

Som en sikkerhedsforbedring opdaterede vi oprettelse af møde -og SetMeeting- API'erne til ikke at tillade brugere at planlægge et møde starttidspunkt, der allerede er passeret. Hvis de forsøger, beder API fejlmeddelelsen: "060016 sessionens starttidspunkt bør være senere end det aktuelle tidspunkt." Hvis en bruger skal planlægge et øjeblikkeligt møde, anbefaler vi, at mødets starttidspunkt indstilles til fem minutter senere end det aktuelle tidspunkt.

Påvirkede API'er:

  • Oprettelse af møde

  • SetMeeting

API 40.1.2-opdateringer

XML API 40.1.2-opdateringer

Klik her for at downloade XML API-40.1.2s skemaet.

Planlægning af et møde genererer automatisk en adgangskode, hvis en sådan ikke leveres

Vi har forbedret oprettelse af møde, createEvent, CreateTrainingSession ogCreateTeleconferenceSession for at inkludere en adgangskode i API-svarets brødtekst.

Som standard skal indstillingen alle møder/begivenheder/session have en adgangskode være aktiveret. Hvis API-anmodningen ikke inkluderer en adgangskode i dette scenario, genereres der automatisk en adgangskode fra XML API-serverne.

Hvis indstillingen alle møder/begivenheder/sessioner skal have en adgangskode er deaktiveret, og API-anmodningen ikke inkluderer en adgangskode, genereres der ikke en adgangskode fra XML API-serverne.

Hvis API-anmodningen inkluderer en adgangskode, vil svaret indeholde den adgangskode, uanset alle møder/begivenheder/sessioner, skal have en adgangskode indstilling, der aktiveres eller deaktiveres.

Påvirkede API'er:

  • Oprettelse af møde

  • CreateEvent

  • CreateTrainingSession

  • CreateTeleconferenceSession

Oprettelse af møde- svaret har nu Meeting password- elementet:

This image 442815.jpg is not available in preview/cisco.com

Oprettelse af møde- anmodnings eksempel:

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

Oprettelse af møde svar eksempel:

<?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>Succes med</serv:result>
            <serv:gsbStatus>primær</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>

CreateEvent- svaret har nu elementet eventPassword :

This image 442816.jpg is not available in preview/cisco.com

CreateTrainingSession -og CreateTeleconferenceSession- svarene har nu sessionPassword- elementet:

This image 442817.jpg is not available in preview/cisco.com

This image 442818.jpg is not available in preview/cisco.com

API 40.1.0-opdateringer

XML API 40.1.0-opdateringer

Klik her for at downloade XML API 40,1-skemaet.

GetSessionInfo- forbedringer

Vi har tilføjet nye elementer til GetSessionInfo API. API returnerer nu også oplysninger om mobile enheder.

Påvirkede API'er:

  • GetSessionInfo

GetSessionInfo anmodnings opdateringer:

This image 442373.jpg is not available in preview/cisco.com

Anmodnings eksempel:

<?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>webstedsadministrator</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 eller 123456789_go@webex.com eller 123456789@go.webex.com</sipUrl>
        <meetingLink>https://go.Webex.com/go/j.php?MTID=m814c6a483d4b5052d539f88d67acbad6</meetingLink>
        <meetingUuid>34567323456787654323456787654</meetingUuid>
    </bodyContent>
</body>
</serv:message>

LstAccessAnywhereHistory- forbedringer

Vi har tilføjet en ny API, lstAccessAnywhereHistory, til at svare med Webex Access Anywhere rapportoplysninger.

Påvirkede API'er:

  • LstAccessAnywhereHistory

LstAccessAnywhereHistory anmodnings opdateringer:

This image 442374.jpg is not available in preview/cisco.com

Opdateringer til LstAccessAnywhereHistory- svar:

This image 442375.jpg is not available in preview/cisco.com

Anmodnings eksempel:

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

Svar eksempel:

<?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>Succes med</serv:result>
            <serv:gsbStatus>primær</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>