Wait until you see the new IBM Sametime Unified Telephony (SUT) Lite Client software. SUT Lite Client is a licensing option that is available with Sametime 8.5.2. For example, with SUT Lite Client you can:
and receive telephone and video calls, even with someone who is
your Sametime contact list, right-click the name of a person you
want to call – even someone who is not online -- and select Call.
can also click a contact and then click the Call icon or in the
toolbar at the top of your contact list.
one-on-one or conference video calls
the Find a person or number field at the top of the Sametime
contact list, type the entire telephone number or the SIP URI of the
video conferencing device you want to call. Select the number when it
displays. In the open call window, click Video > Start Video.
With Sametime 8.5.2, we've introduced a great new security feature, "managed access," that lets people join your meeting rooms only when you or a room manager is there.
You can select this option either when creating a new meeting room or by changing the room settings of an existing meeting room.
This picture shows where this setting appears when you create a new meeting room:
This same feature is available for meetings accessed from a web browser: People who try to join your meeting when you're not there are put in a "waiting room", and they must wait until you're there before they can see any content in the room.
Use this feature whenever you don't want people in your meeting room when you're not there!
With Sametime 8.5.2, there are some new features that will help meeting room owners and managers manage their meetings.
First, we've added a new End Meeting button in the global toolbar so that meeting room owners
or managers can simply click the button to close the meeting room. This
action ends the meeting for all participants, so they no longer are in the room, and no longer see any room content. The room owner (or manager, depending on who presses the button) stays in the room, so they can be ready for their next meeting.
Here's what this new button looks like in the toolbar:
We've also added a feature that allows meeting room owners and managers to remove a participant from a meeting. From
within a meeting room, a room owner or manager simply right-clicks a
participant's name to remove that person from the meeting:
Users who are removed will see a notification that they've been removed, and they will no longer see the content of the meeting room.
When someone is removed from a room, there may be a "lockout" time, during which that person will not be able to re-enter the room. System administrators set this timeout period on a per-server level, using this configuration setting:
The Lotus Design Team is here at Lotusphere, with a user experience and usability lab, in room Asia 4 of the Dolphin Hotel. Stop by and test drive new product interfaces, and future prototypes, and give us feedback on your experiences with existing products. I'm in the lab, showing new interfaces for a browser-based version of Sametime IM, Sametime Advanced, and an iPhone interface for Sametime IM. I also invite you to attend a deep dive on Sametime Advanced, where I'll be covering UI features, and developer Alan Cooke will be providing architecture and implementation best practices. The deep dive is tomorrow at 4:15, session title ID405, in the Dolphin N. Hemisphere (rooms A-C).
Amy Travis is also in the lab, showcasing 8.5 Sametime eMeetings.
We're also giving away a free registration to Lotusphere 2010 in a raffle - the entry requirements are that you stop by the lab and test drive one of the many Lotus products showcased there by the actual product designers.
Looking forward to meeting you, and reinvigorating this blog in 2009!
You are on the phone with a co-worker, and while you are on the phone with that coworker, you also open a chat with that same co-worker.
Conversely, you are chatting with a co-worker, and decide to have a phone call, but you still use the chat channel with that co-worker while on the phone with him or her.
If these sound familiar to you, I'd like to hear from you! (And if they don't match how you work, I'd be interested to hear that, too!)
I'm especially curious to know what you are doing in the chat window that you can't do via the phone. Transfer files? Screen captures? Type something that your phone partner is having trouble understanding? Send links? Type something that you don't want to say out loud? :-)
Do any of you connect to multiple server communities, and if so, do you enable the community icon in the contact list? We are re-evaluating this design element and want to know more about why you choose to show it. If we were to remove this preference option, and therefore, the display of the icon from the contact list and the business card, would you miss it? Would it prevent you achieving a goal with the contact list?
It was great seeing many of you at Lotusphere. As always, your input was excellent, and I look forward to incorporating your feedback in our design work in 2008. If you did not get the chance to attend the conference, you can still provide product input. We'll be doing more usability testing this year, and you can participate in the lab, or remotely via a web conference. If interested, drop us a note at: email@example.com, or sign up here to be a tester for our other products: http://www.notes.net/usability
We're currently wrapping up our first release of Lotus Sametime Advanced, which introduces persistent chat rooms, new topic-based community chat tools that help you to create and reuse knowledge identified during chat sessions, and an "Instant Share" tool for screen sharing and remote control built directly into the Sametime chat window. Look for this new product by the end of Q1.
This is my first external post to this blog, the first of many to engage you in discussion regarding the design of the IBM Lotus Sametime instant messaging client. Following the success of other design blogs, such as Mary Beth Raven's Notes User Experience blog (http://www-03.ibm.com/developerworks/blogs/page/marybeth), I look forward to your input.
Let's get things started with a question about Sametime extensibility. I'd like to learn how you are extending Sametime. Feel free to respond to this blog, or send e-mail privately to (firstname.lastname@example.org)
- what types of plug-ins are you building?
- how well is the Sametime interface supporting the plug-ins you are building?
- how many plug-ins are you or your users adding to a Sametime client and running at once?
Let's start with these questions and I'll post some follow-up questions later in the week. I'm currently looking at how we should continue to evolve our extensibility model and interfaces.
We had our first Lotusphere User Experience lab prep meeting last week... We're busy working out new ideas for the coming year, figuring out what we need to improve in our lab. Feel free to post a comment here if there are things you'd especially like to see done and/or changed in our lab.
At IBM, we've been using agile development process for some time now, and that process includes designers being part of project scrums. But we've only lately started using agile methods *within* our design groups -- that is, having design-only scrum meetings, and 2-week sprint schedules to address the design work we have across the projects we work on.
As a design lead, I find the scrum process extremely helpful, so I know what all the designers on my team are working on, and can hear what's blocking people. The daily 15-minute meetings take almost no time, and we really hold tight to that meeting time limit.
One of the challenges we face is that design is an inherently iterative process, so we've needed to build iteration into our sprints. Also, new requirements crop up each day, as we learn more details from customers, get Beta feedback, or find that a developer has run into a hitch. So we've had to stay very flexible within our scrum process -- updating sprints as priorities shift.
Overall, though, I think it's been a great win. Much more productive than our older-style weekly "status meetings". I like the fast-pace of 15-minute meetings -- makes me wonder if more of my meetings could be that short!!
Hello, The Lotus User Experience Research team is gathering information on how you use and manage your contacts, as well as your thoughts on the future of contact management. Please take a few minutes to complete this survey and provide us with input to the future design direction of Contacts.