Absolutely. You need to be sure to put the -x- feature on the IOS. You can have additional features too. so if you want ip and gatekeeper/h323, you need -ix-
features of IOS, if you need IP/H323, Gatekeeper as well as Gateway functionality, you need -isx- features. The IOS version should be at least the latest 12.1T or better yet: the latest 12.2 mainline available for 7200.
Not sure what you mean as best solution for gatekeeper, but 7200 does support gatekeeper functionality and it can be an H323 GK in your network. The way you set it up depends on how you have designed the rest of your network. Here is some URLs on H323 networks with GKs:
Yes that is correct. We do not have General Deployment IOS on most of our Voice software but that is what you will need to use to be able to run most of the new features and have most of the new bug fixes. most of our customers run it everyday. Voice is on its way to become stable but to get to GD status of IOS, it takes time.
However, I checked CCO for 7200 12.1 mainline and 12.1.14 and 12.1.15 are both GD, this code is based on 12.07T. The basic gatekeeper functions are available for 7200 in this code so you can run this.
Actually for 7200 the -x- and the -s- is bundled onto the -i-
This is what I mean: when you go to download code on cco->software center-> IOS software -> 12.1 code or 12.2 code (whichever you choose), then you choose platform 7200, then IOS ver then you have to choose a "FEATURE SET". There choose IP and the IOS version will read
c7200-is-mz.121-15 (for example for 12.1(15) version).
The features set are those letters that follow platforms. For a 3640 the similar IOS feature for GK/GW/H323/IP would be: IP/H323 PLUS and would read
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.