Implementing TMS

[Shawn Jones]

The company I work for just purchased TMS :banana: , and I am trying to get the ground work taken care of before I receive the software package, and give it to the Server Admin guys.

Any certian things that need to be done when implementing?

For right now, my 30+ codecs are ISDN and spread across the country, but connected to our corporate network, although, i can't make IP calls without stressing out the LAN guys.

Any insights would be greatly appreciated.

[Morgan81]

If you have your database maintained by a separate team make sure they aren't doing too many backups. We almost ran out of space when we realized that our database guys were making a million backups of the server, but not deleting them.
And for your server guys, TMS doesn't really need a huge machine to hold it, just follow the recommended specs from Tandberg and you'll be fine.
Oh and make sure you give the user "IUSR_[server name]" Site admin access if you have Polycom endpoints, that "user" is how IIS logs files into the database and if it isn't an admin, you won't log any call information.
I know there's a wealth of information on this site concerning TMS, just serch away and you'll find almost anything you'll need.

[Sean Lessman]

Oh and make sure you give the user "IUSR_[server name]" Site admin access if you have Polycom endpoints, that "user" is how IIS logs files into the database and if it isn't an admin, you won't log any call information.

You do not have to do that at all. You do not need to do anything with the IUSR account.

Sean

[Viking]

Older TMS versions pre 9.x found the single SP384 we have, but 9.6 and now 10.0 do not.

Error is
System not found! Please check that the address to the system is correct, and that the system can be contacted by the TMS server. Also, check that the SNMP community name set for the system is listed under the 'SNMP community name' setting under Administrative Tools -> Configuration -> Network

Both TMS and the SP384 have this set to "public", and the IP address is correct.

Where did the old scan/find function go from the old TMS versions??

[Sean Lessman]

Older TMS versions pre 9.x found the single SP384 we have, but 9.6 and now 10.0 do not.

Error is
System not found! Please check that the address to the system is correct, and that the system can be contacted by the TMS server. Also, check that the SNMP community name set for the system is listed under the 'SNMP community name' setting under Administrative Tools -> Configuration -> Network

Both TMS and the SP384 have this set to "public", and the IP address is correct.

Where did the old scan/find function go from the old TMS versions??

Depending on what software version you are running on the Polycom units it may be the Polycom. They make changes quite often to their products which requires us to then make patches to work with the products again. I don't think its intentional, but it does happen. There is a TMS10 patch available now that should do the trick.

Please contact your TANDBERG representative to get the patch etc.

Sean

[Viking]

SP 384 is running Firmware 7.5.4 dated 4 march 2005.

Will check with our agent for the patch. Be good if these were availible off the net support site somewhere.

Thanks for the pointer.

As a point of feedback: We are running TMS 10.0 on 2003 server and have tested changing the IUSR_ permissions on our test network without resolving the problem.
We have been looking at minimising the admin level accounts as much as possible in the environment.

[Morgan81]

You do not have to do that at all. You do not need to do anything with the IUSR account.

Sean
Right, what I ment was, don't change it's access.

[trapehzoid]

SP 384 is running Firmware 7.5.4 dated 4 march 2005.

Will check with our agent for the patch. Be good if these were availible off the net support site somewhere.

TANDBERG software.. ftp://ftp.tandberg.net