TMSXE OBTP > UCCapabilities attribut documentation

[Salim_Guerid]

Hello,

Is there any documentation around the UCCapabilities attribut used by TMSXE to identify that a meeting is UC-enabled and therefore triggers the OBTP feature? I noticed under the reference here that the below content is generated but have found no documentation on how to set the right values (mandatory vs optional, accepted value) for the various fields.

<?xml version="1.0" encoding="UTF-8"?>
<CiscoOI>
   <PTVersion>310000</PTVersion>
   <PTReleaseVersion>31.5.1.60</PTReleaseVersion>
   <OIVersion>
   <CreatorOS>Windows</CreatorOS>
   <ClientOS>Windows</ClientOS>
   </OIVersion>
   <PTFeatureConfig>1</PTFeatureConfig>
   <ExternalSIPUrl>'.$dest_uri.'</ExternalSIPUrl>
   <WebExOI>BLABLA</WebExOI>
  <WebExSegmentID>PHNlZz48dHlwZT5ib29rbWFyazwvdHlwZT48cGF0dGVybj48Y2F0ZWdvcnk+cGxhaW5UZXh0PC9jYXRlZ29yeT48bmFtZT5XQlg2RjUxRTwvbmFtZT48dmVyaWZ5Q29kZT44MTE4MDwvdmVyaWZ5Q29kZT48L3BhdHRlcm4+PC9zZWc+DQoAAA==</WebExSegmentID>
   <WebEx>
   <Product>
   <Major>Train</Major>
   <Minor>T29</Minor>
   <SP>8</SP>
   <EP />
   <OtherFlag />
   </Product>
   <MeetingInfo>
   <site>acecloud.webex.com</site>
   <brandName>acecloud</brandName>
   <LoginName>gubraux</LoginName>
   <LoginAccount>userEmail@cisco.com</LoginAccount>
   <HostName>gubraux</HostName>
   <HostAccount>userEmail@cisco.com</HostAccount>
   <HostID>488092317</HostID>
   <svcType>MC</svcType>
   <MeetingKey>201430513</MeetingKey>
   <audioType>2</audioType>
   <meetingType>3</meetingType>
   <meetingTemplateKey>S;MC;en_US;9.1;1445782;MC Default;D; ;</meetingTemplateKey>
   <EmailBody>
   <Version>1</Version>
   <TagDataLength>100</TagDataLength>
   <BeginTag />
   <EndTag />
   </EmailBody>
   </MeetingInfo>
   </WebEx>
   <WebExPMR>AAA=</WebExPMR>
</CiscoOI>

[ronlewis]

We don't document this, no....the UCC field can be used by MSFT and/or Webex PT client to insert the URI for a cloud meeting. If a cloud CMR customer, scheduling with Productivity Tool (PT), PT client inserts the mtg URI.

XE will then pick this up and sets meeting to be externally hosted.

An Outlook user would not have visibility or method to set this themselves.

What are you trying to do?

Ron Lewis

Cisco

[Salim_Guerid]

Hi Ron,

We have developed an Add-In which allows user to provision CMS conference from Outlook and have implemented the OBTP feature using TMS API for the time being. We would like now to propose the feature for TMSXE customer and therefore need to get those parameters set with the right values under a CMS context.