For H.323, we recommend that you configure the Codian MCU to use a service prefix before adding the system to TMS.
When TMS creates a conference on an MCU it assigns a numeric ID to that conference. Where there is more than one MCU, TMS might assign the same numeric ID to more than one conference (on different MCUs); however, by specifying a unique Prefix for MCU registrations for each MCU (Settings > Gatekeeper), it is possible to ensure that registrations and connections do not fail.
Alternatively, change the numeric IDs that TMS uses when creating conferences. To do this:
Go to Systems and select the MCU in the left-hand pane
Click Settings and then Extended settings.
For First meeting Id specify the first numeric ID to be used on this MCU.
Specify the Meeting id step.
The number of meeting IDs that could potentially be used by TMS is equal to the port count of the MCU; for example, for a 4520 there are 40 video ports and 40 audio ports and therefore a maximum 80 meeting IDs. These should not overlap with those of other MCUs unless a service prefix has been specified.
Sometimes TMS will report that a gatekeeper registration from the MCU has failed, even though the MCU reports that all gatekeeper registrations have been successful.
Using TMS with SIP
For SIP it is recommended that you follow the above procedure of ensuring meeting IDs do not conflict between MCUs because service prefixes are not supported in SIP. It is also recommended that conference SIP registration is enabled. To do this:
In TMS, go to Systems and select the MCU in the left hand pane.