Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Field
Description
Prefer H.323 ID
over E.164 Alias
over E.164 Alias
n
Yes: H.323 ID will be favored over E.164 aliases when routing H.323 calls.
n
No: E.164 aliases will be favored over H.323 ID when routing H.323 calls.
Send Warning
When Ad Hoc
Conferences
Exceed This
Duration (in hours)
When Ad Hoc
Conferences
Exceed This
Duration (in hours)
A conference event is triggered in Conference Control Center when the duration of an Ad
Hoc conference has exceeded the set time limit (in hours). Set to 0 to disable (no event will
be triggered).
Hoc conference has exceeded the set time limit (in hours). Set to 0 to disable (no event will
be triggered).
Send Warning
When Auto
Attendant
Conferences
Exceed This
Duration (in
seconds)
When Auto
Attendant
Conferences
Exceed This
Duration (in
seconds)
A conference event is triggered in Conference Control Center when the duration of an MCU
Auto Attendant conference has exceeded the set time limit (in seconds). Set to 0 to disable
(no event will be triggered).
Auto Attendant conference has exceeded the set time limit (in seconds). Set to 0 to disable
(no event will be triggered).
Automatic MCU
Failover
Failover
n
Off: Cisco TMS will not initiate automatic MCU failover.
n
If conference start fails: Cisco TMS will automatically try another MCU if conference setup
fails during conference start.
fails during conference start.
n
If conference start or MCU polling fails: Cisco TMS will automatically try another MCU if
conference setup fails during conference start, or if the MCU is unresponsive during the
conference. For failover threshold, see the field below. We do not recommend using this
setting, as Cisco TMS could disconnect all participants from a conference if the network
connection to the hosting MCU is lost for a short time, despite the conference having
continued with no problem. This setting is ignored for conferences hosted by a
TelePresence Conductor.
conference setup fails during conference start, or if the MCU is unresponsive during the
conference. For failover threshold, see the field below. We do not recommend using this
setting, as Cisco TMS could disconnect all participants from a conference if the network
connection to the hosting MCU is lost for a short time, despite the conference having
continued with no problem. This setting is ignored for conferences hosted by a
TelePresence Conductor.
Note: Automatic MCU Failover is only supported for scheduled, non-cascaded MCU
conferences.
conferences.
Automatic MCU
Failover Threshold
(seconds after
first poll failure)
Failover Threshold
(seconds after
first poll failure)
Specify the number of seconds Cisco TMS will wait after the first poll failure before MCU
failover is executed.
failover is executed.
WebEx Settings
In Cisco TMS:
Administrative Tools > Configuration > WebEx Settings
This is where you configure the settings for the WebEx sites.
WebEx site and user credentials
For each user to be able to use WebEx in telepresence conferences, WebEx Site, WebEx Username and
WebEx Password must be entered in Cisco TMS.
WebEx Password must be entered in Cisco TMS.
There are two alternative ways to enter this information:
n
Using Single Sign On.
n
Entering the information manually.
Cisco TMS Administrator Guide (14.3.2)
Page 253 of 342
Administrative Tools
Configuration