Guest

Preview Tool

Cisco Bug: CSCvi66395 - TMS Booking API object attributes noted as optional are required

Last Modified

Aug 02, 2018

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases

15.6.1

Description (partial)

Symptom:
There are a number of object attributes that are noted in the current documentation as being optional or deprecated, but are still actually required when saving a conference through the TMS Booking API.
Cisco TelePresence Management Suite Extension Booking API Programming Reference Guide for Cisco TMS 15.6 is used as reference for all details below.

Object : Conference

Attribute : ConferenceType

The documentation states "If unspecified, the default conference type configured in Cisco TMS will be used" and is tagged as "optional."
It has been found that if this attribute is not included when saving conference, the ConferenceType of "Reservation Only" is being used, even though the default setting for confereces in TMS is set to One Button to Push.

Attribute : Bandwidth

This attribute is noted as "discontinued", and is noted to use "ISDNBandwidth" and "IPBandwidth". Even with the addition of these attributes, the faultstring of "Unrecognized bandwidth: 0" will be returned by the TMSBAPI.

Attribute : Encrypted

This attribute is noted as optional, and if it is not present, the default option is used. With the default setting set to "If Possible", saving a conference without the attribute will result in the TMSBAPI returning an error if the participants do not support encryption. For example, external participants.

Attribute : DataConference

This attribute is noted as optional and as the "legacy" method of adding WebEx to the meeting. If this attribute is not present, the booking will automatically attempt to include a WebEx meeting, regardless of the setting within TMS for "Add WebEx To All Conferences". "No" is identified as the default, but this does not seem to be the case.



It has also been found that the "Participants" array will accept a "participant" set as a TMS system entity that is a system type of a bridge. Though not specifically called out in the TMSBAPI documentation, it has been understood that specific bridges can not be selected through a BAPI call. It would seem that this is not the case, and specific bridges can be selected.


Conditions:
Saving a conference using the TMS Booking API
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.