Which gatekeepers have been tested for the Cisco TelePresence MCU?
The table below shows the gatekeepers (and versions) that have been tested with the Cisco TelePresence MCU for calls. The latest versions of each gatekeeper support neighboring with the MCU's built-in gatekeeper.
We recommend that you use the Terminal / Gateway option unless you are using an MCU service prefix (in this case, use Gateway). Only use a different option if you are:
- using the Cisco VCS or Cisco acquired TANDBERG gatekeeper (with or without a service prefix), in which case use MCU (standard)
- using the Cisco Gatekeeper (with or without a service prefix), in which case use Gateway (Cisco GK compatible)
- using the VCON MXM Gatekeeper (with or without a service prefix), in which case use MCU (compatible)
|Gatekeeper||Version||Routed mode||Recommended registration type:|
|Service prefix||No service prefix|
|Cisco VCS||Up to X6.1||H.245-routed||MCU (standard)||MCU (standard)|
|Cisco acquired TANDBERG Gatekeeper||N4.0
|MCU (standard)||MCU (standard)|
|Cisco TelePresence||2.0(x) and later||Direct||Gateway||Terminal/Gateway|
|Emblaze-Vcon MXM Gatekeeper||4.29
|H.245-routed||MCU (compatible)||MCU (compatible)|
|Cisco Gatekeeper||12.3(19)||Direct||Gateway (Cisco GK compatible)||Gateway (Cisco GK compatible)|
* Disable H.264 if you experience problems with video.
Note: Over the last few years we have found that some older gatekeepers require particular registration types to enable the Cisco TelePresence MCU to register with them, which is why we have developed a range of settings. However, in testing more recent versions of third party gatekeepers we find that some of these settings are no longer required - but they remain in the product for compatibility reasons.
This article applies to the following products:
- Cisco TelePresence MCU 4200 / MSE 8420
- Cisco TelePresence MCU 4500
- Cisco TelePresence MSE 8510 blade
|April 13th, 2011||TAA_KB_47|