TMS Problems with Polycom codecs

[Morgan81]

I was wondering if anyone had a problem similar to this...
We have had TMS 7.2 and later 8.0 running since January. All Tandbergs running B 5 software and above are loggin CDR data and reporting traps as normal.
However, all Polycom's have not been logging any traps since one day in Feburay. No CDR data has been logged either. All codec settings are correct on the endpoint, TMS has been upgraded and reinstalled 2 times now and Tandberg seems to be stumped. I was just wondering if anyone else has seen anything like this.
It seems like it's a problem with the server settings but nothing was changed on the day it stopped logging data. This is driving me crazy and if anyone has any ideas I would really appreciate the input.

[robertk]

Is it ONLY the Polycoms that isn't logging?

If not:
Check that all the Watchdog traps are running on your TMS server. (both from the TMS WEB-page and also the WINDOWS services, all that is named TMSsomething should be started and running.)

Make sure that you don't have any other SNMP-aware software on that server.

This sound stupid, but has happend to me too many times:
make sure that the harddrive isn't full. :)

//Robert

[Morgan81]

Yup, only the ploycoms.
We have it on its own server so no other programs are installed on it and the Watchdog is running too.

[Morgan81]

Finnally fixed this stupid thing, turns out the problem was with user administration.
For IIS to communicate with TMS it needs a "user" to log into TMS and post to TMS' internal website. The user name is something like "IUSR_<name of TMS server>". When we were setting up user groups we had no idea what this was, so we left it alone and just left it in the base "User" group. Now TMS sticks you in that group as soon as you log in the first time automatically, so as a safety feature, we set all the access to nothing, that way if anyone trys to monkey around and finds our server, they get a page that simply says "you have no access to TMS". However, since we didn't realize it at the time, we didn't move the IUSR user to a group with appropriate access. As soon as I got access to the our server and looked at the IIS settings, it clicked and Polycoms are reporting as soon as I gave it the appropriate access.
8 months of headaches solved in 5 minutes.
God, do I love this profession :)
Just figured someone else could use this info.

[trapehzoid]

could be a polycom software difference. Did you upgrade your endpoints since it stopped working?

BTW.. IUSR is the windows account that anonymous web users use.. so logging into an anonymous site in IIS associates that user (by default)

[Morgan81]

The software is fine. It's working now. See above post.


Thanks anyway.

[jlu]

Morgan,
Perhaps you can help me!

I want to know if TMS can run on a port other than 80 like 8080. It is my understanding any web page running on IIS cab be configured to run on any desired ports. However, I am not sure if certain portion of TMS like the Web Java applets assume you are on port 80.

I am trying to findout if there are any problems running TMS with IIS associated IP address on a server with multiple LAN cards.

Thanks!

[Morgan81]

As far as I know TMS is pretty much a "fire and forget" type of system. What I mean is, unless you have special circumstances, TMS installs itself the best way possible and as long as the endpoints are setup correctly everything should be working as it should.
Granted we have a dedicated server specifically for TMS that we use that was specifically built for this application and all of the specifics as to the basic settings of IIS were taken care of before our group even took ownership over for this box. So I may not be able to give you the right answers. sorry about that, but I'm sure others on this board could help you out.

[dbl]

Just to enlighten about why TMS was failing with the PLCM's was that the polycoms send "http-traps" to TMS to a specific web page (as it does to GMS too if set up right). This web page MUST be acceccible anonymously as the Polycoms have no way of authenticating themselves. The polycoms post their http-traps to port 80, so if you want to move the TMS application to another port you have to let this anonynous part still stay on port 80 or else the logging will stop working.