If you install TMS and don't specify a custom install and your own SQL instance, using the basic options, it should install SQL on the local server with TMS. I think SQL 2005, I'm not totally sure, we've always used our own SQL server.
You can run TMS in demo mode, however it will be at limited capacity, I can't remember the numbers right now of how many systems you can manage with it, or other limited features, etc.
I don't fully understand this question, but you could get it up and running and play around with it to see if it suites your needs.
As the Q3, actually I want to build up a TMS, that will service the different companies and departments. A company only want to manage their TPs, Phone Book, and Schedule through the TMS and B company only want to manage their TPs, Phone Book, and Schedule through the same of TMS.
2) it should be three systems which can be managed without a key + other limitations (no provisioning, api restricted, ...) you could reach out to your Cisco contact / partner and ask for temporary license keys.
3) You could manage different customers with different phonebooks on your TMS,
but TMS is an enterprise sofware, not a real multi tenant system.
Though there are some companies who use it in that way, but you have limitations
regards separation of views.
Like you do not have groups for phonebooks and editing. You could map that to an external ldap or http server, but thats some programming around it.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...