Este artigo contém atualizações e alterações para as versões do SP mensal do XML API.

Para obter mais informações sobre o XML API 40 e a API REST 40, consulte a Cisco Webex Meetings visão geral de atualizações API (api 40).

Para atualizações do XML API 11 SP9 e anterior, vá para Cisco devnet.

Atualizações de 39.11.0 API XML

Clique aqui para baixar o esquema XML API 39,11.

LstSummaryUser pode consultar contas de usuário pela última modificação de hora

Estamos atualizando a API LstSummaryUser para que seja possível permitir que os usuários consultem as contas de usuário com base na hora em que foram modificados pela última vez. Três novos elementos, modifiedDateStart, modifiedDateEnde LastModifiedTime foramadicionados à API.


O escopo máximo de tempo para esta consulta é de 90 dias. Se você inserir um intervalo de tempo maior que 90 dias, um erro será exibido: 999999 intervalo de datas máximo é de 90 dias para a consulta de data de modificação.

APIs afetadas:

  • LstSummaryUser

Exemplo de solicitação 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>senha</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>

Exemplo de resposta 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>Primário de sucesso</serv:result>
            <serv:gsbStatus></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 * * * * * * Sr * @qa * * * * * * * * * * * * * * * * * * * * * * * *</use:userID>
                <use:webExId></use:webExId>
                <use:firstName></use:firstName>
                <use:lastName></use:lastName>
                <use:email></use:email>
                <use:userRoleType></use:userRoleType>
                <use:registrationDate></use:registrationDate>
                <use:active></use:active>
                <use:timeZoneID>4</use:timeZoneID>
                <use:meetingTypes>
                    <use:meetingType>3</use:meetingType>
                    <use:meetingType>9</use:meetingType>
                    <use:meetingType>10</use:meetingType>
                    <use:meetingType>11</use:meetingType>
                    <use:meetingType>13</use:meetingType>
                    <use:meetingType>14</use:meetingType>
                    <use:meetingType>102</use:meetingType>
                </use:meetingTypes>
                <use:lastLoginTime></use:lastLoginTime>
                <use:lastModifiedTime>11/11/2019 19:11:11 10/19/2019 23:13:14 06/19/2016 22:13:06.</use:lastModifiedTime>
            </use:user>

Atualizações de 39.10.0 API XML

Clique aqui para baixar o esquema XML API 39,10.

Obterinformaçãodaseção e GetUserCard retornam um código de captcha ao usar acesso anônimo

Como uma atualização de segurança, aprimoramos as APIs obterinformaçãodaseção e GetUserCard com proteção de resposta de código Captcha. Se seus aplicativos chamarem as APIs usando acesso anônimo, Aprimore seu aplicativo para suportar a entrada do código CAPTCHA.

APIs afetadas:

  • Obterinformaçãodaseção

  • GetUserCard

CAPTCHA atualizações de segurança e resposta:

Resposta Obterinformaçãodaseção sem captcha exemplo:

<?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>FALHA na</serv:result>
            <serv:reason>reunião correspondente não encontrada</serv:reason>
            <serv:gsbStatus>principal</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Obterinformaçãodaseção resposta com captcha exemplo:

<?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>Falha na</serv:result>
            <serv:reason>reunião correspondente não encontrada</serv:reason>
            <serv:gsbStatus>SDDHEEfgkerwAAAI do primário * * * * qHS * * *</serv:gsbStatus>
            <serv:exceptionID>060001</serv:exceptionID>
            <serv:CAPTCHAID>* 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 você receber uma resposta CAPTCHA e continuar chamando a API, inclua o CAPTCHAID e o CAPTCHAWord na sua solicitação de 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>

Resposta obterinformaçãodaseção para CAPTCHAID incorreta e CAPTCHAWord exemplo:

<?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>A falha</serv:result>
            <serv:reason>captcha ID e o Word são inválidos ou estão faltando</serv:reason>
            <serv:gsbStatus>SDDHEEfgkerwAAAI primários</serv:gsbStatus>
            <serv:exceptionID>030113</serv:exceptionID>
            <serv:CAPTCHAID>* * * 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>

Suporte LstSummaryUser para retornar URLs da sala pessoal

Adicionamos um novo elemento de resposta, personalMeetingRoomURL, à API LstSummaryUser .

Exemplo de resposta LstSummaryUser:

Atualizações de 39.9.0 API XML

Clique aqui para baixar o esquema XML API 39,9.

Suporte para URLs SIP curtas para salas de reuniões pessoais (PMR)

O suporte para o formato de URL SIP curto para PMRs impacta as APIs obterinformaçãodaseção, getmeetings, GetUsere GetMe . Um novo elemento de resposta chamado displayMeetingUrl foi adicionado às APIs GetUser e GetMe e já está presente em obterinformaçãodaseção e getmeeting. displayMeetingUrl retorna a URL do PMR de um usuário.

APIs afetadas:

  • Obterinformaçãodaseção

  • Getmeeting

  • Getuser

  • GetMe

Exemplo de resposta GetUser:

Exemplo de resposta GetMe:

Obterinformaçãodaseção retorna elementos necessários para acesso anônimo

Como requisito de segurança, apenas os elementos necessários agora podem ser retornados por obterinformaçãodaseção para acesso anônimo.

Exemplo de resposta obterinformaçãodaseção:

<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>Public</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, Pacífico (São Francisco)</ep:timeZone>
        <ep:timeZoneID>4</ep:timeZoneID>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount>falso</ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAllowJBH>verdadeiro</ep:isAllowJBH>
    <ep:isCETMeeting>verdadeiro</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>

APIs afetadas:

  • Obterinformaçãodaseção

Agendar alteração de comportamento de reuniões e eventos

Por padrão, todas as reuniões agendadas são reuniões habilitadas para dispositivos de vídeo. No entanto, quando você agenda uma reunião, mas seleciona nenhuma ou outras pessoas para o áudio da sua reunião, a reunião será agendada como uma reunião Webex habilitada para dispositivos sem vídeo.

APIs afetadas:

  • Criação reunião

  • Setmeeting

  • Createevent

  • Setevent

