Questo articolo contiene aggiornamenti e modifiche per le release SP mensili delle API XML.

Per ulteriori informazioni su API XML 40 e API REST 40, vedere la Cisco Webex Meetings Panoramica sugli aggiornamenti API (api 40).

Per aggiornamenti per API XML 11 SP9 e versioni precedenti, andare a Cisco DevNet.

Aggiornamenti API XML 39.11.0 Updates

Fare clic qui per scaricare lo schema API XML 39,11.

LstSummaryUser può interrogare gli account utente per l'ora dell'Ultima modifica

Stiamo eseguendo l'aggiornamento dell' API lstsummaryuser per consentire agli utenti di eseguire query sugli account utente in base all'ora dell'Ultima modifica. Tre nuovi elementi, modifieddatestart, modifieddateende LastModifiedTime, sono stati aggiunti all'API.


L'ambito di tempo massimo per questa query è 90 giorni. Se si immettere un intervallo di tempo superiore a 90 giorni, viene visualizzato un errore: 999999 intervallo di date massimo 90 giorni per query data di modifica.

API interessate:

  • Necessario

Esempio di richiesta LastSummaryUser :

<?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>Site_Name</siteName>
    <webExID>siteadmin</webExID>
    <password>password</password>
    <partnerID>webexpartner</partnerID>
  </securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.user.LstsummaryUser">
        <dataScope>
            <modifiedDateStart>10/01/2019 09:24:54</modifiedDateStart>
            <modifiedDateEnd>11/30/2019 09:24:54</modifiedDateEnd>
            <timeZoneID>4</timeZoneID>
        </dataScope>
    </bodyContent>
</body>
</message>

Esempio di risposta LstSummaryUser :

<?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></serv:result>
            <serv:gsbStatus>Primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>* * 5124 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</use:userID>
                <use:webExId></use:webExId>
                <use:firstName></use:firstName>
                <use:lastName></use:lastName>
                <use:email></use:email>
                <use:userRoleType></use:userRoleType>
                <use:registrationDate></use:registrationDate>
                <use:active></use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:meetingTypes>
                    <use:meetingType>3</use:meetingType>
                    <use:meetingType>9</use:meetingType>
                    <use:meetingType>10</use:meetingType>
                    <use:meetingType>11</use:meetingType>
                    <use:meetingType>13</use:meetingType>
                    <use:meetingType>14</use:meetingType>
                    <use:meetingType>102</use:meetingType>
                </use:meetingTypes>
                <use:lastLoginTime></use:lastLoginTime>
                <use:lastModifiedTime>11/11/2019 19:11:11 10/19/2019 23:13:14 06/19/2016 22:13:06 @qa * * * * * *</use:lastModifiedTime>
            </use:user>

Aggiornamenti API XML 39.10.0 Updates

Fare clic qui per scaricare lo schema API XML 39,10.

GetSessionInfo e getusercard restituisce un codice captcha quando si utilizza l'accesso anonimo

In qualità di aggiornamento della sicurezza, sono state migliorate le API getsessioninfo e getusercard con captcha protezione da risposta codice. Se le applicazioni chiamano le API utilizzando l'accesso anonimo, migliorare l'applicazione per supportare CAPTCHA codice di input.

API interessate:

  • GetSessionInfo

  • GetUserCard

CAPTCHA aggiornamenti di sicurezza e risposta:

Risposta GetSessionInfo senza captcha esempio:

<?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: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></serv:result>
            <serv:reason>Riunione non riuscita corrispondente non trovata</serv:reason>
            <serv:gsbStatus>principale</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Risposta GetSessionInfo con captcha esempio:

<?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: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>Mancata</serv:result>
            <serv:reason>riunione corrispondente non trovata</serv:reason>
            <serv:gsbStatus>principale</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
            <serv:CAPTCHAID>sddheefgkerwaaai * * * * QHS * * * * Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320jgube349924</serv:CAPTCHAID>
           <serv:CAPTCHAImage> iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA............... maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu + ZUFb7SAAAAAElFTkSuQmCC </serv:CAPTCHAImage>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Se si riceve una risposta CAPTCHA e si continua a chiamare l'API, includere CAPTCHAID e CAPTCHAWord nella richiesta API:

<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>
    <CAPTCHAID>sddheefgkerwaaai * * * * qHS * * * * Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</CAPTCHAID>
    <CAPTCHAWord>pyjihk</CAPTCHAWord>
</securityContext>
</header>
<body>
    <bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
        <sessionKey>715801743</sessionKey>
    </bodyContent>
</body>
</serv:message>

Risposta GetSessionInfo a esempio CAPTCHAID e CAPTCHAWord non corretto:

<?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: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></serv:result>
            <serv:reason>ID captcha e Word non validi o mancanti</serv:reason>
            <serv:gsbStatus></serv:gsbStatus>
            <serv:exceptionID>030113</serv:exceptionID>
            <serv:CAPTCHAID>sddheefgkerwaaai * * * * QHS * * * * Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320jgube349924</serv:CAPTCHAID>
           <serv:CAPTCHAImage> iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA........... maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu + ZUFb7SAAAAAElFTkSuQmCC </serv:CAPTCHAImage>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Supporto utente Lstsummaryper la restituzione degli URL della sala riunioni personale

È stato aggiunto un nuovo elemento di risposta, personalmeetingroomurl, all' API lstsummaryuser .

Esempio di risposta LstSummaryUser :

Aggiornamenti API XML 39.9.0 Updates

Fare clic qui per scaricare lo schema API XML 39,9.

Supporto per URL SIP brevi per sale riunioni personali (PMR)

Il supporto per il formato URL SIP breve per PMRs influisce sulle API getsessioninfo, getmeeting, GetUsere GETME . È stato aggiunto un nuovo elemento di risposta denominato displaymeetingurl alle API GetUser e GETME ed è già presente in getsessioninfo e getmeeting. displayMeetingUrl restituisce l'URL del PMR di un utente.

API interessate:

  • GetSessionInfo

  • GetMeeting

  • Getuser

  • GetMe

Esempio di risposta GetUser:

Esempio di risposta GetMe:

GetSessionInfo restituisce gli elementi necessari per l'accesso anonimo

Come requisito di sicurezza, ora è possibile restituire solo gli elementi necessari da getsessioninfo per l'accesso anonimo.

Esempio di risposta GetSessionInfo :

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:sessionkey>715952675</ep:sessionkey>
    <ep:accessControl>
        <ep:listStatus>pubblico</ep:listStatus>
        <ep:registration>falso</ep:registration>
        <ep:passwordReq>vero</ep:passwordReq>
        <ep:registrationURL>https://sqdemo6.DMZ.Webex.com/ec3300/EventCenter/Enroll/Register.do?loadFlag=1&reqFlag=1&confId=123203663769372547&SiteUrl=sqdemo6</ep:registrationURL>
        <ep:registrationURLForMobile>https://sqdemo6.DMZ.Webex.com/ec3300/EventCenter/Enroll/mobileRegister.do?formId=0&formType=0&loadFlag=1&from=mobileClient&SiteUrl=sqdemo6&confId=123203663769372547</ep:registrationURLForMobile>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Anony_Meeting_Retuning</ep:confName>
        <ep:serviceType>meetingcenter</ep:serviceType>
    </ep:metaData>
    <ep:schedule>
        <ep:startDate>03/29/2019 11:55:00</ep:startDate>
        <ep:duration>60</ep:duration>
        <ep:timeZone>GMT-07:00, Pacifico (San Francisco) falso vero vero falso</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount></ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH></ep:isAllowJBH>
    <ep:isCETMeeting></ep:isCETMeeting>
    <ep:isPersonalMeetingRoom></ep:isPersonalMeetingRoom>
    <ep:meetingLink>https://sqdemo6.DMZ.Webex.com/sqdemo6/e.php?MTID=m2399b241f12722ca325388495e845103</ep:meetingLink>
    <ep:sipURL>715952675@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>715952675@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
</serv:bodyContent>

API interessate:

  • GetSessionInfo

Pianificazione della modifica del funzionamento di riunioni ed eventi

Per impostazione predefinita, tutte le riunioni pianificate sono riunioni abilitate per dispositivi video. Tuttavia, quando si pianifica una riunione ma si seleziona nessuno o altri per l' audio della riunione, la riunione verrà pianificata come riunione non abilitata per dispositivi non video Webex.

API interessate:

  • Riunione

  • SetMeeting

  • CreateEvent

  • SetEvent

Aggiornamenti API XML 39.8.0 Updates

Fare clic qui per scaricare lo schema API XML 39,8.

Lsttrainingattendeecronologia ora restituisce attenzione dei partecipanti alla riunione

È stato aggiunto un nuovo elemento di risposta, attentiontodurationpercentage, all' API lsttrainingattendeehistory . Lsttrainingattendeecronologia restituisce i dettagli di attenzione dei partecipanti alla riunione. L'elemento viene restituito in questo formato:

<history:attentionToDurationPercentage>100</history:AttentionToDurationPercentage>

API interessate:

  • Lsttrainingattendeecronologia

    • Attenzionepercentuale Durationpercentage

    • attentionToAttendancePercentage

Esempio di risposta LsttrainingattendeeHistory :

<history:endTime>04/17/2019 23:37:07</history:endTime>
<history:duration>6</history:duration>
    <history:attentionToDurationPercentage>100</history:AttentionToDurationPercentage>
    <history:attentionToAttendancePercentage>100</history:AttentionToAttendancePercentage>
<history:registered>n</history:registered>
<history:invited>n</history:invited>

GetSite ora restituisce i conteggi delle licenze

Sono stati forniti nuovi elementi di risposta per restituire diversi conteggi di licenze nell' API GetSite .

API interessate:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

Riprogettazione di GetSiteFT e setsiteft

Le API getsiteft e setsiteft sono state riprogettate per consentire la commutazione dinamica delle funzioni.

API interessate:

  • GetSiteFT

  • SetSiteFT

Esempio di richiesta GetSite:

