..............paraphrased:
The only limitation I've found is what I can make the system do, not what it is capable of........................
I've got a few hotels running MT, the least troublesome of all the WLAN's I've done.
Cant resist jumping in here...Every deployment should have it's 'setup' designed 'suitable for the purpose' of what exactly the customer wants. That makes OldMan's statement quite appropriate, and I'm sure everyone has one time or another been told what the 'best' system is. MT can do anything you know how to make it do. Sometimes thats good enough (suitable), sometimes its a nitemare(bad expectations), sometimes you dont know how it works so very well, and the customer loves it even more(more profit)...
MT is a powerful enabler of almost any network and/or wireless application. What is available from other sources is really just 'compiled code'. MT gives you assembler level capability, but you must 'make the system do' the job end-to-end by developing a customer and operator friendly environment. Some would just go get the shrink wrap, others would go find a project that uses what your 'system does'...Or you might not have the resources to make it do what it should. Maybe you need to do the project, or are a risk taker and like a challenge. MT can, will, and should be a component of 'the project' or possibly a very important point has been missed visiting this forum.
There are so many suitable opportunities that MT drops in, I would carefully review all projects for 'money pits' that the customer is specifying certain vendor specific functionality. Thats just a way for a bid to get the brand of equipment the customer wants, not what the bid requires...
Enough verbosity now....Had a very late network upgrade nite...Comments?...SZ