Atualizações de 39.8.0 API XML

Clique aqui para baixar o esquema XML API 39,8.

LsttrainingattendeeHistory agora retorna o convidado da reunião a atenção é

Um novo elemento de resposta, attentionToDurationPercentage, foi adicionado ao API LsttrainingattendeeHistory. LsttrainingattendeeHistory retorna os detalhes da a atenção é de um convidado de reunião. O elemento é retornado neste formato:

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

APIs afetadas:

  • LsttrainingattendeeHistory

    • attentionToDurationPercentage

    • attentionToAttendancePercentage

Exemplo de resposta 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 agora retorna contagens de licenças

Novos elementos de resposta foram fornecidos para retornar contagens de licença diferentes na API GetSite .

APIs afetadas:

  • GetSite

    • EEActiveUserCount

    • activeCETHost

    • MCActiveUserCount

    • ECActiveUserCount

    • TCActiveUserCount

    • SCActiveUserCount

Redesignação de GetSiteFT e SetSiteFT

As APIs GetSiteFT e SetSiteFT foram reprojetadas para permitir alternâncias de recursos dinâmicos.

APIs afetadas:

  • GetSiteFT

  • SetSiteFT

Exemplo de solicitação GetSite:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <siteName>{siteName}</siteName>
            <accessToken>{Este é o token de acesso da conta de computador}</accessToken>
        </securityContext>
    </header>
    <bodyContent xsi:type="java:com.webex.service.binding.site.GetSiteFT">
        <featureToggles>
            <name>SupportCrossLaunch</name>
            <name>RemoveCMRLicenseSA</name>
        </featureToggles>
    </bodyContent>
</body>
</serv:message>

Exemplo de resposta 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>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>

Exemplo de solicitação SetSite:

<?xml version="1.0" encoding="UTF-8"?>
<serv:message
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:serv="http://www.webex.com/schemas/2002/06/service"
   xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
   http://www.webex.com/schemas/2002/06/service/service.xsd">
    <header>
        <securityContext>
            <siteName>{siteName}</siteName>
            <accessToken>{Este é o token de acesso da conta de computador}</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>verdadeiro</value>
                </featureToggle>
            </featureToggles>
        </bodyContent>
    </body>
</serv:message>

Exemplo do SetSiteFT .

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ns1="http://www.webex.com/schemas/2002/06/service/site" xmlns:event="http://www.webex.com/schemas/2002/06/service/event">
    <serv:header>
        <serv:response>
            <serv:result>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>

A duração da descrição da reunião agora está limitada a 2500 caracteres

As seguintes APIs agora têm o comprimento do conteúdo do elemento de descrição da reunião restrito a 2500 caracteres:

APIs afetadas:

  • Createevent

  • Setevent

  • CreateTrainingSession

  • SetTrainingSession

Isso é para evitar que o Cisco Webex seja incapaz de processar a solicitação. Se a descrição da reunião tiver mais de 2500 caracteres, uma mensagem de erro será retornada.

Atualizações de 39.5.0 API XML

Novo elemento videoMeshInterclusters adicionado aos esquemas SetSite e GetSite

Um novo elemento, videoMeshInterclusters, foi adicionado ao elemento SetSite . o videoMeshInterclusters também contém três elementos filhos videoMeshHomeCluster1, videoMeshHomeCluster2e videoMeshHomeCluster3.

APIs afetadas:

  • Setsite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

  • GetSite

    • videoMeshInterclusters

      • videoMeshHomeCluster1

      • videoMeshHomeCluster2

      • videoMeshHomeCluster3

Atualizações de solicitação SetSite:

Atualizações de resposta GetSite:

Atualizações de 39.3.0 API XML

URL SIP curta no API XML, novo elemento displayMeetingUrl

Clique aqui para baixar o esquema XML API 39,3.

Atualmente, ao entrar em uma reunião Webex, o aplicativo ou o dispositivo deve fornecer informações do site, dificultando a participação em reuniões às vezes. Isso é especialmente verdadeiro ao discar de um dispositivo SIP, porque o usuário deve digitar a meeting_number@sitename.webex.com.

Para facilitar a associação de reuniões, retiramos a necessidade de inserir o nome do site no URI do SIP da reunião: meeting_number@webex.com. Para manter a compatibilidade com versões anteriores, o formato antigo funciona no sipURL e o novo formato é anexado ao novo elemento displayMeetingUrl.

APIs afetadas:

  • Getmeeting

    • displayMeetingUrl

  • Getevent

    • displayMeetingUrl

  • Obterinformaçãodaseção

    • displayMeetingUrl

Exemplo de resposta de getmeetings :

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

Exemplo de resposta de GetEvent :

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

Exemplo de resposta obterinformaçãodaseção:

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

Exemplo de e-mail:

O comprimento da descrição agora está limitado a 1024 caracteres

As seguintes APIs agora têm o tamanho do conteúdo do elemento de descrição restrito a 1024 caracteres:

APIs afetadas:

  • CreateTrainingSession

  • SetTrainingSession

  • Createevent

  • Setevent

Essa alteração é para evitar que o Cisco Webex seja incapaz de processar a solicitação. Se a descrição tiver mais de 1024 caracteres, uma mensagem de erro será retornada: "060067 descrição de entrada ilegal. A descrição não pode exceder o comprimento máximo de caracteres de exibição de 1024. "

Exemplo de resposta para a duração da descrição superior a 1024 caracteres:

<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>FALHA na</serv:result>
            <serv:reason> Descrição de entrada ilegal. A descrição não pode exceder o comprimento máximo de caracteres de exibição 1024 </serv:reason>
            <serv:gsbStatus>primários</serv:gsbStatus>
            <serv:exceptionID>060067</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Obterinformaçãodaseção agora retorna apenas informações básicas sobre as salas pessoais quando houver um usuário anônimo usando a API

Para garantir maior segurança, estamos diminuindo a quantidade de informações retornadas por obterinformaçãodaseção quando há um usuário de convidado anônimo usando a API. Nesta atualização, reduziremos os seguintes elementos na resposta da API:

