이 문서에는 XML API 월별 SP 릴리즈에 대한 업데이트 및 변경 사항이 포함됩니다.
XML API 40 및 REST API 40에 대한 자세한 정보는 Cisco Webex Meetings API 업데이트 개요 (API 40)를 참조하십시오.
XML API 11 SP9 이하에 대한 업데이트는 Cisco DevNet으로 이동합니다.
XML API 39.11.0 업데이트
LstSummaryUser는 마지막으로 수정한 시간으로 사용자 계정을 쿼리할 수 있습니다.
사용자가 마지막으로 수정된 시간에 기반하여 사용자 계정을 쿼리할 수 있도록 LstSummaryUser API를 업그레이드하고 있습니다. 세 개의 새로운 구성 요소인 modifiedDateStart, modifiedDateEnd, lastModifiedTime이 API에 추가되었습니다.
 |
이 쿼리에 대한 최대 시간 범위는 90일입니다. 90일 이상의 시간 범위를 입력하는 경우, 다음과 같은 오류가 나타납니다. 999999 수정된 날짜 쿼리에 대한 최대 날짜 범위는 90일입니다. |
적용되는 API:
-
LstSummaryUser
LastSummaryUser 요청 예제:
<?xml version="1.0" encoding="UTF-8"?>
<message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2009/05/service">
<header>
<securityContext>
<siteName>Site_Name</siteName>
<webExID>SiteAdmin</webExID>
<password>Password</password>
<partnerID>webexpartner</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.user.LstsummaryUser">
<dataScope>
<modifiedDateStart>10/01/2019 09:24:54</modifiedDateStart>
<modifiedDateEnd>11/30/2019 09:24:54</modifiedDateEnd>
<timeZoneID>4</timeZoneID>
</dataScope>
</bodyContent>
</body>
</message>
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xsi:type="use:lstsummaryUserResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<use:user>
<use:userID>**5124***</use:userID>
<use:webExId>***MR***</use:webExId>
<use:firstName>***MR***</use:firstName>
<use:lastName>***est***</use:lastName>
<use:email>***est***@qa.webex.com</use:email>
<use:userRoleType>HOST</use:userRoleType>
<use:registrationDate>06/19/2016 22:13:06</use:registrationDate>
<use:active>DEACTIVATED</use:active>
<use:timeZoneID>4</use:timeZoneID>
<use:meetingTypes>
<use:meetingType>3</use:meetingType>
<use:meetingType>9</use:meetingType>
<use:meetingType>10</use:meetingType>
<use:meetingType>11</use:meetingType>
<use:meetingType>13</use:meetingType>
<use:meetingType>14</use:meetingType>
<use:meetingType>102</use:meetingType>
</use:meetingTypes>
<use:lastLoginTime>10/19/2019 23:13:14</use:lastLoginTime>
<use:lastModifiedTime>11/11/2019 19:11:11</use:lastModifiedTime>
</use:user>
XML API 39.10.0 업데이트
GetSessionInfo 및 GetUserCard에서 익명의 액세스를 사용할 때 CAPTCHA 코드를 반환함
보안 업데이트의 일환으로, CAPTCHA 코드 응답 보호를 포함하여 GetSessionInfo 및 GetUserCard API를 강화했습니다. 응용프로그램이 익명의 액세스를 사용하여 API에 전화하는 경우, CAPTCHA 코드 입력을 지원하기 위해 응용프로그램을 향상시킵니다.
적용되는 API:
-
GetSessionInfo -
GetUserCard
CAPTCHA 보안 및 응답 업데이트:
GetSessionInfo 응답 - CAPTCHA 포함하지 않음 예제:
<?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>FAILURE</serv:result>
<serv:reason>관련된 미팅을 찾을 수 없음</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>060001</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
GetSessionInfo 응답 - CAPTCHA 포함 예제:
<?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>FAILURE</serv:result>
<serv:reason>관련된 미팅을 찾을 수 없음</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>060001</serv:exceptionID>
<serv:CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</serv:CAPTCHAID>
<serv:CAPTCHAImage> iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA
........... maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu+ZUFb7SAAAAAElFTkSuQmCC </serv:CAPTCHAImage>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
CAPTCHA 응답을 수신하고 계속 API로 전화하는 경우, API 요청에 다음 CAPTCHAID 및 CAPTCHAWord를 포함합니다.
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteName>sqdemo6</siteName>
<CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</CAPTCHAID>
<CAPTCHAWord>pyjihk</CAPTCHAWord>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.ep.GetSessionInfo">
<sessionKey>715801743</sessionKey>
</bodyContent>
</body>
</serv:message>
GetSessionInfo 응답 - 올바르지 않은 CAPTCHAID 및 CAPTCHAWord 예제:
<?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>FAILURE</serv:result>
<serv:reason>CAPTCHA ID 및 단어가 유효하지 않거나 없음</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>030113</serv:exceptionID>
<serv:CAPTCHAID>SDDHEEfgkerwAAAI****qHS****Nfx_d34znF8RdVHzrsMIYFeuArjD96Q2:234322374320JGUBE349924</serv:CAPTCHAID>
<serv:CAPTCHAImage> iVBORw0KGgoAAAANSUhEUgAAAHgAAAAyCAMAAACgee/qAAADAFBMVEUAAAAAADMAAGYAAJkAAMwAAP8AMwAAMzMAM2YA
........... maorF0PESWQ15APDKJ74YLs/hlGmaRGeJuRxvyyg8smcK3veB/v5sueF/pxD8H4J/A0HPu+ZUFb7SAAAAAElFTkSuQmCC </serv:CAPTCHAImage>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
LstSummaryUser 지원 - 개인 룸 URL 반환용
새로운 응답 요소인 personalMeetingRoomURL을 LstSummaryUser API에 추가했습니다.
LstSummaryUser 응답 예제:
XML API 39.9.0 업데이트
개인 미팅 룸(PMR)에 대한 짧은 SIP URL 지원
PMR에 대한 짧은 SIP URL 형식 지원은 GetSessionInfo, GetMeeting, GetUser 및 GetMe API에 영향을 미칩니다. displayMeetingUrl이라고 칭하는 새로운 응답 요소가 GetUser 및 GetMe API에 추가되었으며, GetSessionInfo 및 GetMeeting에 이미 나타납니다. displayMeetingUrl은 사용자의 PMR URL을 반환합니다.
적용되는 API:
-
GetSessionInfo -
GetMeeting -
GetUser -
GetMe
GetUser 응답 예제:
GetMe 응답 예제:
GetSessionInfo는 익명 액세스에 대해 필요한 요소를 반환합니다.
보안 요구 사항의 일환으로, 이제 익명 액세스에 대해 필요한 요소만 GetSessionInfo에서 반환합니다.
GetSessionInfo 응답 예제:
<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:status>NOT_INPROGRESS</ep:status>
<ep:sessionkey>715952675</ep:sessionkey>
<ep:accessControl>
<ep:listStatus>PUBLIC</ep:listStatus>
<ep:registration>false</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, Pacific (San Francisco)</ep:timeZone>
<ep:timeZoneID>4</ep:timeZoneID>
</ep:schedule>
<ep:attendeeOptions>
<ep:joinRequiresAccount>false</ep:joinRequiresAccount>
</ep:attendeeOptions>
<ep:isAllowJBH>true</ep:isAllowJBH>
<ep:isCETMeeting>true</ep:isCETMeeting>
<ep:isPersonalMeetingRoom>false</ep:isPersonalMeetingRoom>
<ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/e.php?MTID=m2399b241f12722ca325388495e845103</ep:meetingLink>
<ep:sipURL>715952675@sqdemo6.dmz.webex.com</ep:sipURL>
<ep:displayMeetingUrl>715952675@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
</serv:bodyContent>
적용되는 API:
-
GetSessionInfo
미팅 및 이벤트 예약 작동 변경
기본적으로 예약된 모든 미팅은 비디오 장치를 사용할 수 있는 미팅입니다. 단, 미팅을 예약할 때 미팅의 오디오에 대해 없음 또는 기타를 선택하면 미팅은 비디오 장치를 사용할 수 있는 Webex 미팅 외의 미팅으로 예약됩니다.
적용되는 API:
-
CreateMeeting -
SetMeeting -
CreateEvent -
SetEvent
XML API 39.8.0 업데이트
LsttrainingattendeeHistory는 이제 미팅 참석자 집중도를 반환합니다.
새로운 응답 요소인 attentionToDurationPercentage가 LsttrainingattendeeHistory API에 추가되었습니다. LsttrainingattendeeHistory는 미팅 참석자의 집중도 세부 사항을 반환합니다. 요소는 다음 형식으로 반환됩니다.
<history:attentionToDurationPercentage>100</history:AttentionToDurationPercentage>
적용되는 API:
-
LsttrainingattendeeHistory-
attentionToDurationPercentage -
attentionToAttendancePercentage
-
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는 이제 라이센스 수를 반환합니다.
GetSite API에서 다른 라이센스 수를 반환하기 위해 새로운 응답 요소가 제공되었습니다.
적용되는 API:
-
GetSite-
EEActiveUserCount -
activeCETHost -
MCActiveUserCount -
ECActiveUserCount -
TCActiveUserCount -
SCActiveUserCount
-
GetSiteFT 및 SetSiteFT 재설계
GetSiteFT 및 SetSiteFT API는 동적인 기능 토글을 허용하도록 재설계되었습니다.
적용되는 API:
-
GetSiteFT -
SetSiteFT
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>{이는 머신 계정 액세스 토큰임}</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>
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteFTResponse">
<ns1:featureToggles>
<ns1:featureToggle>
<ns1:name>SupportCrossLaunch</ns1:name>
<ns1:value>false</ns1:value>
</ns1:featureToggle>
<ns1:featureToggle>
<ns1:name>RemoveCMRLicenseSA</ns1:name>
<ns1:value>false</ns1:value>
</ns1:featureToggle>
</ns1:featureToggles>
</serv:bodyContent>
</serv:body>
</serv:message>
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>{이는 머신 계정 액세스 토큰임}</accessToken>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.site.SetSiteFT">
<featureToggles>
<featureToggle>
<name>SupportCrossLaunch</name>
<value>false</value>
</featureToggle>
<featureToggle>
<name>SupportPeopleInsight</name>
<value>true</value>
</featureToggle>
</featureToggles>
</bodyContent>
</body>
</serv:message>
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:setSiteFTResponse"/>
</serv:body>
</serv:message>
이제 미팅 설명 길이는 2500자로 제한됨
이제 다음 API에 대해 미팅 설명 요소의 콘텐츠 길이는 2500자로 제한됩니다.
적용되는 API:
-
CreateEvent -
SetEvent -
CreateTrainingSession -
SetTrainingSession
이는 Cisco Webex에서 요청을 처리할 수 있게 하기 위한 의도입니다. 미팅 설명이 2500자보다 긴 경우, 다음과 같은 오류 메시지가 반환됩니다.
XML API 39.5.0 업데이트
새로운 요소 videoMeshInterclusters가 SetSite 및 GetSite 스키마에 추가됨
새로운 요소인 videoMeshInterclusters가 SetSite 요소에 추가되었습니다. videoMeshInterclusters에는 세 개의 하위 요소인 videoMeshHomeCluster1, videoMeshHomeCluster2, videoMeshHomeCluster3도 포함됩니다.
적용되는 API:
-
SetSite-
videoMeshInterclusters-
videoMeshHomeCluster1 -
videoMeshHomeCluster2 -
videoMeshHomeCluster3
-
-
-
GetSite-
videoMeshInterclusters-
videoMeshHomeCluster1 -
videoMeshHomeCluster2 -
videoMeshHomeCluster3
-
-
SetSite 요청 업데이트:
GetSite 응답 업데이트:
XML API 39.3.0 업데이트
XML API에서 짧은 SIP URL, 새 구성 요소 displayMeetingUrl
여기를 클릭하여 XML API 39.3 스키마를 다운로드하십시오.
현재 Webex 미팅에 참여할 때 앱 또는 장치에서 사이트 정보를 제공해야 하며, 이로 인해 간혹 미팅 참여가 어려울 수 있습니다. 특히 SIP 장치에서 다이얼하는 경우에는 사용자가 meeting_number@sitename.webex.com을 입력해야 하기 때문에 더욱 어렵습니다.
미팅 참여 과정을 더욱 쉽게 만들기 위해 미팅 SIP URI에서 사이트명을 입력하도록 요구하는 과정을 제거했습니다. meeting_number@webex.com. 이전 버전과 호환되게 하기 위해 이전의 형식은 sipURL에서 작동하고, 새로운 형식은 새로운 요소인 displayMeetingUrl에 첨부됩니다.
적용되는 API:
-
GetMeeting-
displayMeetingUrl
-
-
GetEvent-
displayMeetingUrl
-
-
GetSessionInfo-
displayMeetingUrl
-
GetMeeting 응답 예제:
<meet:isCETMeeting>true</meet:isCETMeeting>
<meet:meetingLink>https://sqdemo.dmz.webex.com/sqdemo/j.php?MTID=m0cdefe09626ba0bec956cdf9088bff55</meet:meetingLink>
<meet:sipURL>712296997@sqdemo.dmz.webex.com</meet:sipURL>
<meet:displayMeetingUrl>712296997@dmz.webex.com</meet:displayMeetingUrl>
</serv:bodyContent>
GetEvent 응답 예제:
<event:hostType>1001001</event:hostType>
<event:isCETMeeting>true</event:isCETMeeting>
<event:sipURL>713847821@sqdemo.dmz.webex.com</event:sipURL>
<event:displayMeetingUrl>713847821@dmz.webex.com</event:displayMeetingUrl>
</serv:bodyContent>
GetSessionInfo 응답 예제:
<ep:isCETMeeting>true</ep:isCETMeeting>
<ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
<ep:meetingLink>https://sqdemo.dmz.webex.com/sqdemo/j.php?MTID=ee7d38639d0b4a9ed2eb8802cfa2810dd</ep:meetingLink>
<ep:sipURL>713847821@sqdemo.dmz.webex.com</ep:sipURL>
<ep:displayMeetingUrl>713847821@dmz.webex.com</ep:displayMeetingUrl>
</serv:bodyContent>
이메일 예제:
현재 설명 길이는 1024자로 제한됨
이제 다음 API에 대해 설명 요소의 콘텐츠 길이는 1024자로 제한됩니다.
적용되는 API:
-
CreateTrainingSession -
SetTrainingSession -
CreateEvent -
SetEvent
이 변경 사항은 Cisco Webex에서 요청을 처리할 수 있게 하기 위함입니다. 설명이 1024자보다 긴 경우, 다음과 같은 오류 메시지가 반환됩니다. "060067 올바르지 않은 설명 입력. 설명은 최대 표시 문자의 길이인 1024자를 초과할 수 없습니다."
1024자보다 긴 설명에 대한 응답 예제:
<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>FAILURE</serv:result>
<serv:reason> 올바르지 않은 설명 입력. 설명은 최대 표시 문자의 길이인 1024자를 초과할 수 없음 </serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>060067</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
GetSessionInfo는 이제 API를 사용하는 익명의 사용자가 있을 때 개인 룸에 대한 기본 정보만 반환함
보안을 더욱 강화하기 위해 API를 사용하는 익명의 참석자가 있을 때 GetSessionInfo에서 반환하는 정보의 양을 줄이고 있습니다. 이번 업데이트에서 API 응답에 대해 다음 요소를 줄이게 됩니다.
적용되는 API:
-
GetSessionInfo-
<ep:accessControl>
-
-
<ep:sessionPassword>-
<ep:telephony> -
<ep:isAlternateHost>…</ep:isAlternateHost> -
<ep:isCreator>…</ep:isCreator> -
<ep:hostKey>…</ep:hostKey> -
<ep:supportE2E>…</ep:supportE2E>
-
응답 비교:
<serv:bodyContent xsi:type="ep:getSessionInfoResponse" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ep:status>NOT_INPROGRESS</ep:status>
<ep:isLocked>false</ep:isLocked>
<ep:sessionkey>712419789</ep:sessionkey>
<ep:confID>120396209273701973</ep:confID>
<ep:accessControl>
<ep:sessionPassword></ep:sessionPassword> <!--Removed-->
<ep:listStatus>UNLISTED</ep:listStatus>
<ep:registration>false</ep:registration>
<ep:passwordReq>false</ep:passwordReq>
<ep:isEnforceAudioPassword>false</ep:isEnforceAudioPassword>
<ep:isEnforceAudioLogin>false</ep:isEnforceAudioLogin>
</ep:accessControl>
<ep:metaData>
<ep:confName>Simon Test's Personal Room</ep:confName>
<ep:sessionType>3</ep:sessionType>
<ep:serviceType>MeetingCenter</ep:serviceType>
<ep:isRecurring>false</ep:isRecurring>
<ep:agendaFormat>TEXT</ep:agendaFormat>
<ep:descriptionFormat>TEXT</ep:descriptionFormat>
<ep:isException>false</ep:isException>
<ep:seriesMeetingKey>0</ep:seriesMeetingKey>
<ep:hasException>false</ep:hasException>
</ep:metaData>
<ep:telephony> <!--Removed-->
<ep:telephonySupport>CALLBACK</ep:telephonySupport> <!--Removed-->
<ep:globalCallInNumbersURL>https://sqdemo6.dmz.webex.com/sqdemo6/globalcallin.php?serviceType=MC&ED=0</ep:globalCallInNumbersURL>
<!--Removed-->
<ep:tollFreeRestrictionsURL>https://www.webex.com/pdf/tollfree_restrictions.pdf</ep:tollFreeRestrictionsURL> <!--Removed-->
<ep:dialInSequences>AutoDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[AttendeeID]#|SilentDialInSequence:[AccessNumber],,*01*[AccessCode]#[AttendeeID]#*01*|AutoLGDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[ProfileID]#,,,[PIN]#|SilentLGDialInSequence:[AccessNumber],,*01*[AccessCode]#[ProfileID]#[PIN]#*01*|AutoLGPWDialInSequence:[AccessNumber],,*00*[AccessCode]#,,,[ProfileID]#,,,[PIN]#,,,[Password]#|SilentLGPWDialInSequence:[AccessNumber],,*01*[AccessCode]#[ProfileID]#[PIN]#[Password]#*01*</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>false</serv:tollFree> <!--Removed-->
<serv:default>false</serv:default> <!--Removed-->
</serv:globalNum> <!--Removed-->
</ep:callInNum> <!--Removed-->
<ep:labels> <!--Removed-->
<ep:tollFreeCallInLabel>발신 무료 전화 번호 (미국/캐나다)</ep:tollFreeCallInLabel> <!--Removed-->
<ep:tollCallInLabel>14085452910</ep:tollCallInLabel> <!--Removed-->
</ep:labels> <!--Removed-->
<ep:isMPAudio>false</ep:isMPAudio> <!--Removed-->
<ep:voip>true</ep:voip> <!--Removed-->
<ep:enableTSP>false</ep:enableTSP> <!--Removed-->
</ep:telephony> <!--Removed-->
<ep:host>
<ep:firstName>Simon</ep:firstName>
<ep:lastName>Test</ep:lastName>
<ep:email>simon0@qa.webex.com</ep:email>
<ep:webExId>Simon</ep:webExId>
<ep:allowAnyoneHostMeeting>false</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, Pacific (San Francisco)</ep:timeZone>
<ep:timeZoneID>4</ep:timeZoneID>
<ep:openTimeInSec>0</ep:openTimeInSec>
</ep:schedule>
<ep:attendeeOptions>
<ep:joinRequiresAccount>false</ep:joinRequiresAccount>
</ep:attendeeOptions>
<ep:isAudioOnly>false</ep:isAudioOnly>
<ep:telePresence>false</ep:telePresence>
<ep:isAlternateHost>false</ep:isAlternateHost> <!--Removed-->
<ep:isCreator>true</ep:isCreator> <!--Removed-->
<ep:hostKey>954462</ep:hostKey> <!--Removed-->
<ep:supportE2E>false</ep:supportE2E> <!--Removed-->
<ep:isAllowJBH>false</ep:isAllowJBH>
<ep:isCETMeeting>true</ep:isCETMeeting>
<ep:isPersonalMeetingRoom>true</ep:isPersonalMeetingRoom>
<ep:isNextUpcomingInstance>true</ep:isNextUpcomingInstance>
<ep:meetingLink>https://sqdemo6.dmz.webex.com/sqdemo6/j.php?MTID=m424620ac1c117e156d97665b455192ed</ep:meetingLink>
<ep:sipURL>simon0@sqdemo6.dmz.webex.com</ep:sipURL>
<ep:displayMeetingUrl>simon0@sqdemo6.dmz.webex.com</ep:displayMeetingUrl>
<ep:isAutoRecord>false</ep:isAutoRecord>
</serv:bodyContent>
XML API 39.2.0 업데이트
새로운 요소 lastLoginTime이 LstSummaryUser 응답에서 반환됨
새로운 응답 요소인 lastLoginTime이 LstSummaryUser API에 추가되었습니다. lastLoginTime은 각 사용자에 대해 마지막 로그인 시간을 반환합니다. 요소는 다음 형식으로 반환됩니다.
<lastLoginTime>04/12/2018 22:40:01**</lastLoginTime>
적용되는 API:
-
LstSummaryUser-
lastLoginTime
-
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</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>DEACTIVATED</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>
XML API 39.1.0 업데이트
새로운 요소 apiVer이 GetAPIVersion API에 추가됨
새로운 응답 요소인 apiVer이 GetAPIVersion API에 추가되었습니다. 이번 업데이트에서 XML API 버전 이름 설정 형식이 다른 Cisco Webex 제품 영역에 통합된 버전 번호와 일치하도록 변경됩니다. apiVer 요소는 2019년 1월 업데이트에서 39.1.0과 같은 새로운 버전 정보를 반환합니다.
적용되는 API:
-
GetAPIVersion-
apiVer
-
2019년 5월 1일에 apiVersion 요소는 제거될 예정이며, 2019년 5월 1일에 release 요소에는 새로운 XML API 값이 지정됩니다.
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ep:getAPIVersionResponse">
<ep:apiVersion>Webex XML API V11.0.0</ep:apiVersion>
<ep:release>SP22</ep:release>
<ep:apiVer>39.1.0</ep:apiVer>
</serv:bodyContent>
</serv:body>
</serv:message>
XML API에서 HQ 및 HD 파라미터 제거됨
이제 HQ 및 HD 비디오 등록 정보는 사용자 수준에서 결정되는 대신, 사이트 수준에서 결정됩니다. 다음 API에서 요청을 발송할 때 다음 파라미터에 대한 두 가지 옵션은 무시됩니다.
-
CreateMeeting -
SetMeeting -
CreateTrainingSession -
SetTrainingSession
GetMeeting 및 GetTrainingSession API는 기존의 코드를 해독하는 것을 피하기 위해 여전히 두 개의 옵션(사이트 수준 및 사용자 수준에서 결정됨)을 반환합니다.
새로운 요소 uploadLogFileUrl이 데스크탑 앱에 반환되는 사이트 메타데이터에 추가됨
새로운 요소 uploadLogFileUrl이 XML API 서버에서 getSite API로 전화할 때 데스크탑 앱으로 반환되는 응답에 추가되었습니다. 데스크탑 앱은 uploadLogFileUrl에 로그 파일을 업로드할 수 있습니다.
적용되는 API:
-
GetSite-
uploadLogFileUrl
-
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&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>
XML API 11.0.0 SP22 업데이트
UploadPMRImage에 대한 파일 크기 제한
API UploadPMRImage를 사용하여 아바타를 업로드할 때 새로운 제한 사항은 파일 크기를 5MB로 제한합니다. 이제 이보다 더 큰 파일을 업로드하려고 시도하면 다음 오류 메시지를 수신하게 됩니다. "010100 업로드되고 있는 이미지의 크기가 너무 큽니다. 5MB보다 작은 크기의 이미지를 시도하십시오."
XML API 11.0.0 SP21 업데이트
새로운 요소 autoRecord가 CreateMeeting, SetMeeting, GetMeeting 및 LstMeeting에 추가됨
autoRecord라고 칭하는 새로운 요소가 CreateMeeting, SetMeeting, GetMeeting 및 LstMeeting API에 추가되었습니다. autoRecord를 통해 사용자는 미팅 스케줄러에서 Webex Meetings을 직접 자동으로 녹화할 수 있습니다. 이는 미팅 수준의 세분성을 제공하며, 미팅을 자동으로 녹화하는 이전의 방법은 사이트 수준에서 글로벌로만 액세스할 수 있습니다.
|
|
적용되는 API:
-
CreateMeeting-
autoRecord
-
-
SetMeeting-
autoRecord
-
-
GetMeeting-
autoRecord
-
-
LstMeeting-
autoRecord
-
CreateMeeting 업데이트:
|
|
사이트 관리에서 네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화 옵션이 비활성화된 경우의 작동 |
|---|---|
|
|
미팅이 시작할 때 자동으로 녹화를 시작 |
|
|
미팅이 시작할 때 자동으로 녹화를 시작하지 않음 |
|
네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화가 활성화된 경우, 요소는 무시되고 미팅이 시작할 때 녹화가 자동으로 시작됩니다. |
SetMeeting 업데이트:
|
|
사이트 관리에서 네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화 옵션이 비활성화된 경우의 작동 |
|---|---|
|
|
미팅이 시작할 때 자동으로 녹화를 시작 |
|
|
미팅이 시작할 때 자동으로 녹화를 시작하지 않음 |
|
네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화가 활성화된 경우, 요소는 무시되고 미팅이 시작할 때 녹화가 자동으로 시작됩니다. |
GetMeeting 업데이트:
|
|
사이트 관리에서 네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화 옵션이 비활성화된 경우의 작동 |
|---|---|
|
|
미팅이 시작할 때 자동으로 녹화를 시작 |
|
|
미팅이 시작할 때 자동으로 녹화를 시작하지 않음 |
|
네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화가 활성화된 경우, 요소는 무시되고 미팅이 시작할 때 녹화가 자동으로 시작됩니다. |
GetMeeting 응답 예제:
LstMeeting 업데이트:
|
|
사이트 관리에서 네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화 옵션이 비활성화된 경우의 작동 |
|---|---|
|
|
미팅이 시작할 때 자동으로 녹화를 시작 |
|
|
미팅이 시작할 때 자동으로 녹화를 시작하지 않음 |
|
네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화가 활성화된 경우, 요소는 무시되고 미팅이 시작할 때 녹화가 자동으로 시작됩니다. |
LstMeeting 응답 예제:
새로운 요소 isAutoRecord가 GetSessionInfo API에 추가됨
상단의 API에 적용된 변경 사항과 함께 새로운 요소인 isAutoRecord가 GetSessionInfo API에 추가되었습니다. 이 요소는 미팅이 시작할 때 녹화가 자동으로 시작되는지 표시하기 위해 사용될 수 있습니다.
적용되는 API:
-
GetSessionInfo-
isAutoRecord
-
GetSessionInfo 업데이트:
|
|
사이트 관리에서 네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화 옵션이 비활성화된 경우의 작동 |
|---|---|
|
|
미팅이 시작할 때 자동으로 녹화를 시작 |
|
|
미팅이 시작할 때 자동으로 녹화를 시작하지 않음 |
|
네트워크 기반 녹화를 사용하여 모든 세션을 자동으로 녹화가 활성화된 경우, 요소는 무시되고 미팅이 시작할 때 녹화가 자동으로 시작됩니다. |
GetSessionInfo 응답 예제:
XML API 11.0.0 SP20 업데이트
새로운 요소 returnShareToMeRecording이 LstRecording API 요청에 추가됨
|
이 변경 사항은 이전에 XML API 11.0 SP17에서 공지되었지만, 이번 업데이트에 적용됩니다. |
새로운 요소인 returnShareToMeRecording이 LstRecording API에 추가되었습니다. returnShareToMeRecording은 LstRecording에 대한 요청에서 부울입니다.
참석자 또는 초대받은 사람 녹화를 찾을 수 있도록 지원하기 위해 이 새로운 요소가 추가되었습니다. returnShareToMeRecording은 LstRecording API에서 참석자 또는 초대받은 사람 녹화를 반환해야 함을 알리는 플래그입니다.
returnShareToMeRecording이 True로 설정되는 경우, LstRecording은 녹화 사용자를 소유자로 반환하고, 녹화 사용자를 참석자 또는 소유자가 공유한 초대받은 사람으로 반환합니다.
|
자동 공유 및 수동 공유 플래그가 모두 |
returnShareToMeRecording이 False로 설정되었거나, 이 요소가 요청에 포함되지 않은 경우, LstRecording은 이전과 동일한 논리를 따릅니다. 녹화 사용자를 소유자로 반환합니다.
적용되는 API:
-
LstRecording-
returnShareToMeRecording
-
LstRecording 업데이트:
요소 shareToMe가 LstRecording API 응답에 추가됨
|
이 변경 사항은 이전에 XML API 11.0 SP17에서 공지되었지만, 이번 업데이트에 적용됩니다. |
새로운 요소인 shareToMe가 LstRecording API에 추가되었습니다. shareToMe는 LstRecording에 대한 응답에서 부울입니다.
참석자 또는 초대받은 사람 녹화를 찾을 수 있도록 지원하기 위해 이 새로운 요소가 추가되었습니다. shareToMe는 현재 녹화에 대해 사용자가 소유자 또는 참석자인지를 정의하는 플래그입니다.
shareToMe가 True일 때 사용자는 현재 녹화의 소유자가 아닙니다. 사용자는 참석자이거나, 소유자가 녹화를 공유했을 수 있습니다.
shareToMe가 False이거나, 이 요소가 응답에 있지 않은 경우, LstRecording은 이전과 동일한 논리를 따릅니다. 사용자는 현재 녹화의 소유자입니다.
적용되는 API:
-
LstRecording-
shareToMe
-
LstRecording 업데이트:
returnShareToMeRecording 및 shareToMe 요청 예제:
<bodyContent xsi:type=”java.com.webex.service.binding..ep.LstRecording”>
<hostWebExID>auto243</hostWebExID>
<createTimeScope>
<createTimeStart>08/15/2018 8:0:0</createTimeStart>
<createTimeEnd>09/05/2018 7:59:59</createTimeEnd>
<timeZoneID>20</timeZoneID>
</createTimeScope>
<serviceTypes>
<serviceType>MeetingCenter</serviceType>
<serviceType>EventCenter</serviceType>
<serviceType>TrainingCenter</serviceType>
</serviceTypes>
<returnShareToMeRecording>true</returnShareToMeRecording>
</bodyContent>
returnShareToMeRecording 및 shareToMe 응답 예제:
새로운 요소가 GetEvent API에 추가됨
네 개의 새로운 요소가 GetEvent API에 추가됨:
-
isCETMeeting: Webex 이벤트가 Webex 비디오 플랫폼 2(CMR 4.0)를 지원하는지를 가리키는 부울 True/False -
sipURL: 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 참여하기 위해 사용되는 URL -
standaloneDialingIPAddress: 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 다이얼하기 위해 사용할 수 있는 IP 주소 -
panelistNumericPassword: 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 참여하기 위한 비밀번호
사이트에서 Webex 비디오를 지원하고, 호스트에게 Webex Events 비디오 권한이 있으며, 이벤트에서 Webex 비디오 플랫폼 2 (CMR 4.0)를 지원하는 경우, GetEvent 값은 해당하는 요소를 반환합니다. 그렇지 않으면 GetEvent은 해당 값을 반환하지 않습니다.
적용되는 API:
-
GetEvent-
isCETMeeting -
sipURL -
standaloneDialingIPAddress -
panelistNumericPassword
-
새로운 요소 panelistNumericPassword가 GetSessionInfo API에 추가됨
GetSessionInfo에 새로운 요소인 panelistNumericPassword가 추가되었으며, 여기에는 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 참여하기 위한 비밀번호가 포함됩니다.
사이트에서 Webex 비디오를 지원하고, 호스트에게 Webex Events 비디오 권한이 있으며, 이벤트에서 Webex 비디오 플랫폼 2 (CMR 4.0)를 지원하는 경우, GetSessionInfo 값은 다음과 같은 네 개의 요소를 반환합니다.
-
isCETMeeting: Webex 이벤트가 Webex 비디오 플랫폼 2(CMR 4.0)를 지원하는지를 가리키는 부울 True/False -
sipURL: 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 참여하기 위해 사용되는 URL -
standaloneDialingIPAddress: 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 다이얼하기 위해 사용할 수 있는 IP 주소 -
panelistNumericPassword: 비디오 회의 시스템 또는 응용프로그램에서 Webex 비디오 미팅에 참여하기 위한 비밀번호
|
Webex Meetings에 대해 다음 요소는
|
적용되는 API:
-
GetSessionInfo-
panelistNumericPassword
-
GetEvent 및 GetSessionInfo에 적용된 스키마 변경
GetEvent 업데이트:
GetSessionInfo 업데이트:
XML API 11.0.0 SP18 업데이트
새로운 요소 EnableCloudTelepresence가 getSite API에 추가됨
새로운 요소인 EnableCloudTelepresence가 getSite API에 추가되었습니다.
옵션 EnableCETForAllUsers가 활성화되면 Webex는 사용자가 Webex 비디오(CMR)를 지원하는지 확인합니다. 이는 이제 getSite API에서 새로운 요소 EnableCloudTelepresence도 반환합니다.
적용되는 API:
-
getSite -
EnableCloudTelepresence
getSite 예제 응답:
XML API 11.0.0 SP17 업데이트
새로운 요소 returnShareToMeRecording이 LstRecording API 요청에 추가됨
새로운 요소인 returnShareToMeRecording이 LstRecording API에 추가되었습니다. returnShareToMeRecording은 LstRecording에 대한 요청에서 부울입니다.
참석자 또는 초대받은 사람 녹화를 불러오도록 지원하기 위해 이 새로운 요소가 추가되었습니다. returnShareToMeRecording은 LstRecording API에서 참석자 또는 초대받은 사람 녹화를 반환해야 함을 알리는 플래그입니다.
returnShareToMeRecording이 True로 설정되는 경우, LstRecording은 녹화 사용자를 소유자로 반환하고, 녹화 사용자를 참석자 또는 소유자가 공유한 초대받은 사람으로 반환합니다.
|
자동 공유 및 수동 공유 플래그가 비활성화된 경우, |
returnShareToMeRecording이 False로 설정되었거나, 이 요소가 요청에 포함되지 않은 경우, LstRecording은 이전과 동일한 논리를 따릅니다. 녹화 사용자를 소유자로 반환합니다.
적용되는 API:
-
LstRecording -
returnShareToMeRecording
LstRecording 업데이트:
새로운 요소 shareToMe가 LstRecording API 응답에 추가됨
새로운 요소인 shareToMe가 LstRecording API에 추가되었습니다. shareToMe는 LstRecording에 대한 응답에서 부울입니다.
참석자 또는 초대받은 사람 녹화를 불러오도록 지원하기 위해 이 새로운 요소가 추가되었습니다. shareToMe는 현재 녹화에 대해 사용자가 소유자, 참석자 또는 초대받은 사람인지를 정의하는 플래그입니다.
shareToMe가 True일 때 사용자는 현재 녹화의 소유자가 아닙니다. 사용자는 참석자 또는 초대받은 사람이거나, 소유자가 녹화를 공유했을 수 있습니다.
shareToMe가 False이거나, 이 요소가 응답에 있지 않은 경우, LstRecording은 이전과 동일한 논리를 따릅니다. 사용자는 현재 녹화의 소유자입니다.
적용되는 API:
-
LstRecording -
shareToMe
LstRecording 업데이트:
참석자 기능에 대해 새로운 요소가 API getSite 응답에 추가됨
네 개의 새로운 요소가 getSite API에 추가되어 다음 Webex 서비스에 대해 참석자 기능을 표시합니다.
attendeeCapacityForMC - Webex Meetings
attendeeCapacityForEC – Webex Events
attendeeCapacityForTC – Webex Training
attendeeCapacityForSC – Webex Support
해당 요소는 미팅, 이벤트 또는 세션에서 포함할 수 있는 최대 참석자의 수를 표시하는 값을 반환합니다. 이는 응답에서 CISiteLicenseInfo의 하위 요소입니다.
적용되는 API:
-
getSite -
attendeeCapacityForMC -
attendeeCapacityForEC -
attendeeCapacityForTC -
attendeeCapacityForSC
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
<ns1:siteInstance> ... ... <ns1:CISiteLicenseInfo>
<ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
<ns1:allowOverageForMC>false</ns1:allowOverageForMC>
<ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
<ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
<ns1:allowOverageForTC>false</ns1:allowOverageForTC>
<ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
<ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
<ns1:allowOverageForEC>false</ns1:allowOverageForEC>
<ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
<ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
<ns1:allowOverageForSC>false</ns1:allowOverageForSC>
<ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
<ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
<ns1:allowOverageForCMRHost>false</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>
XML API 11.0.0 SP16 업데이트
새로운 API hostStreamURL가 lstRecordingResponse에 추가됨
요소 hostStreamURL이 녹화 세부 사항의 일부로 LstRecording 응답에 추가되었습니다. hostStreamURL은 호스트가 먼저 로그인하지 않고 녹화를 보기 위해 사용할 수 있는 URL을 반환합니다. 이 URL은 생성된 후 30분 동안 유효합니다.
적용되는 API:
-
hostStreamURL
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"/>
GetSite API는 데이터를 반환하기 위해 새로운 WebDB 모델링을 사용함
고객의 요청에 따라 이제 API GetSite는 CI 사이트에 대해 새로운 WebDB 모델링을 사용하여 더욱 정확한 호스트 라이센스, 사용 보고서 데이터 및 기타 데이터를 검색합니다.
적용되는 API:
-
GetSite
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
<ns1:siteInstance> ... ... <ns1:CISiteLicenseInfo>
<ns1:accountNumberLimitForMC>999</ns1:accountNumberLimitForMC>
<ns1:allowOverageForMC>false</ns1:allowOverageForMC>
<ns1:accountNumberUsedForMC>43</ns1:accountNumberUsedForMC>
<ns1:accountNumberLimitForTC>999</ns1:accountNumberLimitForTC>
<ns1:allowOverageForTC>false</ns1:allowOverageForTC>
<ns1:accountNumberUsedForTC>44</ns1:accountNumberUsedForTC>
<ns1:accountNumberLimitForEC>999</ns1:accountNumberLimitForEC>
<ns1:allowOverageForEC>false</ns1:allowOverageForEC>
<ns1:accountNumberUsedForEC>22</ns1:accountNumberUsedForEC>
<ns1:accountNumberLimitForSC>999999</ns1:accountNumberLimitForSC>
<ns1:allowOverageForSC>false</ns1:allowOverageForSC>
<ns1:accountNumberUsedForSC>13</ns1:accountNumberUsedForSC>
<ns1:accountNumberLimitForCMRHost>999999</ns1:accountNumberLimitForCMRHost>
<ns1:allowOverageForCMRHost>false</ns1:allowOverageForCMRHost>
<ns1:accountNumberUsedForCMRHost>4</ns1:accountNumberUsedForCMRHost>
</ns1:CISiteLicenseInfo>
</ns1:siteInstance>
</serv:bodyContent>
</serv:body>
</serv:message>
GetSite 응답 예제 (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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns1:getSiteResponse">
<ns1:siteInstance> ... ... <ns1:CISiteLicenseInfo>
<ns1:accountNumberLimitForCMRHost>80</ns1:accountNumberLimitForCMRHost>
<ns1:allowOverageForCMRHost>true</ns1:allowOverageForCMRHost>
<ns1:accountNumberUsedForCMRHost>99</ns1:accountNumberUsedForCMRHost>
<ns1:accountNumberLimitForEEHost>999999</ns1:accountNumberLimitForEEHost>
<ns1:allowOverageForEEHost>false</ns1:allowOverageForEEHost>
<ns1:accountNumberUsedForEEHost>368</ns1:accountNumberUsedForEEHost>
</ns1:CISiteLicenseInfo>
</ns1:siteInstance>
</serv:bodyContent>
</serv:body>
</serv:message>
XML API 11.0.0 SP15 업데이트
GetSessionsInfo API를 사용하여 Webex Meetings 미팅 링크 반환
GetSessionInfo API에 대한 스키마에 새로운 반환 값 meetingLink가 있습니다. 미팅 링크를 사용하여 호스트로서 Webex 미팅을 시작하거나, 참석자로서 Webex 미팅에 참여할 수 있습니다.
적용되는 API:
-
GetSessionInfo -
meetingLink
GetSessionInfo 응답 예제:
<ep:meetingLink>https://hmwds6.qa.webex.com/hmwds6/j.php?MTID=m265e64705c6660d4132c2d4f19aed7e7</ep:meetingLink>
</serv:bodyContent>
LstRecording API에서 RecordingID에 따른 쿼리에 대한 새로운 조건
이제 recordingID를 사용하여 녹화를 쿼리하기 위해 LstRecording을 사용할 수 있습니다. 여기에는 다음과 같은 두 가지 유형의 녹화 ID가 있습니다.
-
Webex Meetings, Webex Events 및 Webex Training에 대한 녹화 ID
-
기타 녹화에 대한 NBR 녹화 ID
XML 요청에 serviceType 요소가 있는 경우, LstRecording은 서비스 녹화(Webex Meetings, Webex Events 및 Webex Training)만 반환합니다.
XML 요청에 serviceType 요소가 없는 경우, LstRecording은 NBR 녹화만 반환합니다.
적용되는 API:
-
LstRecording -
녹화ID
LstRecording 응답 예제:
서비스 녹화 ID에 대한 요청 예제:
<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>
NBR 녹화 ID에 대한 요청 예제:
<bodyContent xsi:type="java:com.webex.service.binding.ep.LstRecording">
<recordingID>974154032</recordingID>
<order>
<orderBy>CREATETIME</orderBy>
<orderAD>DESC</orderAD>
<orderBy>HOSTID</orderBy>
<orderAD>ASC</orderAD>
<orderBy>RECORDNAME</orderBy>
<orderAD>ASC</orderAD>
</order>
</bodyContent>
XML API 11.0.0 SP14 업데이트
Meeting Center에 대해 예비 사용 요약 보고서
두 개의 새로운 API가 Meeting Center 예비 보고서, LstmeetingusagePreliminaryHistory 및 LstmeetingattendeePreliminaryHistory에 추가되었습니다. 해당 API는 최종 보고서에서 LsteventsessionPreliminaryHistory 및 LsteventattendeePreliminaryHistory와 동일하게 작동합니다.
적용되는 API:
-
LstmeetingusagePreliminaryHistory -
LstmeetingattendeePreliminaryHistory
LstmeetingusagePreliminaryHistory 요청 예제:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
http://www.webex.com/schemas/2002/06/service/service.xsd">
<header>
<securityContext>
<webExID>testuser</webExID>
<password>****</password>
<siteName>testsite</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingusagePreliminaryHistory">
<startTimeScope>
<sessionStartTimeStart>4/23/2018 00:00:00</sessionStartTimeStart>
<sessionStartTimeEnd>4/24/2018 11:59:59</sessionStartTimeEnd>
</startTimeScope>
<listControl>
<startFrom>1</startFrom>
<maximumNum>10</maximumNum>
<listMethod>AND</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>
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingusagePreliminaryHistoryResponse">
<history:meetingUsagePreliminaryHistory>
<history:confID>93115261364733685</history:confID>
<history:sessionKey>800150023</history:sessionKey>
<history:confName>200804231215</history:confName>
<history:openTime>04/23/2018 19:16:34</history:openTime>
<history:timeZoneID>4</history:timeZoneID>
<history:meetingType>PRO</history:meetingType>
<history:timeZoneWithDST>San Francisco (Pacific Daylight Time, 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>
LstmeetingattendeePreliminaryHistory 요청 예제:
<?xml version="1.0" encoding="UTF-8"?>
<serv:message
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service"
xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
http://www.webex.com/schemas/2002/06/service/service.xsd">
<header>
<securityContext>
<webExID>testuser</webExID>
<password>****</password>
<siteName>testsite</siteName>
</securityContext>
</header>
<body>
<bodyContent xsi:type="java:com.webex.service.binding.history.LstmeetingattendeePreliminaryHistory">
<startTimeScope>
<sessionStartTimeStart>4/23/2018 00:00:00</sessionStartTimeStart>
<sessionStartTimeEnd>4/24/2018 11:59:59</sessionStartTimeEnd>
</startTimeScope>
<listControl>
<startFrom>1</startFrom>
<maximumNum>10</maximumNum>
<listMethod>AND</listMethod>
</listControl>
<order>
<orderBy>STARTTIME</orderBy>
<orderAD>ASC</orderAD>
<orderBy>CONFID</orderBy>
<orderAD>ASC</orderAD>
</order>
</bodyContent>
</body>
</serv:message>
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="history:lstmeetingattendeePreliminaryHistoryResponse">
<history:meetingAttendeePreliminaryHistory>
<history:meetingKey>800150023</history:meetingKey>
<history:confName>200804231215</history:confName>
<history:company>XYZ</history:company>
<history:title>DJ</history:title>
<history:phoneNumber>1,222,654-3210,,,,</history:phoneNumber>
<history:address1>1 Any Street</history:address1>
<history:address2>xyz</history:address2>
<history:city>SanJose</history:city>
<history:state>CA</history:state>
<history:country>USA</history:country>
<history:zipCode>95111</history:zipCode>
<history:name>user test2</history:name>
<history:email>ut2@qa.webex.com</history:email>
<history:joinTime>04/23/2018 19:13:06</history:joinTime>
<history:participantType>ATTENDEE</history:participantType>
<history:confID>93115261364733685</history:confID>
</history:meetingAttendeePreliminaryHistory>
<history:meetingAttendeePreliminaryHistory>
<history:meetingKey>800150023</history:meetingKey>
<history:confName>200804231215</history:confName>
<history:name>zzz zzzz</history:name>
<history:email>z6@webex.com</history:email>
<history:joinTime>04/23/2018 19:14:10</history:joinTime>
<history:participantType>ATTENDEE</history:participantType>
<history:confID>93115261364733685</history:confID>
</history:meetingAttendeePreliminaryHistory>
<history:meetingAttendeePreliminaryHistory>
<history:meetingKey>800150023</history:meetingKey>
<history:confName>200804231215</history:confName>
<history:name>test host</history:name>
<history:email>testuser@webex.com</history:email>
<history:joinTime>04/23/2018 19:12:42</history:joinTime>
<history:participantType>ATTENDEE</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>
GLA GetsessionInfo API에서 SIP URL 및 Skype URL 반환
두 개의 새로운 요소인 <sipURL> 및 <skypeURL>이(가) GLA GetSessionInfo API에 전화할 때 응답에 첨부되었습니다. 해당하는 요소는 익명의 액세스에 대해 반환될 수 있는 기준 요소입니다.
-
<sipURL>은(는) TelePresence 또는 기타 Cisco video 장치에서 미팅에 참여하기 위해 사용할 수 있습니다. 이렇게 하면 Cisco 비디오 플랫폼 버전 1.0 또는 2.0을 사용하는 미팅에서만 GetSessionInfo가<sipURL>요소를 반환합니다. -
<skypeURL>은(는) 제한 사항 또는 조건 없이 Microsoft Skype 앱에서 미팅에 참여하기 위해 사용될 수 있기 때문에 각 전화에 대해 반환될 수 있습니다.
적용되는 API:
-
GetSessionInfo
응답 예:
GetMeeting API에서 SIP URL 및 미팅 링크 반환
세 개의 새로운 요소인 <isCETMeeting>, <meetingLink> 및 <sipURL>이(가) GetMeeting API에 전화할 때 응답에 첨부되었습니다.
-
<isCETMeeting>은(는) 미팅에서 Cisco 비디오 플랫폼(TelePresence 및 비디오 지원)을 사용하는지 여부를 반환합니다. -
<meetingLink>은(는) 미팅에 연결하기 위해 사용할 수 있습니다. -
<sipURL>은(는) TelePresence 또는 기타 Cisco video 장치에서 미팅에 참여하기 위해 사용할 수 있습니다. 이렇게 하면 Cisco 비디오 플랫폼 버전 1.0 또는 2.0을 사용하는 미팅에서만GetMeeting이 요소를 반환합니다.
적용되는 API:
-
GetMeeting
GetMeeting 응답 예제:
XML API 11.0.0 SP13 업데이트
상위 항목에서 <siteID> 요소의 제거 알림 <securityContext>
Cisco는 <siteID> 구성 요소를 상위 <securityContext> 요소에서 제거하고 <siteName>(으)로 대체할 계획입니다. 사이트 마이그레이션 중에 다수의 <siteID> 구성 요소가 자주 변경되기 때문에 조직에 대해 이 요소를 계속 사용하기 위한 유지 비용이 많이 발생합니다. 이는 실행하기 2년 전에 미리 알리는 알림입니다.
-
기존의 Webex 고객에게는 2020년 5월 1일에 영향을 미칩니다.
-
새로운 고객은
<siteName>구성 요소를 2018년 5월 1일부터 사용해야 합니다. -
CI, Spark 또는 Atlas 시스템에 통합을 실행하는 고객은
<siteName>구성 요소를 2018년 5월 1일부터 사용해야 합니다.
적용되는 API:
-
<siteName> -
<securityContext>
<tollCallInData> 및 <tollFreeCallInData> 요소의 데이터 유효성 검증
2018년 6월 1일부터 <tollCallInData> 및 <tollFreeCallInData> API 모두 데이터 유효성이 검증됩니다. 이는 <CreateUser> 및 <SetUser> API에 영향을 미칩니다.
발신 데이터에서 유효하지 않은 문자열 또는 부적합하게 형식화된 문자열을 사용하는 사이트는 해당 문자열을 수정하여 해당 요소가 데이터 유효성 검증을 통과하게 해야 합니다.
CreateUser 및 SetUser, tollCallInData 및 tollFreeCallInData의 올바른 형식에 대한 예제는 다음과 같습니다.
<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>false</createOnBridge>
<defaultFlag>false</defaultFlag>
</tspAccount>
</tspAccount> ...
XML API 11.0.0 SP12 업데이트
두 개의 새로운 API SetContact 및 DelContacts
이전에 XML API 스키마에는 두 개의 API CreateContacts 및 LstContacts만 있었으며, 이는 사용자 연락처의 완전한 관리를 제공하지 못했습니다. XML API를 사용하여 사용자 연락처를 관리할 때 더욱 향상된 기능을 제공하기 위해 다음 두 개의 새로운 API, SetContact 및 DelContacts를 추가했습니다.
|
API |
참고 |
|---|---|
|
|
이 API로 전화하여 이메일, 이름, 직위 및 언어 등 연락처 정보를 수정합니다. 예외:
|
|
|
지정된 이메일에 기반하여 내 연락처 목록에서 한 개 이상의 연락처를 삭제하려면 이 API로 전화합니다.
내 연락처 목록에서 지정된 모든 이메일을 찾을 수 없는 경우, 예외 00015(죄송합니다. 기록을 찾을 수 없음)가 반환됩니다. |
적용되는 API:
-
SetContact -
DelContacts
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>연락처 이메일 주소</contactEmail>
<contact>
<name>새 연락처 이름</name>
<email>새 연락처 이메일 주소</email>
<title>새 직위</title>
<company>새로운 회사</company>
<notes>새로운 메모</notes>
<url>새로운 링크</url>
<phones>
<phone>1,,408######,,,,</phone>
<mobilePhone>1,,408######,,,,</mobilePhone>
<fax>1,,408######,,,,</fax>
</phones>
<address>
<address1>새로운 주소 1</address1>
<address2>새로운 주소 2</address2>
<city>새로운 도시</city>
<state>새로운 주/도</state>
<zipCode>새로운 우편 번호</zipCode>
<country>새로운 회사</country>
</address>
<language>새 언어</language>
</contact>
</bodyContent>
</body>
</serv:message>
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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</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>
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>
DelContacts 응답 예제:
|
이 예제에서는 기존의 두 개의 연락처가 내 연락처 목록에서 삭제됩니다. |
<?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>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</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>
|
이 예제에서는 이메일이 내 연락처 목록에 존재하지 않습니다. |
<?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>FAILURE</serv:result>
<serv:reason>Sorry, no record found</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>000015</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
XML API 11.0.0 SP11 업데이트
새로운 API LstTrainingPollResultsHistory
LstTrainingPollResultsHistory API는 원래 URL API에서 실행되었습니다. 고객의 요청으로 이는 이제 XML API에서 실행됩니다.
Training Center sessionKey를 입력하면 설문조사 목록 결과가 반환됩니다. API는 Training Center 세션 소유자 또는 사이트 관리자가 요청할 수 있습니다.
|
Webex DB에서 교육 설문조사 결과가 저장되기 전에 강화된 TC 설문조사 설정이 활성화되어야 합니다.
|
적용되는 API:
-
LstTrainingPollResultsHistory
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>
|
해당 요청은 T32/XML API 11.0.0에만 해당합니다. |
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>
미팅을 찾을 수 없는 경우, 미팅이 요청하는 사용자에게 속하지 않은 경우, 요청하는 사용자가 사이트 관리자가 아닌 경우에 응답은 달라집니다.
응답 예:
<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>FAILURE</serv:result>
<serv:reason>Sorry, no record found</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>000015</serv:exceptionID>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent/>
</serv:body>
</serv:message>
API CreateTrainingSession, SetTrainingSession 및 GetTrainingSession에 있는 새로운 attendeeSendVideo 옵션
Training Center 세션을 예약할 때 사용할 수 있는 옵션에 비디오 보내기가 포함되기 때문에 이제 XML API는 attendeeSendVideo 옵션을 추가하여 Training Center 세션에 대한 API를 만들고, 확보, 설정합니다.
적용되는 API:
-
CreateTrainingSession -
SetTrainingSession -
GetTrainingSession
디자인
옵션은 DB 표 WbxMMConfParam/paramvalue as paramname = 'optionSupportSendVideo'에 저장되었습니다.
CreateTrainingSession 요청 업데이트:
SetTrainingSession 요청 업데이트:
|
해당 요청은 T32/XML API11.0.0에만 해당합니다. |
GetTrainingSession 응답 업데이트:
ConfName 크기 제한 최대값을 128 표시 문자로 변경
회의 이름 문자열 ConfName은 이제 최대 128 표시 문자로 제한됩니다. 이 변경 사항은 J2EE 홈 페이지 제한 사항과 맞춥니다. API 요청에 비어 있거나 128 표시 문자 길이를 초과하는 ConfName이 포함되는 경우, 다음 오류 메시지가 표시됩니다.
"060065 올바르지 않은 입력 회의 이름. 회의 이름은 비어 있거나, 최대 표시 문자 길이인 128자를 초과할 수 없습니다."
적용되는 API:
-
ConfName
API LstRecording에서 예외 메시지가 변경됨
쿼리 시간 범위가 API LstRecording에서 최대 제한을 초과할 때 나타나는 예외 메시지가 변경되었습니다. 기본값으로 쿼리는 4주의 녹화를 지원합니다. 요청이 4주를 넘기면 다음 오류 메시지를 수신합니다.
"999999 28일의 최대 쿼리 시간 범위가 초과됨"
적용되는 API:
-
LstRecording
XML API 11.0.0 SP10 업데이트
XML API 11.0 SP10 업데이트에 스키마 변경 사항이 포함되지 않습니다.
Join the conversation
