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

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

Per aggiornamenti per l'API XML 11 SP9 e versioni precedenti, andare a Cisco devnet.

Aggiornamenti 39.11.0 API XML

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

LstSummaryUser può eseguire query sugli account utente in base all'ora Ultima modifica

Stiamo aggiornando l' API LstSummaryUser per consentire agli utenti di interrogare gli account utente in base all'ora di modifica dell'ultima. Tre nuovi elementi, modifiedDateStart, modifiedDateEnde lastModifiedTime, sono stati aggiunti all'API.


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

API interessate:

  • LstSummaryUser

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>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>* * 5124 * * *</use:userID>                 <use:webExId>* * * Mr * * *</use:webExId>                 <use:firstName>* * * Mr * * *</use:firstName>                 <use:lastName>* * * est * * * * * *</use:lastName>                 <use:email>est * * * @qa. Webex.com</use:email>
                <use:userRoleType>ORGANIZZA</use:userRoleType>
                <use:registrationDate>06/19/2016 22:13:06</use:registrationDate>
                <use:active>DISATTIVATO</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>10/19/2019 23:13:14</use:lastLoginTime>
                <use:lastModifiedTime>11/11/2019 19:11:11</use:lastModifiedTime>
            </use:user>

Aggiornamenti 39.10.0 API XML

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

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

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

API interessate:

  • GetSessionInfo

  • GetUserCard

Aggiornamenti di sicurezza e risposta CAPTCHA:

GetSessionInfo risposta 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>ERRORE</serv:result>
            <serv:reason>Riunione 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>

GetSessionInfo risposta 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>ERRORE</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>

GetSessionInfo risposta a CAPTCHAID errato e CAPTCHAWord 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>ERRORE</serv:result>
            <serv:reason>ID CAPTCHA e parola non validi o mancanti</serv:reason>
            <serv:gsbStatus>PRINCIPALE</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 LstSummaryUser per la restituzione degli URL della sala riunioni personale

È stato aggiunto un nuovo elemento di risposta, personalMeetingRoomURL, all' API LstSummaryUser.

Esempio di risposta LstSummaryUser:

Aggiornamenti 39.9.0 API XML

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

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

Il supporto per il formato URL SIP breve per PMRs ha impatto sulleAPI GetSessionInfo, getmeetinging, GetUsere modoper tirarmi . Un nuovo elemento di risposta denominato displayMeetingUrl è stato aggiunto alle API GetUser e modoper tirarmi ed è già presente in GetSessionInfo e getmeeting. displayMeetingUrl restituisce l'URL PMR di un utente.

API interessate:

  • GetSessionInfo

  • Getmeeting

  • GetUser

  • Modoper tirarmi

Esempio risposta GetUser:

Esempio di risposta modoper tirarmi:

GetSessionInfo restituisce gli elementi necessari per l'accesso anonimo

Come requisito di sicurezza, solo gli elementi necessari ora possono essere restituiti 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>true</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)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>falso</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>true</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>falso</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

Modifica del funzionamento delle riunioni e degli 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 Webex abilitata per dispositivi non video.

API interessate:

  • CreateMeeting

  • Riunione

  • CreateEvent

  • SetEvent

Aggiornamenti 39.8.0 API XML

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

LsttrainingattendeeHistory ora restituisce l'attenzione del partecipante alla riunione

Un nuovo elemento di risposta, attentionToDurationPercentage, è stato aggiunto all' API LsttrainingattendeeHistory. LsttrainingattendeeHistory restituisce i dettagli di attenzione del partecipante alla riunione. L'elemento viene restituito in questo formato:

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

API interessate:

  • LsttrainingattendeeHistory

    • attentionToDurationPercentage

    • 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 i conteggi delle licenze diversi nell' API GetSite .

API interessate:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

Riprogettazione GetSiteFT e SetSiteFT