APIs afetadas:

  • Obterinformaçãodaseção

    • <ep:accessControl>

  • <ep:sessionPassword>

    • <ep:telephony>

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

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

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

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

Comparações de resposta:

<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ep:status>NOT_INPROGRESS falso não listado falso falso falso falsa falso</ep:status>
    <ep:isLocked></ep:isLocked>
    <ep:sessionkey>712419789</ep:sessionkey>
    <ep:confID>120396209273701973</ep:confID>
    <ep:accessControl>
        <ep:sessionPassword></ep:sessionPassword>   <!--Removed-->
        <ep:listStatus></ep:listStatus>
        <ep:registration></ep:registration>
        <ep:passwordReq></ep:passwordReq>
        <ep:isEnforceAudioPassword></ep:isEnforceAudioPassword>
        <ep:isEnforceAudioLogin></ep:isEnforceAudioLogin>
    </ep:accessControl>
    <ep:metaData>
        <ep:confName>de sala pessoal</ep:confName>
        <ep:sessionType>3</ep:sessionType>
        <ep:serviceType>MeetingCenter texto de</ep:serviceType>
        <ep:isRecurring>texto falso falso</ep:isRecurring>
        <ep:agendaFormat></ep:agendaFormat>
        <ep:descriptionFormat></ep:descriptionFormat>
        <ep:isException></ep:isException>
        <ep:seriesMeetingKey>0</ep:seriesMeetingKey>
        <ep:hasException>falso</ep:hasException>
    </ep:metaData>
    <ep:telephony>    <!--Removed-->
        <ep:telephonySupport>retorno de chamada</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 * [doassinante] #,,, [convidadoid] # | SilentDialInSequence: [AccessNumber],, * 01 * [Doassinante] # [convidado] # * 01 * | AutoLGDialInSequence: [AccessNumber],, * 00 * [Doassinante] #,,, [ProfileId] #,,, [PIN] # | SilentLGDialInSequence: [AccessNumber],, * 01 * [Doassinante] # [ProfileId] # [PIN] # * 01 * | AutoLGPWDialInSequence: [AccessNumber],, * 00 * [Doassinante] #,,, [ProfileId] #,,, [PIN] #,,, [senha] # | SilentLGPWDialInSequence: [AccessNumber],, * 01 * [doassinante] # [ProfileId] # [PIN] # [senha] # * 01 *</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>falso</serv:tollFree>    <!--Removed-->
                <serv:default>falso de</serv:default>  <!--Removed-->
            </serv:globalNum> <!--Removed-->
        </ep:callInNum>   <!--Removed-->
        <ep:labels>   <!--Removed-->
            <ep:tollFreeCallInLabel>chamada de entrada (EUA/Canadá)</ep:tollFreeCallInLabel>   <!--Removed-->
            <ep:tollCallInLabel>14085452910</ep:tollCallInLabel>    <!--Removed-->
        </ep:labels>  <!--Removed-->
        <ep:isMPAudio>falso</ep:isMPAudio>  <!--Removed-->
        <ep:voip>verdadeiro</ep:voip> <!--Removed-->
        <ep:enableTSP>falso</ep:enableTSP>  <!--Removed-->
    </ep:telephony>   <!--Removed-->
    <ep:host>
        <ep:firstName></ep:firstName>
        <ep:lastName>teste</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, Pacífico (São Francisco)</ep:timeZone>
        <ep:timeZoneID>falso4</ep:timeZoneID>
        <ep:openTimeInSec>0</ep:openTimeInSec>
    </ep:schedule>
    <ep:attendeeOptions>
        <ep:joinRequiresAccount></ep:joinRequiresAccount>
    </ep:attendeeOptions>
    <ep:isAudioOnly>falso</ep:isAudioOnly>
    <ep:telePresence></ep:telePresence>
    <ep:isAlternateHost></ep:isAlternateHost>  <!--Removed-->
    <ep:isCreator></ep:isCreator>   <!--Removed-->
    <ep:hostKey>954462</ep:hostKey> <!--Removed-->
    <ep:supportE2E></ep:supportE2E>    <!--Removed-->
    <ep:isAllowJBH></ep:isAllowJBH>
    <ep:isCETMeeting></ep:isCETMeeting>
    <ep:isPersonalMeetingRoom></ep:isPersonalMeetingRoom>
    <ep:isNextUpcomingInstance></ep:isNextUpcomingInstance>
    <ep:meetingLink></ep:meetingLink>
    <ep:sipURL></ep:sipURL>
    <ep:displayMeetingUrl></ep:displayMeetingUrl>
    <ep:isAutoRecord>falso falso verdadeiro falso falso verdadeiro verdadeiro https://sqdemo6.DMZ.Webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed simon0@sqdemo6.dmz.webex.com simon0@sqdemo6.dmz.webex.com falso</ep:isAutoRecord>
</serv:bodyContent>

Atualizações de 39.2.0 API XML

Novo elemento lastLoginTime retornado na resposta LstSummaryUser

Um novo elemento de resposta, lastLoginTime, foi adicionado ao API LstSummaryUser. lastLoginTime retorna o último horário de logon para cada usuário. O elemento é retornado neste formato:

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

APIs afetadas:

  • LstSummaryUser

    • lastLoginTime

Exemplo de resposta 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>Sucesso</serv:result>
            <serv:gsbStatus>primário</serv:gsbStatus>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <use:user>
                <use:userID>3469487</use:userID>
                <use:objectGUID>a14e3312-e1d1-4E41-82b9-6ddac80c9f9a</use:objectGUID>
                <use:webExId>Sangeetha.Swaminathan@gmail.com</use:webExId>
                <use:firstName>sangee</use:firstName>
                <use:lastName>gmail</use:lastName>
                <use:email>Sangeetha.Swaminathan@gmail.com</use:email>
                <use:userRoleType>host</use:userRoleType>
                <use:registrationDate>12/11/2018 14:41:27</use:registrationDate>
                <use:active>desativada</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>

Atualizações de 39.1.0 API XML

Clique aqui para baixar o esquema 39.1.0 XML API.

Novo elemento apiVer adicionado à API GetAPIVersion

