Cisco Cisco TelePresence Management Suite (TMS) Version 15
Examples of aliases generated from Numeric ID values
The following tables show examples of aliases generated from example Numeric ID values for both Unified
CM and Cisco VCS deployments:
CM and Cisco VCS deployments:
Field
Example value
Numeric ID Base
000
Numeric ID Step
1
Numeric ID Quantity
999
Table 6: Numeric ID example
Unified CM
Cisco VCS
Alias Pattern
5%
meet.%@example.org
First generated alias
5000
meet.000@example.org
Second generated alias
5001
meet.001@example.org
Last possible alias
5999
meet.999@example.org
Table 7: Examples of aliases generated from example Numeric ID values
Task 8: Setting TelePresence Conductor as the preferred
MCU
MCU
When TelePresence Conductor has been added to Cisco TMS, we recommend setting it as the preferred
MCU in booking. This ensures that Cisco TMS will route all conferences through the TelePresence
Conductor if an external bridge is needed.
MCU in booking. This ensures that Cisco TMS will route all conferences through the TelePresence
Conductor if an external bridge is needed.
1. Go to
Administrative Tools > Configuration > Conference Settings
.
2. Under
Advanced
, set Preferred MCU Type in Routing to Cisco TelePresence Conductor.
3. If you want all scheduled conferences to go through TelePresence Conductor, also set External MCU
Usage in Routing to Always.
4. Click Save.
Cisco TelePresence Conductor with Cisco TMS Deployment Guide (XC3.0 with 14.6)
Page 17 of 25
Configuring TelePresence Conductor in Cisco TMS