Le API GetSiteFT e SetSiteFT sono state riprogettate per consentire l'attivazione delle funzioni dinamiche.

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>{nomesito}</siteName>             <accessToken>{Questo è il token di accesso dell'account macchina}</accessToken>         </securityContext>     </header>     <bodyContent xsi:type="java:com.webex.service.binding.site.GetSiteFT">         <featureToggles>             <name>SupportCrossLaunch</name>
            <name>RemoveCMRLicenseSA</name>
        </featureToggles>
    </bodyContent>

</serv:message>

Esempio 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>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="ns1:getSiteFTResponse">
            <ns1:featureToggles>
                <ns1:featureToggle>
                    <ns1:name>SupportCrossLaunch</ns1:name>
                    <ns1:value>falso</ns1:value>
                </ns1:featureToggle>
                <ns1:featureToggle>
                    <ns1:name>RemoveCMRLicenseSA</ns1:name>
                    <ns1:value>falso</ns1:value>
                </ns1:featureToggle>
            </ns1:featureToggles>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Esempio di richiesta di postsite :

<?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>{nomesito}</siteName>             <accessToken>{Questo è il token di accesso dell'account macchina}</accessToken>         </securityContext>     </header>     <body>         <bodyContent xsi:type="java:com.webex.service.binding.site.SetSiteFT">             <featureToggles>                 <featureToggle>                     <name>SupportCrossLaunch</name>
                    <value>falso</value>
                </featureToggle>
                <featureToggle>
                    <name>SupportPeopleInsight</name>
                    <value>true</value>
                </featureToggle>
            </featureToggles>
        </bodyContent>
    </body>
</serv:message>

Esempio di SetSiteFT resonse:

<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>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="ns1:setSiteFTResponse"/>
    </serv:body>
</serv:message>

Lunghezza Descrizione riunione ora limitata a 2500 caratteri

Le seguenti API ora dispongono della 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 39.5.0 API XML

Nuovo elemento videoMeshInterclusters aggiunto agli schemi di postsite e GetSite

Un nuovo elemento, videoMeshInterclusters, è stato aggiunto all' elemento di postsite . videoMeshInterclusters contiene anche tre elementi figlio videoMeshHomeCluster1, videoMeshHomeCluster2e videoMeshHomeCluster3.

API interessate:

  • SetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

Aggiornamenti richieste per il sito :

Aggiornamenti risposta GetSite:

Aggiornamenti 39.3.0 API XML

URL SIP breve in API XML, nuovo elemento displayMeetingUrl

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

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

Per semplificare la partecipazione alle riunioni, è stato rimosso il requisito per inserire il nome del sito dall'URI SIP della riunione: meeting_number@webex.com. Per mantenere la compatibilità all'indietro, il vecchio formato funziona in sipURL e il 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>

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>

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>

Esempio e-mail:

Descrizione lunghezza ora limitata a 1024 caratteri

Le seguenti API ora hanno la lunghezza del contenuto dell'elemento di descrizione 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 i 1024 caratteri, viene restituito un messaggio di errore: "060067 Descrizione dell'input non valido. La descrizione non può superare la lunghezza massima di 1024 caratteri di visualizzazione. "

Esempio di risposta per Descrizione lunghezza 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>ERRORE</serv:result>
            <serv:reason>
Descrizione ingresso non valida. La descrizione non può superare la lunghezza massima di 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 esiste un utente anonimo che utilizza l'API

Per garantire una maggiore sicurezza, stiamo diminuendo la quantità di informazioni restituite da GetSessionInfo quando esiste un utente partecipante anonimo che utilizza l'API. In questo aggiornamento, verranno Riduci 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>

Confronti di risposta:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS</ep:status>
    <ep:isLocked>falso</ep:isLocked>
    <ep:sessionkey>712419789</ep:sessionkey>
    <ep:confID>120396209273701973</ep:confID>
    <ep:accessControl>
        <ep:sessionPassword></ep:sessionPassword>   <!--Removed-->
        <ep:listStatus>PRIVATA</ep:listStatus>
        <ep:registration>falso</ep:registration>
        <ep:passwordReq>falso</ep:passwordReq>
        <ep:isEnforceAudioPassword>falso</ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin>falso</ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>Sala riunioni personale di Simon test</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType>MeetingCenter</ep:serviceType>
        <ep:isRecurring>falso</ep:isRecurring>
        <ep:agendaFormat>TESTO</ep:agendaFormat>
        <ep:descriptionFormat>TESTO</ep:descriptionFormat>
        <ep:isException>falso</ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException>falso</ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>Richiamata</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 * [codice] #,,, [AttendeeID] # | SilentDialInSequence: [AccessNumber],, * 01 * [codice] # [AttendeeID] # * 01 * | AutoLGDialInSequence: [AccessNumber],, * 00 * [codice] #,,, [ProfileID] #,,, [PIN] # | SilentLGDialInSequence: [AccessNumber],, * 01 * [codice] # [ProfileID] # [PIN] # * 01 * | AutoLGPWDialInSequence: [AccessNumber],, * 00 * [codice] #,,, [ProfileID] #,,, [PIN] #,,, [password] # | SilentLGPWDialInSequence: [AccessNumber],, * 01 * [codice] # [ProfileID] # [PIN] # [password] # * 01 * falsa falsa</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>chiamata in ingresso numero gratuito (USA/Canada)</ep:tollFreeCallInLabel>   <!--Removed-->             <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->         </ep:labels>  <!--Removed-->         <ep:isMPAudio>falso</ep:isMPAudio>  <!--Removed-->         <ep:voip>vero</ep:voip> <!--Removed-->         <ep:enableTSP>falso</ep:enableTSP>  <!--Removed-->     </ep:telephony>   <!--Removed-->     <ep:host>         <ep:firstName>Simon</ep:firstName>
        <ep:lastName>Test</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>falso</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly>falso</ep:isAudioOnly>
    <ep:telePresence>falso</ep:telePresence>
    <ep:isAlternateHost>falso</ep:isAlternateHost>  <!--Removed-->     <ep:isCreator>vero</ep:isCreator>   <!--Removed-->     <ep:hostKey>954462</ep:hostKey> <!--Removed-->     <ep:supportE2E>falso</ep:supportE2E>    <!--Removed-->     <ep:isAllowJBH>false</ep:isAllowJBH>
    <ep:isCETMeeting>true</ep:isCETMeeting>
    <ep:isPersonalMeetingRoom>true</ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
    <ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed</ep:meetingLink>
    <ep:sipURL>simon0@sqdemo6.dmz.webex.com</ep:sipURL>
    <ep:displayMeetingUrl>simon0@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
    <ep:isAutoRecord>falso</ep:isAutoRecord>
</serv:bodyContent>

Aggiornamenti 39.2.0 API XML

Nuovo elemento lastLoginTime restituito in risposta LstSummaryUser

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:

  • LstSummaryUser

    • 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>Ha cantato</use:firstName>
                <use:lastName>Gmail</use:lastName>
                <use:email>sangeetha.swaminathan@gmail.com</use:email>
                <use:userRoleType>ORGANIZZA</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 39.1.0 API XML

Fare clic qui per scaricare lo schema 39.1.0 API XML.

Nuovo elemento apiVer aggiunto a GetAPIVersion API

Un nuovo elemento di risposta, apiVer, è stato aggiunto all' API GetAPIVersion. Con questo aggiornamento, la convenzione di denominazione della versione API XML cambia in base a un numero di versione unificata con altre aree di prodotto Cisco Webex. apiVer restituisce le nuove informazioni sulla versione, come 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>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="ep:getAPIVersionResponse">
            <ep:apiVersion>API XML Webex V 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 ora sono 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:

  • CreateMeeting

  • Riunione

  • CreateTrainingSession

  • SetTrainingSession

Le API Getmeetinging e GetTrainingSession ancora restituiscono le due opzioni (decise per livello di sito e livello utente) per evitare di interrompere il codice esistente.

Nuovo elemento uploadLogFileUrl aggiunto ai metadati del sito restituiti all'app desktop

Un nuovo elemento uploadLogFileUrl è stato aggiunto 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 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>SUCCESSO</serv:result>
            <serv:gsbStatus>PRINCIPALE</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>AGGIUNTIVI</ns1:meetingTypeName>
                        <ns1:hideInScheduler>falso</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>11</ns1:meetingTypeID>
                        <ns1:meetingTypeName>TRS</ns1:meetingTypeName>
                        <ns1:hideInScheduler>falso</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>13</ns1:meetingTypeID>
                        <ns1:meetingTypeName>SC3</ns1:meetingTypeName>
                        <ns1:hideInScheduler>falso</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>16</ns1:meetingTypeID>
                        <ns1:meetingTypeName>AUO</ns1:meetingTypeName>
                        <ns1:hideInScheduler>falso</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:meetingTypes>
                        <ns1:meetingTypeID>214</ns1:meetingTypeID>
                        <ns1:meetingTypeName>PRO</ns1:meetingTypeName>
                        <ns1:hideInScheduler>falso</ns1:hideInScheduler>
                    </ns1:meetingTypes>
                    <ns1:siteName>sqdemo28</ns1:siteName>
                    <ns1:brandName>sqdemo28</ns1:brandName>
                    <ns1:brandName>sqdemo28-de</ns1:brandName>
                    <ns1:brandName>sqdemo28-it</ns1:brandName>
                    <ns1:brandName>sqdemo28-fr</ns1:brandName>
                    <ns1:region>Francia</ns1:region>
                    <ns1:currency>Franchi francesi</ns1:currency>
                    <ns1:timeZoneID>4</ns1:timeZoneID>
                    <ns1:timeZone>GMT-08:00, Pacifico (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>Francese</ns1:pageLanguage>
                    <ns1:activateStatus>true</ns1:activateStatus>
                    <ns1:webPageType>J2EE</ns1:webPageType>
                    <ns1:iCalendar>true</ns1:iCalendar>
                    <ns1:myWebExDefaultPage>Riunioni personali</ns1:myWebExDefaultPage>
                    <ns1:componentVersion>cmp3300</ns1:componentVersion>
                    <ns1:accountNumLimit>999999</ns1:accountNumLimit>
                    <ns1:activeUserCount>40</ns1:activeUserCount>
                    <ns1:displayMeetingActualTime>falso</ns1:displayMeetingActualTime>
                    <ns1:displayOffset>true</ns1:displayOffset>
                    <ns1:supportWebEx11>falso</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>falso</ns1:hpUnix>
                    <ns1:java>true</ns1:java>
                    <ns1:palm>falso</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>falso</ns1:backwardAPI>
                    <ns1:xmlAPI>true</ns1:xmlAPI>
                    <ns1:cAPI>falso</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>falso</ns1:folders>
                    <ns1:eventDocument>true</ns1:eventDocument>
                    <ns1:myReport>falso</ns1:myReport>
                    <ns1:myComputer>falso</ns1:myComputer>
                    <ns1:personalMeetingPage>falso</ns1:personalMeetingPage>
                    <ns1:myFilesStorage>1000</ns1:myFilesStorage>
                    <ns1:myComputerNumbers>0</ns1:myComputerNumbers>
                    <ns1:enableMyWebExPro>true</ns1:enableMyWebExPro>
                    <ns1:myWebExProMaxHosts>999999</ns1:myWebExProMaxHosts>
                    <ns1:restrictAccessAnyApps>falso</ns1:restrictAccessAnyApps>
                    <ns1:restrictAccessAnyAppsNum>0</ns1:restrictAccessAnyAppsNum>
                    <ns1:addlAccessAnyComputersLimit>CRITERI rigidi</ns1:addlAccessAnyComputersLimit>
                    <ns1:addlAccessAnyComputers>0</ns1:addlAccessAnyComputers>
                    <ns1:addlStorageLimit>CRITERI rigidi</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>falso</ns1:foldersPro>
                    <ns1:eventDocumentPro>true</ns1:eventDocumentPro>
                    <ns1:myReportPro>true</ns1:myReportPro>
                    <ns1:myComputerPro>falso</ns1:myComputerPro>
                    <ns1:personalMeetingPagePro>true</ns1:personalMeetingPagePro>
                    <ns1:myFilesStoragePro>1000</ns1:myFilesStoragePro>
                    <ns1:myComputerNumbersPro>0</ns1:myComputerNumbersPro>
                    <ns1:PMRheaderBranding>falso</ns1:PMRheaderBranding>
                </ns1:myWebExConfig>
                <ns1:telephonyConfig>
                    <ns1:isTSPUsingTelephonyAPI>falso</ns1:isTSPUsingTelephonyAPI>
                    <ns1:serviceName>Conferenza personale No.</ns1:serviceName>                     <ns1:participantAccessCodeLabel>Codice di accesso partecipante</ns1:participantAccessCodeLabel>
                    <ns1:subscriberAccessCodeLabel>Codice di accesso organizzatore</ns1:subscriberAccessCodeLabel>
                    <ns1:attendeeIDLabel>ID partecipante</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>passare</ns1:subscribePassword>
                    <ns1:defaultPhoneLines>10</ns1:defaultPhoneLines>
                    <ns1:defaultSpeakingLines>10</ns1:defaultSpeakingLines>
                    <ns1:majorCountryCode>1</ns1:majorCountryCode>
                    <ns1:majorAreaCode>408</ns1:majorAreaCode>
                    <ns1:publicName>Utente chiamata in ingresso</ns1:publicName>
                    <ns1:hybridTeleconference>true</ns1:hybridTeleconference>
                    <ns1:instantHelp>falso</ns1:instantHelp>
                    <ns1:customerManage>falso</ns1:customerManage>
                    <ns1:maxCallersNumber>500</ns1:maxCallersNumber>
                    <ns1:isSpecified>falso</ns1:isSpecified>
                    <ns1:isContinue>falso</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>falso</serv:tollFree>
                                <serv:default>falso</serv:default>
                            </serv:globalNum>
                            <serv:enableServer>true</serv:enableServer>
                            <serv:tollLabel>14085452910</serv:tollLabel>
                            <serv:tollFreeLabel>Numero chiamata in ingresso gratuita (USA/Canada)</serv:tollFreeLabel>                         </ns1:primaryLargeServer>                         <ns1:backup1LargeServer>                             <serv:enableServer>falso</serv:enableServer>
                            <serv:tollLabel>Numero di chiamata in ingresso a pagamento (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>numero gratuito di chiamata (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup1LargeServer>                         <ns1:backup2LargeServer>                             <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Backup numero di chiamata in ingresso a pagamento (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>numero di chiamata in ingresso gratuito di backup (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup2LargeServer>                         <ns1:primarySmallServer>                             <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Numero di chiamata in ingresso a pagamento (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>numero gratuito di chiamata (USA/Canada)</serv:tollFreeLabel>                         </ns1:primarySmallServer>                         <ns1:backup1SmallServer>                             <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Numero di chiamata in ingresso a pagamento (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>numero gratuito di chiamata (USA/Canada)</serv:tollFreeLabel>                         </ns1:backup1SmallServer>                         <ns1:backup2SmallServer>                             <serv:enableServer>false</serv:enableServer>
                            <serv:tollLabel>Backup numero di chiamata in ingresso a pagamento (USA/Canada)</serv:tollLabel>                             <serv:tollFreeLabel>numero di chiamata in ingresso gratuito di backup (USA/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>falso</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Numero chiamata in ingresso</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Numero chiamata in ingresso gratuito</ns1:label>
                            </ns1:mpAudio>
                        </ns1:primaryLarge>
                        <ns1:backup1Large>
                            <ns1:enableAdaptor>falso</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Numero chiamata in ingresso</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Numero chiamata in ingresso gratuito</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup1Large>
                        <ns1:backup2Large>
                            <ns1:enableAdaptor>falso</ns1:enableAdaptor>
                            <ns1:serverIP></ns1:serverIP>
                            <ns1:mpAudio>
                                <ns1:label>Numero chiamata in ingresso</ns1:label>
                            </ns1:mpAudio>
                            <ns1:mpAudio>
                                <ns1:label>Numero chiamata in ingresso gratuito</ns1:label>
                            </ns1:mpAudio>
                        </ns1:backup2Large>
                    </ns1:tspAdaptorSettings>
                    <ns1:meetingPlace>
                        <ns1:persistentTSP>falso</ns1:persistentTSP>
                        <ns1:mpAudioConferencing>WithoutIntegration</ns1:mpAudioConferencing>
                    </ns1:meetingPlace>
                    <ns1:supportOtherTypeTeleconf>falso</ns1:supportOtherTypeTeleconf>
                    <ns1:otherTeleServiceName>Altro servizio di teleconferenza</ns1:otherTeleServiceName>
                    <ns1:supportAdapterlessTSP>falso</ns1:supportAdapterlessTSP>
                    <ns1:displayAttendeeID>falso</ns1:displayAttendeeID>
                    <ns1:provisionTeleAccount>true</ns1:provisionTeleAccount>
                    <ns1:choosePCN>falso</ns1:choosePCN>
                    <ns1:audioOnly>true</ns1:audioOnly>
                    <ns1:configTollAndTollFreeNum>falso</ns1:configTollAndTollFreeNum>
                    <ns1:configPrimaryTS>falso</ns1:configPrimaryTS>
                    <ns1:teleCLIAuthEnabled>falso</ns1:teleCLIAuthEnabled>
                    <ns1:teleCLIPINEnabled>falso</ns1:teleCLIPINEnabled>
                </ns1:telephonyConfig>
                <ns1:commerceAndReporting>
                    <ns1:trackingCode>falso</ns1:trackingCode>
                    <ns1:siteAdminReport>true</ns1:siteAdminReport>
                    <ns1:subScriptionService>falso</ns1:subScriptionService>
                    <ns1:isECommmerce>falso</ns1:isECommmerce>
                    <ns1:customereCommerce>falso</ns1:customereCommerce>
                    <ns1:isLocalTax>falso</ns1:isLocalTax>
                    <ns1:localTaxName>IVA</ns1:localTaxName>
                    <ns1:localTaxtRate>0,0</ns1:localTaxtRate>
                    <ns1:holReport>1</ns1:holReport>
                </ns1:commerceAndReporting>
                <ns1:tools>
                    <ns1:businessDirectory>falso</ns1:businessDirectory>
                    <ns1:officeCalendar>falso</ns1:officeCalendar>
                    <ns1:meetingCalendar>true</ns1:meetingCalendar>
                    <ns1:displayOnCallAssistLink>falso</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>falso</ns1:emails>
                    <ns1:outlookIntegration>true</ns1:outlookIntegration>
                    <ns1:wirelessAccess>falso</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>falso</ns1:userLockDown>
                    <ns1:meetingAssist>falso</ns1:meetingAssist>
                    <ns1:sms>falso</ns1:sms>
                    <ns1:encryption>NESSUNO</ns1:encryption>
                    <ns1:internalMeeting>falso</ns1:internalMeeting>
                    <ns1:enableTP>falso</ns1:enableTP>
                    <ns1:enableTPplus>falso</ns1:enableTPplus>
                    <ns1:uploadLogFileUrl>https://sqwd.webex.com/logadmin/spr.do?SiteUrl=sqdemo28&LanguageId=1</ns1:uploadLogFileUrl>
                </ns1:tools>
                <ns1:custCommunications>
                    <ns1:displayType>
                        <ns1:prodSvcAnnounce>falso</ns1:prodSvcAnnounce>
                        <ns1:trainingInfo>falso</ns1:trainingInfo>
                        <ns1:eNewsletters>falso</ns1:eNewsletters>
                        <ns1:promotionsOffers>falso</ns1:promotionsOffers>
                        <ns1:pressReleases>falso</ns1:pressReleases>
                    </ns1:displayType>
                    <ns1:displayMethod>
                        <ns1:email>falso</ns1:email>
                        <ns1:fax>falso</ns1:fax>
                        <ns1:phone>falso</ns1:phone>
                        <ns1:mail>falso</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>falso</ns1:marketingAddOn>
                        <ns1:optimizeAttendeeBandwidthUsage>falso</ns1:optimizeAttendeeBandwidthUsage>
                    </ns1:eventCenter>
                    <ns1:salesCenter>
                        <ns1:enabled>falso</ns1:enabled>
                    </ns1:salesCenter>
                </ns1:supportedServices>
                <ns1:securityOptions>
                    <ns1:passwordExpires>falso</ns1:passwordExpires>
                    <ns1:passwordLifetime>0</ns1:passwordLifetime>
                    <ns1:ECMeetingsUnlisted>falso</ns1:ECMeetingsUnlisted>
                    <ns1:TCMeetingsUnlisted>falso</ns1:TCMeetingsUnlisted>
                    <ns1:allMeetingsUnlisted>true</ns1:allMeetingsUnlisted>
                    <ns1:allMeetingsPassword>true</ns1:allMeetingsPassword>
                    <ns1:joinBeforeHost>falso</ns1:joinBeforeHost>
                    <ns1:audioBeforeHost>falso</ns1:audioBeforeHost>
                    <ns1:audioBeforeHostEC>falso</ns1:audioBeforeHostEC>
                    <ns1:audioBeforeHostTC>falso</ns1:audioBeforeHostTC>
                    <ns1:changePersonalURL>true</ns1:changePersonalURL>
                    <ns1:changeUserName>falso</ns1:changeUserName>
                    <ns1:meetings>
                        <ns1:strictPasswords>true</ns1:strictPasswords>
                    </ns1:meetings>
                    <ns1:strictUserPassword>true</ns1:strictUserPassword>
                    <ns1:accountNotify>falso</ns1:accountNotify>
                    <ns1:requireLoginBeforeSiteAccess>falso</ns1:requireLoginBeforeSiteAccess>
                    <ns1:changePWDWhenAutoLogin>falso</ns1:changePWDWhenAutoLogin>
                    <ns1:enforceBaseline>true</ns1:enforceBaseline>
                    <ns1:passwordChangeIntervalOpt>falso</ns1:passwordChangeIntervalOpt>
                    <ns1:passwordChangeInterval>24</ns1:passwordChangeInterval>
                    <ns1:firstAttendeeAsPresenter>falso</ns1:firstAttendeeAsPresenter>
                    <ns1:isEnableUUIDLink>true</ns1:isEnableUUIDLink>
                    <ns1:isEnableUUIDLinkForSAC>true</ns1:isEnableUUIDLinkForSAC>
                    <ns1:enforceRecordingPwdForMC>true</ns1:enforceRecordingPwdForMC>
                    <ns1:enforceRecordingPwdForEC>falso</ns1:enforceRecordingPwdForEC>
                    <ns1:enforceRecordingPwdForTC>falso</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>RICHIAMATA</ns1:telephonySupport>
                        <ns1:tollFree>true</ns1:tollFree>
                        <ns1:intlLocalCallIn>true</ns1:intlLocalCallIn>
                    </ns1:teleconference>
                    <ns1:joinTeleconfNotPress1>falso</ns1:joinTeleconfNotPress1>
                    <ns1:updateTSPAccount>falso</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>Benvenuto</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>Amministrazione sito</ns1:serviceName>
                    </ns1:button>
                    <ns1:button>
                        <ns1:order>7</ns1:order>
                        <ns1:enabled>falso</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>Nuovo</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:partnerLinks>
                        <ns1:partnerLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:partnerLink>
                        <ns1:partnerLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:partnerLink>
                    </ns1:partnerLinks>
                    <ns1:partnerIntegration>true</ns1:partnerIntegration>
                    <ns1:support>
                        <ns1:target>Nuovo</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:target>Nuovo</ns1:target>
                    </ns1:training>
                </ns1:navMyWebEx>
                <ns1:navAllServices>
                    <ns1:customLinks>
                        <ns1:customLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:customLink>
                        <ns1:customLink>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:customLink>
                    </ns1:customLinks>
                    <ns1:support>
                        <ns1:name>Supporto</ns1:name>
                        <ns1:target>Nuovo</ns1:target>
                    </ns1:support>
                    <ns1:training>
                        <ns1:name>Formazione</ns1:name>
                        <ns1:target>Nuovo</ns1:target>
                    </ns1:training>
                    <ns1:supportMenu>
                        <ns1:userGuides>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:userGuides>
                        <ns1:downloads>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:downloads>
                        <ns1:training>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:training>
                        <ns1:contactUs>
                            <ns1:target>Nuovo</ns1:target>
                        </ns1:contactUs>
                        <ns1:supportMyResources>true</ns1:supportMyResources>
                    </ns1:supportMenu>
                </ns1:navAllServices>
                <ns1:passwordCriteria>
                    <ns1:mixedCase>falso</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>passare</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>falso</ns1:disallowWebTextSessions>
                    <ns1:disallowList>falso</ns1:disallowList>
                    <ns1:disallowValue>password</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>passare</ns1:disallowValue>
                </ns1:recordingPasswordCriteria>
                <ns1:accountPasswordCriteria>
                    <ns1:mixedCase>falso</ns1:mixedCase>
                    <ns1:minLength>0</ns1:minLength>
                    <ns1:minNumeric>0</ns1:minNumeric>
                    <ns1:minAlpha>0</ns1:minAlpha>
                    <ns1:minSpecial>0</ns1:minSpecial>
                    <ns1:disallow3XRepeatedChar>falso</ns1:disallow3XRepeatedChar>
                    <ns1:disallowWebTextAccounts>true</ns1:disallowWebTextAccounts>
                    <ns1:disallowList>true</ns1:disallowList>
                    <ns1:disallowValue>password</ns1:disallowValue>
                    <ns1:disallowValue>passwd</ns1:disallowValue>
                    <ns1:disallowValue>passare</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>falso</ns1:firefox>
                        <ns1:explorerRightClick>falso</ns1:explorerRightClick>
                        <ns1:instantMessenger>true</ns1:instantMessenger>
                        <ns1:aolMessenger>falso</ns1:aolMessenger>
                        <ns1:googleTalk>falso</ns1:googleTalk>
                        <ns1:lotusSametime>true</ns1:lotusSametime>
                        <ns1:skype>true</ns1:skype>
                        <ns1:windowsMessenger>true</ns1:windowsMessenger>
                        <ns1:yahooMessenger>falso</ns1:yahooMessenger>
                        <ns1:ciscoIPPhone>falso</ns1:ciscoIPPhone>
                        <ns1:pcNow>falso</ns1:pcNow>
                        <ns1:iGoogle>falso</ns1:iGoogle>
                        <ns1:iPhoneDusting>true</ns1:iPhoneDusting>
                    </ns1:integrations>
                    <ns1:oneClick>
                        <ns1:allowJoinUnlistMeeting>true</ns1:allowJoinUnlistMeeting>
                        <ns1:requireApproveJoin>falso</ns1:requireApproveJoin>
                    </ns1:oneClick>
                    <ns1:templates>
                        <ns1:useTemplate>falso</ns1:useTemplate>
                    </ns1:templates>
                    <ns1:lockDownPT>
                        <ns1:lockDown>falso</ns1:lockDown>
                    </ns1:lockDownPT>
                    <ns1:imSettings>
                        <ns1:attendeeInviteOther>true</ns1:attendeeInviteOther>
                    </ns1:imSettings>
                </ns1:productivityTools>
                <ns1:meetingPlace/>
                <ns1:salesCenter>
                    <ns1:allowJoinWithoutLogin>falso</ns1:allowJoinWithoutLogin>
                </ns1:salesCenter>
                <ns1:connectIntegration>
                    <ns1:integratedWebEx11>falso</ns1:integratedWebEx11>
                </ns1:connectIntegration>
                <ns1:video>
                    <ns1:HQvideo>true</ns1:HQvideo>
                    <ns1:maxBandwidth>MEDIO</ns1:maxBandwidth>
                    <ns1:HDvideo>true</ns1:HDvideo>
                </ns1:video>
                <ns1:siteCommonOptions>
                    <ns1:SupportCustomDialRestriction>falso</ns1:SupportCustomDialRestriction>
                    <ns1:SupportTelePresence>falso</ns1:SupportTelePresence>
                    <ns1:SupportTelePresencePlus>falso</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>falso</ns1:enableSSO>
                    <ns1:autoAccountCreation>falso</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>

Aggiornamenti SP22 API XML 11.0.0

Limitazione dimensione 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 caricare file più grandi di questo ora riceveranno un messaggio di errore: "010100 dimensione dell'immagine caricata è troppo grande. Provare un'immagine di dimensioni inferiori a 5 MB."

Aggiornamenti SP21 API XML 11.0.0

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

Registrazione automatica nuovo elemento aggiunta a CreateMeeting, riunione, riunione e LstMeeting

Un nuovo elemento, denominato autorecord, è stato aggiunto alleAPI CreateMeeting, riunione, getmeetinge LstMeeting . autorecord consente agli utenti di registrare automaticamente le riunioni Webex 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 può essere eseguito solo a livello globale sul sito.


L' elemento autorecord si applica solo alle riunioni Webex. Non si applica agli eventi Webex o alla formazione Webex.

API interessate:

  • CreateMeeting

    • Registrazione automatica

  • Riunione

    • Registrazione automatica

  • Getmeeting

    • Registrazione automatica

  • LstMeeting

    • Registrazione automatica

Aggiornamenti CreateMeeting:

Impostazione registrazione automatica

Comportamento quando tutte le sessioni vengono registrate automaticamente 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 l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è abilitata, l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Aggiornamenti di riunione :

Impostazione registrazione automatica

Comportamento quando tutte le sessioni vengono registrate automaticamente 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 l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è abilitata, l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Aggiorna aggiornamenti:

Impostazione registrazione automatica

Comportamento quando tutte le sessioni vengono registrate automaticamente 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 l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è abilitata, l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Esempio di risposta getmeeting :

Aggiornamenti LstMeeting:

Impostazione registrazione automatica

Comportamento quando tutte le sessioni vengono registrate automaticamente 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 l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è abilitata, l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Esempio di risposta LstMeeting:

Nuovo elemento isAutoRecord aggiunto a GetSessionInfo API

Insieme alle modifiche apportate alle API di cui sopra, un nuovo elemento, isAutoRecord, è stato aggiunto 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

Comportamento quando tutte le sessioni vengono registrate automaticamente 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 l'opzione Registra automaticamente tutte le sessioni utilizzando la registrazione basata su rete è abilitata, l'elemento viene ignorato e la registrazione viene avviata automaticamente all'inizio della riunione.

Esempio di risposta GetSessionInfo:

Aggiornamenti SP20 API XML 11.0.0

Fare clic qui per scaricare lo schema XML API 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 valore booleano nella richiesta di LstRecording.

Questo nuovo elemento è stato aggiunto per supportare la ricerca delle registrazioni del partecipante o dell'invitato. returnShareToMeRecording è un flag per consentire all' API LstRecording di sapere che deve restituire il partecipante o le registrazioni degli 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 manuale sono entrambi disattivi, LstRecording restituisce l'utente solo come proprietario delle registrazioni.

Se returnShareToMeRecording è impostato su falseo questo elemento non è incluso nella richiesta, LstRecording segue la stessa logica di prima: Restituisce l'utente delle registrazioni come proprietario.

API interessate:

  • LstRecording

    • returnShareToMeRecording

Aggiornamenti LstRecording:

Elemento shareToMe aggiunto a risposta 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 valore booleano nella risposta per LstRecording.

Questo nuovo elemento è stato aggiunto per supportare la ricerca delle registrazioni del partecipante o dell'invitato. shareToMe è un flag per definire se l'utente è il proprietario o un partecipante per la registrazione corrente.

Quando shareToMe è vero, 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, LstRecording segue la stessa logica di prima: l'utente è il proprietario della registrazione corrente.

API interessate:

  • LstRecording

    • shareToMe

Aggiornamenti LstRecording:

esempi di richieste 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>MeetingCenter</serviceType>
<serviceType>EventCenter</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 :

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

  • sipURL: URL utilizzato per partecipare alla riunione video Webex da una sistema di videoconferenza o un'applicazione

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

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

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

API interessate:

  • GetEvent

    • isCETMeeting

    • sipURL

    • standaloneDialingIPAddress

    • panelistNumericPassword

Nuovo elemento panelistNumericPassword aggiunto a GetSessionInfo API

GetSessionInfo dispone di un nuovo elemento, panelistNumericPassword, contenente la password per partecipare alla riunione video Webex da una sistema di videoconferenza o un'applicazione.

Se il sito supporta il video Webex, l'organizzatore dispone dei privilegi video Webex Events e l'evento supporta la piattaforma video Webex 2 (CMR 4,0), GetSessionInfo restituisce i quattro elementi seguenti:

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

  • sipURL: URL utilizzato per partecipare alla riunione video Webex da una sistema di videoconferenza o un'applicazione

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

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


Per le riunioni Webex, questi elementi già esistevano in GetSessionInfo:

  • isCETMeeting

  • sipURL

  • standaloneDialingIPAddress

API interessate:

  • GetSessionInfo

    • panelistNumericPassword

Modifiche dello schema apportate a GetEvent e GetSessionInfo

Aggiornamenti GetEvent :

Aggiornamenti GetSessionInfo:

Aggiornamenti SP18 API XML 11.0.0

Fare clic qui per scaricare lo schema XML API 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 il video Webex (CMR). Ora viene anche restituito un nuovo elemento EnableCloudTelepresence nell' API GetSite .

API interessate:

  • getSite

  • EnableCloudTelepresence

Risposta di esempio GetSite:

Aggiornamenti SP17 API XML 11.0.0

Nuovo elemento returnShareToMeRecording aggiunto alla richiesta API LstRecording

Un nuovo elemento, returnShareToMeRecording, è stato aggiunto all' API LstRecording. returnShareToMeRecording è un valore booleano nella richiesta di LstRecording.

Questo nuovo elemento è stato aggiunto al supporto per il pull delle registrazioni del partecipante o dell'invitato. returnShareToMeRecording è un flag per consentire all' API LstRecording di sapere che deve restituire il partecipante o le registrazioni degli 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 manuale sono disabilitati, LstRecording restituisce solo l'utente come proprietario delle registrazioni.

Se returnShareToMeRecording è impostato su falseo questo elemento non è incluso nella richiesta, LstRecording segue la stessa logica di prima: Restituisce l'utente delle registrazioni come proprietario.

API interessate:

  • LstRecording

  • returnShareToMeRecording

Aggiornamenti LstRecording:

Nuovo elemento shareToMe aggiunto a risposta API LstRecording

Un nuovo elemento, shareToMe, è stato aggiunto all' API LstRecording. shareToMe è un valore booleano nella risposta per LstRecording.

Questo nuovo elemento è stato aggiunto al supporto per il pull delle registrazioni del partecipante o dell'invitato. shareToMe è un flag per definire se l'utente è il proprietario o il partecipante o l'invitato per la registrazione corrente.

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

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

API interessate:

  • LstRecording

  • shareToMe

Aggiornamenti LstRecording:

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

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

attendeeCapacityForMC -Webex Meetings

attendeeCapacityForEC – Webex Events

attendeeCapacityForTC – Webex Training

attendeeCapacityForSC – supporto Webex

Questi valori restituiti indicano il numero massimo di invitati che la riunione, l'evento o la sessione possono avere. Sono figli dell' elemento CISiteLicenseInfo nella risposta.

API interessate:

  • getSite

  • attendeeCapacityForMC

  • attendeeCapacityForEC

  • attendeeCapacityForTC

  • attendeeCapacityForSC

esempio 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>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="ns1:getSiteResponse">
            <ns1:siteInstance>
...
...
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
                    <ns1:allowOverageForMC>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>falso</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>falso</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>falso</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>

Aggiornamenti SP16 API XML 11.0.0

Nuova API hostStreamURL aggiunta a lstRecordingResponse

L'elemento hostStreamURL è stato aggiunto alla risposta LstRecording come parte dei dettagli della registrazione. hostStreamURL restituisce un URL per l'ospite da utilizzare per visualizzare la registrazione senza dover eseguire prima 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"/>

L'API GetSite utilizza la nuova modellazione WEBDB per restituire i dati

In base alla richiesta del cliente, l'API GetSite ora recupera una licenza organizzatore più accurata, l'uso dei dati di Reporting e altri dati utilizzando la nuova modellazione WEBDB per i siti ci.

API interessate:

  • GetSite

Esempio 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>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="ns1:getSiteResponse">
            <ns1:siteInstance>
...
...
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
                    <ns1:allowOverageForMC>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>falso</ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC>falso</ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>falso</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>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="ns1:getSiteResponse">
            <ns1:siteInstance>
...
...
                <ns1:CISiteLicenseInfo>
                    <ns1:accountNumberLimitForCMRHost>80</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost>true</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>

Aggiornamenti SP15 API XML 11.0.0

Restituisce il collegamento alla riunione Webex Meetings utilizzando l'API GetSessionsInfo

Lo schema per l' API GetSessionInfo ha un nuovo valore di ritorno, meetingLink. È possibile utilizzare un collegamento alla riunione per avviare una riunione Webex come organizzatore o per partecipare a una riunione Webex come partecipante.

API interessate:

  • GetSessionInfo

  • meetingLink

Esempio di risposta GetSessionInfo:

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

Nuova condizione per l'esecuzione di query da RecordingID su LstRecording API

Ora è possibile utilizzare LstRecording per eseguire query sulle registrazioni utilizzando recordingID. Sono disponibili due tipi di ID registrazione:

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

  • ID registrazione NBR per registrazioni varie

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

Se nella richiesta XML non è presente alcun elemento serviceType, LstRecording restituisce solo una registrazione NBR.

API interessate:

  • LstRecording

  • RecordingID

Esempi di risposta LstRecording:

Esempio di richiesta per un ID registrazione servizio:

<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
    <serviceTypes>
        <serviceType>MeetingCenter</serviceType>
        <serviceType>EventCenter</serviceType>
        <serviceType>TrainingCenter</serviceType>
    </serviceTypes>
    <recordingID>974164492</recordingID>
    <order>
         <orderBy>CREATETIME</orderBy>
         <orderAD>DESC</orderAD>
         <orderBy>HOSTID</orderBy>
         <orderAD>ASS</orderAD>
         <orderBy>RECORDNAME</orderBy>
         <orderAD>ASS</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>ASS</orderAD>
         <orderBy>RECORDNAME</orderBy>
         <orderAD>ASS</orderAD>
    </order>
</bodyContent>

Aggiornamenti SP14 API XML 11.0.0

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 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>ASS</orderAD>
                <orderBy>CONFNAME</orderBy>
                <orderAD>ASS</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASS</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

Esempio di risposta 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 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>ASS</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASS</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>STATI UNITI D'AMERICA</history:country>
                <history:zipCode>95111</history:zipCode>
                <history:name>test2 utente</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>Organizzatore di test</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>

Ritorno URL SIP e URL Skype dall' 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 partecipare alle riunioni da una TelePresence o da un altro dispositivo video Cisco. In questo modo, solo le riunioni che utilizzano la piattaforma video Cisco versioni 1,0 o 2,0 devono GetSessionInfo restituire l' <sipURL> elemento.

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

API interessate:

  • GetSessionInfo

Esempio di risposta:

Ritorno dell'URL SIP e del collegamento alla riunione dall' API Getmeeting

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

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

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

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

API interessate:

  • Getmeeting

Esempio di risposta getmeeting :

Aggiornamenti SP13 API XML 11.0.0

Annuncio di deprecazione dell' <siteID> elemento in Parent <securityContext>

Cisco prevede di deprecare l' <siteID> elemento nell'elemento padre <securityContext> e di sostituirlo con <siteName>. A causa di un numero elevato di <siteID> elementi spesso modificati durante le migrazioni del sito, le organizzazioni incorrono in 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 dei dati degli <tollCallInData><tollFreeCallInData> elementi e

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 devono correggere le stringhe affinché questi elementi passino la convalida dei dati.

Di seguito sono riportati alcuni esempi di CreateUser e seuser, 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>
...

Aggiornamenti SP12 API XML 11.0.0

Due nuove API SetContact e DelContacts

Lo schema API XML aveva in precedenza solo le due API CreateContacts e LstContacts, che non fornivano la gestione completa dei contatti utente. Per fornire una migliore funzionalità per la gestione dei contatti utente mediante l'API XML, sono state aggiunte queste due nuove API, recontact 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 "non una lingua valida"

  • Se il nuovo indirizzo e-mail a cui l'utente desidera passare è un duplicato con un altro contatto nell' elenco contatti personali, viene restituita l'eccezione 140001 "e-mail utilizzata da un altro contatto".

DelContacts

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

contactID viene restituito se il messaggio e-mail specificato può essere trovato 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 contatti personali, viene restituita l'eccezione 00015 (spiacenti, nessun record trovato).

API interessate:

  • SetContact

  • DelContacts

Esempio di richiesta di contatto:

<?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>SiteName</siteName>
      <webExID>UserID</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 indirizzo E-mail di contatto</email>
                <title>Nuovo titolo</title>
                <company>Nuova società</company>
                <notes>Nuove note</notes>
                <url>Nuovo 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à</city>
                    <state>Nuovo stato</state>
                    <zipCode>Nuovo codice postale</zipCode>
                    <country>Nuova società</country>
                </address>
                <language>Nuova lingua</language>
            </contact>
</bodyContent>
</body>
</serv:message>

Esempio di risposta di contatto:

<?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>SUCCESSO</serv:result>
            <serv:gsbStatus>PRINCIPALE</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>SiteName</siteName>
      <webExID>UserID</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 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>SUCCESSO</serv:result>
            <serv:gsbStatus>PRINCIPALE</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 nell' elenco 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>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>

Aggiornamenti SP11 API XML 11.0.0

Nuova API LstTrainingPollResultsHistory

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

I risultati del sondaggio dell'elenco vengono restituiti inserendo un Training Center SessionKey. L'API può essere richiesta sia dal proprietario sessione Training Center che da un amministratore sito.


L' impostazione del sondaggio TC migliorato deve essere abilitata prima che i risultati del sondaggio di formazione vengano memorizzati nel DB Webex:

API interessate:

  • LstTrainingPollResultsHistory

Esempio di richiesta LstTrainingPollResultHistory:

<?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 T32/XML API 11.0.0.

Esempio di risposta LstTrainingPollResultHistory:

<?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>SUCCESSO</serv:result>
            <serv:gsbStatus>PRINCIPALE</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>Test TC sondaggio 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>domanda di test 1 (risposta multipla/singola)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>test risposta 4</history:answerChoice>
                                <history:answerChoice>test risposta 3</history:answerChoice>
                                <history:answerChoice correct="true">test risposta 2</history:answerChoice>
                                <history:answerChoice>test risposta 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 risposta 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 risposta 1</history:pollResponse>
                                    <history:isCorrect>falso</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>Nessuna risposta</history:pollResponse>
                                    <history:isCorrect>falso</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>test domanda 2 (multi-choiec. multi-risposta)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>risposta di prova D</history:answerChoice>
                                <history:answerChoice>test risposta C</history:answerChoice>
                                <history:answerChoice correct="true">test risposta B</history:answerChoice>
                                <history:answerChoice correct="true">test risposta 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 risposta B, test risposta 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 risposta D, test risposta C, test risposta B, test risposta A</history:pollResponse>
                                    <history:isCorrect>falso</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>Nessuna risposta</history:pollResponse>
                                    <history:isCorrect>falso</history:isCorrect>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>test domanda 2 (risposta breve)</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>Nessuna risposta</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                    </history:questions>
                </history:poll>
                <history:poll>
                    <history:pollDesc>Sondaggio</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>domanda di sondaggio 1 (multi-choiec/sinngle-risposta)</history:questionDesc>
                            <history:questionType>1</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>risposta sondaggio 3</history:answerChoice>
                                <history:answerChoice>risposta sondaggio 2</history:answerChoice>
                                <history:answerChoice>risposta sondaggio 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>risposta sondaggio 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>risposta sondaggio 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>Nessuna risposta</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>2</history:questionSequence>
                            <history:questionDesc>domanda di sondaggio 2 (multi-choiec/Multi-answer)</history:questionDesc>
                            <history:questionType>2</history:questionType>
                            <history:answerChoices>
                                <history:answerChoice>risposta sondaggio D</history:answerChoice>
                                <history:answerChoice>risposta sondaggio C</history:answerChoice>
                                <history:answerChoice>risposta sondaggio B</history:answerChoice>
                                <history:answerChoice>sondaggio risposta 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>risposta sondaggio D, risposta sondaggio 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>risposta sondaggio C, risposta sondaggio 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>Nessuna risposta</history:pollResponse>
                                </history:attendee>
                            </history:attendees>
                        </history:question>
                        <history:question>
                            <history:questionSequence>3</history:questionSequence>
                            <history:questionDesc>domanda di sondaggio 3 (risposta breve)</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>Nessuna risposta</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 la richiede o se l'utente che la richiede non è anche un amministratore 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>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>

Nuova opzione AttendeeSendVideo nelle API CreateTrainingSession, SetTrainingSessione GetTrainingSession

Poiché le opzioni disponibili quando si pianifica un sessione Training Center includono Invia video, l'API XML 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 come paramName =' optionSupportSendVideo '

CreateTrainingSession richiesta aggiornamenti:

SetTrainingSession richiesta aggiornamenti:


La richiesta è solo per T32/XML API 11.0.0.

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 viene allineata alla limitazione della pagina iniziale J2EE. Se una richiesta API include confname che è vuota o supera la lunghezza del carattere di visualizzazione 128, viene visualizzato il seguente messaggio di errore:

"060065 nome conferenza di input non valido. Il nome della conferenza non può essere vuoto o supera 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 query supera il limite massimo di LSTRECORDING API è 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 di tempo di query massimo di 28 giorni".

API interessate:

  • LstRecording

Aggiornamenti SP10 API XML 11.0.0

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