Um novo elemento de resposta, apiVer, foi adicionado ao API GetAPIVersion. Com esta atualização, a Convenção de nomenclatura da versão da API XML muda para corresponder a um número de versão unificado com outras áreas Cisco Webex produtos. apiVer retorna as novas informações de versão, como 39.1.0 para a atualização de janeiro de 2019.

APIs afetadas:

  • GetAPIVersion

    • apiVer

O elemento apiVersion será reprovado em 1º de maio de 2019 e a versão do elemento receberá um novo valor da API XML em 1º de maio de 2019.

Exemplo de resposta 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>Webex do sucesso</serv:result>
            <serv:gsbStatus>primário do</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>XML API v 11.0.0</ep:apiVersion>
            <ep:release>SP22</ep:release>
            <ep:apiVer>39.1.0</ep:apiVer>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Parâmetros de HQ e HD removidos do XML API

As propriedades de vídeo de HQ e HD são agora determinadas no nível do site, em vez de serem determinadas no nível do usuário. As duas opções para esses parâmetros são ignoradas ao enviar solicitações das seguintes APIs:

  • Criação reunião

  • Setmeeting

  • CreateTrainingSession

  • SetTrainingSession

As APIs Getmeeting e GetTrainingSession ainda retornam as duas opções (decidido pelo nível do site e do usuário) para evitar quebrar o código existente.

Novo elemento uploadLogFileUrl adicionado aos metadados do site retornados ao aplicativo de desktop

Um novo elemento uploadLogFileUrl foi adicionado à resposta retornada ao aplicativo de desktop quando ele chamar a API GetSite no servidor de API XML. O aplicativo de desktop pode carregar o arquivo de registro para uploadLogFileUrl.

APIs afetadas:

  • GetSite

    • uploadLogFileUrl

Exemplo de resposta GetSite:

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

Atualizações do 11.0.0 SP22 API

Limitação de tamanho de arquivo para UploadPMRImage

Ao carregar os avatares usando a API UploadPMRImage, uma nova limitação restringe o tamanho do arquivo para 5 MB. As tentativas de carregar arquivos maiores do que agora receberão uma mensagem de erro: "010100 tamanho da imagem que está sendo carregada é muito grande. Tente uma imagem menor do que 5 MB de tamanho."

Atualizações do 11.0.0 suporte SP21 API

Clique aqui para baixar o esquema XML API 11,0 suporte SP21.

Novo Autoregistro de elemento adicionado a createmeetings, Setmeeting, getmeetinge LstMeeting

Um novo elemento, denominado Autoregistro, foi adicionado às APIs createmeetings, Setmeetings, getmeetingse LstMeeting . o Autoregistro permite que os usuários gravem automaticamente Webex reuniões diretamente do Agendador de reunião. Isso fornece granularidade no nível da reunião, onde o método anterior para gravar automaticamente reuniões só podia ser acessado globalmente no nível do site.


O elemento de autogravar se aplica apenas ao Webex Meetings. Ela não se aplica a Webex Events ou Webex Training.

APIs afetadas:

  • Criação reunião

    • Gravação automática

  • Setmeeting

    • Gravação automática

  • Getmeeting

    • Gravação automática

  • LstMeeting

    • Gravação automática

Createmeeting atualizações:

configuração de Autoregistro

Comportamento quando gravar automaticamente todas as sessões usando a gravação baseada em rede está desabilitada no administração do site

True

Iniciar automaticamente a gravação quando a reunião começar

Falso (padrão) ou nenhum elemento

Não inicia automaticamente a gravação quando a reunião é iniciada


Se você gravar automaticamente todas as sessões usando a gravação baseada em rede estiver ativada, o elemento será ignorado e a gravação será iniciada automaticamente quando a reunião começar.

Reunir atualizações:

configuração de Autoregistro

Comportamento quando gravar automaticamente todas as sessões usando a gravação baseada em rede está desabilitada no administração do site

True

Iniciar automaticamente a gravação quando a reunião começar

Falso (padrão) ou nenhum elemento

Não inicia automaticamente a gravação quando a reunião é iniciada


Se você gravar automaticamente todas as sessões usando a gravação baseada em rede estiver ativada, o elemento será ignorado e a gravação será iniciada automaticamente quando a reunião começar.

Getmeeting atualizações:

configuração de Autoregistro

Comportamento quando gravar automaticamente todas as sessões usando a gravação baseada em rede está desabilitada no administração do site

True

Iniciar automaticamente a gravação quando a reunião começar

False

Não inicia automaticamente a gravação quando a reunião é iniciada


Se você gravar automaticamente todas as sessões usando a gravação baseada em rede estiver ativada, o elemento será ignorado e a gravação será iniciada automaticamente quando a reunião começar.

Exemplo de resposta de getmeetings :

Atualizações do LstMeeting :

configuração de Autoregistro

Comportamento quando gravar automaticamente todas as sessões usando a gravação baseada em rede está desabilitada no administração do site

True

Iniciar automaticamente a gravação quando a reunião começar

False

Não inicia automaticamente a gravação quando a reunião é iniciada


Se você gravar automaticamente todas as sessões usando a gravação baseada em rede estiver ativada, o elemento será ignorado e a gravação será iniciada automaticamente quando a reunião começar.

Exemplo de resposta LstMeeting:

Novo elemento isAutoRecord adicionado à API obterinformaçãodaseção

Junto com as alterações feitas nas APIs acima, um novo elemento, isAutoRecord, foi adicionado ao API do obterinformaçãodaseção . Este elemento pode ser usado para indicar se a gravação é iniciada automaticamente quando uma reunião é iniciada.

APIs afetadas:

  • Obterinformaçãodaseção

    • isAutoRecord

Atualizações do Obterinformaçãodaseção :

configuração de isAutoRecord

Comportamento quando gravar automaticamente todas as sessões usando a gravação baseada em rede está desabilitada no administração do site

True

Iniciar automaticamente a gravação quando a reunião começar

False

Não inicia automaticamente a gravação quando a reunião é iniciada


