= When adding a Cisco Meeting Server to TMS, you need to configure the following items before the server can be used in scheduled conferences12:

domain: This is the domain name of the Cisco Meeting Server, which is used to generate the conference aliases and URIs. For example, if the domain is cisco.com, the conference alias will be something like 123456@cisco.com. The domain name must match the domain name configured on the Cisco Meeting Server and the certificates used for secure communication.

numeric ID base: This is the starting number for the numeric conference IDs that TMS assigns to the conferences scheduled on the Cisco Meeting Server. For example, if the numeric ID base is 1000, the first conference will have the numeric ID 1000, the second conference will have the numeric ID 1001, and so on. The numeric ID base must be unique for each Cisco Meeting Server in TMS and must not overlap with any existing conference IDs in TMS.

numeric ID quantity: This is the number of numeric conference IDs that TMS can assign to the conferences scheduled on the Cisco Meeting Server. For example, if the numeric ID quantity is 100, TMS can assign numeric IDs from 1000 to 1099 to the conferences on the Cisco Meeting Server. The numeric ID quantity must be sufficient to accommodate the expected number of conferences on the Cisco Meeting Server.

The other options are not required or relevant for adding a Cisco Meeting Server to TMS. The DNS address and MAC address are not used by TMS to identify or communicate with the Cisco Meeting Server. The conference ID range is not a valid parameter for TMS.

References := Connect to TMS, Cisco Meeting Server - Configuration Guides