Sametime Proxy SSL Certificate About to Expire

May 21, 2015

Thanks to my co-worker, Barb, for pointing this out to me.

The Sametime Proxy server ships with an SSL certificate to allow for push notifications to occur securely for the Sametime Mobile Chat client for Apple iOS via the Apple Push Notification Service (APNS). The current certificate expires 9 June 2015.

Before that date, Sametime administrators should download and apply an updated certificate to continue expected functionality for users.

If you haven’t updated your SSL certificate, time is running out.

More >


Sametime 9 Meeting Server Cumulative Hotfix – May 2015

May 5, 2015

IBM has released a cumulative hotfix for Sametime 9.

A new cumulative hotfix for Sametime 9 Meeting Server is available. A new feature to enable screen sharing using a browser plugin (instead of Java) on Windows has been added to Sametime 9 meetings. It also resolves a number of issues affecting Sametime Meetings.

More >

 


Sametime Status

January 7, 2014

I don’t think that this is something that I would put in my Sametime Location status. But, that’s just me.

SametimeStatus1

 

 


Sametime Gateway Update

December 7, 2012

A while back, I asked if anyone knew Sametime Gateway. I certainly appreciated the responses, however restarting the Gateway and the Nodes was not my idea of a good time.

Even if we were able to script it.

What did opening a PMR with IBM get us?

After much time and effort, on both IBM’s and our part, it came down to a problem between, not the Gateway and Google Talk, as I expected, but a communication issue between the Sametime Gateway and the Sametime XMPP server. That’s right kids, the IBM pieces weren’t able to communicate with each other, which resulted in the installation of an IBM patch. A patch that was unknown to the IBM techs that were trying valiantly to resolve this issue.

Wonderful.

However, this episode did bring me to a harsh conclusion – there are so many moving parts in these new tools from IBM, so many different areas within IBM involved in the development and support of these tools, that there is no one person or group that is responsible for, in this case, the Instant Messaging stack. You need a WebSphere person. You need a Sametime person. You may even need a person from Israel who was there on “Day One” when someone decided that moving Sametime to WebSphere was a good idea, someone with A LOT of institutional knowledge. Then, at the end, someone, somewhere, discovers a patch. A patch that was unknown to the tech, until he happened to ask the right person,the right question.

Apparently, important information is missing from a wiki somewhere.

While I certainly see the usefulness of having something like Sametime Gateway installed and functioning, it’s true value would be delivered by allowing more than just two external communities to communicate with it; AOL Clearinghouse and Google Talk. Yes, that’s right, this is probably the only Instant Messaging gateway on the planet that talks to only two communities. I see no indication from anyone that Yahoo will soon be added back into the mix. Nor do I see any other instant messaging community lining up to be included to Sametime Gateway.

Where is the value you are delivering with this product, IBM?