Se você gravar automaticamente todas as sessões usando a gravação baseada em rede estiver ativada, o elemento será ignorado e a gravação será iniciada automaticamente quando a reunião começar.

Exemplo de resposta obterinformaçãodaseção:

Atualizações do 11.0.0 SP20 API

Clique aqui para baixar o esquema XML API 11,0 SP20.

Novo elemento returnShareToMeRecording adicionado à solicitação de API LstRecording


Esta alteração foi anunciada anteriormente no XML API 11,0 SP17, mas está sendo aplicada a esta atualização.

Um novo elemento, returnShareToMeRecording, foi adicionado ao API LstRecording . returnShareToMeRecording é um booliano na solicitação de LstRecording.

Este novo elemento foi adicionado ao suporte para encontrar as gravações de convidado ou de convite. o returnShareToMeRecording é um sinalizador que permite que o API do LstRecording saiba que ele deve retornar as gravações de convidados ou convidar.

Quando o returnShareToMeRecording é definido comoverdadeiro , o LstRecording retorna o usuário da gravação como o proprietário e também retorna o usuário da gravação como um convidado ou convite compartilhado pelo proprietário.


Se os sinalizadores de compartilhamento automático e de compartilhamento manual estiverem desativados, o LstRecording retornará o usuário apenas como o proprietário das gravações.

Quando o returnShareToMeRecording está definido para falso, ou este elemento não está incluído na solicitação, LstRecording segue a mesma lógica que antes: Ela retorna o usuário de gravações como o proprietário.

APIs afetadas:

  • LstRecording

    • returnShareToMeRecording

Atualizações do LstRecording :

Elemento shareToMe adicionado à resposta da API LstRecording


Esta alteração foi anunciada anteriormente no XML API 11,0 SP17, mas está sendo aplicada a esta atualização.

Um novo elemento, shareToMe, foi adicionado ao API LstRecording . shareToMe é um booliano na resposta para o LstRecording.

Este novo elemento foi adicionado ao suporte para encontrar as gravações de convidado ou de convite. shareToMe é um sinalizador para definir se o usuário é o proprietário ou um convidado da gravação atual.

Quando shareToMe é verdadeiro, o usuário não é o proprietário da gravação atual. O usuário pode ser um convidado ou a gravação é compartilhada pelo proprietário.

Quando o shareToMe é falso, ou este elemento não está na resposta, LstRecording segue a mesma lógica que antes: o usuário é o proprietário da gravação atual.

APIs afetadas:

  • LstRecording

    • shareToMe

Atualizações do LstRecording :

exemplos de solicitações 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>verdadeiro</returnShareToMeRecording>
</bodyContent>

exemplos de respostas returnShareToMeRecording e shareToMe :

Novos elementos adicionados à API GetEvent

Quatro novos elementos foram adicionados à API GetEvent :

  • isCETMeeting: um booliano verdadeiro/falso indicando se o evento Webex suporta a plataforma de vídeo Webex 2 (CMR 4,0)

  • sipURL: a URL usada para entrar Webex reunião de vídeo a partir de um aplicativo ou sistema de videoconferência

  • standaloneDialingIPAddress: o endereço de IP que pode ser usado para discar para a reunião de vídeo Webex de um aplicativo ou sistema de videoconferência

  • panelistNumericPassword: a senha para entrar na reunião de vídeo Webex de um aplicativo ou sistema de videoconferência

Se o site suportar Webex vídeo, o organizador tem privilégios de vídeo Webex Events, e o evento suporta Webex plataforma de vídeo 2 (CMR 4,0), GetEvent retorna esses elementos. Caso contrário, o GetEvent não os retornará.

APIs afetadas:

  • Getevent

    • isCETMeeting

    • sipURL

    • standaloneDialingIPAddress

    • panelistNumericPassword

Novo elemento panelistNumericPassword adicionado à API obterinformaçãodaseção

O obterinformaçãodaseção tem um novo elemento, panelistNumericPassword, que contém a senha para entrar na reunião de vídeo Webex de um aplicativo ou sistema de videoconferência.

Se o site suportar Webex vídeo, o organizador tem privilégios de vídeo Webex Events, e o evento suporta a plataforma de vídeo Webex 2 (CMR 4,0), obterinformaçãodaseção retorna esses quatro elementos:

  • isCETMeeting: um booliano verdadeiro/falso indicando se o evento Webex suporta a plataforma de vídeo Webex 2 (CMR 4,0)

  • sipURL: a URL usada para entrar Webex reunião de vídeo a partir de um aplicativo ou sistema de videoconferência

  • standaloneDialingIPAddress: o endereço de IP que pode ser usado para discar para a reunião de vídeo Webex de um aplicativo ou sistema de videoconferência

  • panelistNumericPassword: a senha para entrar na reunião de vídeo Webex de um aplicativo ou sistema de videoconferência


Para Webex Meetings, estes elementos já existiam no obterinformaçãodaseção:

  • isCETMeeting

  • sipURL

  • standaloneDialingIPAddress

APIs afetadas:

  • Obterinformaçãodaseção

    • panelistNumericPassword

As alterações de esquema feitas em GetEvent e obterinformaçãodaseção

Atualizações de GetEvent :

Atualizações do Obterinformaçãodaseção :

Atualizações do 11.0.0 SP18 API

Clique aqui para baixar o esquema XML API 11,0 SP18.

Novo elemento EnableCloudTelepresence adicionado à API GetSite

Um novo elemento, o EnableCloudTelepresence foi adicionado à API GetSite .

Quando a opção EnableCETForAllUsers estiver habilitada, o Webex verifica para ver se o usuário suporta Webex vídeo (CMR). Agora também retorna um novo elemento EnableCloudTelepresence na API GetSite .

APIs afetadas:

  • getSite

  • EnableCloudTelepresence

Resposta de exemplo GetSite:

Atualizações do 11.0.0 SP17 API

Novo elemento returnShareToMeRecording adicionado à solicitação de API LstRecording

Um novo elemento, returnShareToMeRecording, foi adicionado ao API LstRecording . returnShareToMeRecording é um booliano na solicitação de LstRecording.