<?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"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <siteName>{siteName}</siteName>
            <accessToken>{Questo è il token di accesso all'account computer}</accessToken>
        </securityContext>
    </header>
    <bodyContent xsi:type="java:com.webex.service.binding.site.GetSiteFT">
        <featureToggles>
            <name>SupportCrossLaunch</name>
            <name>removecmrlicensesa</name>
        </featureToggles>
    </bodyContent>
</body>
</serv:message>

Esempio di risposta GetSite:

<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></serv:result>
            <serv:gsbStatus>Supporto principale di</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteFTResponse">
            <ns1:featureToggles>
                <ns1:featureToggle>
                    <ns1:name>supportcrosslaunch</ns1:name>
                    <ns1:value>false</ns1:value>
                </ns1:featureToggle>
                <ns1:featureToggle>
                    <ns1:name>removecmrlicensesa</ns1:name>
                    <ns1:value>false</ns1:value>
                </ns1:featureToggle>
            </ns1:featureToggles>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Esempio di richiesta SetSite:

<?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"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <siteName>{siteName}</siteName>
            <accessToken>{Questo è il token di accesso all'account computer}</accessToken>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.site.SetSiteFT">
            <featureToggles>
                <featureToggle>
                    <name>SupportCrossLaunch</name>
                    <value>false</value>
                </featureToggle>
                <featureToggle>
                    <name>supportpeopleinsight</name>
                    <value>vero</value>
                </featureToggle>
            </featureToggles>
        </bodyContent>
    </body>
</serv:message>

Esempio di risonanza SetSiteFT :

<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></serv:result>
            <serv:gsbStatus>primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:setSiteFTResponse"/>
    </serv:body>
</serv:message>

Lunghezza Descrizione riunione ora limitata a 2500 caratteri

Le seguenti API ora presentano la lunghezza del contenuto dell'elemento della descrizione della riunione limitata a 2500 caratteri:

API interessate:

  • CreateEvent

  • SetEvent

  • CreateTrainingSession

  • SetTrainingSession

Ciò impedisce a Cisco Webex di non essere in grado di elaborare la richiesta. Se la descrizione della riunione supera i 2500 caratteri, viene restituito un messaggio di errore.

Aggiornamenti API XML 39.5.0 Updates

Nuovo elemento videomeshinterclusters aggiunti agli schemi SetSite e GetSite

Un nuovo elemento, videomeshinterclusters, è stato aggiunto all' elemento SetSite . videoMeshInterclusters contiene anche tre elementi Children videoMeshHomeCluster1, videoMeshHomeCluster2e videoMeshHomeCluster3.

API interessate:

  • SetSite

    • Videomeshintercluster

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • Videomeshintercluster

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

Aggiornamenti delle richieste SetSite:

Aggiornamenti risposta GetSite:

Aggiornamenti API XML 39.3.0 Updates

URL SIP breve nell'API XML, nuovo elemento displaymeetingurl

Fare clic qui per scaricare lo schema API XML 39,3.

Attualmente, quando si accede a una riunione Webex, l'app o il dispositivo deve fornire informazioni sul sito, rendendo difficile l'accesso alle riunioni a volte. Ciò è particolarmente vero quando si accede da un dispositivo SIP, perché l'utente deve digitare la meeting_number@sitename.webex.com.

Per facilitare l'accesso alle riunioni, è stato rimosso il requisito di inserire il nome del sito dall'URI SIP della riunione: meeting_number@webex.com. Per mantenere la compatibilità con le versioni precedenti, il formato precedente funziona su sipURL e nuovo formato viene aggiunto al nuovo elemento displaymeetingurl.

API interessate:

  • GetMeeting

    • displayMeetingUrl

  • GetEvent

    • displayMeetingUrl

  • GetSessionInfo

    • displayMeetingUrl

Esempio di risposta GetMeeting:

    <meet:isCETMeeting>true</meet:isCETMeeting>
    <meet:meetingLink>https://sqdemo.dmz.webex.com/sqdemo/j.php?MTID=m0cdefe09626ba0bec956cdf9088bff55</meet:meetingLink>
    <meet:sipURL>712296997@sqdemo.dmz.webex.com</meet:sipURL>
    <meet:displayMeetingUrl>712296997@dmz.webex.com</meet:displayMeetingUrl>
</serv:bodyContent>

Esempio di risposta GetEvent:

    <event:hostType>1001001</event:hostType>
    <event:isCETMeeting>true</event:isCETMeeting>
    <event:sipURL>713847821@sqdemo.dmz.webex.com</event:sipURL>
    <event:displayMeetingUrl>713847821@dmz.webex.com</event:displayMeetingUrl>
</serv:bodyContent>

Esempio di risposta GetSessionInfo :

    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
    <ep:meetingLink>https://sqdemo.dmz.webex.com/sqdemo/j.php?MTID=ee7d38639d0b4a9ed2eb8802cfa2810dd</ep:meetingLink>
    <ep:sipURL>713847821@sqdemo.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>713847821@dmz.webex.com</ep:displayMeetingUrl>
</serv:bodyContent>

Esempio e-mail:

Descrizione lunghezza ora limitata a 1024 caratteri

Le seguenti API ora presentano la lunghezza del contenuto dell'elemento Description limitata a 1024 caratteri:

API interessate:

  • CreateTrainingSession

  • SetTrainingSession

  • CreateEvent

  • SetEvent

Questa modifica impedisce a Cisco Webex di non essere in grado di elaborare la richiesta. Se la descrizione supera 1024 caratteri, viene restituito un messaggio di errore: "060067 Descrizione ingresso illegale. La descrizione non può superare la lunghezza massima dei caratteri di visualizzazione 1024. "

Esempio di risposta per la lunghezza della descrizione maggiore di 1024 caratteri:

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:sess="http://www.webex.com/schemas/2002/06/service/session" xmlns:train="http://www.webex.com/schemas/2002/06/service/trainingsession" xmlns:qti="http://www.webex.com/schemas/2002/06/service/trainingsessionqti" xmlns:qtiasi="http://www.webex.com/schemas/2002/06/service/trainingsessionqtiasi">
    <serv:header>
        <serv:response>
            <serv:result></serv:result>
            <serv:reason> Descrizione ingresso non valida. La descrizione non può superare la lunghezza massima dei caratteri di visualizzazione 1024 </serv:reason>
            <serv:gsbStatus>principale</serv:gsbStatus>
            <serv:exceptionID>060067</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

GetSessionInfo ora restituisce solo informazioni di base per le sale riunioni personali quando un utente anonimo utilizza l'API

Per garantire una maggiore sicurezza, stiamo diminuendo la quantità di informazioni restituite da getsessioninfo quando un utente partecipante anonimo utilizza l'API. In questo aggiornamento verranno ridurre i seguenti elementi nella risposta API:

API interessate:

  • GetSessionInfo

    • <ep:accessControl>

  • <ep:sessionPassword>

    • <ep:telephony>

    • <ep:isAlternateHost>…</ep:isAlternateHost>

    • <ep:isCreator>…</ep:isCreator>

    • <ep:hostKey>…</ep:hostKey>

    • <ep:supportE2E>…</ep:supportE2E>

Confronto risposta:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS falso non elencato falso falso falso falso</ep:status>
    <ep:isLocked></ep:isLocked>
    <ep:sessionkey>712419789</ep:sessionkey>
    <ep:confID>120396209273701973</ep:confID>
    <ep:accessControl>
        <ep:sessionPassword></ep:sessionPassword>   <!--Removed-->
        <ep:listStatus></ep:listStatus>
        <ep:registration></ep:registration>
        <ep:passwordReq></ep:passwordReq>
        <ep:isEnforceAudioPassword></ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin></ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Simon sala riunioni personale meetingcenter falso testo testo falso falso</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType></ep:serviceType>
        <ep:isRecurring></ep:isRecurring>
        <ep:agendaFormat></ep:agendaFormat>
        <ep:descriptionFormat></ep:descriptionFormat>
        <ep:isException></ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException></ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>richiamo</ep:telephonySupport> <!--Removed-->
        <ep:globalCallInNumbersURL>https://sqdemo6.DMZ.Webex.com/sqdemo6/globalcallin.php?ServiceType=MC&ed=0</ep:globalCallInNumbersURL>   <!--Removed-->
        <ep:tollFreeRestrictionsURL>https://www.Webex.com/PDF/tollfree_restrictions.pdf</ep:tollFreeRestrictionsURL>    <!--Removed-->
        <ep:dialInSequences>autodialinsequence: [AccessNumber],, * 00 * [Accesscode] #,,, [attendeeid] # | SilentDialInSequence: [AccessNumber],, * 01 * [AccessCode] # [AttendeeID] # * 01 * | AutoLGDialInSequence: [AccessNumber],, * 00 * [AccessCode] #,,, [ProfileID] #,,, [PIN] # | SilentLGDialInSequence: [AccessNumber],, * 01 * [AccessCode] # [ProfileID] # [PIN] # * 01 * | AutoLGPWDialInSequence: [AccessNumber],, * 00 * [AccessCode] #,,, [ProfileID] #,,, [PIN] #,,, [password] # | Silentlgpwdialinsequence: [AccessNumber],, * 01 * [Accesscode] # [ProfileID] # [PIN] # [password] # * 01 * falso falso</ep:dialInSequences>  <!--Removed-->
        <ep:callInNum>    <!--Removed-->
            <serv:tollNum>14085452910</serv:tollNum>    <!--Removed-->
            <serv:globalNum>  <!--Removed-->
                <serv:countryAlias>14085452912</serv:countryAlias>  <!--Removed-->
                <serv:phoneNumber>14085452912</serv:phoneNumber>    <!--Removed-->
                <serv:tollFree></serv:tollFree>    <!--Removed-->
                <serv:default></serv:default>  <!--Removed-->
            </serv:globalNum> <!--Removed-->
        </ep:callInNum>   <!--Removed-->
        <ep:labels>   <!--Removed-->
            <ep:tollFreeCallInLabel>numero di chiamata in ingresso gratuito (USA/Canada)</ep:tollFreeCallInLabel>   <!--Removed-->
            <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->
        </ep:labels>  <!--Removed-->
        <ep:isMPAudio>falso</ep:isMPAudio>  <!--Removed-->
        <ep:voip>vero falso</ep:voip> <!--Removed-->
        <ep:enableTSP></ep:enableTSP>  <!--Removed-->
    </ep:telephony>   <!--Removed-->
    <ep:host>
        <ep:firstName>test Simon</ep:firstName>
        <ep:lastName></ep:lastName>
        <ep:email>simon0@qa.webex.com</ep:email>
        <ep:webExId>Simon</ep:webExId>
        <ep:allowAnyoneHostMeeting>falso</ep:allowAnyoneHostMeeting>
    </ep:host>
    <ep:schedule>
        <ep:startDate>12/31/2068 13:00:00</ep:startDate>
        <ep:duration>720</ep:duration>
        <ep:timeZone>GMT-08:00, Pacifico (San Francisco)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
        <ep:openTimeInSec>0</ep:openTimeInSec>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount></ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly></ep:isAudioOnly>
    <ep:telePresence></ep:telePresence>
    <ep:isAlternateHost></ep:isAlternateHost>  <!--Removed-->
    <ep:isCreator></ep:isCreator>   <!--Removed-->
    <ep:hostKey>954462</ep:hostKey> <!--Removed-->
    <ep:supportE2E></ep:supportE2E>    <!--Removed-->
    <ep:isAllowJBH></ep:isAllowJBH>
    <ep:isCETMeeting></ep:isCETMeeting>
    <ep:isPersonalMeetingRoom></ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance></ep:isNextUpcomingInstance>
    <ep:meetingLink></ep:meetingLink>
    <ep:sipURL></ep:sipURL>
    <ep:displayMeetingUrl></ep:displayMeetingUrl>
    <ep:isAutoRecord>falso falso falso falso vero falso falso vero vero vero https://sqdemo6.DMZ.Webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed simon0@sqdemo6.dmz.webex.com simon0@sqdemo6.dmz.webex.com falso</ep:isAutoRecord>
</serv:bodyContent>

Aggiornamenti API XML 39.2.0 Updates

Nuovo elemento lastLoginTime restituito in lstsummaryrisposta utente

Un nuovo elemento di risposta, lastLoginTime, è stato aggiunto all' API lstsummaryuser . lastLoginTime restituisce l'ultimo tempo di accesso per ciascun utente. L'elemento viene restituito in questo formato:

<lastLoginTime>04/12/2018 22:40:01 * *</lastLoginTime>

API interessate:

  • Necessario

    • lastLoginTime

Esempio di risposta LstSummaryUser :

<?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>Successo</serv:result>
            <serv:gsbStatus>principale</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>3469487</use:userID>
                <use:objectGUID>a14e3312-e1d1-4E41-82b9-6ddac80c9f9a</use:objectGUID>
                <use:webExId>Sangeetha.Swaminathan@gmail.com</use:webExId>
                <use:firstName>sangee</use:firstName>
                <use:lastName>gmail</use:lastName>
                <use:email>Sangeetha.Swaminathan@gmail.com</use:email>
                <use:userRoleType>Organizzatore</use:userRoleType>
                <use:registrationDate>12/11/2018 14:41:27</use:registrationDate>
                <use:active>disattivato</use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:lastLoginTime>04/12/2018 22:40:01</use:lastLoginTime>
            </use:user>
            <use:matchingRecords>
                <serv:total>1</serv:total>
                <serv:returned>1</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </use:matchingRecords>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Aggiornamenti API XML 39.1.0 Updates

Fare clic qui per scaricare lo schema 39.1.0 API XML.

Nuovo apiver elemento aggiunto all' API getapiversion

Un nuovo elemento di risposta, apiver, è stato aggiunto all' API getapiversion . Con questo aggiornamento, la convenzione di denominazione della versione dell'API XML cambia in base a un numero di versione unificato con altre Cisco Webex aree di prodotto. apiVer restituisce le nuove informazioni sulla versione, ad esempio 39.1.0 per l'aggiornamento del 2019 gennaio.

API interessate:

  • GetAPIVersion

    • apiVer

L'elemento ApiVersion sarà deprecato il 1 maggio 2019 e alla release dell'elemento verrà assegnato un nuovo valore API XML il 1 ° maggio 2019.

Esempio di risposta GetAPIVersion :

<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></serv:result>
            <serv:gsbStatus></serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ep:getAPIVersionResponse">
            <ep:apiVersion>Webex API XML primaria riuscita 11.0.0</ep:apiVersion>
            <ep:release>SP22</ep:release>
            <ep:apiVer>39.1.0</ep:apiVer>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Parametri HQ e HD rimossi dall'API XML

Le proprietà del video HQ e HD sono ora determinate a livello di sito, anziché essere determinate a livello di utente. Le due opzioni per questi parametri vengono ignorate quando si inviano richieste dalle seguenti API:

  • Riunione

  • SetMeeting

  • CreateTrainingSession

  • SetTrainingSession

Le API getmeeting e gettrainingsession restituiscono ancora le due opzioni (decise in base al livello del sito e a livello utente) per evitare di rompere il codice esistente.

Nuovo elemento uploadlogfileurl aggiunto ai metadati del sito restituito all'app desktop

È stato aggiunto un nuovo elemento uploadlogfileurl alla risposta restituita all'app desktop quando chiama l' API GetSite nel server API XML. L'app desktop può caricare il file di log in uploadlogfileurl.

API interessate:

  • GetSite

    • uploadLogFileUrl

Esempio di risposta GetSite:

<?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:metaData>
                    <ns1:isEnterprise>true</ns1:isEnterprise>
                    <ns1:serviceType>Meeting Center</ns1:serviceType>
                    <ns1:serviceType>Event Center</ns1:serviceType>
                    <ns1:serviceType>Training Center</ns1:serviceType>
                    <ns1:serviceType>Support Center</ns1:serviceType>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>9</ns1:meetingTypeID>
                        <ns1:meetingTypeName>ONS</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>11</ns1:meetingTypeID>
                        <ns1:meetingTypeName>TRS</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>13</ns1:meetingTypeID>
                        <ns1:meetingTypeName>SC3</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>16</ns1:meetingTypeID>
                        <ns1:meetingTypeName>AUO</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>214</ns1:meetingTypeID>
                        <ns1:meetingTypeName>PRO</ns1:meetingTypeName>
                        <ns1:hideInScheduler>false</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:siteName>sqdemo28</ns1:siteName>
                    <ns1:brandName>sqdemo28</ns1:brandName>
                    <ns1:brandName>sqdemo28-de</ns1:brandName>
                    <ns1:brandName>sqdemo28-en</ns1:brandName>
                    <ns1:brandName>sqdemo28-fr</ns1:brandName>
                    <ns1:region>France</ns1:region>
                    <ns1:currency>French Francs</ns1:currency>
                    <ns1:timeZoneID>4</ns1:timeZoneID>
                    <ns1:timeZone>GMT-08:00, Pacific (San Jose)</ns1:timeZone>
                    <ns1:parterID>7Dsupoc6DOfzpgcNViYvUA</ns1:parterID>
                    <ns1:webDomain>sqwd</ns1:webDomain>
                    <ns1:meetingDomain>sqmd</ns1:meetingDomain>
                    <ns1:telephonyDomain>sqtd</ns1:telephonyDomain>
                    <ns1:pageVersion>T33L</ns1:pageVersion>
                    <ns1:clientVersion>T33L</ns1:clientVersion>
                    <ns1:pageLanguage>FRENCH</ns1:pageLanguage>
                    <ns1:activateStatus>true</ns1:activateStatus>
                    <ns1:webPageType>J2EE</ns1:webPageType>
                    <ns1:iCalendar>true</ns1:iCalendar>
                    <ns1:myWebExDefaultPage>My Meetings</ns1:myWebExDefaultPage>
                    <ns1:componentVersion>cmp3300</ns1:componentVersion>
                    <ns1:accountNumLimit>999999</ns1:accountNumLimit>
                    <ns1:activeUserCount>40</ns1:activeUserCount>
                    <ns1:displayMeetingActualTime>false</ns1:displayMeetingActualTime>
                    <ns1:displayOffset>true</ns1:displayOffset>
                    <ns1:supportWebEx11>false</ns1:supportWebEx11>
                </ns1:metaData>
                <ns1:ucf>
                    <ns1:ucfConfiguration>UCF 2.1</ns1:ucfConfiguration>
                </ns1:ucf>
                <ns1:clientPlatforms>
                    <ns1:msWindows>true</ns1:msWindows>
                    <ns1:macOS9>true</ns1:macOS9>
                    <ns1:macOSX>true</ns1:macOSX>
                    <ns1:sunSolaris>true</ns1:sunSolaris>
                    <ns1:linux>true</ns1:linux>
                    <ns1:hpUnix>false</ns1:hpUnix>
                    <ns1:java>true</ns1:java>
                    <ns1:palm>false</ns1:palm>
                </ns1:clientPlatforms>
                <ns1:resourceRestrictions>
                    <ns1:isLicenseManager>true</ns1:isLicenseManager>
                    <ns1:concurrentLicense>0</ns1:concurrentLicense>
                    <ns1:fileFolderCapacity>1000</ns1:fileFolderCapacity>
                    <ns1:maxConcurrentEvents>0</ns1:maxConcurrentEvents>
                    <ns1:archiveStorageLimit>0</ns1:archiveStorageLimit>
                </ns1:resourceRestrictions>
                <ns1:supportAPI>
                    <ns1:autoLogin>true</ns1:autoLogin>
                    <ns1:aspAndPHPAPI>true</ns1:aspAndPHPAPI>
                    <ns1:backwardAPI>false</ns1:backwardAPI>
                    <ns1:xmlAPI>true</ns1:xmlAPI>
                    <ns1:cAPI>false</ns1:cAPI>
                    <ns1:scorm>true</ns1:scorm>
                </ns1:supportAPI>
                <ns1:myWebExConfig>
                    <ns1:myContacts>true</ns1:myContacts>
                    <ns1:myProfile>true</ns1:myProfile>
                    <ns1:myMeetings>true</ns1:myMeetings>
                    <ns1:trainingRecordings>true</ns1:trainingRecordings>
                    <ns1:folders>false</ns1:folders>
                    <ns1:eventDocument>true</ns1:eventDocument>
                    <ns1:myReport>false</ns1:myReport>
                    <ns1:myComputer>false</ns1:myComputer>
                    <ns1:personalMeetingPage>false</ns1:personalMeetingPage>
                    <ns1:myFilesStorage>1000</ns1:myFilesStorage>
                    <ns1:myComputerNumbers>0</ns1:myComputerNumbers>
                    <ns1:enableMyWebExPro>true</ns1:enableMyWebExPro>
                    <ns1:myWebExProMaxHosts>999999</ns1:myWebExProMaxHosts>
                    <ns1:restrictAccessAnyApps>false</ns1:restrictAccessAnyApps>
                    <ns1:restrictAccessAnyAppsNum>0</ns1:restrictAccessAnyAppsNum>
                    <ns1:addlAccessAnyComputersLimit>STRICT</ns1:addlAccessAnyComputersLimit>
                    <ns1:addlAccessAnyComputers>0</ns1:addlAccessAnyComputers>
                    <ns1:addlStorageLimit>STRICT</ns1:addlStorageLimit>
                    <ns1:addlStorage>0</ns1:addlStorage>
                    <ns1:myContactsPro>true</ns1:myContactsPro>
                    <ns1:myProfilePro>true</ns1:myProfilePro>
                    <ns1:myMeetingsPro>true</ns1:myMeetingsPro>
                    <ns1:trainingRecordingsPro>true</ns1:trainingRecordingsPro>
                    <ns1:foldersPro>false</ns1:foldersPro>
                    <ns1:eventDocumentPro>true</ns1:eventDocumentPro>
                    <ns1:myReportPro>true</ns1:myReportPro>
                    <ns1:myComputerPro>false</ns1:myComputerPro>
                    <ns1:personalMeetingPagePro>true</ns1:personalMeetingPagePro>
                    <ns1:myFilesStoragePro>1000</ns1:myFilesStoragePro>
                    <ns1:myComputerNumbersPro>0</ns1:myComputerNumbersPro>
                    <ns1:PMRheaderBranding>false</ns1:PMRheaderBranding>
                </ns1:myWebExConfig>
                <ns1:telephonyConfig>
                    <ns1:isTSPUsingTelephonyAPI>false</ns1:isTSPUsingTelephonyAPI>
                    <ns1:serviceName>Personal Conference No.</ns1:serviceName>
                    <ns1:participantAccessCodeLabel>Attendee access code</ns1:participantAccessCodeLabel>
                    <ns1:subscriberAccessCodeLabel>Host access code</ns1:subscriberAccessCodeLabel>
                    <ns1:attendeeIDLabel>Attendee ID</ns1:attendeeIDLabel>
                    <ns1:internetPhone>true</ns1:internetPhone>
                    <ns1:supportCallInTypeTeleconf>true</ns1:supportCallInTypeTeleconf>
                    <ns1:callInTeleconferencing>true</ns1:callInTeleconferencing>
                    <ns1:tollFreeCallinTeleconferencing>true</ns1:tollFreeCallinTeleconferencing>
                    <ns1:intlCallInTeleconferencing>true</ns1:intlCallInTeleconferencing>
                    <ns1:callBackTeleconferencing>true</ns1:callBackTeleconferencing>
                    <ns1:callInNumber>1</ns1:callInNumber>
                    <ns1:defaultTeleServerSubject>0.0.0.0</ns1:defaultTeleServerSubject>
                    <ns1:subscribeName>QA</ns1:subscribeName>
                    <ns1:subscribePassword>pass</ns1:subscribePassword>
                    <ns1:defaultPhoneLines>10</ns1:defaultPhoneLines>
                    <ns1:defaultSpeakingLines>10</ns1:defaultSpeakingLines>
                    <ns1:majorCountryCode>1</ns1:majorCountryCode>
                    <ns1:majorAreaCode>408</ns1:majorAreaCode>
                    <ns1:publicName>Call-in User</ns1:publicName>
                    <ns1:hybridTeleconference>true</ns1:hybridTeleconference>
                    <ns1:instantHelp>false</ns1:instantHelp>
                    <ns1:customerManage>false</ns1:customerManage>
                    <ns1:maxCallersNumber>500</ns1:maxCallersNumber>
                    <ns1:isSpecified>false</ns1:isSpecified>
                    <ns1:isContinue>false</ns1:isContinue>
                    <ns1:intlCallBackTeleconferencing>true</ns1:intlCallBackTeleconferencing>
                    <ns1:personalTeleconf>
                        <ns1:primaryLargeServer>
                            <serv:tollNum>14085452910</serv:tollNum>
                            <serv:globalNum>
                                <serv:countryAlias>14085452912</serv:countryAlias>
                                <serv:phoneNumber>14085452912</serv:phoneNumber>
                                <serv:tollFree>false</serv:tollFree>
                                <serv:default>false</serv:default>
                            </serv:globalNum>
                            <serv:enableServer>true</serv:enableServer>
                            <serv:tollLabel>14085452910</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:primaryLargeServer>
                        <ns1:backup1LargeServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup1LargeServer>
                        <ns1:backup2LargeServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Backup call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Backup call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup2LargeServer>
                        <ns1:primarySmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:primarySmallServer>
                        <ns1:backup1SmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup1SmallServer>
                        <ns1:backup2SmallServer>
                            <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Backup call-in toll number (US/Canada)</serv:tollLabel>
                            <serv:tollFreeLabel>Backup call-in toll-free number (US/Canada)</serv:tollFreeLabel>
                        </ns1:backup2SmallServer>
                        <ns1:joinBeforeHost>false</ns1:joinBeforeHost>
                    </ns1:personalTeleconf>
                    <ns1:multiMediaPlatform>true</ns1:multiMediaPlatform>
                    <ns1:multiMediaHostName>msa1mcccl01.dmz.webex.com</ns1:multiMediaHostName>
                    <ns1:broadcastAudioStream>true</ns1:broadcastAudioStream>
                    <ns1:tspAdaptorSettings>
                        <ns1:primaryLarge>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Call-in number</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Call-in toll-free number</ns1:label>
                            </ns1:mpAudio>
                        </ns1:primaryLarge>
                        <ns1:backup1Large>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Call-in number</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Call-in toll-free number</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup1Large>
                        <ns1:backup2Large>
                            <ns1:enableAdaptor>false</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Call-in number</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Call-in toll-free number</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup2Large>
                    </ns1:tspAdaptorSettings>
                    <ns1:meetingPlace>
                        <ns1:persistentTSP>false</ns1:persistentTSP>
                        <ns1:mpAudioConferencing>WithoutIntegration</ns1:mpAudioConferencing>
                    </ns1:meetingPlace>
                    <ns1:supportOtherTypeTeleconf>false</ns1:supportOtherTypeTeleconf>
                    <ns1:otherTeleServiceName>Other teleconference service</ns1:otherTeleServiceName>
                    <ns1:supportAdapterlessTSP>false</ns1:supportAdapterlessTSP>
                    <ns1:displayAttendeeID>false</ns1:displayAttendeeID>
                    <ns1:provisionTeleAccount>true</ns1:provisionTeleAccount>
                    <ns1:choosePCN>false</ns1:choosePCN>
                    <ns1:audioOnly>true</ns1:audioOnly>
                    <ns1:configTollAndTollFreeNum>false</ns1:configTollAndTollFreeNum>
                    <ns1:configPrimaryTS>false</ns1:configPrimaryTS>
                    <ns1:teleCLIAuthEnabled>false</ns1:teleCLIAuthEnabled>
                    <ns1:teleCLIPINEnabled>false</ns1:teleCLIPINEnabled>
                </ns1:telephonyConfig>
                <ns1:commerceAndReporting>
                    <ns1:trackingCode>false</ns1:trackingCode>
                    <ns1:siteAdminReport>true</ns1:siteAdminReport>
                    <ns1:subScriptionService>false</ns1:subScriptionService>
                    <ns1:isECommmerce>false</ns1:isECommmerce>
                    <ns1:customereCommerce>false</ns1:customereCommerce>
                    <ns1:isLocalTax>false</ns1:isLocalTax>
                    <ns1:localTaxName>VAT</ns1:localTaxName>
                    <ns1:localTaxtRate>0.0</ns1:localTaxtRate>
                    <ns1:holReport>1</ns1:holReport>
                </ns1:commerceAndReporting>
                <ns1:tools>
                    <ns1:businessDirectory>false</ns1:businessDirectory>
                    <ns1:officeCalendar>false</ns1:officeCalendar>
                    <ns1:meetingCalendar>true</ns1:meetingCalendar>
                    <ns1:displayOnCallAssistLink>false</ns1:displayOnCallAssistLink>
                    <ns1:displayProfileLink>true</ns1:displayProfileLink>
                    <ns1:recordingAndPlayback>true</ns1:recordingAndPlayback>
                    <ns1:recordingEditor>true</ns1:recordingEditor>
                    <ns1:publishRecordings>true</ns1:publishRecordings>
                    <ns1:instantMeeting>true</ns1:instantMeeting>
                    <ns1:emails>false</ns1:emails>
                    <ns1:outlookIntegration>true</ns1:outlookIntegration>
                    <ns1:wirelessAccess>false</ns1:wirelessAccess>
                    <ns1:allowPublicAccess>true</ns1:allowPublicAccess>
                    <ns1:ssl>true</ns1:ssl>
                    <ns1:handsOnLab>true</ns1:handsOnLab>
                    <ns1:holMaxLabs>999999</ns1:holMaxLabs>
                    <ns1:holMaxComputers>999999</ns1:holMaxComputers>
                    <ns1:userLockDown>false</ns1:userLockDown>
                    <ns1:meetingAssist>false</ns1:meetingAssist>
                    <ns1:sms>false</ns1:sms>
                    <ns1:encryption>NONE</ns1:encryption>
                    <ns1:internalMeeting>false</ns1:internalMeeting>
                    <ns1:enableTP>false</ns1:enableTP>
                    <ns1:enableTPplus>false</ns1:enableTPplus>
                    <ns1:uploadLogFileUrl>https://sqwd.webex.com/logadmin/spr.do?SiteUrl=sqdemo28&amp;LanguageId=1</ns1:uploadLogFileUrl>
                </ns1:tools>
                <ns1:custCommunications>
                    <ns1:displayType>
                        <ns1:prodSvcAnnounce>false</ns1:prodSvcAnnounce>
                        <ns1:trainingInfo>false</ns1:trainingInfo>
                        <ns1:eNewsletters>false</ns1:eNewsletters>
                        <ns1:promotionsOffers>false</ns1:promotionsOffers>
                        <ns1:pressReleases>false</ns1:pressReleases>
                    </ns1:displayType>
                    <ns1:displayMethod>
                        <ns1:email>false</ns1:email>
                        <ns1:fax>false</ns1:fax>
                        <ns1:phone>false</ns1:phone>
                        <ns1:mail>false</ns1:mail>
                    </ns1:displayMethod>
                </ns1:custCommunications>
                <ns1:trackingCodes/>
                <ns1:supportedServices>
                    <ns1:meetingCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>mc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                    </ns1:meetingCenter>
                    <ns1:trainingCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>tc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                    </ns1:trainingCenter>
                    <ns1:supportCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>sc3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                        <ns1:webACD>true</ns1:webACD>
                    </ns1:supportCenter>
                    <ns1:eventCenter>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:pageVersion>ec3300</ns1:pageVersion>
                        <ns1:clientVersion>T33L</ns1:clientVersion>
                        <ns1:marketingAddOn>false</ns1:marketingAddOn>
                        <ns1:optimizeAttendeeBandwidthUsage>false</ns1:optimizeAttendeeBandwidthUsage>
                    </ns1:eventCenter>
                    <ns1:salesCenter>
                        <ns1:enabled>false</ns1:enabled>
                    </ns1:salesCenter>
                </ns1:supportedServices>
                <ns1:securityOptions>
                    <ns1:passwordExpires>false</ns1:passwordExpires>
                    <ns1:passwordLifetime>0</ns1:passwordLifetime>
                    <ns1:ECMeetingsUnlisted>false</ns1:ECMeetingsUnlisted>
                    <ns1:TCMeetingsUnlisted>false</ns1:TCMeetingsUnlisted>
                    <ns1:allMeetingsUnlisted>true</ns1:allMeetingsUnlisted>
                    <ns1:allMeetingsPassword>true</ns1:allMeetingsPassword>
                    <ns1:joinBeforeHost>false</ns1:joinBeforeHost>
                    <ns1:audioBeforeHost>false</ns1:audioBeforeHost>
                    <ns1:audioBeforeHostEC>false</ns1:audioBeforeHostEC>
                    <ns1:audioBeforeHostTC>false</ns1:audioBeforeHostTC>
                    <ns1:changePersonalURL>true</ns1:changePersonalURL>
                    <ns1:changeUserName>false</ns1:changeUserName>
                    <ns1:meetings>
                        <ns1:strictPasswords>true</ns1:strictPasswords>
                    </ns1:meetings>
                    <ns1:strictUserPassword>true</ns1:strictUserPassword>
                    <ns1:accountNotify>false</ns1:accountNotify>
                    <ns1:requireLoginBeforeSiteAccess>false</ns1:requireLoginBeforeSiteAccess>
                    <ns1:changePWDWhenAutoLogin>false</ns1:changePWDWhenAutoLogin>
                    <ns1:enforceBaseline>true</ns1:enforceBaseline>
                    <ns1:passwordChangeIntervalOpt>false</ns1:passwordChangeIntervalOpt>
                    <ns1:passwordChangeInterval>24</ns1:passwordChangeInterval>
                    <ns1:firstAttendeeAsPresenter>false</ns1:firstAttendeeAsPresenter>
                    <ns1:isEnableUUIDLink>true</ns1:isEnableUUIDLink>
                    <ns1:isEnableUUIDLinkForSAC>true</ns1:isEnableUUIDLinkForSAC>
                    <ns1:enforceRecordingPwdForMC>true</ns1:enforceRecordingPwdForMC>
                    <ns1:enforceRecordingPwdForEC>false</ns1:enforceRecordingPwdForEC>
                    <ns1:enforceRecordingPwdForTC>false</ns1:enforceRecordingPwdForTC>
                    <ns1:enforceRecordingPwdForMisc>true</ns1:enforceRecordingPwdForMisc>
                </ns1:securityOptions>
                <ns1:defaults>
                    <ns1:emailReminders>true</ns1:emailReminders>
                    <ns1:entryExitTone>BEEP</ns1:entryExitTone>
                    <ns1:voip>true</ns1:voip>
                    <ns1:teleconference>
                        <ns1:telephonySupport>CALLBACK</ns1:telephonySupport>
                        <ns1:tollFree>true</ns1:tollFree>
                        <ns1:intlLocalCallIn>true</ns1:intlLocalCallIn>
                    </ns1:teleconference>
                    <ns1:joinTeleconfNotPress1>false</ns1:joinTeleconfNotPress1>
                    <ns1:updateTSPAccount>false</ns1:updateTSPAccount>
                </ns1:defaults>
                <ns1:scheduleMeetingOptions>
                    <ns1:scheduleOnBehalf>true</ns1:scheduleOnBehalf>
                    <ns1:saveSessionTemplate>true</ns1:saveSessionTemplate>
                </ns1:scheduleMeetingOptions>
                <ns1:navBarTop>
                    <ns1:button>
                        <ns1:order>1</ns1:order>
                        <ns1:serviceName>Welcome</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>2</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Meeting Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>3</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Event Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>4</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Support Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>5</ns1:order>
                        <ns1:enabled>true</ns1:enabled>
                        <ns1:serviceName>Training Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>6</ns1:order>
                        <ns1:serviceName>Site Administration</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>7</ns1:order>
                        <ns1:enabled>false</ns1:enabled>
                        <ns1:serviceName>Sales Center</ns1:serviceName>
                    </ns1:button>
                    <ns1:displayDisabledService>true</ns1:displayDisabledService>
                </ns1:navBarTop>
                <ns1:navMyWebEx>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:partnerLinks>
                        <ns1:partnerLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:partnerLink>
                    </ns1:partnerLinks>
                    <ns1:partnerIntegration>true</ns1:partnerIntegration>
                    <ns1:support>
                        <ns1:target>NEW</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:target>NEW</ns1:target>
                    </ns1:training>
                </ns1:navMyWebEx>
                <ns1:navAllServices>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>NEW</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:support>
                        <ns1:name>Support</ns1:name>
                        <ns1:target>NEW</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:name>Training</ns1:name>
                        <ns1:target>NEW</ns1:target>
                    </ns1:training>
                    <ns1:supportMenu>
                        <ns1:userGuides>
                            <ns1:target>NEW</ns1:target>
                        </ns1:userGuides>
                        <ns1:downloads>
                            <ns1:target>NEW</ns1:target>
                        </ns1:downloads>
                        <ns1:training>
                            <ns1:target>NEW</ns1:target>
                        </ns1:training>
                        <ns1:contactUs>
                            <ns1:target>NEW</ns1:target>
                        </ns1:contactUs>
                        <ns1:supportMyResources>true</ns1:supportMyResources>
                    </ns1:supportMenu>
                </ns1:navAllServices>
                <ns1:passwordCriteria>
                    <ns1:mixedCase>false</ns1:mixedCase>
                    <ns1:minLength>4</ns1:minLength>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallowWebTextSessions>true</ns1:disallowWebTextSessions>
                    <ns1:disallowWebTextAccounts>true</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>true</ns1:disallowList>
                    <ns1:disallowValue>password</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>pass</ns1:disallowValue>
                </ns1:passwordCriteria>
                <ns1:recordingPasswordCriteria>
                    <ns1:mixedCase>true</ns1:mixedCase>
                    <ns1:minLength>8</ns1:minLength>
                    <ns1:minAlpha>2</ns1:minAlpha>
                    <ns1:minNumeric>1</ns1:minNumeric>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallowWebTextSessions>false</ns1:disallowWebTextSessions>
                    <ns1:disallowList>false</ns1:disallowList>
                    <ns1:disallowValue>password</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>pass</ns1:disallowValue>
                </ns1:recordingPasswordCriteria>
                <ns1:accountPasswordCriteria>
                    <ns1:mixedCase>false</ns1:mixedCase>
                    <ns1:minLength>0</ns1:minLength>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallow3XRepeatedChar>false</ns1:disallow3XRepeatedChar>
                    <ns1:disallowWebTextAccounts>true</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>true</ns1:disallowList>
                    <ns1:disallowValue>password</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>pass</ns1:disallowValue>
                    <ns1:disallowValue>webex</ns1:disallowValue>
                    <ns1:disallowValue>cisco</ns1:disallowValue>
                    <ns1:disallowValue>xebew</ns1:disallowValue>
                    <ns1:disallowValue>ocsic</ns1:disallowValue>
                </ns1:accountPasswordCriteria>
                <ns1:productivityTools>
                    <ns1:enable>true</ns1:enable>
                    <ns1:installOpts>
                        <ns1:autoUpdate>true</ns1:autoUpdate>
                    </ns1:installOpts>
                    <ns1:integrations>
                        <ns1:outlook>true</ns1:outlook>
                        <ns1:outlookForMac>true</ns1:outlookForMac>
                        <ns1:lotusNotes>true</ns1:lotusNotes>
                        <ns1:oneClick>true</ns1:oneClick>
                        <ns1:showSysTrayIcon>true</ns1:showSysTrayIcon>
                        <ns1:office>true</ns1:office>
                        <ns1:excel>true</ns1:excel>
                        <ns1:powerPoint>true</ns1:powerPoint>
                        <ns1:word>true</ns1:word>
                        <ns1:IE>true</ns1:IE>
                        <ns1:firefox>false</ns1:firefox>
                        <ns1:explorerRightClick>false</ns1:explorerRightClick>
                        <ns1:instantMessenger>true</ns1:instantMessenger>
                        <ns1:aolMessenger>false</ns1:aolMessenger>
                        <ns1:googleTalk>false</ns1:googleTalk>
                        <ns1:lotusSametime>true</ns1:lotusSametime>
                        <ns1:skype>true</ns1:skype>
                        <ns1:windowsMessenger>true</ns1:windowsMessenger>
                        <ns1:yahooMessenger>false</ns1:yahooMessenger>
                        <ns1:ciscoIPPhone>false</ns1:ciscoIPPhone>
                        <ns1:pcNow>false</ns1:pcNow>
                        <ns1:iGoogle>false</ns1:iGoogle>
                        <ns1:iPhoneDusting>true</ns1:iPhoneDusting>
                    </ns1:integrations>
                    <ns1:oneClick>
                        <ns1:allowJoinUnlistMeeting>true</ns1:allowJoinUnlistMeeting>
                        <ns1:requireApproveJoin>false</ns1:requireApproveJoin>
                    </ns1:oneClick>
                    <ns1:templates>
                        <ns1:useTemplate>false</ns1:useTemplate>
                    </ns1:templates>
                    <ns1:lockDownPT>
                        <ns1:lockDown>false</ns1:lockDown>
                    </ns1:lockDownPT>
                    <ns1:imSettings>
                        <ns1:attendeeInviteOther>true</ns1:attendeeInviteOther>
                    </ns1:imSettings>
                </ns1:productivityTools>
                <ns1:meetingPlace/>
                <ns1:salesCenter>
                    <ns1:allowJoinWithoutLogin>false</ns1:allowJoinWithoutLogin>
                </ns1:salesCenter>
                <ns1:connectIntegration>
                    <ns1:integratedWebEx11>false</ns1:integratedWebEx11>
                </ns1:connectIntegration>
                <ns1:video>
                    <ns1:HQvideo>true</ns1:HQvideo>
                    <ns1:maxBandwidth>MEDIUM</ns1:maxBandwidth>
                    <ns1:HDvideo>true</ns1:HDvideo>
                </ns1:video>
                <ns1:siteCommonOptions>
                    <ns1:SupportCustomDialRestriction>false</ns1:SupportCustomDialRestriction>
                    <ns1:SupportTelePresence>false</ns1:SupportTelePresence>
                    <ns1:SupportTelePresencePlus>false</ns1:SupportTelePresencePlus>
                    <ns1:EnableCloudTelepresence>true</ns1:EnableCloudTelepresence>
                    <ns1:EnableCMRForAllUsers>true</ns1:EnableCMRForAllUsers>
                    <ns1:enablePersonalMeetingRoom>true</ns1:enablePersonalMeetingRoom>
                    <ns1:SupportAlternateHost>true</ns1:SupportAlternateHost>
                    <ns1:SupportAnyoneHostMeetings>true</ns1:SupportAnyoneHostMeetings>
                </ns1:siteCommonOptions>
                <ns1:samlSSO>
                    <ns1:enableSSO>false</ns1:enableSSO>
                    <ns1:autoAccountCreation>false</ns1:autoAccountCreation>
                </ns1:samlSSO>
                <ns1:attendeeLimitation>
                    <ns1:maxInviteesNumberForMC>1000</ns1:maxInviteesNumberForMC>
                    <ns1:maxRegistrantsNumberForMC>1000</ns1:maxRegistrantsNumberForMC>
                    <ns1:maxInviteesNumberForTC>1000</ns1:maxInviteesNumberForTC>
                    <ns1:maxRegistrantsNumberForTC>1000</ns1:maxRegistrantsNumberForTC>
                    <ns1:maxInviteesNumberForEC>10000</ns1:maxInviteesNumberForEC>
                    <ns1:maxRegistrantsNumberForEC>10000</ns1:maxRegistrantsNumberForEC>
                </ns1:attendeeLimitation>
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForCMRHost>200</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>true</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>40</ns1:accountNumberUsedForCMRHost>
                    <ns1:accountNumberLimitForEEHost>200</ns1:accountNumberLimitForEEHost>
                    <ns1:allowOverageForEEHost>true</ns1:allowOverageForEEHost>
                    <ns1:accountNumberUsedForEEHost>40</ns1:accountNumberUsedForEEHost>
                    <ns1:attendeeCapacityForMC>200</ns1:attendeeCapacityForMC>
                    <ns1:attendeeCapacityForTC>200</ns1:attendeeCapacityForTC>
                    <ns1:attendeeCapacityForEC>200</ns1:attendeeCapacityForEC>
                    <ns1:attendeeCapacityForSC>200</ns1:attendeeCapacityForSC>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

API XML 11.0.0 SP22 aggiornamenti

Limite di dimensione del file per uploadpmrimage

Quando si caricano gli avatar utilizzando l'API uploadpmrimage, una nuova limitazione limita la dimensione del file a 5 MB. I tentativi di caricamento di file più grandi di questo riceveranno un messaggio di errore: "010100 dimensione dell'immagine caricata è troppo grande. Provare un'immagine di dimensioni inferiori a 5 MB."

API XML 11.0.0 SP21 aggiornamenti

Fare clic qui per scaricare lo schema API XML 11,0 SP21.

Nuovo elemento autorecord aggiunto a createmeeting, setmeeting, getmeetinge lstmeeting

Un nuovo elemento, denominato autorecord, è stato aggiunto alle API createmeeting, setmeeting, getmeetinge lstmeeting . autoRecord consente agli utenti di registrare automaticamente Webex riunioni direttamente dallo strumento di pianificazione della riunione. In questo modo, viene fornita la granularità a livello di riunione, in cui il metodo precedente per la registrazione automatica delle riunioni è accessibile solo globalmente a livello di sito.


L' elemento autorecord si applica solo a Webex Meetings. Non si applica a Webex Events o Webex Training.

API interessate:

  • Riunione

    • autoRecord

  • SetMeeting

    • autoRecord

  • GetMeeting

    • autoRecord

  • Lstriunione

    • autoRecord

Aggiornamenti CreateMeeting :

impostazione autoRecord

Il funzionamento quando registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è disabilitata il amministrazione sito

True

Avvia automaticamente la registrazione all'inizio della riunione

Falso (predefinito) o nessun elemento

Non avvia automaticamente la registrazione all'inizio della riunione

Se è abilitata l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete , l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Aggiornamenti di SetMeeting :

impostazione autoRecord

Il funzionamento quando registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è disabilitata il amministrazione sito

True

Avvia automaticamente la registrazione all'inizio della riunione

Falso (predefinito) o nessun elemento

Non avvia automaticamente la registrazione all'inizio della riunione

Se è abilitata l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete , l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Aggiornamenti GetMeeting :

impostazione autoRecord

Il funzionamento quando registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è disabilitata il amministrazione sito

True

Avvia automaticamente la registrazione all'inizio della riunione

False

Non avvia automaticamente la registrazione all'inizio della riunione

Se è abilitata l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete , l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Esempio di risposta GetMeeting:

Aggiornamenti riunione:

impostazione autoRecord

Il funzionamento quando registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è disabilitata il amministrazione sito

True

Avvia automaticamente la registrazione all'inizio della riunione

False

Non avvia automaticamente la registrazione all'inizio della riunione

Se è abilitata l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete , l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Esempio di risposta LstMeeting :

Nuovo elemento isautorecord aggiunto all' API getsessioninfo

Insieme alle modifiche apportate alle API precedenti, è stato aggiunto un nuovo elemento, isautorecord, all' API getsessioninfo . Questo elemento può essere utilizzato per indicare se la registrazione viene avviata automaticamente all'inizio di una riunione.

API interessate:

  • GetSessionInfo

    • isAutoRecord

Aggiornamenti GetSessionInfo :

impostazione isAutoRecord

Il funzionamento quando registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è disabilitata il amministrazione sito

True

Avvia automaticamente la registrazione all'inizio della riunione

False

Non avvia automaticamente la registrazione all'inizio della riunione

Se è abilitata l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete , l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Esempio di risposta GetSessionInfo :

API XML 11.0.0 SP20 aggiornamenti

Fare clic qui per scaricare lo schema API XML 11,0 SP20.

Nuovo elemento returnsharetomerecording aggiunto alla richiesta API lstrecording

Questa modifica è stata annunciata in precedenza nell'API XML 11,0 SP17, ma viene applicata a questo aggiornamento.

Un nuovo elemento, returnsharetomerecording, è stato aggiunto all' API lstrecording . returnShareToMeRecording è un Boolean nella richiesta di registrazionelst.

Questo nuovo elemento è stato aggiunto per supportare la ricerca di registrazioni di partecipanti o invitati. returnShareToMeRecording è un flag che consente all' API lstrecording di essere informato che deve restituire le registrazioni di partecipanti o invitati.

Quando returnsharetomerecording è impostato su true, lstrecording restituisce l'utente della registrazione come proprietario e restituisce anche l'utente della registrazione come partecipante o invitato condiviso dal proprietario.


Se i flag di condivisione automatica e condivisione manuale sono disattivati, la registrazione lstrecording restituisce all'utente solo il proprietario delle registrazioni.

Quando returnsharetomerecording è impostato su falseo questo elemento non è incluso nella richiesta, la registrazione lstrecording segue la stessa logica di prima: Restituisce l'utente delle registrazioni come proprietario.

API interessate:

  • LstRecording

    • returnShareToMeRecording

Aggiornamenti della registrazione :

Elemento sharetome aggiunto alla risposta all'API lstrecording

Questa modifica è stata annunciata in precedenza nell'API XML 11,0 SP17, ma viene applicata a questo aggiornamento.

Un nuovo elemento, sharetome, è stato aggiunto all' API lstrecording . shareToMe è un Boolean nella risposta per lstrecording.

Questo nuovo elemento è stato aggiunto per supportare la ricerca di registrazioni di partecipanti o invitati. shareToMe è un flag per definire se l'utente è il proprietario o un partecipante per la registrazione corrente.

Quando sharetome è true, l'utente non è il proprietario della registrazione corrente. L'utente può essere un partecipante o la registrazione è condivisa dal proprietario.

Quando sharetome è falsoo questo elemento non è nella risposta, la registrazione lstrecording segue la stessa logica di prima: l'utente è il proprietario della registrazione corrente.

API interessate:

  • LstRecording

    • shareToMe

Aggiornamenti della registrazione :

Esempi di richieste di returnShareToMeRecording e sharetome :

<bodyContent xsi:type=”java.com.webex.service.binding..ep.LstRecording”>
<hostWebExID>auto243</hostWebExID>
<createTimeScope>
<createTimeStart>08/15/2018 8:0:0</createTimeStart>
<createTimeEnd>09/05/2018 7:59:59</createTimeEnd>
<timeZoneID>20</timeZoneID>
</createTimeScope>
<serviceTypes>
<serviceType>EventCenter di meetingcenter</serviceType>
<serviceType></serviceType>
<serviceType>trainingcenter</serviceType>
</serviceTypes>
<returnShareToMeRecording>true</returnShareToMeRecording>
</bodyContent>

Esempi di risposta returnShareToMeRecording e sharetome :

Nuovi elementi aggiunti all' API GetEvent

Quattro nuovi elementi sono stati aggiunti all' API GetEvent :

  • Iscetriunione: un valore booleano vero/falso che indica se l'evento Webex supporta Webex piattaforma video 2 (CMR 4,0)

  • sipURL: l'URL utilizzato per accedere Webex riunione video da un sistema o un'applicazione di videoconferenza

  • standaloneDialingIPAddress: Indirizzo IP che può essere utilizzato per chiamare Webex riunione video da un sistema di videoconferenza o un'applicazione

  • Numericpassword: la password per partecipare alla riunione video Webex da un sistema di videoconferenza o un'applicazione

Se il sito supporta Webex video, l'organizzatore dispone di Webex Events privilegi video e l'evento supporta Webex piattaforma video 2 (CMR 4,0), GetEvent restituisce questi elementi. In caso contrario, GetEvent non li restituisce.

API interessate:

  • GetEvent

    • Iscetriunione

    • sipURL

    • standaloneDialingIPAddress

    • Coordinatore Numericpassword

Nuovo elemento Panel numericpassword aggiunto all' API getsessioninfo

GetSessionInfo dispone di un nuovo elemento, coordinatore , che contiene la password per partecipare alla riunione video Webex da un sistema o un'applicazione di videoconferenza.

Se il sito supporta Webex video, l'organizzatore dispone di Webex Events privilegi video e l'evento supporta Webex piattaforma video 2 (CMR 4,0), getsessioninfo restituisce questi quattro elementi:

  • Iscetriunione: un valore booleano vero/falso che indica se l'evento Webex supporta Webex piattaforma video 2 (CMR 4,0)

  • sipURL: l'URL utilizzato per accedere Webex riunione video da un sistema o un'applicazione di videoconferenza

  • standaloneDialingIPAddress: Indirizzo IP che può essere utilizzato per chiamare Webex riunione video da un sistema di videoconferenza o un'applicazione

  • Numericpassword: la password per partecipare alla riunione video Webex da un sistema di videoconferenza o un'applicazione


Per Webex Meetings, questi elementi esistevano già in getsessioninfo:

  • Iscetriunione

  • sipURL

  • standaloneDialingIPAddress

API interessate:

  • GetSessionInfo

    • Coordinatore Numericpassword

Modifiche allo schema apportate a GetEvent e getsessioninfo

Aggiornamenti GetEvent :

Aggiornamenti GetSessionInfo :

API XML 11.0.0 SP18 aggiornamenti

Fare clic qui per scaricare lo schema API XML 11,0 SP18.

Nuovo elemento enablecloudtelepresence aggiunto all' API GetSite

Un nuovo elemento, enablecloudtelepresence è stato aggiunto all' API GetSite .

Quando l'opzione enablecetforallusers è abilitata, Webex verifica se l'utente supporta Webex video (CMR). Ora restituisce anche un nuovo elemento enablecloudtelepresence nell' API GetSite .

API interessate:

  • getSite

  • EnableCloudTelepresence

Risposta di esempio getSite:

API XML 11.0.0 SP17 aggiornamenti

Nuovo elemento returnsharetomerecording aggiunto alla richiesta API lstrecording

Un nuovo elemento, returnsharetomerecording, è stato aggiunto all' API lstrecording . returnShareToMeRecording è un Boolean nella richiesta di registrazionelst.

Questo nuovo elemento è stato aggiunto per supportare la trazione delle registrazioni dei partecipanti o degli invitati. returnShareToMeRecording è un flag che consente all' API lstrecording di essere informato che deve restituire le registrazioni di partecipanti o invitati.

Quando returnsharetomerecording è impostato su true, lstrecording restituisce l'utente delle registrazioni come proprietario e restituisce anche l'utente delle registrazioni come partecipante o invitato condiviso dal proprietario.


Se i flag di condivisione automatica e condivisione manuale sono disabilitati, la registrazione lstrecording restituisce solo l'utente come proprietario delle registrazioni.

Quando returnsharetomerecording è impostato su falseo questo elemento non è incluso nella richiesta, la registrazione lstrecording segue la stessa logica di prima: Restituisce l'utente delle registrazioni come proprietario.

API interessate:

  • LstRecording

  • returnShareToMeRecording

Aggiornamenti della registrazione :

Nuovo elemento sharetome aggiunto alla risposta all'API lstrecording

Un nuovo elemento, sharetome, è stato aggiunto all' API lstrecording . shareToMe è un Boolean nella risposta per lstrecording.

Questo nuovo elemento è stato aggiunto per supportare la trazione delle registrazioni dei partecipanti o degli invitati. shareToMe è un flag per definire se l'utente è il proprietario o il partecipante o l'invitato per la registrazione corrente.

Quando sharetome è true, l'utente non è il proprietario della registrazione corrente. L'utente può essere un partecipante o un invitato o la registrazione è condivisa dal proprietario.

Quando sharetome è falsoo questo elemento non è nella risposta, la registrazione lstrecording segue la stessa logica di prima: l'utente è il proprietario della registrazione corrente.

API interessate:

  • LstRecording

  • shareToMe

Aggiornamenti della registrazione :

Nuovi elementi per la capacità dei partecipanti aggiunti alla risposta API GetSite

Quattro nuovi elementi sono stati aggiunti all' API GetSite per indicare la capacità dei partecipanti per i seguenti servizi di Webex:

attendeeCapacityForMC -Webex Meetings

attendeeCapacityForEC – Webex Events

attendeeCapacityForTC – Webex Training

attendeeCapacityForSC – Webex Support

Questi valori restituiti indicano il numero massimo di partecipanti che possono avere la riunione, l'evento o la sessione. Sono elementi figlio dell' elemento cisitelicenseinfo nella risposta.

API interessate:

  • getSite

  • attendeeCapacityForMC

  • attendeeCapacityForEC

  • attendeeCapacityForTC

  • attendeeCapacityForSC

Esempio di risposta getSite:

<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></serv:result>
            <serv:gsbStatus>primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
            <ns1:siteInstance> ... ... <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
                    <ns1:allowOverageForMC>falso falso falso falso</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>falso</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC></ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC></ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost></ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                    <ns1:attendeeCapacityForMC>1000</ns1:attendeeCapacityForMC>
                    <ns1:attendeeCapacityForTC>1000</ns1:attendeeCapacityForTC>
                    <ns1:attendeeCapacityForEC>3000</ns1:attendeeCapacityForEC>
                    <ns1:attendeeCapacityForSC>500</ns1:attendeeCapacityForSC>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

API XML 11.0.0 SP16 aggiornamenti

Nuovo API hoststreamurl aggiunto a lstrecordingresponse

L'elemento hoststreamurl è stato aggiunto alla risposta lstrecording come parte dei dettagli della registrazione. hostStreamURL restituisce un URL per l'organizzatore da utilizzare per visualizzare la registrazione senza dover prima eseguire l'accesso. Questo URL è valido per 30 minuti dopo la generazione.

API interessate:

  • hostStreamURL

Esempio di risposta hostStreamURL :

<xsd:complexType name="recordingType">
<xsd:sequence>
<xsd:element name="recordingID" type="xsd:int"/>
<xsd:element name="hostWebExID" type="xsd:string"/>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="description" type="xsd:string"/>
<xsd:element name="createTime" type="xsd:string"/>
<xsd:element name="timeZoneID" type="xsd:int"/>
<xsd:element name="size" type="xsd:float"/>
<xsd:element name="streamURL" type="xsd:string"/>
<xsd:element name="hostStreamURL" type="xsd:string" minOccurs="0"/>
<xsd:element name="fileURL" type="xsd:string"/>

API GetSite utilizza la nuova modellazione WebDB per restituire i dati

Tramite richiesta del cliente, l'API GetSite ora recupera una licenza organizzatore più accurata, dati di report di utilizzo e altri dati utilizzando la nuova modellazione WEBDB per i siti ci.

API interessate:

  • GetSite

Esempio di risposta GetSite:

<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></serv:result>
            <serv:gsbStatus>primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
            <ns1:siteInstance> ... ... <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
                    <ns1:allowOverageForMC>falso falso falso falso</ns1:allowOverageForMC>
                    <ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC>falso</ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC></ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC></ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost></ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Esempio di risposta GetSite per i siti EE:

<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></serv:result>
            <serv:gsbStatus>primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
            <ns1:siteInstance> ... ... <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForCMRHost>80</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>vero</ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>99</ns1:accountNumberUsedForCMRHost>
                    <ns1:accountNumberLimitForEEHost>999999</ns1:accountNumberLimitForEEHost>
                    <ns1:allowOverageForEEHost>falso</ns1:allowOverageForEEHost>
                    <ns1:accountNumberUsedForEEHost>368</ns1:accountNumberUsedForEEHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

API XML 11.0.0 SP15 aggiornamenti

Restituire Webex Meetings collegamento alla riunione utilizzando l'API GetSessionsInfo

Lo schema per l' API getsessioninfo presenta un nuovo valore restituito, meetinglink. È possibile utilizzare un collegamento alla riunione per avviare una riunione Webex come organizzatore o partecipando a una riunione Webex come partecipante.

API interessate:

  • GetSessionInfo

  • Collegamento meetingLink

Esempio di risposta GetSessionInfo :

    <ep:meetingLink>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=m265e64705c6660d4132c2d4f19aed7e7</ep:meetingLink>
</serv:bodyContent>

Nuova condizione per l'esecuzione di query tramite RecordingID su lstrecording API

Ora è possibile utilizzare lstrecording per interrogare le registrazioni utilizzando il protocollo RecordingID. Esistono due tipi di ID registrazione:

  • ID registrazione per Webex Meetings, Webex Events e Webex Training

  • ID registrazione NBR per registrazioni varie

Se è presente un elemento ServiceType nella richiesta XML, lstrecording restituisce solo una registrazione del servizio (Webex Meetings, Webex Events e Webex Training).

Se non è presente alcun elemento ServiceType nella richiesta XML, la registrazione lstrecording restituisce solo una registrazione NBR.

API interessate:

  • LstRecording

  • RecordingID

Esempi di risposta della registrazione :

Esempio di richiesta per un ID registrazione servizio:

<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
    <serviceTypes>
        <serviceType>Organizzazionecenter</serviceType>
        <serviceType>EventCenter</serviceType>
        <serviceType>trainingcenter</serviceType>
    </serviceTypes>
    <recordingID>974164492</recordingID>
    <order>
         <orderBy>CreateTime</orderBy>
         <orderAD>desc</orderAD>
         <orderBy>HostID</orderBy>
         <orderAD>ASC</orderAD>
         <orderBy>RecordName</orderBy>
         <orderAD>ASC</orderAD>
    </order>
</bodyContent>

Esempio di richiesta per un ID registrazione NBR:

<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
    <recordingID>974154032</recordingID>
    <order>
         <orderBy>CREATETIME</orderBy>
         <orderAD>desc</orderAD>
         <orderBy>HostID</orderBy>
         <orderAD>ASC</orderAD>
         <orderBy>RecordName</orderBy>
         <orderAD>ASC</orderAD>
    </order>
</bodyContent>

API XML 11.0.0 SP14 aggiornamenti

Report di riepilogo utilizzo preliminare per Meeting Center

Sono state aggiunte due nuove API per Meeting Center report preliminari, lstmeetingusagepreliminaryhistory e lstmeetingattendeepreliminaryhistory. Questi avranno lo stesso comportamento di lsteventsessionpreliminaryhistory e lsteventattendeepreliminaryhistory nel report finale.

API interessate:

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

Esempio di richiesta di LstmeetingusagePreliminaryHistory :

<?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"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <webExID>TestUser</webExID>
            <password>* * * *</password>
            <siteName>TestSite</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingusagePreliminaryHistory">
            <startTimeScope>
                <sessionStartTimeStart>4/23/2018 00:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>4/24/2018 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>e</listMethod>
            </listControl>
            <order>
                <orderBy>StartTime</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>confname</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>confid</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

Esempio di risposta di LstmeetingusagePreliminaryHistory :

<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>Successo</serv:result>
            <serv:gsbStatus>principale</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingusagePreliminaryHistoryResponse">
            <history:meetingUsagePreliminaryHistory>
                <history:confID>93115261364733685</history:confID>
                <history:sessionKey>800150023</history:sessionKey>
                <history:confName>200804231215</history:confName>
                <history:openTime>04/23/2018 19:16:34</history:openTime>
                <history:timeZoneID>4</history:timeZoneID>
                <history:meetingType>Pro</history:meetingType>
                <history:timeZoneWithDST>San Francisco (ora legale Pacifico, GMT-07:00)</history:timeZoneWithDST>
                <history:trackingCode>
                    <com:trackingCode1>mytrackingcode1</com:trackingCode1>
                    <com:trackingCode2>mytrackingcode2</com:trackingCode2>
                </history:trackingCode>
                <history:registered>1</history:registered>
                <history:invited>1</history:invited>
                <history:attended>3</history:attended>
            </history:meetingUsagePreliminaryHistory>
            <history:matchingRecords>
                <serv:total>1</serv:total>
                <serv:returned>1</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Esempio di richiesta di LstmeetingattendeePreliminaryHistory :

<?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"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <webExID>TestUser</webExID>
            <password>* * * *</password>
            <siteName>TestSite</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingattendeePreliminaryHistory">
            <startTimeScope>
                <sessionStartTimeStart>4/23/2018 00:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>4/24/2018 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>e</listMethod>
            </listControl>
            <order>
                <orderBy>StartTime</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>confid</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

Esempio di risposta LstmeetingattendeePreliminaryHistory :

<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>Successo</serv:result>
            <serv:gsbStatus>principale</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingattendeePreliminaryHistoryResponse">
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:company>xyz</history:company>
                <history:title>DJ</history:title>
                <history:phoneNumber>1222654-3210,,,,</history:phoneNumber>
                <history:address1>1 qualsiasi strada</history:address1>
                <history:address2>xyz</history:address2>
                <history:city>sanjose</history:city>
                <history:state>CA</history:state>
                <history:country>Usa</history:country>
                <history:zipCode>95111</history:zipCode>
                <history:name>utente Test2</history:name>
                <history:email>UT2@qa.webex.com</history:email>
                <history:joinTime>04/23/2018 19:13:06</history:joinTime>
                <history:participantType>partecipante</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name>zzz zzzz</history:name>
                <history:email>Z6@webex.com</history:email>
                <history:joinTime>04/23/2018 19:14:10</history:joinTime>
                <history:participantType>partecipante</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name>test organizzatore</history:name>
                <history:email>testuser@webex.com</history:email>
                <history:joinTime>04/23/2018 19:12:42</history:joinTime>
                <history:participantType>partecipante</history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:matchingRecords>
                <serv:total>3</serv:total>
                <serv:returned>3</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Restituzione dell'URL SIP e dell'URL Skype da API GLA getsessioninfo

Due nuovi elementi <sipURL> e <skypeURL>, sono stati aggiunti alla risposta quando si chiama l' API GLA getsessioninfo . Questi elementi sono elementi di base che possono essere restituiti per l'accesso anonimo.

  • <sipURL> può essere utilizzato per accedere alle riunioni da un TelePresence o da un altro dispositivo video Cisco. In questo modo, solo le riunioni che utilizzano le versioni della piattaforma video Cisco 1,0 o 2,0 devono restituire l' <sipURL> elemento.

  • <skypeURL> può essere utilizzato per accedere alle riunioni da un'app Microsoft Skype, senza limitazioni o condizioni, in modo che possa essere restituita per ciascuna chiamata.

API interessate:

  • GetSessionInfo

Esempio di risposta:

Ritorno dell'URL SIP e del collegamento della riunione da API getmeeting

Tre nuovi elementi,, <isCETMeeting><meetingLink>e <sipURL>, sono stati aggiunti alla risposta quando si chiama l' API getmeeting .

  • <isCETMeeting> Restituisce se la riunione utilizza una piattaforma video Cisco (supporta TelePresence e video).

  • <meetingLink> può essere utilizzato per la connessione alle riunioni.

  • <sipURL> può essere utilizzato per accedere alle riunioni da un TelePresence o da un altro dispositivo video Cisco. In questo modo, solo le riunioni che utilizzano le versioni della piattaforma video Cisco 1,0 o 2,0 devono restituire l'elemento.

API interessate:

  • GetMeeting

Esempio di risposta GetMeeting:

API XML 11.0.0 SP13 aggiornamenti

Annuncio di deprecazione dell' <siteID> elemento nel genitore <securityContext>

Cisco prevede di deprecare l' <siteID> elemento nell'elemento principale <securityContext> e sostituirlo con <siteName>. A causa di un numero elevato di <siteID> elementi spesso modificati durante le migrazioni dei siti, le organizzazioni comportano costi di manutenzione elevati per continuare a utilizzare questo elemento. Questa è una notifica anticipata di due anni.

  • Per i clienti esistenti Webex l'impatto avrà luogo il 1° maggio 2020.

  • I nuovi clienti devono utilizzare l'elemento a partire dal 1° maggio 2018.<siteName>

  • I clienti che effettuano integrazioni con CI, Spark o sistema Atlas, devono utilizzare l'elemento a partire dal 1° maggio 2018.<siteName>

API interessate:

  • <siteName>

  • <securityContext>

Convalida dati degli <tollCallInData> elementi e <tollFreeCallInData>

A partire dal 1 giugno 2018, entrambe le <tollCallInData><tollFreeCallInData> API e saranno dati convalidati. Ciò influisce sulle <CreateUser><SetUser> API e.

I siti che utilizzano stringhe non valide o stringhe formattate in modo errato nei dati di chiamata in ingresso devono correggere le stringhe affinché questi elementi passino la convalida dei dati.

Di seguito sono riportati alcuni esempi di CreateUser e SETUSER, tollcallindata e tollfreecallindata nel formato corretto:

<tspAccount>
    <tspAccount>
        <tollFreeCallInNumber>86, 123, 4567000</tollFreeCallInNumber>
        <tollFreeCallInData>1, 86</tollFreeCallInData>
        <accountIndex>1</accountIndex>
        <tollCallInNumber>86, 123, 4567890</tollCallInNumber>
        <tollCallInData>0, 86</tollCallInData>
        <subscriberAccessCode>12341234</subscriberAccessCode>
        <participantAccessCode>12341234</participantAccessCode>
        <createOnBridge>falso</createOnBridge>
        <defaultFlag>falso</defaultFlag>
    </tspAccount>
</tspAccount> ...

API XML 11.0.0 SP12 aggiornamenti

Due nuove API SetContact e DelContacts

Lo schema API XML precedentemente disponeva solo delle due API createcontacts e lstContacts, che non fornivo la gestione completa dei contatti utente. Per offrire una migliore funzionalità per la gestione dei contatti utente mediante l'API XML, sono state aggiunte queste due nuove API, SetContact e delcontacts.

API

Note

SetContact

Chiamare questa API per modificare le informazioni di contatto come e-mail, nome, titolo e lingua.

Eccezioni:

  • Se il contatto non viene trovato dall' elemento ContactEmail , viene restituita l'eccezione 140004 "contatto non trovato"

  • Se il sito Webex non supporta una determinata lingua, viene restituita l'eccezione 030060 "lingua non valida"

  • Se il nuovo indirizzo e-mail che l'utente desidera modificare è un duplicato con un altro contatto nell'elenco dei contatti personali , l'eccezione 140001 "viene utilizzato da un altro contatto" viene restituito

DelContacts

Chiamare questa API per eliminare uno o più contatti dall' elenco di contatti personali in base ai messaggi e-mail.

contactID viene restituito se il messaggio e-mail specificato è disponibile dall' elenco contatti personali e ignora il messaggio e-mail specificato se non è presente nell' elenco di contatti personali .

Se tutti i messaggi e-mail non vengono trovati nell' elenco dei contatti personali , viene restituita l'eccezione 00015 (spiacenti, nessun record trovato).

API interessate:

  • SetContact

  • DelContacts

Esempio di richiesta SetContact:

<?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>UserID nome utente</siteName>
      <webExID></webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.SetContact">
            <contactEmail>Indirizzo E-mail di contatto</contactEmail>
           <contact>
                <name>nuovo nome contatto</name>
                <email>nuovo contatto e-mail</email>
                <title>Nuovo titolo</title>
                <company>Nuova società nuove</company>
                <notes>note nuovo</notes>
                <url>collegamento</url>
                <phones>
                    <phone>1,, 408 # # # # # #,,,,</phone>
                    <mobilePhone>1,, 408 # # # # # #,,,,</mobilePhone>
                    <fax>1,, 408 # # # # # #,,,,</fax>
                </phones>
                <address>
                    <address1>Nuovo indirizzo 1</address1>
                    <address2>nuovo indirizzo 2</address2>
                    <city>nuova città nuovo</city>
                    <state>stato nuovo</state>
                    <zipCode>ZipCode nuova</zipCode>
                    <country>società</country>
                </address>
                <language>Nuova lingua</language>
            </contact>
</bodyContent>
</body>
</serv:message>

Esempio di risposta SetContact:

<?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: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></serv:result>
            <serv:gsbStatus>primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="ep:setContactResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
    </serv:body>
</serv:message>

Esempio di richiesta DelContacts:

<?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>UserID nome utente</siteName>
      <webExID></webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.DelContacts">
        <contactEmail>contact1@qa.webex.com</contactEmail>
        <contactEmail>contact2@qa.webex.com</contactEmail>
</bodyContent>
</body>
</serv:message>

Esempi di risposta DelContacts:

In questo esempio, due contatti esistenti vengono eliminati dall' elenco dei contatti personali .

<?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: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></serv:result>
            <serv:gsbStatus>primaria riuscita</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="ep:delContactsResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ep:contactID>31830997</ep:contactID>
            <ep:contactID>31831002</ep:contactID>
        </serv:bodyContent>
    </serv:body>
</serv:message>

In questo esempio, i messaggi e-mail non sono presenti nell' elenco dei contatti personali .

<?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: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>ERRORE</serv:result>
            <serv:reason>non riuscito, nessun record trovato</serv:reason>
            <serv:gsbStatus>principale</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

API XML 11.0.0 SP11 aggiornamenti

Nuova API LstTrainingPollResultsHistory

L' API lsttrainingpollresultshistory è stata originariamente implementata nell'API URL. Tramite richiesta del cliente, è ora implementato nell'API XML.

I risultati del sondaggio di elenco vengono restituiti inserendo una Training Center SessionKey. L'API può essere richiesta dal proprietario della sessione Training Center o da un amministratore del sito.


È necessario abilitare l'impostazione del sondaggio TC avanzato prima che i risultati dei sondaggi di formazione vengano memorizzati nel Webex DB:

API interessate:

  • LstTrainingPollResultsHistory

Esempio di richiesta Lsttrainingpollleaderthistory :

<?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"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <!-- <returnAdditionalInfo>true</returnAdditionalInfo> -->
            <webExID>UT2</webExID>
            <password>xxxxxxx</password>
            <siteName>testsite1</siteName>
        </securityContext>
    </header>
    <body>
        <bodyContent
xsi:type="java:com.webex.service.binding.history.LstTrainingPollResultsHistory"
            xmlns:meet="http://www.webex.com/schemas/2002/06/service/history">
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
            </listControl>
            <confID>81722715648558691</confID>
        </bodyContent>
    </body>
</serv:message>

La richiesta è solo per 11.0.0 API T32/XML.

Esempio di risposta Lsttrainingpollleaderthistory :

<?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:lstTrainingPollResultsHistoryResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <history:matchingRecords>
                <serv:total>2</serv:total>
                <serv:returned>2</serv:returned>
                <serv:startFrom>1</serv:startFrom>
            </history:matchingRecords>
            <history:sessionInfo>
                <history:sessionKey>81901776767288734</history:sessionKey>
                <history:confName>TC poll test 20171220 1635</history:confName>
                <history:host>John Doe</history:host>
            </history:sessionInfo>
            <history:polls>
                <history:poll>
                    <history:pollDesc>Test</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>12/20/2017 16:54:48</history:startTime>
                    <history:endTime>12/20/2017 16:58:07</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>test question 1 (multi-choice/single-answer)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test answer 4</history:answerChoice>
                                <history:answerChoice>test answer 3</history:answerChoice>
                                <history:answerChoice correct="true">test answer 2</history:answerChoice>
                                <history:answerChoice>test answer 1</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>test answer 2</history:pollResponse>
                                    <history:isCorrect>true</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>test answer 1</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>test question 2 (multi-choiec.multi-answer)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test answer D</history:answerChoice>
                                <history:answerChoice>test answer C</history:answerChoice>
                                <history:answerChoice correct="true">test answer B</history:answerChoice>
                                <history:answerChoice correct="true">test answer A</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>test answer B,test answer A</history:pollResponse>
                                    <history:isCorrect>true</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>test answer D,test answer C,test answer B,test answer A</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                    <history:isCorrect>false</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>test question 2 (short answer)</history:questionDesc>
                            <history:questionType>3</history:questionType>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465742</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>ans1</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465747</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>ans2</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465752</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
                <history:poll>
                    <history:pollDesc>Survey</history:pollDesc>
                    <history:timeLimit>300</history:timeLimit>
                    <history:startTime>12/20/2017 16:58:57</history:startTime>
                    <history:endTime>12/20/2017 17:02:39</history:endTime>
                    <history:numAttendees>3</history:numAttendees>
                    <history:questions>
                        <history:question>
                            <history:questionSequence>1</history:questionSequence>
                            <history:questionDesc>survey question 1 (multi-choiec/sinngle-answer)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>survey answer 3</history:answerChoice>
                                <history:answerChoice>survey answer 2</history:answerChoice>
                                <history:answerChoice>survey answer 1</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>survey answer 3</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465762</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>survey answer 2</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465767</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>survey question 2 (multi-choiec/multi-answer)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>survey answer D</history:answerChoice>
                                <history:answerChoice>survey answer C</history:answerChoice>
                                <history:answerChoice>survey answer B</history:answerChoice>
                                <history:answerChoice>survey answer A</history:answerChoice>
                            </history:answerChoices>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>survey answer D,survey answer C</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465762</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>survey answer C,survey answer B</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465767</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>survey question 3 (short answer)</history:questionDesc>
                            <history:questionType>3</history:questionType>
                            <history:attendees>
                                <history:attendee>
                                    <history:username>2128465757</history:username>
                                    <history:fullName>test</history:fullName>
                                    <history:email>test@qa.webex.com</history:email>
                                    <history:pollResponse>AAA</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465762</history:username>
                                    <history:fullName>test2</history:fullName>
                                    <history:email>test2@qa.webex.com</history:email>
                                    <history:pollResponse>BBB</history:pollResponse>
                                </history:attendee>
                                <history:attendee>
                                    <history:username>2128465767</history:username>
                                    <history:fullName>test3</history:fullName>
                                    <history:email>test3@qa.webex.com</history:email>
                                    <history:pollResponse>No Answer</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
            </history:polls>
        </serv:bodyContent>
    </serv:body>
</serv:message>

La risposta è diversa se la riunione non viene trovata, non appartiene all'utente che lo richiede o se l'utente che lo richiede non è anche un amministratore del sito.

Esempio di risposta:

<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>ERRORE</serv:result>
            <serv:reason>non riuscito, nessun record trovato</serv:reason>
            <serv:gsbStatus>principale</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Nuovo partecipante deesendvideo opzione nel createtrainingsession API, settrainingsessione gettrainingsession

Poiché le opzioni disponibili quando si pianifica una sessione di Training Center includono Invia video, l'API XML ora ha aggiunto l' opzione attendeesendvideo per creare, ottenere e impostare le api per le sessioni Training Center.

API interessate:

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

Design

L'opzione è stata memorizzata nella tabella DB WbxMMConfParam/paramValue As paramName =' optionSupportSendVideo '

Aggiornamenti della richiesta CreateTrainingSession :

Aggiornamenti delle richieste di SetTrainingSession :

La richiesta è solo per 11.0.0 API T32/XML.

Aggiornamenti risposta GetTrainingSession :

Modifica dimensione confname limite massimo a 128 caratteri di visualizzazione

La stringa nome conferenza confname ora è limitata a un massimo di 128 caratteri di visualizzazione. Questa modifica si allinea alla limitazione della Home page J2EE. Se una richiesta API include confname vuoto o supera la lunghezza del carattere di visualizzazione 128, viene visualizzato il seguente messaggio di errore:

"060065 nome conferenza di input illegale. Il nome della conferenza non può essere vuoto o superare la lunghezza massima del carattere di visualizzazione 128. "

API interessate:

  • ConfName

Messaggio di eccezione modificato nell'API LstRecording

Il messaggio di eccezione generato quando l'ambito del tempo di interrogazione supera il limite massimo consentito per l'API lstrecording è stato modificato. Per impostazione predefinita, le query supportano 4 settimane di registrazioni. Le richieste di più di quattro settimane ricevono il seguente messaggio di errore:

"999999 ha superato l'intervallo massimo di query di 28 giorni".

API interessate:

  • LstRecording

API XML 11.0.0 SP10 aggiornamenti

L'aggiornamento API XML 11,0 SP10 non presenta modifiche allo schema.