Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.1)
Page 8 of 90
In an upcoming release of Cisco TMSXE, this mechanism will be used to replace the “Downgrade to
Reservation” feature for most routing failure scenarios.
Reservation” feature for most routing failure scenarios.
Administrators can easily locate and diagnose defective conferences by going to
Administrative Tools >
Diagnostics > Conference Diagnostics
or
Booking > List Conferences
. Many defects can also be
resolved by the user directly from the client, and proposed actions for the user will be included in the email
notification returned from Cisco TMS, flagged as ACTION REQUIRED.
notification returned from Cisco TMS, flagged as ACTION REQUIRED.
A defective conference retains all properties of the booking request, and sets the endpoints to Busy unless
there is an endpoint availability conflict. Defective conferences will not be sent to endpoints or initiated until
all issues are resolved. Until resolved, it will also not be routed or consume any telepresence resources.
there is an endpoint availability conflict. Defective conferences will not be sent to endpoints or initiated until
all issues are resolved. Until resolved, it will also not be routed or consume any telepresence resources.
To achieve the behavior described above, external clients must use the latest version of Cisco TMSBA and
specify the booking mode BestEffortForced.
specify the booking mode BestEffortForced.
Booking mode Strict will make Cisco TMS decline conferences rather than save them as defective.
This change is versioned and does not affect clients using older versions of the API.
Booking confirmation email prefix
The title of booking confirmation emails will now include a prefix as follows:
All booking methods:
CONFIRMED: <conference title>
Bookings using Cisco TMSBA clients such as Cisco TMSXE only:
n
DECLINED: <conference title>
n
ACTION REQUIRED: <conference title>
Dial-in addresses in booking confirmation emails
Booking confirmation emails now always include dial-in numbers, regardless of whether participants are
scheduled to dial into the conference. For multipoint conferences hosted on an external bridge, dial-in
numbers to the bridge for all protocols used are included. For point-to-point calls or calls hosted on an
endpoint with embedded multisite, addresses of all participants are included.
scheduled to dial into the conference. For multipoint conferences hosted on an external bridge, dial-in
numbers to the bridge for all protocols used are included. For point-to-point calls or calls hosted on an
endpoint with embedded multisite, addresses of all participants are included.
Direct Join
You can now include links to two different applications and a web client from booking invites, so that users
can join directly from the invite. To support this, new settings have been added to
can join directly from the invite. To support this, new settings have been added to
Administrative Tools >
Configuration > Email Settings
:
n
Primary SIP Protocol Handler
n
Secondary SIP Protocol Handler
n
Web Client URL
n
Base URL for Icons
Note that both the protocol handler/URL field and the App Name field (to the right) for each of these settings
must be populated for each link to work.
must be populated for each link to work.
A preview of what the booking invite email will look like is displayed and updates in real time as you enter text
in the fields. Clicking the links to the apps and web browser in the preview will open them so it is clear what
users receiving the booking invite will see and have access to.
in the fields. Clicking the links to the apps and web browser in the preview will open them so it is clear what
users receiving the booking invite will see and have access to.