Este novo elemento foi adicionado para oferecer suporte à recepção de gravações de convidado ou de convidados. o returnShareToMeRecording é um sinalizador que permite que o API do LstRecording saiba que ele deve retornar as gravações de convidados ou convidar.

Quando o returnShareToMeRecording é definido como verdadeiro, o LstRecording retorna o usuário de gravações como proprietário e também retorna o usuário de gravações como um convidado ou convite compartilhado pelo proprietário.


Se os sinalizadores de compartilhamento automático e de compartilhamento manual estiverem desativados, o LstRecording retornará apenas o usuário como o proprietário das gravações.

Quando o returnShareToMeRecording está definido para falso, ou este elemento não está incluído na solicitação, LstRecording segue a mesma lógica que antes: Ela retorna o usuário de gravações como o proprietário.

APIs afetadas:

  • LstRecording

  • returnShareToMeRecording

Atualizações do LstRecording :

Novo elemento shareToMe adicionado à resposta da API LstRecording

Um novo elemento, shareToMe, foi adicionado ao API LstRecording . shareToMe é um booliano na resposta para o LstRecording.

Este novo elemento foi adicionado para oferecer suporte à recepção de gravações de convidado ou de convidados. o shareToMe é um sinalizador que determina se o usuário é o proprietário ou o convidado ou convite para gravação atual.

Quando shareToMe é verdadeiro, o usuário não é o proprietário da gravação atual. O usuário pode ser um participante ou convidado ou a gravação é compartilhada pelo proprietário.

Quando o shareToMe é falso, ou este elemento não está na resposta, LstRecording segue a mesma lógica que antes: o usuário é o proprietário da gravação atual.

APIs afetadas:

  • LstRecording

  • shareToMe

Atualizações do LstRecording :

Novos elementos para a capacidade do convidado adicionados à resposta do API GetSite

Quatro novos elementos foram adicionados à API GetSite para indicar a capacidade do convidado para os seguintes serviços de Webex:

attendeeCapacityForMC -Webex Meetings

attendeeCapacityForEC – Webex Events

attendeeCapacityForTC – Webex Training

attendeeCapacityForSC – Webex support

Esses valores retornados indicam o número máximo de convidados que a reunião, o evento ou a sessão podem ter. Eles são filhos do elemento CISiteLicenseInfo na resposta.

APIs afetadas:

  • getSite

  • attendeeCapacityForMC

  • attendeeCapacityForEC

  • attendeeCapacityForTC

  • attendeeCapacityForSC

Exemplo de resposta 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>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>falso falso falso43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC></ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC></ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC></ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost></ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                    <ns1:attendeeCapacityForMC>1000</ns1:attendeeCapacityForMC>
                    <ns1:attendeeCapacityForTC>1000</ns1:attendeeCapacityForTC>
                    <ns1:attendeeCapacityForEC>3000</ns1:attendeeCapacityForEC>
                    <ns1:attendeeCapacityForSC>500</ns1:attendeeCapacityForSC>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Atualizações do 11.0.0 SP16 API

Novos hostStreamURL de API adicionados ao lstRecordingResponse

O elemento hostStreamURL foi adicionado à resposta LstRecording como parte dos detalhes da gravação. hostStreamURL retorna uma URL para o organizador usar para visualizar a gravação sem ter que iniciar sessão primeiro. Esta URL é válida por 30 minutos após sua geração.

APIs afetadas:

  • hostStreamURL

exemplo de resposta 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"/>

A API GetSite usa a nova modelagem WebDB para retornar dados

Por solicitação do cliente, o API GetSite agora recupera uma licença de organizador mais precisa, dados de relatórios de uso e outros dados usando a nova modelagem WebDB para sites CI.

APIs afetadas:

  • GetSite

Exemplo de resposta 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>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>falso falso falso43</ns1:accountNumberUsedForMC>
                    <ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
                    <ns1:allowOverageForTC></ns1:allowOverageForTC>
                    <ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
                    <ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
                    <ns1:allowOverageForEC></ns1:allowOverageForEC>
                    <ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
                    <ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
                    <ns1:allowOverageForSC></ns1:allowOverageForSC>
                    <ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
                    <ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
                    <ns1:allowOverageForCMRHost></ns1:allowOverageForCMRHost>
                    <ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
                </ns1:CISiteLicenseInfo>
            </ns1:siteInstance>
        </serv:bodyContent>
    </serv:body>
</serv:message>

Exemplo de resposta GetSite para sites 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>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>verdadeiro</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>

Atualizações do 11.0.0 SP15 API

Retornar o link da reunião Webex Meetings usando a API GetSessionsInfo

O esquema para a API obterinformaçãodaseção tem um novo valor de retorno, meetingLink. Você pode usar um link de reunião para iniciar uma reunião Webex como um organizador ou entrando em uma reunião de Webex como um convidado.

APIs afetadas:

  • Obterinformaçãodaseção

  • meetingLink

Exemplo de resposta obterinformaçãodaseção:

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

Nova condição para consultar por recordId na API do LstRecording

Agora você pode usar o LstRecording para consultar gravações usando o CódigoDaGravação de gravação. Existem dois tipos de IDs de gravação:

  • IDs de gravação para Webex Meetings, Webex Events e Webex Training

  • IDs de gravação NBR para gravações diversas

Se houver um elemento ServiceType na solicitação XML, então LstRecording retornará uma gravação de serviço (Webex Meetings, Webex Events e Webex Training) apenas.

Se não houver um elemento ServiceType na solicitação XML, então LstRecording retornará apenas uma gravação NBR.

APIs afetadas:

  • LstRecording

  • RecordingID

Exemplos de resposta LstRecording:

Exemplo de solicitação para uma ID de gravação de serviço:

<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>ASC</orderAD>
         <orderBy>RecordName</orderBy>
         <orderAD>ASC</orderAD>
    </order>
</bodyContent>

Exemplo de solicitação para uma ID de gravação NBR:

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

Atualizações do 11.0.0 SP14 API

Relatórios resumidos de uso preliminar para Meeting Center

