Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6)
Page 9 of 79
For more detail on configuring these settings and customizing email templates, see the updated context-
sensitive web help or the Administrator Guide.
sensitive web help or the Administrator Guide.
New Bridge Utilization report
Note: This feature is a Technical Preview only: this feature could change significantly in future releases and
is not currently supported by TAC.
is not currently supported by TAC.
Accessed from
Reporting > Bridge Utilization
.
Two graphs and a data table show how much your bridges are being used. The upper graph compares the
total number of available bridge ports with the peak used port count for a given point in time. The lower graph
presents the same information as a percentage and shows the usage trend over time.
total number of available bridge ports with the peak used port count for a given point in time. The lower graph
presents the same information as a percentage and shows the usage trend over time.
The report uses the ISO week numbering model to define the timespan of data in the graph.
The raw data can be exported as a .csv file to Microsoft Excel (both 2010 and 2013 are supported). The data
is downloaded as daily regardless of which timespan has been selected in the Show Last menu.
is downloaded as daily regardless of which timespan has been selected in the Show Last menu.
The data is collected using an extract, transform and load (ETL) process in the SQL database. The ETL job
runs at 04:05 every day. This time is non-configurable. There is a new ETL log downloadable in the
Diagnostic Files log bundle for assistance in troubleshooting ETL job failure. The report page displays the
date and time that the ETL job last ran.
runs at 04:05 every day. This time is non-configurable. There is a new ETL log downloadable in the
Diagnostic Files log bundle for assistance in troubleshooting ETL job failure. The report page displays the
date and time that the ETL job last ran.
Port capacity and usage prior to upgrading to 14.5 is estimated after upgrade. This calculation is based on the
bridges currently in Cisco TMS and their current capacity, and the data is estimated from the day they were
added to Cisco TMS. Certain factors can affect the accuracy of this data, such as whether a bridge had a
capacity upgrade or reduction in the past. Once 14.5 is running however, capacity and usage are calculated
on a daily basis and will be correct.
bridges currently in Cisco TMS and their current capacity, and the data is estimated from the day they were
added to Cisco TMS. Certain factors can affect the accuracy of this data, such as whether a bridge had a
capacity upgrade or reduction in the past. Once 14.5 is running however, capacity and usage are calculated
on a daily basis and will be correct.
WebEx using deferred connect on TelePresence Server
When WebEx is included in a conference hosted on a TelePresence Server, the WebEx participant will now
be added to the bridge at conference start time, but will not connect until there is another participant in the
telepresence conference. In the conference event log, the WebEx participant will show as ‘SIP Dial Deferred’
when added to the conference, and ‘Connected’ once it is connected to the conference.
be added to the bridge at conference start time, but will not connect until there is another participant in the
telepresence conference. In the conference event log, the WebEx participant will show as ‘SIP Dial Deferred’
when added to the conference, and ‘Connected’ once it is connected to the conference.
This change does not apply to other bridge types.
Note that WebEx will not be connected during the early join window.