Day 1 - Real Time Collab Seminar and a Nasty sametime.ini variable
Tags :Sametime Sametime Gateway Real-Time Collaboration Gateway
During the day, which had decent turnout even right behind Lotusphere, a question arose revolving around trusting the IP address of the Sametime Gateway in the Sametime server. The person stated that they had placed the following:
VPS_Trusted_IPS=1
in the sametime.ini thereby allowing all IP addresses to be trusted. So in turn, did they still need to go into stconfig.nsf and list the IP address of the Sametime Gateway. Some research says this is not the setting they are using and that if they are using the one I think:
VPS_Bypass_Trusted_IPS=1
instead, then they are allowing any server to connect to their Sametime server. The first ini variable should have been a list of IP addresses and not a 1 (one). This setting should only be utilized during debugging connectivity issues and then should revert back to the trusted list. If they are running this in production, we will cover it tomorrow in how to clean it up.
Otherwise it was good to see everyone in the room was running Sametime, outside of 1 person, already. A few had test installs of 7.5.1 running but no one had gotten near the Sametime Gateway. The user ranges were from under 50 to over 10k. Which gives a nice slice of environment sizes to cover examples with. It seems there are still not enough Sametime marketing campaigns for some reason to reach everyone. While they have it in place, so much of the capabilities and architecture were still unknown to them. Wait till Day 2.
blog comments powered by Disqus
On Tuesday, February 20th, 2007 by Chris Miller