Duas novas APIs foram adicionadas para Meeting Center relatórios preliminares, LstmeetingusagePreliminaryHistory e LstmeetingattendeePreliminaryHistory. Eles terão o mesmo comportamento que LsteventsessionPreliminaryHistory e LsteventattendeePreliminaryHistory no relatório final.

APIs afetadas:

  • LstmeetingusagePreliminaryHistory

  • LstmeetingattendeePreliminaryHistory

Exemplo de solicitação 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>23/04/2018 00:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>24/04/2018 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>E</listMethod>
            </listControl>
            <order>
                <orderBy>STARTTIME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFNAME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

Exemplo de resposta 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>Sucesso</serv:result>
            <serv:gsbStatus>primário</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 da</history:meetingType>
                <history:timeZoneWithDST>San Francisco (horário de Verão do Pacífico, 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>

Exemplo de solicitação 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>23/04/2018 00:00:00</sessionStartTimeStart>
                <sessionStartTimeEnd>24/04/2018 11:59:59</sessionStartTimeEnd>
            </startTimeScope>
            <listControl>
                <startFrom>1</startFrom>
                <maximumNum>10</maximumNum>
                <listMethod>E</listMethod>
            </listControl>
            <order>
                <orderBy>STARTTIME</orderBy>
                <orderAD>ASC</orderAD>
                <orderBy>CONFID</orderBy>
                <orderAD>ASC</orderAD>
            </order>
        </bodyContent>
    </body>
</serv:message>

Exemplo de resposta 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>Sucesso</serv:result>
            <serv:gsbStatus>principal</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></history:title>
                <history:phoneNumber>1222654-3210,,,,</history:phoneNumber>
                <history:address1>1 qualquer rua</history:address1>
                <history:address2>XYZ</history:address2>
                <history:city>SANJOSE</history:city>
                <history:state>CA</history:state>
                <history:country>EUA</history:country>
                <history:zipCode>95111</history:zipCode>
                <history:name>usuário test2</history:name>
                <history:email>ut2@qa.webex.com</history:email>
                <history:joinTime>04/23/2018 19:13:06</history:joinTime>
                <history:participantType>convidado</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 04/23/2018 19:14:10 convidado teste do organizador</history:email>
                <history:joinTime></history:joinTime>
                <history:participantType></history:participantType>
                <history:confID>93115261364733685</history:confID>
            </history:meetingAttendeePreliminaryHistory>
            <history:meetingAttendeePreliminaryHistory>
                <history:meetingKey>800150023</history:meetingKey>
                <history:confName>200804231215</history:confName>
                <history:name></history:name>
                <history:email>testuser@webex.com</history:email>
                <history:joinTime>04/23/2018 19:12:42</history:joinTime>
                <history:participantType>convidado</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>

Retornando URL SIP e URL do Skype da API do GLA obterinformaçãodaseção

Dois novos elementos, <sipURL> e <skypeURL>foram anexados à resposta ao chamar a API GLA obterinformaçãodaseção . Estes elementos são elementos base que podem ser retornados para acesso anônimo.

  • <sipURL> pode ser usado para entrar em reuniões a partir de um TelePresence ou outro dispositivo de vídeo da Cisco. Dessa forma, apenas as reuniões que usam a plataforma de vídeo Cisco versão 1,0 ou 2,0 devem obterinformaçãodaseção retornar o <sipURL> elemento.

  • <skypeURL> pode ser usado para entrar em reuniões a partir de um aplicativo Microsoft Skype, sem quaisquer limitações ou condições, de modo que possa ser devolvido para cada chamada.

APIs afetadas:

  • Obterinformaçãodaseção

Exemplo de resposta:

Retornando a URL SIP e o link da reunião de Getmeeting API

Três novos elementos,, <isCETMeeting><meetingLink>e <sipURL>, foram anexados à resposta ao chamar a API getmeeting .

  • <isCETMeeting> Retorna se a reunião está usando uma plataforma de vídeo Cisco (suporta TelePresence e vídeo).

  • <meetingLink> pode ser usado para se conectar a reuniões.

  • <sipURL> pode ser usado para entrar em reuniões a partir de um TelePresence ou outro dispositivo de vídeo da Cisco. Dessa forma, apenas as reuniões que usam a plataforma de vídeo Cisco versão 1,0 ou 2,0 devem obter o elemento.

APIs afetadas:

  • Getmeeting

Exemplo de resposta de getmeetings :

Atualizações do 11.0.0 SP13 API

Anúncio de substituição do <siteID> elemento no pai <securityContext>

A Cisco planeja <siteID> substituir o elemento no <securityContext> elemento pai e substituí-lo com o <siteName>. Devido a um grande número de <siteID> elementos que muitas vezes estão sendo alterados durante migrações do site, as organizações incorrem em altos custos de manutenção para continuar a usar este elemento. Esta é uma notificação antecipada de dois anos.

  • Para clientes Webex existentes, o impacto ocorrerá em 1º de maio de 2020.

  • Os novos clientes devem usar o elemento a partir de 1º de maio de 2018.<siteName>

  • Os clientes que fazem integrações com o CI, Spark ou o sistema Atlas devem usar o elemento a partir de 1º de maio de 2018.<siteName>

APIs afetadas:

  • <siteName>

  • <securityContext>

Validação de dados dos <tollCallInData><tollFreeCallInData> elementos e

A partir de 1º de junho de 2018, o <tollCallInData> e as <tollFreeCallInData> APIs serão validados por dados. Isso afeta as <CreateUser><SetUser> APIs e.

Os sites que usam sequências não válidas ou sequências formatadas incorretamente em seus dados de chamada de entrada devem corrigir as seqüências de caracteres para que esses elementos passem na validação de dados.

Abaixo estão exemplos de CreateUser e SETUSER, tollCallInData e tollFreeCallInData no formato correto:

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

Atualizações do 11.0.0 SP12 API

Duas novas APIs SetContact e DelContacts

O esquema da API XML anteriormente tinha apenas duas APIs Createcontacts e LstContacts, que não fornecia o gerenciamento completo dos contatos do usuário. A fim de fornecer funcionalidades melhores para gerenciar o contato do usuário usando o XML API, adicionamos essas duas novas APIs, setcontact e DelContacts.

API

Notas

SetContact

Chamar esta API para modificar informações de contato, como e-mail, nome, título e idioma.

Exceções:

  • Se o contato não for encontrado pelo elemento contactEmail, a exceção 140004 "contato não encontrado" será retornada

  • Se o site Webex não suportar um idioma específico, a exceção 030060 "não é uma linguagem válida" será retornada

  • Se o novo endereço de e-mail ao qual o usuário deseja alterar for uma duplicata com outro contato na lista de meus contatos , a exceção 140001 "e-mail é usado por outro contato" é retornada

DelContacts

Chamar esta API para excluir um ou mais contatos da lista de meus contatos baseada em e-mails.

o ContactID será retornado se o e-mail fornecido puder ser encontrado na lista de meus contatos e ignorará o e-mail dado se não estiver na lista de meus contatos .

Se todos os e-mails fornecidos não forem encontrados na lista de meus contatos, a exceção 00015 (Desculpe, nenhum registro encontrado) será retornada.

APIs afetadas:

  • SetContact

  • DelContacts

Exemplo de solicitação do setcontact :

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
    <securityContext>
      <siteName>SiteName</siteName>
      <webExID>userid</webExID>
       <password>UserPWD</password>
    </securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.SetContact">
            <contactEmail>Endereço de E-mail de contato</contactEmail>
           <contact>
                <name>novo nome do contato</name>
                <email>novo contato endereço de e-mail</email>
                <title>Novo título</title>
                <company>Nova empresa</company>
                <notes>novas notas</notes>
                <url>novo link</url>
                <phones>
                    <phone>1,, 408 # # # # # #,,,,</phone>
                    <mobilePhone>1,, 408 # # # # # #,,,,</mobilePhone>
                    <fax>1,, 408 # # # # # #,,,,</fax>
                </phones>
                <address>
                    <address1>Novo endereço 1</address1>
                    <address2>novo endereço 2</address2>
                    <city>nova cidade</city>
                    <state>novo estado novo</state>
                    <zipCode>CEP nova</zipCode>
                    <country>empresa</country>
                </address>
                <language>Novo idioma</language>
            </contact>
</bodyContent>
</body>
</serv:message>

Exemplo de resposta do setcontact :

<?xml version="1.0" encoding="ISO-8859-1"?>
<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common" xmlns:ep="http://www.webex.com/schemas/2002/06/service/ep" xmlns:meet="http://www.webex.com/schemas/2002/06/service/meeting">
    <serv:header>
        <serv:response>
            <serv:result>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>

Exemplo de solicitação 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>

Exemplos de resposta DelContacts:


Neste exemplo, dois contatos existentes são excluídos da lista de meus contatos .

<?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>SUCESSO</serv:result>
            <serv:gsbStatus>primário</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>


Neste exemplo, os e-mails não estão na lista de meus contatos .

<?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>FALHA</serv:result>
            <serv:reason>, nenhum registro encontrado</serv:reason>
            <serv:gsbStatus>primário</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Atualizações do 11.0.0 SP11 API

Nova API LstTrainingPollResultsHistory

O API LstTrainingPollResultsHistory foi originalmente implementado na API da URL. Por solicitação do cliente, ele agora é implementado na API XML.

Os resultados da sondagem da lista são retornados pela inclusão de um Training Center SessionKey. A API pode ser solicitada pelo proprietário da sessão de Training Center ou por um administrador do site.


A configuração aprimorada de sondagem de TC deve ser ativada antes do treinamento os resultados da sondagem são armazenados no Webex DB:

APIs afetadas:

  • LstTrainingPollResultsHistory

Exemplo de solicitação 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>


A solicitação é apenas para 11.0.0 API T32/XML.

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

A resposta é diferente se a reunião não for encontrada, não pertence ao usuário solicitando, ou se o usuário solicitando que ele também não é um administrador do site.

Exemplo de resposta:

<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>FALHA</serv:result>
            <serv:reason>Desculpe, nenhum registro encontrado</serv:reason>
            <serv:gsbStatus>PRIMÁRIO</serv:gsbStatus>
            <serv:exceptionID>000015</serv:exceptionID>
        </serv:response>
    </serv:header>
    <serv:body>
        <serv:bodyContent/>
    </serv:body>
</serv:message>

Nova opção AttendeeSendVideo nas APIs CreateTrainingSession, SetTrainingSessione GetTrainingSession

Como as opções disponíveis ao agendar uma sessão de Training Center incluem enviar vídeo, a API XML agora adicionou a opção attendeeSendVideo para criar, obter e definir APIs para Training Center sessões.

APIs afetadas:

  • CreateTrainingSession

  • SetTrainingSession

  • GetTrainingSession

Design

A opção foi armazenada na tabela DB WbxMMConfParam/ParamValue como paramName = ' optionSupportSendVideo '

CreateTrainingSession solicitar atualizações:

SetTrainingSession solicitar atualizações:


A solicitação é apenas para 11.0.0 API T32/XML.

Atualizações de resposta GetTrainingSession:

Alterar confname tamanho máximo de 128 exibir caracteres

O nome da conferência String confname está limitado a um máximo de 128 de exibição de caracteres. Essa alteração é alinhada com a limitação da página inicial do J2EE. Se uma solicitação de API inclui confname que está vazia ou excede um comprimento de caracteres de exibição de 128, a seguinte mensagem de erro é exibida:

"060065 nome de conferência de entrada ilegal. O nome da conferência não pode estar vazio nem exceder o tamanho máximo de caracteres de exibição 128 ".

APIs afetadas:

  • ConfName

Mensagem de exceção alterada na API LstRecording

A mensagem de exceção lançada quando o escopo do tempo de consulta excede o limite máximo no API LstRecording foi alterado. Por padrão, as consultas suportam 4 semanas de gravações. Solicitações de mais de quatro semanas recebem a seguinte mensagem de erro:

"999999 excedeu o escopo máximo de tempo de consulta de 28 dias".

APIs afetadas:

  • LstRecording

Atualizações do 11.0.0 SP10 API

A atualização do XML API 11,0 SP10 não tem alterações de esquema.